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 2224 - [Regression] Menu hightlighting glitch
Summary: [Regression] Menu hightlighting glitch
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2014-12-01 18:23 CST by Kristopher
Modified: 2018-05-27 10:49 CDT (History)
3 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 Kristopher 2014-12-01 18:23:10 CST 
Starting about two weeks ago, sliding the pointer along menus in TDE applications reveals a bit of lag in the highlighting. As the previously hightlighted item un-highlights, the item to be hightlighted disappears momentarily, then reappears, then hightlights.
Comment 1 Kristopher 2014-12-01 18:34:20 CST 
This bug appears completely at random, and only when changing Control Center -> Appearance & Themes -> Styles or Control Center -> Appearance & Themes -> Colors (any style or color theme will do), and rebooting (*not* relogging) will fix until, possibly, the next change to COlors or Styles.
Comment 2 Timothy Pearson 2014-12-01 19:40:50 CST 
If you disable the TDE composition manager (Window Behaviour-->Translucency) does this issue persist?
Comment 3 Kristopher 2014-12-01 19:50:08 CST 
(In reply to Timothy Pearson from comment #2)
> If you disable the TDE composition manager (Window Behaviour-->Translucency)
> does this issue persist?

Yes. It is a little quicker to happen with translucency disabled, but still very much noticible.
Comment 4 Timothy Pearson 2014-12-01 20:51:04 CST 
Interesting.  I haven't seen this at all and until it does show up on one of my systems there isn't much I can do.

I assume this is with QtCurve?  Does it appear with Plastik or a different widget style?

Thanks!
Comment 5 Kristopher 2014-12-01 20:57:35 CST 
(In reply to Timothy Pearson from comment #4)
> Interesting.  I haven't seen this at all and until it does show up on one of
> my systems there isn't much I can do.
> 
> I assume this is with QtCurve?  Does it appear with Plastik or a different
> widget style?
> 
> Thanks!

Comment 1 contains the answer: this bug appears at random when I switch to any color theme or style (regardless of whether it's QtCurve, Plastik, etc.).
Comment 6 Timothy Pearson 2014-12-01 21:32:25 CST 
(In reply to Kristopher from comment #5)
> (In reply to Timothy Pearson from comment #4)
> > Interesting.  I haven't seen this at all and until it does show up on one of
> > my systems there isn't much I can do.
> > 
> > I assume this is with QtCurve?  Does it appear with Plastik or a different
> > widget style?
> > 
> > Thanks!
> 
> Comment 1 contains the answer: this bug appears at random when I switch to
> any color theme or style (regardless of whether it's QtCurve, Plastik, etc.).

I had misunderstood Comment 1, sorry.

So this appears only when changing the color theme or style, and when it does appear it takes a reboot to clear.  Got it. :-)
Comment 7 Timothy Pearson 2014-12-01 21:34:06 CST 
(In reply to Timothy Pearson from comment #6)
> (In reply to Kristopher from comment #5)
> > (In reply to Timothy Pearson from comment #4)
> > > Interesting.  I haven't seen this at all and until it does show up on one of
> > > my systems there isn't much I can do.
> > > 
> > > I assume this is with QtCurve?  Does it appear with Plastik or a different
> > > widget style?
> > > 
> > > Thanks!
> > 
> > Comment 1 contains the answer: this bug appears at random when I switch to
> > any color theme or style (regardless of whether it's QtCurve, Plastik, etc.).
> 
> I had misunderstood Comment 1, sorry.
> 
> So this appears only when changing the color theme or style, and when it
> does appear it takes a reboot to clear.  Got it. :-)

Oh and since logging out and in does not fix the bug my initial guess would be something being changed in the context of Xorg server itself (e.g. allocated resources not being freed), as that is the only graphical software not re-initialized across a logout/login cycle.
Comment 8 Kristopher 2014-12-02 08:12:53 CST 
(In reply to Timothy Pearson from comment #7)
> (In reply to Timothy Pearson from comment #6)
> > (In reply to Kristopher from comment #5)
> > > (In reply to Timothy Pearson from comment #4)
> > > > Interesting.  I haven't seen this at all and until it does show up on one of
> > > > my systems there isn't much I can do.
> > > > 
> > > > I assume this is with QtCurve?  Does it appear with Plastik or a different
> > > > widget style?
> > > > 
> > > > Thanks!
> > > 
> > > Comment 1 contains the answer: this bug appears at random when I switch to
> > > any color theme or style (regardless of whether it's QtCurve, Plastik, etc.).
> > 
> > I had misunderstood Comment 1, sorry.
> > 
> > So this appears only when changing the color theme or style, and when it
> > does appear it takes a reboot to clear.  Got it. :-)
> 
> Oh and since logging out and in does not fix the bug my initial guess would
> be something being changed in the context of Xorg server itself (e.g.
> allocated resources not being freed), as that is the only graphical software
> not re-initialized across a logout/login cycle.

Next time it happens, I'll tell TDM to restart Xorg to see if that fixes it without rebooting. Though personally, I doubt Xorg is the issue since this was not present in 3.5.13.2 and older, nor was it present for a short time after installing the nightlies, and I'm using exactly the same version, packages, and configuration for Xorg that I used back then.

Also, if it would be helpful, I can record a video of it happening next time it occurs so you can see the bug it in action.
Comment 9 Timothy Pearson 2014-12-02 10:14:01 CST 
(In reply to Kristopher from comment #8)
> (In reply to Timothy Pearson from comment #7)
> > (In reply to Timothy Pearson from comment #6)
> > > (In reply to Kristopher from comment #5)
> > > > (In reply to Timothy Pearson from comment #4)
> > > > > Interesting.  I haven't seen this at all and until it does show up on one of
> > > > > my systems there isn't much I can do.
> > > > > 
> > > > > I assume this is with QtCurve?  Does it appear with Plastik or a different
> > > > > widget style?
> > > > > 
> > > > > Thanks!
> > > > 
> > > > Comment 1 contains the answer: this bug appears at random when I switch to
> > > > any color theme or style (regardless of whether it's QtCurve, Plastik, etc.).
> > > 
> > > I had misunderstood Comment 1, sorry.
> > > 
> > > So this appears only when changing the color theme or style, and when it
> > > does appear it takes a reboot to clear.  Got it. :-)
> > 
> > Oh and since logging out and in does not fix the bug my initial guess would
> > be something being changed in the context of Xorg server itself (e.g.
> > allocated resources not being freed), as that is the only graphical software
> > not re-initialized across a logout/login cycle.
> 
> Next time it happens, I'll tell TDM to restart Xorg to see if that fixes it
> without rebooting. Though personally, I doubt Xorg is the issue since this
> was not present in 3.5.13.2 and older, nor was it present for a short time
> after installing the nightlies, and I'm using exactly the same version,
> packages, and configuration for Xorg that I used back then.

It wouldn't be Xorg's fault per se; this comment was simply a hint for myself or anyone else to look for leaked resources or misconfiguration that could persist across TDE restarts within the same X11 session.