Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 230543 - Backtrace was generated from '/usr/bin/gnome-panel'
Summary: Backtrace was generated from '/usr/bin/gnome-panel'
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 6
Hardware: athlon
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-01 12:47 UTC by Bernhard Fastenrath
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-03-18 18:40:43 UTC

Attachments (Terms of Use)
Backtrace was generated from '/usr/bin/gnome-panel' (deleted)
2007-03-01 12:47 UTC, Bernhard Fastenrath
no flags Details

Description Bernhard Fastenrath 2007-03-01 12:47:29 UTC
Description of problem:
Backtrace was generated from '/usr/bin/gnome-panel'

Version-Release number of selected component (if applicable):
Name        : gnome-panel                  Relocations: (not relocatable)
Version     : 2.16.3                            Vendor: Red Hat, Inc.
Release     : 2.fc6                         Build Date: Fri 09 Feb 2007 04:30:21

How reproducible:
cause unknown

Actual results:
Bug feedback dialog requests sending in the attached backtrace.

Expected results:

Comment 1 Bernhard Fastenrath 2007-03-01 12:47:30 UTC
Created attachment 149015 [details]
Backtrace was generated from '/usr/bin/gnome-panel'

Comment 2 Ray Strode [halfline] 2008-03-18 18:40:43 UTC

We no longer support Fedora Core 6 and I am currently trying to get my open bug
count down to a more manageable state.  I'm going to close this bug as WONTFIX.
 If this issue is still a concern for you, would you mind trying to reproduce on
a supported version of Fedora and reopening?

(this is a mass message)

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