-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
what(): Malformed file (Koofr) #176
Comments
Can you please post debug output (using the |
I had the same issue. When I used @meator 's suggestion, I could easily find the problematic desktop file. It belonged to a cloud service which I had recently uninstalled. But the desktop file was still around since it didn't have a proper uninstaller. Removing the file solved my problem. |
On a different machine where I had the application still installed, I get the same error. Renaming this desktop file solves the issue. But then I won't be able to use the desktop launcher.
Content of the desktop file in question
|
Exceptions should be more informative now. Invalid desktop files now fall under invalid_error and are handled gracefully instead of aborting j4-dmenu-desktop. related to #176
Desktop files may not contain spaces before the key. I believe this is against the Desktop entry specification. Please ask Koofr to fix their desktop file. You can remove the whitespace before all keys to fix it: [Desktop Entry]
Name=Koofr
GenericName=Hybrid storage cloud
Exec=/home/linn/.koofr-dist/storagegui
Terminal=false
Type=Application
Icon=/home/linn/.koofr-dist/icon.png
Categories=Network;FileTransfer;Internet; Desktop files with invalid |
Thanks! That helped identify the issue. One of the desktop files were indeed causing errors, but for me not by Koofr. |
@Swexti Would you mind posting the faulty desktop file here? |
Sorry, I removed the desktop file. I can't remember what it was. |
Searched through the issues and couldn't find this anywhere.
Recently ran
pacman -Syu
to update packages, and then j4-dmenu-desktop stopped working. I believe j4dd was updated with the rest of the packages.The j4dd menu appears as normal, but nothing is listed. I can include binaries the same way as listed in the README, but trying to run them does nothing.
Things I've tried:
EndeavourOS
6.10.2-arch1-2
I'm assuming the problem lies somewhere in my packages or my system configurations, and not in j4dd. I don't sync nearly often enough as I should. Not sure what to do about it though, nothing else has been affected by the update as far as I've noticed.
The text was updated successfully, but these errors were encountered: