Bug 465255 – crash in Services: nuevamente abriendo serv...

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 465255 - crash in Services: nuevamente abriendo serv...


Summary:	crash in Services: nuevamente abriendo serv...


Status:	RESOLVED DUPLICATE of bug 350758

Product:	gnome-system-tools
Classification:	Deprecated
Component:	services-admin
Version:	2.15.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Carlos Garnacho
QA Contact:	Carlos Garnacho

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-10 02:13 UTC by ferguez
Modified:	2007-09-11 19:16 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description ferguez 2007-08-10 02:13:58 UTC

Version: 2.15.4

What were you doing when the application crashed?
nuevamente abriendo servicios


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 17756160 vsize: 0 resident: 17756160 share: 0 rss: 6754304 rss_rlim: 0
CPU usage: start_time: 1186715620 rtime: 0 utime: 18 stime: 0 cutime:16 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225169232 (LWP 4686)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 154116

Thread 1 (Thread -1225169232 (LWP 4686))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 *__GI_raise
from /lib/tls/i686/cmov/libc.so.6
#6 *__GI_abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 oobs_session_get
from /usr/lib/liboobs-1.so.1
#11 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#12 g_object_set
from /usr/lib/libgobject-2.0.so.0
#13 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#14 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_object_new
from /usr/lib/libgobject-2.0.so.0
#16 oobs_session_get
from /usr/lib/liboobs-1.so.1
#17 ??
#18 ??
from /usr/lib/libgobject-2.0.so.0
#19 ??
#20 ??
#21 g_object_connect
from /usr/lib/libgobject-2.0.so.0
#22 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#23 g_object_set
from /usr/lib/libgobject-2.0.so.0
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
from /usr/lib/libgobject-2.0.so.0
#29 ??
#30 ??
#31 ??
#32 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#33 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#34 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#35 g_object_new
from /usr/lib/libgobject-2.0.so.0
#36 ??
#37 ??
#38 _IO_stdin_used
#39 _IO_stdin_used
#40 _IO_stdin_used
#41 _IO_stdin_used
#42 _IO_stdin_used
#43 _IO_stdin_used
#44 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-09-11 19:16:01 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 350758 ***