moolticute fails to correctly generate udev rule under opensuse 42.3

[sczep]

On startup moolticute generates an empty udev rule.

On start up it gives the following output: test@test:~/mooltipass> ./Moolticute-v0.12.11.glibc2.14-x86_64.AppImage zenity, kdialog, Xdialog missing. Skipping /tmp/.mount_Moolti8Q0BMD/usr/bin//moolticute.sh.wrapper. which: no kdesudo in (/tmp/.mount_Moolti8Q0BMD/usr/bin/:/tmp/.mount_Moolti8Q0BMD/usr/sbin/:/tmp/.mount_Moolti8Q0BMD/usr/games/:/tmp/.mount_Moolti8Q0BMD/bin/:/tmp/.mount_Moolti8Q0BMD/sbin/:/home/sczep/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games) which: no gksudo in (/tmp/.mount_Moolti8Q0BMD/usr/bin/:/tmp/.mount_Moolti8Q0BMD/usr/sbin/:/tmp/.mount_Moolti8Q0BMD/usr/games/:/tmp/.mount_Moolti8Q0BMD/bin/:/tmp/.mount_Moolti8Q0BMD/sbin/:/home/sczep/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games) Allow Mooltipass Udev rules to be applied in your system? sh: Zeile 11: $'change, GOTO=mooltipass_end\n\n# console user\\n\nKERNEL==hidraw*, SUBSYSTEM==hidraw, ATTRS{idVendor}==16d0, ATTRS{idProduct}==09a0, MODE=0660, SYMLINK+=mooltipass_keyboard, TAG+=uaccess\n# libusb\nSUBSYSTEM==usb, ATTRS{idVendor}==16d0, ATTRS{idProduct}==09a0, MODE=0660, SYMLINK+=mooltipass_device, TAG+=uaccess\n\nLABEL=mooltipass_end\n': Kommando nicht gefunden. static QPlatformTheme* QKdeTheme::createKdeTheme(): Unable to determine KDE dirs

