Thanks for answering and thanks for the advice, most of which I agree with, since I've been running sd since 2006.Since I am now 84, I'm not as good at figuring things out as I used to be, so if anyone else can offer help, I'd be grateful.
On Friday, December 8, 2023 at 03:36:19 PM EST, Andrew M.A. Cater <
amacater@einval.com> wrote:
On Fri, Dec 08, 2023 at 06:13:59PM +0000, John - wrote:
Since I last (3 December) upgraded the software (sid)Â on my old Thinkpad, my gui fails to come up. The last line of /var/log/Xorg.0.log reads:
(EE) systemd-login: failed to take device /dev/dri/card0: Message recipient disconnected from message bus without replying
I've been trying for weeks to fix it, including tracking down all suggests from googling the error message, without success. Can anyone help me figure out what the problem is?
Thanks.
Hi John,
Today is the 8th of December - strictly, that's barely a business week.
Debian expressly comes with no guarantees. You are running sid a.k.a
unstable - that comes with still fewer guarantees other than breakage
from time to time.
You are expected to be able to fix breakage in sid
yourself or you get to keep both pieces :)
You may find that the issue has been fixed if you update today: you may not. There's not much there in logs to help any of the rest of us who don't habitually run sid.
This is explicitly *not* a sarcastic suggestion: if you can't run sid,
then I would suggest you reformat your disks and install Debian stable.
Most of the people either active on this list or lurking and reading on
the sidelines run Debian stable for a reason.
If you are a Debian maintainer, you are expected to build new software in unstable for it to propagate to testing and (eventually) to the next Debian major release. Outside that, unless you are actively interested in testing
and fixing breakage as it occurs, there is little justification for running
sid as a daily operating system.
Sid is explicitly *not* a chance to run the latest, greatest bleeding edge software reliably on a sustained basis without the occasional crash or significant problems.
With every good wish, as ever,
Andy
(
amacater@debian.org)
<html><head></head><body><div class="ydpfd0e642ayahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false">Thanks for answering and thanks for the advice, most of which I agree with, since I've been running sd since 2006.</div><div dir="ltr" data-setdir="false">Since I am now 84, I'm not as good at figuring things
out as I used to be, so if anyone else can offer help, I'd be grateful.</div><div><br></div>
</div><div id="yahoo_quoted_2946972842" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, December 8, 2023 at 03:36:19 PM EST, Andrew M.A. Cater <
amacater@einval.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div>On Fri, Dec 08, 2023 at 06:13:59PM +0000, John - wrote:<div class="yqt6194356957" id="yqtfd94828"><br clear="none">> Since I last (3 December) upgraded the software (sid) on my old Thinkpad, my gui fails to come up. The last
line of /var/log/Xorg.0.log reads:<br clear="none">> (EE) systemd-login: failed to take device /dev/dri/card0: Message recipient disconnected from message bus without replying<br clear="none">> I've been trying for weeks to fix it, including
tracking down all suggests from googling the error message, without success. Can anyone help me figure out what the problem is?<br clear="none">> Thanks.</div><br clear="none">><br clear="none"><br clear="none">Hi John,<br clear="none"><br clear="
none">Today is the 8th of December - strictly, that's barely a business week.<br clear="none"><br clear="none">Debian expressly comes with no guarantees. You are running sid a.k.a<br clear="none">unstable - that comes with still fewer guarantees other
than breakage<br clear="none">from time to time.<br clear="none"><br clear="none">You are expected to be able to fix breakage in sid<br clear="none">yourself or you get to keep both pieces :) <br clear="none"><br clear="none">You may find that the issue
has been fixed if you update today: you may not.<br clear="none">There's not much there in logs to help any of the rest of us who don't <br clear="none">habitually run sid.<br clear="none"><br clear="none">This is explicitly *not* a sarcastic suggestion:
if you can't run sid,<br clear="none">then I would suggest you reformat your disks and install Debian stable.<br clear="none">Most of the people either active on this list or lurking and reading on<br clear="none">the sidelines run Debian stable for a
reason.<br clear="none"><br clear="none">If you are a Debian maintainer, you are expected to build new software in<br clear="none">unstable for it to propagate to testing and (eventually) to the next Debian<br clear="none">major release. Outside that,
unless you are actively interested in testing<br clear="none">and fixing breakage as it occurs, there is little justification for running<br clear="none">sid as a daily operating system.<br clear="none"><br clear="none">Sid is explicitly *not* a chance
to run the latest, greatest bleeding edge<br clear="none">software reliably on a sustained basis without the occasional crash or <br clear="none">significant problems.<br clear="none"><br clear="none">With every good wish, as ever,<br clear="none"><br
clear="none">Andy<br clear="none"><br clear="none">(
amacater@debian.org)<div class="yqt6194356957" id="yqtfd97890"><br clear="none"><br clear="none"></div></div>
</div>
</div></body></html>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)