Has it reached Manjaro Stable yet? It was still in Unstable, last time I blinked.
I also had an issue solved with sudo pacman -Syu kpeoplevcard but I also noticed that I was enabled to used sudo. A simple reboot did fixed that anyway.
libkipi broke dependencies. Some say it is deprecated and no longer needed, I uninstalled it, the update started then. Hope nothing breaks.
Source: Pacman Update Issue [SOLVED] / Applications & Desktop Environments / Arch Linux Forums
Looks good upon restart.
Since updating, the fans on my laptop have been running much more noticeably. They start immediately after booting up, even when the device is idle. Does anyone have any idea what could be causing this?
1 Like
There was a complaint (#10, #65) that 545.29.02 stable did not make it in this release. I merely provided an example that there are still issue with it.
To me, the confusion seems to come from your I see it’s still in beta; no great concern yet referring to the 545.29.02 being in Unstable branch, while I was only referencing beta vs. stable for the driver itself.
Hope this clears it out.
Note: mods, please feel free to clean/move this up, if needed.
There is a problem with Texstudio. It crash after some seconds:
$ texstudio
crashed with signal SIGSEGV
SIGSEGV (TXS-Version 0.0.0++ R )
SIGSEGV (TXS-Version 0.0.0++ R )
SIGSEGV (TXS-Version 0.0.0++ R )
SIGSEGV (TXS-Version 0.0.0++ R )
[bt] texstudio(_Z15print_backtraceRK7QString+0x4) [0x556f6a441254]
[bt] texstudio(_Z15print_backtraceRK7QString+0x4) [0x556f6a441254]
"/tmp/texstudio_backtrace1.txt"
crashed with signal SIGSEGV
SIGSEGV (TXS-Version 0.0.0++ R )
SIGSEGV (TXS-Version 0.0.0++ R )
SIGSEGV (TXS-Version 0.0.0++ R )
SIGSEGV (TXS-Version 0.0.0++ R )
[bt] texstudio(_Z15print_backtraceRK7QString+0x4) [0x556f6a441254]
[bt] texstudio(_Z15print_backtraceRK7QString+0x4) [0x556f6a441254]
"/tmp/texstudio_backtrace2.txt"
"Current: 0/0"
Killed on user request after error: SIGSEGV
zsh: IOT instruction (core dumped) texstudio
Yes, it did the same here.
I thought there was something wrong with my monitor, but it suddenly flashed back to normal intensity when I moved the mouse. So I gathered it would have been a setting somewhere, and indeed, it was set to automatically dim the screen after 5 minutes. 
2 Likes
Running Plasma, updated system via Pamac, all seemed to go fine, and when finished I closed Pamac. With no other windows or desktop programs running other than a konsole I was using nano from just before update, rebooted from there like many times prior.
PC reboots fine, comes to log in screen and typing in my password does nothing, screen username grays out slightly, looks like it’s going to log in but never does.
If I press CTRL+ALT+F3, log in and enter,
startx
it will put me in my desktop, asking for wallet password and Wi-Fi password and all seems fine until next boot. Anyone else have this issue or ideas how to fix?
@zo0M try this, should probably work for you too. I guess my issue is not plasma specific since you appear to be running gnome and have it too.
1 Like
ZFS :: zfs-dkms (2.2.0-2). in my case.
Now, I am using 6.6.0 with ZFS.
There have been some odd things(strange phenomena) with ZFS, but ZFS is available at the moment. This is the pamac log from earlier. zfs-dkms (2.2.0-2).
removed zfs-dkms (2.2.0-1)
Yesterday I was failing with dkms by all means with the following kernels.(ZFS ng)
6.6.0-1-MANJARO
6.6.0-AMD
6.6.0-AMD-znver3Yesterday I was sucessing with dkms by all means with the following kernels.(ZFS OK)
6.1.60-1-MANJARO
6.4.16-5-MANJARO
6.5.9-1-MANJARO
$ uname -r
6.6.0-1-MANJARO
$ zpool status -pv
pool: ZET
state: ONLINE
[2023-11-07T21:22:31+0900] [ALPM] installed zfs-dkms (2.2.0-2)
[2023-11-07T12:29:55+0900] [ALPM] upgraded vmaf-git (2.3.1.r168.g5ec4e265-1 -> 2.3.1.r169.g0f841517-1)
[2023-11-07T12:28:01+0900] [ALPM] upgraded visual-studio-code-bin (1.84.0-1 -> 1.84.1-1)
[2023-11-07T12:23:47+0900] [ALPM] upgraded fish-fzf (10.1-1 -> 10.2-1)
[2023-11-07T03:42:02+0900] [ALPM] upgraded firefox-beta-bin (120.0b6-1 -> 120.0b7-1)
[2023-11-07T01:33:58+0900] [ALPM] removed zfs-dkms (2.2.0-1)
[2023-11-07T01:23:49+0900] [ALPM] installed linux66-headers (6.6.0-1)
[2023-11-07T01:23:47+0900] [ALPM] installed linux66 (6.6.0-1)
[2023-11-07T01:08:16+0900] [ALPM-SCRIPTLET] -> These were most likely installed directly by cpan or a similar tool.
[2023-11-07T01:08:16+0900] [ALPM-SCRIPTLET] WARNING: '/usr/lib/perl5/5.36' contains data from at least 1 packages which will NOT be used by the installed perl interpreter.
[2023-11-07T01:08:16+0900] [ALPM-SCRIPTLET] -> These were most likely installed directly by cpan or a similar tool.
[2023-11-07T00:52:08+0900] [ALPM] upgraded yt-dlp (2023.10.07-1 -> 2023.10.13-1)
[2023-11-07T00:52:08+0900] [ALPM] upgraded xterm (385-1 -> 388-1)
The following is a log.
Arming ConditionNeedsUpdate...
Install DKMS modules
==> dkms install --no-depmod zfs/2.2.0 -k 6.6.0-AMD
==> dkms install --no-depmod zfs/2.2.0 -k 6.4.16-5-MANJARO
==> dkms install --no-depmod zfs/2.2.0 -k 6.6.0-1-MANJARO
==> dkms install --no-depmod zfs/2.2.0 -k 6.1.60-1-MANJARO
==> dkms install --no-depmod zfs/2.2.0 -k 6.5.9-1-MANJARO
==> dkms install --no-depmod zfs/2.2.0 -k 6.6.0-AMD-znver3
==> depmod 6.4.16-5-MANJARO
==> depmod 6.5.9-1-MANJARO
==> depmod 6.6.0-1-MANJARO
==> depmod 6.1.60-1-MANJARO
==> depmod 6.6.0-AMD
==> depmod 6.6.0-AMD-znver3
(success.)
In my case, I don’t have any problems in my current environment.
So it may not be very helpful. In fact, since last month, I have been taking action to eradicate ZFS. I decided to move everything to BTRFS RAID.
My ZFS dismantling process is almost in its final stages. It just happened to coincide with the policy of the Manjaro development team. ZFS is very nice, but you can’t use it with timeshift, for example.
I found that perl-linux-inotify2 needed reinstalling (due to new Perl version), but that package no longer seems to exist (I don’t think it was an AUR package). Had to install directly from CPAN.
[Edited to remove irrelevant KDEConnect comment].
I found a problem with the latest version of Wine Staging, some applications do not connect to the network. I solved the Problem downgrading to version 8.15.2.
Packages don’t work. I got that error message
files conflict
linux65-zfs : /usr/lib/modules/6.5.9-1-MANJARO/extramodules already exists in filesystem
Folder contains nvidia and virtualbox modules but nothing related to zfs’s module
1 Like
Don’t Do That!™
Just use… 
sudo pacman -Syuu
… this one time to install the updated package.
(This was already mentioned several times on the thread. Next time please read before posting.)
1 Like
xsensors 0.80.
Cinnamon edition.
This program now stops from time to time. If I request a high load from the CPU, it seems that the update will definitely get stuck.
I think they must have been posted between me reading the thread before upgrading and me coming back after upgrading.
Though since KDEConnect is the only package I use that needs those packages, it’s as good a workaround for me as any other.
i can confirm, samething over here
After recent updates there are the following issues:
More than agree, ZFS is major FS it should be supported and it works in many distros and bsds. If it fails it means something wrong not with ZFS but with environment.
6 Likes
OK, I’ll recheck the packaging. Maybe some went wrong in placing the modules.
3 Likes
After the update parts of GNOME (the applications) have green accent (Maia) and part (the shell) appear in default GNOME blue. How do I make it consistent like it was before? I prefer Maia accent.
1 Like