W dniu 03.05.2017 o 17:42, Apollon Oikonomopoulos pisze:
Hi Mateusz,
On 17:12 Tue 02 May , Apollon Oikonomopoulos wrote:
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.
Would you l
Hi Mateusz,
On 17:12 Tue 02 May , Apollon Oikonomopoulos wrote:
> 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.
Would you like to update the package, or should I go ahead with
Control: tags -1 patch
Hi all,
On Sun, 30 Apr 2017 12:38:33 +0200 Lukas 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 g
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
R
Lukas' solution worked it for me as well:
echo "Type=simple" >> /lib/systemd/system/slim.service
systemctl daemon-reload
Shai
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
I have exact the same issue with the new version, I also reinstalled the
lenny *-4 version - no restarts anymore.
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 del
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
h
I wonder if it may be the fix for #860465 which is the only thing which
looks remotely fishy in the changelog.
FWIW I do not have plymouth installed on the affected system.
On Sat, 29 Apr 2017 14:12:43 +0100 ael wrote:
> 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,
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
12 matches
Mail list logo
