kde: system freezes at log-out when using kernel 2.4 and arts over alsa

Bug #9480 reported by Debian Bug Importer
8
Affects Status Importance Assigned to Milestone
arts (Debian)
Fix Released
Unknown
arts (Ubuntu)
Invalid
High
Unassigned

Bug Description

Automatically imported from Debian bug report #266760 http://bugs.debian.org/266760

Revision history for this message
In , Josh Metzler (joshdeb) wrote : Re: Bug#266760: kde: kde crashes X when quitting

On Wednesday 18 August 2004 07:47 pm, Anthony Labarre wrote:
> Package: kdebase-bin
> Version: 4:3.3.0-1
> Severity: critical
> File: kde
> Justification: breaks the whole system
>
>
> I've had this problem for weeks if not months, and it is very annoying. I
> haven't been able to locate _exactly_ where the problem comes from, but
> it happens very often that, when I quit KDE (be it by logging out,
> restarting or turning off my computer), the screen becomes black with the
> mouse pointer centered, and everything freezes. I then have no choice but
> to power off my system manually.

Do you have any access to another computer so you could try using ssh to
connect to the system after X has frozen? I know this isn't a solution, as
once X dies, it is usually not possible to get the display back, but it
would tell us if it is just X crashing or if the kernel is crashing too.

Josh

Revision history for this message
In , Chris Cheney (ccheney-cheney) wrote :

Which video driver do you use in xfree?

Chris

Revision history for this message
In , Anthony Labarre (anthony-labarre) wrote :

Chris Cheney wrote:

>Which video driver do you use in xfree?
>
>Chris
>
>
I use the nvidia driver - I have a GeForce 4 MX 420.

Anthony

Revision history for this message
In , =?ISO-8859-1?Q?Peder_Chr=2E_N=F8rgaard?= (peder-chr-norgaard) wrote : Two "me too"s, and some supplementary information

Hello,
 I have observed this bug on two different i386 Debian "unstable"
systems, one a new HP system where Xfree86 uses the Intel "i810" driver,
the other one a rather old Dell system using the "ati" driver.

 The systems are quite dead in both cases; they respond to "ping",
but neither "ssh" nor "telnet" access is possible.

 The bug behaves exactly as the submitter (Anthony Labarre
<email address hidden>) describes, except that I haven't had the bug
for a very long time - I never observed it until the upload of KDE 3.3 to
"unstable".

 Furthermore - and this may be very important - I never observed
the bug on an unmodified "unstable" system. Only after the "Xsession"
hack to the problems with KDE 3.3 and "tcsh" - as described in bug 265895
- got installed did I see the bug. Then it was completely reproducible -
happens every time I log out.

 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.

 Hope this all helps - KDE 3.3 is a great system.

--
Peder Chr. Nørgaard 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>)

Revision history for this message
In , Tony Smith (tony-smee) wrote : kde: kde crashes X when quitting

I'm experiencing this problem nearly (but not quite) 100% of the time on an
up-to-date (as of two-days ago) debian "unstable" system. This is with KDE
3.3 and in fact I didn't have the problem at all until the KDE 3.3 update.

Video driver is tdfx under xfree86-4.3

If you need more info, let me know.

Thanks,

Tony

Revision history for this message
In , Riku Voipio (riku-voipio) wrote :

tags 266760 +moreinfo,+help,+sid
thanks

Hi,

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.

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?
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=265865&msg=22

Revision history for this message
In , Riku Voipio (riku-voipio) wrote : bug editing

forwarded 270945 http://bugs.kde.org/show_bug.cgi?id=89812
severity 270945 important
tags 266760 +sid
tags 266760 +help
thanks

for #270945 - this is annoying but does not render kicker useless.

Revision history for this message
In , Gunnar Kloke (gunnar-kloke) wrote : same problem

i have the same problem since i upgraded kde from 3.2 up to 3.3 (two weeks
ago). i'm using debian unstable and get the error when i shutdown or reboot
my computer (i386) with kdm. if i shutdown or reboot with tty1 or any other
console (like konsole), the error doesn't occur. graphics driver is nvidia.
nothing changed, just kde-upgrade.

regards

gunnar

Revision history for this message
In , =?ISO-8859-1?Q?Peder_Chr=2E_N=F8rgaard?= (peder-chr-norgaard) wrote : Re: kde: kde crashes X when quitting

Important information: this bug is known upstream! See

http://bugs.kde.org/show_bug.cgi?id=88401
http://bugs.kde.org/show_bug.cgi?id=86426

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=265865&msg=22

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 do
that can provide you with useful information, I am more than willing to do
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ørgaard 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>)

Revision history for this message
In , Jason Le Vaillant (jfl2) wrote :

I am using the nv driver with a GeForce 2 MX440 under XFree86 4.3.0, and on my system this bug occurs only under kernel 2.4. If I downgrade to 2.2, or upgrade to 2.6 log out works fine.

Revision history for this message
In , =?ISO-8859-1?Q?Peder_Chr=2E_N=F8rgaard?= (peder-chr-norgaard) wrote :

On Mon, 20 Sep 2004, Peder Chr. Nørgaard wrote:

>
> 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 do
> that can provide you with useful information, I am more than willing to do
> 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".
>

Hmm - I may have to withdraw that promise - for this morning, after having
upgraded to the newly issued versions of kdebase (3.3.0a-1) and kdelibs
(3.3.0-2) the problem simply went away! Anyone else experience the same
thing?

By the way, I can confirm the observations from "Jason Le Vaillant"
<email address hidden>, that the bugs seems (or should I say "seemed") to be
related to 2.4 kernels. I have only observed the bug on 2.4 kernels, and
never on 2.6 kernels.

best regards

--
Peder Chr. Nørgaard 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>)

Revision history for this message
In , Dato Simó (dato) wrote : Re: Bug#266760: kde: kde crashes X when quitting

* Peder Chr. Nørgaard [Mon, 27 Sep 2004 11:38:09 +0200]:
> On Mon, 20 Sep 2004, Peder Chr. Nørgaard wrote:

> > 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 do
> > that can provide you with useful information, I am more than willing to do
> > 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".

