Devuan bug report logs - #746
Killed when starting modale dialog like pinentry

version graph

Package: fvwm; Maintainer for fvwm is (unknown); Source for fvwm is src:fvwm.

Affects: fvwm

Reported by: Klaus Ethgen <Klaus@ethgen.de>

Date: Mon, 6 Mar 2023 17:04:01 UTC

Severity: critical

Tags: debian

Merged with 751

Fixed in version 1:2.7.0-2

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

Forwarded to https://bugs.debian.org/1034054

Full log


🔗 View this message in rfc822 format

X-Loop: owner@bugs.devuan.org
Subject: bug#746: Killed when starting modale dialog like pinentry
Reply-To: Ralph Ronnquist <ralph.ronnquist@gmail.com>, 746@bugs.devuan.org
Resent-From: Ralph Ronnquist <rrq@mail.rrq.id.au>
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: Devuan Developers <devuan-dev@lists.dyne.org>
X-Loop: owner@bugs.devuan.org
Resent-Date: Tue, 07 Mar 2023 12:34:01 +0000
Resent-Message-ID: <handler.746.B746.167819238532096@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
X-Devuan-PR-Message: followup 746
X-Devuan-PR-Package: xserver-xorg-core
X-Devuan-PR-Keywords: 
References: <ZAYcbqpjyFTyOS/f@ikki.ethgen.ch>
X-Devuan-PR-Source: xorg-server
Received: via spool by 746-submit@bugs.devuan.org id=B746.167819238532096
          (code B ref 746); Tue, 07 Mar 2023 12:34:01 +0000
Received: (at 746) by bugs.devuan.org; 7 Mar 2023 12:33:05 +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); Tue, 07 Mar 2023 12:33:05 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id 70L6H7wuB2SpbQAAmSBk0A
	(envelope-from <rrq@mail.rrq.id.au>)
	for <bugs@devuan.org>; Tue, 07 Mar 2023 12:31:56 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 6178C66F; Tue,  7 Mar 2023 12:31:56 +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=2.5 required=5.0 tests=FREEMAIL_FORGED_REPLYTO,
	SPF_PASS autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2001:19f0:5801:e4:afc4:ef12:0:2; helo=mail.rrq.id.au; envelope-from=rrq@mail.rrq.id.au; receiver=<UNKNOWN> 
Received: from mail.rrq.id.au (mail.rrq.id.au [IPv6:2001:19f0:5801:e4:afc4:ef12:0:2])
	by email.devuan.org (Postfix) with ESMTPS id D8316393
	for <746@bugs.devuan.org>; Tue,  7 Mar 2023 12:31:49 +0000 (UTC)
Received: from localhost (194-193-171-157.tpgi.com.au [194.193.171.157])
	by mail.rrq.id.au (Postfix) with ESMTPSA id 4074B9FE42
	for <746@bugs.devuan.org>; Tue,  7 Mar 2023 23:31:43 +1100 (AEDT)
Date: Tue, 7 Mar 2023 23:31:41 +1100
From: Ralph Ronnquist <rrq@mail.rrq.id.au>
To: 746@bugs.devuan.org
Message-ID: <ZAcurbj0anoyXVVQ@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
I studied the Xorg logs and had the following thoughts

both Xorg logs shows grief when a new monitor is connected

nvidia at about 1312258.437 and amd at about 117563.217

nvidia "survives" a long time (20h?), but with repeated hickups

amd doesn't show extended use but rather X goes down within 20 sec

I'm not sure how gpu memory is used or computed but I suppose one
possibility is that it's not enough for the 3840x2400 side monitor
(plus the 1920x1200 LCD)

possibly amd says it has 1Gb memory; nvidia appears to reserve 6GB

----

All that might suggest some underlying hardware issue(s) but evenso it
appears X terminates peacefully without any log line explaining why.

Perhaps a deeper code review is needed to trace what happens when a
functioning GPU "suddenly disappears".

Ralph.

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 Nov 24 05:00:48 2024;