Your message dated Mon, 08 May 2017 17:29:00 +0000
with message-id <1d3c25fa-0033-79a1-a5d9-e0c33c9ff...@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
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: slim
Source-Version: 1.3.6-5.1
Sebastian Rasmussen:
>>> Could you please try to upgrade to slim/1.3.6-5.1 to see if that
>>> fixes your issue?
>> Of course, no problem, but it will have to wait a day or so.
>
> I can now confirm that upgrading to 1.3.6-5.1 does indeed fix
> the issue I was experiencing. From my perspective that means
> that you may mark this bug as resolved, but you might want to
> tie it to to the 1.3.6-5.1 release some how.
With the -done + plus the above Pseudo-headers the bug will now be
closed in 1.3.6-5.1 and later.
> Thanks for being responsive and helpful! :)
>
> / Sebastian
>
You are welcome. :)
Thanks,
~Niels
--- End Message ---
