Bug 597084

Summary: [abrt] crash in xfce4-cellmodem-plugin-0.0.5-2.fc12: IA__g_object_unref: Process /usr/libexec/xfce4/panel-plugins/xfce4-cellmodem-plugin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: deuno_panopticon
Component: xfce4-cellmodem-pluginAssignee: Christoph Wickert <cwickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: cwickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:763d841eca18258a2d2be24f46bcca341a976f51
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-10 13:14:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
File: backtrace none

Description deuno_panopticon 2010-05-28 05:38:58 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/xfce4/panel-plugins/xfce4-cellmodem-plugin socket_id 29367415 name cellmodem id 12750247651 display_name 'Cellular Modem Monitor' size 28 screen_position 11
component: xfce4-cellmodem-plugin
crash_function: IA__g_object_unref
executable: /usr/libexec/xfce4/panel-plugins/xfce4-cellmodem-plugin
global_uuid: 763d841eca18258a2d2be24f46bcca341a976f51
kernel: 2.6.33.4-95.fc13.i686
package: xfce4-cellmodem-plugin-0.0.5-2.fc12
rating: 3
reason: Process /usr/libexec/xfce4/panel-plugins/xfce4-cellmodem-plugin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.Right Click, load XFCE cellmodem plugin
2.Right Click, Remove XFCE Cellmodem plugin
3.

Comment 1 deuno_panopticon 2010-05-28 05:39:00 UTC
Created attachment 417478 [details]
File: backtrace

Comment 2 Christoph Wickert 2010-06-10 13:14:30 UTC
Thanks for your bug report. We have a better backtrace now in bug 602662.

*** This bug has been marked as a duplicate of bug 602662 ***