If you switch to a terminal and kill file-roller or if you manage to
alt-tab into a terminal (even tough it doesn't become the top window),
then you can also kill file-roller. In both cases, your mouse will get
back. At least that's what happens with me (I got here looking for more
info on this bu
Sorry, but I can not test it right now, nor do I think I'll be able to
in the future. Someone else will have to check it out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/502375
Title:
Wine randoml
I'm going to have to but in here. I know that I am not contributing that much
to the bug report, but this needs to be said:
Wine does not have to meet "your specifications".
Ubuntu is still a Linux distro. And Wine is made for far more than "just
Ubuntu" or even "just Linux". Wine follows wide st
Could you try with the latest Wine and, in case it is still an issue,
provide a log? Maybe it is related to
https://bugs.launchpad.net/ubuntu/+source/wine1.2/+bug/502375
--
Winecfg audio tests fail in Maverick
https://bugs.launchpad.net/bugs/605880
You received this bug notification because you a
This is a Wine bug, unrelated to Wine packaging or Ubuntu. Should it
really be here? Isn't it invalid?
--
Office 2007 SP2 installer fails
https://bugs.launchpad.net/bugs/429234
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Is this really related to Ubuntu? Shouldn't you be reporting this as a
bug in Wine?
--
wine crashes while closing some windows game
https://bugs.launchpad.net/bugs/546622
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Here's more news about the issue:
https://bugzilla.redhat.com/show_bug.cgi?id=550736
So, as you see, it is a matter of interference between Pulse and Wine. It is
fixable by, as suggested by a comment replacing
{ (void *)0x0011, 0x6fef }, /* low memory area */
with
{ (void *)0x0011, 0
** Summary changed:
- Wine randomly cannot initialize sound [mmap() failed: ]
+ Wine randomly cannot initialize sound [Pulseaudio-related ; mmap() failed: ]
--
Wine randomly cannot initialize sound [Pulseaudio-related ; mmap() failed: ]
https://bugs.launchpad.net/bugs/502375
You received this bu
great for me!
You can even add more devices to redirect, so if somebody tries to
directly access dmix:0 you can direct that to pulse, so that only Wine
uses it (beware that pulseaudio itself is opening up dmix:0, so we might
have the need for a pulse-dmix device, hehe!). This way, there will only
b
** Summary changed:
- Wine randomly cannot initialize sound
+ Wine randomly cannot initialize sound [mmap() failed: ]
--
Wine randomly cannot initialize sound [mmap() failed: ]
https://bugs.launchpad.net/bugs/502375
You received this bug notification because you are a member of Ubuntu
Bugs, whic
As additional info, I've been tracing the issue to see if it is somehow
related to something that Wine does. I've managed to keep returning
hackish values from the alsa driver loading code, all the way down (or
up the stack) to LdrInitializeThunk. Yes, I actually was nuts enough to
keep returning a
The lack of completeness of this patch is a major blocker for me to
agree with its inclusion. Until Ubuntu 9.10, my Wine could use ALSA
without any issue, side-by-side with Pulseaudio. Back in that time I
managed to follow the "Pulseaudio Configuration Guides" around the
Ubuntu Forums.
Now, with e
This is a serious problem which has been laying around for too long. If
you, like myself, lurk around the WineHQ forums and AppDB, you will see
MANY logs with the "mmap() failed: Cannot allocate memory" message. It
seems, though, that these users do not care about it, probably because
Wine ends up
13 matches
Mail list logo
