I don’t have any advice wrt the Discord app (I assume flatpak) but you should try Goofcord if you haven’t already, it’s what I use.
pinguinu [any]
- 0 Posts
- 7 Comments
I hadn’t read the other drive stuff. I’m guessing it’s the same case as mine since you planned or guessed you would be using Grub on your primary drive instead of Windows boot manager. I don’t have my computer with me but I would be willing to make a more concrete “tutorial”. You can DM me too
I had the exact same problem with regular Fedora KDE. In my case it turned out that it didn’t wipe out the entire Microsoft bootloader because there was a backup
bootx64.efi
. In the end I downloaded a windows installer iso, copied the boot* files and directory to efi/Microsoft/boot and copied that bootx64.efi and added it to the grub menu using the 40_custom file in grub.d and applied grub2-mkconfig -o /boot/grub2/grub.cfgTo boot from grub you use
set root
andchainloader /...
which you then write as a menuentrySorry for the bad reply but I’m working
pinguinu [any]@lemmygrad.mlto Linux@lemmy.ml•Discord now properly supports screensharing on linux1·8 months agoGoofcord gang rise up
“dough” and “mass” are the same word in Spanish
Fr if I turn on my laptop with a monitor connected, the taskbar will be on the monitor, regardless of the settings, every time. Also Bluetooth definitively died.
I’ve been thinking of switching distros for a while, maybe a fresh install helps?
That simply wouldn’t work in non-english machines lmao