I notice that the new GIMP release seems to have its default theme messed up (fonts too big, toolbox icons too small). Playing around with the adjustments in settings doesn’t seem to help.
If anyone else dislikes this, my fix is to restore /usr/share/gimp/3.0/themes/Default from your last backup as /usr/share/gimp/3.0/themes/MyDefault, then choosing MyDefault in GIMP’s settings.
It’s probably theme-related. My gimp does not appear to be affected, but I am using a non-standard gtk theme from the AUR. 
Very much so, as restoring the previous theme fixes it.
openssl-1.1 is required by python2 which is way outdated. Check for ancient packages which use python2 like fslint
/usr/share/sddm/themes/breeze/ is owned by plasma-desktop 6.5.5-1
/usr/share/sddm/themes/breath/ is owned by sddm-breath-theme 24.0.0-6
Well, in that case I guess it’ll be reinstalled when plasma-desktop gets updated. Or not, because plasma-login-manager is scheduled for Plasma 6.6, and therefore it is possible that 6.6 does not push an sddm theme on our systems anymore.
I posted a picture of text, because nobody needs to search or paste and copy. And the picture showed the error best. Its not my fault when pamac CLI is buggy. To show the error the best way was a picture. It is now for a longer time when pamac CLI crashing more or less. Still no workarounds except not using pamac. This is not a good solution anyway.
Best regards
CC
Therefore:
Whats this:
Best regards
CC
A picture still takes up more room in the database than plain text.
No, it’s not.
That is a photo from a tty. One cannot copy/paste from a tty, because it’s a raw-text framebuffer.
It works for me on X11.
Apparently it still does for now, but not for much longer. Native X11 support is scheduled for removal in Plasma 6.8, and plasma-login-manager will be fully integrated in the Plasma experience, whereas sddm is actually a separate project that the KDE developers do not control.
After the update I discovered fragments & transmission would not work. Tracked it down to transmission.service being disabled.
What would have caused this?
transmission-gtk 4.1.0 does have a regression - magnets dont work.
__
Additionally, Gnome media sharing started advertising 2 copies over the network.
In my case: In System Settings GUI I only share 1 folder from an external drive & all other folders are removed. (That choice is saved in ~/.config/rygel.conf)
However, in /etc/rygel.conf there is a [LocalSearch] share & its enabled by default. - this is causing the duplicate.
I overrode it in ~/.config/rygel.conf
[LocalSearch]
enabled=false
Just noticed that the plasma-login-manager has one annoying thing. It hides the login and when you type with your keyboard it doesn’t pop back in. That makes you have to press Enter twice after your credentials are typed. It does accept the letters, but the view stays hidden.
I hope they make it so that pressing keyboard keys actually makes it show the login screen in it’s entirety.
Magnet links no longer working · Issue #8123 · transmission/transmission · GitHub
The fix landed a few days ago at #8277 and will be included in 4.1.1.
I’ll need to coordinate with the other people who build & sign the releases, so I don’t have a date in mind yet. Also there are some other bugs that need to get fixed before 4.1.1.
But my guess is 1-2 weeks. Not months.
As i mentionend in another topic to you already, i have this on my radar already, thats why i bought a AMD GPU (RX 9070) already to switch to Wayland when the time is ready to switch, i just delay the replacement with my nvidia card.
Till then, X11 user’s like me can still stay at least for full 10 Month on X11 (if not longer, no one knows the exact timestamp when Wayland is ultimate forced on all KDE user’s in 2027), hopefully nvidia driver’s will have better Wayland support till then. 
At the moment, Nvidia X-Server is a mess. And GPU Prices went already ~100€ higher just in the last 3 weeks in germany.
I just wait 2-3 release updates (waiting for more hotfixes, there is a good reason why Manjaro delayed newest KDE releases in the past) and then i switch to plasma-login-manager.
My AMD Laptop is already running with Wayland.
Thanks for the info, i will make the switch to plasma-login-manager on my X11 system then, just with a little delay.
Whooow, thats bad. My Wayland Session on my machine is laggy as f***. What can i do for getting a better performance? When KDE Plasma is getting to support wayland only, i have to switch to xfce.
My System:
System:
Host: rich-pc Kernel: 6.12.68-1-MANJARO arch: x86_64 bits: 64 compiler: gcc
v: 15.2.1 clocksource: hpet
Desktop: KDE Plasma v: 6.5.5 tk: Qt v: N/A wm: kwin_x11 vt: 2 dm: SDDM
Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: N/A v: N/A
serial: <superuser required> Chassis: type: 3 serial: <superuser required>
Mobo: Gigabyte model: X79-UD3 serial: <superuser required>
uuid: <superuser required> Firmware: BIOS vendor: American Megatrends v: F20
date: 03/19/2014
Battery:
Device-1: hidpp_battery_0 model: Logitech MK700 serial: b9-e4-c8-7d
charge: 70% (should be ignored) rechargeable: yes status: discharging
Device-2: hidpp_battery_1 model: Logitech Marathon Mouse/Performance Plus
M705 serial: 76-a6-79-0f charge: 5% (should be ignored) rechargeable: yes
status: discharging
Memory:
System RAM: total: 32 GiB available: 31.26 GiB used: 2.34 GiB (7.5%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 96 GiB slots: 4 modules: 4 EC: None
max-module-size: 24 GiB note: est.
Device-1: Node0_Dimm0 type: DDR3 detail: unbuffered (unregistered)
size: 8 GiB speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
manufacturer: N/A part-no: F3-1600C10-8G serial: N/A
Device-2: Node0_Dimm1 type: DDR3 detail: unbuffered (unregistered)
size: 8 GiB speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
manufacturer: N/A part-no: F3-1600C10-8G serial: N/A
Device-3: Node0_Dimm2 type: DDR3 detail: unbuffered (unregistered)
size: 8 GiB speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
manufacturer: N/A part-no: F3-1600C10-8G serial: N/A
Device-4: Node0_Dimm3 type: DDR3 detail: unbuffered (unregistered)
size: 8 GiB speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
manufacturer: N/A part-no: F3-1600C10-8G serial: N/A
CPU:
Info: 6-core model: Intel Core i7-3930K bits: 64 type: MT MCP smt: enabled
arch: Sandy Bridge rev: 7 cache: L1: 384 KiB L2: 1.5 MiB L3: 12 MiB
Speed (MHz): avg: 1293 min/max: 1200/3800 cores: 1: 1293 2: 1293 3: 1293
4: 1293 5: 1293 6: 1293 7: 1293 8: 1293 9: 1293 10: 1293 11: 1293 12: 1293
bogomips: 76829
Flags: acpi aes aperfmperf apic arat arch_perfmon avx bts clflush cmov
constant_tsc cpuid cx16 cx8 dca de ds_cpl dtes64 dtherm dts epb ept est
flexpriority flush_l1d fpu fxsr ht ibpb ibrs ida lahf_lm lm mca mce
md_clear mmx monitor msr mtrr nonstop_tsc nopl nx pae pat pbe pcid
pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdtscp
rep_good sep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
tpr_shadow tsc tsc_deadline_timer vme vmx vnmi vpid x2apic xsave xsaveopt
xtopology xtpr
Graphics:
Device-1: NVIDIA GK107 [GeForce GT 640] vendor: ASUSTeK driver: nvidia
v: 470.256.02 arch: Kepler-2 pcie: speed: 5 GT/s lanes: 16 ports:
active: none off: VGA-1 empty: DVI-D-1,DVI-D-2,HDMI-A-1 bus-ID: 02:00.0
chip-ID: 10de:0fc1 class-ID: 0300
Display: x11 server: X.Org v: 21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 95 s-size: 513x292mm (20.20x11.50")
s-diag: 590mm (23.24")
Monitor-1: VGA-1 mapped: VGA-0 note: disabled model: Samsung S23B550
serial: H4MCB01752 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 96
size: 510x287mm (20.08x11.3") diag: 585mm (23") modes: max: 1920x1080
min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: kms_swrast surfaceless: drv: swrast x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 470.256.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GT 640/PCIe/SSE2
API: Vulkan v: 1.4.335 layers: 3 surfaces: N/A device: 0
type: discrete-gpu driver: nvidia device-ID: 10de:0fc1
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel C600/X79 series High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1d20
class-ID: 0403
Device-2: NVIDIA GK107 HDMI Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel pcie: speed: 5 GT/s lanes: 16 bus-ID: 02:00.1 chip-ID: 10de:0e1b
class-ID: 0403
API: ALSA v: k6.12.68-1-MANJARO status: kernel-api with: aoss
type: oss-emulator
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.4.10 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
Device-1: Intel 82579V Gigabit Network vendor: Gigabyte driver: e1000e
v: kernel port: f040 bus-ID: 00:19.0 chip-ID: 8086:1503 class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 90:2b:34:57:9e:d5
IP v4: ***** type: dynamic noprefixroute scope: global
broadcast: ****
IP v6: *****
type: dynamic noprefixroute scope: global
IP v6: ******* type: dynamic noprefixroute
scope: global
IP v6: ******* type: noprefixroute scope: link
IF-ID-1: virbr0 state: down mac:
IP v4: **** scope: global broadcast: ***
WAN IP: ****
Bluetooth:
Message: No bluetooth data found.
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 3.87 TiB used: 452.96 GiB (11.4%)
ID-1: /dev/sda vendor: Samsung model: SSD 850 PRO 256GB size: 238.47 GiB
speed: 6.0 Gb/s tech: SSD serial: S39KNX0J711905L fw-rev: 4B6Q scheme: MBR
ID-2: /dev/sdb vendor: Western Digital model: WD4001FAEX-00MJRA0
size: 3.64 TiB speed: 6.0 Gb/s tech: N/A serial: WD-WCC130163113
fw-rev: 1L01 scheme: GPT
Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE BH16NS40 rev: 1.00
dev-links: cdrom
Features: speed: 48 multisession: yes audio: yes dvd: yes
rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
ID-1: / size: 238.47 GiB used: 37.8 GiB (15.9%) fs: btrfs dev: /dev/sda1
label: N/A uuid: ****
ID-2: /home size: 3.58 TiB used: 415.15 GiB (11.3%) fs: ext4
dev: /dev/sdb1 label: N/A uuid: ****
ID-3: /var/cache size: 238.47 GiB used: 37.8 GiB (15.9%) fs: btrfs
dev: /dev/sda1 label: N/A uuid: ****
ID-4: /var/log size: 238.47 GiB used: 37.8 GiB (15.9%) fs: btrfs
dev: /dev/sda1 label: N/A uuid: ****
Alert: No swap data was found.
Unmounted:
Message: No unmounted partitions found.
USB:
Hub-1: 1-0:1 info: full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s
lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900
Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
speed: 480 Mb/s lanes: 1 chip-ID: 8087:0024 class-ID: 0900
Hub-3: 2-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900
Hub-4: 3-0:1 info: full speed or root hub ports: 2 rev: 2.0
speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900
Hub-5: 3-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
speed: 480 Mb/s lanes: 1 chip-ID: 8087:0024 class-ID: 0900
Device-1: 3-1.1:3 info: Logitech Unifying Receiver
type: keyboard,mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3
rev: 2.0 speed: 12 Mb/s lanes: 1 power: 98mA chip-ID: 046d:c52b
class-ID: 0300
Hub-6: 4-0:1 info: super-speed hub ports: 2 rev: 3.0 speed: 5 Gb/s
lanes: 1 chip-ID: 1d6b:0003 class-ID: 0900
Hub-7: 5-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900
Hub-8: 6-0:1 info: super-speed hub ports: 2 rev: 3.0 speed: 5 Gb/s
lanes: 1 chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
System Temperatures: cpu: 29.0 C mobo: N/A gpu: nvidia temp: 40 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 10%
Info:
Processes: 303 Power: uptime: 9m states: freeze,mem,disk suspend: deep
wakeups: 0 hibernate: platform Init: systemd v: 258 default: graphical
Packages: 1661 pm: pacman pkgs: 1635 pm: flatpak pkgs: 26 Compilers:
gcc: 15.2.1 Shell: Bash v: 5.3.9 running-in: konsole inxi: 3.3.40Thanks for the help
Laptop with an Intel BE201 Wi-Fi/Bluetooth card, linux-firmware-intel 20260110-1 broke Bluetooth (Bluetooth keyboards did not work).
They resumed working after manually downgrading to linux-firmware-intel 20251125-2 via pacman cache.
I assume the issue was caused by this:
And there has been another update to the firmware for the BE201 since the latest release:
How does one file a bug for linux-firmware?
What’s the release cadence there?
Which guides? For there is none below…
There is …
Just a little more below.
Oh, you mean the ones from previous upgrades? I was reading the text as if that was something new, important for people upgrading specifically to this new upgrade. It’s a bit confusing, I think, perhaps the warning could be improved. Anyway, Thanks!
I see you’re a 1st time poster… not sure how long your GNU/Linux experience is… I thought I might pass along some advise / knowledge / opinions that you might find useful.
GUI tools are nice… when they work. I know that pamac-gtk (the “add/remove software” gui) has a little “chevron”/arrow in the bottom right that people can click to watch the progress/log… but I bet there are folks who are oblivious to it… and having access to see the log via the GUI only works so long as the application does not terminate/close.
I know it’s been suggested/highlighted with some updates that “toolchain” is involved/impacted… and in these cases it’s recommended to use “pacman-static” to do the update as it’s not affected by the low level dependencies like glibc changing during the update process.
And why is this important? Because here (and perhaps all Arch-based distro’s) updates are applied to a live system… Windows and some Linux Distro’s like Debian download updates, reboot, install the updates, then load back into the desktop. Updating a LIVE system needs special care/attention… as when something “breaks” (like a critical dependency being replaced)… things fail / terminate. We reboot to load the new kernel and app configs, but at no point during our install was the system in a “safe” state.
So this scratches the surface of why “we” need to have awareness of what type, like (toolchain or not) of updates we are downloading so that we can change our approach to increase success.
Give [HowTo] Updating Manjaro as safely as possible a read… it provides more background for what I’ve provided.
I never use the GUI tools for system updates. I don’t always follow the advise of the link I provided in ensuring I always use a TTY… in those cases I opt to use a terminal. As a plasma DE user, I generally save the TTY updates for when there has been a major KDE update… like moving between major versions.
So let’s circle back to your experience and try answer some questions directly…
Why did the pamac-gtk (gui updater/installer) terminate mid update?
I can’t know for certain, but I would suspect (a) something related to toolchain or (b) another important dependency for the app changed during the update process and caused the failure.
The other thing to note is that pamac-gtk is kinda like a “wrapper” in that it isn’t doing the work directly… but is running “terminal” commands in the background to accomplish it’s tasks… so even though the GUI failed, the task is likely still running… verify that before doing anything “drastic” like rebooting before you know what’s gone / going on.
Where can I check on the status / log of an update?
Typically, regardless of the update method, you should be able to find a log of all updates in the file /var/log/pacman.log
If in a terminal type something like cat /var/log/pacman.log | more, or open the file in your favorite GUI text editor.
keep rerunning the command or refreshing the GUI text viewer/editor to watch new lines being added as progress is being made.
All successful updates finalize with the following line…
[ALPM] transaction completed… until you see this, keep refreshing, and don’t think about rebooting.
Why are initramfs files deleted during an update?
If you check the update log file, you’ll see a “hook” that ran shortly after the update files were downloaded… [ALPM] running '60-mkinitcpio-remove.hook'... So it’s by design, and can think of at least 2 reasons:
initramfs files need to be purged to make space for the new onesinitramfs files createdoh, and guess what hook runs shortly after all the downloaded updates are applied?
[ALPM] running '90-mkinitcpio-install.hook'... yup, it recreates new initramfs files so they are present for the reboot (Note: followed by a GRUB update hook)
What’s a better way to to update the system?
Whether using TTY or terminal I always follow the same recipe:
pacman-mirrors --status … verify all listed mirrors have a “sync’d” status of OK… if not, abort and try again latersudo pacman -Syy … update the package database (before updating)sudo pacman -Syu or sudo pacman-static -Syu … update system (use the second command when “toolchain” is involved or if you’re not sure) … (install pacman-static via sudo pacman -S pacman-static)grub and via mkinitcpio were successful… if not, troubleshoot and fix before continuingDIFFPROG=meld pacdiff -s … use meld (a GUI app) to manually merge the proposed config file changes … OPTIONAL for new users, but something to keep an eye on and get comfortable with config file contents over time via cat /var/log/pacman.log | grep pacnew[ALPM] warning: /etc/mkinitcpio.conf installed as /etc/mkinitcpio.conf.pacnew .. tells you the two files to look atpacman -Qdt … list out the orphan packagessudo pacman -Rns $(sudo pacman -Qdtq) .. remove all orphan packagespacman -Qm … list all foreign packagessudo pacman -Rns $(sudo pacman -Qmq) … removes all foreign packagessudo pacman -Rns package1 package 2 .. selectively remove foreign packagespamac update -a … update the AUR packages … Note: I sometimes defer this until after the reboot