Bug 5110 - When exiting gnome console reports errors
Summary: When exiting gnome console reports errors
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: gnome-core
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-09-13 19:22 UTC by Jaroslaw Sosnicki
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-09-13 20:42:21 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jaroslaw Sosnicki 1999-09-13 19:22:46 UTC 
When shutdiwn down gnome release
rawhide-release-19990907-1.noarch.rpm
I am getting folowing console errors
---
Gtk-WARNING **: invalid cast from (NULL) pointer to
`GtkCTree'

Gtk-CRITICAL **: file gtkctree.c: line 3908
(gtk_ctree_post_recursive): assertio
n `ctree != NULL' failed.

** WARNING **: an initialization error occurred while
starting 'background-prope
rties-capplet'.
aborting...

@rm: cannot remove `/root/.gnome//gmc-xIbuYE': No such file
or directory

waiting for X server to shut down
----
Comment 1 Jaroslaw Sosnicki 1999-09-13 19:29:59 UTC 
I have folowing gnome packages installed:
gnome-audio-1.0.0-7.noarch.rpm        gnome-linuxconf-0.22-1.i386.rpm
gnome-audio-extra-1.0.0-7.noarch.rpm  gnome-media-1.0.9.1-2.i386.rpm
gnome-core-1.0.9-4.i386.rpm           gnome-objc-1.0.2-5.i386.rpm
gnome-core-devel-1.0.9-4.i386.rpm
gnome-objc-devel-1.0.2-5.i386.rpm
gnome-games-1.0.2-12.i386.rpm         gnome-pim-1.0.9-1.i386.rpm
gnome-games-devel-1.0.2-12.i386.rpm   gnome-pim-devel-1.0.9-1.i386.rpm
gnome-libs-1.0.15-3.i386.rpm
gnome-users-guide-1.0.5-5rh.noarch.rpm
gnome-libs-devel-1.0.15-3.i386.rpm    gnome-utils-1.0.12-1.i386.rpm
Comment 2 Elliot Lee 1999-09-13 20:42:59 UTC 
Pay no attention to the debug messages behind the curtain...

There's no actual functionality problem here.
Note You need to log in before you can comment on or make changes to this bug.