I created this small script and thought it might be useful to someone else. Any feedback is welcome!

I watch the F1 on NowTV. In windows this works fine in Firefox but not in Linux. My research turned up various posts linking to the "widevine" package that depends on "glibc-widevine" but that seems to have disappeared. What happened to it? did it work? where can I get it? is there an alternative?

As title says.

I've followed this guide, everything is working as desired but I got myself thinking if it'd be possible in the future to add a second nvme (I have a 1 TB nvme now). I've googled a little but all that I found so far apparently was about expanding the very same drive used in the installation, not adding a second one.

Could anyone more experienced tell me if that's is possible in this context and, if so, point me in the right direction?

Okay so I just finished struggling through my archlinux install. I have arch Linux with hyprland now.

But I cannot figure out how to download anything.

At minimum i need a browser, and git. But I cannot figure out web downloads in kitty.

Edit: nmtui to connect to WiFi, and then a reboot solved it.

How do non explicitly installed package dependencies get updated in Arch? Do they update independently of the package that is dependent on them, or do they get updated when the parent package updates? Or is it some secret third thing?

Thanks!

cross-posted from: https://programming.dev/post/13156830

https://codeberg.org/cyber-luna/lunas

Archlinux: yay -S lunas

i made a versatile syncing cli program, lunas, that's capable of syncing local to local, local to remote, remote to local and remote to remote at the same time with many input directories, with their file attributes if enabled and more. It syncs both ways but it has src/dest options that can be assigned to individual input directories

it runs locally, unless remote syncing is used then it runs peer-to-peer using libssh/sftp

It can do sync removal between different input directories, meaning if u want to remove a file/directory that you don't want to sync back to other directories, you can "lunas -rm file" for local or "lunas -rrm user@ip:/path/to/dir" for remote and then use the option "-cr Y" while syncing to remove it from every other directories, or simply don't use this option and it should be ignored without removal, or "-cr S" and it should be synced back to the directory it was removed from, IF it was found in one of the other directories

it has an optional config file for defining presets for easier syncing instead of writing them each time in the cli

there are more options to it which can be found in the --help or in the man page for more details

a simple usage of lunas can be like this

lunas -p dir1 -p dir2 --dry-run

lunas -s dir1 -d dir2 -d dir3 -rd user@ip:dir4

lunas -r user@ip:dir1 -d dir2 -dr

lunas -rs user@ip:dir1 -d dir2 -cr Y

lunas -rd user@ip:dir1 -s dir2

lunas -p dir1 -p dir2 -p dir3 -p user@ip:dir4 -p user@ip:dir5

p: local path r: remote path , both of them are source and destination

s: source local path d: destination local path

rs: source remote path rd: destination remote path

-dr/--dry-run: outputs what would be synced without actually syncing them

-cr/--confirm-remove Y: confirms the sync removal as explained previously

Hey everyone, I'm currently trying out river wm. For some reason, actions that should invoke the file picker dialog (like uploading a file to a webpage) fail to bring up the dialog and just do nothing.

I've tried this in firefox and chromium to no avail in river, though they both work as expected in other window managers (I've tested sway and labwc). Anyone run into this issue before?

I'm running an nvidia card on X11 Plasma 6, with a 4K monitor alongside a QHD monitor. Both monitors are the same physical size, despite being different resolutions, so in the nvidia settings app, I've got the second X screen setup to generate 4K but downscale it to QHD in the output. It makes the second screen slightly blurry, but it's worth it for the ability to move windows back and forth without dealing with different resolutions.

The problem is, no matter what I do, I can't make the changes "stick". The nvidia applet has an option to save it to the x.conf file, and I've verified that it has done so in a text editor. But every time I boot, I have to change it in the nvidia settings applet again.

Is there something I'm missing with the way arch/kde handles x conf files? How do I make it stick between reboots?

Hello! I've got a new Arch install that I'm in the process of setting up, however I wanted to do things differently this time around for the goal of getting this system as stable as possible without sacrificing features. So, the AUR...

I've used yay extensively and paru briefly before, but this time to achieve that goal I wanted to try aurutils with a local repository. I'm in the process of setting that up and using the command: repo-add aur-local.db.tar which gives the output: ==> No changes made to package database.

In all the guides I've gotten open in all these tabs, the output I should be getting starts with this: ==> Creating updated database file...

When I run the command, for a microsecond I get a file appear in Thunar but then disappears. Running pacman -Syy fails as the repo's database file obviously doesn't exist. No matter what I search I can't find anyone else with this problem nor a solution.

My system is a manual Arch installation, no archinstall, using the XFCE desktop. My shell is fish and, I can't see this having any influence whatsoever but my DM is ly.

My pacman.conf: Gitea

