Arch Linux BBS - Applications & Desktop Environments

https://archlinux.org/packages/extra/x86_64/colord-kde/https://wiki.archlinux.org/title/ICC_pr … C_profilescolord-kde was dropped from the repositories as it seems to not be needed now that KDE is Wayland-only. We should probably add a section about KDE's support of ICC profiles since it does not seem to depend on colord

I'm having a similar issue, in that Blender straight will not detect my NVIDIA GPU, regardless of whether I activate CUDA or OptiX.I'm using:nvidia-580xx-dkms 580.196.07-1 cuda 13.4.3-1 blender 17:5.2.3-5

seth wrote:It's likely one of those - can you try adding0.0.0.0 pagead2.googlesyndication.com 0.0.0.0 www.googletagmanager.com to your /etc/hostsI did, but it didn't help (with 6.11.1-3 nor 6.11.1-4). Meanwhile, qt6-webengine 6.11.3-2 appeared and no crashes happend since the upgrade (with or without blocking the domains).Marking this solved, thanks for help.

BTW, You can suppress these broadcast messageson restart/reboot in KDE with the following mod;edit /etc/systemd/logind.conf and insert;WallMessages=nothis does not however explain why the broadcast only occurs in KDEand not other desktop environments...

https://wiki.archlinux.org/title/Environment_variables

a_manthey wrote:i run hyprland with nwg-panel.After updating hyprland config to lua-syntax the screenshot-applet did not work any longer, see https://github.com/nwg-piotr/nwg-shell-config/issues/95 anagram solversince a few days i get similar errors when clicking on panel executors:$ nwg-panel -c preset-hypr -s preset-hypr.css ... Executing: hyprctl dispatch exec "swaync-client -t" error: 3 [string "return hl.dispatch(exec swaync-client -t)"]:1: ')' expected near 'swaync' → Note: dispatch in lua is a shorthand for hl.dispatch(...), your syntax might need to be updated. Executing: hyprctl dispatch exec "hyprshutdown" error: 3 [string "return hl.dispatch(exec hyprshutdown)"]:1: ')' expected near 'hyprshutdown' → Note: dispatch in lua is a shorthand for hl.dispatch(...), your syntax might need to be updated.Any help appreciatedIt looks like the issue may be related to a syntax change in the Hyprland configuration or the way the panel executes commands through Lua. I would recommend checking whether the updated configuration uses the correct hl.dispatch syntax and whether the affected commands still match the current Hyprland version. You could also try updating nwg-panel and its related components to the latest compatible versions. Hopefully, someone familiar with the recent changes can help identify the exact cause.

Thanks a lot, ldd was really helpful.After running thisfd --type x --hidden --no-ignore --search-path /usr -x sh -c ' if ldd "$1" 2>/dev/null | grep -q "libhyprutils.so.12"; then owner=$(pacman -Qoq "$1" 2>/dev/null || echo "(not owned)") printf "%s: %s\n" "$owner" "$1" fi ' _ {}(its smaller versionfd --type x --hidden --no-ignore --search-path /usr -x sh -c 'ldd "$1" 2>/dev/null | grep -q "libhyprutils.so.12" && echo "$1"' _ {}would have been enough)I found out that in /usr/local/bin there were some binaries (hyprctl, hyprland, Hyprland, hyprpm, start-hyprland) that required the old libhyprutils.so.12After moving them to a backup directory and updating again, hyprland now doesn't crash on startup and runs again.

Oops... I spoke too fast actually it was updated later than the update.All works fine now.

A packaging error that exclusively affects you. Sure.Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855 - post the actual error you encounter verbatim.appimages simply bundle most dependencies, so any issue w/ local libraries and paths won't affect them.

Thanks for the advice.I will mark the thread solved and hopefully the issue won't happen again with either lower refresh rate or VRR enabled.

Removing pulse-audio fixed it for me as well. I somehow already had pipewire and wireplumber installed, so I only had to do the following: # Install the pulseaudio compatibility package for pipewire sudo pacman -Syu pipewire-pulse # Remove pulseaudio remnants sudo pacman -Rns lib32-libpulse pavucontrol pulseaudio-alsa

Thank you, but I'm afraid I don't use IRC. Anyway, I see that the new 1.6.11 version is in Extra-Staging and I think it might solve this problem.

Setup: Arch, GNOME 51 on Wayland, QT_QPA_PLATFORMTHEME=qt6ct.Symptom: Dolphin started with white/black alternating rows in Details view and a light sidebar. It only looked right after re-applying the color scheme in Dolphin (Default -> restart -> Breeze Dark), every single time.Fix: use the -kde variants from the AUR and select Breeze Dark in them. Plain qt6ct/qt5ct only list their own palettes (airy, darker, ...). The -kde variants can load KDE color schemes and offer "Breeze Dark (KColorScheme)":yay -S qt6ct-kde qt5ct-kdeThen in both qt6ct and qt5ct: Appearance -> Color scheme -> Breeze Dark (KColorScheme).Extra pitfall: if qt6ct shows "The application is not configured correctly" orThe libqt6ct.so plugin is compiled against incompatible Qt version (x.y.z).the plugin was built against an older Qt and silently doesn't load. Rebuild it:yay -S --rebuild qt6ct-kdeSince these are AUR packages, rebuild them after every qt6-base / qt5-base update.Related KDE bugs: https://bugs.kde.org/show_bug.cgi?id=513322 and https://bugs.kde.org/show_bug.cgi?id=513338

I've been using Nemo file manager standalone in my Niri+DankMateralShell setup. I have been able to pin files and folders and it would appear bold and sorted to the top of the list. For some reason, after an update in the past month, all my pinned files don't appear pinned anymore and I can't pin other files either.Weirdly enough, Favourited files also don't have the star in the icon anymore, either.I've checked out this post in the Linux Mint forums and I got nothing. gio doesn't fail and the files still don't show up pinned.Has this stopped working for anyone else?EDIT: It might have fixed itself after an update.

sudo cmake .. -DCMAKE_BUILD_TYPE=Release -DSTRATA_ENABLE_HIP=ON -DCMAKE_HIP_ARCHITECTURES=gfx1012Things set in ~/.bashrc are only valid for your normal user, no idea which environment vars cmake sees when running with root rights.CMAKE_INSTALL_PREFIX on unix systems defaults to /usr/local, no need for root rights.What is the output of that cmake command ran as normal user ?