Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#861474: slim: Session restarts in a loop renedering whole system useless.
9 views
Skip to first unread message
ael
Apr 29, 2017, 9:20:02 AM4/29/17
to
Package: slim
Version: 1.3.6-5
Severity: critical
Justification: breaks the whole system
I am not sure that this is a slim problem, but as the system is almost
unusable, I cannot investigate.
After an apt-get upgrade earlier today, the system presents a new slim
login page. Logging in works, but then the whole system restarts X
(presumably) and the sylim login prompt appear again. This ahhpens in
what seems to be an infinite loop, roughly every minute or so.
I am only able to compose this message outside X using a pseudo
terminal. The restarts interrupt the terminal and represents the slim
login page. Fortunately the terminal context is retained so I can switch
back to the terminal.
I have not yet tried removing slim which I hope I may be able to do
despite the constant restarts.
I suspect slim because it seems to be the only likely candidate in the
set of upgrades earlier today, and it is the slim login screen which
keeps looping.
Presumably others will report this problem as well.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages slim depends on:
ii dbus 1.10.18-1
ii debconf [debconf-2.0] 1.5.60
ii libc6 2.24-10
ii libfontconfig1 2.11.0-6.7+b1
ii libfreetype6 2.6.3-3.1
ii libgcc1 1:6.3.0-14
ii libjpeg62-turbo 1:1.5.1-2
ii libpam0g 1.1.8-3.5
ii libpng16-16 1.6.28-1
ii libstdc++6 6.3.0-14
ii libx11-6 2:1.6.4-3
ii libxext6 2:1.3.3-1+b2
ii libxft2 2.3.2-1+b2
ii libxmu6 2:1.1.2-2
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii lsb-base 9.20161125
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages slim recommends:
ii xterm 327-2
Versions of packages slim suggests:
pn scrot <none>
ii xauth 1:1.0.9-1+b2
-- debconf information:
* shared/default-x-display-manager: slim
slim/daemon_name: /usr/bin/slim
Version: 1.3.6-5
Severity: critical
Justification: breaks the whole system
I am not sure that this is a slim problem, but as the system is almost
unusable, I cannot investigate.
After an apt-get upgrade earlier today, the system presents a new slim
login page. Logging in works, but then the whole system restarts X
(presumably) and the sylim login prompt appear again. This ahhpens in
what seems to be an infinite loop, roughly every minute or so.
I am only able to compose this message outside X using a pseudo
terminal. The restarts interrupt the terminal and represents the slim
login page. Fortunately the terminal context is retained so I can switch
back to the terminal.
I have not yet tried removing slim which I hope I may be able to do
despite the constant restarts.
I suspect slim because it seems to be the only likely candidate in the
set of upgrades earlier today, and it is the slim login screen which
keeps looping.
Presumably others will report this problem as well.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages slim depends on:
ii dbus 1.10.18-1
ii debconf [debconf-2.0] 1.5.60
ii libc6 2.24-10
ii libfontconfig1 2.11.0-6.7+b1
ii libfreetype6 2.6.3-3.1
ii libgcc1 1:6.3.0-14
ii libjpeg62-turbo 1:1.5.1-2
ii libpam0g 1.1.8-3.5
ii libpng16-16 1.6.28-1
ii libstdc++6 6.3.0-14
ii libx11-6 2:1.6.4-3
ii libxext6 2:1.3.3-1+b2
ii libxft2 2.3.2-1+b2
ii libxmu6 2:1.1.2-2
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii lsb-base 9.20161125
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages slim recommends:
ii xterm 327-2
Versions of packages slim suggests:
pn scrot <none>
ii xauth 1:1.0.9-1+b2
-- debconf information:
* shared/default-x-display-manager: slim
slim/daemon_name: /usr/bin/slim
Konstantin Khomoutov
Apr 29, 2017, 10:00:02 AM4/29/17
to
Happens to me as well after the last `apt update && apt upgrade` of my
Stretch (amd64) system.
I've tracked it down to be an issue with Slim as switching to an
alternate login manager (tried xdm and lxdm) fixes the problem.
In the log file, Slim appears to write something about the X server not
having been connected in a timely manner.
Since the session reset happens in some 10-15 seconds, I'd say Slim has
some logic to check whether the X server has become available and if it
hasn't Slim retries. Looks like after some late change in either Slim
or X.org, this check now fails.
If needed, I could try debugging this further or provide futher info
(unfortunately, I have no slim.log from the affected machine at hand
currently).
Stretch (amd64) system.
I've tracked it down to be an issue with Slim as switching to an
alternate login manager (tried xdm and lxdm) fixes the problem.
In the log file, Slim appears to write something about the X server not
having been connected in a timely manner.
Since the session reset happens in some 10-15 seconds, I'd say Slim has
some logic to check whether the X server has become available and if it
hasn't Slim retries. Looks like after some late change in either Slim
or X.org, this check now fails.
If needed, I could try debugging this further or provide futher info
(unfortunately, I have no slim.log from the affected machine at hand
currently).
Konstantin Khomoutov
Apr 29, 2017, 10:00:02 AM4/29/17
to
Aleksandr Konkov
Apr 29, 2017, 11:00:02 AM4/29/17
to
Package: slim
Version: 1.3.6-5
Followup-For: Bug #861474
SLIM worked well before update to 1.3.6-5.
Maybe it's a problem with systemd slim.service
~$ journalctl -x -u slim
apr 29 13:40:00 dell-1520 slim[476]: pam_unix(slim:session): session
opened for user konkovaa by (uid=0)
apr 29 13:41:06 dell-1520 systemd[1]: slim.service: Start operation
timed out. Terminating.
apr 29 13:41:09 dell-1520 systemd[1]: slim.service: Main process exited,
code=exited, status=1/FAILURE
apr 29 13:41:09 dell-1520 systemd[1]: Failed to start SLiM Simple Login
Manager.
-- Subject: Unit slim.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit slim.service has failed.
--
-- The result is failed.
apr 29 13:41:09 dell-1520 systemd[1]: slim.service: Unit entered failed
state.
apr 29 13:41:09 dell-1520 systemd[1]: slim.service: Triggering
OnFailure= dependencies.
apr 29 13:41:09 dell-1520 systemd[1]: slim.service: Failed to enqueue
OnFailure= job: No such file or directory
apr 29 13:41:09 dell-1520 systemd[1]: slim.service: Failed with result
'timeout'.
apr 29 13:41:09 dell-1520 systemd[1]: slim.service: Service hold-off
time over, scheduling restart.
apr 29 13:41:09 dell-1520 systemd[1]: Stopped SLiM Simple Login Manager.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
* shared/default-x-display-manager: slim
Version: 1.3.6-5
Followup-For: Bug #861474
SLIM worked well before update to 1.3.6-5.
Maybe it's a problem with systemd slim.service
~$ journalctl -x -u slim
apr 29 13:40:00 dell-1520 slim[476]: pam_unix(slim:session): session
opened for user konkovaa by (uid=0)
apr 29 13:41:06 dell-1520 systemd[1]: slim.service: Start operation
timed out. Terminating.
apr 29 13:41:09 dell-1520 systemd[1]: slim.service: Main process exited,
code=exited, status=1/FAILURE
apr 29 13:41:09 dell-1520 systemd[1]: Failed to start SLiM Simple Login
Manager.
-- Subject: Unit slim.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit slim.service has failed.
--
-- The result is failed.
apr 29 13:41:09 dell-1520 systemd[1]: slim.service: Unit entered failed
state.
apr 29 13:41:09 dell-1520 systemd[1]: slim.service: Triggering
OnFailure= dependencies.
apr 29 13:41:09 dell-1520 systemd[1]: slim.service: Failed to enqueue
OnFailure= job: No such file or directory
apr 29 13:41:09 dell-1520 systemd[1]: slim.service: Failed with result
'timeout'.
apr 29 13:41:09 dell-1520 systemd[1]: slim.service: Service hold-off
time over, scheduling restart.
apr 29 13:41:09 dell-1520 systemd[1]: Stopped SLiM Simple Login Manager.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Locale: LANG=en_US.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages slim depends on:
ii dbus 1.10.18-1
ii debconf [debconf-2.0] 1.5.60
ii libc6 2.24-10
ii libfontconfig1 2.11.0-6.7+b1
ii libfreetype6 2.6.3-3.1
ii libgcc1 1:6.3.0-14
ii libjpeg62-turbo 1:1.5.1-2
ii libpam0g 1.1.8-3.5
ii libpng16-16 1.6.28-1
ii libstdc++6 6.3.0-14
ii libx11-6 2:1.6.4-3
ii libxext6 2:1.3.3-1+b2
ii libxft2 2.3.2-1+b2
ii libxmu6 2:1.1.2-2
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii lsb-base 9.20161125
ii zlib1g 1:1.2.8.dfsg-5
Init: systemd (via /run/systemd/system)
Versions of packages slim depends on:
ii dbus 1.10.18-1
ii debconf [debconf-2.0] 1.5.60
ii libc6 2.24-10
ii libfontconfig1 2.11.0-6.7+b1
ii libfreetype6 2.6.3-3.1
ii libgcc1 1:6.3.0-14
ii libjpeg62-turbo 1:1.5.1-2
ii libpam0g 1.1.8-3.5
ii libpng16-16 1.6.28-1
ii libstdc++6 6.3.0-14
ii libx11-6 2:1.6.4-3
ii libxext6 2:1.3.3-1+b2
ii libxft2 2.3.2-1+b2
ii libxmu6 2:1.1.2-2
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii lsb-base 9.20161125
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages slim recommends:
ii xterm 327-2
Versions of packages slim suggests:
pn scrot <none>
ii xauth 1:1.0.9-1+b2
-- debconf information:
slim/daemon_name: /usr/bin/slim
ii xterm 327-2
Versions of packages slim suggests:
pn scrot <none>
ii xauth 1:1.0.9-1+b2
-- debconf information:
* shared/default-x-display-manager: slim
Ruwen Schwedewsky
May 2, 2017, 9:40:02 AM5/2/17
to
Same problem here on debian testing with 1.3.6-5. My current workaround:
- Open a root shell (via ctrl+alt+f1)
- Stop slim via: /etc/init.d/slim stop (it is stopped via systemctl)
- Start slim by simply entering slim
I would guess it has something to do with the systemd startup scripts.
Cheers
Ruwen
- Open a root shell (via ctrl+alt+f1)
- Stop slim via: /etc/init.d/slim stop (it is stopped via systemctl)
- Start slim by simply entering slim
I would guess it has something to do with the systemd startup scripts.
Cheers
Ruwen
Apollon Oikonomopoulos
May 2, 2017, 10:20:02 AM5/2/17
to
Control: tags -1 patch
Hi all,
On Sun, 30 Apr 2017 12:38:33 +0200 Lukas <h...@zwergenfeste.ch> wrote:
> Hi
>
> Got the same problem on stretch.
>
> Changing the systemd service type to simple solves the problem for me:
>
> echo "Type=simple" >> /lib/systemd/system/slim.service
> systemctl daemon-reload
>
> So, i guess the dbus name can't be acquired...
>
> BR
>
> Lukas
So, to recap, this is due to the fix for #860465, which is part of
1.3.6-5. It appears that in order to fix plymouth handling, the service
file was modified to include a number of things slim currently does
*not* support:
- BusName=org.freedesktop.DisplayManager which was added to the unit
file silently converts the unit to Type=dbus and instructs systemd to
expect slim to bind the org.freedesktop.DisplayManager endpoint on
the system bus before it marks the service as running. However,
grepping the source indicates that slim is completely unaware of
dbus. Thus this directive causes systemd to endlessly restart slim
every TimeoutStartSec seconds.
- Moreover, slim seems to not be able to stop plymouth by itself,
contrary to what is stated in the service file. This is also
reflected by the manual handling of plymouth in the upstart and
initscript files.
The attached debdiff resolves the restart loop, while ensuring that slim
plays nice with plymouth. If nobody responds, I intend to NMU the
package tomorrow.
Regards,
Apollon
Hi all,
On Sun, 30 Apr 2017 12:38:33 +0200 Lukas <h...@zwergenfeste.ch> wrote:
> Hi
>
> Got the same problem on stretch.
>
> Changing the systemd service type to simple solves the problem for me:
>
> echo "Type=simple" >> /lib/systemd/system/slim.service
> systemctl daemon-reload
>
> So, i guess the dbus name can't be acquired...
>
> BR
>
> Lukas
So, to recap, this is due to the fix for #860465, which is part of
1.3.6-5. It appears that in order to fix plymouth handling, the service
file was modified to include a number of things slim currently does
*not* support:
- BusName=org.freedesktop.DisplayManager which was added to the unit
file silently converts the unit to Type=dbus and instructs systemd to
expect slim to bind the org.freedesktop.DisplayManager endpoint on
the system bus before it marks the service as running. However,
grepping the source indicates that slim is completely unaware of
dbus. Thus this directive causes systemd to endlessly restart slim
every TimeoutStartSec seconds.
- Moreover, slim seems to not be able to stop plymouth by itself,
contrary to what is stated in the service file. This is also
reflected by the manual handling of plymouth in the upstart and
initscript files.
The attached debdiff resolves the restart loop, while ensuring that slim
plays nice with plymouth. If nobody responds, I intend to NMU the
package tomorrow.
Regards,
Apollon
Debian Bug Tracking System
May 2, 2017, 10:20:03 AM5/2/17
to
Processing control commands:
> tags -1 patch
Bug #861474 [slim] slim: Session restarts in a loop rendering the whole system useless
Added tag(s) patch.
--
861474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
> tags -1 patch
Bug #861474 [slim] slim: Session restarts in a loop rendering the whole system useless
Added tag(s) patch.
--
861474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Debian Bug Tracking System
May 4, 2017, 3:40:02 AM5/4/17
to
Your message dated Thu, 04 May 2017 07:34:05 +0000
with message-id <E1d6BH3-...@fasolo.debian.org>
and subject line Bug#861474: fixed in slim 1.3.6-5.1
has caused the Debian Bug report #861474,
regarding slim: Session restarts in a loop rendering the whole system useless
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
with message-id <E1d6BH3-...@fasolo.debian.org>
and subject line Bug#861474: fixed in slim 1.3.6-5.1
has caused the Debian Bug report #861474,
regarding slim: Session restarts in a loop rendering the whole system useless
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
Debian Bug Tracking System
May 8, 2017, 1:40:03 PM5/8/17
to
Your message dated Mon, 08 May 2017 17:29:00 +0000
with message-id <1d3c25fa-0033-79a1...@thykier.net>
and subject line Re: Latest slim upgrade caused involuntary crashes/logouts...
has caused the Debian Bug report #862052,
with message-id <1d3c25fa-0033-79a1...@thykier.net>
and subject line Re: Latest slim upgrade caused involuntary crashes/logouts...
has caused the Debian Bug report #862052,
regarding slim: Session restarts in a loop rendering the whole system useless
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
862052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862052
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
0 new messages