Ever since the most recent update 2023-08-11 (which I just did a few days ago) I am experiencing a few seconds where everything is frozen, immediately after I login. I do not have hibernate or suspend activated.
Output of inxi --full --admin --filter --width is as follows:
Please find some output from journalctl here (what I think is related to the issue): https://dpaste.com/HHM7XBHFV
Any suggestions would be greatly appreciated!!
EDIT: it seems this issue is also occurring while machine is in use, not just upon login. With the same errors as in the linked logs (- at this time/date in the logs):
Aug 16 14:33:16 luke-pc systemd-coredump[353948])
It seems that pamac-manager is the culprit in this case (which got an update last week - 11.6.0-0.1).
pamac-manager (or a process of it) is trying to execute code from an unmapped area (error 14), therefore the kernel throws a segault (segmentation fault) error.
The error more detailed: 01110b
bit 0: no page found
bit 1: write-access
bit 2: user-mode access
bit 3: use of reserved bit detected
bit 4: not interesting in this case
The cause was a user-mode write resulting in no page being found. A reserved bit was detected.
After that segfault it starts a core dump of the process (353830 - pamac manager) which takes around 3.1 seconds, as you pointed out.
Since I’m not at home, this is all that I currently can point out.
Edit: You could also check the log of pamac itself under /var/log/
Aug 16 14:33:29 luke-pc kernel: pamac-manager[353830]: segfault at 7f94b0ff8070 ip 00007f94b0ff8070 sp 00007ffd7c64f8a8 error 14 in libnss_mdns_minimal.so.2[7f94b1000000+1000] likely on CPU 4 (core 4, socket 0)
Aug 16 14:33:29 luke-pc kernel: Code: Unable to access opcode bytes at 0x7f94b0ff8046.
Aug 16 14:33:29 luke-pc systemd[1]: Started Process Core Dump (PID 354179/UID 0).
Aug 16 14:33:32 luke-pc systemd-coredump[354180]: [🡕] Process 353830 (pamac-manager) of user 1000 dumped core.
Stack trace of thread 353830:
#0 0x00007f94b0ff8070 n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64
Aug 16 14:33:32 luke-pc systemd[1]: systemd-coredump@5-354179-0.service: Deactivated successfully.
Aug 16 14:33:32 luke-pc systemd[1]: systemd-coredump@5-354179-0.service: Consumed 3.107s CPU time.
@MystikReasons Thanks for the reply, I assumed it was to do with the errors on bijiben-shell-s (which appears to do with gnome-notes) that are also listed in the logs, so I was looking at the wrong thing to start with.
Yeah pamac is working fine for me, no issues at all, I checked the pamac logs and everything seems to be in order, there are a couple of errors in there but to me they don’t look related, considering the issue only appeared a few days ago and some of these errors are from a couple of weeks ago.
[2023-08-05T14:59:11+0800] [ALPM-SCRIPTLET] depmod: ERROR: could not open directory /lib/modules/6.2.13-1-MANJARO: No such file or directory
[2023-08-05T14:59:11+0800] [ALPM-SCRIPTLET] depmod: FATAL: could not search modules: No such file or directory
[2023-08-05T15:10:53+0800] [ALPM-SCRIPTLET] ==> ERROR: '/lib/modules/6.2.13-1-MANJARO' is not a valid kernel module directory
[2023-08-05T15:10:53+0800] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux62.preset: 'fallback'
[2023-08-05T15:10:53+0800] [ALPM-SCRIPTLET] ==> Using configuration file: '/etc/mkinitcpio.conf'
[2023-08-05T15:10:53+0800] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-6.2-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.2-x86_64-fallback.img -S autodetect --microcode /boot/intel-ucode.img
[2023-08-05T15:10:53+0800] [ALPM-SCRIPTLET] ==> ERROR: '/lib/modules/6.2.13-1-MANJARO' is not a valid kernel module directory
[2023-08-14T16:32:34+0800] [ALPM-SCRIPTLET] ==> ERROR: '/lib/modules/6.2.13-1-MANJARO' is not a valid kernel module directory
[2023-08-14T16:32:34+0800] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux62.preset: 'fallback'
[2023-08-14T16:32:34+0800] [ALPM-SCRIPTLET] ==> Using configuration file: '/etc/mkinitcpio.conf'
[2023-08-14T16:32:34+0800] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-6.2-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.2-x86_64-fallback.img -S autodetect --microcode /boot/intel-ucode.img
[2023-08-14T16:32:34+0800] [ALPM-SCRIPTLET] ==> ERROR: '/lib/modules/6.2.13-1-MANJARO' is not a valid kernel module directory
EDIT: I believe you can ignore the above logs, I see why the above errors are in the pamac log file - kernel 6.2.13-1 is no longer available (I’m on 6.4.9-1 anyways) so this should be an non-issue.
Would it be unwise for me to reinstall pamac-cli and pamac-gtk to see if that helps?
If you have any further suggestions, I’m all ears!
You could definetly try to reinstall pamac, never tried it myself.
You could use this command in that case: pacman -S pkg
According to the wiki you only need to reinstall pamac-gtk, since it will automatically install -cli.
Both the GTK and Qt pamac packages will automatically install the CLI version as well Pamac - Manjaro
Could you also post your pamac version? pamac --version
When was the last time the issue occured?
Is the log always showing the same section of failure (see below)?
Aug 16 14:33:29 luke-pc kernel: pamac-manager[353830]: segfault at 7f94b0ff8070 ip 00007f94b0ff8070 sp 00007ffd7c64f8a8 error 14 in libnss_mdns_minimal.so.2[7f94b1000000+1000] likely on CPU 4 (core 4, socket 0)
Aug 16 14:33:29 luke-pc kernel: Code: Unable to access opcode bytes at 0x7f94b0ff8046.
Aug 16 14:33:29 luke-pc systemd[1]: Started Process Core Dump (PID 354179/UID 0).
Aug 16 14:33:32 luke-pc systemd-coredump[354180]: [🡕] Process 353830 (pamac-manager) of user 1000 dumped core.
Stack trace of thread 353830:
#0 0x00007f94b0ff8070 n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64
Aug 16 14:33:32 luke-pc systemd[1]: systemd-coredump@5-354179-0.service: Deactivated successfully.
Aug 16 14:33:32 luke-pc systemd[1]: systemd-coredump@5-354179-0.service: Consumed 3.107s CPU time.
I saw that above the pamac-manager error pamac-manager loaded appstream2/x86_64 from flathub.
Could you check if its always loading appstream2/x86_64 from flathub before pamac-manager crashes?
Aug 16 14:33:17 luke-pc pamac-manager[353830]: /var/tmp/flatpak-cache-B4MG91/repo-jFEfdu: Pulled appstream2/x86_64 from flathub
Aug 16 14:33:17 luke-pc dbus-daemon[819]: [system] Activating via systemd: service name='org.freedesktop.Flatpak.SystemHelper' unit='flatpak-system-helper.service' requested by ':1.161898' (uid=1000 pid=353830 comm="/usr/bin/pamac-manager --gapplication-service")
Aug 16 14:33:17 luke-pc systemd[1]: Starting flatpak system helper...
Aug 16 14:33:17 luke-pc dbus-daemon[819]: [system] Successfully activated service 'org.freedesktop.Flatpak.SystemHelper'
Aug 16 14:33:17 luke-pc systemd[1]: Started flatpak system helper.
Aug 16 14:33:18 luke-pc flatpak-system-helper[354016]: system: Pulled appstream2/x86_64 from /var/tmp/flatpak-cache-B4MG91/repo-jFEfdu
Aug 16 14:33:19 luke-pc dbus-daemon[2131]: [session uid=1000 pid=2131] Successfully activated service 'org.manjaro.pamac.manager'
Aug 16 14:33:21 luke-pc gnome-shell[3513]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5e00004
Aug 16 14:33:23 luke-pc systemd[1]: fprintd.service: Deactivated successfully.
Aug 16 14:33:26 luke-pc gnome-character[353836]: JS LOG: Characters Application exiting
Sorry for clogging up the update thread with this and sorry for the late reply I have not been in front of my pc for a while
I reinstalled pamac and am still getting those errors in relation to it, but they no longer coincide with the temp freezing of the system and they seem to have no effect on the function of pamac. Though further to your question, yes it is always loading appstream2/x86_64 from flathub before pamac-manager crashes.
pamac-cli 11.6.0 - libpamac 11.6.0
Now my logs are full of errors from calendar, even though it still seems to work - not that I use it. If you see the recent logs: https://dpaste.com/DA6PCQB9U
I entered my password and unlocked the screens a few seconds after 10:12 am (looks like it was around 10:12:09), the logs I included are for the entire minute 10:12 - 10:13.
@Wollie I did remove that kernel as soon as I realised that it was unsupported and I generally do try and keep up on the announcements, thanks for the advice I will remove those orphaned entries - it looks like there’s a few others in there as well even though I have removed the kernels ages ago with mhwd-kernel.
At the moment I have these kernels installed: linux515, linux 61, linux 64 but in my mkinitcpio.d directory there’s a number of others listed
EDIT:It seems as if this issue is caused by an extension. I disabled extensions all together and the problem disappeared, though I am yet to figure out which extension is specifically causing it as just disabling one extension at a time has no effect, the main extension toggle must be turned off for the issue to be resolved. Not great as I rely on a few extensions for my workflow, but i’ll continue troubleshooting and hopefully find the culprit. Apologies for wasting your time looking at my logs and trying to help me, but also thank you for your time and assistance, I greatly appreciate it!
If it is present - perhaps it is causing interference - as the topic category is Gnome it would be safe to remove the package - thus relying only on GTK4?
Thank you for the suggestion, unfortunately I don’t have that package installed. So I’ll keep playing around with the extensions and see if I can figure out a fix for it.
I’m assuming no, but would you expect me to have any issues if I were to uninstall all extensions (including the Built-in ones plus maybe gnome-shell-extensions and manjaro-gnome-extension-settings) and then reinstall one at a time to see if I can pinpoint the culprit?
I cannot say for sure - long time since I used Gnome - if it fix the issue when you disable extensions completely - I cannot see a problem if they are removed as well.
I would ensure the system is set to use Gnome default layout - the layout switcher depends on extensions so not setting the layout to Gnome default would likely cause issues when required extensions are removed.
I vaguely remember something about applying a vanilla Gnome layout - but I cannot remember where.
Thank you very much for that info, I definitely would have overlooked checking my layout, to be on the safe side I’ll ensure my system has a current backup before I go ahead.
