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.

This no longer happens so I’m marking this as being fixed.

Tuon Commonsin suositteleman attribuutiotavan uskottavuutta syö se, ettei sitä käytetä WMF:n omissakaan projekteissa. Esim. Wikipediassa kuvan linkitys sen kuvaussivulle katsotaan riittäväksi, eikä noita erillisiä tekijän- ja lisenssinselityslitanioita artikkeleihin upotettujen kuvien alla käytetä.

Ei niistä erillisselvityksistä tietenkään haittaakaan ole, mutta ainakaan minä en jaksa vaivautua. :)

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

IMHO enin osa noista palvelun erillisistä osista, jollei kaikki, voitaisiin aivan hyvin kattaa tämän pääartikkelin alla. Ne ovat pahimmillaan pelkkiä yhden virkkeen tynkiä ominaisuusluettelon kera.

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.

Then I would rephrase this into a bug report as follows: currently, the toolbar navigational buttons (previous, next) are positioned to the right from the location bar. This is inconsistent with what most users probably expect, which is the way they are located in a web browser.

The three web browsers I currently have installed on this system position these elements as follows:

1. Epiphany 3.2.1: previous, next buttons above the left end of location bar.
2. Firefox 9.0: previous, next buttons to the left from location bar.
3. Chromium 15.0.874.121: previous, next buttons to the left from location bar.

From my personal anecdotal evidence, with this background, I say suddenly finding the navigational buttons from the right end of the location bar in one app is undly arduous. Thus this bug’s title should be: Move the navigation buttons to the left of the location bar.

(IIRC this was also how the buttons were back in Gnome 2. If there was some usability reasoning behind moving them to the right, I’d be interested in reading about it.)