Bug 19967 - linuxconf apps fail to load on SUN Solaris 8 CDE
linuxconf apps fail to load on SUN Solaris 8 CDE
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
7.0
i686 Linux
high Severity high
: ---
: ---
Assigned To: Elliot Lee
Wil Harris
:
: 19970 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-10-28 17:25 EDT by The Ha
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-10-30 11:20:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description The Ha 2000-10-28 17:25:56 EDT
I try to run linuxconf on remote console (Sun Solaris 8 CDE)
ssh  to pearson (Linux 7 server with sshd 1.3)

Here is the error

[root@ xinetd.d]# linuxconf
Error message from remadmin :
Error message from remadmin :Gdk-CRITICAL **: file gdkimage.c: line 416
(gdk_image_destroy): assertion `image != NULL' failed.
Error message from remadmin :
Error message from remadmin :Gdk-CRITICAL **: file gdkimage.c: line 416
(gdk_image_destroy): assertion `image != NULL' failed.
Error message from remadmin :
Error message from remadmin :Gdk-CRITICAL **: file gdkimage.c: line 416
(gdk_image_destroy): assertion `image != NULL' failed.

Thanks
Comment 1 The Ha 2000-10-28 17:46:41 EDT
netscape, emacs run fine...
Comment 2 David Mason 2000-10-30 11:20:46 EST
Elliot, isnt this the same thing we saw with gnome-terminal on Alphas? Check it out.
Comment 3 Elliot Lee 2001-01-22 19:37:11 EST
Yes, and a patch was put into gtk+ to fix this entirely cosmetic warning
(although from gnome-linuxconf it's probably not just cosmetic, due to linuxconf
interpreting the output of the UI).
Comment 4 Elliot Lee 2001-01-22 19:38:56 EST
*** Bug 19970 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.