I've just upgraded a laptop, in the last 2 days, Jaunty - Karmic -
Lucid (one upgrade each night).
(This was a very vanilla Jaunty installation, previously upgraded from
Intrepid and kept the same for ages, very little extra installed,
virtually no settings changes, and used by its owner almost
Responding to comment #18, Milan Bouchet-Valat wrote on 2010-05-02:
So we'd need to be sure that the actual wanted behavior is adding the
applet. Else, another solution would be to autostart gnome-volume-
control-applet when we detect that the applet is not present.
- How about *not remove*
Leann Ogasawara wrote:
Thanks for the update Mike. So this would appear to be resolved for
Intrepid. Although from your comments it would appear this was not
resolved with the newer 2.6.27 kernel as you mentioned originally
testing showed no improvement with 2.6.27 but after an Intrepid
Sebastien Bacher wrote:
the comments indicate the issue is not a nautilus-cd-burner one
I disagree. Which comments?
The comment from me indicates that it's exactly nautilus-cd-burner.
Other burning programs work: Brasero, cdrecord, etc. (Apart from
Brasero getting confused at the end, trying
Thank you Benjamin. That is so not obvious and _very_ useful for
connecting to Windows servers and VMs.
Actually, F11 makes no difference. Mouse focus is the trick.
The natural thing doesn't work. You're using the remote desktop, it has
mouse focus, and you type ctrl+alt+del - that doesn't
Martin, if I understand right that means the problem I'm seeing is fixed
upstream now, and will get to the Ubuntu version soon?
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
That symlink may well work if you're using GDM. If you start Gnome
without using GDM, though, it still locks up.
Aside: Shouldn't the name of the GDM socket be an environment variable,
passed down from GDM to gnome-screensaver just like all the other
sockets, D-BUS, SSH agent etc...
--
screen
I'm afraid it is not properly fixed in 2.17.7-0ubuntu2.
When the X session is started from GDM, it probably works. (I've seen
it lockup, but I suspect that was before I picked up 2.17.7-0ubuntu2).
However, when the X session is started using 'startx' (which starts the
X server then runs
