LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-21-2024, 11:37 PM   #1
Fission Chips
LQ Newbie
 
Registered: Aug 2016
Location: Switzerland
Distribution: Slackware 14.2
Posts: 21

Rep: Reputation: Disabled
X not working after slackpkg upgrade-all


I upgraded about 100 packages with slackpkg/slackpkg+, and I must admit I did not really check the .new files, I just glanced over it and hit O to overwrite as nothing caught my eye. Then, since a reboot, X doesn't work anymore.

This happens every once in a while, and usually deleting the .xserverauth and .Xauthority files does the trick, but it didn't, also not chown on the whole user folder. The files were all the user's to begin with.

Also, root and a newly created user cannot startx, so I reinstalled with slackpkg+ off. (slackpkg reinstall x), also reinstalled xrandr, mesa and a few more, didn't help.

What is curious: I have three monitors connected, and when X crashed, I was back in the tty on a different monitor every timeat first. One is HDMI/DVI/DP each. When I usually start, I'm not even sure whether it is alyways the same, but I think it is the HDMI one that gets detected as primary. At any rate it is never the DP one, that is upright/portrait. Now, when I get back into the tty and the DP is primary, the one on HDMI has a duplicate of the screen which flickers, when any of the other ones are active, it's only that one. That was annoying, especially since one is upright, so I disconnected two of them, and when I do that, I don't get the tty back, I just get a blank screen. So I connected a second monitor again, and I get the tty back again, but only after a few minutes.

The output I get is the regular one after X has shut down, only that there is some residual text on the last line which has been overwritten twice apparently, the line goes
Code:
(...) Closing the log file.b64/libQt5Core.co.5)xinit: connectio
To double check whether the output is really the same, I started up my laptop and was surprised to see that I get the same message of a missing ~/.serverauth, but the desktop starts fine.

I'm therefore unsure if the problem even has anything to do with that file or permission.

