Bug 239889 - gnome-panel restarts when trying to set properties on second screen
Summary: gnome-panel restarts when trying to set properties on second screen
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel   
(Show other bugs)
Version: rawhide
Hardware: i686 Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-05-11 22:32 UTC by G.Wolfe Woodbury
Modified: 2008-03-27 16:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-03-27 16:31:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description G.Wolfe Woodbury 2007-05-11 22:32:59 UTC
Description of problem:
   gnome-panel crashes with lots of (unreadable) notices and restarts itself
when trying to set properties (background color) on second screen of a
dual head setup.

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

How reproducible:
consistently, always

Steps to Reproduce:
1. F7t4 install
2. dual head screen setup
3. right-click top panel on second screen and select "properties"
4. select "background" tab in properties box.
Actual results:
    gnome-panel crashes and restarts (on both screens of course)

Expected results:
    being able to set background color on panel bar on second screen

Additional info:

Celeron (Coppermine) CPU @ 600MHz       MSI Motherboard
mobo video: Trident Cyberblade/i1
2nd  video: ATI (Mach 64) Rage card             256 MB RAM

Xorg.0.log shows no errors after crash
no traces of crash in any logs or messages
lots of warning boxes flash by so fast that the contents have no time to display
error messages on screens

setting properties on screen0 works correctly

Comment 1 G.Wolfe Woodbury 2008-03-27 16:31:17 UTC
This is so old, I'm closing it as UPSTREAM, It has been fixed upstream

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