You are not logged in.
Hi there, since that Syu I did two days ago, after i start kde my pc freezes about 2-10Minutes after starting kde. The symptoms:
no programm is responsible to any input. I can still change the tty and enter a username but no password prompt comes up, if i log in before the freeze, it does not respond to any command(i can enter them though). Started up openbox, it only did that once but did it, too.
Nothing suspicious in Xorg.log nor journalctl. Since dmesg only goes bakc up to the last boot it is ueeless here. I can not ssh into the pc after freezing it roes not respond.
Already tried https://www.reddit.com/r/archlinux/comm … dia_39025/ but that downgrade did nothing for me.
How to get my kde back to work again?
journalctl -b1: http://ix.io/Rro
Xorg.0.log: http://ix.io/Rrq
If anything else is needed or there is any idea where to look or how to solve it please tell me I need my pc back again.
Thank you in advance
Last edited by nerdnils (2018-03-03 13:38:49)
Offline
Nobody? Not even a clue or some new place/log to look at? Really would be great to get this fixed again, never had such an reproducable unstable system.
If I boot into a tty only, no freezing occurs but when I start kde it still comes up after a few minutes. Alredy tried disabling vsync, disabling compositing... Changes nothing
Last edited by nerdnils (2018-03-02 18:30:09)
Offline
Nobody?
Please do not bump a thread. Do you believe a sub 1 hour response time from a volunteer community which would be the same response you could find on a high tier service level agreement is reasonable?
The journal entry for the previous boot is incomplete did you truncate it or was the journal corrupted? Which packages were upgrade in this update two days ago?
Does reverting all the packages in that upgrade resolve the issue?
Offline
Please do not bump a thread. Do you believe a sub 1 hour response time from a volunteer community which would be the same response you could find on a high tier service level agreement is reasonable?
Please excuse me. I did not want to be pushy. I was panicking a bit. Some data(in this case it is even medical data. But please don't care I should have thought about copying it to a USB-stick and use it on another pc before) and work to do... Please excuse me.
The journal entry for the previous boot is incomplete did you truncate it or was the journal corrupted?
No, this is journalctl -b 1|ix. Perhaps it is because I had to restart using a hard reset because of the freeze?? Had to do that waaay to often now. I hope this can be solved before I am causing any damage to my hardware.
Which upgrade in this update two days ago?
Please see my pacman. log from 2018 under http://ix.io/Rtu The error happens since the Syu from march the first.
Does reverting all the packages in that upgrade resolve the issue?
I did not try that yet except for the downgrade I mentioned above. What is the best way to do/test this?
Last edited by nerdnils (2018-03-02 19:13:50)
Offline
Have you tried checking "journalctl --since=today" to find more complete logs?
Offline
Note sure if this is the original issue or a later issue.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Concurrent.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Widgets.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5OpenGL.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5DBus.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5EglFSDeviceIntegration.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5EglFSDeviceIntegration.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Gui.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Sql.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Widgets.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5EglFSDeviceIntegration.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5EglFsKmsSupport.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Xml.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Widgets.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5PrintSupport.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5EglFSDeviceIntegration.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Sql.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5XcbQpa.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5EglFsKmsSupport.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Test.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5XcbQpa.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Test.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5EglFsKmsSupport.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Xml.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Core.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Network.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5PrintSupport.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Concurrent.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Test.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5EglFsKmsSupport.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5XcbQpa.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Core.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5OpenGL.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5XcbQpa.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5PrintSupport.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Xml.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5DBus.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Network.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Concurrent.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Network.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Sql.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5OpenGL.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Widgets.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Test.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5PrintSupport.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Core.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Gui.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5DBus.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Core.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Xml.so.5 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Sql.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Network.so.5.10.1 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5OpenGL.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Gui.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Gui.so ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5DBus.so.5.10 ist leer; keine Überprüfung.
[2018-03-02 16:46] [ALPM-SCRIPTLET] ldconfig: Datei /usr/lib/libQt5Concurrent.so.5 ist leer; keine Überprüfung.
pacman -Qkk #check if pacman can detect corruption in those files
journalctrl -b1 #is the first boot in the journal
journalctrl -b-1 #the journal for the previous boot
journalctrl -b-3 > journal.log #journal from 3 boots ago redirect stdout to journal.log
Edit:
[2018-01-20 09:39] [PACMAN] Running 'pacman -S --force libx264'
[2018-02-11 11:32] [PACMAN] Running 'pacman -U --force openclonk-8.0-1-x86_64.pkg.tar.xz'
[2018-03-02 16:46] [PACMAN] Running 'pacman -S --force x-server nvidia xorg'
[2018-03-02 16:54] [PACMAN] Running 'pacman -S --force kinit'
[2018-03-02 16:57] [PACMAN] Running 'pacman -S --force kinit'
[2018-03-02 17:01] [PACMAN] Running 'pacman -S --force qt5 kinit'
Using --force especially with package groups is never required. If there is not a news item instructing you to use --force consider is it appropriate or is it just a quick fix that can lead to long term breakage?
Last edited by loqs (2018-03-02 19:29:15)
Offline
Have you tried checking "journalctl --since=today" to find more complete logs?
http://ix.io/RtS
http://ix.io/RtT
Had to split it in two because it was too large for the pastebin
Sorry for some parts being in german
And yeah, this morning from about 6:30 to 6:47 it did not freeze and had a complete shutdown. I don't know why it didn't freeze there and can not reproduce it. Freeze occured before and afterwards and a whole lot of times.
Last edited by nerdnils (2018-03-02 20:44:49)
Offline
Note sure if this is the original issue or a later issue.
I had to do a whole lot of hard resets because of freezings. This causee other errors. Some files were corrupted/erased(ext4). pacman would not reinstall the packages because it said the files are already there/empty and some more errors. This forcing fixed those errors. Now I am back to the error before the filesystem got corrupted. Didn't and don't know any way to fix this without --force. Thecorrupted file system was root anit is ext4. The errors I am reporting here already existed before this and caused this. But those are fixed with the reinstall of those packages.
Offline
So the issue existed since at least
[2018-01-20 09:39] [PACMAN] Running 'pacman -S --force libx264'
The package corruption included every package in the xorg group and every package in the qt5 group?
$ pacman -Qg xorg
xorg xorg-bdftopcf
xorg xorg-font-util
xorg xorg-fonts-encodings
xorg xorg-iceauth
xorg xorg-mkfontdir
xorg xorg-mkfontscale
xorg xorg-server
xorg xorg-server-common
xorg xorg-server-xvfb
xorg xorg-server-xwayland
xorg xorg-setxkbmap
xorg xorg-xauth
xorg xorg-xev
xorg xorg-xhost
xorg xorg-xkbcomp
xorg xorg-xmodmap
xorg xorg-xrdb
xorg xorg-xset
$ pacman -Qg qt5
qt5 qt5-base
qt5 qt5-declarative
qt5 qt5-location
qt5 qt5-multimedia
qt5 qt5-tools
qt5 qt5-webchannel
qt5 qt5-webengine
qt5 qt5-xmlpatterns
If it was fixing the issue why did you have to run it twice?
[2018-03-02 16:54] [PACMAN] Running 'pacman -S --force kinit'
[2018-03-02 16:57] [PACMAN] Running 'pacman -S --force kinit'
Offline
So the issue existed since at least
[2018-01-20 09:39] [PACMAN] Running 'pacman -S --force libx264'
The package corruption included every package in the xorg group and every package in the qt5 group?
$ pacman -Qg xorg xorg xorg-bdftopcf xorg xorg-font-util xorg xorg-fonts-encodings xorg xorg-iceauth xorg xorg-mkfontdir xorg xorg-mkfontscale xorg xorg-server xorg xorg-server-common xorg xorg-server-xvfb xorg xorg-server-xwayland xorg xorg-setxkbmap xorg xorg-xauth xorg xorg-xev xorg xorg-xhost xorg xorg-xkbcomp xorg xorg-xmodmap xorg xorg-xrdb xorg xorg-xset $ pacman -Qg qt5 qt5 qt5-base qt5 qt5-declarative qt5 qt5-location qt5 qt5-multimedia qt5 qt5-tools qt5 qt5-webchannel qt5 qt5-webengine qt5 qt5-xmlpatterns
If it was fixing the issue why did you have to run it twice?
[2018-03-02 16:54] [PACMAN] Running 'pacman -S --force kinit' [2018-03-02 16:57] [PACMAN] Running 'pacman -S --force kinit'
I don't really know which packages where corrupted. Had seen those librarie issues you pointed out, had a look which packes they belong to and reinstalled kinid, plasma and Xorg and it worked again afterwardX and kde came back up, first virtual keyboard could not be initialized then kinit5 was "not installed".
I ran it twice because there was an error the first time. I am sorry I don't remember what it was. Another package missing or some dependency? I don't wanna lie I don't remember.
Offline
There are multiple users on this pc. I just tried letting only the one using openbox work. Worked for a very long time. But when the kde-user comes on and kde gets started it is only2-4minutes and everything freezes as described(even the other user with all his programs). So this somehow seems to be kde-related? But what is it?
As I said openbox did it once, too. But kde now did it I have stopped counting but around 30-50times?
Offline
I switched to enlightenment because of this bug and it did the same thing with the same freeze to me. So this is not kde-related. Any further ideas? Does nobody have this error but me?
Does anybody see anything in the logs?
Since this is freezing even ttys havin no x, could this be the kernel?
Last edited by nerdnils (2018-03-03 11:53:22)
Offline
This isn't the fault of any single user space program. A large amount of libraries on your system are corrupted. Run a memcheck and verify the integrity of your harddisks with SMART another potential cause might be the kernel maybe there was regression with your hardware constellation, you might want to see if you can restore stability by switching to the LTS kernel.
Your logs don't contain any direct kernel errors from what I can tell, so I'm not entirely sure that that might be the cause.
Offline
OK, pc runs forever if I only use tty and no display manager so it does not seem like a hdd or ram-issue. I tested in a tty after a freeze. echo works. dmesg does not answer, ps gives no answer... ctrl+c works to cancel the commands. Just switched to linux-lts as suggested. nvidia drivers are not loaded proprly and resolution is very bad as a result. How to get nvidia driver to work with lts kernel?
And it does not matter, lts kernel freezes, too damn I just want to work with my pc for more than 5minutes again and not need to hard reset it every time
Last edited by nerdnils (2018-03-03 12:41:29)
Offline
OK, pc runs forever if I only use tty and no display manager
You keep saying "Display Manager" but there is nothing in this thread that would specifically implicate a DM. You are comparing just running in the tty to running Xorg with a full fledged DE. Have you tried starting X with startx/xinit? I doubt it's relevant as I'm pretty sure you'd have the same problem. But that would demonstrate that this is *not* a display manager issue - so you should fix your title, especially as your title indicates that you have tried every (or at least many) display managers, but there is no indication in this thread that you have.
How to get nvidia driver to work with lts kernel
https://wiki.archlinux.org/index.php/NV … stallation
Last edited by Trilby (2018-03-03 12:48:45)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
I tested kde(kde/openbox and plasma) openbox and environment. Also tried running them directly with startx and through sddm. What else should I test or what should I rename the topic to?
The error was already there before the corruptions with the files contradicting what v1del said. The corruptions came because of the hard resets(I had no choice because of no program or cammond doing anything useful).
Last edited by nerdnils (2018-03-03 13:28:39)
Offline
I tested kde(kde/openbox and plasma) openbox and environment. What else should I test or what should I rename the topic to?
Please research the difference between a Display Manager,a Desktop Environment and a Window Manager.
The error was already there before the corruptions with the files contradicting what v1del said. The corruptions came because of the hard resets(I had no choice because of no program or cammond doing anything useful).
Where did V1del state the error was not there before the file corruption occurred?
Offline
Where did V1del state the error was not there before the file corruption occurred?
He said this is because libraries were/are corrupted. They were not when this error started. If this is the cause how to dtect which are corrupted and how to repair them?
I hope the topic is better now and we can get back to solving the problem but I start thinking this is only solveable by reinstalling the whole system
Last edited by nerdnils (2018-03-03 13:36:01)
Offline
He said this is because libraries were/are corrupted. They were not when this error started. If this is the cause how to dtect which are corrupted and how to repair them?
Where in the following does V1del state the error was not present before the corruption of a large number of libraries.
This isn't the fault of any single user space program. A large amount of libraries on your system are corrupted. Run a memcheck and verify the integrity of your harddisks with SMART another potential cause might be the kernel maybe there was regression with your hardware constellation, you might want to see if you can restore stability by switching to the LTS kernel.
Your logs don't contain any direct kernel errors from what I can tell, so I'm not entirely sure that that might be the cause.
I already gave you a method to detect corrupted files tracked by pacman in post #6
pacman -Qkk #check if pacman can detect corruption in those files
edit:
spelling method
Last edited by loqs (2018-03-03 13:36:42)
Offline
pacman -Qkk with all lines including " 0 altered files" filtered: http://ix.io/RPm
Offline
The pacman database is corrupted for those two packages.
nodejs: 44 terror: error while reading file /var/lib/pacman/local/npm-5.7.1-1/mtree: Unrecognized archive format
xorg-fonts-alias: error: error while reading file /var/lib/pacman/local/youtube-dl-2018.02.26-1/mtree: Unrecognized archive format
Given the use of --force over two groups earlier I would not trust a pacman result even if it reported clean at this stage and would reinstall but that is just my view.
Edit:
You should probably also check that
/var/lib/pacman/local/*/files is present for every package and none zero in length.
Last edited by loqs (2018-03-03 13:52:16)
Offline
Thank you for your time and efforts. Since nothing worked and no new ideas come up I will reinstall the whole system tomorrow and hooe this solves the problem.
Thanks to anybody reading this thread and trying to help me
Offline
Before you do would follow V1del's advice and perform a SMART check on the systems storage devices also run a self test if the devices do not use NVME.
Reinstalling a system onto bad storage will surely lead to more corruption and similar issues in future.
Offline
Before you do would follow V1del's advice and perform a SMART check on the systems storage devices also run a self test if the devices do not use NVME.
Reinstalling a system onto bad storage will surely lead to more corruption and similar issues in future.
On top of that, you could also try running a live graphical environment from USB such as Ubuntu for 5-10 minutes (or however long it takes to freeze) and confirm that your freezes don't persist there.
Last edited by Gigamo (2018-03-03 15:13:16)
Offline
Ubuntu live cd runs fine. Just running the smart/tests from it. I ran it for sda, sdb and sdc, could it be harmful to run multiple at once? They only said a time when they will be done and went into background. Is that the right behaviour? I can not see any status.
I never used smart-tools before.
Last edited by nerdnils (2018-03-03 16:18:26)
Offline