Running 15.0 with KDE desktop. Recently been working on usb drive encryption and using Nitrokey App and Zulucrypt.
Have been successful with Nitrokey but not yet worked on Zulucrypt. My problem is that if I boot up I get both Nitrokey App, Zulucrypt and Zulumount starting even though I have not started any of these. Where is this autostart function coming from and how may I control this behaviour please?
Initially I’d take a look at:
System Settings -> Startup and Shutdown -> Autostart
Already done that. Not a hint of Nitrokey, Zulucrypt or Zulumount anywhere. Only two programs in Autostart and many in Background Services but none of these in the list. Thanks for the suggestion but I must look elsewhere.
OK… In this instance google may be your friend.
Couple of other suggestions, bearing in mind I’m not familiar with any of those applications:
Take a look below ~/.config for directories or files with related names, particularly any *.sh script files.
Or perhaps they run as a service?
YaST -> Services Manager
An afterthought… probable far less likely, but maybe worth a try.
Is your setup enabled to “Restore Previous Session”?
System Settings -> Startup and Shutdown -> Desktop Session -> On Login
For each of the packages you installed,
You can view the package contents with the following
rpm -ql *package_name*
Typically something in there will describe among other things how it starts… ie creating a systemd Unit file, writing a config file to your /home directory, etc.
If you have problems ferreting out the part that specifies how the app is starting, post your list… often an educated guess can be made based only on the file names…
TSU
Hi Tsu,
What a pain these titles are when they capitalise and include spaces when what I need is what was installed! Here is the result of your code:
alastair@linux-jqbk:~> rpm -ql nitrokey-app
/usr/bin/nitrokey-app
/usr/share/applications/nitrokey-app.desktop
/usr/share/bash-completion/completions/nitrokey-app
/usr/share/doc/packages/nitrokey-app
/usr/share/doc/packages/nitrokey-app/OTP_full_specification.txt
/usr/share/doc/packages/nitrokey-app/README.md
/usr/share/icons/hicolor/128x128/apps/nitrokey-app.png
/usr/share/icons/hicolor/16x16/apps/nitrokey-app.png
/usr/share/icons/hicolor/22x22/apps/nitrokey-app.png
/usr/share/icons/hicolor/24x24/apps/nitrokey-app.png
/usr/share/icons/hicolor/32x32/apps/nitrokey-app.png
/usr/share/icons/hicolor/48x48/apps/nitrokey-app.png
/usr/share/icons/hicolor/scalable/apps/nitrokey-app.svg
/usr/share/icons/ubuntu-mono-dark/apps/16/nitrokey-app.svg
/usr/share/icons/ubuntu-mono-dark/apps/22/nitrokey-app.svg
/usr/share/icons/ubuntu-mono-dark/apps/24/nitrokey-app.svg
/usr/share/icons/ubuntu-mono-dark/apps/48/nitrokey-app.svg
/usr/share/icons/ubuntu-mono-light/apps/16/nitrokey-app.svg
/usr/share/icons/ubuntu-mono-light/apps/22/nitrokey-app.svg
/usr/share/icons/ubuntu-mono-light/apps/24/nitrokey-app.svg
/usr/share/icons/ubuntu-mono-light/apps/48/nitrokey-app.svg
/usr/share/licenses/nitrokey-app
/usr/share/licenses/nitrokey-app/GPLv3
/usr/share/licenses/nitrokey-app/LGPLv3
/usr/share/licenses/nitrokey-app/MIT
/usr/share/metainfo/com.nitrokey.nitrokey-app.appdata.xml
/usr/share/pixmaps/nitrokey-app.png
alastair@linux-jqbk:~>
I hope you can explain what starts this. Further to this, when I insert the Nitrokey USB stick is there something running in the background which detects the usb stick and starts the PIN prompt or does this come from the stick itself?
Thanks for the reply.
Regards,
Binaries are running applications, so the following is the app that has to run
/usr/bin/nitrokey-app
Documentation for your nitrokey is installed in the usual location
/usr/share/doc/packages/
Everything else are images supporting the app or documentation, licenses, etc that are less important.
Typically,
When you plug in a USB dongle,
udev will detect, try to identify and based on what is found try to mount the key.
The nitrokey itself likely detects the attempt to mount (access) the file system which triggers the binary installed on your machine (see the first thing I mentioned)
Bottom line,
Although you could manually run the binary if it’s not automatically triggered, if you have a more basic mount problem, then simply running the nitrokey app may not work. But, it’s a try.
If you have problems with kodi, then I recommend you look at available guides on how nitrokey is set up on kodi.
TSU
Regarding the ‘autostart’ query, it may well be session-related, so read tannington’s advice in post #5.
HJi Paul and thanks for this. I had missed this earlier and think you have solved my problem.
Thanks again,
Budge
Great. I had missed this post earlier and think this was problem.
Thanks Deano.
Budge