if I insert the udev rule manually, moolticute works normally. (https://github.com/mooltipass/mooltipass-udev)

Regards Markus

[limpkin]

@raoulh will be able to provide a better answer than me... but isn't it due to the fact that the appimage isn't launched as sudo?

[raoulh]

Actually no, the sudo command for installing the udev rule is executed automatically using either kdesudo/gksudo/sudo. It seems the kdesudo/gksudo/zenity are not found on the system and thus it uses sudo. But an error occured

Allow Mooltipass Udev rules to be applied in your system? sh: Zeile 11:
[......]
Kommando nicht gefunden.

The startup script seems to contain some errors. I will look into it.

[raoulh]

@sczep What's your distro?

And your /bin/bash is a real bash or points to something else? Could you give me the output of bash --version please?

[sczep]

I did not use the sudo enviroment, but after starting the container i entered the root password

⁣Gesendet mit TypeApp ​

Am 1. Mai 2018, 22:15, um 22:15, Mathieu notifications@github.com schrieb:

@raoulh will be able to provide a better answer than me... but isn't it due to the fact that the appimage isn't launched as sudo?

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/mooltipass/moolticute/issues/271#issuecomment-385776866

[raoulh]

You don't have the sudo command installed at all?

The startup script for moolticute automatically tries to start to install the rules using sudo. You don't have to use sudo youself when running moolticute

[sczep]

I did start the container as a normal user, not with sudo. The startup script asked automatically for my sudo password. It created a udev rule file, but the file was empty and gave me the already posted output.

My distro is opensuse 42.3

bash --version>>>>

GNU bash, Version 4.3.42(1)-release (x86_64-suse-linux-gnu) Copyright (C) 2013 Free Software Foundation, Inc. Lizenz GPLv3+: GNU GPL Version 3 oder jünger http://gnu.org/licenses/gpl.html

Dies ist freie Software. Sie darf verändert und verteilt werden. Für den größtmöglichen gesetzlich zulässigen Umfang wird jede Haftung ausgeschlossen.

[suntorytimed]

Same thing happens on OpenSUSE Tumbleweed as well:

GNU bash, version 4.4.19(1)-release (x86_64-suse-linux-gnu)

zenity, kdialog, Xdialog missing. Skipping /tmp/.mount_Mooltif6aM3G/usr/bin//moolticute.sh.wrapper.
which: no kdesudo in (/tmp/.mount_Mooltif6aM3G/usr/bin/:/tmp/.mount_Mooltif6aM3G/usr/sbin/:/tmp/.mount_Mooltif6aM3G/usr/games/:/tmp/.mount_Mooltif6aM3G/bin/:/tmp/.mount_Mooltif6aM3G/sbin/:/home/suntorytimed/bin:/usr/local/bin:/usr/bin:/bin)
which: no gksudo in (/tmp/.mount_Mooltif6aM3G/usr/bin/:/tmp/.mount_Mooltif6aM3G/usr/sbin/:/tmp/.mount_Mooltif6aM3G/usr/games/:/tmp/.mount_Mooltif6aM3G/bin/:/tmp/.mount_Mooltif6aM3G/sbin/:/home/suntorytimed/bin:/usr/local/bin:/usr/bin:/bin)
Allow Mooltipass Udev rules to be applied in your system?
sh: line 11: $'change, GOTO=mooltipass_end\n\n# console user\\n\nKERNEL==hidraw*, SUBSYSTEM==hidraw, ATTRS{idVendor}==16d0, ATTRS{idProduct}==09a0, MODE=0660, SYMLINK+=mooltipass_keyboard, TAG+=uaccess\n# libusb\nSUBSYSTEM==usb, ATTRS{idVendor}==16d0, ATTRS{idProduct}==09a0, MODE=0660, SYMLINK+=mooltipass_device, TAG+=uaccess\n\nLABEL=mooltipass_end\n': command not found
static QPlatformTheme* QKdeTheme::createKdeTheme(): Unable to determine KDE dirs
DEBUG: :0 - System locale:  QLocale(English, Latin, UnitedStates)
INFO: :0 - Trying to set language:  ":/lang/mc_en.qm"
WARNING: :0 - QSslSocket: cannot resolve CRYPTO_num_locks
WARNING: :0 - QSslSocket: cannot resolve CRYPTO_set_id_callback
WARNING: :0 - QSslSocket: cannot resolve CRYPTO_set_locking_callback
WARNING: :0 - QSslSocket: cannot resolve ERR_free_strings
WARNING: :0 - QSslSocket: cannot resolve sk_new_null
WARNING: :0 - QSslSocket: cannot resolve sk_push
WARNING: :0 - QSslSocket: cannot resolve sk_free
WARNING: :0 - QSslSocket: cannot resolve sk_num
WARNING: :0 - QSslSocket: cannot resolve sk_pop_free
WARNING: :0 - QSslSocket: cannot resolve sk_value
WARNING: :0 - QSslSocket: cannot resolve SSL_library_init
WARNING: :0 - QSslSocket: cannot resolve SSL_load_error_strings
WARNING: :0 - QSslSocket: cannot resolve SSL_get_ex_new_index
WARNING: :0 - QSslSocket: cannot resolve SSLv3_client_method
WARNING: :0 - QSslSocket: cannot resolve SSLv23_client_method
WARNING: :0 - QSslSocket: cannot resolve SSLv3_server_method
WARNING: :0 - QSslSocket: cannot resolve SSLv23_server_method
WARNING: :0 - QSslSocket: cannot resolve X509_STORE_CTX_get_chain
WARNING: :0 - QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
WARNING: :0 - QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
WARNING: :0 - QSslSocket: cannot resolve SSLeay
WARNING: :0 - QSslSocket: cannot resolve SSLeay_version
WARNING: :0 - QSslSocket: cannot call unresolved function SSLeay
WARNING: :0 - QSslSocket: cannot call unresolved function CRYPTO_num_locks
WARNING: :0 - QSslSocket: cannot call unresolved function CRYPTO_set_id_callback
WARNING: :0 - QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback
WARNING: :0 - QSslSocket: cannot call unresolved function SSL_library_init
WARNING: :0 - QSslSocket: cannot call unresolved function SSLv23_client_method
WARNING: :0 - QSslSocket: cannot call unresolved function sk_num

[limpkin]

@raoulh did you fix that one with your latest commits?

[raoulh]

I think so, it needs to be tested now

[suntorytimed]

If you can provide me with an updated AppImage I can test it for you.

On 06/11/2018 08:46 AM, raoulh wrote:

I think so, it needs to be tested now

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mooltipass/moolticute/issues/271#issuecomment-396138860, or mute the thread https://github.com/notifications/unsubscribe-auth/ACngOcwsY4RlD3NZiXAc-HZtee0IXXpgks5t7hI0gaJpZM4Tuar9.

-- Stefan Weiberg sweiberg@suse.com Release- and Project Manager SLES for SAP Applications SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

[limpkin]

https://mooltipass-tests.com/mc_betas/v0.17.6-testing/

On Mon, Jun 11, 2018, 08:59 Stefan Weiberg notifications@github.com wrote:

If you can provide me with an updated AppImage I can test it for you.

On 06/11/2018 08:46 AM, raoulh wrote:

I think so, it needs to be tested now

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/mooltipass/moolticute/issues/271#issuecomment-396138860 , or mute the thread < https://github.com/notifications/unsubscribe-auth/ACngOcwsY4RlD3NZiXAc-HZtee0IXXpgks5t7hI0gaJpZM4Tuar9 .

-- Stefan Weiberg sweiberg@suse.com Release- and Project Manager SLES for SAP Applications SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mooltipass/moolticute/issues/271#issuecomment-396141547, or mute the thread https://github.com/notifications/unsubscribe-auth/AF4ms7HY2vQlSf6LEfQvCtt98NAfYZdkks5t7hVMgaJpZM4Tuar9 .

[raoulh]

This one please: https://mooltipass-tests.com/mc_betas/v0.17.6-testing/

[suntorytimed]

AppImage can now create the udev rule. Unfortunately my USB cable doesn't provide a data lane. I will have to test it again in the evening as soon as I arrive at home.

One new bug appeared with AppImage not able to create the .desktop file for system integration.

Error on file "/tmp/.mount_MooltisOVN3S/moolticute.desktop": Failed to create file “/home/suntorytimed/.local/share/applications/appimagekit-moolticute.desktop.54XEKZ”: Not a directory
static QPlatformTheme* QKdeTheme::createKdeTheme(): Unable to determine KDE dirs
DEBUG: :0 - System locale:  QLocale(English, Latin, UnitedStates)
INFO: :0 - Trying to set language:  ":/lang/mc_en.qm"
WARNING: :0 - QSslSocket: cannot resolve CRYPTO_num_locks
WARNING: :0 - QSslSocket: cannot resolve CRYPTO_set_id_callback
WARNING: :0 - QSslSocket: cannot resolve CRYPTO_set_locking_callback
WARNING: :0 - QSslSocket: cannot resolve ERR_free_strings
WARNING: :0 - QSslSocket: cannot resolve sk_new_null
WARNING: :0 - QSslSocket: cannot resolve sk_push
WARNING: :0 - QSslSocket: cannot resolve sk_free
WARNING: :0 - QSslSocket: cannot resolve sk_num
WARNING: :0 - QSslSocket: cannot resolve sk_pop_free
WARNING: :0 - QSslSocket: cannot resolve sk_value
WARNING: :0 - QSslSocket: cannot resolve SSL_library_init
WARNING: :0 - QSslSocket: cannot resolve SSL_load_error_strings
WARNING: :0 - QSslSocket: cannot resolve SSL_get_ex_new_index
WARNING: :0 - QSslSocket: cannot resolve SSLv3_client_method
WARNING: :0 - QSslSocket: cannot resolve SSLv23_client_method
WARNING: :0 - QSslSocket: cannot resolve SSLv3_server_method
WARNING: :0 - QSslSocket: cannot resolve SSLv23_server_method
WARNING: :0 - QSslSocket: cannot resolve X509_STORE_CTX_get_chain
WARNING: :0 - QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
WARNING: :0 - QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
WARNING: :0 - QSslSocket: cannot resolve SSLeay
WARNING: :0 - QSslSocket: cannot resolve SSLeay_version
WARNING: :0 - QSslSocket: cannot call unresolved function SSLeay
WARNING: :0 - QSslSocket: cannot call unresolved function CRYPTO_num_locks
WARNING: :0 - QSslSocket: cannot call unresolved function CRYPTO_set_id_callback
WARNING: :0 - QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback
WARNING: :0 - QSslSocket: cannot call unresolved function SSL_library_init
WARNING: :0 - QSslSocket: cannot call unresolved function SSLv23_client_method
WARNING: :0 - QSslSocket: cannot call unresolved function sk_num

[limpkin]

closing this issue as the remaining problem is captured in #291

[suntorytimed]

Sorry, I forgot to reply that the test worked fine with a different cable.