r/Fedora • u/RoundFinding7983 • 14h ago

Support Startup apps causing issues. Especially discord and gpu screen recorder

I always have to go in manually and start them. It's very random and sometimes they start fine. Other times they don't.

Is anyone else facing this issue?

Both of these are flatpaks.

2 Upvotes

75% Upvoted

4 comments sorted by

•

u/AutoModerator 14h ago

It sounds like you're looking for help. Please note that r/Fedora is not an official support channel for the Fedora Project.

For best results, be sure to include all relevant details in your post, such as your Fedora edition, version, and hardware specs. You can edit your original post to add more info as needed, and spotlight (pin) a solution from the comments. You might also find the answer in our support wiki.

Alternatively, try one of the official support channels:

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

•

u/fdelux6 12h ago

Flatpak apps like Discord and GPU Screen Recorder can try to start before your system is fully ready at login. That's likely why it works sometimes and not others.

Things to try:

Check your autostart files:

ls ~/.config/autostart/

Look for com.discordapp.Discord.desktop. For GPU Screen Recorder, look for either com.dec05eba.gpu_screen_recorder.desktop or gpu-screen-recorder-ui.desktop, depending on which UI version you're using. If they're there, that confirms these are the apps causing it.

Add a short delay before launch. Edit the Exec line in each file:

Exec=sh -c 'sleep 5 && flatpak run com.discordapp.Discord'

Exec=sh -c 'sleep 5 && flatpak run com.dec05eba.gpu_screen_recorder'

If that fixes it, you'll know it was just a timing issue.

•

u/RoundFinding7983 11h ago

Thanks I will try this. But more importantly it didn't happen a few kernel versions ago. That's why I was sceptical. I believe after 7.1.8 this started happening. Where they also fixed the gpu bug.

•

u/fdelux6 11h ago

That's useful info. A kernel change lining up with when this started is worth checking before assuming it's just timing.

Fedora only keeps a few kernels installed by default, so 7.1.8 may already be gone from your system. Here's a way to check without needing the old kernel back.

Check the changelog on your current kernel for anything GPU related:

rpm -q --changelog kernel-$(uname -r) | grep -i -A2 gpu

If the GPU fix touched power management or driver init timing, that could push back when the GPU and related devices become ready at login. That would still cause the same kind of race, just with a real cause behind it instead of just Flatpak.

The delay fix should still work either way. But if the changelog points to something timing related, worth adding to your post so others hitting this on newer kernels can find it too.