Here s non-trivial looking content from my /var/log/Xorg.0.log:
Code:
[    70.316] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[    70.316] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    70.316] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    70.316] (**) Power Button: Applying InputClass "keyboard-all"
[    70.316] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    70.316] (II) LoadModule: "libinput"
[    70.317] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
[    70.320] (II) Module libinput: vendor="X.Org Foundation"
[    70.320] 	compiled for 1.21.1.8, module version = 1.4.0
[    70.320] 	Module class: X.Org XInput Driver
[    70.320] 	ABI class: X.Org XInput driver, version 24.4
[    70.320] (II) Using input driver 'libinput' for 'Power Button'
[    70.320] (**) Power Button: always reports core events
[    70.320] (**) Option "Device" "/dev/input/event3"
[    70.332] (II) event3  - Power Button: is tagged by udev as: Keyboard
[    70.332] (II) event3  - Power Button: device is a keyboard
[    70.332] (II) event3  - Power Button: device removed
[    70.352] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[    70.352] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    70.352] (**) Option "xkb_layout" "us"
[    70.352] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[    70.365] (II) event3  - Power Button: is tagged by udev as: Keyboard
[    70.365] (II) event3  - Power Button: device is a keyboard
[    70.365] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[    70.365] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    70.365] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    70.365] (**) Power Button: Applying InputClass "keyboard-all"
[    70.365] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    70.365] (II) Using input driver 'libinput' for 'Power Button'
[    70.365] (**) Power Button: always reports core events
[    70.365] (**) Option "Device" "/dev/input/event2"
[    70.365] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    70.365] (II) event2  - Power Button: device is a keyboard
[    70.366] (II) event2  - Power Button: device removed
[    70.380] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2"
[    70.380] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    70.380] (**) Option "xkb_layout" "us"
[    70.380] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[    70.380] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    70.380] (II) event2  - Power Button: device is a keyboard
[    70.381] (II) config/udev: Adding input device PixArt Dell MS116 USB Optical Mouse (/dev/input/event0)
[    70.381] (**) PixArt Dell MS116 USB Optical Mouse: Applying InputClass "evdev pointer catchall"
[    70.381] (**) PixArt Dell MS116 USB Optical Mouse: Applying InputClass "libinput pointer catchall"
[    70.381] (II) Using input driver 'libinput' for 'PixArt Dell MS116 USB Optical Mouse'
[    70.381] (**) PixArt Dell MS116 USB Optical Mouse: always reports core events
[    70.381] (**) Option "Device" "/dev/input/event0"
[    70.381] (II) event0  - PixArt Dell MS116 USB Optical Mouse: is tagged by udev as: Mouse
[    70.381] (II) event0  - PixArt Dell MS116 USB Optical Mouse: device set to 1000 DPI
[    70.381] (II) event0  - PixArt Dell MS116 USB Optical Mouse: device is a pointer
[    70.381] (II) event0  - PixArt Dell MS116 USB Optical Mouse: device removed
[    70.408] (II) libinput: PixArt Dell MS116 USB Optical Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[    70.408] (II) libinput: PixArt Dell MS116 USB Optical Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[    70.408] (II) libinput: PixArt Dell MS116 USB Optical Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[    70.408] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-1/1-1:1.0/0003:413C:301A.0001/input/input0/event0"
[    70.408] (II) XINPUT: Adding extended input device "PixArt Dell MS116 USB Optical Mouse" (type: MOUSE, id 8)
[    70.408] (**) Option "AccelerationScheme" "none"
[    70.408] (**) PixArt Dell MS116 USB Optical Mouse: (accel) selected scheme none/0
[    70.408] (**) PixArt Dell MS116 USB Optical Mouse: (accel) acceleration factor: 2.000
[    70.408] (**) PixArt Dell MS116 USB Optical Mouse: (accel) acceleration threshold: 4
[    70.408] (II) event0  - PixArt Dell MS116 USB Optical Mouse: is tagged by udev as: Mouse
[    70.408] (II) event0  - PixArt Dell MS116 USB Optical Mouse: device set to 1000 DPI
[    70.409] (II) event0  - PixArt Dell MS116 USB Optical Mouse: device is a pointer
[    70.409] (II) config/udev: Adding input device PixArt Dell MS116 USB Optical Mouse (/dev/input/mouse0)
[    70.409] (II) No input driver specified, ignoring this device.
[    70.409] (II) This device may have been added with another device file.
[    70.409] (II) config/udev: Adding input device HID 046a:0011 (/dev/input/event1)
[    70.409] (**) HID 046a:0011: Applying InputClass "evdev keyboard catchall"
[    70.409] (**) HID 046a:0011: Applying InputClass "libinput keyboard catchall"
[    70.409] (**) HID 046a:0011: Applying InputClass "keyboard-all"
[    70.409] (**) HID 046a:0011: Applying InputClass "libinput keyboard catchall"
[    70.409] (II) Using input driver 'libinput' for 'HID 046a:0011'
[    70.409] (**) HID 046a:0011: always reports core events
[    70.409] (**) Option "Device" "/dev/input/event1"
[    70.410] (II) event1  - HID 046a:0011: is tagged by udev as: Keyboard
[    70.410] (II) event1  - HID 046a:0011: device is a keyboard
[    70.410] (II) event1  - HID 046a:0011: device removed
[    70.424] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-2/1-2:1.0/0003:046A:0011.0002/input/input1/event1"
[    70.424] (II) XINPUT: Adding extended input device "HID 046a:0011" (type: KEYBOARD, id 9)
[    70.424] (**) Option "xkb_layout" "us"
[    70.424] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[    70.424] (II) event1  - HID 046a:0011: is tagged by udev as: Keyboard
[    70.424] (II) event1  - HID 046a:0011: device is a keyboard
[    70.425] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=11 (/dev/input/event10)
[    70.425] (II) No input driver specified, ignoring this device.
[    70.425] (II) This device may have been added with another device file.
[    70.425] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event5)
[    70.425] (II) No input driver specified, ignoring this device.
[    70.425] (II) This device may have been added with another device file.
[    70.425] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event6)
[    70.425] (II) No input driver specified, ignoring this device.
[    70.425] (II) This device may have been added with another device file.
[    70.425] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event7)
[    70.425] (II) No input driver specified, ignoring this device.
[    70.425] (II) This device may have been added with another device file.
[    70.425] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event8)
[    70.425] (II) No input driver specified, ignoring this device.
[    70.425] (II) This device may have been added with another device file.
[    70.425] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=10 (/dev/input/event9)
[    70.425] (II) No input driver specified, ignoring this device.
[    70.425] (II) This device may have been added with another device file.
[    70.426] (II) config/udev: Adding input device HD-Audio Generic Front Mic (/dev/input/event11)
[    70.426] (II) No input driver specified, ignoring this device.
[    70.426] (II) This device may have been added with another device file.
[    70.426] (II) config/udev: Adding input device HD-Audio Generic Rear Mic (/dev/input/event12)
[    70.426] (II) No input driver specified, ignoring this device.
[    70.426] (II) This device may have been added with another device file.
[    70.426] (II) config/udev: Adding input device HD-Audio Generic Line (/dev/input/event13)
[    70.426] (II) No input driver specified, ignoring this device.
[    70.426] (II) This device may have been added with another device file.
[    70.426] (II) config/udev: Adding input device HD-Audio Generic Line Out (/dev/input/event14)
[    70.426] (II) No input driver specified, ignoring this device.
[    70.426] (II) This device may have been added with another device file.
[    70.426] (II) config/udev: Adding input device HD-Audio Generic Front Headphone (/dev/input/event15)
[    70.426] (II) No input driver specified, ignoring this device.
[    70.426] (II) This device may have been added with another device file.
[    70.426] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event4)
[    70.426] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[    70.426] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[    70.426] (**) Eee PC WMI hotkeys: Applying InputClass "keyboard-all"
[    70.426] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[    70.426] (II) Using input driver 'libinput' for 'Eee PC WMI hotkeys'
[    70.426] (**) Eee PC WMI hotkeys: always reports core events
[    70.426] (**) Option "Device" "/dev/input/event4"
[    70.427] (II) event4  - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[    70.427] (II) event4  - Eee PC WMI hotkeys: device is a keyboard
[    70.427] (II) event4  - Eee PC WMI hotkeys: device removed
[    70.440] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input4/event4"
[    70.440] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 10)
[    70.440] (**) Option "xkb_layout" "us"
[    70.440] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[    70.440] (II) event4  - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[    70.440] (II) event4  - Eee PC WMI hotkeys: device is a keyboard
[    70.487] (--) NVIDIA(GPU-0): Asustek Computer Inc ASUS VG289Q1A (DFP-1): connected
[    70.487] (--) NVIDIA(GPU-0): Asustek Computer Inc ASUS VG289Q1A (DFP-1): Internal TMDS
[    70.487] (--) NVIDIA(GPU-0): Asustek Computer Inc ASUS VG289Q1A (DFP-1): 600.0 MHz maximum pixel clock
[    70.487] (--) NVIDIA(GPU-0): 
[    70.530] (--) NVIDIA(GPU-0): Asustek Computer Inc ASUS VG289Q1A (DFP-1): connected
[    70.530] (--) NVIDIA(GPU-0): Asustek Computer Inc ASUS VG289Q1A (DFP-1): Internal TMDS
[    70.530] (--) NVIDIA(GPU-0): Asustek Computer Inc ASUS VG289Q1A (DFP-1): 600.0 MHz maximum pixel clock
[    70.530] (--) NVIDIA(GPU-0): 
[    70.669] (II) event3  - Power Button: device removed
[    70.684] (II) event2  - Power Button: device removed
[    70.696] (II) event0  - PixArt Dell MS116 USB Optical Mouse: device removed
[    70.720] (II) event1  - HID 046a:0011: device removed
[    70.732] (II) event4  - Eee PC WMI hotkeys: device removed
[    70.756] (II) UnloadModule: "libinput"
[    71.039] (II) NVIDIA(GPU-0): Deleting GPU-0
[    71.043] (II) Server terminated successfully (0). Closing log file.
I also updated the NVIDIA driver, after that, the crash was faster and I get back to the same monitor,but not much more and now I could need some help on further steps. Thanks a lot!
 
