Ticket #197 (closed defect: invalid)

Opened 8 months ago

Last modified 7 months ago

Crash in guake.py

Reported by: pingou Owned by: somebody
Priority: major Milestone:
Component: guake Version: 0.4
Keywords: Cc:

Description

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    

Backtrace:

Summary: TBf8e8d949 guake.py:397:configure_terminal:TypeError: Vte.Terminal.set_word_chars() argument 1 must be string, not None

Traceback (most recent call last):
  File "/usr/lib64/guake/guake.py", line 1080, in <module>
    guake = Guake()
  File "/usr/lib64/guake/guake.py", line 557, in __init__
    self.add_tab()
  File "/usr/lib64/guake/guake.py", line 929, in add_tab
    box = GuakeTerminalBox()
  File "/usr/lib64/guake/guake.py", line 448, in __init__
    self.terminal = GuakeTerminal()
  File "/usr/lib64/guake/guake.py", line 388, in __init__
    self.configure_terminal()
  File "/usr/lib64/guake/guake.py", line 397, in configure_terminal
    self.set_word_chars(word_chars)
TypeError: Vte.Terminal.set_word_chars() argument 1 must be string, not None

Local variables in innermost frame:
self: <GuakeTerminal object at 0x28ff050 (VteTerminal at 0x2993000)>
client: <gconf.Client object at 0x28fddc0 (GConfClient at 0x269cf00)>
word_chars: None

Original report: https://bugzilla.redhat.com/show_bug.cgi?id=538532

Change History

Changed 8 months ago by lincoln

Hello there. I'm not sure that it is a bug. This happens when guake schemas file is not correctly installed.

Changed 8 months ago by pingou

hm, something weird must have happened then since the schema is installed directly via the RPM.

I am wondering if there is not something going wrong sometime with the way it is done. This only happens the first time AFAIK.

Changed 7 months ago by pingou

  • status changed from new to closed
  • resolution set to invalid

I'll close the bug for the moment, to me it is a gconf fedora related issue.

I'll see what can be done if I get more of these bugs

Note: See TracTickets for help on using tickets.