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 880

Summary: kompmgr running without being enabled.
Product: TDE Reporter: Calvin Morrison <mutantturkey>
Component: tdebaseAssignee: Timothy Pearson <kb9vqf>
Status: RESOLVED WORKSFORME    
Severity: normal CC: bugwatch, michele.calgaro
Priority: P5    
Version: 3.5.13.x [Trinity]   
Hardware: All   
OS: Other   
Compiler Version: TDE Version String:
Application Version: Application Name:
Attachments: kwinrc

Description Calvin Morrison 2012-02-28 12:49:14 CST
kompmgr continues to run even when not set. It is rather annoying to be wasting 
my cpu and running in the background for no purpose!

I have it disabled in settings -> Desktop -> Window Behavior -> Transluceny

Attached is my kwinrc

Calvin
Comment 1 Calvin Morrison 2012-02-28 12:49:25 CST
Created attachment 432 [details]
kwinrc
Comment 2 Darrell 2012-02-28 14:10:12 CST
Does not help you directly, but I have Desktop -> Window Behavior -> Transluceny disabled as well and do not have kcompmgr running.

I do receive an incorrect stdout/stderr message of reading '/home/users/tester/.kompmgr.pid' as kompmgr pidfile (bug report 645), but that is all.

I'm running from GIT, not 3.5.13.
Comment 3 Darrell 2012-03-01 23:42:43 CST
I don't know whether this helps, but kompmgr creates two files in $HOME:

.kompmgr.available
.kompmgr.pid

Possibly delete those files and see what happens?
Comment 4 Calvin Morrison 2012-10-10 12:09:43 CDT
Still a problem for me. Can't get it to stop running no matter what options I try
Comment 5 Darrell 2012-10-10 14:00:01 CDT
What happens when using a temporary fresh profile?
Comment 6 Michele Calgaro 2014-04-12 08:01:38 CDT
Is this bug still valid?
Comment 7 Michele Calgaro 2018-07-28 09:20:01 CDT
Closing for too long inactivity.
Feel free to reopen if the problem is still happennig and provide detailed instructions.