that_leaflet

joined 2 years ago
MODERATOR OF
[–] that_leaflet@lemmy.world 33 points 4 days ago (7 children)

Heroic is really nice and what I recommend, but the UI is a bit clunky and spread out.

[–] that_leaflet@lemmy.world 1 points 5 days ago

Strange. Discord, ProtonMail, ProtonUp-Qt, and Spotify should all work perfectly. Except maybe some drag and drop issues for Discord and ProtonMail? And Discord's activity status is blocked from tracking you. What issues did you have specifically?

I can see OpenRGB having issues given that tries to talk to the hardware itself, did you install the udev rules?

Handbrake has access to all your files by default so that shouldn't be an issue.

[–] that_leaflet@lemmy.world 2 points 5 days ago (2 children)

What Flatpaks did you have issues with?

[–] that_leaflet@lemmy.world 17 points 1 week ago (3 children)

I’ve had no issues with the ProtonVPN flatpak on Fedora Silverblue.

[–] that_leaflet@lemmy.world 7 points 1 week ago (5 children)

Firefox is taking that icon from your GTK theme. And that’s the maximize button in the Papirus theme. So this is intended behavior.

You’d have to modify the theme or tell Firefox to use a title bar to fix it.

[–] that_leaflet@lemmy.world 3 points 1 week ago (7 children)

Are you using an icon theme? Papirus?

[–] that_leaflet@lemmy.world 6 points 1 week ago (2 children)

Probably the biggest one is the next piece of the Wayland session restore puzzle clicking into place: David Edmundson has implemented support for the xx-session-management-v1 Wayland session restore protocol in Qt 6.10! This means that software built on top of Qt 6.10 (for example, Plasma and KDE apps) will be able to start implementing the protocol themselves. Once they do, then finally real session restore will work on Wayland

I hope we’re able to opt out of apps positioning their own Windows. My favorite thing about Wayland is that apps can’t control where their windows open, so they always open in a consistent location chosen by the compositor.

Annoys me whenever I use Windows, MacOS, or Xwayland apps that open up in seemingly random locations.

[–] that_leaflet@lemmy.world 6 points 1 week ago

You probably ran an update before this and updated the screen locker. Then the OS was in a mismatched that caused the screen locker to break.

[–] that_leaflet@lemmy.world 3 points 1 week ago

Throughout the entire thread.

Here's the suggestions I remember

  • Recommend the Steam flatpak (cons: VR requires more tinkering to get working, flatpak version of gamescope apparently has limitations for dedicated Big Screen mode)
  • Ship Steam in a container (cons: breaks gaming on Asahi Linux, relies on third parties)
  • Ship a curated list of 32 bit software (cons: even if there's just one 32 bit package, it's still a lot of work and infrastructure, current infrastructure work need to be reworked)
  • Use ELN for building 32 bit packages (avoids the above mentioned infrastucture rework)
  • Stop shipping 32 bit stuff and rely on third party repos for it (cons: rpmfusion can't afford to do this)
  • Create a SIG to represent 32 bit software or repurpose the Gaming SIG
[–] that_leaflet@lemmy.world 5 points 1 week ago* (last edited 1 week ago) (1 children)

They’re joking, the comment the link is to writes about this same behavior.

[–] that_leaflet@lemmy.world 10 points 1 week ago (2 children)

Thankfully this isn’t actually being dropped. A more concrete plan of how to drop 32 bit but keep Steam and older games working is underway.

 

I am disappointed in some of the reactions this !! proposal !! has received, with some people apparently reading it in the most uncharitable way. It was a proposal that tried to address technical problems package maintainers and release engineering is facing, not some conspiracy to break the “gaming use case”.

[–] that_leaflet@lemmy.world 1 points 1 week ago

That's what I thought at first, but I changed it after searching it up.

But I just realized that when I was checking "widthdrawled", DuckDuckGo was actually showing me the definition for "withdraw".

view more: next ›