Bug 101308 - mythtv: KDE session managemant attempts to restart mythbackend
|
Bug#:
101308
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: media-tv@gentoo.org
|
Reported By: makomk@lycos.co.uk
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: mythtv: KDE session managemant attempts to restart mythbackend
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-08-04 02:34 0000
|
This is a bizzare one. If I restart mythbackend from a terminal within KDE
using
"/etc/init.d/mythbackend restart", it seems to use KDE session management
somehow. After logging off, the next time I start KDE, I get a prompt for a
root
password so that it can restart mythbackend with some sort of "-session"
parameter. The mythbackend that I started earlier is (correctly) still running.
This has happened to me several times (though I would like to repeat it under
more controlled conditions)
Reproducible: Didn't try
Steps to Reproduce:
1. Start KDE
2. Su to root and run "/etc/init.d/mythbackend restart"
3. Exit KDE using the logout button
4. Restart KDE.
Actual Results:
KDE su popped up a dialog box asking for a password to run mythbackend with
root
priviledges.
Expected Results:
KDE session management should have ignored mythbackend - it's a daemon and has
no GUI
Using KDE 3.4 and mythtv 0.18.1-r1. Mythbackend is running as root.
Okay, it looks like I was wrong. It seems that (if I start mythbackend in the
way I specified) it is terminated when I log out of KDE.
Also, since I initially filed the bug, I've succesfully reproduced it using the
steps indicated. (I did add a comment to this effect, but it appears to have got
lost.)
By the way, I'm using QT 3.3.4-r3.
Created an attachment (id=65743) [details]
Modified /etc/init.d/mythbackend
It turns out there's a fairly simple workaround/fix for this. The attached
/etc/init.d/mythbackend unsets DISPLAY and SESSION_MANAGEMENT (the former may
be unneccesary, but it does no harm). I should've figured this out earlier.
This isn't a perfect fix; mythbackend shouldn't be using session management in
teh first place. It seems to work though.
