Home | Devuan | Git | Forum | Packages | Popcon
Donate now!
Download

Devuan bug report logs - #740
xserver-xorg-core: keyboard/mouse lockup after switching VC1/2/3

version graph

Package: xserver-xorg-core; Maintainer for xserver-xorg-core is Devuan Developers <devuan-dev@lists.dyne.org>; Source for xserver-xorg-core is src:xorg-server.

Reported by: "wirelessduck+debian@gmail.com" <wirelessduck+debian@gmail.com>

Date: Thu, 2 Feb 2023 01:18:02 UTC

Severity: normal

Found in version 2:21.1.6-1devuan1

Done: Mark Hindley <mark@hindley.org.uk>

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.devuan.org
Subject: bug#740: [devuan-dev] bug#740: xserver-xorg-core: keyboard/mouse lockup after switching VC1/2/3
Reply-To: wirelessduck@gmail.com, 740@bugs.devuan.org
Resent-From: wirelessduck@gmail.com
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: Devuan Developers <devuan-dev@lists.dyne.org>
X-Loop: owner@bugs.devuan.org
Resent-Date: Wed, 22 Feb 2023 11:44:01 +0000
Resent-Message-ID: <handler.740.B740.16770662206549@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
X-Devuan-PR-Message: followup 740
X-Devuan-PR-Package: xserver-xorg-core
X-Devuan-PR-Keywords: 
References: <Y9wzp6/16eKrRjle@localhost> <167530050618.23854.8792077410759034231.reportbug@tom-pc-devuan>
X-Devuan-PR-Source: xorg-server
Received: via spool by 740-submit@bugs.devuan.org id=B740.16770662206549
          (code B ref 740); Wed, 22 Feb 2023 11:44:01 +0000
Received: (at 740) by bugs.devuan.org; 22 Feb 2023 11:43:40 +0000
Delivered-To: bugs@devuan.org
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 22 Feb 2023 11:43:40 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id c0FCKaj/9WPvawAAmSBk0A
	(envelope-from <wirelessduck@gmail.com>)
	for <bugs@devuan.org>; Wed, 22 Feb 2023 11:42:32 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 9F5D9B9C; Wed, 22 Feb 2023 11:42:32 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,FREEMAIL_REPLY,RCVD_IN_DNSWL_NONE,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::534; helo=mail-pg1-x534.google.com; envelope-from=wirelessduck@gmail.com; receiver=<UNKNOWN> 
Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534])
	by email.devuan.org (Postfix) with ESMTPS id 0E2CE32
	for <740@bugs.devuan.org>; Wed, 22 Feb 2023 11:42:27 +0000 (UTC)
Received: by mail-pg1-x534.google.com with SMTP id p5so3986388pgh.11
        for <740@bugs.devuan.org>; Wed, 22 Feb 2023 03:42:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20210112;
        h=to:in-reply-to:references:message-id:date:subject:mime-version:from
         :content-transfer-encoding:from:to:cc:subject:date:message-id
         :reply-to;
        bh=VS0xrDHu4gNFpVg4oopsypoemNptItTvN3Tqu6Dr0Aw=;
        b=IulHyoGabrngaedTQ3E3TU8kG8ZhNq5oXoLv7fNAJs4FNuNReJEBLk9oY7URfbma8a
         vMFwpYd4TKc3OpB16o3ilNb45ytwT+1L/Gg3xrapGKcp1vS2CdFi9jxAQZBtUPLTcT8m
         hJOCdIWOidMZI5N33tY7l3WCjYUUx+GrXN4T3cH+qF7yU0krG0twykZbIN3jpNhebr79
         TXUNzvLx69Skc9Mus+YiEtF9CXJ5O3OWePOHFfx02x7OyThkiT9TvOYWikOeHQ6sjzSn
         kL2vFuhTQBqZ8KN63DwxGDe3sCexOJUCleyvO5oeQKUrujHVdjXbvTTqByNhbDJt7dRE
         sYSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112;
        h=to:in-reply-to:references:message-id:date:subject:mime-version:from
         :content-transfer-encoding:x-gm-message-state:from:to:cc:subject
         :date:message-id:reply-to;
        bh=VS0xrDHu4gNFpVg4oopsypoemNptItTvN3Tqu6Dr0Aw=;
        b=hvQWpEPSjmtF6oreJFD4uPVZClrVaP4f7WGGf4YLBOSznk7vrhFHmzSQKdPaQwROXb
         DnMfyK0HR2uVhFdbWX81RRlMhUVXHLMZO5Ei34lIXVqLSe4npgkHEmBaH/wSOYAA9xn4
         FzzDDNXiFEhQV5sgI4w2cc2T3j26SxoWTDGBpMPR3BIViCOZV8iuUEvJBcwpZBRvUGcN
         o2i4iA4Vl8+HBrJ/5CHKsf6EUKV902ry954sTvGs6EZMEJ5oDHKXBhssLwprHfrOdZ9p
         zOuXKuRI1GJPoBAEtdT80KBS0/0P6CGg6Uo9Je9XMt+DOc8Byxv10N1AFZBPGc1l+U3C
         ZnoA==
