Hi all,
after this update and select “dbus-broker” my system with kernel 6.7 freezes for about 20 seconds, then it works for about 3-5 seconds and then it freezes again for about 20 seconds and so on.
With kernel 6.6.x it works without any problems.
I see in journalctl this:
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: Loading theme configuration from "/usr/share/sddm/themes/breath/theme.conf"
Jan 14 17:45:45 manjaro64 systemd[1670]: Created slice User Core Session Slice.
Jan 14 17:45:45 manjaro64 systemd[1670]: Starting D-Bus User Message Bus...
Jan 14 17:45:45 manjaro64 dbus-broker-launch[1684]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Jan 14 17:45:45 manjaro64 dbus-broker-launch[1684]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Jan 14 17:45:45 manjaro64 dbus-broker-launch[1684]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Jan 14 17:45:45 manjaro64 dbus-broker-launch[1684]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Jan 14 17:45:45 manjaro64 dbus-broker-launch[1684]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Jan 14 17:45:45 manjaro64 systemd[1670]: Started D-Bus User Message Bus.
Jan 14 17:45:45 manjaro64 dbus-broker-launch[1684]: Ready
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: Connected to the daemon.
Jan 14 17:45:45 manjaro64 sddm[635]: Message received from greeter: Connect
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: Loading file:///usr/share/sddm/themes/breath/Main.qml...
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7fffb71e5580), parent's thread is QThread(0x55ad054919c0), current thread is QThread(0x55ad056652d0)
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7fffb71e5580), parent's thread is QThread(0x55ad054919c0), current thread is QThread(0x55ad056652d0)
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7fffb71e5580), parent's thread is QThread(0x55ad054919c0), current thread is QThread(0x55ad056652d0)
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: Adding view for "DVI-I-1" QRect(0,0 1920x1080)
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: Message received from daemon: Capabilities
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: Message received from daemon: HostName
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:47 manjaro64 pipewire-media-session[1188]: spa.bluez5: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner
hmm, noticed something else unusual …
memory consumption has increased significantly since the update
system monitor → processes shows many processes which now use lots of memory e.g. Thunderbird 430 MiB, about 10 Chromium processes with 290 MiB each, Plasmashell 390MiB etc.
When i take a look at my Boot-Partition, i see the mkinitcpio.conf and also the fallback file is stored there.
I dont have enough space, even when i deactivate the fallback file. And im not sure if i want to disable it, because im not aware what the backstep is, i need atleast 180MB for only mkinitcpio.conf and this is a ridicules big size for such files.
Anyways i try to evade this problem as long as possible with the much smaller LTS Kernels… lucky that the previous Kernel 6.6 is LTS.
Having only 200MB for /boot is extremely bad idea. Don’t know where did you got this stupid idea from. Try to fix it if you want to have a working system. The best solution will be to move /boot back to the root / where it is by default in the first place instead of a separate partition.
Before i started Linux, I asked in a PC Forum (Computerbase.de) for tipps, how to install Manjaro and it was their suggestion how i should do to install Manjaro with custom install settings.
It was indeed a stupid idea/help and i regret it pretty soon… but i don’t wanted to reinstall my system after i realised it.
How can i archive this goal? Should i backup my files in /boot partition? And remove my partition after, and then i create a boot folder in root and just copy this and stuff into it?
Actually when i look into my root directory, at looks like a boot folder is already created in root, but i think its a mirror or something like that from my /boot partition… but when i click on my /boot partition in dolphin it leading me to the exact same path, its a little confusing for me.
Its the same story with my /home folder in root, it should be a partition, but it looks as a normal folder when i browse from root to home or boot it all looks like a folder.
I don’t get it, i normaly would expect a symlink in this situations.
Anyways in short, when i remove the /boot partition will / (root)>boot folder step in place and will instant boot from there or do i have to adjust some files (editing pathing) in Grub or Fstab maybe?
Your reaction here-above suggests that you do not understand UNIX. UNIX doesn’t distinguish (for the user) between a mountpoint and a directory (cough “folder” cough) on purpose.
A mountpoint is a directory, and the idea is that you would navigate to where the files are by simply moving up and down the directory hierarchy. Approaching storage by way of individual volumes is an older modus operandi that dates back to the days when x86 computers — and their CP/M and MS-DOS operating systems (until DOS 3.0) — did not support hard disks yet and had to make do with floppy disks. CP/M, DOS and even the early Apple operating systems also didn’t even support directories, and everything was in a flat filesystem.
Please read (the introduction of) my tutorial below.
Update proceeded well on both my zen4 7950x workstation and dell xps 9700 laptop whilst running linux 6.6.
Kernel 6.7, however, crashes during boot on the dell xps 9700 and upon inspecting the kernel boot logs and performing some research, appears to be related to a kernel ath11k driver regression detailed in the following link:
I suppose copying everything from old boot to boot1, running live session, removing /boot entry in fstab and renaming boot1 to boot before restarting should do it, but do your research. And restoring grub after that with install-grub.
No issues here, but I noticed a significant speedup when booting up! I have an encrypted root with Plymouth set up, and now I can hardly see the pulsing three dots, before and after the decryption prompt. Also sleep seems to work again, but that’s something I could have lived without
According to Manjaro Settings Manager → Kernels, 6.6.10 is not installed. Is the update supposed to auto-upgrade the kernel to 6.6.10. Wonder why mine stays at 6.1.71?
For the first time I also have two problems after an update.
Steam gets confused with display
In the living room, an old company laptop is connected to the TV via HDMI.
Only the TV is used as a display.
When a game is started in Steam, it runs but is not displayed on the TV.
The output on the TV was not a problem before the update.
When the TV is unplugged, the output appears on the laptop display.
Kernel is 6.6.
It runs X11 with KDE Plasma.
VNC output only 4:3 and cut off
A VM with Manjaro is also running on a Proxmox hypervisor.
The connection is established with VNC (Krfb).
The output should be in 1920/1080, but it actually looks like a 4:3 resolution.
Starting from the center, all outer areas are cut off so that only a part of the desktop is visible.
There are no scroll bars.
Worked without problems before the update.
Changing to differen resolutions did not solve the issue.
Kernel of the VM is 6.6
It runs X11 with KDE Plasma.
Well I thought it was smooth sailing, but I have an issue. My computer boots fine, but doesn’t halt, reboot nor sleep anymore (even from the text console). It’s a HP z240 i7-7700 with an nVidia 1050Ti. Switching from kernel 6.7 back to 6.6 doesn’t address the problem, so I believe it’s systemd related.
When trying to halt or sleep, the screen goes black, and after a couple of seconds, the fan starts to turn at 100% speed (which on this type of station is quite scary, frankly). The log reaches the last target, but the power supply doesn’t switch off. I have to hold the switch manually for 5 seconds to power off.
I’ll investigate further time permitting.
M.
So what to choose ?
I will try using pamac update in CLI
[Edit] pamac update did the job
pamac update
Préparation…
Synchronisation des bases de données des paquets…
Choix d’un fournisseur pour dbus-units:
1: dbus-broker-units 35-2 core
2: dbus-daemon-units 1.14.10-2 core
Entrer un nombre (par défaut = 1):
Résolution des dépendances…
Recherche des conflits entre paquets…
and the update ended without error.
But in the mean time i should also delete the old boot directory or i better delete it in a partition manager and then i go for renaming boot1 into boot, right?
After i restarted my system again in a live session, i guess it won’t normal start without it… so i should also chroot before doing it?
