The problem seems to be not with X-windows but with arts; the work-around
described in the upstream bug reports works nicely around the problem.
On Sun, 19 Sep 2004, Riku Voipio wrote:
>
> This is probably an X or kernel bug, right? even if kdm included buggy
> code, the x server should not kill the machine for it.
You are formally right, of course, but that is not very interesting as
long as we can't point out the place where X or kernel fails us. Or
artsd, which right now seems to be the case.
> Peder Wrote:
> > To get a stable (!) "unstable" system with KDE 3.3, no freezing
> > problem at logout and no problems with "tcsh" I instead implement the
> > solution to the "tcsh" problem described in bug 266814.
>
> You mean, that by fixing the Xsession, kde no longer crashes on logout?
Yeah, I was pretty surprised myself. But you know how it is - a bug of
this kind, occurring along the interface between two complex systems, can
come and go for the most obscure reasons. The Xsession fix probably
changed some timing; it certainly didn't fix the bug directly.
> Xsession is known to be broken in unstable at the moment, and it can
> be fixed either by replacing /etc/kde3/kdm/Xsession with
> --snip--
> #!/bin/sh
>
> . /etc/X11/Xsession
> --snip--
> Or with patch in
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D265865&msg=3D22
That is not what I wrote: to get the work-around effect I had to use the
fix to the Xsession bug described in 266814.
-----
Be that is it may, I must correct my posting as of August 25: fixing
the Xsession bug did not entirely work around the crashing bug. The bug
is still there, only now it only happens when I log out and shut down in
one operation (KDE Menu/Logout/Turn of computer). If I do it in two
operations (KDE Menu/Logout/End current Session, the shutdown system from
KDM "Menu" buttom, the system does not crash.
But: if I use the fix described in the upstream bug reports (Control
Center/Sound & Multimedia/Sound System/disable "run with highest possible
priority"), the crashing bug disappears for good.
Riku, you ask for more information. I am willing to help, bug I am no
expert in KDE/artsd interaction. If you can suggest specific things to d=
o
that can provide you with useful information, I am more than willing to d=
o
it. After all, the bug is quite simple to reproduce on several of
my systems - I just have the re-enable "run with highest possible
priority".
best regards
--
Peder Chr. N=F8rgaard Senior System Developer, M. Sc.
Ericsson Telebit A/S tel: +45 30 91 84 31
Skanderborgvej 232 fax: +45 89 38 51 01
DK-8260 Viby J, Denmark
e-mail: <email address hidden>
(old e-mail 2000-2003: <email address hidden>)
(old e-mail 1992-2000: <email address hidden>)
Message-ID: <email address hidden> 1?Q?Peder_ Chr=2E_ N=F8rgaard? = <email address hidden>
Date: Mon, 20 Sep 2004 08:51:53 +0200 (CEST)
From: =?ISO-8859-
To: <email address hidden>
cc: Riku Voipio <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: kde: kde crashes X when quitting
Important information: this bug is known upstream! See
http:// bugs.kde. org/show_ bug.cgi? id=3D88401 bugs.kde. org/show_ bug.cgi? id=3D86426
http://
The problem seems to be not with X-windows but with arts; the work-around
described in the upstream bug reports works nicely around the problem.
On Sun, 19 Sep 2004, Riku Voipio wrote:
>
> This is probably an X or kernel bug, right? even if kdm included buggy
> code, the x server should not kill the machine for it.
You are formally right, of course, but that is not very interesting as
long as we can't point out the place where X or kernel fails us. Or
artsd, which right now seems to be the case.
> Peder Wrote:
> > To get a stable (!) "unstable" system with KDE 3.3, no freezing
> > problem at logout and no problems with "tcsh" I instead implement the
> > solution to the "tcsh" problem described in bug 266814.
>
> You mean, that by fixing the Xsession, kde no longer crashes on logout?
Yeah, I was pretty surprised myself. But you know how it is - a bug of
this kind, occurring along the interface between two complex systems, can
come and go for the most obscure reasons. The Xsession fix probably
changed some timing; it certainly didn't fix the bug directly.
> Xsession is known to be broken in unstable at the moment, and it can kdm/Xsession with bugs.debian. org/cgi- bin/bugreport. cgi?bug= 3D265865& msg=3D22
> be fixed either by replacing /etc/kde3/
> --snip--
> #!/bin/sh
>
> . /etc/X11/Xsession
> --snip--
> Or with patch in
>
> http://
That is not what I wrote: to get the work-around effect I had to use the
fix to the Xsession bug described in 266814.
-----
Be that is it may, I must correct my posting as of August 25: fixing
the Xsession bug did not entirely work around the crashing bug. The bug
is still there, only now it only happens when I log out and shut down in
one operation (KDE Menu/Logout/Turn of computer). If I do it in two
operations (KDE Menu/Logout/End current Session, the shutdown system from
KDM "Menu" buttom, the system does not crash.
But: if I use the fix described in the upstream bug reports (Control
Center/Sound & Multimedia/Sound System/disable "run with highest possible
priority"), the crashing bug disappears for good.
Riku, you ask for more information. I am willing to help, bug I am no
expert in KDE/artsd interaction. If you can suggest specific things to d=
o
that can provide you with useful information, I am more than willing to d=
o
it. After all, the bug is quite simple to reproduce on several of
my systems - I just have the re-enable "run with highest possible
priority".
best regards
--
Peder Chr. N=F8rgaard Senior System Developer, M. Sc.
Ericsson Telebit A/S tel: +45 30 91 84 31
Skanderborgvej 232 fax: +45 89 38 51 01
DK-8260 Viby J, Denmark
e-mail: <email address hidden>
(old e-mail 2000-2003: <email address hidden>)
(old e-mail 1992-2000: <email address hidden>)