gfax.exe crashed with SIGABRT in gconf_client_get_default()

[Hans Joachim Desserud]

Crashed when I attempted to run it on Ubuntu Precise. (My main reason for running it was to see if it still complained about missing /var/spool/gfax, see for instance bug 711223 for more info) I am not sure whether this is simply the same issue, but it seem to generate a totally different error message.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gfax 0.7.7+ds-1build1
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Tue Dec 27 19:58:59 2011
ExecutablePath: /usr/lib/gfax/gfax.exe
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
InterpreterPath: /usr/bin/mono
PackageArchitecture: all
ProcCmdline: mono /usr/lib/gfax/gfax.exe
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: gfax
StacktraceTop:
 ?? () from /usr/lib/libgconf-2.so.4
 gconf_client_get_default () from /usr/lib/libgconf-2.so.4
 ?? ()
 ?? ()
 ?? ()
Title: gfax.exe crashed with SIGABRT in gconf_client_get_default()
UpgradeStatus: Upgraded to precise on 2011-12-17 (10 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Hans Joachim Desserud (hjd)]

The output I got when attempting to run gfax from the terminal.

[Apport retracing service (apport)]

StacktraceTop:
 set_engine (client=0x0, engine=0x8b9f200) at gconf-client.c:277
 gconf_client_get_default () at gconf-client.c:471
 ?? ()
 ?? ()
 ?? ()

[Przemek Peron (huan-j)]

As of 2012-02-21 this bug still exists :(

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Hans Joachim Desserud (hjd)]

This crash still occurs on Ubuntu 12.10, but I am no longer able to trigger it on Ubuntu 13.04. No idea what fixed it since both releases have the same version of the package, so not sure what should/could be updated on earlier releases. Though since it no longer happens on newer releases, I consider this fixed and close it.

Bug 711223 is still very much present though.