Bug 718305 - [abrt] gnome-panel-2.28.0-16.fc12: bonobo_property_bag_new: Process /usr/libexec/clock-applet was killed by signal 7 (SIGBUS)
Summary: [abrt] gnome-panel-2.28.0-16.fc12: bonobo_property_bag_new: Process /usr/libe...
Keywords:
Status: CLOSED DUPLICATE of bug 718308
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 12
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:61ab058a913af5e559094917db7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-01 18:35 UTC by biscuit.ak41
Modified: 2012-03-21 16:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 16:44:16 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (22.48 KB, text/plain)
2011-07-01 18:35 UTC, biscuit.ak41 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description biscuit.ak41 2011-07-01 18:35:33 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=27
component: gnome-panel
crash_function: bonobo_property_bag_new
executable: /usr/libexec/clock-applet
kernel: 2.6.32.26-175.fc12.i686.PAE
package: gnome-panel-2.28.0-16.fc12
rating: 4
reason: Process /usr/libexec/clock-applet was killed by signal 7 (SIGBUS)
release: Fedora release 12 (Constantine)
time: 1309542775
uid: 500
Comment 1 biscuit.ak41 2011-07-01 18:35:36 UTC 
Created attachment 510912 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 16:44:16 UTC 
Backtrace analysis found this bug to be similar to bug #718308, closing as duplicate.

Bugs which were found to be similar to this bug: 
  gdm: bug #718301
  gnome-panel: bug #718300, bug #718302
  gnote: bug #718308

This comment is automatically generated.

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