[GH-ISSUE #185] [BUG] Error 24 on Nobara Linux Despite System Settings #101

Open
opened 2026-02-17 17:12:05 -05:00 by yindo · 2 comments
Owner

Originally created by @Elite-Alien on GitHub (Feb 16, 2026).
Original GitHub issue: https://github.com/Drop-OSS/drop-app/issues/185

Originally assigned to: @DecDuck on GitHub.

Some random games when trying to download them will prompt a IO Error to many open files, error. Not all games do this, but some will and some will not. It's random, but it does seem to happen more on longer titled names more often.
https://snipboard.io/MkJutS.jpg

My latest offender is "Supreme Ruler 1936". Which is a DRM-Free other than a CDKey. I bought this game digitally and the files are all portable. This is a bit of an older title so it's not very large in size or has very many files compared to modern games. As I have portable games that are much larger in terms of files and size than this game I purchased and they download fine on this machine.

I have set the limit both system wide, made a systemd configuration, and have done manual session based temporary "ulimit -Sn, ulimit -Hn, ulimit -n" commands and Drop still will have the OS Error 24. Drop-app seems to be ignoring the systems settings and is the only application suffering from this issue.

Drop-App was obtained through a RPM since Nobara is a Fedora based distro. Which is "Drop.Desktop.Client.0.3.4-1.x86_64.rpm".

System Information

  • Nobara Linux 43
  • KDE Plasma
  • AMD Rayzen 3 2200G
  • 16GB RAM
  • Intel Arc A770 GPU

I've yet to recreate this on my main rig which is not Fedora based. This only seems to be happening with Drop and on Nobara Linux.

I have tried the appimage though it seems to be built for a different system in mind as it will not accept any of the "ayantana-appindicator" or "appindicator" packages in the Nobara Linux package manager. As it looks for ones ending with "3".

Originally created by @Elite-Alien on GitHub (Feb 16, 2026). Original GitHub issue: https://github.com/Drop-OSS/drop-app/issues/185 Originally assigned to: @DecDuck on GitHub. Some random games when trying to download them will prompt a IO Error to many open files, error. Not all games do this, but some will and some will not. It's random, but it does seem to happen more on longer titled names more often. https://snipboard.io/MkJutS.jpg My latest offender is "Supreme Ruler 1936". Which is a DRM-Free other than a CDKey. I bought this game digitally and the files are all portable. This is a bit of an older title so it's not very large in size or has very many files compared to modern games. As I have portable games that are much larger in terms of files and size than this game I purchased and they download fine on this machine. I have set the limit both system wide, made a systemd configuration, and have done manual session based temporary "ulimit -Sn, ulimit -Hn, ulimit -n" commands and Drop still will have the OS Error 24. Drop-app seems to be ignoring the systems settings and is the only application suffering from this issue. Drop-App was obtained through a RPM since Nobara is a Fedora based distro. Which is "Drop.Desktop.Client.0.3.4-1.x86_64.rpm". #### System Information - Nobara Linux 43 - KDE Plasma - AMD Rayzen 3 2200G - 16GB RAM - Intel Arc A770 GPU I've yet to recreate this on my main rig which is not Fedora based. This only seems to be happening with Drop and on Nobara Linux. I have tried the appimage though it seems to be built for a different system in mind as it will not accept any of the "ayantana-appindicator" or "appindicator" packages in the Nobara Linux package manager. As it looks for ones ending with "3".
yindo changed title from [BUG] Error 24 on Nobara Linux Despite System Settings to [GH-ISSUE #185] [BUG] Error 24 on Nobara Linux Despite System Settings 2026-06-05 14:24:47 -04:00
Author
Owner

@DecDuck commented on GitHub (Mar 4, 2026):

Sorry for the delay.

I remember implementing a fix for this, but I'm not sure if it was confirmed as working. Will need to investigate.

<!-- gh-comment-id:3997216159 --> @DecDuck commented on GitHub (Mar 4, 2026): Sorry for the delay. I remember implementing a fix for this, but I'm not sure if it was confirmed as working. Will need to investigate.
Author
Owner

@Elite-Alien commented on GitHub (Mar 5, 2026):

Sorry for the delay.

I remember implementing a fix for this, but I'm not sure if it was confirmed as working. Will need to investigate.

All good.

I wish I had more to go on and logs, but nothing super helpful to go off of. However, I do have a large library on the system. At least 40+ games as of now. I've also noticed it sometimes happens on games if multiple are downloading in the queue. Though sometimes putting them back in the queue while another is also in the queue makes it actually finish downloading. It's a strange bug and willing to try and test a few things.

While I still have this PC. This PC is actually a computer I put together for a family member so I just loaded it up with a distro I thought would be easier and easier to update Drop thanks to the whole RPM's. So I will have it for a little while before handing it off to them. I have some old parts that I could try and put Nobara onto another machine too and test, when I get a chance to do that. So, let me know if there is anything I can test or do to help maybe pin-point the problem.

<!-- gh-comment-id:4009294088 --> @Elite-Alien commented on GitHub (Mar 5, 2026): > Sorry for the delay. > > I remember implementing a fix for this, but I'm not sure if it was confirmed as working. Will need to investigate. All good. I wish I had more to go on and logs, but nothing super helpful to go off of. However, I do have a large library on the system. At least 40+ games as of now. I've also noticed it sometimes happens on games if multiple are downloading in the queue. Though sometimes putting them back in the queue while another is also in the queue makes it actually finish downloading. It's a strange bug and willing to try and test a few things. While I still have this PC. This PC is actually a computer I put together for a family member so I just loaded it up with a distro I thought would be easier and easier to update Drop thanks to the whole RPM's. So I will have it for a little while before handing it off to them. I have some old parts that I could try and put Nobara onto another machine too and test, when I get a chance to do that. So, let me know if there is anything I can test or do to help maybe pin-point the problem.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drop-OSS/drop-app#101