Bug 562291 - [abrt] crash in gnome-applet-alarm-clock-0.2.6-1.fc12
Summary: [abrt] crash in gnome-applet-alarm-clock-0.2.6-1.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 575539
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-applet-alarm-clock
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:cc7481eb7ee62e4944bd636a649...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-05 20:26 UTC by LEFEVRE Franck
Modified: 2010-03-21 22:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-21 22:06:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (20.78 KB, text/plain)
2010-02-05 20:26 UTC, LEFEVRE Franck 		no flags Details
View All

Description LEFEVRE Franck 2010-02-05 20:26:26 UTC 
abrt 1.0.4 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/alarm-clock-applet --oaf-activate-iid=OAFIID:AlarmClock_Factory --oaf-ior-fd=23
component: gnome-applet-alarm-clock
executable: /usr/libexec/alarm-clock-applet
kernel: 2.6.31.12-174.2.3.fc12.i686.PAE
package: gnome-applet-alarm-clock-0.2.6-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)
Comment 1 LEFEVRE Franck 2010-02-05 20:26:29 UTC 
Created attachment 389180 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-02-05 20:42:16 UTC 
Thanks for your report Franck. Unfortunately the bug reporting tool did not install all the necessary debuginfo, not even gnome-applet-alarm-clock-debuginfo is installed. Please run

$ debuginfo-install gnome-applet-alarm-clock

to install the missing bits manually. If the applet crashes again, please attach the backtrace to this bug or simply submit a new report.
Comment 3 Christoph Wickert 2010-03-21 22:06:10 UTC 

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