Actually, in my case it was apparmor-notify. It was starting via the old
/etc/X11/Xsession.d mechanism which made it start on a different bus.
Moving the autostart to /etc/xdg/autostart fixes this issue for me.
Thanks to Sebastien and Marc for helping me diagnose this. Assigning to
myself-- I'll fi
Do other people experiencing this bug have /etc/X11/Xsession.d
/90apparmor-notify installed?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1288241
Title:
gnome-screensav
Looked at this slightly more and have more information:
$ ps auxww|grep [g]nome-screen
jamie 3033 0.0 0.2 511004 18932 ?Sl Mar24 0:10
/usr/bin/gnome-screensaver --no-daemon
jamie 3657 0.0 0.2 506844 16460 ?Sl Mar24 0:07
/usr/bin/gnome-screensaver --no-daemon
$
This happens to me with and without suspending.
** Tags added: rls-t-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1288241
Title:
gnome-screensaver is running
This happens to me even without suspending.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1288241
Title:
gnome-screensaver is running twice and prompts twice to unlock
It renders essential features or functionality of the package (or a
dependent one) broken.
** Changed in: lightdm (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member o
It seems that gnome-session reloading before suspend. Because when I
click to Suspend - display blink with black screen ones and after, about
4-5 seconds I see ordinary desktop and folders.
Second lock screen process name (Gnome Lock screen) is "gnome-
screensaver-dialog".
--
You received this b
This bug affects me too! (see more details
https://bugs.launchpad.net/bugs/1295673)
And I think it associated with
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1184262
Becouse:
When laptop suspending, before display turns off and laptop become fully
suspended - I see Default Ubunt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.
Checked again, as im using lightdm by default (gdm also installed by
gnome-shell)
oem@dev32:~$ ps auxww|grep [g]nome-screensaver
oem 2224 0.0 0.3 179692 14220 ?Sl 06:23 0:01
/usr/bin/gnome-screensaver --no-daemon
oem@dev32:~$
So it seems "always" clean on my system.
--
You
Adding a lightdm task too. Perhaps it is actually something in the
session. Please reassign as necessary.
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gn
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.
Note, this doesn't *always* happen, it only *sometimes* happens (but it
does seem most of the time for me).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1288241
Title:
Cant confirm here on Trusty i386:
oem@dev32:~$ ps auxww|grep [g]nome-screensaver
oem 2103 0.0 0.3 178320 16180 ?Sl 07:20 0:06
/usr/bin/gnome-screensaver --no-daemon
oem@dev32:~$
but what is strange for that LTS release is : we are mixing 3.6, 3.8
and 3.10 gnome packages. Th
14 matches
Mail list logo