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 2824

Summary: [wishlist] launch sysguard when system monitor applet is clicked by default
Product: TDE Reporter: wofgdkncxojef
Component: tdeadminAssignee: Timothy Pearson <kb9vqf>
Status: NEW ---    
Severity: wishlist CC: bugwatch, michele.calgaro, wofgdkncxojef
Priority: P5    
Version: R14.1.x [Trinity]   
Hardware: All   
OS: All   
Compiler Version: TDE Version String:
Application Version: Application Name: system monitor applet
Bug Depends on:    
Bug Blocks: 2967    

Description wofgdkncxojef 2017-08-27 07:11:18 CDT
This is a little feature from KDE4.
Launching sysguard when clicking the system monitor applet.
It's really trivial, the user alredy can do it.
It would be nice to be the default.
Comment 1 Michele Calgaro 2018-05-21 08:31:45 CDT
Moved to R14.0.6 bug list since R14.0.5 bug list is already frozen.
Comment 2 wofgdkncxojef 2018-05-21 11:32:08 CDT
this simply changes the default config.
Users can already do it themselves.
This is why i added it in the 14.0.5 list
Comment 3 Michele Calgaro 2018-05-22 07:17:37 CDT
Sure, nothing against it, but we had already frozen R14.0.5 bug list. 
At some point a line needs to be drawn, and in the past we already when through the "let's move the line a bit more and then more and then more" thing, result in continuous delays. Anyhow if you use the preliminary stable build from Slavek, you will get the fix as soon as the bug is fixed, no need to wait for the next official release.
Hope this clear things a bit :-)
Comment 4 wofgdkncxojef 2018-05-22 11:37:54 CDT
I wasn't complaining
And were was it written that the list was frozen?
Comment 5 Michele Calgaro 2018-05-22 11:47:54 CDT
> And were was it written that the list was frozen?
Agreed, we didn't annouce that officially I think. Our fault :-(
BTW thanks for the continuous support, keep it up.
Comment 6 Michele Calgaro 2018-07-24 09:44:40 CDT
Moved to R14.1.0.
This bug requires a change in the Sensor Display API, meaning it does not qualify for R14.0.x branch.