** Changed in: lightdm (Ubuntu)
Status: Incomplete => Invalid
** Changed in: lightdm-gtk-greeter (Ubuntu)
Status: Incomplete => Invalid
** Changed in: upstart (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Last updated in 2016. Is this still an issue with these greeters?
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: lightdm-gtk-greeter (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: upstart (Ubuntu)
Status: Confirmed => Incomplete
--
Unbelievable
Since this bug was originally released:
14.04 has had 4 mayor updates, 14.04.1, 14.04.2, 14.04.3, 14.04.4, soon
to be .5, 16.04 has been released (soon to be 16.04.1) and this bug is
still there.
It is BASIC issues like these that give Linux distros a bad
name/reputation, locking
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm-gtk-greeter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
> This is a glaring red sign that neither lightdm nor upstart are the
> appropriate packages for this issue, but lightdm-gtk-greeter is.
That still doesn't explain how I'm getting the problem with unity-
greeter. There may be more than one bug at play here. Maybe my issue is
better tracked by bug
* Jonathan Sahagun [2016-01-29 12:51:08 +]:
> In this file:
> /etc/xdg/xdg-xubuntu/lightdm/
You probably mean /etc/xdg/xdg-xubuntu/lightdm/lightdm-gtk-greeter.conf
.
> In line 27, in a default installation, it reads:
> show-indicators=power;~session;~language;~a11y;~power;
>
> Remove the
Hello, here's what I did on my Xubuntu installation that seems to work:
In this file:
/etc/xdg/xdg-xubuntu/lightdm/
In line 27, in a default installation, it reads:
show-indicators=power;~session;~language;~a11y;~power;
Remove the first "power" entry, leaving only the built-in indicators:
Hi Sergio,
Yes I did mean /etc/xdg/xdg-xubuntu/lightdm/lightdm-gtk-greeter.conf ,
thanks for that.
Here's what I have for x-1-greeter.log:
(lightdm-gtk-greeter:2212): Gtk-CRITICAL **: gtk_container_foreach: assertion
'GTK_IS_CONTAINER (container)' failed
(lightdm-gtk-greeter:2212):
> Can you see if this solves the issue on your computers?
No luck here (Xubuntu 14.04), what actually did fix the issue was
installing the latest stable release of lightdm-gtk-indicator from the
upstream ppa. This caused a few hiccups with the Greybird theme, but at
least the ghost sessions are
Silly me, I had overlooked the fact that we aren't using the same
greeter. I've got [SeatDefaults]greeter-session=unity-greeter in
/etc/lightdm/lightdm.conf. So of course your solution didn't work for
me. (I need to give users a choice of desktop sessions, and found unity-
greeter to be better at
> Can you see if this solves the issue on your computers?
I am pleased to report that this workaround fixes the problem for me.
Thanks! (Xubuntu 14.04)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
For those desperate because they work for companies who take locking
screen as a serious thing, this is the workaround I came with, have been
running for a few weeks and it does the job well so far.
The script if run via cron every 10 mins will keep your system clean of
lightdm dead sessions,
unity-greeter has code to kill upstart, but for some reason this isn't
being executed. My best guess is that unity-greeter often (if not
always) dies before it exits the GTK main loop. Does it receive a second
SIGTERM, or a SIGPIPE? (When lightdm says "Stopping display server, no
sessions require
It looks like that nobody is actually issuing the indicator-services-end
upstart signal, so the stop events of *all* indicators for lightdm
sessions never get fired. The other indicators just die because the
session bus disappears under their feet, but indicator-sound-service
keeps hanging around
I'm seeing the same problem (on multiple systems), and have been looking
at the lightdm and unity-greeter log files in an attempt to understand
what is going on. Some additional observations:
* I see three processes survive the termination of the greeter session:
init (aka Upstart),
Another workaround, at least for those not requiring the a11y-indicator
(accessibility menu for visual impaired): removing the a11y-indicator
from the lightdm session, seems to prevent the start of the sound-
indicator. Hence the sound-indicator does not block the termination of
lightdm session,
This is incredibly annoying, if you leave your computer permanently on
sessions mount up each time you lock your screen, eventually sessions
pile up to the point where you notice your computer running very slowly.
This bug has been there since Xubuntu 14.04 was released.
Most people do not
To get rid of the proliferation of sessions I run this on a script:
loginctl | awk '$3~/lightdm/ {print $1}' | xargs -I{} loginctl
terminate-session {}
ps aux | awk '$0~/^[l]ightdm.*indicator-services-start/ {print $2}' | xargs
-I{} kill -9 {}
--
You received this bug notification because you
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
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
Touch seeded packages, which is subscribed to upstart in Ubuntu.
20 matches
Mail list logo
