slim: Two regressions on v.1.4.1

  • Open
  • quality assurance status badge
Details
2 participants
  • André Batista
  • Z572
Owner
unassigned
Submitted by
André Batista
Severity
normal
A
A
André Batista wrote on 24 May 00:34 +0200
(address . bug-guix@gnu.org)
Zk_EhUiEeHNXfT4i@andel
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.

Z
Z
Z572 wrote on 25 May 16:30 +0200
(name . André Batista)(address . nandre@riseup.net)
87o78uq80l.fsf@iscas.ac.cn
André Batista <nandre@riseup.net> writes:

Toggle quote (15 lines)
> 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?

Toggle quote (7 lines)
>
> 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?.

Toggle quote (10 lines)
>
> '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?

Toggle quote (4 lines)
>
> For now I have reverted the upgrade to its current upstream version.
>
> 1. https://sourceforge.net/projects/slim-fork/files/
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEfr6klGDOXiwIdX/bO1qpk+Gi3/AFAmZR9eoACgkQO1qpk+Gi
3/ChGQ//UFn3uzWhsK7vFhv02xL+Ms7lzFf2ha5qqekhCfIzqcDMUX9hRtpT90zL
RPwKb9LyqC5TcJkhct00Pu7iT1DTa/XQHMuX+vazL1iqJVVKLcg2cGaqEfa8r25t
mUZO5U6RZGjnUhOTs0s78CIvYYVWrKBmFy7TCtbM2ZPWateOB4O1vBf2fjyMN203
9HFikvKeoviHSp4URTKLQIXLQbNWB85YNOHNk2b3MilTcYfDZLmGllyGkeikPICU
QWm+el0GFYodn27amb8kdYsq3JamR9h/alHXxkPkSU7Gzm82XxXrAvDMeYATSdyG
U/mhXeZ0CkuXDI8R7t0HT73jRKXOL47wVfh4cZEbOq8qeEUx2GBbv3ryA4m9cX7q
mh1DSY5FgInPms5+b22tfKe4mBbHs5pxLGUedepXI6wBdC4EAGdxLbyslOpM80VS
jkGmvZPmsEszWRXiug99B26CmlcGTVneEzjIhJiK7zBluxjmzpikontrLN5SIHRW
qOtRnyzUIpIY7Pq0jzE8OPI3e/h8lSotoWsJWLSoFR+/gwQ5nwaiZa7uYxD8+07Y
198HQpAnfqqU21stKfMCBJ19bdP6QPYsbnNuDeJFfdGU739fOR/Hkliz/HJNE9qe
15aEHBCynW7CGrCS+w4QSHpmv+kEQf20zlLPukhhWHMplHRn9Qo=
=7cLK
-----END PGP SIGNATURE-----

?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 71154@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 71154
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch