GNOME Bugzilla – Bug 109374
Need to create a default panel if no panels are found in the config
Last modified: 2004-12-22 21:47:04 UTC
Using garnome-0.22.0 I upgraded to gnome-panel-2.3.0, gnome-session-2.3.0 and gnome-desktop-2.3.0 (along with all the related requirements like GConf-2.3.0 and ORBit-2.7.0). Gnome started fine, and gnome-panel was running, but no panel showed. I even deleted .gconf and .gconfd and ran gconftool-[1|2] --shutdown before deleting these. If I tried to run gnome-panel I was advised that it was already running. It wasn't crashing and restarting either.
Just for your information: I have the same problem, but not with GARNOME build but with Slackware-9.0 upgraded (by self) to the gnome-{session,desctop,panel} + orbit + gconf + etc to the 2.3.0. Panel shows if previous (from gnome-panel-2.2.x) gconf entries are exists, but fresh install does't work (panel running, but doesn't exists on screen). If you need additional info -- welcome.
This bug still exist with latest gnome 2.3.1 packages
Checkd for gnome-panel-2.3.2.1 -- bug still exists. To gnome-panel-maint@bugzilla.gnome.org: Is someone care about usability of GNOME in the real live???? Neither ACK not NACK nor any other activity around this bug! This bug prevents using of GNOME by "fresh" users -- I'm enforced to copy my panle-related settings to the every new user of my system that is not goog (more right -- very poor!)
Does gconftool-2 -R /apps/panel/default_setup return anything?
gconftool-2 -R /apps/panel/default_setup returns nothing uder both my (working) settings and under fresh/new user.
awn, I'm going to take a moment to stand up for the developers on this. I appreciate that you might be frustrated with this issue in gnome-panel, but remember that this version is a development release and as such you shouldn't expect it to work. Gnome users who want a stable, working desktop are not recommended to use this version and as such I think you've been a little harsh on the guys that work on gnome-panel. Rodd
What you are seeing is an installation problem of some sort. When you do a make install the panel should be installing the default panel setup using a command similar to GCONF_CONFIG_SOURCE=xml:/etc/gconf/gconf.xml.defaults gconftool-2 --load panel-default-setup.entries Could you try and figure out why thats not working for you ?
Not excactly, but following command helps: gconftool-2 --direct --config-source=xml::/etc/gconf/gconf.xml.defaults --load panel-default-setup.entries Note about `--direct'. How about note this (needing to load panel-default-setup.entries) in the README file? Why just loading of default entries from Makefile is not enough: because this not work for `make install DESTDIR=...' case. About needing to register .schemas by hand know if not all then neary to all because this is common problem for all gnome applications. But default entries beside schemas...
You installed using DESTDIR ? If so, then yes this is expected behaviour. Just like schemas these have to be installed in postinstall scripts in packages ... However, there is the problem that we seem to have lost the code to create a default panel when no panels are found in the configuration. That needs to be brought back.
*** Bug 115754 has been marked as a duplicate of this bug. ***
Fixed on HEAD: 2003-07-01 Mark McLoughlin <mark@skynet.ie> Fix bug #109374. When no panel's are found in the default configuration, show a fallback panel so we don't end up with a running panel process and no panels. This seems to be getting reported a fair bit, so I reckon packagers mustn't yet have twigged about installing the default configuration using gconftool-2 --load. Your post install magic should be something like this: gconftool-2 --direct --config-source=$GCONF_CONFIG_SOURCE --load %{_sysconfdir}/gconf/schemas/panel-default-setup.entries * panel-profile.c: (panel_profile_find_new_id): assert that we always return an id. (panel_profile_copy_defaults_for_screen): fix using the wrong key for the schemas location. (panel_profile_create_fallback_toplevel_list): impl returning a list of fallback toplevels. Currently just a single toplevel according to the schemas defaults with no objects. (panel_profile_load_defaults_on_screen): if we can't find any toplevels in the default configuration, load a fallback panel. (panel_profile_ensure_toplevel_per_screen): kill FIXME.
*** Bug 113674 has been marked as a duplicate of this bug. ***
*** Bug 116436 has been marked as a duplicate of this bug. ***