> Hmm - I may have to withdraw that promise - for this morning, after having
> upgraded to the newly issued versions of kdebase (3.3.0a-1) and kdelibs
> (3.3.0-2) the problem simply went away! Anyone else experience the same
> thing?

  hi Peder, may I assume that it hasn't happened once since then? I've
  been playing around today, and it's still reproducible here...

  let me ask: what "audio device" is arts using? in case you're using
  "Autoselect", _perhaps_ the selection code between 3.3.0 and 3.3.0a
  changed and it selects OSS instead of ALSA (that's a very wild guess).

  in case you're not using alsa, could you please select it and do
  several trials to see if it happens?

  thanks in advance,

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

Any life, no matter how long and complex it may be, is made up of a
single moment: the moment in which a man finds out, once and for all,
who he is.
                -- Jorge Luis Borges

Revision history for this message
In , Dato Simó (dato) wrote : KDE Logout Hang because realtime artsd: a followup
Download full text (3.3 KiB)

[This is a crosspost to Debian Bug#266760 and KDE Bugs #88401 and #86426,
plus the debian-kde mailing list.]

  hi all, I've been "playing" around with this bug for a couple of
  hours, and after some hard reboots I've made some *little* findings
  which I'll share hoping that people with more knowledge may find it of
  some utility.

  for completeness sake, I'll restate what is already known:

    - it only happens with 2.4.x kernels

    - it only happens if arts is running with realtime priority
      (which means: checkbox enabled in control center and artswrapper
      is setuid root)

  my little findings are:

    - there has to be a sound associated with the "KDE is exiting"
      event. I'm surprised this has never been mentioned; perhaps it is
      that I'm wrong, but if you're looking for a workaround and
      disabling realtime priority is not an option, having no sound with
      the exit event seems to do the trick.

    - the "culprit" of "root of all evil" seems to be kdeinit_shutdown
      in /usr/bin/startkde: I'd say the hang is produced when kdeinit
      (as per kdeinit_shutdown request) tries to shutdown an arts
      process that is in the middle of playback. the lines in question
      are:

          echo 'startkde: Shutting down...' 1>&2

          # Clean up
          kdeinit_shutdown
          dcopserver_shutdown
          artsshell -q terminate

      adding a "sleep 10" statement just before the kdeinit_shutdown
      invocation seems to prevent the crash, too. that'd be because
      kdeinit makes arts terminate when the sound was already output.

      note that is effectively kdeinit who kills arts: if one takes out
      the "-q" from artsshell, it appears in the log: "unable to connect
      to sound server". I ignore if this is the expected behavior (I
      imagine it is), I just mention in case it may be relevant.

    - finally, one thing that strikes me as unusual but that may be not
      (and, again, I mention in case it's relevant): with the same KDE
      3.3 setup, when using a 2.6 kernel there is just one artsd process
      per user session; with a 2.4, though, there are *two* (one being
      the child of the other).

      I haven't been able to test if this happened with KDE 3.2, but if
      it didn't, perhaps something weird is going in there. also, IIRC,
      the child process did not respond to "kill -15", "kill -9" was
      necessary".

                                 * * *

    I would ask everybody who has experienced the problem if they can
    check the above: (1), that having no sound associated with "KDE is
    exiting" prevents the crash; (2), that the "sleep 10" statement in
    the proper place does, too; (3), that there are two artsd processes
    by user session when using Linux 2.4.

    also, it'd be nice if someone with access to a KDE 3.2 installation
    could check if (3) applies.

                                 * * *

    and that was all this time, please excuse my verbosity.

    hoping some of the above may be of some help to somebody,

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
    Listening to: Múm - Don't be afraid, you have just got ...

Read more...

Revision history for this message
In , Dato Simó (dato) wrote : Re: Bug#266760: KDE Logout Hang because realtime artsd: a followup

* Adeodato Simó [Fri, 01 Oct 2004 05:01:45 +0200]:

> - finally, one thing that strikes me as unusual but that may be not
> (and, again, I mention in case it's relevant): with the same KDE
> 3.3 setup, when using a 2.6 kernel there is just one artsd process
> per user session; with a 2.4, though, there are *two* (one being
> the child of the other).

> I haven't been able to test if this happened with KDE 3.2, but if
> it didn't, perhaps something weird is going in there. also, IIRC,
> the child process did not respond to "kill -15", "kill -9" was
> necessary".

  bah, actually I must be stupid or something. or I'm not getting enough
  sleep. lemme guess: those multiple processes are threads, which
  obviously explain why they only appear 2.4 kernels.

  the arts plugins that make it go threaded are (somebody correct me if
  I'm wrong, please, this was deduced from experience alone): akode,
  libarts1-mpeglib, libarts1-xine. a 2.4 system without those plugins
  should not (I think) experience any trouble.

  I, er, of course cannot determine who's at fault here, but I'd bet
  there is some tight coupling/coordination between threads that perhaps
  kdeinit_shutdown is breaking.

  but enough guesses already, some arts wizard should look into this.

  foo,

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

He has never been known to use a word that might send a reader to the
dictionary.
                -- William Faulkner (about Ernest Hemingway)

Revision history for this message
In , =?ISO-8859-1?Q?Peder_Chr=2E_N=F8rgaard?= (peder-chr-norgaard) wrote : Re: Bug#266760: kde: kde crashes X when quitting

On Fri, 1 Oct 2004, Adeodato Simó wrote:

> hi Peder, may I assume that it hasn't happened once since then? I've
> been playing around today, and it's still reproducible here...

You may safely assume that - I haven't seen the crashing bug since upgrade
of kdebase and kdelibs. That is, until:

>
> let me ask: what "audio device" is arts using? in case you're using
> "Autoselect", _perhaps_ the selection code between 3.3.0 and 3.3.0a
> changed and it selects OSS instead of ALSA (that's a very wild guess).
>
> in case you're not using alsa, could you please select it and do
> several trials to see if it happens?

Your guess may be wild, but it does hit the mark. I am using Autoselect
(I don't know how to see what the autoselect function ends up selecting).
When I change the setting to use ALSA explicitly, the crashing bug is back
with a vengeance.

(The setting is KDE Control Center/Sound & Multimedia/Sound System/
Hardware.)

>
> thanks in advance,
>
> --
> Adeodato Simó
> EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
>
> Any life, no matter how long and complex it may be, is made up of a
> single moment: the moment in which a man finds out, once and for all,
> who he is.
> -- Jorge Luis Borges
>

Peder Chr. Nørgaard 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>)

Revision history for this message
In , Dato Simó (dato) wrote :

* Peder Chr. Nørgaard [Sat, 02 Oct 2004 09:50:55 +0200]:
> On Fri, 1 Oct 2004, Adeodato Simó wrote:

> > let me ask: what "audio device" is arts using? in case you're using
> > "Autoselect", _perhaps_ the selection code between 3.3.0 and 3.3.0a
> > changed and it selects OSS instead of ALSA (that's a very wild guess).

> > in case you're not using alsa, could you please select it and do
> > several trials to see if it happens?

> Your guess may be wild, but it does hit the mark. I am using Autoselect
> (I don't know how to see what the autoselect function ends up selecting).
> When I change the setting to use ALSA explicitly, the crashing bug is back
> with a vengeance.

  ack, thanks a lot for checking.

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

Algebraic symbols are used when you do not know what you are talking about.
                -- Philippe Schnoebelen

Revision history for this message
In , Dato Simó (dato) wrote : tagging 266760

# Automatically generated email from bts, devscripts version 2.8.5
tags 266760 - moreinfo

Revision history for this message
In , Dato Simó (dato) wrote : retitle 266760 to kde: system freezes at log-out when using kernel 2.4 and arts over alsa

# Automatically generated email from bts, devscripts version 2.8.5
retitle 266760 kde: system freezes at log-out when using kernel 2.4 and arts over alsa

Revision history for this message
In , Riku Voipio (riku-voipio) wrote : Re: Bug#266760: KDE Logout Hang because realtime artsd: a followup

On Fri, Oct 01, 2004 at 05:01:45AM +0200, Adeodato Simó wrote:
> [This is a crosspost to Debian Bug#266760 and KDE Bugs #88401 and #86426,
> plus the debian-kde mailing list.]

> - the "culprit" of "root of all evil" seems to be kdeinit_shutdown
> in /usr/bin/startkde: I'd say the hang is produced when kdeinit
> (as per kdeinit_shutdown request) tries to shutdown an arts
> process that is in the middle of playback. the lines in question
> are:

That would be an arts bug then, right? By adding a sleep 10
to startkde we would just be working around the bug that artsd
running on realtime priority deadlocks the system if killed
while playing back?

Revision history for this message
In , Josh Metzler (joshdeb) wrote :

On Saturday 16 October 2004 11:10 am, Riku Voipio wrote:
> On Fri, Oct 01, 2004 at 05:01:45AM +0200, Adeodato Simó wrote:
> > [This is a crosspost to Debian Bug#266760 and KDE Bugs #88401 and
> > #86426, plus the debian-kde mailing list.]
> >
> > - the "culprit" of "root of all evil" seems to be kdeinit_shutdown
> > in /usr/bin/startkde: I'd say the hang is produced when kdeinit
> > (as per kdeinit_shutdown request) tries to shutdown an arts
> > process that is in the middle of playback. the lines in question
> > are:
>
> That would be an arts bug then, right? By adding a sleep 10
> to startkde we would just be working around the bug that artsd
> running on realtime priority deadlocks the system if killed
> while playing back?

If this is an arts bug, then it should be reassigned to arts. And, if it
is, it also affects testing, as testing has the same version of arts as
unstable. Has anyone using kernel 2.4 and arts over alsa in testing
experienced this bug?

Josh

Revision history for this message
In , Josh Metzler (joshdeb) wrote : this is a bug in arts and therefore affects sarge, too

reassign 266760 arts
tags 266760 - sid
tags 266760 + upstream
forwarded 266760 <email address hidden>
thanks

I am reassigning this bug to arts, as it seems it is obviously a bug in arts
(or a bug in kernel 2.4 or X that arts somehow triggers). In addition this
is an unresolved upstream bug (see 88401 in addition to 86426).

Known workarounds:
- use kernel 2.6
- use OSS rather than ALSA
- do not set arts to use realtime priority
- do not associate a soud with "KDE is exiting"
- add a "sleep 10" before "kdeinit_shutdown" in /usr/bin/startkde
- issue "killall artsd" from a terminal (or konsole) immediately before
shutting down.

Josh

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #266760 http://bugs.debian.org/266760

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (3.2 KiB)

Message-Id: <E1Bxa9d-0000HA-00@lecter>
Date: Thu, 19 Aug 2004 01:47:41 +0200
From: Anthony Labarre <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: kde: kde crashes X when quitting

Package: kdebase-bin
Version: 4:3.3.0-1
Severity: critical
File: kde
Justification: breaks the whole system

I've had this problem for weeks if not months, and it is very annoying. I haven't
been able to locate _exactly_ where the problem comes from, but it happens very
often that, when I quit KDE (be it by logging out, restarting or turning off my
computer), the screen becomes black with the mouse pointer centered, and
everything freezes. I then have no choice but to power off my system manually.

The only thing I'm sure about is that the problem is somewhere in the base
packages of KDE: this bug only happens when I use KDE (I've been using gnome,
xfce4 and others to test X, but this *never* happened with others window/desktop
managers), and closing all apps before exiting makes no change.

I've rebuilt some of my packages with apt-build (never using higher levels than
-02 plus a few extra "safe" options) and I wondered if this had something to do
with the unstability of my system under KDE, but I don't think so; since I use
apt-get dist-upgrade on a daily basis, surely most of - if not all - those
packages have long since been replaced.

Dying to read a solution ... KDE is such a great environment with such great
apps, but this is really getting on my nerves. More and more.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26
Locale: LANG=fr_BE@euro, LC_CTYPE=fr_BE@euro (ignored: LC_ALL set to fr_BE)

Versions of packages kdebase-bin depends on:
ii kdelibs4 4:3.3.0-1 KDE core libraries
ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi
ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an
ii libfam0c102 2.7.0-5 client library to control the FAM
ii libgcc1 1:3.4.1-5 GCC support library
ii libice6 4.3.0.dfsg.1-6 Inter-Client Exchange library
ii libidn11 0.5.2-2 GNU libidn library, implementation
ii libpam-runtime 0.76-22 Runtime support for the PAM librar
ii libpam0g 0.76-22 Pluggable Authentication Modules l
ii libpng12-0 1.2.5.0-7 PNG library - runtime
ii libqt3c102-mt 3:3.3.3-3 Qt GUI Library (Threaded runtime v
ii libsm6 4.3.0.dfsg.1-6 X Window System Session Management
ii libstdc++5 1:3.3.4-9 The GNU Standard C++ Library v3
ii libx11-6 4.3.0.dfsg.1-6 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-6 X Window System miscellaneous exte
ii libxrender1 0.8.3-7 X Rendering Extension client libra
ii libxtst6 4.3.0.dfsg.1-6 X Window System event recording an
ii xlibs 4.3.0.dfsg.1-6 X Window System client libraries m
ii zlib1g ...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 18 Aug 2004 21:38:45 -0400
From: Josh Metzler <email address hidden>
To: Anthony Labarre <email address hidden>,
 <email address hidden>
Subject: Re: Bug#266760: kde: kde crashes X when quitting

On Wednesday 18 August 2004 07:47 pm, Anthony Labarre wrote:
> Package: kdebase-bin
> Version: 4:3.3.0-1
> Severity: critical
> File: kde
> Justification: breaks the whole system
>
>
> I've had this problem for weeks if not months, and it is very annoying. I
> haven't been able to locate _exactly_ where the problem comes from, but
> it happens very often that, when I quit KDE (be it by logging out,
> restarting or turning off my computer), the screen becomes black with the
> mouse pointer centered, and everything freezes. I then have no choice but
> to power off my system manually.

Do you have any access to another computer so you could try using ssh to
connect to the system after X has frozen? I know this isn't a solution, as
once X dies, it is usually not possible to get the display back, but it
would tell us if it is just X crashing or if the kernel is crashing too.

Josh

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 19 Aug 2004 03:56:49 -0500
From: Chris Cheney <email address hidden>
To: Anthony Labarre <email address hidden>, <email address hidden>
Subject: Re: Bug#266760: kde: kde crashes X when quitting

--mgIE+9cwyCTt+85Z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Which video driver do you use in xfree?

Chris

--mgIE+9cwyCTt+85Z
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBJGtR0QZas444SvIRAn74AJ4iUa9d+9VJHOcD8+Ckzdtg39yifACggWoS
MMCtrF3/coODkJKW2k7BAow=
=bQOM
-----END PGP SIGNATURE-----

--mgIE+9cwyCTt+85Z--

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 19 Aug 2004 11:47:26 +0200
From: Anthony Labarre <email address hidden>
To: Chris Cheney <email address hidden>
CC: <email address hidden>
Subject: Re: Bug#266760: kde: kde crashes X when quitting

Chris Cheney wrote:

>Which video driver do you use in xfree?
>
>Chris
>
>
I use the nvidia driver - I have a GeForce 4 MX 420.

Anthony

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 25 Aug 2004 12:57:51 +0200 (CEST)
From: =?ISO-8859-1?Q?Peder_Chr=2E_N=F8rgaard?= <email address hidden>
To: <email address hidden>
Subject: Two "me too"s, and some supplementary information

Hello,
 I have observed this bug on two different i386 Debian "unstable"
systems, one a new HP system where Xfree86 uses the Intel "i810" driver,
the other one a rather old Dell system using the "ati" driver.

 The systems are quite dead in both cases; they respond to "ping",
but neither "ssh" nor "telnet" access is possible.

 The bug behaves exactly as the submitter (Anthony Labarre
<email address hidden>) describes, except that I haven't had the bug
for a very long time - I never observed it until the upload of KDE 3.3 to
"unstable".

 Furthermore - and this may be very important - I never observed
the bug on an unmodified "unstable" system. Only after the "Xsession"
hack to the problems with KDE 3.3 and "tcsh" - as described in bug 265895
- got installed did I see the bug. Then it was completely reproducible -
happens every time I log out.

 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.

 Hope this all helps - KDE 3.3 is a great system.

--
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>)

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 7 Sep 2004 19:35:45 +0100
From: Tony Smith <email address hidden>
To: <email address hidden>
Subject: kde: kde crashes X when quitting

I'm experiencing this problem nearly (but not quite) 100% of the time on an
up-to-date (as of two-days ago) debian "unstable" system. This is with KDE
3.3 and in fact I didn't have the problem at all until the KDE 3.3 update.

Video driver is tdfx under xfree86-4.3

If you need more info, let me know.

Thanks,

Tony

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sun, 19 Sep 2004 13:24:50 +0300
From: Riku Voipio <email address hidden>
To: <email address hidden>
Cc: <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: kde: kde crashes X when quitting

tags 266760 +moreinfo,+help,+sid
thanks

Hi,

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.

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?
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=265865&msg=22

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sun, 19 Sep 2004 14:20:27 +0300
From: Riku Voipio <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: bug editing

forwarded 270945 http://bugs.kde.org/show_bug.cgi?id=89812
severity 270945 important
tags 266760 +sid
tags 266760 +help
thanks

for #270945 - this is annoying but does not render kicker useless.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Sun, 19 Sep 2004 15:29:06 +0200
From: Gunnar Kloke <email address hidden>
To: <email address hidden>
Subject: same problem

i have the same problem since i upgraded kde from 3.2 up to 3.3 (two weeks
ago). i'm using debian unstable and get the error when i shutdown or reboot
my computer (i386) with kdm. if i shutdown or reboot with tty1 or any other
console (like konsole), the error doesn't occur. graphics driver is nvidia.
nothing changed, just kde-upgrade.

regards

gunnar

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (3.2 KiB)

Message-ID: <email address hidden>
Date: Mon, 20 Sep 2004 08:51:53 +0200 (CEST)
From: =?ISO-8859-1?Q?Peder_Chr=2E_N=F8rgaard?= <email address hidden>
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
http://bugs.kde.org/show_bug.cgi?id=3D86426

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: Peder.Chr.Norgaard@eric...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sat, 25 Sep 2004 07:07:51 +0000
From: "Jason Le Vaillant" <email address hidden>
To: <email address hidden>
Subject: kde: kde crashes X when quitting

I am using the nv driver with a GeForce 2 MX440 under XFree86 4.3.0, and on=
 my system this bug occurs only under kernel 2.4. If I downgrade to 2.2, =
or upgrade to 2.6 log out works fine.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Mon, 27 Sep 2004 11:38:09 +0200 (CEST)
From: =?ISO-8859-1?Q?Peder_Chr=2E_N=F8rgaard?= <email address hidden>
To: <email address hidden>
cc: Riku Voipio <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: kde: kde crashes X when quitting

On Mon, 20 Sep 2004, Peder Chr. N=F8rgaard wrote:

>
> 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=
 do
> that can provide you with useful information, I am more than willing to=
 do
> 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".
>

Hmm - I may have to withdraw that promise - for this morning, after havin=
g
upgraded to the newly issued versions of kdebase (3.3.0a-1) and kdelibs
(3.3.0-2) the problem simply went away! Anyone else experience the same
thing?

By the way, I can confirm the observations from "Jason Le Vaillant"
<email address hidden>, that the bugs seems (or should I say "seemed") to b=
e
related to 2.4 kernels. I have only observed the bug on 2.4 kernels, and
never on 2.6 kernels.

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>)

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Fri, 1 Oct 2004 03:25:11 +0200
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: Peder =?iso-8859-1?Q?Chr=2E_N=F8rgaard?= <email address hidden>,
 <email address hidden>
Subject: Re: Bug#266760: kde: kde crashes X when quitting

* Peder Chr. N�rd [Mon, 27 Sep 2004 11:38:09 +0200]:
> On Mon, 20 Sep 2004, Peder Chr. N�rd wrote:

> > 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 do
> > that can provide you with useful information, I am more than willing to do
> > 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".

> Hmm - I may have to withdraw that promise - for this morning, after having
> upgraded to the newly issued versions of kdebase (3.3.0a-1) and kdelibs
> (3.3.0-2) the problem simply went away! Anyone else experience the same
> thing?

  hi Peder, may I assume that it hasn't happened once since then? I've
  been playing around today, and it's still reproducible here...

  let me ask: what "audio device" is arts using? in case you're using
  "Autoselect", _perhaps_ the selection code between 3.3.0 and 3.3.0a
  changed and it selects OSS instead of ALSA (that's a very wild guess).

  in case you're not using alsa, could you please select it and do
  several trials to see if it happens?

  thanks in advance,

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

Any life, no matter how long and complex it may be, is made up of a
single moment: the moment in which a man finds out, once and for all,
who he is.
                -- Jorge Luis Borges

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (3.7 KiB)

Message-ID: <email address hidden>
Date: Fri, 1 Oct 2004 05:01:45 +0200
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: <email address hidden>, <email address hidden>, <email address hidden>,
 <email address hidden>
Cc: Anthony Labarre <email address hidden>,
 Peder =?iso-8859-1?Q?Chr=2E_N=F8rgaard?= <email address hidden>
Subject: KDE Logout Hang because realtime artsd: a followup

[This is a crosspost to Debian Bug#266760 and KDE Bugs #88401 and #86426,
plus the debian-kde mailing list.]

  hi all, I've been "playing" around with this bug for a couple of
  hours, and after some hard reboots I've made some *little* findings
  which I'll share hoping that people with more knowledge may find it of
  some utility.

  for completeness sake, I'll restate what is already known:

    - it only happens with 2.4.x kernels

    - it only happens if arts is running with realtime priority
      (which means: checkbox enabled in control center and artswrapper
      is setuid root)

  my little findings are:

    - there has to be a sound associated with the "KDE is exiting"
      event. I'm surprised this has never been mentioned; perhaps it is
      that I'm wrong, but if you're looking for a workaround and
      disabling realtime priority is not an option, having no sound with
      the exit event seems to do the trick.

    - the "culprit" of "root of all evil" seems to be kdeinit_shutdown
      in /usr/bin/startkde: I'd say the hang is produced when kdeinit
      (as per kdeinit_shutdown request) tries to shutdown an arts
      process that is in the middle of playback. the lines in question
      are:

          echo 'startkde: Shutting down...' 1>&2

          # Clean up
          kdeinit_shutdown
          dcopserver_shutdown
          artsshell -q terminate

      adding a "sleep 10" statement just before the kdeinit_shutdown
      invocation seems to prevent the crash, too. that'd be because
      kdeinit makes arts terminate when the sound was already output.

      note that is effectively kdeinit who kills arts: if one takes out
      the "-q" from artsshell, it appears in the log: "unable to connect
      to sound server". I ignore if this is the expected behavior (I
      imagine it is), I just mention in case it may be relevant.

    - finally, one thing that strikes me as unusual but that may be not
      (and, again, I mention in case it's relevant): with the same KDE
      3.3 setup, when using a 2.6 kernel there is just one artsd process
      per user session; with a 2.4, though, there are *two* (one being
      the child of the other).

      I haven't been able to test if this happened with KDE 3.2, but if
      it didn't, perhaps something weird is going in there. also, IIRC,
      the child process did not respond to "kill -15", "kill -9" was
      necessary".

                                 * * *

    I would ask everybody who has experienced the problem if they can
    check the above: (1), that having no sound associated with "KDE is
    exiting" prevents the crash; (2), that the "sleep 10" statement in
    the proper place does, too; (3), that there are two artsd processes
    by ...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Fri, 1 Oct 2004 07:59:14 +0200
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: <email address hidden>, <email address hidden>, <email address hidden>,
 <email address hidden>
Cc: Anthony Labarre <email address hidden>,
 Peder =?iso-8859-1?Q?Chr=2E_N=F8rgaard?= <email address hidden>
Subject: Re: Bug#266760: KDE Logout Hang because realtime artsd: a followup

* Adeodato Sim�ri, 01 Oct 2004 05:01:45 +0200]:

> - finally, one thing that strikes me as unusual but that may be not
> (and, again, I mention in case it's relevant): with the same KDE
> 3.3 setup, when using a 2.6 kernel there is just one artsd process
> per user session; with a 2.4, though, there are *two* (one being
> the child of the other).

> I haven't been able to test if this happened with KDE 3.2, but if
> it didn't, perhaps something weird is going in there. also, IIRC,
> the child process did not respond to "kill -15", "kill -9" was
> necessary".

  bah, actually I must be stupid or something. or I'm not getting enough
  sleep. lemme guess: those multiple processes are threads, which
  obviously explain why they only appear 2.4 kernels.

  the arts plugins that make it go threaded are (somebody correct me if
  I'm wrong, please, this was deduced from experience alone): akode,
  libarts1-mpeglib, libarts1-xine. a 2.4 system without those plugins
  should not (I think) experience any trouble.

  I, er, of course cannot determine who's at fault here, but I'd bet
  there is some tight coupling/coordination between threads that perhaps
  kdeinit_shutdown is breaking.

  but enough guesses already, some arts wizard should look into this.

  foo,

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

He has never been known to use a word that might send a reader to the
dictionary.
                -- William Faulkner (about Ernest Hemingway)

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sat, 2 Oct 2004 09:50:55 +0200 (CEST)
From: =?ISO-8859-1?Q?Peder_Chr=2E_N=F8rgaard?= <email address hidden>
To: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
cc: <email address hidden>
Subject: Re: Bug#266760: kde: kde crashes X when quitting

On Fri, 1 Oct 2004, Adeodato Sim=F3 wrote:

> hi Peder, may I assume that it hasn't happened once since then? I've
> been playing around today, and it's still reproducible here...

You may safely assume that - I haven't seen the crashing bug since upgrad=
e
of kdebase and kdelibs. That is, until:

>
> let me ask: what "audio device" is arts using? in case you're using
> "Autoselect", _perhaps_ the selection code between 3.3.0 and 3.3.0a
> changed and it selects OSS instead of ALSA (that's a very wild guess).
>
> in case you're not using alsa, could you please select it and do
> several trials to see if it happens?

Your guess may be wild, but it does hit the mark. I am using Autoselect
(I don't know how to see what the autoselect function ends up selecting).
When I change the setting to use ALSA explicitly, the crashing bug is bac=
k
with a vengeance.

(The setting is KDE Control Center/Sound & Multimedia/Sound System/
Hardware.)

>
> thanks in advance,
>
> --
> Adeodato Sim=F3
> EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
>
> Any life, no matter how long and complex it may be, is made up of a
> single moment: the moment in which a man finds out, once and for all,
> who he is.
> -- Jorge Luis Borges
>

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>)

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sun, 3 Oct 2004 14:57:17 +0200
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: Peder =?iso-8859-1?Q?Chr=2E_N=F8rgaard?= <email address hidden>,
 <email address hidden>
Subject: Re: Bug#266760: kde: kde crashes X when quitting

* Peder Chr. N�rd [Sat, 02 Oct 2004 09:50:55 +0200]:
> On Fri, 1 Oct 2004, Adeodato Sim�ote:

> > let me ask: what "audio device" is arts using? in case you're using
> > "Autoselect", _perhaps_ the selection code between 3.3.0 and 3.3.0a
> > changed and it selects OSS instead of ALSA (that's a very wild guess).

> > in case you're not using alsa, could you please select it and do
> > several trials to see if it happens?

> Your guess may be wild, but it does hit the mark. I am using Autoselect
> (I don't know how to see what the autoselect function ends up selecting).
> When I change the setting to use ALSA explicitly, the crashing bug is back
> with a vengeance.

  ack, thanks a lot for checking.

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

Algebraic symbols are used when you do not know what you are talking about.
                -- Philippe Schnoebelen

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Sun, 3 Oct 2004 16:53:14 +0200
From: Adeodato Simó <email address hidden>
To: <email address hidden>
Subject: tagging 266760

# Automatically generated email from bts, devscripts version 2.8.5
tags 266760 - moreinfo

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 5 Oct 2004 07:19:00 +0200
From: Adeodato Simó <email address hidden>
To: <email address hidden>
Subject: retitle 266760 to kde: system freezes at log-out when using kernel 2.4 and arts over alsa

# Automatically generated email from bts, devscripts version 2.8.5
retitle 266760 kde: system freezes at log-out when using kernel 2.4 and arts over alsa

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sat, 16 Oct 2004 18:10:19 +0300
From: Riku Voipio <email address hidden>
To: <email address hidden>, <email address hidden>, <email address hidden>, <email address hidden>,
 Anthony Labarre <email address hidden>,
 Peder =?iso-8859-15?Q?Chr=2E_N=F8rgaard?= <email address hidden>
Subject: Re: Bug#266760: KDE Logout Hang because realtime artsd: a followup

On Fri, Oct 01, 2004 at 05:01:45AM +0200, Adeodato Sim=F3 wrote:
> [This is a crosspost to Debian Bug#266760 and KDE Bugs #88401 and #8642=
6,
> plus the debian-kde mailing list.]

> - the "culprit" of "root of all evil" seems to be kdeinit_shutdown
> in /usr/bin/startkde: I'd say the hang is produced when kdeinit
> (as per kdeinit_shutdown request) tries to shutdown an arts
> process that is in the middle of playback. the lines in question
> are:

That would be an arts bug then, right? By adding a sleep 10
to startkde we would just be working around the bug that artsd
running on realtime priority deadlocks the system if killed
while playing back?

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 26 Oct 2004 17:34:31 -0400
From: Josh Metzler <email address hidden>
To: Riku Voipio <email address hidden>, <email address hidden>
Subject: Re: Bug#266760: KDE Logout Hang because realtime artsd: a followup

On Saturday 16 October 2004 11:10 am, Riku Voipio wrote:
> On Fri, Oct 01, 2004 at 05:01:45AM +0200, Adeodato Sim=F3 wrote:
> > [This is a crosspost to Debian Bug#266760 and KDE Bugs #88401 and
> > #86426, plus the debian-kde mailing list.]
> >
> > - the "culprit" of "root of all evil" seems to be kdeinit_shutdown
> > in /usr/bin/startkde: I'd say the hang is produced when kdeinit
> > (as per kdeinit_shutdown request) tries to shutdown an arts
> > process that is in the middle of playback. the lines in question
> > are:
>
> That would be an arts bug then, right? By adding a sleep 10
> to startkde we would just be working around the bug that artsd
> running on realtime priority deadlocks the system if killed
> while playing back?

If this is an arts bug, then it should be reassigned to arts. And, if it=20
is, it also affects testing, as testing has the same version of arts as=20
unstable. Has anyone using kernel 2.4 and arts over alsa in testing=20
experienced this bug?

Josh

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 26 Oct 2004 21:51:14 -0400
From: Josh Metzler <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: this is a bug in arts and therefore affects sarge, too

reassign 266760 arts
tags 266760 - sid
tags 266760 + upstream
forwarded 266760 <email address hidden>
thanks

I am reassigning this bug to arts, as it seems it is obviously a bug in arts
(or a bug in kernel 2.4 or X that arts somehow triggers). In addition this
is an unresolved upstream bug (see 88401 in addition to 86426).

Known workarounds:
- use kernel 2.6
- use OSS rather than ALSA
- do not set arts to use realtime priority
- do not associate a soud with "KDE is exiting"
- add a "sleep 10" before "kdeinit_shutdown" in /usr/bin/startkde
- issue "killall artsd" from a terminal (or konsole) immediately before
shutting down.

Josh

Revision history for this message
Matt Zimmerman (mdz) wrote :

Kernel 2.6 reported to have no problems, so NOTWARTY

Revision history for this message
In , Dato Simó (dato) wrote : bug 266760 is forwarded to http://bugs.kde.org/86426

# Automatically generated email from bts, devscripts version 2.8.5
 # Give http address of the bug
forwarded 266760 http://bugs.kde.org/86426

Revision history for this message
In , Dato Simó (dato) wrote : Re: Bug#266760: this is a bug in arts and therefore affects sarge, too

* Josh Metzler [Tue, 26 Oct 2004 21:51:14 -0400]:

> this is a bug in arts and therefore affects sarge, too
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^

  I'm not sure this is true. I checked once some days after my
  investigation and didn't seem to be the case.

  I'll try to re-check soon.

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

The reader this message encounters not failing to understand is cursed.

Revision history for this message
In , Riku Voipio (riku-voipio) wrote :

On Tue, Oct 26, 2004 at 09:51:14PM -0400, Josh Metzler wrote:
> Known workarounds:
> - do not set arts to use realtime priority

Maybe we should just drop setuid bit from artswrapper? That might
save us from a security upload in future...

The drawback is that 2.6 kernel users might get annoyed that they
have to use dpkg-statoverride to enable realtim priority.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 27 Oct 2004 13:10:56 +0200
From: Adeodato Simó <email address hidden>
To: <email address hidden>
Subject: bug 266760 is forwarded to http://bugs.kde.org/86426

# Automatically generated email from bts, devscripts version 2.8.5
 # Give http address of the bug
forwarded 266760 http://bugs.kde.org/86426

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 27 Oct 2004 13:17:13 +0200
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: Josh Metzler <email address hidden>, <email address hidden>
Subject: Re: Bug#266760: this is a bug in arts and therefore affects sarge, too

* Josh Metzler [Tue, 26 Oct 2004 21:51:14 -0400]:

> this is a bug in arts and therefore affects sarge, too
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^

  I'm not sure this is true. I checked once some days after my
  investigation and didn't seem to be the case.

  I'll try to re-check soon.

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

The reader this message encounters not failing to understand is cursed.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 27 Oct 2004 15:11:11 +0300
From: Riku Voipio <email address hidden>
To: Josh Metzler <email address hidden>, <email address hidden>
Subject: Re: Bug#266760: this is a bug in arts and therefore affects sarge, too

On Tue, Oct 26, 2004 at 09:51:14PM -0400, Josh Metzler wrote:
> Known workarounds:
> - do not set arts to use realtime priority

Maybe we should just drop setuid bit from artswrapper? That might
save us from a security upload in future...

The drawback is that 2.6 kernel users might get annoyed that they
have to use dpkg-statoverride to enable realtim priority.

Revision history for this message
In , =?UTF-8?B?T25kxZllaiBNYXphbsO9?= (mazany-o) wrote : The same problem

I have the same problem, when I try from console on tty0 shutdown -h -P
now, then computer freezes at quiting kdm: ......, when I try shutdown
computer from KDE menu, I have a black screen with a my keyboard flag on
the top of left corner and everything freezes. I am also using nvidia
drivers from nvidia - no nv from Xfree. Do you have any solution? Thank you
       Ondrej Mazany

Revision history for this message
In , =?UTF-8?B?T25kxZllaiBNYXphbsO9?= (mazany-o) wrote : kdm problem found

I propably solved the problem - it is in the sound system artsd - i
turned off network sound and realtime processing and the computer halt now.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 28 Oct 2004 19:07:38 +0200
From: =?UTF-8?B?T25kxZllaiBNYXphbsO9?= <email address hidden>
To: <email address hidden>
Subject: The same problem

I have the same problem, when I try from console on tty0 shutdown -h -P
now, then computer freezes at quiting kdm: ......, when I try shutdown
computer from KDE menu, I have a black screen with a my keyboard flag on
the top of left corner and everything freezes. I am also using nvidia
drivers from nvidia - no nv from Xfree. Do you have any solution? Thank you
       Ondrej Mazany

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Fri, 29 Oct 2004 07:48:48 +0200
From: =?UTF-8?B?T25kxZllaiBNYXphbsO9?= <email address hidden>
To: <email address hidden>
Subject: kdm problem found

I propably solved the problem - it is in the sound system artsd - i
turned off network sound and realtime processing and the computer halt now.

Revision history for this message
In , Thomas Hood (jdthood-aglu) wrote : Plan for fixing RC bug?

What are the plans (if any) for fixing RC bug #266760?

No reply will be interpreted as an answer that there is no plan.

One way of solving the problem would be to make alsa-modules-* (for 2.4)
conflict with arts.
--
Thomas Hood

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <1099577274.3654.372.camel@thanatos>
Date: Thu, 04 Nov 2004 15:07:54 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: Plan for fixing RC bug?

What are the plans (if any) for fixing RC bug #266760?

No reply will be interpreted as an answer that there is no plan.

One way of solving the problem would be to make alsa-modules-* (for 2.4)
conflict with arts.
--
Thomas Hood

Revision history for this message
In , Dato Simó (dato) wrote :

* Thomas Hood [Thu, 04 Nov 2004 15:07:54 +0100]:
> What are the plans (if any) for fixing RC bug #266760?

> No reply will be interpreted as an answer that there is no plan.

> One way of solving the problem would be to make alsa-modules-* (for 2.4)
> conflict with arts.

  this I said on irc:

17:19 <jdthood> Anyone working on #266760?
17:21 <dato> jdthood: I believe that it does not apply to sarge
17:22 <dato> the sarge tag that I put there was removing without checking
17:22 <dato> I'm still hoping to find some time to test it again before putting it again, though
17:23 <dato> if anybody else can check, it'd be great

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

One way to make your old car run better is to look up the price of a new model.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 4 Nov 2004 17:24:01 +0100
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: Thomas Hood <email address hidden>
Cc: <email address hidden>
Subject: Re: Plan for fixing RC bug?

* Thomas Hood [Thu, 04 Nov 2004 15:07:54 +0100]:
> What are the plans (if any) for fixing RC bug #266760?

> No reply will be interpreted as an answer that there is no plan.

> One way of solving the problem would be to make alsa-modules-* (for 2.4)
> conflict with arts.

  this I said on irc:

17:19 <jdthood> Anyone working on #266760?
17:21 <dato> jdthood: I believe that it does not apply to sarge
17:22 <dato> the sarge tag that I put there was removing without checking
17:22 <dato> I'm still hoping to find some time to test it again before putting it again, though
17:23 <dato> if anybody else can check, it'd be great

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

One way to make your old car run better is to look up the price of a new model.

Revision history for this message
In , Dato Simó (dato) wrote :

* Adeodato Simó [Thu, 04 Nov 2004 17:24:01 +0100]:

> 17:19 <jdthood> Anyone working on #266760?
> 17:21 <dato> jdthood: I believe that it does not apply to sarge
> 17:22 <dato> the sarge tag that I put there was removing without checking

  s/sarge tag/sid tag/, of course. but in any case, not true any more.

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

Experience is something you don't get until just after you need it.

Revision history for this message
In , Dato Simó (dato) wrote : Re: this is a bug in arts and therefore affects sarge, too

* Josh Metzler [Tue, 26 Oct 2004 21:51:14 -0400]:

> Known workarounds:
> - use kernel 2.6
> - use OSS rather than ALSA
> - do not set arts to use realtime priority
> - do not associate a soud with "KDE is exiting"

  or use a sound in WAV format (not ogg or mp3).

> - add a "sleep 10" before "kdeinit_shutdown" in /usr/bin/startkde
> - issue "killall artsd" from a terminal (or konsole) immediately before
> shutting down.

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

America may be unique in being a country which has leapt from barbarism
to decadence without touching civilization.
                -- John O'Hara

Revision history for this message
In , Dato Simó (dato) wrote : the arts bug applies to sarge, too

  sadly, I've just learnt that the bug is reproducible in sarge too. I
  was misled in my previous checks since the default logout sound in KDE
  3.2 is in WAV format, which does not trigger the bug. OGG or MP3 is
  necessary.

  moreover, I managed to reproduce the bug with arts 1.2.3, so having
  let 1.3.x into sarge has nothing to do with the status of the bug.

  aba, if you think that sarge-ignore is ok for it, then I have nothing
  more to say. it's nasty as hell, though, but there are many
  workarounds available and very specific conditions have to be met.

  cu,

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

Proper treatment will cure a cold in seven days, but left to itself, a
cold will hang on for a week.
                -- Darrell Huff

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Fri, 5 Nov 2004 01:55:30 +0100
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: <email address hidden>, <email address hidden>
Cc: Josh Metzler <email address hidden>
Subject: Re: this is a bug in arts and therefore affects sarge, too

* Josh Metzler [Tue, 26 Oct 2004 21:51:14 -0400]:

> Known workarounds:
> - use kernel 2.6
> - use OSS rather than ALSA
> - do not set arts to use realtime priority
> - do not associate a soud with "KDE is exiting"

  or use a sound in WAV format (not ogg or mp3).

> - add a "sleep 10" before "kdeinit_shutdown" in /usr/bin/startkde
> - issue "killall artsd" from a terminal (or konsole) immediately before
> shutting down.

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

America may be unique in being a country which has leapt from barbarism
to decadence without touching civilization.
                -- John O'Hara

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Fri, 5 Nov 2004 01:53:17 +0100
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: <email address hidden>
Subject: Re: Plan for fixing RC bug?

* Adeodato Sim�hu, 04 Nov 2004 17:24:01 +0100]:

> 17:19 <jdthood> Anyone working on #266760?
> 17:21 <dato> jdthood: I believe that it does not apply to sarge
> 17:22 <dato> the sarge tag that I put there was removing without checking

  s/sarge tag/sid tag/, of course. but in any case, not true any more.

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

Experience is something you don't get until just after you need it.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Fri, 5 Nov 2004 02:05:14 +0100
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: <email address hidden>
Cc: Andreas Barth <email address hidden>,
 Thomas Hood <email address hidden>
Subject: the arts bug applies to sarge, too

  sadly, I've just learnt that the bug is reproducible in sarge too. I
  was misled in my previous checks since the default logout sound in KDE
  3.2 is in WAV format, which does not trigger the bug. OGG or MP3 is
  necessary.

  moreover, I managed to reproduce the bug with arts 1.2.3, so having
  let 1.3.x into sarge has nothing to do with the status of the bug.

  aba, if you think that sarge-ignore is ok for it, then I have nothing
  more to say. it's nasty as hell, though, but there are many
  workarounds available and very specific conditions have to be met.

  cu,

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

Proper treatment will cure a cold in seven days, but left to itself, a
cold will hang on for a week.
                -- Darrell Huff

Revision history for this message
In , Chris Cheney (ccheney-cheney) wrote : Re: Bug#266760: the arts bug applies to sarge, too

On Fri, Nov 05, 2004 at 02:05:14AM +0100, Adeodato Simó wrote:
> sadly, I've just learnt that the bug is reproducible in sarge too. I
> was misled in my previous checks since the default logout sound in KDE
> 3.2 is in WAV format, which does not trigger the bug. OGG or MP3 is
> necessary.
>
> moreover, I managed to reproduce the bug with arts 1.2.3, so having
> let 1.3.x into sarge has nothing to do with the status of the bug.
>
> aba, if you think that sarge-ignore is ok for it, then I have nothing
> more to say. it's nasty as hell, though, but there are many
> workarounds available and very specific conditions have to be met.
>
> cu,

Is the best solution to just remove setuid on artswrapper? If so I can
do that and upload a new arts soon...

Thanks,
Chris

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 4 Nov 2004 19:58:29 -0600
From: Chris Cheney <email address hidden>
To: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>,
 <email address hidden>
Cc: Andreas Barth <email address hidden>,
 Thomas Hood <email address hidden>
Subject: Re: Bug#266760: the arts bug applies to sarge, too

On Fri, Nov 05, 2004 at 02:05:14AM +0100, Adeodato Sim�ote:
> sadly, I've just learnt that the bug is reproducible in sarge too. I
> was misled in my previous checks since the default logout sound in KDE
> 3.2 is in WAV format, which does not trigger the bug. OGG or MP3 is
> necessary.
>
> moreover, I managed to reproduce the bug with arts 1.2.3, so having
> let 1.3.x into sarge has nothing to do with the status of the bug.
>
> aba, if you think that sarge-ignore is ok for it, then I have nothing
> more to say. it's nasty as hell, though, but there are many
> workarounds available and very specific conditions have to be met.
>
> cu,

Is the best solution to just remove setuid on artswrapper? If so I can
do that and upload a new arts soon...

Thanks,
Chris

Revision history for this message
In , Thomas Hood (jdthood-aglu) wrote : hack workaround into arts?

Could arts be hacked so that it plays non-wav files in
non-realtime-priority mode on Linux 2.4 + ALSA systems?

--
Thomas Hood

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <1099643416.3654.391.camel@thanatos>
Date: Fri, 05 Nov 2004 09:30:16 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: hack workaround into arts?

Could arts be hacked so that it plays non-wav files in
non-realtime-priority mode on Linux 2.4 + ALSA systems?

--
Thomas Hood

Revision history for this message
In , Steve Langasek (vorlon) wrote : Re: kde: system freezes at log out when using kernel 2.4 and arts over alsa

> Could arts be hacked so that it plays non-wav files in
> non-realtime-priority mode on Linux 2.4 + ALSA systems?

No; only suid artswrapper has the necessary privs to change the kernel
scheduling priority of the artsd thread, and it (correctly, so I can't
assert that there's a security issue here ;) drops suid privs immediately
after this change. However, a more realistic workaround might be for
artswrapper to detect the kernel version and avoid fiddling with scheduler
policies at all on 2.4 (possibly in favor of setting nice levels instead, if
this is safe).

--
Steve Langasek
postmodern programmer

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Mon, 15 Nov 2004 05:17:21 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: Re: kde: system freezes at log out when using kernel 2.4 and arts over alsa

--DEueqSqTbz/jWVG1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> Could arts be hacked so that it plays non-wav files in
> non-realtime-priority mode on Linux 2.4 + ALSA systems?

No; only suid artswrapper has the necessary privs to change the kernel
scheduling priority of the artsd thread, and it (correctly, so I can't
assert that there's a security issue here ;) drops suid privs immediately
after this change. However, a more realistic workaround might be for
artswrapper to detect the kernel version and avoid fiddling with scheduler
policies at all on 2.4 (possibly in favor of setting nice levels instead, if
this is safe).

--=20
Steve Langasek
postmodern programmer

--DEueqSqTbz/jWVG1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBmKxeKN6ufymYLloRAme+AJ49nZeIye37iHWDxz0CzS55Kp8agQCaAhr+
3IvKVYaNHqayKVyNnrCRgu8=
=7njf
-----END PGP SIGNATURE-----

--DEueqSqTbz/jWVG1--

Revision history for this message
In , Thomas Hood (jdthood-aglu) wrote : Info copied from upstream bug report log

FYI it was remarked in the log of the upstream bug report:

> Using OSS rather than ALSA does not work as a workaround. I still get
> a lockup on shutdown using OSS + realtime priority
>
> Not having a sound associated with "KDE is exiting" is not a
> workaround. That's the first thing I turn off, and I still get a
> lockup on shutdown.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <1100720988.15510.187.camel@thanatos>
Date: Wed, 17 Nov 2004 20:49:48 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: Info copied from upstream bug report log

FYI it was remarked in the log of the upstream bug report:

> Using OSS rather than ALSA does not work as a workaround. I still get
> a lockup on shutdown using OSS + realtime priority
>
> Not having a sound associated with "KDE is exiting" is not a
> workaround. That's the first thing I turn off, and I still get a
> lockup on shutdown.

Revision history for this message
In , Christopher Martin (chrsmrtn) wrote : Bug#266760: fixed in arts 1.3.2-1
Download full text (3.2 KiB)

Source: arts
Source-Version: 1.3.2-1

We believe that the bug you reported is fixed in the latest version of
arts, which is due to be installed in the Debian FTP archive:

arts_1.3.2-1.diff.gz
  to pool/main/a/arts/arts_1.3.2-1.diff.gz
arts_1.3.2-1.dsc
  to pool/main/a/arts/arts_1.3.2-1.dsc
arts_1.3.2-1_all.deb
  to pool/main/a/arts/arts_1.3.2-1_all.deb
arts_1.3.2.orig.tar.gz
  to pool/main/a/arts/arts_1.3.2.orig.tar.gz
libarts1-dev_1.3.2-1_i386.deb
  to pool/main/a/arts/libarts1-dev_1.3.2-1_i386.deb
libarts1_1.3.2-1_i386.deb
  to pool/main/a/arts/libarts1_1.3.2-1_i386.deb
libartsc0-dev_1.3.2-1_i386.deb
  to pool/main/a/arts/libartsc0-dev_1.3.2-1_i386.deb
libartsc0_1.3.2-1_i386.deb
  to pool/main/a/arts/libartsc0_1.3.2-1_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christopher Martin <email address hidden> (supplier of updated arts package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 6 Dec 2004 12:26:16 -0500
Source: arts
Binary: libarts1 libarts1-dev libartsc0-dev libartsc0 arts
Architecture: source i386 all
Version: 1.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers <email address hidden>
Changed-By: Christopher Martin <email address hidden>
Description:
 arts - Analog Realtime Synthesizer (aRts) metapackage
 libarts1 - aRts Sound system
 libarts1-dev - aRts Sound system (development files)
 libartsc0 - aRts Sound system C support library
 libartsc0-dev - aRts Sound system C support library (development files)
Closes: 266760
Changes:
 arts (1.3.2-1) unstable; urgency=medium
 .
   * New upstream release.
   * No longer set suid on artswrapper. Works around a 2.4 kernel lockup bug,
     but disables realtime priority. Added a README.Debian, explaining the
     change and how to cope with it, and reverse it.
     (Closes: #266760)
   * Add Suggests on akode, which often suffices in place of realtime priority.
Files:
 b2a657fd78fcc269293ab8ee546e8b50 973 libs optional arts_1.3.2-1.dsc
 7dc40742d9853845bd306130d1c0bc3a 1274578 libs optional arts_1.3.2.orig.tar.gz
 d46ee1a07c4d4bb7cf4b2c38ed30e993 31709 libs optional arts_1.3.2-1.diff.gz
 8ec6f2d66541a3c97566fce00b063a27 1145742 libs optional libarts1_1.3.2-1_i386.deb
 fb606f510b30d7b09e2e143f004ccc66 175070 libdevel optional libarts1-dev_1.3.2-1_i386.deb
 35b08ac91cf8130caeeb34f6e757e06a 12898 libs optional libartsc0_1.3.2-1_i386.deb
 ec9cc59790ae3a84f6fa3cda1a079b04 8548 libdevel optional libartsc0-dev_1.3.2-1_i386.deb
 5584858c1b784a8dc5a69a0f12df0ba6 3538 sound optional arts_1.3.2-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBtePwibPvMsrqrwMRAtgEAKDJpcyUcmv3wHKElbXpX2J6ExEiEgCggqyL
V7gNNI+fwG1HxExjJLPh...

Read more...

Revision history for this message
In , Dato Simó (dato) wrote : reopening 266760, tagging 266760

# Automatically generated email from bts, devscripts version 2.8.5
reopen 266760
tags 266760 = sarge pending

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (3.4 KiB)

Message-Id: <email address hidden>
Date: Tue, 07 Dec 2004 12:47:04 -0500
From: Christopher Martin <email address hidden>
To: <email address hidden>
Subject: Bug#266760: fixed in arts 1.3.2-1

Source: arts
Source-Version: 1.3.2-1

We believe that the bug you reported is fixed in the latest version of
arts, which is due to be installed in the Debian FTP archive:

arts_1.3.2-1.diff.gz
  to pool/main/a/arts/arts_1.3.2-1.diff.gz
arts_1.3.2-1.dsc
  to pool/main/a/arts/arts_1.3.2-1.dsc
arts_1.3.2-1_all.deb
  to pool/main/a/arts/arts_1.3.2-1_all.deb
arts_1.3.2.orig.tar.gz
  to pool/main/a/arts/arts_1.3.2.orig.tar.gz
libarts1-dev_1.3.2-1_i386.deb
  to pool/main/a/arts/libarts1-dev_1.3.2-1_i386.deb
libarts1_1.3.2-1_i386.deb
  to pool/main/a/arts/libarts1_1.3.2-1_i386.deb
libartsc0-dev_1.3.2-1_i386.deb
  to pool/main/a/arts/libartsc0-dev_1.3.2-1_i386.deb
libartsc0_1.3.2-1_i386.deb
  to pool/main/a/arts/libartsc0_1.3.2-1_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christopher Martin <email address hidden> (supplier of updated arts package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 6 Dec 2004 12:26:16 -0500
Source: arts
Binary: libarts1 libarts1-dev libartsc0-dev libartsc0 arts
Architecture: source i386 all
Version: 1.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers <email address hidden>
Changed-By: Christopher Martin <email address hidden>
Description:
 arts - Analog Realtime Synthesizer (aRts) metapackage
 libarts1 - aRts Sound system
 libarts1-dev - aRts Sound system (development files)
 libartsc0 - aRts Sound system C support library
 libartsc0-dev - aRts Sound system C support library (development files)
Closes: 266760
Changes:
 arts (1.3.2-1) unstable; urgency=medium
 .
   * New upstream release.
   * No longer set suid on artswrapper. Works around a 2.4 kernel lockup bug,
     but disables realtime priority. Added a README.Debian, explaining the
     change and how to cope with it, and reverse it.
     (Closes: #266760)
   * Add Suggests on akode, which often suffices in place of realtime priority.
Files:
 b2a657fd78fcc269293ab8ee546e8b50 973 libs optional arts_1.3.2-1.dsc
 7dc40742d9853845bd306130d1c0bc3a 1274578 libs optional arts_1.3.2.orig.tar.gz
 d46ee1a07c4d4bb7cf4b2c38ed30e993 31709 libs optional arts_1.3.2-1.diff.gz
 8ec6f2d66541a3c97566fce00b063a27 1145742 libs optional libarts1_1.3.2-1_i386.deb
 fb606f510b30d7b09e2e143f004ccc66 175070 libdevel optional libarts1-dev_1.3.2-1_i386.deb
 35b08ac91cf8130caeeb34f6e757e06a 12898 libs optional libartsc0_1.3.2-1_i386.deb
 ec9cc59790ae3a84f6fa3cda1a079b04 8548 libdevel optional libartsc0-dev_1.3.2-1_i386.deb
 5584858c1...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 7 Dec 2004 19:08:50 +0100
From: Adeodato Simó <email address hidden>
To: <email address hidden>
Subject: reopening 266760, tagging 266760

# Automatically generated email from bts, devscripts version 2.8.5
reopen 266760
tags 266760 = sarge pending

Revision history for this message
In , Dato Simó (dato) wrote : more bugs closed by the KDE 3.3 tranisition

  The following bugs against KDE packages were tagged sarge. I've done a
  quick review of them and all can be closed now that the 3.3 transition
  is finished.

  To submitters: the KDE 3.3 packages will be available in your mirror
  in about 12 hours.

  Thanks to all the people that made the transition possible.

#282462: kaboodle: babble when playing MP3 files
#280974: mpeglib: Old bug #245192 never got fixed.
#266760: kde: system freezes at log-out when using kernel 2.4 and arts over alsa

#274989: libsmokeqt-dev depends on libsmokeqt1, but doesn't have a dependency

#288251: build dependencies for kdelibs fails

#282925: Konqueror crashes randomly
#282418: kaudiocreator: fails on extracting tracks
#281393: Sarge-konqueror performance-option "Minimize memory-usage: Always" doesn't work.
#274911: kate-plugins: Does not parse entire XML tree when file is opened
#248157: kdelibs: Selection in different selection dialogs is "jumpy"

#288185: juk: crashes with gstreamer output, stops play with arts output

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

As an adolescent I aspired to lasting fame, I craved factual certainty,
and I thirsted for a meaningful vision of human life -- so I became a
scientist. This is like becoming an archbishop so you can meet girls.
                -- Matt Cartmill

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Tue, 4 Jan 2005 10:15:47 +0100
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: more bugs closed by the KDE 3.3 tranisition

  The following bugs against KDE packages were tagged sarge. I've done a
  quick review of them and all can be closed now that the 3.3 transition
  is finished.

  To submitters: the KDE 3.3 packages will be available in your mirror
  in about 12 hours.

  Thanks to all the people that made the transition possible.

#282462: kaboodle: babble when playing MP3 files
#280974: mpeglib: Old bug #245192 never got fixed.
#266760: kde: system freezes at log-out when using kernel 2.4 and arts over alsa

#274989: libsmokeqt-dev depends on libsmokeqt1, but doesn't have a dependency

#288251: build dependencies for kdelibs fails

#282925: Konqueror crashes randomly
#282418: kaudiocreator: fails on extracting tracks
#281393: Sarge-konqueror performance-option "Minimize memory-usage: Always" doesn't work.
#274911: kate-plugins: Does not parse entire XML tree when file is opened
#248157: kdelibs: Selection in different selection dialogs is "jumpy"

#288185: juk: crashes with gstreamer output, stops play with arts output

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

As an adolescent I aspired to lasting fame, I craved factual certainty,
and I thirsted for a meaningful vision of human life -- so I became a
scientist. This is like becoming an archbishop so you can meet girls.
                -- Matt Cartmill

Changed in arts:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.