Bug 82998 - atrsd does not exit after kde application closed when run remotely via ssh
Summary: atrsd does not exit after kde application closed when run remotely via ssh
Status: CLOSED UNMAINTAINED
Alias: None
Product: arts
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Stefan Westerfeld
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-07 17:25 UTC by Tim Wunder
Modified: 2008-11-19 23:37 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Wunder 2004-06-07 17:25:56 UTC
Version:            (using KDE KDE 3.2.2)
Installed from:    Unspecified Unix
OS:                Linux

After logging into linux (Fedora Core 1 and Fedora Core 2), running a KDE 3.2.2 app that uses artsd (like kmail), and then exiting the KDE app results in an artsd instance remaining that doesn't quit. This results in an unclean exit from the ssh session unless artsd is manually killed.

Using KDE 3.2.2 on Fedora Core 2 as supplied by kde-redhat.sf.net.

Steps to reproduce.
Login to linux via ssh with X forwarding enabled.
Start a KDE app that uses arts, like kmail.
Exit the kde app.
wait...
execute 'ps -u <your user name>' from the shell, notice that artsd is still running
Try to exit from the shell by typing 'exit' or 'logout' or <Ctrl-D>.
ssh session hangs and must be killed.

If you 'kill <artsd PID>' prior to exiting, ssh terminates normally.
Comment 1 Matt Rogers 2008-11-19 23:37:47 UTC
Arts is no longer developed and has been unmaintained for quite some time - more than 2 years. With phonon as the replacement for arts in KDE4, we're closing out all the arts bugs in Bugzilla since there is no chance of them being fixed.

Thanks