Bug 390946 – crash in Sessions: start session

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 390946 - crash in Sessions: start session


Summary:	crash in Sessions: start session


Status:	RESOLVED DUPLICATE of bug 364839

Product:	gnome-session
Classification:	Core
Component:	gnome-session
Version:	2.17.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Session Maintainers
QA Contact:	Session Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-30 11:53 UTC by okd
Modified:	2006-12-30 15:11 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description okd 2006-12-30 11:53:11 UTC

Version: 2.17.2

What were you doing when the application crashed?
start session


Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:19 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 76681216 vsize: 0 resident: 76681216 share: 0 rss: 12443648 rss_rlim: 0
CPU usage: start_time: 1167479535 rtime: 0 utime: 41 stime: 0 cutime:34 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-session-properties'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208252720 (LWP 2574)]
(no debugging symbols found)
0x00f7a402 in __kernel_vsyscall ()

+ Trace 97992

Thread 1 (Thread -1208252720 (LWP 2574))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strlen
from /lib/libc.so.6
#5 giop_send_buffer_append_string
from /usr/lib/libORBit-2.so.0
#6 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#7 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#8 ORBit_marshal_any
from /usr/lib/libORBit-2.so.0
#9 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#10 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#11 ORBit_small_allocbuf
from /usr/lib/libORBit-2.so.0
#12 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#13 ORBit_small_invoke_stub_n
from /usr/lib/libORBit-2.so.0
#14 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#15 Accessibility_EventListener_notifyEvent
from /usr/lib/libspi.so.0
#16 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#17 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#18 exit
from /lib/libc.so.6
#19 __libc_start_main
from /lib/libc.so.6
#20 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 Jens Granseuer 2006-12-30 15:11:06 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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