crash when gconf is inaccessible or configuation gets fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Terminator |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When GConf is present but inaccessible (running as a different user, on a different machine sharing the same $HOME over NFS, etc), or indeed if other errors happen when acquiring gconf info, we get a crash at startup as terminator tries to acquire defaults:
Traceback (most recent call last):
File "./terminator", line 120, in <module>
TERMINATOR.
File "/usr/src/
window, terminal = self.new_window()
File "/usr/src/
terminal = maker.make(
File "/usr/src/
output = func(**kwargs)
File "/usr/src/
return(
File "/usr/src/
self.
File "/usr/src/
self.
File "/usr/src/
title_font = Pango.FontDescr
File "/usr/src/
'/desktop/
GLib.Error: gconf-error-quark: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://
It is clearly better to silently drop said defaults than to crash.
Patch to do that attached.
Hi Nix, thanks for the patch, but it turns out I "fixed" this already when making a change to move away from old gtk2 GConfig to new gtk3 DConfig, fixing: https:/ /bugs.launchpad .net/terminator /+bug/1655446
You can see the change: http:// bazaar. launchpad. net/~gnome- terminator/ terminator/ gtk3/revision/ 1697
I'm going to mark this as invalid, as it no longer applies.