After downloading the .deb package I couldnāt launch the app. I then followed the steps in Ubuntu 18.04 (stopped current inkdrop process, installed missing deps) and launched inkdrop again. This it launched but logging in throws the following error:
Error message:
Failed to store user ID to Keychain. This is usually a permission issue and you may need to restart your computer.
Status code:
Restarting the system and trying again seems to make no difference.
Thank you for reporting.
I guess this is a gnome-keyring problem.
Could you run the app from terminal and check error messages?
If thereās an additional information, please search the web with it.
$ inkdrop
Gkr-Message: 13:46:50.293: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
Gkr-Message: 13:46:50.516: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
Gkr-Message: 13:46:50.520: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
Gkr-Message: 13:46:50.529: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
Gkr-Message: 13:46:51.825: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
(inkdrop:12242): LIBDBUSMENU-GLIB-WARNING **: 13:46:52.104: About to Show called on an item wihtout submenus. We're ignoring it.
(inkdrop:12242): LIBDBUSMENU-GLIB-WARNING **: 13:46:52.146: About to Show called on an item wihtout submenus. We're ignoring it.
(inkdrop:12242): LIBDBUSMENU-GLIB-WARNING **: 13:46:52.148: About to Show called on an item wihtout submenus. We're ignoring it.
Still looking into missing packages, the diff between your systemās output and mine is quite complex. In the meantime, here are a couple screenshots of what I see when trying to loginā¦
Do you have libsecret-1-0 installed?
Inkdrop uses keytar to store credentials and I found that the app uses kind of old version now.
Iāll update it in the next release.
Thatās weird. It runs fine on my Ubuntu 18.04.
Please run it from terminal and check if thereās an error.
If not, Iām afraid that I canāt solve the problem.
Running from the commandline reveals the following error:
$ inkdrop
app:info Quit because of duplicated instance +0ms
Iāve tried a couple different ways to uninstall the previous version, all seemed successful yet when I install this new .deb file I get the same error when trying to launch inkdrop from the commandline.
I did notice 2 different version numbers in the output when installing the .deb package:
Selecting previously unselected package inkdrop.
(Reading database ... 260905 files and directories currently installed.)
Preparing to unpack .../inkdrop_3.20.2_amd64.deb ...
Unpacking inkdrop (3.20.2-1) ...
Setting up inkdrop (3.20.2-1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Done
This may be a red herring but I thought it worth sharing in case it meant more to you.
Iām currently trying to switch to Linux from macOS so Iām afraid Iām not overly familiar with duplicate instances etc. Sorry if Iāve missed something basic here!
First you have to kill existing Inkdrop process which didnāt quit successfully for some reason. You can find existing process with following command:
ps aux | grep inkdrop
and run kill <pid>.
And then please launch the app again.
ps aux | grep inkdrop returns a process with a different ID each time. When I go to kill that process, the PID has already changed and Iām just told bash: kill: (<pid>) - No such process. E.g:
dan@dan-desktop:~$ ps aux | grep inkdrop
dan 3185 0.0 0.0 14428 988 pts/0 S+ 19:05 0:00 grep --color=auto inkdrop
dan@dan-desktop:~$ kill 3185
bash: kill: (3185) - No such process
dan@dan-desktop:~$ ps aux | grep inkdrop
dan 3190 0.0 0.0 14428 1096 pts/0 S+ 19:06 0:00 grep --color=auto inkdrop
Thatās because, as you can see, the process you tried to kill is grep itself.
It seems that the inkdrop process doesnāt exist anymore. I guess you rebooted your computer?
You should be able to run the app again.
Iām afraid that I canāt reproduce that problem.
I also tried to run it on Kubuntu 18.04 which is the same setup as you and the app successfully launched.
What I did is just as follows: