Still present on 13.10
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/35643
Title:
Disabling subtitles hangs Totem
To manage notifications about this bug go to:
https://bugs.launchpa
I'm debugging wrong. Please give me some suggestion.
I've attached gdb to gnome-session, I have reproduce the bug (sudo
/usr/share/checkbox/scripts/suspend_test --enable repeat) but this is all I get:
...
[Thread 0x7fa275fa2700 (LWP 2232) exited]
[Thread 0x7fa2757a1700 (LWP 2233) exited]
[Thread 0
To get the stacktrace we have to attach to gnome-session, right?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/882956
Title:
[Oneiric] [Dell XPS M1330] Gnome session exits w
Hi guys, I've found a regression on my laptop (Dell Latitude E6500).
Stutus before upgrading to 2.32.0-2ubuntu2.1:
Duplicate entries of the same battery listed but no "estimating" bug.
Status after upgrading to 2.32.0-2ubuntu2.1:
Clicking on g-p-m icon show up two lines: one for my actual battery
Peter, you were viewing video using Flash?
I notice much more hangs playing Flash content and every time last line of
Xorg.0.log was "AIGLX: Suspending AIGLX clients for VT switch" .
Someone expert of AIGLX, Xorg, intel video cards can suppose where the bug can
be?
--
You received this bug noti
The problem I describe (and probably also of Sean Fenton and others upgrading
to natty) seam the same of Bug 780653.
What do you think about it?
Sorry for my bad english.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensa
I think the cause of this bug was misunderstood by someone.
I also get hanging after screen goes blank in 11.04 (natty) but switching to
VT1 and killing gnome-screensaver doesn't help (and I don't even think it's the
cause).
Every time I notice this problem the last line of Xorg.0.log was like: