gconf-editor crashed with SIGABRT in g_assertion_message()

Bug #949751 reported by Ondergetekende
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gconf-editor (Ubuntu)
New
Medium
Unassigned

Bug Description

I 'unset' the key desktop/gnome/peripherals/keyboard/kbd -> options. After the crash, that key unset was indeed gone.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gconf-editor 3.0.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
Date: Thu Mar 8 09:28:18 2012
ExecutablePath: /usr/bin/gconf-editor
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: gconf-editor
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LANGUAGE=en
Signal: 6
SourcePackage: gconf-editor
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgconf-2.so.4
Title: gconf-editor crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-01-11 (56 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare wireshark

Revision history for this message
Ondergetekende (kvdveer) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #912116. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: added: regression-retracer
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x7f51525a8680 "gconf_client_lookup", message=0x1e93e90 "assertion failed: (last_slash != NULL)") at /build/buildd/glib2.0-2.31.20/./glib/gtestutils.c:1860
 g_assertion_message_expr (domain=0x7f51525a914b "GConf", file=0x7f51525a7ac5 "gconf-client.c", line=2369, func=0x7f51525a8680 "gconf_client_lookup", expr=<optimized out>) at /build/buildd/glib2.0-2.31.20/./glib/gtestutils.c:1871
 gconf_client_lookup (client=0x1dec760, key=0x21207d0 "", entryp=<optimized out>) at gconf-client.c:2369
 gconf_client_key_is_writable (client=0x1dec760, key=0x21207d0 "", err=0x0) at gconf-client.c:1415
 gconf_editor_window_update_list_selection (selection=<optimized out>, window=0x1daa0e0) at gconf-editor-window.c:1078

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gconf-editor (Ubuntu):
importance: Undecided → Medium
summary: - gconf-editor crashed with SIGABRT in raise()
+ gconf-editor crashed with SIGABRT in g_assertion_message()
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.