X-Gm-Message-State: AO0yUKW7ancCfM0VF9yooJQEBwoKfMGC5285PxJaGQbGRdbpQ2/09asx
	kUbkw54QP024dffk4b1Ek2WhNjE803w=
X-Google-Smtp-Source: AK7set8J5zlEcsoWBqT73yc/Peo+yVAkyPCErkfIP9rM5mnfeDfqfVoTwiycH2zaIy8wNIq82gLPnw==
X-Received: by 2002:aa7:961a:0:b0:5a8:ae9e:de20 with SMTP id q26-20020aa7961a000000b005a8ae9ede20mr6220357pfg.30.1677066144558;
        Wed, 22 Feb 2023 03:42:24 -0800 (PST)
Received: from smtpclient.apple (2403-5807-c808-0-2c7c-1720-2c3d-c0ee.ip6.aussiebb.net. [2403:5807:c808:0:2c7c:1720:2c3d:c0ee])
        by smtp.gmail.com with ESMTPSA id m20-20020aa79014000000b00593c1c5bd0esm4513859pfo.164.2023.02.22.03.42.23
        for <740@bugs.devuan.org>
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Wed, 22 Feb 2023 03:42:23 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: wirelessduck@gmail.com
Mime-Version: 1.0 (1.0)
Date: Wed, 22 Feb 2023 22:42:11 +1100
Message-Id: <51B7F5CA-E134-47BE-A951-6D1B2F0E01EB@gmail.com>
In-Reply-To: <Y9wzp6/16eKrRjle@localhost>
To: 740@bugs.devuan.org
X-Mailer: iPhone Mail (20D67)


> On 3 Feb 2023, at 09:08, Ralph Ronnquist <rrq@mail.rrq.id.au> wrote:
> 
> On Thu, 02 Feb 2023 12:15:06 +1100 "wirelessduck+debian@gmail.com" <wirelessduck+debian@gmail.com> wrote:
>> Package: xserver-xorg-core
>> Version: 2:21.1.6-1devuan1
>> Severity: normal
>> 
>> Dear Maintainer,
>> 
>> *** Reporter, please consider answering these questions, where appropriate ***
>> 
>>   * What led up to the situation?
>> Install newer version of xserver-xorg-core to test libseat1 elogind support without seatd
>> ...
>>   * What exactly did you do (or not do) that was effective (or
>>     ineffective)?
>> 
>> Login to VC1 as root.
>> Install libseat1 and newer versions of xserver-xorg-core and xserver-common.
>> Logout and login to VC1 as normal user.
>> Run startx to start openbox on VC1.
>> 
>> Switch to VC2 (ctrl+alt+f2) and login again as normal user.
>> Run startx to start openbox on VC2.
>> 
>> Switch to VC3 (ctrl+alt+f3) and login again as normal user.
>> Run startx to start openbox on VC3.
>> 
>> Switch back to VC1 (ctrl+alt+f1).
>> Mouse and keyboard are now unresponsive.  After unplug/replug mouse and keyboard they become responsive again.
>> 
>> Continue switching between VC1/2/3.  The mouse/keyboard will become unresponsive each time until the usb plugs are unplug/replug again.
> 
> At this time, there should have been separate Xorg log files by the
> user(s) that started X. Ideally it should be different non-root users
> in each VC, and then each of them would gain a log file; probably
> saved in their respective ~/.local/share/xorg/ directory. It's thus
> good to clean out those directories before the test session, or at
> least clean out each before running startx.
> 
> Further, the non-root users should not be in groups tty or input, but
> need to be in group video.
> 
> And, it would be really useful with a snap of the Xorg log for the VC
> in focus exactly when the problem is discovered, and before remedy
> actions have been taken.
> 
> To be able do that, you might need a separate machine with an ssh (or
> otherwise remote) login to the test machine, and then snapshot that
> log file via that remote login before changing VC or unplug/plug
> devices on that problem machine.
> 
> Or otherwise, make sure that the user actions are well separated in
> the log, eg by waiting some 5 minutes between user actions. Such time
> gaps in the log are good as "markers" between the various user
> actions.
> 
>> 
>> I then downgraded both xorg packages back to daedalus version and confirmed the issue did not occur under daedalus package versions.
>> 
> 
> That was good :)
> 
>> I then re-installed the newer testing versions of both xorg packages and repeated the testing but was unable to reproduce the problem.
> 
> Hmm. That is very confusing! It almost sounds like something ended up
> differently in the device handling packages with the downgrad + upgrade.
> 
> It would however be really good if you could re-confirm the test
> scenario with 3 different VC and non-root users (not in groups tty or
> input) each running startx, and then shifting successfully between the
> VC,
> 
>> Hopefully something in the xorg log file might provide some clue to what happened.
> 
> Though, isn't that log file from the latest session, when things
> worked?
> 
> Also, it looks like X was started by root in all cases?
> 
>> ...

Thanks for the pointers. I’ll get back onto testing this again as soon as the dreaded covid and associated brain fog has passed through my system. I didn’t realise there were xorg log files in home directory so anything I provided would have been from /var/log. I will setup multiple user accounts for the next test.

Send a report that this bug log contains spam.

Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Devuan Bugs Owner <owner@bugs.devuan.org>.
Last modified: Sun May 18 13:47:00 2025;