Bug 768939 - [abrt] gnome-applet-sensors-2.2.5-3.fc14: active_sensor_update: Process /usr/libexec/sensors-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-applet-sensors-2.2.5-3.fc14: active_sensor_update: Process /usr/...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-applet-sensors
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Huzaifa S. Sidhpurwala
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:db87d882262dd8272522dd2c302...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-19 13:42 UTC by francesco
Modified: 2012-01-08 03:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-08 03:26:18 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (48.94 KB, text/plain)
2011-12-19 13:42 UTC, francesco
no flags Details

Description francesco 2011-12-19 13:42:11 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 50114 bytes
cmdline: /usr/libexec/sensors-applet --oaf-activate-iid=OAFIID:SensorsApplet_Factory --oaf-ior-fd=22
component: gnome-applet-sensors
Attached file: coredump, 21962752 bytes
crash_function: active_sensor_update
executable: /usr/libexec/sensors-applet
kernel: 2.6.35.14-103.fc14.x86_64
package: gnome-applet-sensors-2.2.5-3.fc14
rating: 4
reason: Process /usr/libexec/sensors-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: it suddenly crashed
time: 1322242087
uid: 500

Comment 1 francesco 2011-12-19 13:42:22 UTC
Created attachment 548577 [details]
File: backtrace

Comment 2 Robert Scheck 2012-01-08 03:26:18 UTC
Fedora 14 changed to end-of-life (EOL) status on 2011-12-08. Fedora 14 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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