Bug 215810 - gnome-power-manager crashing sometimes
Summary: gnome-power-manager crashing sometimes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-power-manager
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Zeuthen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-15 21:18 UTC by Colin Adams
Modified: 2013-03-06 03:48 UTC (History)
4 users (show)

Fixed In Version: F8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-19 06:07:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Bug buddy report (7.58 KB, text/plain)
2006-11-15 21:18 UTC, Colin Adams
no flags Details

Description Colin Adams 2006-11-15 21:18:48 UTC
Description of problem:
Crash in SCIM (when using Firefox, I think)

Version-Release number of selected component (if applicable):


How reproducible:

happens occaisionaly

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

see attachment

Comment 1 Colin Adams 2006-11-15 21:18:48 UTC
Created attachment 141307 [details]
Bug buddy report

Comment 2 Jens Petersen 2006-11-16 00:40:33 UTC
Backtrace is from gnome-power-manager though.

If you could install all the relevant debuginfo packages that would be great
and you should get more info in the backtrace next time it happens.

Comment 3 Colin Adams 2006-11-16 07:28:02 UTC
What are the relevant debuginfo packages? I am not familiar with the phrase.

Comment 4 Jens Petersen 2006-11-16 07:42:28 UTC
I would start with gnome-power-manager-debuginfo.

I doubt the scim warnings you're seeing in .xsession-errors are related
to your crash.

Comment 6 petrosyan 2008-03-17 05:42:21 UTC
Fedora Core 5 and Fedora Core 6 are no longer maintained. Is this bug still
present in Fedora 7 or Fedora 8?

Comment 7 Jens Petersen 2008-03-19 06:07:58 UTC
I think this can be closed - it g-p-m seems better in F8 updates anyway.

Please re-open if there are still problems.


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