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).

Totem crashes when trying to use the ’open file’ dialog to navigate to a certain subdirectory (containing only two subdirectories). This happens with 99% certainty. In the remaining 1% it happens when I proceed to one of the two sub-subdirectories. Unlike bug #891460, this is on an ext4 partition.

Mitenkä on, onko bugien raportoinnissa syytä olla tavallista harkitsevaisempi näin varhaisessa vaiheessa kehityssykliä (ennen feature freezeä)? Järjestelmähän on tässä vielä liikkuva maali, eli bugeja tulee ja menee jatkuvien muutosten myötä joka tapauksessa. Vievätkö bugiraportit tällöin kehittäjien resursseja turhaan, vai olisiko ongelmat päinvastoin hyvä raportoida mahdollisimman pian, jotta mahdollisimman monta myös ehditään korjata ennen julkaisua?

Bug still present in Precise.