Bug 819217 - [abrt] gnome-applets-1:2.30.0-1.fc13: IA__gdk_drawable_set_colormap: Process /usr/libexec/cpufreq-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-applets-1:2.30.0-1.fc13: IA__gdk_drawable_set_colormap: Process ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-applets
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:12f1121999940f4a6aa8095cde4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-05 18:43 UTC by Patrick Kasper
Modified: 2016-02-10 14:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-26 09:30:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (27.28 KB, text/plain)
2012-05-05 18:43 UTC, Patrick Kasper
no flags Details

Description Patrick Kasper 2012-05-05 18:43:08 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/cpufreq-applet --oaf-activate-iid=OAFIID:GNOME_CPUFreqApplet_Factory --oaf-ior-fd=18
component: gnome-applets
crash_function: IA__gdk_drawable_set_colormap
executable: /usr/libexec/cpufreq-applet
kernel: 2.6.34.8-68.fc13.i686
package: gnome-applets-1:2.30.0-1.fc13
rating: 4
reason: Process /usr/libexec/cpufreq-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1335793949
uid: 500

How to reproduce
-----
1.
2.
3.
pff

Comment 1 Patrick Kasper 2012-05-05 18:43:12 UTC
Created attachment 582309 [details]
File: backtrace

Comment 2 Jan Kurik 2015-12-22 11:31:34 UTC
This bug is currently assigned to an unsupported release. If you think this bug is still valid and should remain open, please re-assign it to a supported release (F22, F23) or to rawhide.

Bugs which will be assigned to an unsupported release are going to be closed as EOL (End Of Life) on January 26th, 2016.


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