Bug 538532 - [abrt] crash detected in guake-0.4.0-2.fc12
Summary: [abrt] crash detected in guake-0.4.0-2.fc12
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: guake
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Pierre-YvesChibon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f8e8d949
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-18 18:50 UTC by David Sieg
Modified: 2010-01-22 10:22 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-01-22 10:22:25 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (963 bytes, text/plain)
2009-11-18 18:50 UTC, David Sieg 		no flags Details
View All

Description David Sieg 2009-11-18 18:50:16 UTC 
abrt detected a crash.

How to reproduce
-----
1. install guake
2. start guake
3. n/a

Attached file: backtrace
cmdline: guake -OO /usr/lib64/guake/guake.py 
component: guake
executable: /usr/lib64/guake/guake.py
kernel: 2.6.31.5-127.fc12.x86_64
package: guake-0.4.0-2.fc12
uuid: f8e8d949
Comment 1 David Sieg 2009-11-18 18:50:19 UTC 
Created attachment 370161 [details]
File: backtrace
Comment 2 Pierre-YvesChibon 2009-11-19 08:17:05 UTC 
Can you reproduce this bug ?
Comment 3 Pierre-YvesChibon 2009-11-19 10:21:29 UTC 
This seems to be a gconf issue. Can you check if the gconf scheme is installed under apps/guake ?

If you reinstall guake (yum reinstall) does the problem still persist ?
Comment 4 David Sieg 2009-11-20 16:00:03 UTC 
After the next boot: no. So it seems to be my fault.
Comment 5 Pierre-YvesChibon 2010-01-03 14:11:42 UTC 
It looks like being something on the gconf, I will see with upstream if we can avoid this in future releases.


I leave the bug open until guake.org comes back to life then I will open a ticket on the trac over there.

Thanks for reporting.
Comment 6 Pierre-YvesChibon 2010-01-22 10:22:25 UTC 
Reported to upstream: http://guake.org/ticket/197 I will see with him.
Note You need to log in before you can comment on or make changes to this bug.