Bug 684084 - [abrt] xfce4-panel-4.6.4-1.fc14: Process /usr/bin/xfce4-panel was killed by signal 11 (SIGSEGV)
Summary: [abrt] xfce4-panel-4.6.4-1.fc14: Process /usr/bin/xfce4-panel was killed by s...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-panel
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8fee6179a4e721a895ebe44c72d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-11 04:30 UTC by DiShi
Modified: 2012-08-16 21:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 21:29:16 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (5.35 KB, text/plain)
2011-03-11 04:30 UTC, DiShi
no flags Details

Description DiShi 2011-03-11 04:30:31 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 5475 bytes
cmdline: xfce4-panel
component: xfce4-panel
Attached file: coredump, 15622144 bytes
executable: /usr/bin/xfce4-panel
kernel: 2.6.35.10-74.fc14.x86_64
package: xfce4-panel-4.6.4-1.fc14
reason: Process /usr/bin/xfce4-panel was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1298314967
uid: 500

How to reproduce
-----
1. Suddenly everything started to collapse. Not sure why? I was just browsing some files and it suddebly crashed. Actually all application which were running all started crashing one by one. :)
2.
3.

Comment 1 DiShi 2011-03-11 04:30:34 UTC
Created attachment 483630 [details]
File: backtrace

Comment 2 Kevin Fenzi 2011-03-11 06:13:12 UTC
It looks like some sort of critical system meltdown... the backtrace is pretty useless here, as it got I/O errors trying to parse the debuginfo. ;( 

Did everything return to normal after a reboot? 
Anything in /var/log/messages after rebooting?

Comment 3 DiShi 2011-03-11 06:34:31 UTC
(In reply to comment #2)
> It looks like some sort of critical system meltdown... the backtrace is pretty
> useless here, as it got I/O errors trying to parse the debuginfo. ;( 
> 
> Did everything return to normal after a reboot? 
> Anything in /var/log/messages after rebooting?

Yeah, everything looks fine after reboot so must be something went wrong with HDD or cable, not sure. But as everything started to crash i thought reboot was a better way to get back to normal. 

There are lots of messages in /var/log/messages file. Do you want me to find something special in that. Something you can think of which i can run through grep to find the exact information you need for this?

Comment 4 Kevin Fenzi 2011-03-11 16:11:28 UTC
Well, hard to say... anything with error or read/only in it might be note.

Comment 5 Christoph Wickert 2011-09-26 19:18:00 UTC
Should we just close this INSUFFICIENT_DATA and hope for a useful backtrace?

Comment 6 Fedora End Of Life 2012-08-16 21:29:18 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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