at least two more people have this problem, see:

http://lists.debian.org/debian-kde/2004/08/msg00298.html

regards,

Francisco Vera

I have had this problem as well using Debian sid, with the 2.4.26 kernel using ALSA. I have no problems on the same machine using Gentoo with a 2.6 series kernel. I have found on my debian system, if I change the hardware settings in control center from "Autodetect" to "Advanced Linux Sound Architecture", the system no longer hangs up on logout. However, in doing so, while the test sound works, the normal system notification sounds (startup and logout) no longer play. I have also chosen "OSS" (I have the compatibility built into alsa) and again, the test sound under "sound system - General" plays, notifications appear absent. Sound works fine in all other non-KDE applications.

Jason Collison

This might have something to do with Bug #86426: http://bugs.kde.org/show_bug.cgi?id=86426

Well, on my machine I'm running kernel 2.4.26 with alsa+oss + soundblaster (emuk10k1 driver).

I have switched the hardware settings to ALSA (not using autodetect), but this doesn't help. Other options (e.g. realtime,...) are set as usual.

After logging out I hear the "system notification logout sound" and see the black screen ;-) ... and doing a reboot.

While beeing logged in to kde 3.3.0 I have sound, with both settings (using autodetect or using alsa directly).

Anyway, I don't think this bug has to do with alsa and the kernel directly. (like mentioned in Bug #86426: http://bugs.kde.org/show_bug.cgi?id=86426)

The last days I set up a Terminalserver (kernel 2.4.27). I have the same problems there, but the machine doesn't have any soundcard installed or alsa driver loaded.

Even setting the hardware settings to "Use no sound" (I can't remember the exact label of the dropdown list now) doesn't help.

I installed it using the Slackware 10 packages. I had the same thing happen. Its not just Gentoo.

right now, only disabling the whole kde soundsystem (option in controlcenter) works for me. But life is much better with sound ;-(

Out of curiousity, how many people who have this problem have emu10k1-based hardware? Thorsten, have you tried turning off Sound Server Suspend if Idle?

I am using the emu10k1, is everyone else?

OK I tried something and it works. I uninstalled all of kde except for arts-1.2.3 that came with Slackware 10. I then installed all of kde-3.3 from the packges provided on kde.org and now it works just fine. Sound works, no freezing on logout. Not sure what is going on but its a problem with the new version of arts that comes with kde-3.3. 

I've got the same problem here with arts-1.2.3/KDE 3.2. Less often, but the same problem, and definitely connected to arts. Unfortunately, I can't reliably test what settings have caused it and what haven't.

Today I just finished compiling qt-3.3.3/arts-1.3.0/kde-3.3.0/koffice-1.3.2 on a slackware 10 computer which has a VIA 82xx alsa soundcard and I'm having the exact same problem except that it also happens if I choose ALSA as the sound driver. With OSS it works OK.

Today I just finished compiling qt-3.3.3/arts-1.3.0/kde-3.3.0/koffice-1.3.2 on a slackware 10 computer which has a VIA 82xx alsa soundcard and I'm having the exact same problem except that it also happens if I choose ALSA as the sound driver. With OSS it works OK.

To everyone:
Do you run arts with realtime priority enabled?
Does it help if you turn it off? Does arts crash on exit if you turn it off? (Instead of hanging up your system)

I run it realtime priority enabled. I am unable to turn this off as this is a 4-year-old system, and performance suffers unacceptably with it turned off.

Hey, that solved it, at least for now.

If you write "killall artsd" in a konsole does artsd also crash?
If it doesnt you can also try to run artsshell and issue the command "terminate". 

What I would really like is backtrace of the crash or where artsd locks up.

Allan: So far, my solution for dealing with this has been:

1) Run killall artsd in konsole or KDesktop Run Command window.
2) Log out /immediately/.

When doing this, I've not had artsd lock up on me once. It appears to respect the killall, and then doesn't restart by the time I've logged out.

