From: Z572 <zhengjunjie@iscas.ac.cn>
To: "André Batista" <nandre@riseup.net>
Cc: tumashu@163.com, ludo@gnu.org, 71154@debbugs.gnu.org
Subject: bug#71154: slim: Two regressions on v.1.4.1
Date: Sat, 25 May 2024 22:30:02 +0800 [thread overview]
Message-ID: <87o78uq80l.fsf@iscas.ac.cn> (raw)
In-Reply-To: <Zk_EhUiEeHNXfT4i@andel> ("André Batista"'s message of "Thu, 23 May 2024 19:34:45 -0300")
[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]
André Batista <nandre@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/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2024-05-25 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 22:34 bug#71154: slim: Two regressions on v.1.4.1 André Batista
2024-05-25 14:30 ` Z572 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o78uq80l.fsf@iscas.ac.cn \
--to=zhengjunjie@iscas.ac.cn \
--cc=71154@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=nandre@riseup.net \
--cc=tumashu@163.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).