https://bugs.winehq.org/show_bug.cgi?id=8277
Anastasius Focht <focht(a)gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Hardware|Other |x86
Summary|Enhancement: |Windows Sysinternals
|NtQueryInformationThread |Process Explorer and other
|with |tools show zero thread
|ThreadQuerySetWin32StartAdd |start address
|ress (Windows Sysinternals |(NtQueryInformationThread
|Process Explorer and other |with
|tools) |ThreadQuerySetWin32StartAdd
| |ress info class)
OS|other |Linux
--- Comment #15 from Anastasius Focht <focht(a)gmx.net> ---
Hello folks,
still present.
1) start 'Process Explorer'
2) right click on a process -> 'Properties'
3) select 'Threads' property sheet: all threads have zero start address
$ sha1sum ProcessExplorer.zip
47ec2b9d1ef2ea2a997722da6ec7749f4cacc4ab ProcessExplorer.zip
$ du -sh ProcessExplorer.zip
1.2M ProcessExplorer.zip
$ wine --version
wine-1.7.13-27-ge610713
Regards
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=9221
Marti Raudsepp <marti(a)juffo.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|marti(a)juffo.org |
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=5227
--- Comment #13 from Guy Roussin <guy.roussin(a)teledetection.fr> ---
Created attachment 47601
--> http://bugs.winehq.org/attachment.cgi?id=47601
"winspection" of the dialog ... good/bad
This image shows the difference between the winspection (winspector) of the
"Open file" dialog which does not respond to any mouse clicks (only with the
keyboard) and the window "Save As" which behaves correctly.
It seems that the button / checkbox "Automatically ..." hides the rest of the
components to the mouse.
I hope it can give a lead to the resolution of this bug ...
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=35638
Bug ID: 35638
Summary: Weird Steam bug
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: luciferianbastard666(a)gmail.com
Created attachment 47598
--> http://bugs.winehq.org/attachment.cgi?id=47598
Crazy blank screen
What on earth is this? I try to open up steam, and I get this absurd window!
How is one to use Steam with this crap? I have no idea what causes it, but it
is in desperate need of repair.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29276
Bug #: 29276
Summary: 360chrome couldn't open embed iexplore but open url in
native Linux browser instead
Product: Wine
Version: 1.3.34
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
Classification: Unclassified
1. Download 360chrome browser:
wget http://down.360safe.com/cse/360cse_4.2.0.516.exe
$ sha1sum 360cse_4.2.0.516.exe
39bb79fc6e4846763a8be86ff86524d64a86adf7 360cse_4.2.0.516.exe
2. install 360chrome
3. start 360chrome with --no-sandbox
$ cd .wine/drive_c/users/fracting/Local\ Settings/Application\
Data/360Chrome/Chrome/Application/
$ wine 360chrome.exe --no-sandbox
4. open a website, such as http://www.winehq.org
5. click on the "极速" button (beside the url bar), switch from "极速"/"Webkit
Mode" to "IE Compatible Mode", then the button will display "e兼容"
Expect result:
Open an embed IE in 360chrome browser, display the website
Actual result:
Open the website in a native Linux browser, for me it is in the default browser
Chromium.
Is this a wine bug?
Is there any register key useful for working around this issue?
Thanks!
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=35631
Bug ID: 35631
Summary: Add giflib support
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mathieu.malaterre(a)gmail.com
It would be easier for package maintainer if wine would build out of the box
using a system installed giflib.
Basically this would help us toward closing
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466181
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=4066
--- Comment #45 from Nick <nickmarko(a)gmail.com> ---
(In reply to theAntiBob from comment #44)
> (In reply to Austin English from comment #41)
> > (In reply to comment #40)
> > > First submitted this bug nearly years ago and it is still an issue.
> >
> > It's not implemented, and no one has stepped up to write it. It's only used
> > by older games, and there's an easy workaround.
> >
> > That said, volunteers are welcome.
>
> Doesn't seem like an easy workaround to me... The list of affected apps for
> this bug is fairly large (and ovbiously incomplete)
>
> Homeworld 2 network issues are in no way resolved by using "winetricks
> directplay" and/or modifying any registry values
>
> Where would one contribute to any effort to improve the issue?
>
> Status: Still NEW?
> Importance: Meh?
Surely it couldn't be hard for someone to at least write a universal shell
script to properly implement the workaround?
Now I'm waiting for the inevitable "Well, why don't you do it?".
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8539
Nikolay Sivov <bunglehead(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |35635
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8539
--- Comment #29 from Nikolay Sivov <bunglehead(a)gmail.com> ---
Created attachment 47592
--> http://bugs.winehq.org/attachment.cgi?id=47592
patch
So it was actually a clearly visible problem, or two:
- with my recent patch I screwed up pointer incrementing when copying;
- after copy destination array wasn't updated with actual element size,
this results in a crash on destroy, because it tries to do 32 byte increments
(default value), instead of 16 bytes in this particular case of a structure
with 2 BSTR pointers.
After this fixed (patch attached), next problem is clear:
---
fixme:scrrun:filesys_QueryInterface Unsupported interface
{7fd52380-4e07-101b-ae2d-08002b2ec713}
fixme:scrrun:filesys_QueryInterface Unsupported interface
{37d84f60-42cb-11ce-8135-00aa004bb851}
fixme:scrrun:filesys_get_Drives 0x7d510ef4 0x33f260
fixme:scrrun:filesys_QueryInterface Unsupported interface
{df0b3d60-548f-101b-8e65-08002b2bd119}
---
with Runtime error '445' message box.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=4066
theAntiBob <theantibob(a)hackermail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |theantibob(a)hackermail.com
--- Comment #44 from theAntiBob <theantibob(a)hackermail.com> ---
(In reply to Austin English from comment #41)
> (In reply to comment #40)
> > First submitted this bug nearly years ago and it is still an issue.
>
> It's not implemented, and no one has stepped up to write it. It's only used
> by older games, and there's an easy workaround.
>
> That said, volunteers are welcome.
Doesn't seem like an easy workaround to me... The list of affected apps for
this bug is fairly large (and ovbiously incomplete)
Homeworld 2 network issues are in no way resolved by using "winetricks
directplay" and/or modifying any registry values
Where would one contribute to any effort to improve the issue?
Status: Still NEW?
Importance: Meh?
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.