Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 161092 - Panel crashes and repeatedly restarts
Panel crashes and repeatedly restarts
Product: Fedora
Classification: Fedora
Component: gnome-panel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mark McLoughlin
Depends On:
  Show dependency treegraph
Reported: 2005-06-20 11:16 EDT by Michael Stevens
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-11 11:10:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Stevens 2005-06-20 11:16:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4

Description of problem:
Panel crashes and attempts to restart.

Restarts, get error message saying "I've detected a panel already running, and will now exit.". Click Ok, message disappears briefly and reappears. This appears to go on forever.

Panel only appears to restart once.

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

How reproducible:
Couldn't Reproduce

Steps to Reproduce:
Have seen problem twice during normal desktop use, unable to reproduce.

Actual Results:  Panel crashed and kept trying to restart.

Expected Results:  Panel should not have crashed, should only have restarted once.

Additional info:
Comment 1 Mark McLoughlin 2005-06-27 12:30:24 EDT
Thanks for the bug report. Without a stack trace from the crash it is very hard
to determine what caused the crash. Please see
http://fedoraproject.org/wiki/StackTraces for more information about getting a
useful stack trace.
Comment 2 Mark McLoughlin 2005-07-11 11:10:30 EDT

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