Bug 711388 - [abrt] gnome-panel-2.32.0.2-2.fc14: on_factory_appeared: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-panel-2.32.0.2-2.fc14: on_factory_appeared: Process /usr/bin/gno...
Keywords:
Status: CLOSED DUPLICATE of bug 659899
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7658325cd1b3003d24fa9b0140c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-07 11:09 UTC by Mike Stefanelli
Modified: 2012-03-20 15:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 15:57:20 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (21.02 KB, text/plain)
2011-06-07 11:09 UTC, Mike Stefanelli 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Mike Stefanelli 2011-06-07 11:09:47 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 21525 bytes
cmdline: gnome-panel
comment: sytem was starting up
component: gnome-panel
Attached file: coredump, 37711872 bytes
crash_function: on_factory_appeared
executable: /usr/bin/gnome-panel
kernel: 2.6.35.13-91.fc14.i686.PAE
package: gnome-panel-2.32.0.2-2.fc14
rating: 4
reason: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1307444849
uid: 500

How to reproduce
-----
1.crashed on boot up
2.
3.
Comment 1 Mike Stefanelli 2011-06-07 11:09:49 UTC 
Created attachment 503449 [details]
File: backtrace
Comment 2 Mike Stefanelli 2011-11-04 13:45:51 UTC 
Package: gnome-panel-2.32.0.2-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1during the boot up process
2.logged in aswith my user ID
3.
Comment 3 abrt-bot 2012-03-20 15:57:20 UTC 
Backtrace analysis found this bug to be similar to bug #659899, closing as duplicate.

Bugs which were found to be similar to this bug: bug #653394, bug #659899

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 659899 ***
Note You need to log in before you can comment on or make changes to this bug.