Bug 594730 - [abrt] crash in gnome-panel-2.30.0-1.fc13: __pthread_mutex_unlock_full: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
[abrt] crash in gnome-panel-2.30.0-1.fc13: __pthread_mutex_unlock_full: Proce...
Status: CLOSED DUPLICATE of bug 594726
Product: Fedora
Classification: Fedora
Component: gnome-panel (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
abrt_hash:a7950b0e743d21115b718636fb4...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-21 09:13 EDT by jeefoo
Modified: 2010-05-25 06:33 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 06:33:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (28.91 KB, text/plain)
2010-05-21 09:13 EDT, jeefoo
no flags Details

  None (edit)
Description jeefoo 2010-05-21 09:13:40 EDT
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=30
component: gnome-panel
crash_function: __pthread_mutex_unlock_full
executable: /usr/libexec/clock-applet
global_uuid: a7950b0e743d21115b718636fb41d3391b3eccdd
kernel: 2.6.33.3-85.fc13.x86_64
package: gnome-panel-2.30.0-1.fc13
rating: 4
reason: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 jeefoo 2010-05-21 09:13:42 EDT
Created attachment 415678 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 06:33:58 EDT

*** This bug has been marked as a duplicate of bug 594726 ***
Comment 3 Karel Klíč 2010-05-25 06:33:58 EDT
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #594726.

Sorry for the inconvenience.

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