In Precise, window auto-maximize is disabled on monitors with a resolution above 1024 × 600 [1]. I have a bigger resolution, but I prefer maximized windows anyway. I want Update Manager to start maximized.
What I’ve tried so far:
- In Compiz Config Settings Manager, I have Place Windows activated and ’Windows with fixed placement mode’ has windows matching the rule ”(name=gnome-terminal) | (name=update-manager)” set to ’Maximize’. With this, Gnome Terminal starts maximized, Update Manager does not.
- In Compiz Config Settings Manager, I have set a Window Rules [2] rule to match ”name=update-manager”. Irregardless of any rules set or not, activating Window Rules results in not being able to bring out Unity Launcher anymore, Alt+Tab window switching becoming slow or nonfunctional entirely and the screen sporadically freezing completely. Not a viable option apparently.
- I’ve installed Maximus [3] and started it. Update Manager ignores it (or vice versa).
I’ve not tried devilspie and would prefer not to. Having to configure something external for this would seem stupidly redundant with (the no-brainer) Maximus and all these Compiz options already available. I just can’t seem to make them work.
Bryce; no problem (and thanks for your working on this), for me the fbdev workaround is good enough to work and live with on this setup. If others affected by this feel differently, do take over with upstream.
Steps to reproduce:
1. In (gnome-control-center) Keyboard settings’ Shortcuts, set the shortcut for ’Lock screen’ to Scroll Lock.
2. Press Scroll Lock.
What happens:
Nothing (screen doesn’t get locked).
What I expect to happen:
For the screen to get locked.
What works:
* Setting ’Lock screen’ shortcut to Shift + Scroll Lock, Ctrl + Scroll Lock etc.
* Setting ’Lock screen’ shortcut to, for example, the Pause/Break key (which is right next to Scroll Lock on common keyboards).
* Setting Scroll Lock as the ’Lock screen’ shortcut in Unity 2D.
Other notes:
Pressing Scroll Lock does nothing whether set as screen locking hotkey or not, so it shouldn’t be tied to some other function either.
Should the first list include –quit too, as that one also doesn’t seem to work? It (2.96) doesn’t print a warning though, either:
jani@saegusa:~$ rhythmbox-client –quit
jani@saegusa:~$
jani@saegusa:~$ rhythmbox-client –debug –quit
(18:28:03) [0xc97800] [rb_debug_init_match] rb-debug.c:240: Debugging enabled
(18:28:03) [0xc97800] [main] rb-client.c:707: quitting existing instance
jani@saegusa:~$
I reported this on Launchpad [1] and was forwarded upstream.
Steps to reproduce:
1. touch ~/foo_åäö
2. In Nautilus, point at the file created in step 1
3. Right-click for context menu
4. Select Move to Trash
5. Press Ctrl-Z/Select Undo from the Edit menu
What happens:
Nothing
What I expect to happen:
For the file to recover from trash to ~.
What works:
* Undoing Move to Trash with files with no scandinavian letters in their path/filename.
* Recovering foo_åäö by opening Trash and selecting Recover from context menu.
More info:
* Could be that more characters, perhaps all non-ASCII characters render Nautilus’ Undo impotent — I’ve only tested å, ä and ö.
* The Finnish translation for Desktop (~/Desktop) is Työpöytä, which means files moved to trash from Desktop can’t be recovered. Nasty.
*[1] https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/973620
For the image labels, you could publish a brief spec/howto of how you create the default labels, crowdsource translated versions and then pick the right one in the code based on current locale.
But then again I think simple text instead of images would work even better. I’m not sure what you mean when you list ”Style (e.g. prev/next buttons) cannot be customized”: surely that applies to images more than text, which can be bent any which way with CSS?
Strangely, with Chromium 18 I could no longer reproduce this with new profiles, but with my old profile it was still there.
Ah, it seems to be just U2D which I was testing earlier today. I too can file all the bugs I want against ’unity’, but if I try `ubuntu-bug unity-2d` all I get is the ”third party package” error. Reproduced this also in a clean VM to be sure.
With Unity updated from the PPA, you cannot file bugs against it using ubuntu-bug, you’ll just get an error message saying ”Please remove any third party package and try again.” You can still file bugs directly on Launchpad using the browser, but then the report won’t have the logs attached to it.
Ah, sorry about that, I thought you wanted both updated logs from Lucid *and* tests with newer versions.
I just gave the current 12.04 Beta a spin and am happy to report that the issue seems to have been fixed there: despite my best efforts I couldn’t make it crash with the gallery site. It did remain somewhat sluggish to browse but the Oops never occurred.