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 626377 - gnome-panel crashes when in process applets are enabled
gnome-panel crashes when in process applets are enabled
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: general
2.31.x
Other Linux
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-08 17:53 UTC by Götz Waschk
Modified: 2014-12-29 19:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
%gconf.xml (714 bytes, text/plain)
2010-11-11 09:51 UTC, Pacho Ramos
Details

Description Götz Waschk 2010-08-08 17:53:59 UTC
This is in Mandriva cooker with gnome-panel 2.31.6. Gnome Panel was built with --with-in-process-applets=all :

(gnome-panel:12431): GLib-GObject-WARNING **: cannot register existing type
`PanelApplet'

(gnome-panel:12431): GLib-CRITICAL **: g_once_init_leave: assertion
`initialization_value != 0' failed
Comment 1 Fabio Durán Verdugo 2010-08-09 18:15:05 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Eric Piel 2010-08-09 21:29:45 UTC
I'm the original reporter (of the Mandriva bug report). There is no stacktrace, because it doesn't crash, just _blocks_ on  a futex, just after these two warnings (in strace).

Removing "--with-in-process-applets=all " works around this problem.

Let me know if you need more info to reproduce the bug. For now here is the end of the strace log:
[pid 12431] mmap2(0x41282000, 252412, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 21, 0) = 0x41282000
[pid 12431] mprotect(0x412bd000, 4096, PROT_NONE) = 0
[pid 12431] mmap2(0x412be000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 21, 0x3b) = 0x412be000
[pid 12431] close(21)                   = 0
[pid 12431] mprotect(0x412be000, 4096, PROT_READ) = 0
[pid 12431] munmap(0xb2012000, 122315)  = 0
[pid 12431] write(2, "\n(gnome-panel:12431): GLib-GObje"..., 91
(gnome-panel:12431): GLib-GObject-WARNING **: cannot register existing type `PanelApplet'
) = 91
[pid 12431] write(2, "\n(gnome-panel:12431): GLib-CRITI"..., 104
(gnome-panel:12431): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
) = 104
[pid 12431] futex(0x855d2ac, FUTEX_WAIT_PRIVATE, 1, NULL) = ? ERESTARTSYS (To be restarted)
Comment 3 Vincent Untz 2010-09-05 15:44:17 UTC
I've never seen this. Do you still see it? What you can do is run gnome-panel with G_DEBUG=fatal-criticals to get a stack trace for the critical warning.
Comment 4 Eric Piel 2010-09-15 21:56:04 UTC
Yes, still happens with the current git head.

Here is the backtrace:

  • #0 g_logv
    at gmessages.c line 554
  • #1 g_log
    at gmessages.c line 568
  • #2 g_return_if_fail_warning
    at gmessages.c line 577
  • #3 g_once_init_leave
    at gthread.c line 1136
  • #4 panel_applet_get_type
    at panel-applet.c line 150
  • #5 _panel_applet_shlib_factory
    at wncklet.c line 222
  • #6 panel_applets_manager_dbus_factory_activate
    at panel-applets-manager-dbus.c line 439
  • #7 panel_applets_manager_factory_activate
    at panel-applets-manager.c line 121
  • #8 panel_applet_frame_dbus_load
    at panel-applet-frame-dbus.c line 421
  • #9 panel_applets_manager_dbus_load_applet
    at panel-applets-manager-dbus.c line 551
  • #10 panel_applets_manager_load_applet
    at panel-applets-manager.c line 197
  • #11 panel_applet_frame_load
    at panel-applet-frame.c line 956
  • #12 panel_applet_frame_load_from_gconf
    at panel-applet-frame.c line 979
  • #13 panel_applet_load_idle_handler
    at applet.c line 953
  • #14 g_idle_dispatch
    at gmain.c line 4224
  • #15 g_main_dispatch
    at gmain.c line 2119
  • #16 g_main_context_dispatch
    at gmain.c line 2672
  • #17 g_main_context_iterate
    at gmain.c line 2750
  • #18 g_main_loop_run
    at gmain.c line 2958
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main
    at main.c line 130

Comment 5 Vincent Untz 2010-09-15 23:13:10 UTC
Ah, could it be that you have some in-process bonobo applets too? I'd need to know what applets are in your configuration, and then if they are built in-process in Mandriva or not. (I'm mostly interested in applets that do not live in gnome-panel).
Comment 6 Pacho Ramos 2010-11-11 09:51:40 UTC
Created attachment 174233 [details]
%gconf.xml

In my case I was getting the same errors until I removed old ~/.gconf/desktop/gnome/interface/%gconf.xml

Attached one causes the failure for me and this is the one is working fine just now:

$ cat %gconf.xml 
<?xml version="1.0"?>
<gconf>
	<entry name="icon_theme" mtime="1289464982" type="string">
		<stringvalue>gnome-gentoo</stringvalue>
	</entry>
	<entry name="gtk_theme" mtime="1289464982" type="string">
		<stringvalue>Shiki-Gentoo</stringvalue>
	</entry>
</gconf>
$
Comment 7 Alberts Muktupāvels 2014-12-29 19:02:02 UTC
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.