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.
So I've made a different post about a different problem, and it sort of led into this problem. I figure this needs it's own posting because people keep responding to the already fixed problem in the other post. Anyway on to the problem...
I've got a fresh install of Slack64 13.37, in which I installed the latest gnome slack build (with gnome 3.0). I also installed the latest NVIDIA proprietary driver (yes it must be this one, I plan on gaming on this rig) for my NVIDIA GeForce 9500 GT. The card with the nvidia driver, the monitor, and slackware have had some problems getting along before, but the solution for that problem was to tell X where to find the raw edid data from the monitor. I have kept this configuration and it seems to work fine for logging in graphically (via gdm). The problem now is that as soon as I log in to gnome, it loads the background and displays it, but then does nothing. The mouse can be moved, but neither button has any effect. The computer has not locked up, I can still restart X or switch to a console login. It just does nothing after loading the desktop background. There are no errors or significant warnings in Xorg.0.log. There are no logs for GDM, and I haven't been able to find any related errors in any of the system logs. It would seem it's having an error that it's not logging.
That sounds more like a window manager problem to me.
Did you also look into ~/.xsession-errors?
Indeed you are correct, I was unaware of this log file. Here's what I've discovered, though this doesn't make any sense:
From .xsession-errors:
Code:
gnome-session[3541]: WARNING: Application 'gnome-settings-daemon.desktop' failed to register before timeout
/usr/bin/gnome-shell: symbol lookup error: /usr/lib64/libgjs.so.0: undefined symbol: JS_SetScriptStackQuota
Failed to play sound: File or data not found
** Message: applet now removed from the notification area
Traceback (most recent call last):
File "/usr/bin/blueman-applet", line 25, in <module>
import pynotify
File "/usr/lib64/python2.6/site-packages/gtk-2.0/pynotify/__init__.py", line 1, in <module>
from _pynotify import *
ImportError: libnotify.so.1: cannot open shared object file: No such file or directory
Traceback (most recent call last):
File "/usr/share/system-config-printer/applet.py", line 29, in <module>
import pynotify
File "/usr/lib64/python2.6/site-packages/gtk-2.0/pynotify/__init__.py", line 1, in <module>
from _pynotify import *
ImportError: libnotify.so.1: cannot open shared object file: No such file or directory
So it would seem the problem is that there is no libnotify installed, so I took a look via slapt-get:
The only one not installed is an older version of the one that is installed... so this leaves me with confusion. Also slapt-get nor slackbuilds.org can find the other library mentioned (libgjs) which seems to be a gnome javascript binding of some sort?
upon further inspection /usr/lib64/libnotify.so.1 does not exist, as it complained. But if I revert to the old version of libnotify that file does exist, but removes libnotify.so.4. Then if I try to login with the old version installed, then it complains about not being able to find libnotify.so.4 which indeed does not exist then. So it would seem I need both, but that can't happen unless I have both installed? So what I did was install the old version, made a copy of libnotify.so.1 named it libnotify.so.1.bak, then reinstalled the newest version of libnotify. Then I checked the /usr/lib64 directory again and found both libnotify.so.1 and libnotify.so.4 as well as my backup copy (for some reason making the backup copy keeps libnotify.so.1 around after installing the new version). Then I restarted X and gave it another go, this time .xsession-errors shows less errors (but I have a feeling I've moved in the wrong direction with this 'fix'):
With some more research it turns out that part of this problem with gnome-settings-daemon timing out was because the cups daemon was not started. So I started the cups daemon, and now there are other problems:
.xsession-errors:
Code:
/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- /etc/X11/xinit/xinitrc.gnome
GNOME_KEYRING_CONTROL=/tmp/keyring-Uj1uDJ
SSH_AUTH_SOCK=/tmp/keyring-Uj1uDJ/ssh
GNOME_KEYRING_PID=2880
GNOME_KEYRING_CONTROL=/tmp/keyring-Uj1uDJ
SSH_AUTH_SOCK=/tmp/keyring-Uj1uDJ/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-Uj1uDJ
SSH_AUTH_SOCK=/tmp/keyring-Uj1uDJ/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-Uj1uDJ
SSH_AUTH_SOCK=/tmp/keyring-Uj1uDJ/ssh
GPG_AGENT_INFO=/tmp/keyring-Uj1uDJ/gpg:0:1
=== auto configure Configuration ===
Clone: false
Output: Unknown attached to default
status: on
width: 1280
height: 1024
rate: 50
primary: false
position: 0 0
=== Applying Configuration Configuration ===
Clone: false
Output: Unknown attached to default
status: on
width: 1280
height: 1024
rate: 50
primary: true
position: 0 0
/usr/bin/gnome-shell: symbol lookup error: /usr/lib64/libgjs.so.0: undefined symbol: JS_SetScriptStackQuota
Failed to play sound: File or data not found
warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
HP Linux Imaging and Printing System (ver. 3.11.3a)
System Tray Status Service ver. 2.0
Copyright (c) 2001-9 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
** Message: applet now removed from the notification area
system-config-printer-applet: failed to start NewPrinterNotification service
Loading configuration plugins
blueman-applet version 1.22 starting
Stale PID, overwriting
Using gconf config backend
Using gconf config backend
Using gconf config backend
Using gconf config backend
Using gconf config backend
Using gconf config backend
Using gconf config backend
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/blueman/plugins/BasePlugin.py", line 65, in _load
self.on_load(parent)
File "/usr/lib64/python2.6/site-packages/blueman/plugins/applet/KillSwitch.py", line 52, in on_load
raise Exception("Failed to initialize killswitch manager")
Exception: Failed to initialize killswitch manager
I don't know how much gnome-shell uses javascript, but I still see your system whining about /usr/lib64/libgjs.so.0. Given that gnome-shell can't find a symbol in there that it thinks should be in libgjs.so, you might have a version mismatch.
I don't know how much gnome-shell uses javascript, but I still see your system whining about /usr/lib64/libgjs.so.0. Given that gnome-shell can't find a symbol in there that it thinks should be in libgjs.so, you might have a version mismatch.
Yeah but I'm not real sure what package libgjs comes with... I thought it came with one of the gnome packages considering it's gnome specific, but I can't find anywhere to download just libgjs. Seems that all the download links I can find for it are distro specific and prebuilt. But it wouldn't make much sense if it was the wrong version that came with the gnome-slackbuild considering I have yet to find a multitude of people complaining about this problem with the latest gsb.
According to the gsb64 MANIFEST file, it's in gsb64/l/gjs-0.7.14-x86_64-2gsb.txz. I've had cases during install when a partition was filled; when that happens, you are best off reinstalling everything after making the partition larger. Did something similar happen to you?
According to the gsb64 MANIFEST file, it's in gsb64/l/gjs-0.7.14-x86_64-2gsb.txz. I've had cases during install when a partition was filled; when that happens, you are best off reinstalling everything after making the partition larger. Did something similar happen to you?
This shouldn't have happened, I had two partitions on the drive that things were installed to. It's a 120GB hdd, with two partitions (/boot 5GB) and (/ 115 GB) so I seriously doubt this was the case in my setup. Keep in mind, GSB was the third thing installed following slackware64 and the NVIDIA proprietary driver.
I just spent the last few days upgrading my installation to 13.37 + GSB 2.32, but I encountered the very exact problem you mentioned. After maaaaany attempts, I gave up and switched to GSB 2.30 (I was using Slackware 13.1 ] GSB 2.28 before that), thinking 2.32 was not yet mature enough, only to stumble upon the same problem.
I finally noticed thiat gjs uses SeaMonkey, and that:
Code:
bash-4.1# slapt-get --search seamonkey
libidl-0.8.14-i486-1 [inst=yes]: libIDL (IDL library)
seamonkey-2.1b3-i486-2 [inst=yes]: SeaMonkey (an open-source web browser suite)
seamonkey-2.5-i486-1_slack13.37 [inst=no]: SeaMonkey (an open-source web browser suite)
seamonkey-solibs-2.1b3-i486-2 [inst=yes]: seamonkey-solibs (Shared libraries from Seamonkey)
seamonkey-solibs-2.5-i486-1_slack13.37 [inst=no]: seamonkey-solibs (Shared libraries from Seamonkey)
So it seems SeaMonkey has received a security update. As you might guess, downgrading 2.5 to 2.1b3 solved the problem.
I will report this to the GSB guys ASAP. At the moment I'm still having a very bad GNOME experience, but probably because of video driver issues (using a 24" iMac here). Anyway I hope it helps .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Downgrade SeaMonkey!
.
