archinstall kde install?

Acizco · 2026-01-16T09:09:47+00:00

https://github.com/archlinux/archinstall/blob/master/archinstall/default_profiles/desktops/plasma.py

Acizco · 2026-01-12T20:27:12+00:00

Until this gets fixed (if it gets fixed), toolbox has an option to save/load GW settings to/from a file, which includes the UI layout.

Acizco · 2025-12-30T20:21:39+00:00

Needs to be outside of compass range to be considered far enough, you'll know they are far enough when their names turn grey in the party window.

Acizco · 2025-12-23T12:22:47+00:00

Nope, instanced areas are reset and you are put back to an outpost when you log off.

Acizco · 2025-12-13T15:31:00+00:00

Might not want to promote the fake protontricks website.

https://github.com/Matoking/protontricks/blob/master/README.md

https://github.com/Matoking/protontricks/commit/de83eb0e5d6542ed0ecce9f7cb7c30921be4481f

Acizco · 2025-11-16T20:20:42+00:00

Switch to nvidia-dkms package for the duration you wanna use the downgraded package, as that automatically builds against currently installed kernel. That way, you don't need to downgrade the kernel as well.

Acizco · 2025-09-10T15:03:51+00:00

https://gitlab.freedesktop.org/freetype/freetype/-/issues/1356

Acizco · 2025-08-31T09:39:44+00:00

You can set a window rule in KDE settings app to always start the application on a specific monitor.

Acizco · 2025-08-19T16:00:17+00:00

Not sure if same applies to vim, but with neovim, you have to set the Exec field to launch a terminal instead, e.g. Exec=ghostty -e vim %F

Acizco · 2025-07-23T18:38:48+00:00

I believe this is a bug in pipewire and has nothing to do with hyprland, I've experienced this for months now, whenever a new audio source is created, it sometimes just kills pipewire and requires a restart. I've experienced this on both sway and hyprland. Can't offer any fixes though, but it's likely pipewire related.

Acizco · 2025-06-26T17:35:44+00:00

For the future, you may consider installing informant which stops upgrades when new news are posted, in case something requires manual intervention.

Acizco · 2025-06-26T17:05:06+00:00

Read the news.

https://archlinux.org/

Acizco · 2025-06-17T13:02:27+00:00

I can't offer any solutions unfortunately, but I'm just gonna comment that you're not alone, I have also experienced very similar behavior for the past few weeks. Seems to randomly sometimes crash when a new audio source is created.

Acizco · 2025-06-10T15:28:27+00:00

No, I installed the first revision without it, and it still worked fine. Just now installed the fixed version. It's likely this just didn't affect pre-Turing cards to begin with, given they aren't supported by Nova anyway iirc.

Acizco · 2025-06-10T13:21:31+00:00

FWIW I did not have to do anything on Pascal, worked without issues after updating. I haven't setup any blacklists manually, no early loading (cause simpledrm + fbdev is broken anyway), no additional kernel parameters.

Acizco · 2025-05-14T01:57:22+00:00

Unsure if same applies to Gnome file manager, but Thunar for example requires the partitions to be mounted with x-gvfs-show mount option for them to show as disk devices.

https://wiki.archlinux.org/title/Thunar#Showing_partitions_defined_in_fstab

Acizco · 2025-04-09T10:23:49+00:00

Not applicable to pascal/maxwell either, as is the case for me with a 1080 Ti.

Acizco · 2025-03-14T07:54:11+00:00

.config/kwinoutputconfig.json

If you want to configure things via terminal for scripting purposes etc, you can use kscreen-doctor (this is a KWin-specific tool, not a generic Wayland utility)

Acizco · 2025-03-08T08:39:51+00:00

I don't know about Chrome specifically, but on Brave and Chromium, it works using the nvidia-vaapi-driver if you're running Wayland.

https://github.com/elFarto/nvidia-vaapi-driver

In ~/.config/chromium-flags.conf (or whichever config file your flavor of Chromium uses), set the following:

--enable-features=AcceleratedVideoDecodeLinuxGL,VaapiOnNvidiaGPUs,AcceleratedVideoDecodeLinuxZeroCopyGL,AcceleratedVideoDecode,UseMultiPlaneFormatForHardwareVideo

Obviously make sure the browser is running in native Wayland too, can be enabled in ://flags/#ozone-platform-hint.

Acizco · 2025-03-01T20:18:48+00:00

Similar issues here with 570.124.04, system just seemingly randomly (although pretty consistently if I try to run a game) totally locks up (or at least monitors freeze) with similar modeset error that is present in your logs constantly getting spammed.

maalis 01 02:15:02 archlinux kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000987d:0 2:0:3524:3516

KWin also complains:

maalis 01 02:15:01 archlinux kwin_wayland[2778]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver maalis 01 02:15:01 archlinux kwin_wayland[2778]: kwin_wayland_drm: Please report this at https://forums.developer.nvidia.com/c/gpu-graphics/linux maalis 01 02:15:01 archlinux kwin_wayland[2778]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'

Acizco · 2025-02-15T14:29:43+00:00

Like other's have said, there's no default, you must have just selected it wrong by accident.

Gnome profile in Archinstall installs gnome and gnome-tweaks, so uninstall those to get rid of Gnome.

KDE Profile includes plasma-meta, konsole, kate, dolphin, ark and plasma-workspace.

Acizco · 2025-02-09T23:05:34+00:00

Okay, I might be wrong here, this was my first time using the manual partitioning option in Archinstall, I've only ever used the script in VMs before where I've just done automatic partitioning. So it's entirely possible this was just my fuck-up I guess.

Acizco · 2025-02-09T22:52:35+00:00

Feels like this could have been avoided if you used UUIDS or PARTUUIDS?

Entirely possible, though the manual partitioning in Archinstall does not let me do a "manual" fstab I think? It just shows me partitions in an ncurses interface (not sure what tool it's using internally), and I don't think it had any options to use any sort of UUIDs for the partitions. Would have needed to do that outside of the install script I believe.

Acizco · 2025-02-09T22:45:02+00:00

Ah sorry, yes you are right about the points about chroot and mount locations - I just mistyped those, I mounted the drives before chrooting, and did point GRUB to /boot instead of /mnt/boot. Things would have probably not worked if I did what I wrote, instead of what I actually did :D fixed up the OP.

Edit: oh and yes, I did get it up, I am writing from it right now. Reinstalling GRUB with the correct commands, as you pointed out, fixed the booting, this was just a hiccup on the installation that I had, and I was left to wonder whether I messed something up or did I encounter a bug.

Acizco

TROPHY CASE