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 Latest slim upgrade caused involuntary crashes/logouts...
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: serious
When upgrading from 1.3.6-4+b2 to 1.3.6-5 of slim I noticed that my
window manager appeared to suddenly "crash" and logged me out. However
I had
not changed anything related to that but I had recently upgraded slim so I
investigated it a bit.
I compiled 1.3.6-5 without the fix for 860465 as mentioned in the -5 debian
patch (but keeping all other additions from -4+b2 to -5 the same). Without
this "fix" my desktop no longer had problems. Could this be because
I don't have plymouth installed (whatever that is)? I'm happy to do further
testing if you can provide something for me to test. Besides this minor
mishap I'm actually a happy slim user, thanks for putting in the effort. :)
/ Sebastian
--- 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 ---
