I installed deno package from native Add/Remove Software application, it was official comunity package.
https://pasteboard.co/JNQv9G3.png
Then some warning showed up, something like restart needed, not sure.
I restarted, but now can’t open terminal, I have only one native bash terminal installed.
Also pulseeffects not detecting audio devices. https://pasteboard.co/JNQv0Qd.png
I can’t even uninstall deno in native app, transaction error. https://pasteboard.co/JNQvdIs.png
Also native folder app icon changed. https://pasteboard.co/JNQv5Qd.png
I have no backup and I was wasting my last two weeks of choosing right linux for me and do not want to reinstall it again…
Is it possible to fix without reinstalling system? I have also dual boot with windows and I can’t backup all my data from both windows and current system.
My guess is that you installed the application and updated at the same time. (this is not a problem in most cases) I can’t see the image but I gues you have some locale problem that can be fixed with this guide.
For your other issues please read this post in the last stable update thread.
Consider subscribing to the Stable Updates Announcements RSS feed
Hi, thanks for your advice. I’ve just updated the post so you can see the images on the external resource. The problem is that I can’t even use terminal, which is the worst problem in linux, since user uses it for everything, some fixes as well.
Can’t you switch to a TTY? CTRL+ALT+F2
or another F key
and then just remove the “deno” package - if it is actually the cause of your problem, which seems unlikely …
sudo pacman -Rns deno
CTRL+ALT+F7
to get back to your session
It’s unlikely that installing that package would require a reboot or mess things up.
Perhaps the whole system was updated … before installing it - and something went wrong there?
The end of /var/log/pacman.log will show what was done and when, besides installing that package.
cat /var/log/pacman.log
edit:
you posted the pacman log while I was writing this
This looks like a full system upgrade - and perhaps you are experiencing the locale issue that many users reported to have.
/edit
If it’s the locale issue:
there is an announcement re this somewhere here on the forum how to fix this easily
You’ll find it … and there are many posts on the issue as well
effectively, from memory:
just check and re-add your language settings in … the settings
or:
check/edit /etc/locale.gen
uncomment your locale
and run locale-gen
… not log’s exactly - but potentially useful info
open a terminal - and run the app from there, by it’s name …
the terminal output will show some info, especially when there are errors
Feb 11 10:51:43 manjaro kernel: ata10: failed stop FIS RX (-16)
Feb 11 10:51:43 manjaro kernel: pcieport 0000:00:03.1: can't change power state from unknown to D0 (config space inaccessible)
Feb 11 10:51:44 manjaro systemd[1]: Failed to start pkgfile database update.
Feb 11 10:57:06 manjaro kernel: Uhhuh. NMI received for unknown reason 2c on CPU 0.
Feb 11 10:57:06 manjaro kernel: Do you have a strange power saving mode enabled?
Feb 11 10:57:06 manjaro kernel: Dazed and confused, but trying to continue
Feb 11 11:06:53 manjaro systemd-fstab-generator[12785]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Feb 11 11:06:53 manjaro systemd[12776]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Feb 11 11:07:20 manjaro systemd-fstab-generator[12871]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Feb 11 11:07:20 manjaro systemd[12862]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
-- Boot 5b6da78dcfb54cc08c4f2bb7d642e11f --
Feb 11 11:12:27 manjaro systemd-fstab-generator[297]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Feb 11 11:12:27 manjaro systemd[288]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Feb 11 11:12:27 manjaro systemd-udevd[371]: could not read from '/sys/module/pcc_cpufreq/initstate': No such device
-- Boot ba9dd49fc744482193c19e6a6ea831b4 --
Feb 11 11:12:31 manjaro gdm[752]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting down.
Feb 11 11:12:32 manjaro kernel: watchdog: watchdog0: watchdog did not stop!
-- Boot 5b6da78dcfb54cc08c4f2bb7d642e11f --
Feb 11 11:12:50 manjaro gdm-password][1438]: gkr-pam: unable to locate daemon control file
Feb 11 11:12:50 manjaro systemd[1443]: Failed to start Application launched by gnome-session-binary.
Feb 11 11:12:53 manjaro sudo[2012]: pam_unix(sudo:auth): conversation failed
Feb 11 11:12:53 manjaro sudo[2012]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 11:12:53 manjaro sudo[2012]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 11:12:53 manjaro systemd[1443]: Failed to start GNOME Terminal Server.
Feb 11 11:13:45 manjaro pulseaudio[1630]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes>
Feb 11 11:14:04 manjaro pulseaudio[1630]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Feb 11 11:14:04 manjaro pulseaudio[1630]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 11:14:04 manjaro pulseaudio[1630]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 11:14:05 manjaro pulseaudio[1630]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Feb 11 11:14:05 manjaro pulseaudio[1630]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 11:14:05 manjaro pulseaudio[1630]: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 11:15:41 manjaro systemd[1443]: Failed to start GNOME Terminal Server.
Feb 11 11:16:11 manjaro kdeconnectd[2007]: The Wayland connection broke. Did the Wayland compositor die?
Feb 11 11:16:12 manjaro systemd-coredump[4192]: Process 2007 (kdeconnectd) of user 1000 dumped core.
Stack trace of thread 2007:
#0 0x00007feab3a49ef5 raise (libc.so.6 + 0x3cef5)
#1 0x00007feab3a33862 abort (libc.so.6 + 0x26862)
#2 0x00007feab3e499ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
#3 0x00007feaafe9a0fa n/a (libQt5WaylandClient.so.5 + 0x620fa)
#4 0x00007feaafea9465 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x71465)
#5 0x00007feab40a5e10 n/a (libQt5Core.so.5 + 0x2ece10)
#6 0x00007feab40a9340 _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2f0340)
#7 0x00007feab40a9b4d _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2f0b4d)
#8 0x00007feab4bbc752 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a752)
#9 0x00007feab406ea7a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b5a7a)
#10 0x00007feab40c82f6 n/a (libQt5Core.so.5 + 0x30f2f6)
#11 0x00007feab25bbb74 g_main_context_dispatch (libglib-2.0.so.0 + 0x52b74)
#12 0x00007feab260fc31 n/a (libglib-2.0.so.0 + 0xa6c31)
#13 0x00007feab25ba3a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#14 0x00007feab40c76e1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6e1)
#15 0x00007feab406d3fc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43fc)
#16 0x00007feab4075894 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2bc894)
#17 0x0000558d1dd76462 n/a (kdeconnectd + 0x3462)
#18 0x00007feab3a34b25 __libc_start_main (libc.so.6 + 0x27b25)
#19 0x0000558d1dd766de _start (kdeconnectd + 0x36de)
Stack trace of thread 2155:
#0 0x00007feab3b0147f __poll (libc.so.6 + 0xf447f)
#1 0x00007feab260fbbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007feab25ba3a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#3 0x00007feab40c76e1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6e1)
#4 0x00007feab406d3fc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43fc)
#5 0x00007feab3e85d22 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd22)
#6 0x00007feab3e86f0f n/a (libQt5Core.so.5 + 0xcdf0f)
#7 0x00007feab3021299 start_thread (libpthread.so.0 + 0x9299)
#8 0x00007feab3b0c153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2117:
#0 0x00007feab3b0147f __poll (libc.so.6 + 0xf447f)
#1 0x00007feab260fbbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007feab25ba3a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#3 0x00007feaaf46cc0e n/a (libdconfsettings.so + 0x5c0e)
#4 0x00007feab25e8fd1 n/a (libglib-2.0.so.0 + 0x7ffd1)
#5 0x00007feab3021299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007feab3b0c153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2119:
#0 0x00007feab3b0147f __poll (libc.so.6 + 0xf447f)
#1 0x00007feab260fbbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007feab25bb0c3 g_main_loop_run (libglib-2.0.so.0 + 0x520c3)
#3 0x00007feaaea65c68 n/a (libgio-2.0.so.0 + 0x101c68)
#4 0x00007feab25e8fd1 n/a (libglib-2.0.so.0 + 0x7ffd1)
#5 0x00007feab3021299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007feab3b0c153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2103:
#0 0x00007feab3b0147f __poll (libc.so.6 + 0xf447f)
#1 0x00007feab260fbbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007feab25ba3a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#3 0x00007feab40c76e1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6e1)
#4 0x00007feab406d3fc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43fc)
#5 0x00007feab3e85d22 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd22)
#6 0x00007feab4325098 n/a (libQt5DBus.so.5 + 0x17098)
#7 0x00007feab3e86f0f n/a (libQt5Core.so.5 + 0xcdf0f)
#8 0x00007feab3021299 start_thread (libpthread.so.0 + 0x9299)
#9 0x00007feab3b0c153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2193:
#0 0x00007feab3b03cf3 pselect (libc.so.6 + 0xf6cf3)
#1 0x00007fea9658a524 n/a (libusbmuxd-2.0.so.6 + 0x2524)
#2 0x00007fea9658b8a9 n/a (libusbmuxd-2.0.so.6 + 0x38a9)
#3 0x00007feab3021299 start_thread (libpthread.so.0 + 0x9299)
#4 0x00007feab3b0c153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2116:
#0 0x00007feab3b0147f __poll (libc.so.6 + 0xf447f)
#1 0x00007feab260fbbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007feab25ba3a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#3 0x00007feab25ba3f2 n/a (libglib-2.0.so.0 + 0x513f2)
#4 0x00007feab25e8fd1 n/a (libglib-2.0.so.0 + 0x7ffd1)
#5 0x00007feab3021299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007feab3b0c153 __clone (libc.so.6 + 0xff153)
Feb 11 11:16:12 manjaro pulseaudio[1630]: Unable to read or parse data from client.
Feb 11 11:16:20 manjaro gdm-password][4583]: gkr-pam: unable to locate daemon control file
Feb 11 11:16:20 manjaro systemd[1443]: Failed to start Application launched by gnome-session-binary.
Feb 11 11:16:23 manjaro sudo[5118]: pam_unix(sudo:auth): conversation failed
Feb 11 11:16:23 manjaro sudo[5118]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 11:16:23 manjaro sudo[5118]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 11:16:23 manjaro systemd[1443]: Failed to start GNOME Terminal Server.
Feb 11 11:16:40 manjaro pulseaudio[4774]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Feb 11 11:16:40 manjaro pulseaudio[4774]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 11:16:40 manjaro pulseaudio[4774]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 11:16:47 manjaro pulseaudio[4774]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes>
Feb 11 11:20:01 manjaro systemd[1443]: Failed to start GNOME Terminal Server.
Feb 11 11:20:15 manjaro pulseaudio[4774]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Feb 11 11:20:15 manjaro pulseaudio[4774]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 11:20:15 manjaro pulseaudio[4774]: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 11:26:14 manjaro kernel: snd_hda_intel 0000:26:00.1: AER: Error of this Agent is reported first
Feb 11 11:32:34 manjaro systemd[1443]: Failed to start GNOME Terminal Server.
Feb 11 11:39:31 manjaro gdm[733]: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.15 was not provided by any .service files
Feb 11 11:39:31 manjaro pulseaudio[4774]: Error opening PCM device front:1: No such file or directory
Feb 11 11:39:31 manjaro pulseaudio[4774]: Error opening PCM device front:1: No such file or directory
Feb 11 11:39:31 manjaro systemd-coredump[9257]: Failed to send coredump datagram: Connection reset by peer
Feb 11 11:39:32 manjaro kernel: watchdog: watchdog0: watchdog did not stop!
-- Boot 029da8ff43a846dba90f03db57244a81 --
Feb 11 13:23:20 manjaro systemd-fstab-generator[298]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Feb 11 13:23:20 manjaro systemd[289]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Feb 11 13:23:35 manjaro gdm-password][1433]: gkr-pam: unable to locate daemon control file
Feb 11 13:23:35 manjaro systemd[1437]: Failed to start Application launched by gnome-session-binary.
Feb 11 13:23:38 manjaro sudo[2011]: pam_unix(sudo:auth): conversation failed
Feb 11 13:23:38 manjaro sudo[2011]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 13:23:38 manjaro sudo[2011]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 13:23:39 manjaro systemd[1437]: Failed to start GNOME Terminal Server.
Feb 11 13:24:34 manjaro pulseaudio[1622]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes>
Feb 11 13:28:41 manjaro pulseaudio[1622]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Feb 11 13:28:41 manjaro pulseaudio[1622]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 13:28:41 manjaro pulseaudio[1622]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 13:30:55 manjaro systemd[1437]: Failed to start GNOME Terminal Server.
Feb 11 13:37:57 manjaro pulseaudio[1622]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Feb 11 13:37:57 manjaro pulseaudio[1622]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 13:37:57 manjaro pulseaudio[1622]: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 13:55:31 manjaro kdeconnectd[2008]: The Wayland connection broke. Did the Wayland compositor die?
Feb 11 13:55:32 manjaro systemd-coredump[6691]: Process 2008 (kdeconnectd) of user 1000 dumped core.
Stack trace of thread 2008:
#0 0x00007f18b5eebef5 raise (libc.so.6 + 0x3cef5)
#1 0x00007f18b5ed5862 abort (libc.so.6 + 0x26862)
#2 0x00007f18b62eb9ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
#3 0x00007f18b233c0fa n/a (libQt5WaylandClient.so.5 + 0x620fa)
#4 0x00007f18b234b465 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x71465)
#5 0x00007f18b6547e10 n/a (libQt5Core.so.5 + 0x2ece10)
#6 0x00007f18b654b340 _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2f0340)
#7 0x00007f18b654bb4d _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2f0b4d)
#8 0x00007f18b705e752 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a752)
#9 0x00007f18b6510a7a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b5a7a)
#10 0x00007f18b656a2f6 n/a (libQt5Core.so.5 + 0x30f2f6)
#11 0x00007f18b4a5db74 g_main_context_dispatch (libglib-2.0.so.0 + 0x52b74)
#12 0x00007f18b4ab1c31 n/a (libglib-2.0.so.0 + 0xa6c31)
#13 0x00007f18b4a5c3a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#14 0x00007f18b65696fc _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6fc)
#15 0x00007f18b650f3fc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43fc)
#16 0x00007f18b6517894 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2bc894)
#17 0x00005627d6810462 n/a (kdeconnectd + 0x3462)
#18 0x00007f18b5ed6b25 __libc_start_main (libc.so.6 + 0x27b25)
#19 0x00005627d68106de _start (kdeconnectd + 0x36de)
Stack trace of thread 2105:
#0 0x00007f18b5fa347f __poll (libc.so.6 + 0xf447f)
#1 0x00007f18b4ab1bbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007f18b4a5c3a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#3 0x00007f18b4a5c3f2 n/a (libglib-2.0.so.0 + 0x513f2)
#4 0x00007f18b4a8afd1 n/a (libglib-2.0.so.0 + 0x7ffd1)
#5 0x00007f18b54c3299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007f18b5fae153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 5447:
#0 0x00007f18b5fa5cf3 pselect (libc.so.6 + 0xf6cf3)
#1 0x00007f18a8a7d524 n/a (libusbmuxd-2.0.so.6 + 0x2524)
#2 0x00007f18a8a7e8a9 n/a (libusbmuxd-2.0.so.6 + 0x38a9)
#3 0x00007f18b54c3299 start_thread (libpthread.so.0 + 0x9299)
#4 0x00007f18b5fae153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2108:
#0 0x00007f18b5fa347f __poll (libc.so.6 + 0xf447f)
#1 0x00007f18b4ab1bbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007f18b4a5d0c3 g_main_loop_run (libglib-2.0.so.0 + 0x520c3)
#3 0x00007f18b0f07c68 n/a (libgio-2.0.so.0 + 0x101c68)
#4 0x00007f18b4a8afd1 n/a (libglib-2.0.so.0 + 0x7ffd1)
#5 0x00007f18b54c3299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007f18b5fae153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2106:
#0 0x00007f18b5fa347f __poll (libc.so.6 + 0xf447f)
#1 0x00007f18b4ab1bbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007f18b4a5c3a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#3 0x00007f18b190ec0e n/a (libdconfsettings.so + 0x5c0e)
#4 0x00007f18b4a8afd1 n/a (libglib-2.0.so.0 + 0x7ffd1)
#5 0x00007f18b54c3299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007f18b5fae153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2100:
#0 0x00007f18b5fa347f __poll (libc.so.6 + 0xf447f)
#1 0x00007f18b4ab1bbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007f18b4a5c3a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#3 0x00007f18b65696e1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6e1)
#4 0x00007f18b650f3fc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43fc)
#5 0x00007f18b6327d22 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd22)
#6 0x00007f18b67c7098 n/a (libQt5DBus.so.5 + 0x17098)
#7 0x00007f18b6328f0f n/a (libQt5Core.so.5 + 0xcdf0f)
#8 0x00007f18b54c3299 start_thread (libpthread.so.0 + 0x9299)
#9 0x00007f18b5fae153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2126:
#0 0x00007f18b5fa347f __poll (libc.so.6 + 0xf447f)
#1 0x00007f18b4ab1bbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007f18b4a5c3a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#3 0x00007f18b65696e1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6e1)
#4 0x00007f18b650f3fc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43fc)
#5 0x00007f18b6327d22 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd22)
#6 0x00007f18b6328f0f n/a (libQt5Core.so.5 + 0xcdf0f)
#7 0x00007f18b54c3299 start_thread (libpthread.so.0 + 0x9299)
#8 0x00007f18b5fae153 __clone (libc.so.6 + 0xff153)
Feb 11 13:55:32 manjaro pulseaudio[1622]: Unable to read or parse data from client.
Feb 11 13:55:40 manjaro gdm-password][7063]: gkr-pam: unable to locate daemon control file
Feb 11 13:55:40 manjaro systemd[1437]: Failed to start Application launched by gnome-session-binary.
Feb 11 13:55:43 manjaro sudo[7589]: pam_unix(sudo:auth): conversation failed
Feb 11 13:55:43 manjaro sudo[7589]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 13:55:43 manjaro sudo[7589]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 13:55:43 manjaro systemd[1437]: Failed to start GNOME Terminal Server.
Feb 11 13:56:08 manjaro pulseaudio[7248]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes>
Feb 11 13:58:02 manjaro pulseaudio[7248]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Feb 11 13:58:02 manjaro pulseaudio[7248]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 13:58:02 manjaro pulseaudio[7248]: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:01:32 manjaro systemd-fstab-generator[10477]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Feb 11 14:01:32 manjaro systemd[10468]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Feb 11 14:01:33 manjaro systemd[10514]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Feb 11 14:01:33 manjaro systemd-fstab-generator[10523]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
-- Boot f74659f0b52e4e609d6115205a6f28bb --
Feb 11 14:02:16 manjaro systemd-fstab-generator[300]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Feb 11 14:02:16 manjaro systemd[291]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
-- Boot 029da8ff43a846dba90f03db57244a81 --
Feb 11 14:02:21 manjaro gdm[726]: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.15 was not provided by any .service files
Feb 11 14:02:21 manjaro pulseaudio[7248]: Error opening PCM device hdmi:0,4: No such file or directory
Feb 11 14:02:22 manjaro kernel: watchdog: watchdog0: watchdog did not stop!
-- Boot f74659f0b52e4e609d6115205a6f28bb --
Feb 11 14:02:34 manjaro gdm-password][1448]: gkr-pam: unable to locate daemon control file
Feb 11 14:02:34 manjaro systemd[1457]: Failed to start Application launched by gnome-session-binary.
Feb 11 14:02:37 manjaro sudo[2032]: pam_unix(sudo:auth): conversation failed
Feb 11 14:02:37 manjaro sudo[2032]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:02:37 manjaro sudo[2032]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:02:37 manjaro systemd[1457]: Failed to start GNOME Terminal Server.
Feb 11 14:02:44 manjaro pulseaudio[1641]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Feb 11 14:02:44 manjaro pulseaudio[1641]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 14:02:44 manjaro pulseaudio[1641]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:03:26 manjaro pulseaudio[1641]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes>
Feb 11 14:07:39 manjaro pulseaudio[1641]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Feb 11 14:07:39 manjaro pulseaudio[1641]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 14:07:39 manjaro pulseaudio[1641]: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:08:05 manjaro systemd[1457]: Failed to start GNOME Terminal Server.
Feb 11 14:13:30 manjaro kdeconnectd[2029]: The Wayland connection broke. Did the Wayland compositor die?
Feb 11 14:13:30 manjaro systemd-coredump[4246]: Process 2029 (kdeconnectd) of user 1000 dumped core.
Stack trace of thread 2029:
#0 0x00007f981e626ef5 raise (libc.so.6 + 0x3cef5)
#1 0x00007f981e610862 abort (libc.so.6 + 0x26862)
#2 0x00007f981ea269ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
#3 0x00007f981aa770fa n/a (libQt5WaylandClient.so.5 + 0x620fa)
#4 0x00007f981aa86465 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x71465)
#5 0x00007f981ec82e10 n/a (libQt5Core.so.5 + 0x2ece10)
#6 0x00007f981ec86340 _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2f0340)
#7 0x00007f981ec86b4d _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2f0b4d)
#8 0x00007f981f799752 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a752)
#9 0x00007f981ec4ba7a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b5a7a)
#10 0x00007f981eca52f6 n/a (libQt5Core.so.5 + 0x30f2f6)
#11 0x00007f981d198b74 g_main_context_dispatch (libglib-2.0.so.0 + 0x52b74)
#12 0x00007f981d1ecc31 n/a (libglib-2.0.so.0 + 0xa6c31)
#13 0x00007f981d1973a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#14 0x00007f981eca46e1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6e1)
#15 0x00007f981ec4a3fc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43fc)
#16 0x00007f981ec52894 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2bc894)
#17 0x000055d62f6d2462 n/a (kdeconnectd + 0x3462)
#18 0x00007f981e611b25 __libc_start_main (libc.so.6 + 0x27b25)
#19 0x000055d62f6d26de _start (kdeconnectd + 0x36de)
Stack trace of thread 2135:
#0 0x00007f981e6de47f __poll (libc.so.6 + 0xf447f)
#1 0x00007f981d1ecbbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007f981d1973a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#3 0x00007f981d1973f2 n/a (libglib-2.0.so.0 + 0x513f2)
#4 0x00007f981d1c5fd1 n/a (libglib-2.0.so.0 + 0x7ffd1)
#5 0x00007f981dbfe299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007f981e6e9153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2138:
#0 0x00007f981e6de47f __poll (libc.so.6 + 0xf447f)
#1 0x00007f981d1ecbbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007f981d1980c3 g_main_loop_run (libglib-2.0.so.0 + 0x520c3)
#3 0x00007f9819642c68 n/a (libgio-2.0.so.0 + 0x101c68)
#4 0x00007f981d1c5fd1 n/a (libglib-2.0.so.0 + 0x7ffd1)
#5 0x00007f981dbfe299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007f981e6e9153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2136:
#0 0x00007f981e6de47f __poll (libc.so.6 + 0xf447f)
#1 0x00007f981d1ecbbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007f981d1973a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#3 0x00007f981a049c0e n/a (libdconfsettings.so + 0x5c0e)
#4 0x00007f981d1c5fd1 n/a (libglib-2.0.so.0 + 0x7ffd1)
#5 0x00007f981dbfe299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007f981e6e9153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2122:
#0 0x00007f981e6de47f __poll (libc.so.6 + 0xf447f)
#1 0x00007f981d1ecbbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007f981d1973a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#3 0x00007f981eca46e1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6e1)
#4 0x00007f981ec4a3fc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43fc)
#5 0x00007f981ea62d22 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd22)
#6 0x00007f981ef02098 n/a (libQt5DBus.so.5 + 0x17098)
#7 0x00007f981ea63f0f n/a (libQt5Core.so.5 + 0xcdf0f)
#8 0x00007f981dbfe299 start_thread (libpthread.so.0 + 0x9299)
#9 0x00007f981e6e9153 __clone (libc.so.6 + 0xff153)
Stack trace of thread 2156:
#0 0x00007f981e6de47f __poll (libc.so.6 + 0xf447f)
#1 0x00007f981d1ecbbf n/a (libglib-2.0.so.0 + 0xa6bbf)
#2 0x00007f981d1973a1 g_main_context_iteration (libglib-2.0.so.0 + 0x513a1)
#3 0x00007f981eca46e1 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6e1)
#4 0x00007f981ec4a3fc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43fc)
#5 0x00007f981ea62d22 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd22)
#6 0x00007f981ea63f0f n/a (libQt5Core.so.5 + 0xcdf0f)
#7 0x00007f981dbfe299 start_thread (libpthread.so.0 + 0x9299)
#8 0x00007f981e6e9153 __clone (libc.so.6 + 0xff153)
Feb 11 14:13:30 manjaro pulseaudio[1641]: Unable to read or parse data from client.
Feb 11 14:13:39 manjaro gdm-password][4641]: gkr-pam: unable to locate daemon control file
Feb 11 14:13:40 manjaro systemd[1457]: Failed to start Application launched by gnome-session-binary.
Feb 11 14:13:42 manjaro sudo[5172]: pam_unix(sudo:auth): conversation failed
Feb 11 14:13:42 manjaro sudo[5172]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:13:42 manjaro sudo[5172]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:13:43 manjaro systemd[1457]: Failed to start GNOME Terminal Server.
Feb 11 14:13:53 manjaro pulseaudio[4832]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Feb 11 14:13:53 manjaro pulseaudio[4832]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 14:13:53 manjaro pulseaudio[4832]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:14:07 manjaro pulseaudio[4832]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes>
Feb 11 14:14:19 manjaro pulseaudio[4832]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Feb 11 14:14:19 manjaro pulseaudio[4832]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 14:14:19 manjaro pulseaudio[4832]: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:15:41 manjaro pulseaudio[4832]: Unable to read or parse data from client.
Feb 11 14:15:48 manjaro gdm-password][7215]: gkr-pam: unable to locate daemon control file
Feb 11 14:15:49 manjaro systemd[1457]: Failed to start Application launched by gnome-session-binary.
Feb 11 14:15:52 manjaro sudo[7742]: pam_unix(sudo:auth): conversation failed
Feb 11 14:15:52 manjaro sudo[7742]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:15:52 manjaro sudo[7742]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:15:52 manjaro systemd[1457]: Failed to start GNOME Terminal Server.
Feb 11 14:16:16 manjaro pulseaudio[7406]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes>
Feb 11 14:17:36 manjaro pulseaudio[7406]: Unable to read or parse data from client.
Feb 11 14:17:43 manjaro gdm-password][9476]: gkr-pam: unable to locate daemon control file
Feb 11 14:17:44 manjaro systemd[1457]: Failed to start Application launched by gnome-session-binary.
Feb 11 14:17:47 manjaro sudo[10017]: pam_unix(sudo:auth): conversation failed
Feb 11 14:17:47 manjaro sudo[10017]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:17:47 manjaro sudo[10017]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:17:47 manjaro systemd[1457]: Failed to start GNOME Terminal Server.
Feb 11 14:17:52 manjaro pulseaudio[9669]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Feb 11 14:17:52 manjaro pulseaudio[9669]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 14:17:52 manjaro pulseaudio[9669]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:18:11 manjaro pulseaudio[9669]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes>
Feb 11 14:20:40 manjaro pulseaudio[9669]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Feb 11 14:20:40 manjaro pulseaudio[9669]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 14:20:40 manjaro pulseaudio[9669]: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:22:44 manjaro systemd[1457]: Failed to start GNOME Terminal Server.
Feb 11 14:25:53 manjaro systemd[1457]: Failed to start GNOME Terminal Server.
Feb 11 14:34:42 manjaro pulseaudio[9669]: Unable to read or parse data from client.
Feb 11 14:34:49 manjaro gdm-password][13718]: gkr-pam: unable to locate daemon control file
Feb 11 14:34:49 manjaro systemd[1457]: Failed to start Application launched by gnome-session-binary.
Feb 11 14:34:52 manjaro sudo[14263]: pam_unix(sudo:auth): conversation failed
Feb 11 14:34:52 manjaro sudo[14263]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:34:52 manjaro sudo[14263]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:34:52 manjaro systemd[1457]: Failed to start GNOME Terminal Server.
Feb 11 14:35:09 manjaro pulseaudio[13912]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Feb 11 14:35:09 manjaro pulseaudio[13912]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 14:35:09 manjaro pulseaudio[13912]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:35:16 manjaro pulseaudio[13912]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the me>
Feb 11 14:36:19 manjaro sudo[15483]: pam_unix(sudo:auth): conversation failed
Feb 11 14:36:19 manjaro sudo[15483]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:36:19 manjaro sudo[15483]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:37:37 manjaro pulseaudio[13912]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Feb 11 14:37:37 manjaro pulseaudio[13912]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 14:37:37 manjaro pulseaudio[13912]: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:38:31 manjaro pulseaudio[15643]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the me>
Feb 11 14:38:58 manjaro pulseaudio[16069]: Unable to read or parse data from client.
Feb 11 14:38:58 manjaro pulseaudio[16069]: Error opening PCM device front:1: No such file or directory
Feb 11 14:38:58 manjaro pulseaudio[16069]: Error opening PCM device front:1: No such file or directory
Feb 11 14:39:04 manjaro gdm-password][16539]: gkr-pam: unable to locate daemon control file
Feb 11 14:39:05 manjaro systemd[1457]: Failed to start Application launched by gnome-session-binary.
Feb 11 14:39:08 manjaro sudo[17075]: pam_unix(sudo:auth): conversation failed
Feb 11 14:39:08 manjaro sudo[17075]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:39:08 manjaro sudo[17075]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:39:08 manjaro systemd[1457]: Failed to start GNOME Terminal Server.
Feb 11 14:39:14 manjaro pulseaudio[16731]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Feb 11 14:40:12 manjaro systemd[18319]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Feb 11 14:40:12 manjaro systemd-fstab-generator[18328]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
-- Boot ec64b2e619b14afe801c8a022e819267 --
Feb 11 14:40:19 manjaro systemd-fstab-generator[299]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Feb 11 14:40:19 manjaro systemd[290]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Feb 11 14:40:19 manjaro systemd-udevd[385]: could not read from '/sys/module/acpi_cpufreq/initstate': No such device
-- Boot f74659f0b52e4e609d6115205a6f28bb --
Feb 11 14:40:19 manjaro gdm[737]: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus is shutting down.
Feb 11 14:40:19 manjaro systemd-coredump[18460]: Failed to send coredump datagram: Connection reset by peer
-- Boot ec64b2e619b14afe801c8a022e819267 --
Feb 11 14:40:31 manjaro gdm-password][1437]: gkr-pam: unable to locate daemon control file
Feb 11 14:40:35 manjaro sudo[2015]: pam_unix(sudo:auth): conversation failed
Feb 11 14:40:35 manjaro sudo[2015]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:40:35 manjaro sudo[2015]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:41:29 manjaro pulseaudio[1626]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes>
Feb 11 14:42:14 manjaro pulseaudio[1626]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Feb 11 14:42:14 manjaro pulseaudio[1626]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 14:42:14 manjaro pulseaudio[1626]: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:43:26 manjaro pulseaudio[1626]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Feb 11 14:43:26 manjaro pulseaudio[1626]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 14:43:26 manjaro pulseaudio[1626]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:44:35 manjaro pulseaudio[3673]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Feb 11 14:44:59 manjaro pulseaudio[3673]: Unable to read or parse data from client.
Feb 11 14:45:05 manjaro gdm-password][4495]: gkr-pam: unable to locate daemon control file
Feb 11 14:45:09 manjaro sudo[5031]: pam_unix(sudo:auth): conversation failed
Feb 11 14:45:09 manjaro sudo[5031]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:45:09 manjaro sudo[5031]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 14:45:22 manjaro pulseaudio[4688]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Feb 11 14:45:22 manjaro pulseaudio[4688]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 14:45:22 manjaro pulseaudio[4688]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:45:33 manjaro pulseaudio[4688]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes>
Feb 11 14:45:59 manjaro pulseaudio[4688]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Feb 11 14:45:59 manjaro pulseaudio[4688]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 14:45:59 manjaro pulseaudio[4688]: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 14:49:29 manjaro systemd-coredump[6624]: Process 6622 (electron) of user 0 dumped core.
Stack trace of thread 6622:
#0 0x0000559c6e652479 n/a (electron + 0x343b479)
#1 0x0000559c6e51b50f n/a (electron + 0x330450f)
#2 0x0000559c6db25bb1 n/a (electron + 0x290ebb1)
#3 0x0000559c6f7a2e15 n/a (electron + 0x458be15)
#4 0x0000559c6cf1ac64 n/a (electron + 0x1d03c64)
#5 0x0000559c6c74d078 n/a (electron + 0x1536078)
#6 0x00007fd37b35fb25 __libc_start_main (libc.so.6 + 0x27b25)
#7 0x0000559c6c74ce2e _start (electron + 0x1535e2e)
Feb 11 15:39:42 manjaro systemd[13360]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Feb 11 15:39:42 manjaro systemd-fstab-generator[13369]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Feb 11 15:40:55 manjaro gdm[733]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting down.
-- Boot 356b6744a3b84ab3960931eae2aa1c57 --
Feb 11 15:40:56 manjaro systemd-fstab-generator[298]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Feb 11 15:40:56 manjaro systemd[289]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
-- Boot ec64b2e619b14afe801c8a022e819267 --
Feb 11 15:40:58 manjaro kernel: watchdog: watchdog0: watchdog did not stop!
-- Boot 356b6744a3b84ab3960931eae2aa1c57 --
Feb 11 15:44:15 manjaro gdm-password][1462]: gkr-pam: unable to locate daemon control file
Feb 11 15:44:18 manjaro systemd[1471]: Failed to start Application launched by gnome-session-binary.
Feb 11 15:44:19 manjaro sudo[2042]: pam_unix(sudo:auth): conversation failed
Feb 11 15:44:19 manjaro sudo[2042]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 15:44:19 manjaro sudo[2042]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 15:44:43 manjaro pulseaudio[1656]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes>
Feb 11 16:09:00 manjaro gdm[735]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting down.
Feb 11 16:09:00 manjaro pulseaudio[1656]: Unable to read or parse data from client.
-- Boot fc802bf6a24e450a8990e5996e5198df --
Feb 11 19:34:27 manjaro systemd-fstab-generator[298]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Feb 11 19:34:27 manjaro systemd[289]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Feb 11 19:37:55 manjaro gdm-password][1430]: gkr-pam: unable to locate daemon control file
Feb 11 19:37:59 manjaro systemd[1443]: Failed to start Application launched by gnome-session-binary.
Feb 11 19:37:59 manjaro sudo[2023]: pam_unix(sudo:auth): conversation failed
Feb 11 19:37:59 manjaro sudo[2023]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 19:37:59 manjaro sudo[2023]: pam_unix(sudo:auth): auth could not identify password for [ramofx]
Feb 11 19:38:23 manjaro pulseaudio[1632]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mes>
Feb 11 19:45:54 manjaro pulseaudio[1632]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Feb 11 19:45:54 manjaro pulseaudio[1632]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Feb 11 19:45:54 manjaro pulseaudio[1632]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 11 19:49:16 manjaro systemd-fstab-generator[8152]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Feb 11 19:49:16 manjaro systemd[8143]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Feb 11 19:49:27 manjaro systemd-fstab-generator[8245]: Failed to create unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Feb 11 19:49:27 manjaro systemd[8236]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
I think this is the reason of big ammount of problems. Can you help me please to make my Add/Remove Software and manjaro-application-utility apps make uninstalling possible again?
Also funny:
Feb 11 10:57:06 manjaro kernel: Uhhuh. NMI received for unknown reason 2c on CPU 0.
Feb 11 10:57:06 manjaro kernel: Do you have a strange power saving mode enabled?
Feb 11 10:57:06 manjaro kernel: Dazed and confused, but trying to continue
There is only one file in etc directory called fstab with following content:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=94EB-2B76 /boot/efi vfat umask=0077 0 2
UUID=6b887aaf-5c53-474f-9795-9e4dc4e5ea5c swap swap defaults,noatime 0 0
UUID=d6df865b-08ad-4512-a3f7-e6e0e16343d2 / ext4 defaults,noatime 0 1
UUID=b3759773-649d-42ea-b596-da36a4931eef /home ext4 defaults,noatime 0 2
UUID=f705e001-ace5-47aa-ba66-e63cc823344e /tmp ext4 defaults,noatime 0 2
UUID=1186b836-ddc9-463d-b1ca-ef25a14be56f /usr ext4 defaults,noatime 0 2
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
Output of refreshing mirrors:
ramofx@manjaro ~: $ sudo pacman-mirrors -c Czech
::INFO Downloading mirrors from repo.manjaro.org
::INFO User generated mirror list
::------------------------------------------------------------
::INFO Custom mirror file saved: /var/lib/pacman-mirrors/custom-mirrors.json
::INFO Using custom mirror file
::INFO Querying mirrors - This may take some time
1.041 Czech : https://mirror.dkm.cz/manjaro/
::INFO Writing mirror list
::Czech : https://mirror.dkm.cz/manjaro/stable/$repo/$arch
::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
::INFO To reset custom mirrorlist 'sudo pacman-mirrors -id'
::INFO To remove custom config run 'sudo pacman-mirrors -c all'
ramofx@manjaro ~: $ sudo pacman -Syyu
:: Synchronizing package databases...
core 167.2 KiB 1520 KiB/s 00:00 [xxxxx] 100%
extra 1983.7 KiB 2.90 MiB/s 00:01 [xxxxx] 100%
community 6.5 MiB 2.44 MiB/s 00:03 [xxxxx] 100%
multilib 181.3 KiB 2.68 MiB/s 00:00 [xxxxx] 100%
:: Starting full system upgrade...
there is nothing to do
System is updated to latest, that is good, single mirror might be a single point of failure, maybe add another country nearby (pacman-mirrors --country-list for countries to pick from)
I no expert, and I’m hesitant to give you advice about this, but having something mounted twice seems like a configuration error to me.
I’ve seen a few times, also not sure what to do about that:
Feb 11 11:16:11 manjaro kdeconnectd[2007]: The Wayland connection broke. Did the Wayland compositor die?
I hope a more expert user will have some sound advice.
On the pantheon terminal install issue what is the output of pamac install pantheon-terminal ?