Bug 555885 - gnome-panel bouncing/empty only with dual screen (and takes 100% CPU)
Summary: gnome-panel bouncing/empty only with dual screen (and takes 100% CPU)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-15 20:25 UTC by Yaniv Kaul
Modified: 2013-07-04 01:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-04 05:17:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg log file (130.35 KB, application/octet-stream)
2010-01-15 20:26 UTC, Yaniv Kaul
no flags Details

Description Yaniv Kaul 2010-01-15 20:25:33 UTC
Description of problem:
My Leonvo T500 is also connected to a 24" Samsung SyncMaster 2494HS display. If I boot in this configuration, I do not get the gnome panel. At most, I get some empty panel which is hoping (up and down!) with no content.
If I boot up without the display connected, and connect it later, everything seems to be fine - the panel is on the laptop's LCD and the display is extended to the 2nd display.

Attaching xorg.0 log and a pstack from the stuck gnome-panel application (which at that point seem to be taking 100% CPU).

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Yaniv Kaul 2010-01-15 20:26:15 UTC
Created attachment 384700 [details]
Xorg log file

Comment 2 Yaniv Kaul 2010-01-15 20:27:09 UTC
Not a lot in the pstack (missing symbols?):
#1  0x000000340e63b705 in g_idle_add_full () from /lib64/libglib-2.0.so.0
#2  0x00000039552b9d73 in ?? ()
#3  0x0000000001478550 in ?? ()
#4  0x00000000014e6100 in ?? ()
#5  0x00000000014e6100 in ?? ()
#6  0x0000000000000001 in ?? ()
#7  0x00007fffc9af2688 in ?? ()
#8  0x00007fffc9af2680 in ?? ()
#9  0x0000000000000000 in ?? ()

Comment 3 Bug Zapper 2010-11-04 00:52:04 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.