Hi,
I have had the same problems. I have done two things (after many other trials):
At first I disabled the KDE sound system, then I replaced my personal /etc/kde3/kdm/kdmrc with the maintainers version from the package (after lockout, so it is not overwritten by KDE).
Then suddenly all my problems were gone. After this I re-enabled the sound KDE sound system and the problems were still away. So, at this point, I can not determine what was the real reason for this terrible lookout problem. But I think it has to do with the KDE sound system, because I did not have the problem at every lockout (Sound System Auto suspend was 4 seconds). May be sometimes the auto suspend time was reached ?

[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

*** This bug has been marked as a duplicate of 86426 ***

I experienced a similar problem after building and installing kde-multimedia3.3.0
the artsserver ended up going into a loop of stopping & restarting during the initialization process.  I nuked & rebuilt arts and kde to get the gui back up, but the sound server is still hosed.  Ironically I can still use XMMS within Kde, as it calls Alsa.  Any attempt to use Arts based software locks the system hard, (no keyboard)-hard reboot/fsck and all that.
The following is the backtrace from the arts failure during startup.

[New Thread 16384 (LWP 10761)]
[KCrash handler]
#4  0x406d4ac1 in kill () from /usr/lib/./libc.so.6
#5  0x405749ed in pthread_kill () from /lib/libpthread.so.0
#6  0x40574d0b in raise () from /lib/libpthread.so.0
#7  0x406d46fa in raise () from /usr/lib/./libc.so.6
#8  0x406d6127 in abort () from /usr/lib/./libc.so.6
#9  0x406cdd6a in __assert_fail () from /usr/lib/./libc.so.6
#10 0x40361feb in Arts::Object_base::_create(std::string const&) ()
   from /opt/kde/lib/libmcop.so.1
#11 0x0805ee8a in Arts::SimpleSoundServer_impl::SimpleSoundServer_impl() ()
#12 0x0805aa18 in Arts::SoundServer_impl::SoundServer_impl() ()
#13 0x080549a2 in Arts::SoundServerV2_impl::SoundServerV2_impl() ()
#14 0x0805b07b in SoundServerV2_impl_Factory::createInstance() ()
#15 0x40368d17 in Arts::ObjectManager::create(std::string const&) ()
   from /opt/kde/lib/libmcop.so.1
#16 0x40056c55 in Arts::SoundServerV2_base::_create(std::string const&) ()
   from /opt/kde/lib/libsoundserver_idl.so.1
#17 0x40059c61 in Arts::SoundServerV2::_Creator() ()
   from /opt/kde/lib/libsoundserver_idl.so.1
#18 0x080643a2 in main ()
#19 0x406c0d06 in __libc_start_main () from /usr/lib/./libc.so.6

I have experienced exactly the same problem. I can confirm that if I disable the sound system in the KDE control panel the problem disappears. All other users are OK.

I use a 2.6 kernel and got the problem when upgrading to KDE3.3.0

I run Gentoo Linux

Here is my emerge info:

Portage 2.0.50-r11 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.4.26-gentoo-r9)
=================================================================
System uname: 2.4.26-gentoo-r9 i686 AMD Athlon(tm) XP 1800+
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp.linux.ee/pub/gentoo/distfiles/ ftp://gentoo.inode.at/source/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X aalib alsa apache2 apm arts avi berkdb bitmap-fonts cdr cjk crypt cups dga doc dvd dvdr emacs encode ethereal evo f77 fbcon foomaticdb ftp gd gdbm ggi gif gphoto2 gpm gstreamer gtk gtk2 imap imlib innodb ipv6 java jikes jpeg kde kerberos ldap libg++ libwww linguas_en_US linguas_hu linguas_sv mad mikmod mms motif mozilla mpeg mysql mysqli nas ncurses nls oggvorbis opengl oss pam pda pdflib perl php png python qt quicktime readline samba scanner sdl slang spell sse ssl svga tcltktcpd tiff truetype usb x86 xine xml2 xmms xprint xv zlib"

Same type of problem -

   but not only with KDE !

Please see:

    https://bugs.freedesktop.org/show_bug.cgi?id=2932#c12 ff.

Kind regards,
Manfred