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.
yeah that / this issue I have not had since v14 permission denied and that was so long ago I cannot remember the file I removed one line on then it bypassed the root thing
Yes, I was hoping that the problem would have been seen before and somebody could say "check the existence/permissions on <file>", but it was only a hope. Or maybe "that's handled by <package>, try re-installing that one." But no joy.
Quote:
Originally Posted by BW-userx
might be faster to try installing again then fiddling around .
thing
That's what I'm thinking. I did try re-installing all the xorg-server packages, and that did not help. So, to hell with it. Unless I get some clever suggestions in the next twelve hours, that's how I'll start my workday tomorrow.
Yes, I was hoping that the problem would have been seen before and somebody could say "check the existence/permissions on <file>", but it was only a hope. Or maybe "that's handled by <package>, try re-installing that one." But no joy.
That's what I'm thinking. I did try re-installing all the xorg-server packages, and that did not help. So, to hell with it. Unless I get some clever suggestions in the next twelve hours, that's how I'll start my workday tomorrow.
Sometimes that's the best fix, I'd separate the root with the home. This way if for any reason you find yourself reinstalling again everything in home is kept safe. All you need to do is reattach it during install.
Sometimes that's the best fix, I'd separate the root with the home. This way if for any reason you find yourself reinstalling again everything in home is kept safe. All you need to do is reattach it during install.
I've kept root on its own partition for many years, so that upgrading to a new Slackware release wouldn't hose the system. I am tempted to swap in a new hard drive and start from scratch, but I don't feel like disassembling the laptop to do it. I miss the old ThinkPads where it was a single screw in a slot on the side to change the drive.
I'll back up the important directories to an external disk, copy the /etc directory, and do the re-install today. Annoying, but it's the option I have left.
I get this
bash-5.1$ setxkbmap us -print
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+inet(evdev)+terminate(ctrl_alt_bksp)" };
xkb_geometry { include "pc(pc105)" };
};
I've kept root on its own partition for many years, so that upgrading to a new Slackware release wouldn't hose the system. I am tempted to swap in a new hard drive and start from scratch, but I don't feel like disassembling the laptop to do it. I miss the old ThinkPads where it was a single screw in a slot on the side to change the drive.
I'll back up the important directories to an external disk, copy the /etc directory, and do the re-install today. Annoying, but it's the option I have left.
I wish I knew what caused the problem, though.
yeah I seen those hot swaps where the hdd was on the side and all one had to do was pull it then slap another one in. then HP use to have a slide lock now they're doing 6 to 8 screws.
you do actually go through the steps to set up the keyboard and make sure it is working? a new hard drive is just a new hard drive that won't make a difference as far as compatibility with this issue.
do just take it slow and don't do the just hit the enter key to get to the next step install process. that might help catch something
have you tried a live slack iso to see if that works fine on the laptop? it is said that you can install / copy the system off of that too.
you do actually go through the steps to set up the keyboard and make sure it is working? a new hard drive is just a new hard drive that won't make a difference as far as compatibility with this issue.
do just take it slow and don't do the just hit the enter key to get to the next step install process. that might help catch something
have you tried a live slack iso to see if that works fine on the laptop? it is said that you can install / copy the system off of that too.
I did a fresh install, exactly as I did when I installed 15.0 the first time (I take pretty complete notes when I do an install), and the problem remains.
I haven't tried liveslak. I tried to boot Knoppix, and it won't boot the dvd (though it had no trouble booting from the slackware install disc when I did the re-install). So, I have no idea. I'll try liveslak. Can't hurt to try.
I have owned this laptop (it's a Thinkpad w550s) since 2016. I ran Slackware 14.2 on it until last February, when I took out the old disk and put in a new one for slackware 15.0. Swapping out a disk should make no difference, but at this point, I'm desperate enough to try.
I get this
bash-5.1$ setxkbmap us -print
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+inet(evdev)+terminate(ctrl_alt_bksp)" };
xkb_geometry { include "pc(pc105)" };
};
I can only run setxkbmap if X is running, and I can't get X to run as regular user. If I run it without X, I get 'cannot open display "default display"'. If I run it as root with X running, I get output like what you list.
I did a fresh install, exactly as I did when I installed 15.0 the first time (I take pretty complete notes when I do an install), and the problem remains.
I haven't tried liveslak. I tried to boot Knoppix, and it won't boot the dvd (though it had no trouble booting from the slackware install disc when I did the re-install). So, I have no idea. I'll try liveslak. Can't hurt to try.
I have owned this laptop (it's a Thinkpad w550s) since 2016. I ran Slackware 14.2 on it until last February, when I took out the old disk and put in a new one for slackware 15.0. Swapping out a disk should make no difference, but at this point, I'm desperate enough to try.
it's been years but try this. Open startx and edit it
sudo nano /usr/bin/startx
then comment out this line enable_xauth=1 , or change it to enable_xauth=0
save then try startx
question: i keep seeing keyboard is it the keyboard that is not working or startx don't give you a gui?
Did you add something about xkeyboard in your config files? Do you have /etc/X11/xorg.conf.d/20-xkmap.conf, or maybe an Xorg.conf with a mention of xkeyboard in it because I do not. I don't have an Xorg.conf. I don't get any errors about xkeyboard on startup, and I've never even seen a file from xkeyboard in /tmp. If reinstalling binaries is not fixing the problem, then that must not be it. I'm guessing you have a bad config file someplace. The server tries to write out a keymap, but can only do so under root.
Just in case, check the usual permission problem areas:
Code:
ls /etc/X11/xorg.conf.d/
10-libvnc.conf 30-dualshock-4-touchpad.conf 51-joystick.conf
ls -la /tmp/.ICE-unix/
total 24
drwxrwxrwt 2 root root 4096 May 19 12:36 ./
drwxrwxrwt 30 root root 20480 Jul 8 14:01 ../
srwxrwxrwx 1 root root 0 May 19 12:36 1791=
ls -la /tmp/.X11-unix/
total 24
drwxrwxrwt 2 root root 4096 Jul 8 13:13 ./
drwxrwxrwt 30 root root 20480 Jul 8 14:01 ../
srwxrwxrwx 1 root users 0 Jul 8 13:13 X0=
ls -la /usr/libexec/Xor*
-rwsr-xr-x 1 root root 2325120 Mar 29 14:01 /usr/libexec/Xorg*
-rwsr-xr-x 1 root root 14544 Mar 29 14:01 /usr/libexec/Xorg.wrap*
Startup log snippet:
Code:
[224863.061] (II) event1 - Power Button: device is a keyboard
[224863.061] (II) event1 - Power Button: device removed
[224863.078] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[224863.078] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[224863.078] (**) Option "xkb_layout" "us"
[224863.078] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[224863.099] (II) event1 - Power Button: is tagged by udev as: Keyboard
[224863.099] (II) event1 - Power Button: device is a keyboard
[224863.100] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[224863.100] (**) Power Button: Applying InputClass "evdev keyboard catchall"
I use "startx" when I want X11, and set which window manager I like via ~/.xinitrc.
Code:
cat ~/.xinitrc
#!/bin/sh
# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/Xresources
sysmodmap=/etc/X11/xinit/Xmodmap
# merge in defaults and keymaps
if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi
if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi
if [ -f $userresources ]; then
xrdb -merge $userresources
fi
if [ -f $usermodmap ]; then
xmodmap $usermodmap
fi
# Start the window manager or desktop environment
xsetroot -def
# Edit graphics tablet button function to add ctrl-z
xsetwacom set "Wacom Intuos S Pad pad" "Button" "1" "key ctrl z"
# Emotif
manager=/usr/bin/emwm
# Motif
#manager=/usr/bin/mwm
# WindowMaker
#manager=/usr/bin/wmaker
if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
ck-launch-session $manager
else
dbus-launch --exit-with-session $manager
fi
Go through X11 startup piece by piece; execute startx line by line and see where, exactly, it bombs out.
Did you add something about xkeyboard in your config files? Do you have /etc/X11/xorg.conf.d/20-xkmap.conf, or maybe an Xorg.conf with a mention of xkeyboard in it because I do not. I don't have an Xorg.conf. I don't get any errors about xkeyboard on startup, and I've never even seen a file from xkeyboard in /tmp. If reinstalling binaries is not fixing the problem, then that must not be it. I'm guessing you have a bad config file someplace. The server tries to write out a keymap, but can only do so under root.
Just in case, check the usual permission problem areas:
Code:
ls /etc/X11/xorg.conf.d/
10-libvnc.conf 30-dualshock-4-touchpad.conf 51-joystick.conf
ls -la /tmp/.ICE-unix/
total 24
drwxrwxrwt 2 root root 4096 May 19 12:36 ./
drwxrwxrwt 30 root root 20480 Jul 8 14:01 ../
srwxrwxrwx 1 root root 0 May 19 12:36 1791=
ls -la /tmp/.X11-unix/
total 24
drwxrwxrwt 2 root root 4096 Jul 8 13:13 ./
drwxrwxrwt 30 root root 20480 Jul 8 14:01 ../
srwxrwxrwx 1 root users 0 Jul 8 13:13 X0=
ls -la /usr/libexec/Xor*
-rwsr-xr-x 1 root root 2325120 Mar 29 14:01 /usr/libexec/Xorg*
-rwsr-xr-x 1 root root 14544 Mar 29 14:01 /usr/libexec/Xorg.wrap*
Startup log snippet:
Code:
[224863.061] (II) event1 - Power Button: device is a keyboard
[224863.061] (II) event1 - Power Button: device removed
[224863.078] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[224863.078] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[224863.078] (**) Option "xkb_layout" "us"
[224863.078] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[224863.099] (II) event1 - Power Button: is tagged by udev as: Keyboard
[224863.099] (II) event1 - Power Button: device is a keyboard
[224863.100] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[224863.100] (**) Power Button: Applying InputClass "evdev keyboard catchall"
I use "startx" when I want X11, and set which window manager I like via ~/.xinitrc.
Code:
cat ~/.xinitrc
#!/bin/sh
# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/Xresources
sysmodmap=/etc/X11/xinit/Xmodmap
# merge in defaults and keymaps
if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi
if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi
if [ -f $userresources ]; then
xrdb -merge $userresources
fi
if [ -f $usermodmap ]; then
xmodmap $usermodmap
fi
# Start the window manager or desktop environment
xsetroot -def
# Edit graphics tablet button function to add ctrl-z
xsetwacom set "Wacom Intuos S Pad pad" "Button" "1" "key ctrl z"
# Emotif
manager=/usr/bin/emwm
# Motif
#manager=/usr/bin/mwm
# WindowMaker
#manager=/usr/bin/wmaker
if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
ck-launch-session $manager
else
dbus-launch --exit-with-session $manager
fi
Go through X11 startup piece by piece; execute startx line by line and see where, exactly, it bombs out.
I did a fresh install, exactly as I did when I installed 15.0 the first time (I take pretty complete notes when I do an install), and the problem remains.
For your fresh install, I presume you didn't do slackpkg update/upgrade-all so that you stayed with the packages when slackware 15.0 was first released?
Also, did you maintain your home directory (prior to fresh install) and re-attach?
Have you tried with a different user other than the problem user or root? I apologize if you mentioned that earlier and I missed that.
For your fresh install, I presume you didn't do slackpkg update/upgrade-all so that you stayed with the packages when slackware 15.0 was first released?
Also, did you maintain your home directory (prior to fresh install) and re-attach?
Have you tried with a different user other than the problem user or root? I apologize if you mentioned that earlier and I missed that.
Maybe too late for Panthan but posting for others in future.
After a power outage had bumped off my computer, after booting it back on, I had exactly the same problem as Panthan's first post with the same error as posted. I tried a few things that didn't worked. Searched for solutions online and found this thread. I tried almost all of the solutions offered in replies with the same results as Panthan's reports. Everything looked right. I was on the verge of reformatting the root partition when I vaguely remembered something else. I have my /tmp on its own partition (to stop it from growing too much and killing off root partition) and I checked to see if it was full. It was 100% full. Nothing could be written to it. Emptying /tmp gave me back my desktop.
Hope this helps someone else. Thanks for this thread!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
