Bug 644514 – [regression] dconf aborts:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 644514 - [regression] dconf aborts:


Summary:	[regression] dconf aborts:


Status:	RESOLVED NOTABUG

Product:	dconf
Classification:	Core
Component:	dconf
Version:	0.7.x
Hardware:	Other Linux

Importance:	Urgent blocker
Target Milestone:	---
Assigned To:	dconf-maint
QA Contact:	dconf-maint

URL:
Whiteboard:

Depends on:
Blocks:	644764

Reported:	2011-03-11 16:11 UTC by David Ronis
Modified:	2011-03-16 18:03 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description David Ronis 2011-03-11 16:11:10 UTC

Things were working fine yesterday.  I upgraded the following:
 
       * desktop/gjs: bump version to 0.7.13
        * desktop/gjs: bump version to 0.7.12
        * platform/gobject-introspection: bump version to 0.10.4
        * desktop/cheese: bump version to 2.91.91.1
        * freedesktop/poppler: bump version to 0.16.3
        * desktop/totem: bump version to 2.91.91
        * desktop/libgnome-keyring: bump version to 2.91.92
        * desktop/gnome-keyring: bump version to 2.91.92
        * desktop/libpeas: bump version to 0.7.4

I've rebuilt dconf,  but it still aborts.   Here's the backtrace:

Core was generated by `dconf'.
Program terminated with signal 5, Trace/breakpoint trap.

+ Trace 226273

Thread 1 (Thread 29347)

#0 g_logv
at gmessages.c line 563
#1 g_log
at gmessages.c line 577
#2 _vala_main
at dconf.c line 260
#3 main
at dconf.c line 287

Comment 1 David Ronis 2011-03-16 14:19:38 UTC

This is causing havoc here; my apps are failing to find things (like icons, earlier kbd settings) and this causes things like metacity to crash.   The only thing I can do is to manually start mutter from a terminal window (after killing anything started after it that hides the terminal window).

This should be a "blocker" (I'm raising it).

Comment 2 Milan Crha 2011-03-16 16:48:31 UTC

After a little chat and investigation with David we figured out that this is a correct "crash", as the dconf binary expect a command name, where only known are read/list/write/update/lock/unlock/watch. I would close this as not-a-bug