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 1028 - [Regression] Desktop background programs are reinvoked on every viewport switch
Summary: [Regression] Desktop background programs are reinvoked on every viewport switch
Status: RESOLVED WONTFIX
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.x [Trinity]
Hardware: All Linux
: P5 minor
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2012-06-11 07:33 CDT by Nix
Modified: 2018-07-29 01:52 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nix 2012-06-11 07:33:49 CDT 
I'm using fvwm 2.6 with Trinity from git, and have a regression regarding desktop background programs. In KDE 3.5.10, my background program is reinvoked as often as I requested in the background advanced dialog, and no more. In Trinity, the background program is reinvoked whenever fvwm switches viewports, even if it's just a small shift of, say, 10% of the screen (as triggered by the EdgeScroll option and ramming the mouse into the screen edge). fvwm sends a NET_DESKTOP_VIEWPORT client message whenever this happens: possibly Trinity is triggering a background refresh on this. It probably shouldn't: KDE 3.5 didn't and I don't like having ten xplanets kick up in parallel because I navigate across ten viewports en route from one to the other (I have viewport navigation bound to keys, so this happens a lot).
Comment 1 Michele Calgaro 2018-07-29 01:52:59 CDT 
TDE used in with tdm seems to work fine. Closing the bug for non-strctly related to TDE, long inactivity and non clear description.
Reopen if you can still replicate this bug and provide a meaningful description on how to reproduce it