Hi. I recently published my app on Flathub and have been steadily updating it to make it better.
With it you can download Music from Youtube and tag it to create a beautiful collection of local Music. Check it out: https://flathub.org/apps/net.fhannenheim.musicfetch
I had similar problems where the logs say it moved the file to my Music directory, but the directory was empty. I made multiple attempts using different directories and making sure the app has permissions with flatseal, but no luck.
It seems like a nice app though, I’m gonna keep an eye on it!
On the download done page there is a button on top with a directory icon, which opens the files in a file manager. Can you please try again and click it and tell me where the files have been downloaded to? That may be a mistake on my part
Hey, thanks for the response! I tried again with the recent update (
--versionsays 1.2.1) and still having the problem. The button you refer to opens my file manager in the system root directory, instead of the download directory shown in settings which is now by default set to my home folder instead of~/Musiclike in the prior version.To recreate, I ran the app from the CLI and searched the videos tab for “flowers”, then clicked download on the top result. The metadata pages had blank values (are they supposed to populate automatically somehow?), and I clicked through until I got to the final page below.
flowers
~$ flatpak run net.fhannenheim.musicfetch --version musicfetch_gui 1.2.1 ~$ flatpak run net.fhannenheim.musicfetch libEGL warning: failed to get driver name for fd -1 libEGL warning: MESA-LOADER: failed to retrieve device information libEGL warning: failed to get driver name for fd -1 MESA: error: ZINK: failed to choose pdev libEGL warning: egl: failed to create dri2 screen libEGL warning: failed to get driver name for fd -1 libEGL warning: MESA-LOADER: failed to retrieve device information libEGL warning: failed to get driver name for fd -1 MESA: error: ZINK: failed to choose pdev libEGL warning: egl: failed to create dri2 screen [2026-01-28T19:22:43Z INFO musicfetch_gui::app] Starting download of 1 songs [2026-01-28T19:22:43Z INFO musicfetch_gui::modules::download] running yt-dlp with args ["--ignore-config", "-x", "-f", "ba", "-o", "/tmp/musicfetch/%(id)s.%(ext)s", "--load-info-json", "-", "-O", "after_move:filepath", "--progress-template", "download:%(progress.downloaded_bytes)s-%(progress.total_bytes)s-%(progress.downloaded_bytes_estimate)s", "--newline", "--progress"] [2026-01-28T19:22:44Z INFO musicfetch_gui::modules::download] All songs downloaded [2026-01-28T19:22:52Z INFO musicfetch_gui::modules::tagwriter] reading filetype from path /tmp/musicfetch/G7KNmW9a75Y.opus [2026-01-28T19:22:52Z INFO musicfetch_gui::modules::tagwriter] filepath extension: Some("opus") [2026-01-28T19:22:52Z INFO musicfetch_gui::modules::rename] moving song to: //1 - .opus [2026-01-28T19:22:52Z INFO musicfetch_gui::modules::rename] creating parent dir: /PS: I tried again with another song (Big Boogie - Shut Up) that seems to have metadata available from however MusicFetch is finding metadata. The logs are slightly different in that it seems to attempt to save the file where it is configured to do so (the home folder), but there’s still not actually a file saved in that location when I click to open in my file manager:
big boogie
$ flatpak run net.fhannenheim.musicfetch libEGL warning: failed to get driver name for fd -1 libEGL warning: MESA-LOADER: failed to retrieve device information libEGL warning: failed to get driver name for fd -1 MESA: error: ZINK: failed to choose pdev libEGL warning: egl: failed to create dri2 screen libEGL warning: failed to get driver name for fd -1 libEGL warning: MESA-LOADER: failed to retrieve device information libEGL warning: failed to get driver name for fd -1 MESA: error: ZINK: failed to choose pdev libEGL warning: egl: failed to create dri2 screen [2026-01-28T19:31:10Z INFO musicfetch_gui::app] Starting download of 1 songs [2026-01-28T19:31:10Z INFO musicfetch_gui::modules::download] running yt-dlp with args ["--ignore-config", "-x", "-f", "ba", "-o", "/tmp/musicfetch/%(id)s.%(ext)s", "--load-info-json", "-", "-O", "after_move:filepath", "--progress-template", "download:%(progress.downloaded_bytes)s-%(progress.total_bytes)s-%(progress.downloaded_bytes_estimate)s", "--newline", "--progress"] [2026-01-28T19:31:11Z INFO musicfetch_gui::modules::download] All songs downloaded [2026-01-28T19:31:17Z INFO musicfetch_gui::modules::tagwriter] reading filetype from path /tmp/musicfetch/B9RNRhoUr6E.opus [2026-01-28T19:31:17Z INFO musicfetch_gui::modules::tagwriter] filepath extension: Some("opus") [2026-01-28T19:31:17Z INFO musicfetch_gui::modules::rename] moving song to: /home/luke /Big Boogie/Shut Up/1 - Shut Up.opus [2026-01-28T19:31:17Z INFO musicfetch_gui::modules::rename] creating parent dir: /home/luke /Big Boogie/Shut Up [2026-01-28T19:31:23Z INFO musicfetch_gui::app::update] Opening directory at /home/luke /Big Boogie/Shut UpEdit: forgot to mention, I’m using Fedora Workstation 43, in case that’s relevant for you.
Good luck with the app, it’s a really good idea!
Well. I don’t know why I didn’t catch this earlier but I’ve found the bug now. I had a trailing newline in the download path. This sucks.
It’s fixed now and should be released in 1-2 hours on flathub
I tried the new version of the app (
1.3.1) and it works a little better. As mentioned in my other comment, the app tries by default to write to my home directory, which fails. However, if I manually tell the app to use ~/Downloads instead, then it works!On the other hand, closing and relaunching the app again clears out what I’ve manually configured and it tries to write to my home directory again until I change it every time.
(Also, apologies, I should be reporting to your issue tracker instead.)
I’ve now tried a fresh install in a Fedora Workstation 43 VM with the language set to German and it worked.
You could try
rm .config/cosmic/net.fhannenheim.musicfetch -rfto reset the app and try again.Okay interesting. Are you using the Flatpak? If so, can you try running
flatpak run --command=bash net.fhannenheim.musicfetchand runningxdg-user-dir MUSICin the bash shell?Hey, sure no problem. I don’t actually have a Music folder ordinarily since I keep my music in a network location instead.
$ flatpak run --command=bash net.fhannenheim.musicfetch [📦 net.fhannenheim.musicfetch ~]$ xdg-user-dir MUSIC /home/lukeFlatseal shows that the app has requested permission to access xdg-music, which in my case is my home directory. I would assume that means it should be able to write there, but maybe the “All user files” toggle being off supercedes that? I’m not sure how flatpak permissions work, exactly.