Here’s i915_error_state as requested on https://wiki.ubuntu.com/X/Troubleshooting/Freeze#. I made a copy (using cp), and I should mention that my first try to do so resulted in an error message: ”failed to extend” … and something about not having enough memory, in Finnish. When I preceded the command with LC_ALL=C to get the entire error message in English, the copying was suddenly successful. I hope this doesn’t mean the actual error state from the hang had been replaced by a new state which I’m now submitting.
Happens consistently when playing video using VLC (other players also), after about 5 minutes. Rockman 2 speedrun from tasvideos.org is pretty reliable for reproducing this. :)
The video goes blank (blue) and can no longer be seen until after reboot, though the playing does resume.
Bug #896899 looks similar on the surface, but I’ve little understanding of these types of crashes so I felt it best to report separately.
After switching to fbdev driver the crash can no longer be reproduced.
I can confirm the bug and the workaround both hold on an up-to-date Precise system with a Radeon HD 3200.
Thank you, I found this post useful so I flattr’d your Twitter account.
Mario, here’s output from the commands you asked.
Output of dkms status, ls /var/lib/dkms -R
I marked this as being Fixed for ”totem (Ubuntu)” because –no-existing-session has been removed from Totem altogether ( I’ve verified this in 12.04). So the bug as I initially described it no longer exists in recent *buntu.
Just a note that this no longer happens now that I’m running 12.04 with Unity; Unity’s run dialog expands tilde correctly. Still broken in Gnome panel 3.2.0 though.
Steps to reproduce:
1. Disable power saving
2. (Re-)boot (logoff may suffice, though I’ve not tested this)
3. Login and don’t touch mouse or keyboard after that
4. Wait
What happens:
Within half an hour (on my system at least) the display signal is turned off (monitor reports ”No signal”).
What you expect to happen:
The screen to stay on as indicated by power saving settings.
Additional info:
1. Any keyboard or mouse activity seems to make it obey the setting: after that the screen won’t go blank on its own (irregardless of whether or not the bug has manifested itself during the session).
2. I’ve disabled screensaver as well, though that probably doesn’t concern this bug.
3. From bug #854624’s comments I picked up this settings listing command, in case it helps:
jani@saegusa:~$ for c in `dconf list /org/gnome/settings-daemon/plugins/power/`; do echo -n ”/org/gnome/settings-daemon/plugins/power/${c}=”; dconf read /org/gnome/settings-daemon/plugins/power/${c}; done
/org/gnome/settings-daemon/plugins/power/sleep-display-ac=0
/org/gnome/settings-daemon/plugins/power/sleep-display-battery=0
Yksi helposti kokeiltava niksi on ottaa laitteistokiihdytys (Hardware Acceleration) pois päältä flashin asetuksissa. (Mikäli sillä ei ole vaikutusta, se kannattanee palauttaa takaisin oletusasetukseen.)
As the title says. Steps to reproduce:
0. Run Maximus.
1. Run gnome-terminal.
What I expect to happen:
Gnome terminal window to open maximized.
What happens instead:
Gnome terminal window opens unmaximized.
Additional notes:
/apps/maximus/exclude_class only has Totem listed (no gnome-terminal).