My pacman.d/aur-local.conf: Gitea

I have an optimus laptop, and after the update to KDE6 optimus-manager stopped working. I needed a second display, and all my display outputs are on the Nvdia GPU, so I needed to switch. I tried many different X11 configs, envycontrol then more X11 configs, but I couldn't get it working right, it would only be the internal display or the external one, not both. after a few hours I gave up and tried optimus-manager again. This time I checked the error log and it was failing to load the nvidia module, I tried loading it manually but I got a "No such device" error, which is where the title of the post comes in. My GPU has disappeared from linux, it won't show up in lspci, lshw, nvidia-smi, or anything else it should. The only reference to the thing in dmesg I can find are :

[    0.216410] pci 0000:01:00.0: [10de:1ba1] type 00 class 0x030000
[    0.216419] pci 0000:01:00.0: reg 0x10: [mem 0xde000000-0xdeffffff]
[    0.216427] pci 0000:01:00.0: reg 0x14: [mem 0xc0000000-0xcfffffff 64bit pref]
[    0.216435] pci 0000:01:00.0: reg 0x1c: [mem 0xd0000000-0xd1ffffff 64bit pref]
[    0.216440] pci 0000:01:00.0: reg 0x24: [io  0xe000-0xe07f]
[    0.216445] pci 0000:01:00.0: reg 0x30: [mem 0xdf000000-0xdf07ffff pref]
[    0.216460] pci 0000:01:00.0: Enabling HDA controller
[    0.257300] pci 0000:01:00.0: vgaarb: bridge control possible
[    0.257300] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
[    0.270521] pci 0000:01:00.1: D0 power state depends on 0000:01:00.0

and then nothing, it doesn't even seem to try to load the nvidia module. I tried booting into windows and it shows up there fine, so the GPU didn't randomly die.
As far as I can tell I've rolled back everything I did in my histfile until it stopped working, The only thing I could think is I upgraded my kernel to (6.7.9) from (6.6.10), could that have caused it? I also tried adding pcie_port_pm=off to the kernel params from the archwiki, but still nothing. I'm just at a loss here, anyone have any ideas?

EDIT: I'm using the nvidia-dkms package
EDIT2: one kernel downgrade later and it's still not appearing, so thats not it.
EDIT3: fixed, see comments

Hello, I'm facing some rather annoying issues with running KDE6 on Wayland. Despite consulting the Arch Wiki and various online resources, I haven't been able to get it working. X11 works fine, so I've been sticking with X exclusively due to my limited experience with desktop Linux and troubleshooting.

For context, my setup includes an AMD 7950x with Unraid as the main OS. My daily desktop runs on a mainline Arch VM with an RTX 3070ti and a dedicated USB controller card passed through. This setup has been stable for months, serving my gaming and media needs.

When attempting a Wayland session, I select it, observe a brief black screen flash, and then return to the login prompt. This issue persisted through upgrades and tests on different distributions like Manjaro and Endeavor. I've also tried multiple Wayland compositors, all with the same outcome.

The only success I've had with Wayland was on Garuda, which defaults to Wayland. I'm keen on using Wayland due to its evolving features, especially since it's essential for running Waydroid.

Any assistance would be greatly appreciated. While my use case may be unique, Waydroid is crucial for specific Android apps vital to my workflow.

Thanks in advance!

Hi,

I am setting up archlinux on a zenbook pro duo UX582L, everything has been setup and is functional, minus audio.

I am running plasma 6, the latest kernel, and have tried about everything I can find online to get this working.

things I've tried:

Pulseaudio

Pipewire

https://www.reddit.com/r/ASUS/comments/o1k04p/ubuntu_linux_on_ux582_zenbook_duo/

everything relevant at https://wiki.archlinux.org/title/PulseAudio/Troubleshooting

https://www.linux.org/threads/no-sound-on-asus-zenbook-oled-ux3402za.45822/

https://github.com/thor2002ro/asus_zenbook_ux3402za

The speakers are un-muted. They show properly in the volume mixer both in plasma GUI and alsamixer UI, when adjusting audio through the plasma GUI it shows the test tone is being played through the speakers but nothing is played.

any help is appreciated. Thanks-

I was creating a new key for pass when I noticed a random expired GPG key assigned to a certain "Roderick van Domburg" in my list of keys. I don't know any Rodericks, and this laptop has been whipped clean.

Should I be concerned? How could this even happen???

I've been trying to install Arch on an old laptop for the past few days but for some reason it will not shut down if I'm using any kernel above version 6.7. It goes all the way through and gets to Reached target: System Power Off but then just sits there and never actually powers down. I waited 30 minutes in case it did something and it never did. I don't believe there is anything useful in the journalctl output as there's nothing after Reached target System Power Off but I'll paste it here in case: https://text.is/4KNL

