https://bugs.winehq.org/show_bug.cgi?id=51667
Bug ID: 51667
Summary: Rufus can't use
Product: Wine
Version: 6.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aykutboray(a)gmail.com
Distribution: ---
When I opened to Rufus, it doesn't see my USB drives.
--
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=51585
Bug ID: 51585
Summary: Couldn't start debugger L"winedbg --auto 96 64" (1115)
Product: Wine
Version: 6.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vladimir.kokovic(a)gmail.com
Distribution: ---
Konsole log:
...
/root/files/spider.sh &
0024:fixme:htmlhelp:HtmlHelpW HH case HH_INITIALIZE not handled.
0024:fixme:htmlhelp:HtmlHelpW HH_PRETRANSLATEMESSAGE unimplemented
wine: Unhandled page fault on write access to 0000000000000000 at address
00007F92D42369BB (thread 0070), starting debugger...
0070:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 96 64"
(1115)
Read the Wine Developers Guide on how to set up winedbg or another debugger
...
wine --version
wine-6.14
Vladimir Koković, DP senior(70), Serbia, Belgrade, 10.August 2021
--
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=51527
Bug ID: 51527
Summary: Seeing and error message after upgrading to 6.13
Product: Wine
Version: 6.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mikes(a)guam.net
Distribution: ---
Just did dnf update and it installed wine 6.13.
Afterwards I generally run
wine notepad
from command line to have it do the test of update.
This time, it did the update fine, and comes up with the
blank screen and I closed the notepad.
After a short time, the following comes up on terminal
window.
wine: Unhandled page fault on write access to
0000000000000000 at address 00007F56D62BE3A1
(thread 0074), starting debugger...
0074:err:seh:start_debugger Couldn't start debugger
L"winedbg --auto 100 72" (1115)
Read the Wine Developers Guide on how to set up
winedbg or another debugger
Not sure why it can't start debugger.
I can run
wine winedbg --auto 100 72
afterwards, but it shows info, but doesn't apply to the
previous notepad run.
If I run notepad from the menu, you would never see this
message at all, so not sure if it is just something to
ignore.
Thanks.
--
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=50986
Bug ID: 50986
Summary: Rufus does not detect USBs because Wine recognizes
mounted pendrives as hard disks
Product: Wine
Version: 6.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: setupapi
Assignee: wine-bugs(a)winehq.org
Reporter: riky.8(a)outlook.it
Distribution: ---
Created attachment 69821
--> https://bugs.winehq.org/attachment.cgi?id=69821
The complete Rufus log generated by WineHQ 6.0 stable
On Windows the usb are seen correctly by Rufus and going into the driver
information I saw that the usb made use of the USBSTOR.SYS and usbstor.inf
driver, not present on WineHQ:
0024:fixme:setupapi:CM_Get_Device_ID_List_SizeA 0093EA30 "USBSTOR"
0x00000102: stub
My request is to add support for usb mass storage (USBSTOR).
The complete Rufus log generated by WineHQ 6.0 stable is attached.
The problem persists even on WineHQ 6.6 develop and staging. Unfortunately the
setupapi bugfixes did not include this enhancement.
--
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=49795
Bug ID: 49795
Summary: widl dislikes restricted attribute somewhen
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: kolan_n(a)mail.ru
Distribution: ---
When compiling SAPI IDL files I have encountered an error, that the attr is
invalid.
--
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=51734
Bug ID: 51734
Summary: Add a FreeBSD build VM
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: NetBSD
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
CC: fgouget(a)codeweavers.com
Depends on: 47903
Similar to bug #47903, but FreeBSD generally works with Wine :)
There have been several patches in recent months to fix breakages related to
the FreeBSD port that ideally would've been found by the testbot preemptively
rather than after the fact (e.g.,
https://source.winehq.org/patches/data/213680).
A test VM would also be welcome, but a build only VM would be a very helpful
first step.
--
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=47903
Bug ID: 47903
Summary: Add a NetBSD test VM
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: NetBSD
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
A GSoC 2019 student worked on improving Wine support on NetBSD:
https://www.phoronix.com/scan.php?page=news_item&px=Wine-NetBSD-GSoC-2019-D…
In order to keep Wine in good shape on NetBSD the TestBot should have a NetBSD
Wine VM. Currently this is blocked on:
1. A wininet patch:
https://www.winehq.org/pipermail/wine-devel/2019-October/151827.html
-> Once fixed setting a NetBSD build-only VM should be possible.
2. Setting up a NetBSD with an auto-login X session.
-> This will allow the TestBot to automatically recreate the live snapshot
when needed.
3. Some RPATH issues that break Wine's WoW support.
https://www.winehq.org/pipermail/wine-devel/2019-September/150284.html
--
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=51731
Bug ID: 51731
Summary: pls help me i am gettting this error while openning a
.exe file
Product: Wine
Version: 6.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ipokdrvhpkeissxlfe(a)ianvvn.com
Distribution: ---
Created attachment 70616
--> https://bugs.winehq.org/attachment.cgi?id=70616
the bug pls help
help me with this error im new to wine
--
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=51727
Bug ID: 51727
Summary: Civilization: Beyond Earth demo crashes on exit
Product: Wine
Version: 6.16
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 70614
--> https://bugs.winehq.org/attachment.cgi?id=70614
Backtrace
Steps to reproduce:
1. (Optional) Open winecfg and enable the virtual desktop to prevent locking up
your computer when the game crashes.
2. Install Steam for Windows and log in.
3. Run `wine 'C:\Program Files (x86)\Steam\Steam.exe' steam://install/322610`
to install the Civilization: Beyond Earth demo.
4. Launch the game, skip the intro video, wait about a minute for the splash
screen to disappear, click SINGLE PLAYER, then click SETUP GAME.
5. Click any option on each of the five tabs and then the game will actually
start.
6. Select a landing site. At this point the game becomes much more interactive.
7. Click the hamburger menu in the top right corner and then click EXIT TO
WINDOWS.
During exit, the game crashes on a null pointer. The backtrace from the Wine
crash dialog is attached.
--
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=48649
Bug ID: 48649
Summary: Guild Wars 2 / TaCo : unable to start overlay, get
only black screen
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: aeris+winehq(a)imirhil.fr
Distribution: ---
It's currently not possible to run an overlay like TaCo
(http://www.gw2taco.com/) over the running game. TaCo starts and works be we
got a black screen everywhere, instead of a transparent background.
See render here: https://www.gamingonlinux.com/forum/topic/3966
Trouble reported here to: https://github.com/doitsujin/dxvk/issues/1225
--
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.