Bug 679772

Summary: [abrt] lxpanel-0.5.6-1.fc13: __strftime_internal: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Anandawardhana <anandawardhana>
Component: lxpanelAssignee: Christoph Wickert <cwickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: cwickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:87a43332b167603b11c24f60cee51304e8062cbc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-23 13:52:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Anandawardhana 2011-02-23 13:43:27 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: lxpanel --profile LXDE
comment: This happened several times on my Fedora 13 installation. I am NOT using Fedora LXDE spin. I installed LXDE later on a gnome installation.
component: lxpanel
crash_function: __strftime_internal
executable: /usr/bin/lxpanel
kernel: 2.6.34.7-66.fc13.i686
package: lxpanel-0.5.6-1.fc13
rating: 4
reason: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1298467500
uid: 500

How to reproduce
-----
1. When running LXDE open panel settings
2. Go to panel applets tab
3. Click Add to add an item
4. Try to move up/down the added item afterwards
Comment 1 Anandawardhana 2011-02-23 13:43:36 UTC 
Created attachment 480449 [details]
File: backtrace
Comment 2 Christoph Wickert 2011-02-23 13:52:26 UTC 
Thanks for submitting this crash report. This is a known bug and I have already forwarded it to the developers.

*** This bug has been marked as a duplicate of bug 600763 ***
Comment 3 Christoph Wickert 2011-02-23 13:52:50 UTC 
Sorry, wrong bug.

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