By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 149 - KDED Media Manager always comes up stopped after reboot
Summary: KDED Media Manager always comes up stopped after reboot
Status: RESOLVED INVALID
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: 3.5.10
Hardware: i386 Kubuntu Karmic
: P3 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2010-01-27 11:15 CST by Phil Salkie
Modified: 2012-10-19 15:40 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name: KDED Media Manager


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Phil Salkie 2010-01-27 11:15:36 CST
Upgraded to Karmic from Jaunty - on several different machines, KDED Media Manager comes up in "Stopped" mode after a reboot, regardless of the settings on the "Startup Services" panel of System Settings "Service Manager" page.
It starts fine if you manually select it and click the "Start" button, and stays running from then on, until the next reboot.  Not sure if the problem is only on upgraded systems, or if it's on new installs as well.
Comment 1 Timothy Pearson 2010-01-27 12:07:41 CST
This is probably because that service was not yet converted to Upstart, and there is a known Karmic bug (not in KDE3/Trinity) that prevents non-Upstart services from starting automatically.
Comment 2 Timothy Pearson 2010-03-26 02:38:12 CDT
I don't seem to have this problem on my systems...maybe it is because of something weird in your upgrade?

After digging deeper, it seems that the KDED Media Manager is not an init.d/Upstart service after all, so please ignore my previous comment.  This is a KDE-only issue unfortunately.

Have you tried creating a new user and seeing if the issue persists when you log in under that new username?
Comment 3 Timothy Pearson 2010-04-09 12:31:30 CDT
Closing due to inactivity.  If you find you still have this problem in Lucid or above, please reopen this bug report.