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 359286 - crash in Services: I opened the service set...
crash in Services: I opened the service set...
Status: RESOLVED OBSOLETE
Product: gnome-system-tools
Classification: Deprecated
Component: services-admin
2.14.x
Other All
: High critical
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
: 369253 425486 430717 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-03 14:01 UTC by denkpadje
Modified: 2007-09-30 23:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
gdb, bug-buddy, strace, valgrind traces (9.44 KB, application/x-gzip)
2006-10-03 19:06 UTC, denkpadje
Details

Description denkpadje 2006-10-03 14:01:59 UTC
Version: 2.14.0

What were you doing when the application crashed?
I opened the service settings, then clicked on a random checkbox to start a service. Trying to enable any service crashes the service setting program. It crashes under GNOME 2.16 and also has crashed under GNOME 2.14

CFLAGS="-march=athlon64 -O2 -pipe -msse3"
Distro: Gentoo amd64


Distribution: Gentoo Base System version 1.6.14
Gnome Release: 2.16.0 2006-10-02 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 114561024 vsize: 114561024 resident: 14548992 share: 10084352 rss: 14548992 rss_rlim: -1
CPU usage: start_time: 1159884111 rtime: 31 utime: 27 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/services-admin'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47833787735680 (LWP 29398)]
0x00002b812ab68e84 in waitpid () from /lib/tls/libpthread.so.0

Thread 1 (Thread 47833787735680 (LWP 29398))

  • #0 waitpid
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 ??
  • #5 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_signal_has_handler_pending
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #9 gtk_cell_renderer_toggle_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 gtk_tree_view_column_focus_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 gtk_tree_view_column_focus_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_tree_view_set_model
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_marshal_VOID__UINT_STRING
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_has_handler_pending
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #18 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gdk_event_get_graphics_expose
    from /usr/lib/libgdk-x11-2.0.so.0
  • #22 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #25 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
  • #27 ??
  • #28 __libc_start_main
    from /lib/tls/libc.so.6
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #0 waitpid
    from /lib/tls/libpthread.so.0

Comment 1 Elijah Newren 2006-10-03 15:45:19 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 denkpadje 2006-10-03 19:06:06 UTC
Created attachment 73964 [details]
gdb, bug-buddy, strace, valgrind traces

Ok, I recompiled system-tools-backend and gnome-system-tools with debug USE flag. Set nostrip feature in /etc/make.conf (to avoid stripping)

It seems the application segfaults when I click any checkbox. .tar.gz file contains text files with trace output from gdb, bug-buddy, strace and valgrind.
Comment 3 Elijah Newren 2006-10-03 19:20:31 UTC
Sweet, you went above and beyond the call of duty.  The stack trace definitely appears to be unique according to the simple dupe finder; I'll paste it here so we can spot any duplicates more easily:

(gdb) run
Starting program: /usr/bin/services-admin 
[Thread debugging using libthread_db enabled]
[New Thread 47473963656096 (LWP 2245)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47473963656096 (LWP 2245)]
gst_xml_element_find_first (parent=0xffffffff00738830, name=0x40c50d "runlevels") at gst-xml.c:85
85      gst-xml.c: No such file or directory.
        in gst-xml.c
(gdb) thread apply all bt

Thread 1 (Thread 47473963656096 (LWP 2245))

  • #0 gst_xml_element_find_first
    at gst-xml.c line 85
  • #1 on_service_toggled
    at callbacks.c line 75
  • #2 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #3 g_signal_has_handler_pending
    from /usr/lib/libgobject-2.0.so.0
  • #4 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #6 gtk_cell_renderer_toggle_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_tree_view_column_focus_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 gtk_tree_view_column_focus_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 gtk_tree_view_set_model
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 gtk_marshal_VOID__UINT_STRING
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_has_handler_pending
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gdk_event_get_graphics_expose
    from /usr/lib/libgdk-x11-2.0.so.0
  • #19 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #22 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 tool_main_do
    at gst-tool.c line 1060
  • #24 main
    at main.c line 64

Comment 4 André Klapper 2006-11-02 12:32:02 UTC
*** Bug 369253 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2006-11-02 12:32:43 UTC
confirming as per duplicate.
Comment 6 palfrey 2007-04-02 14:09:15 UTC
*** Bug 425486 has been marked as a duplicate of this bug. ***
Comment 7 Susana 2007-04-22 12:08:17 UTC
*** Bug 430717 has been marked as a duplicate of this bug. ***
Comment 8 Sven Arvidsson 2007-05-20 19:13:30 UTC
Any guesses on this one? It seems to be limited to 2.14 on amd64.
Comment 9 Carlos Garnacho 2007-09-30 23:01:56 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.