According to a report today in bug 925309, the kernel part of this might
have been fixed, making the processes killable. Also, if bug 913787 is
correct, ecryptfs might have a hand on these 100% CPU processes
(although not necessarily in the totem case, where I agree with comment
#88).
--
You rece
Same as #5, but haven't yet tried to kill processes, I had always used
the sudo service gdm restart route.
Also 11.04 up to date with classic desktop, random screensaver and
monitor suspend.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribe
I'm sorry for posting in this old bug, but I'm having this issue with
yet another program. See for yourself this sequence of commands:
$ sudo -s
# uname -a
Linux tacitus 2.6.35-23-generic #41-Ubuntu SMP Wed Nov 24 10:18:49 UTC 2010
i686 GNU/Linux
# ps ax | grep amule | grep -v grep
2912 ?
I tried the export LIBXCB_ALLOW_SLOPPY_LOCK=[1|true] thing to no avail,
just as some others have reported previously.
As for the -noxcb packages, I got a violation fault with them.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notif
@Bryce: Of course you're right, the xcd/xcb thing was an unfortunate
mental glitch on my part.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk i
I hit this bug recently using the player/stage robot simulator [1].
Although the main GUI works okay, the amcl driver debug GUI will cause
player to crash with the familiar locking assertions. I think that
player/stage uses XCD through the C binding.
I know the above description is not totally hel
