Bug 607473 - [abrt] crash in lxpanel-0.5.5-3.fc13: __strftime_internal: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in lxpanel-0.5.5-3.fc13: __strftime_internal: Process /usr/bin/l...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: lxpanel
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL: https://sourceforge.net/tracker/?func...
Whiteboard: abrt_hash:404fca3641d551bdaba48ad7207...
: 679772 697661 724000 753859 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-24 07:55 UTC by Onur Samiloglu
Modified: 2011-11-14 17:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-16 13:34:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (150.06 KB, text/plain)
2010-06-24 07:55 UTC, Onur Samiloglu
no flags Details

Description Onur Samiloglu 2010-06-24 07:55:21 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: lxpanel --profile LXDE
comment: reading the variables in the field in real-time causes the program to crash. That's the behaviour of most applications, but reading a null causes it to crash. It should check for the field to show nothing but not crash when the field is empty.
component: lxpanel
crash_function: __strftime_internal
executable: /usr/bin/lxpanel
global_uuid: 404fca3641d551bdaba48ad720764539754bdd35
kernel: 2.6.33.5-124.fc13.x86_64
package: lxpanel-0.5.5-3.fc13
rating: 4
reason: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. digital clock settings
2. clear "clock format" field
3. bang. crash.

Comment 1 Onur Samiloglu 2010-06-24 07:55:24 UTC
Created attachment 426473 [details]
File: backtrace

Comment 2 Christoph Wickert 2010-07-16 13:34:00 UTC
Thanks for your bug report. It seems to be related to bug 600763 which I already forwarded upstream as https://sourceforge.net/tracker/?func=detail&aid=3030531&group_id=180858&atid=894869

Feel free to add yourself to the upstream bug report in order to follow any changes. Even if you don't, will be notified once this bug is resolved in Fedora. If I need more information, I will get back to you.

I'm now closing the bug UPSTREAM because this is where further investigation should take place.

Comment 3 Christoph Wickert 2011-02-23 13:52:50 UTC
*** Bug 679772 has been marked as a duplicate of this bug. ***

Comment 4 Christoph Wickert 2011-06-02 19:52:45 UTC
*** Bug 697661 has been marked as a duplicate of this bug. ***

Comment 5 Christoph Wickert 2011-10-24 09:04:46 UTC
*** Bug 724000 has been marked as a duplicate of this bug. ***

Comment 6 Christoph Wickert 2011-11-14 17:36:50 UTC
*** Bug 753859 has been marked as a duplicate of this bug. ***


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