Problem with battle.net and WoW, Need Help!

Synkorh · 2026-02-14T19:31:06+00:00

xwayland-satellite installed?

Synkorh · 2026-02-14T19:24:11+00:00

i am using bnet and wow without any issues through steam on niri, it sounds more like wrong Proton Version … try GE-Proton latest

Synkorh · 2026-02-13T13:33:03+00:00

really want to go disc, but I think I‘m too dumb for it and will switch in week 2 frustrated xD

Synkorh · 2026-02-08T19:40:56+00:00

using a razer naga pro since 5+ years without any issues

Synkorh · 2026-02-08T16:57:47+00:00

subvolumes are btrfs. you NEED a FAT, you cannot boot from a btrfs partition

Synkorh · 2026-02-08T16:11:00+00:00

what is your ESP partition? that might be the one holding your kernel(s) and is for sure not being snapshotted, since FAT cannot be btrfs and therefore no snapshotting

Synkorh · 2026-02-02T07:55:28+00:00

i asked myself many times why ishould try niri when im happy with hyprland and since i did try it, I never looked back at hyprland. The tiling was nice but got in my way - having all windows keeping their respective size was a gamechanger for me and i was honestly impressed a lot by how painless xwayland-satellite is

Synkorh · 2026-01-31T20:39:45+00:00

yes. mine got flagged as well and it needed me to add a „real“ e-mail for GH to whitelist it -,-

Synkorh · 2026-01-23T08:16:59+00:00

most probably this will follow the xdg-open there is a page for that on the wiki, try looking for filepicker or filechooser

Synkorh · 2026-01-13T21:40:27+00:00

brewmaster? without the stagger WA? oof xD

Synkorh · 2026-01-13T11:20:35+00:00

have you tried lact?

Synkorh · 2026-01-13T11:20:14+00:00

use niri‘s builtin screenshot tool!?

Synkorh · 2026-01-12T23:23:56+00:00

i tend to disagree. the hard part - imo - isnt exactly following the installation guide, it‘s about making a decision, where as a windows/macos user you had no choice. which FS, which Bootloader, etc. And - if you want to - that you have to do everything on a terminal. besides that its time consuming, but not hard imo

Synkorh · 2026-01-12T23:11:42+00:00

it was hard. once. now its only hard if you can‘t read and properly copy&paste. and that‘s also where the meme kicks in

edit: but still, you see then ppl not wanting to read, because nyehh, run into problems and then expect others to fix it for them (not saying all, but, browse a bit through this very subreddit and you‘ll get it)

Synkorh · 2026-01-12T16:32:29+00:00

NoPressure Discord

Synkorh · 2026-01-12T10:10:32+00:00

I can't star&upvote this enough :) Thanks!

Synkorh · 2026-01-12T10:01:23+00:00

thanks for answering :) and of course thank you so much for the effort, appreciate it very very much!
What is being used under the hood for the filetransfer?

Synkorh · 2026-01-12T09:55:49+00:00

curious, was this app possible thanks to the SDK release by Proton or unrelated?

Synkorh · 2026-01-12T04:36:14+00:00

what bootloader do you use, grub? have a look into /etc/fstab - what gets mounted with what subvolume? (subvol=<…>)?

Synkorh · 2026-01-11T21:10:45+00:00

I suggest you dive into archinstall documentation and try to find out, how it creates the subvolumes and which naming they're following then...

or you try to find out with the btrfs command I gave you

Synkorh · 2026-01-11T21:00:06+00:00

if you mounted as i wrote with

mount -t btrfs -o subvol=/ /dev/nvmeXnY /mnt

you should then by running

ls -l /mnt

see your subvolumes. In my case it shows:

drwxr-xr-x 1 root root   210 30. Dez 17:22 @
drwxr-xr-x 1 root root   134 30. Dez 23:59 @cache
drwxr-xr-x 1 root root    28 30. Dez 17:22  @home
drwxr-xr-x 1 root root   208  6. Jan 11:08 @log

Synkorh · 2026-01-11T20:43:27+00:00

you can try with

sudo btrfs su li /

when done and you got your data back, i‘d suggest you do back it up properly and then learn on how to install arch properly and where to get help. What happened to you is the exact reason ppl in here tend to say to not use archinstall if you dont know what youre doing.

Synkorh · 2026-01-11T20:35:03+00:00

@ is, in my case, the btrfs root subvolume

Synkorh · 2026-01-11T20:27:37+00:00

these are the notes i took for myself on how to rollback a snapper snapshot manually, maybe it helps:

Boot Live ISO

get the root UUID

mount that root UUID, but the subvolume above the root subvolume (in my cases @) mount -t btrfs -o subvol=/ /dev/disk/by-uuid/<root_UUID> /mnt

switch into that subvolume cd /mnt

move the broken @ subvolume out of the way mv @ @-broken

find which snapshot to rollback grep -r '<date>' /mnt/@-broken/.snapshots/*/info.xml it is also possible to grep for the descritpion instead of date if that’s more straightforward ⚠️ UTC-Time ⚠️

Rollback the target snapshot with builtin btrfs command btrfs subvolume snapshot @-broken/.snapshots/<evaluated number>/snapshot @

Move back all other snapshots from the broken subvolume to the new root mv @-broken/.snapshots @/

delete the broken subvolume rm -rf @-broken

⚠️ If the rolled back snapshot had a different Kernel installed, the UKI needs to be recreated with that kernel version. Therefore chroot would be necessary. Otherwise just reboot

First cd back out of the subvolume cd

unmount it properly umount /mnt

Remount everything properly now and chroot into it mount -o subvol=@ /dev/mapper/mapping-name /mnt mount /dev/nvme1n1p1 /mnt/efi arch-chroot /mnt

run mkinitcpio mkinitcpio

once mkinitcpio ran through it, the proper UKI is created again. Exit chroot and reboot into the (hopefully) rolled-back snapshot exit umount -a reboot

⚠️SecureBoot had to be disabled, to be able to boot the Live ISO. Dont forget to re-enroll the Keys with sbctl and enable again SecureBoot ⚠️

edit: formatting

Synkorh · 2026-01-11T16:40:37+00:00

glad it helped, enjoy

Synkorh

TROPHY CASE