GNU bug report logs - #71154
slim: Two regressions on v.1.4.1

Previous Next

Package: guix;

Reported by: André Batista <nandre <at> riseup.net>

Date: Thu, 23 May 2024 22:36:02 UTC

Severity: normal

To reply to this bug, email your comments to 71154 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#71154; Package guix. (Thu, 23 May 2024 22:36:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to André Batista <nandre <at> riseup.net>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Thu, 23 May 2024 22:36:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: André Batista <nandre <at> riseup.net>
To: bug-guix <at> gnu.org
Cc: tumashu <at> 163.com, zhengjunjie <at> iscas.ac.cn
Subject: slim: Two regressions on v.1.4.1
Date: Thu, 23 May 2024 19:34:45 -0300
Hi Guix,

I've found two regressions after upgrading to v. 1.4.1 of slim.

The first one is that it is no longer possible to use a secondary monitor
with it. If it is connected at the same time as a the primary one, only
the later gets to show the slim greater. If the primary one is disabled
via kernel command line (eg. "video=LVDS-1:d"), slim does not start and
the xorg-server crashes. Shepherd keeps trying to restart it to no avail.

Curiously enough the changelog for the current version mentions that
there has been some change to "how/when the pseudo-root window is created
and removed, in preparation for handling multiple monitors"[*]. I, for one,
have been using multiple monitors without issue until now.

The second regression is more subtle and annoying. After logging in with
one account, sometimes, in what appears to be related to have used any
gtk application, the user session is not properly terminated on logout
and herd looses track of xorg-server. If one tries to stop it with herd,
the session remais alive and there is only one bit on slim.log:

'WaitForServer: Not seen SigUSR1 from Xserver'

and nothing useful on Xorg.log.

Only by manually killing the xorg process, I've been able to get back
to a sane state again.

Any thoughts?

For now I have reverted the upgrade to its current upstream version.

1. https://sourceforge.net/projects/slim-fork/files/




Information forwarded to bug-guix <at> gnu.org:
bug#71154; Package guix. (Sat, 25 May 2024 14:31:02 GMT) Full text and rfc822 format available.

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Z572 <zhengjunjie <at> iscas.ac.cn>
To: André Batista <nandre <at> riseup.net>
Cc: tumashu <at> 163.com, ludo <at> gnu.org, bug-guix <at> gnu.org
Subject: Re: slim: Two regressions on v.1.4.1
Date: Sat, 25 May 2024 22:30:02 +0800
[Message part 1 (text/plain, inline)]
André Batista <nandre <at> riseup.net> writes:

> Hi Guix,
>
> I've found two regressions after upgrading to v. 1.4.1 of slim.
>
> The first one is that it is no longer possible to use a secondary monitor
> with it. If it is connected at the same time as a the primary one, only
> the later gets to show the slim greater. If the primary one is disabled
> via kernel command line (eg. "video=LVDS-1:d"), slim does not start and
> the xorg-server crashes. Shepherd keeps trying to restart it to no avail.
>
> Curiously enough the changelog for the current version mentions that
> there has been some change to "how/when the pseudo-root window is created
> and removed, in preparation for handling multiple monitors"[*]. I, for one,
> have been using multiple monitors without issue until now.

maybe you can report it to upstream?

>
> The second regression is more subtle and annoying. After logging in with
> one account, sometimes, in what appears to be related to have used any
> gtk application, the user session is not properly terminated on logout
> and herd looses track of xorg-server. If one tries to stop it with herd,
> the session remais alive and there is only one bit on slim.log:

I'm not exactly familiar with shepherd, maybe replacing
fork+exec-command with make-forkexec-constructor would solve this
problem?.

>
> 'WaitForServer: Not seen SigUSR1 from Xserver'
>
> and nothing useful on Xorg.log.
>
> Only by manually killing the xorg process, I've been able to get back
> to a sane state again.
>
> Any thoughts?

We can revert this commit or add a slim-1.4.0 package?

>
> For now I have reverted the upgrade to its current upstream version.
>
> 1. https://sourceforge.net/projects/slim-fork/files/
[signature.asc (application/pgp-signature, inline)]

This bug report was last modified 105 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.