Bug 679772 - [abrt] lxpanel-0.5.6-1.fc13: __strftime_internal: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
Summary: [abrt] lxpanel-0.5.6-1.fc13: __strftime_internal: Process /usr/bin/lxpanel wa...
Keywords:
Status: CLOSED DUPLICATE of bug 607473
Alias: None
Product: Fedora
Classification: Fedora
Component: lxpanel
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:87a43332b167603b11c24f60cee...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-23 13:43 UTC by Anandawardhana
Modified: 2011-02-23 13:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-23 13:52:26 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (96.37 KB, text/plain)
2011-02-23 13:43 UTC, Anandawardhana 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.