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 439398 - control-center crashes on Solaris when gnome-main-menu isn't present.
control-center crashes on Solaris when gnome-main-menu isn't present.
Status: RESOLVED WONTFIX
Product: gnome-main-menu
Classification: Other
Component: libslab
unspecified
Other All
: Normal critical
: ---
Assigned To: GNOME main menu maintainers
GNOME main menu maintainers
gnome[unmaintained]
: 416360 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-05-18 11:03 UTC by Darren Kenny
Modified: 2020-03-05 10:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18

Attachments
Fix for crashes. (955 bytes, patch)
2007-05-18 11:04 UTC, Darren Kenny 		none Details | Review
gnome-control-center-2.19.90-no-warnings.patch (2.51 KB, patch)
2007-08-20 10:36 UTC, Bastien Nocera 		none Details | Review

Description Darren Kenny 2007-05-18 11:03:15 UTC 
Steps to reproduce:
Can be easily reproduced by simply running gnome-control-center. On Solaris we are not deliver gnome-main-menu since it's not a core product of GNOME 2.18. Control Center should run without it ever being installed.

The errors reported are:

 gnome-control-center 

** (GNOME Control Center:22394): WARNING **: 
error raised: [???: error getting /desktop/gnome/applications/main-menu/lock-down/user_modifiable_apps]


** (GNOME Control Center:22394): WARNING **: 
error raised: [???: couldn't load bookmark file [NULL]
]



Stack trace:


Other information:
The first message (about the gconf key) caused a crash when freeing the value, which was null.

When this was fixed, we proceeded to get the next error about the bookmark file, where the filename was null.

Once these were fixed the control-center starts fine.
Comment 1 Darren Kenny 2007-05-18 11:04:32 UTC 
Created attachment 88379 [details] [review]
Fix for crashes.

Attaching a fix that stops the crashes (but doesn't stop the errors being reported).
Comment 2 Jens Granseuer 2007-05-18 16:38:18 UTC 
Moving to libslab...
Comment 3 Jens Granseuer 2007-05-31 12:57:46 UTC 
Jim, what is this supposed to mean?

The crash is very obviously in libslab code. Does this imply we should commit patches to libslab without maintainer review from main-menu?

(this is a duplicate of bug 416360, btw)
Comment 4 Jim Krehl 2007-06-04 17:50:36 UTC 
I applied a modified version of the patch to svn trunk.
Comment 5 Jens Granseuer 2007-06-04 18:23:30 UTC 
*** Bug 416360 has been marked as a duplicate of this bug. ***
Comment 6 Bastien Nocera 2007-08-20 10:18:31 UTC 
Reopening. Although the crashes caused by those warnings are fixed, we shouldn't even get a warning for them:

** (GNOME Control Center:22394): WARNING **: 
error raised: [???: error getting
/desktop/gnome/applications/main-menu/lock-down/user_modifiable_apps]

This is dependent on gnome-main-menu being installed, which is just wrong.

** (GNOME Control Center:22394): WARNING **: 
error raised: [???: couldn't load bookmark file [NULL]
]

This is pretty useless as well...
Comment 7 Bastien Nocera 2007-08-20 10:36:56 UTC 
Created attachment 93971 [details] [review]
gnome-control-center-2.19.90-no-warnings.patch

Don't show warnings for minor errors.
Comment 8 André Klapper 2020-03-05 10:55:23 UTC 
This project is not under active development anymore; see https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/263

Hence reflecting reality and mass-closing all its remaining open tasks.