SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I exit X (to the command line interface, CLI) I get various errors and warning messages. The precise errors vary according to which window manager I use, but they all seem to be fairly similar. Here is what I get when I use Gnome:
Code:
(gnome-panel:1008): GdkPixbuf-CRITICAL: file gdk-pixbuf-io.c: line 769 (gdk-pixbuf-new-from-file): assertion 'filename != NULL' failed
** (nautilus:1010): WARNING **: destroyed file still being monitored
** (nautilus:1010): WARNING **: destroyed file still being monitored
** (nautilus:1010): WARNING **: destroyed file still being monitored
** (nautilus:1010): WARNING **: destroyed file still being monitored
(nautilus:1010): Bonobo-WARNING **: Leaked a total of 1 refs to 1 bonobo object(s)
I may also get errors on startup but they disappear too quickly for me to see them, and I'm not sure whether they get written to some file or not, or how to write them to a file. Gnome runs OK, though, as do other windows managers.
The other problem I get when I exit X (no matter what window manager I use) is that the mouse moves a white cursor block around on the (CLI) screen, and will frequently paste stuff to the command line that it has selected (without me do anything but moving the mouse around). This is very strange behaviour. I don't think I noticed before that I could use the mouse while in command line interface mode, but I only just installed slackware a week ago.
So what would be the best course of action for me?
Originally posted by cragwolf The other problem I get when I exit X (no matter what window manager I use) is that the mouse moves a white cursor block around on the (CLI) screen, and will frequently paste stuff to the command line that it has selected (without me do anything but moving the mouse around). This is very strange behaviour. I don't think I noticed before that I could use the mouse while in command line interface mode, but I only just installed slackware a week ago.
So what would be the best course of action for me?
make /etc/rc.d/rc.gpm non executable ("chmod a-x /etc/rc.d/rc.gpm"). That will stop the mouse from being enabled in the console.
Originally posted by Mephisto make /etc/rc.d/rc.gpm non executable ("chmod a-x /etc/rc.d/rc.gpm"). That will stop the mouse from being enabled in the console.
That worked, thank you, but the fact that it was executable before didn't cause me any problems until today. Very strange.
The error and warning messages still bother me, too, especially the gdkpixbuf error. The only error I find in the /var/log/Xorg.0.log file is this:
Code:
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/cragwolf:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
I guess this means my kernel is not compiled with IP v6 support, but that shouldn't be a problem.
Oh well, any further advice would be much appreciated. But thanks for the help so far.
These messages are notmal, I don't know what else to tell you. Technically they are not even error messages. It is just telling you the server is checking for inet6 and not finding it.
I get the same things. The "destroyed file still being monitored" didn't happen until I removed the xscreensaver package and deleted the file from my home directory. I get the other errors you show, as well, but everything still works fine (GNOME warned me that xscreensaver wasn't found at my next bootup, but had an option to never show the message again).
I'm anal about things like this, but I guess if it's not broke, no need to fix it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.