** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/904340
Title:
nautilus crashed with SIGSEGV in g_simple_async_result_complete()
To manage notifica
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/896494
Title:
metacity crashed with SIGABRT in raise()
To manage notifications about this bug go t
*** This bug is a duplicate of bug 862950 ***
https://bugs.launchpad.net/bugs/862950
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/893537
Tit
#27: did the trick for me too, thanks!
For the record: I've upgraded from karmic to lucid and switched from
XFCE to GNOME at the same time and got this problem.
--
Waiting for sound system to respond
https://bugs.launchpad.net/bugs/400973
You received this bug notification because you are a memb
Oh, I take it back--after a restart it finally worked with xscreensaver.
My question about patching gnome-screensaver is still actual I think.
--
gnome-screensaver not functioning
https://bugs.launchpad.net/bugs/411350
You received this bug notification because you are a member of Ubuntu
Desktop
Hey, I've just removed gnome-screensaver and installed xscreensaver
instead. It doesn't work either!
Can it be something is broken on some lower level?
I've re-logged in, checked that xscreensaver process is running,
adjusted settings to activate after 1 minute of idle time--and it didn't
work,
On Fri, Dec 4, 2009 at 18:48, Marc Deslauriers
wrote:
> I'm not sure what "Not really" means. Does gnome-screensaver come up
> after the idle timeout or not?
It means "not". Sorry for confusion.
--
gnome-screensaver not functioning
https://bugs.launchpad.net/bugs/411350
You received this bug n
On Fri, Dec 4, 2009 at 18:18, Marc Deslauriers
wrote:
> Alex: if you set the screensaver to "blank screen" only, does it work?
Not really.
--
gnome-screensaver not functioning
https://bugs.launchpad.net/bugs/411350
You received this bug notification because you are a member of Ubuntu
Desktop Bu
On Fri, Dec 4, 2009 at 17:30, Marc Deslauriers
wrote:
> Alex:
> Could you please run the following command and attach or send me the
> resulting file:
> gconftool-2 --dump /apps/gnome-screensaver /desktop/gnome/session
> /desktop/gnome/lockdown > debug.xml
Marc: Here you go. :)
** Attachment
On Fri, Dec 4, 2009 at 16:08, Marc Deslauriers
wrote:
> I think we may have more than one problem here.
>
> Alex:
> You're using xubuntu?
Yep.
> After logging in, is the gnome-screensaver process running?
Yes.
--
gnome-screensaver not functioning
https://bugs.launchpad.net/bugs/411350
You rec
On Fri, Dec 4, 2009 at 15:05, Marc Deslauriers
wrote:
> Yes, a reboot is necessary after installing the updated package.
Of course, I rebooted the machine before testing.
--
Alex
--
gnome-screensaver not functioning
https://bugs.launchpad.net/bugs/411350
You received this bug notification beca
On Thu, Dec 3, 2009 at 22:29, Marc Deslauriers
wrote:
> Could you please try the gnome-screensaver packages in the following PPA
> once they've finished building:
>
> https://launchpad.net/~mdeslaur/+archive/screen-locking
>
> Even if you don't use totem, it could be when totem is used as a firefo
Hey, I still have this problem on up-to-date karmic Xubuntu amd64!
The screensaver doesn't start automatically, but works correctly if I
run `gnome-screensaver-command -a' or lock the screen with Ctrl+Alt+Del.
Screen blanking is working correctly in the meantime.
--
gnome-screensaver not functi
13 matches
Mail list logo