I tried the shutdown troubleshooting steps from here: https://freedesktop.org/wiki/Software/systemd/Debugging/

The debug shell is no help as I can't access it once it hangs, and since it never finishes shutting down the logging script won't help. reboot -f and poweroff -f both work which made me think it wasn't a kernel issue, however it works fine using the linux-lts kernel. Because of this I tried manually downgrading to a few standard kernel versions from 6.6, 6.7 and 6.8 and only the ones above 6.7 had this issue. Specifically the latest lts version (6.6.23 at the time I tested) worked fine, 6.6.9 (the last 6.6 version in the main branch) worked fine, 6.7.arch1-1 and above didn't.

Weirdly I don't have any issues with the installation media (currently using the ones from 29th March and 1st April). I also tried Opensuse Tumbleweed which I believe is on the same kernel version and had no issues so it seems to be Arch specific. I also tried linux-zen in case that had any difference but it didn't help.

I have tried several re-installs with both legacy and UEFI boot, mostly minimal installs (base, linux, linux-firmware, linux-headers and nano). Since the live iso works I also tried installing all the packages from that but it still didn't work.

I'm completely out of ideas at this point. I can't see anything obvious in the kernel 6.7 changelog, but then I don't really know enough to know what to look for there. I know for now I can keep using the lts kernel but presumably at some point that will be upgraded to a version above 6.7 so that doesn't seem like a good long term solution, I'd also really like to know the root cause behind this as its been bugging me for days! The laptop is an Acer aspire E15 with an Intel 6500U (I have tried with the Intel-ucode package installed) and an Nvidia Geforce 920M.

Edit: somehow installing kde plasma has fixed the issue

I am going to request arch and the greater linux community replace xz with winrar.exe

This is a community effort.

I'm trying to install Arch on Btrfs but every time mkinitcpio runs it fails as shown in the attached screenshot. I've tried on the actual laptop which I'm trying to set up, and also on a couple of Hyper-V VMs set up as I usually do and I've never had this issue before. This happens when its run automatically after installing linux via pacstrap, and if I run it again while chrooted into the new system. If I format as ext4 instead I don't have any problems.

I have a single subvolume called root mounted at / and a fat32 volume mounted at /boot, and I'm using the latest arch install iso (2024.03.29). Any idea why this is happening? The Btrfs volume is on a single device so as far as I'm aware I don't need to add the btrfs module to mkinitcpio.conf

I find that I habitually open a terminal and run an update on every boot of my system (which gets rebooted once a day). I'm curious what other people do.

The past few times I’ve run yay I’ve got these warnings about packages that are orphaned/not in the AUR. Based on the names I’m assuming these are leftover from the upgrade from kde plasma 5 to 6, are these safe to remove now? And secondly how would I find orphaned packages like that if I wasn’t using yay since I never installed these from the AUR?

So I was wondering, is there a place you can make the --debug flag output to or if there was a default location besides the terminal itself?

Like the title says pacman -Syu is occasionally hard locking the computer forcing a power cycle. After restarting the computer the update will go fine after deleting the archives that are corrupted from the failed update.

It always hangs in the :: Running post-transaction hooks... part of the update. This time it hung specifically on the ( 3/19) Reloading system manager configuration...

I have tried to redirect the debug output like: pacman -Syu --debug >> ~/Desktop/pacdebug.txt but it seems that I only get the standard upgrade output.

Is there some other tool or steps I can use to investigate this?

This has been happening since I upgraded to KDE 6 but I don't think it's directly related to KDE it's just when it started.

Thanks!

~~Update for future peoples:~~

~~At this point I'm relatively sure that I had broken my kernel. I switched to a different kernel and the pacman freezing has stopped. Still testing but so far I'm pretty confident that was the issue as it has been several days without issue.~~

~~To future peoples that might be having a similar issue try a different kernel and if the issue is resolved, remove the broken kernel + kernel headers and reinstall it.~~

# pacman -Syyu

I'm running Garuda. My laptop screen is on its very last legs. I have an external monitor that connects via USB-C. It has a Display Port connection, but the laptop itself does not. I'm using HDMI to connect to a larger display, but not having two monitors available is driving me insane. I know that the firmware supports display over USB-C, since it has worked before on previous distros and on Windows. My issue is that I can't get the system to recognize the display, and I'm not sure where to start troubleshooting.

I can post whatever dumps etc. if asked, but here's a neofetch screenshot screenshot for starters:

Are there packages I need to install? Drivers? I'm clueless and would really appreciate a starting point at the least. The last thing I need is a broken system because I'd have to use the (almost) entirely broken laptop screen to attempt a reinstall/change the BIOS.

while true; do; sudo pacman -Syu --noconfirm; done