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 423003 - Calls into gconf crash when no gconf directory structures /daemons are running
Calls into gconf crash when no gconf directory structures /daemons are running
Status: RESOLVED WONTFIX
Product: GConf
Classification: Deprecated
Component: gconf
2.18.x
Other All
: Normal critical
: ---
Assigned To: GConf Maintainers
GConf Maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2007-03-26 13:57 UTC by Wade Mealing
Modified: 2018-08-17 14:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18

Attachments
The quick example to trip over the bug (2.83 KB, application/x-compressed-tar)
2007-03-26 14:01 UTC, Wade Mealing 		Details

Description Wade Mealing 2007-03-26 13:57:48 UTC 
Steps to reproduce:
1.  Compile attached program
2.  Create new user
3.  Run attached program


Stack trace:
Program received signal SIGSEGV, Segmentation fault.

+ Trace 122362

Thread NaN (LWP 7422)

  • #0 set_engine
    at gconf-client.c line 269
  • #1 gconf_client_get_default
    at gconf-client.c line 445
  • #2 e_book_get_addressbooks
    at e-book.c line 3752
  • #3 e_book_new_default_addressbook
    at e-book.c line 3944
  • #4 main 


Other information:
Vuntz wanted this to be assigned to him.
Comment 1 Wade Mealing 2007-03-26 14:01:02 UTC 
Created attachment 85322 [details]
The quick example to trip over the bug

Maybe I'm doing something completely wrong.. who knows.
Comment 2 Kjartan Maraas 2008-05-08 14:02:35 UTC 
Maybe the problem is unrefing the book before it's even opened?
Comment 3 Kjartan Maraas 2008-05-08 14:06:19 UTC 
And you had logged in as the new user? Or did you run it via su - $user -c ./test?
Comment 4 Akhil Laddha 2009-12-02 04:34:19 UTC 
bug 603517 filed against evolution 2.28.x looks same
Comment 5 André Klapper 2018-08-17 14:00:16 UTC 
GConf has been deprecated since 2011.

GConf is not under active development anymore. Its codebase has been archived:
https://gitlab.gnome.org/Archive/gconf/commits/master

dconf and gsettings are its successors. See https://developer.gnome.org/gio/stable/ch34.html and https://developer.gnome.org/GSettings/ for porting info.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of dconf/gsettings. Thanks!