Bug 17641

Summary: system tray regression under KDE4 since intel driver update 2.4.2 (EXA/MigrationHeuristic)
Product: xorg Reporter: Fathi Boudra <fabo>
Component: Driver/intelAssignee: Gordon Jin <gordon.jin>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: 7.4 (2008.09)   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
broken systray
none
xorg configuration
none
xorg log none

Description Fathi Boudra 2008-09-18 07:03:19 UTC
Since I have updated to 2.4.2, the system tray under KDE4 is broken.
Comment 1 Fathi Boudra 2008-09-18 07:04:47 UTC
Created attachment 18975 [details]
broken systray
Comment 2 Julien Cristau 2008-09-18 07:09:14 UTC
On Thu, Sep 18, 2008 at 07:03:22 -0700, bugzilla-daemon@freedesktop.org wrote:

> Since I have updated to 2.4.2, the system tray under KDE4 is broken.
> 
What hardware, what previous version worked, using what X server
version, etc?
See http://intellinuxgraphics.org/how_to_report_bug.html
Also try switching the EXANoComposite and/or AccelMethod options.
Comment 3 Fathi Boudra 2008-09-18 07:20:25 UTC
Created attachment 18976 [details]
xorg configuration
Comment 4 Fathi Boudra 2008-09-18 07:20:51 UTC
Created attachment 18977 [details]
xorg log
Comment 5 Fathi Boudra 2008-09-18 08:18:56 UTC
Hardware: Dell D620 laptop with i945
previous working version: 2.3.2
X.Org X Server: 1.5.0
Comment 6 Fathi Boudra 2008-09-18 08:33:40 UTC
EXANoComposite does nothing.
Switching to XAA works: the systray isn't broken anymore.

Note: I have commented CacheLines option to be able to start X server.
Comment 7 Fathi Boudra 2008-09-18 08:59:54 UTC
Removing MigrationHeuristic option with EXA works too
Comment 8 Julien Cristau 2008-09-18 09:04:28 UTC

*** This bug has been marked as a duplicate of bug 16773 ***
Comment 9 Fathi Boudra 2008-09-18 09:05:31 UTC

*** This bug has been marked as a duplicate of bug 16773 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.