qubes-issues icon indicating copy to clipboard operation
qubes-issues copied to clipboard

qvm-run qubes.StartApp+ not handling long names of .desktop files

Open Szewcson opened this issue 3 years ago • 1 comments

How to file a helpful issue

Qubes OS release

4.1

Brief summary

"Installed" Telegram AppImage that creates own .desktop shortcut. When I want to run it from qubes "start menu" nothing happens. After small investigation I found out that if I create .desktop file with long name it is visible in the menu but it not work (also from the CLI), but same file with short name works as normal. Original nameame of that Telegram app shortcut is appimagekit_e9d4f8123d28a5a3f93f92ec58a23421-Telegram_Desktop.desktop

Steps to reproduce

1.) Create .desktop file in ~/.local/share/applications with long name (use the one from Telegram app to be sure is long enough) 2.) Refresh Applications 3.) Try to run application from the menu, or using qvm-run with qubes.StartApp+

Expected behavior

Application should run as normal

Actual behavior

Nothing happens

Szewcson avatar Sep 13 '22 16:09 Szewcson

See #7766 (and its comments) for more on this bug.

andrewdavidwong avatar Sep 16 '22 12:09 andrewdavidwong

Same is true for Chrome/Chromium shortcuts for PWA. They are also have longer filename then qubes limit.

Szewcson avatar Oct 02 '22 09:10 Szewcson

Duplicate of https://github.com/QubesOS/qubes-issues/issues/7421

marmarek avatar Feb 25 '24 02:02 marmarek

This issue has been closed as a "duplicate." This means that another issue exists that is very similar to or subsumes this one. If any useful information on this issue is not already present on the other issue, please add it in a comment on the other issue. Here are some common cases of duplicate issues:

  • The other issue is closed. The other issue being closed does not prevent this issue from duplicating it. We will examine the closed issue and, if appropriate, reopen it.
  • The other issue is for a different Qubes release. We usually maintain only one issue for all affected Qubes releases.
  • The other issue is very old. The mere age of an issue is not, by itself, a relevant factor when determining duplicates.

By default, the newer issue will be closed in favor of the older issue. However, we make exceptions when we determine that it would be significantly more useful to keep the newer issue open instead of the older one.

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

If anyone reading this believes that this issue was closed in error or that the resolution of "duplicate" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.

github-actions[bot] avatar Feb 25 '24 02:02 github-actions[bot]