From: ar-jan <ar-jan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dbeaver no desktop entry KDE Plasma
Date: Sun, 12 Jun 2022 12:40:04 +0200 [thread overview]
Message-ID: <20220612104004.v6KMW1YeOBlj74Rjtq83_MYbbJzRO6ZEMUCJZNFm3WY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34040@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
New comment by ar-jan on void-packages repository
https://github.com/void-linux/void-packages/issues/34040#issuecomment-1153125549
Comment:
It looks like the desktop entry should be generated by Maven. I'm not familiar with how this works, but it looks like the configuration comes from [here](https://github.com/dbeaver/dbeaver/blob/devel/product/community/DBeaver.product).
On my system I found an entry `~/.local/share/applications/_usr_lib_dbeaver_.desktop` containing:
```
[Desktop Entry]
Name=DBeaver
Exec=/usr/lib/dbeaver/dbeaver %u
NoDisplay=true
Type=Application
MimeType=x-scheme-handler/eclipse+command;
```
I don't know where the `NoDisplay=true` comes from.
Any suggestions how to handle this? I also see in DBeaver's issue queue they've had problems with packaging the desktop entry multiple times.
To patch this in the meantime, make the entry look like:
```
[Desktop Entry]
Name=DBeaver
Exec=/usr/lib/dbeaver/dbeaver %u
Icon=/usr/lib/dbeaver/icon.xpm
Type=Application
MimeType=x-scheme-handler/eclipse+command;
```
and run `sudo update-desktop-database ~/.local/share/applications/`.
next prev parent reply other threads:[~2022-06-12 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 9:07 [ISSUE] " russnes
2021-11-15 15:15 ` splpaul
2021-11-15 16:16 ` Johnnynator
2022-06-12 2:16 ` github-actions
2022-06-12 9:32 ` paper42
2022-06-12 10:40 ` ar-jan [this message]
2023-06-16 19:12 ` ar-jan
2023-06-16 19:54 ` [ISSUE] [CLOSED] " classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220612104004.v6KMW1YeOBlj74Rjtq83_MYbbJzRO6ZEMUCJZNFm3WY@z \
--to=ar-jan@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).