Old 05-22-2024, 12:34 AM   #2
henca
Senior Member
 
Registered: Aug 2007
Location: Linköping, Sweden
Distribution: Slackware
Posts: 1,029

Rep: Reputation: 693Reputation: 693Reputation: 693Reputation: 693Reputation: 693Reputation: 693
Are you on current? Did you also upgrade the gcc package?

https://www.linuxquestions.org/quest...nt-4175737238/

Did your kernel packages get updated? If so, did you consider the following text from ChangeLog.txt:

+--------------------------+
Tue Dec 26 00:20:26 UTC 2023
patches/packages/kernel-firmware-20231222_a7dee43-noarch-1.txz: Upgraded.
Updated to the latest kernel firmware.
patches/packages/linux-5.15.145/*: Upgraded.
These updates fix various bugs and security issues.
Thanks to jwoithe for the PCI fix!
Be sure to upgrade your initrd after upgrading the kernel packages.
If you use lilo to boot your machine, be sure lilo.conf points to the correct
kernel and initrd and run lilo as root to update the bootloader.
If you use elilo to boot your machine, you should run eliloconfig to copy the
kernel and initrd to the EFI System Partition.
For more information, see:
Fixed in 5.15.140:
https://www.cve.org/CVERecord?id=CVE-2023-46862
Fixed in 5.15.141:
https://www.cve.org/CVERecord?id=CVE-2023-6121
(* Security fix *)
+--------------------------+
(The above text is from ChangeLog.txt in Slackware 15.0, users of current are supposed to know that.)

If your booted kernel does not match the installed modules different strange things can happen. If you are using a generic kernel with an initrd instead of a huge kernel there is yet another set of installed modules to consider.

regards Henrik
 
Old 05-22-2024, 01:48 AM   #3
Petri Kaukasoina
Senior Member
 
Registered: Mar 2007
Posts: 1,962

Rep: Reputation: 1574Reputation: 1574Reputation: 1574Reputation: 1574Reputation: 1574Reputation: 1574Reputation: 1574Reputation: 1574Reputation: 1574Reputation: 1574Reputation: 1574
Are you using kde? Have you tried something else? Change with xwmconfig and try startx.
 
  


Reply

Tags
nvidia, slackpkg, xorg



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
I stopped a slackpkg upgrade-all in midstream and now I cannot slackpkg upgrade-all jkh2cpu Slackware 5 02-13-2022 03:05 AM
Weird slackpkg upgrade message during a slackpkg upgrade-all process. frtorres Slackware 8 02-13-2021 11:36 AM
SARPI on Pi3 - Ran slackpkg update & slackpkg upgrade-all and now won't boot, can't find init petejc Slackware - ARM 11 03-25-2020 04:30 AM
[SOLVED] Slackpkg upgrade-all returns 'no packages to upgrade' after slackpkg-update has downloaded files san2ban Slackware 8 11-01-2019 05:44 AM
[SOLVED] After upgrade all using slackpkg upgrade, configuration is failed to read ethereal1m Linux - Newbie 3 04-28-2010 01:03 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:45 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration