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 86689 - Gnome session manager crash at logout
Gnome session manager crash at logout
Status: RESOLVED DUPLICATE of bug 59290
Product: gnome-core
Classification: Deprecated
Component: gsm
1.4.x
Other other
: Normal normal
: 1.4.1
Assigned To: gnome-core Maintainers
Luis Villa
Depends on:
Blocks:
 
 
Reported: 2002-06-28 05:39 UTC by rkrishna
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description rkrishna 2002-06-28 05:40:21 UTC
Package: gnome-session
Severity: normal
Version: 1.4.1
Synopsis: Gnome session manager crash at logout
Bugzilla-Product: gnome-session
Bugzilla-Component: gnome-session

Description:
The system is a PII-400 running debian/testing.
Everything appears to work fine until logout. At logout, I get a message
that the gnome session manager has crashed and that I should close all
windows and log out and re-start it. This problem appears to have
started at some point after making the following changes to my setup:

1) Deactivated nautilus from displaying the desktop (for performance,
basically)
2) Setting up gnome-terminals with transparent/shaded backgrounds (can't
imagine that is the cause)

There have been a couple of other changes too, but I honestly don't
remember (been tweeking my config for the last couple of days.)



Debugging Information:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x4052aa39 in wait4 () from /lib/libc.so.6
  • #0 wait4
    from /lib/libc.so.6
  • #1 __check_rhosts_file
    from /lib/libc.so.6
  • #2 gnome_init
    from /usr/lib/libgnomeui.so.32
  • #3 sigaction
    from /lib/libc.so.6
  • #4 gdk_get_show_events
    from /usr/lib/libgdk-1.2.so.0
  • #5 g_io_add_watch
    from /usr/lib/libglib-1.2.so.0
  • #6 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #8 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #9 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #10 main
  • #11 __libc_start_main
    from /lib/libc.so.6
  • #0 wait4
    from /lib/libc.so.6
  • #1 __check_rhosts_file
    from /lib/libc.so.6
  • #2 gnome_init
    from /usr/lib/libgnomeui.so.32
  • #3 sigaction
    from /lib/libc.so.6
  • #4 gdk_get_show_events
    from /usr/lib/libgdk-1.2.so.0
  • #5 g_io_add_watch
    from /usr/lib/libglib-1.2.so.0
  • #6 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-1.2.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-28 01:40 -------

The original reporter (rkrishna@eecs.umich.edu) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-session-maint@bugzilla.gnome.org.

Comment 1 Kjartan Maraas 2002-06-28 18:37:58 UTC
Please try resetting your terminal configs since we've had more than
enough reports of those crashing with shaded/transparent backgrounds.
Just see if it helps and report back here.
Comment 2 Ben FrantzDale 2002-07-24 00:10:46 UTC

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