Bug#266760: KDE Logout Hang because realtime artsd: a followup

[Adeodato Simó <asp16@alu.ua.es>]

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