Menu

#1548 "File or path not found" when pressing Yubikey button.

Next release
closed
linux (6)
Medium
2022-06-02
2021-10-06
seth
No

"File or path not found" when pressing Yubikey button.
passwordsafe 1.13.0-1

OS: Garuda Linux
Kernel: 5.14.9-zen2-1-zen
Shell: bash
DE: Plasma 5.22.5
WM: KWin

Yubikey dependencies installed:
yubico-c 1.13-6
yubico-c-client 2.15-5
yubikey-personalization 1.20.0-3

Related

Bugs: #1548

Discussion

  • seth

    seth - 2021-10-06

    The yubikey is recognized and working. If I open a text editor and touch the yubikey button the expected string of characters is output.

     
  • Rony Shapiro

    Rony Shapiro - 2021-10-06
    • labels: --> linux
    • status: open --> accepted
    • assigned_to: Rony Shapiro
     
  • Rony Shapiro

    Rony Shapiro - 2021-10-06

    Hm. I haven't encountered this error with Yubikey before. I also don't have a Garuda Linux VM handy for testing.
    Can you run pwsafe under strace, reproduce the problem and attach the output to this ticket? E.g.,

    $ strace -o pwsafe.strace pwsafe
    
     
  • seth

    seth - 2021-10-07

    This is all that showed. These lines were all generated prior to the error taking place and no new lines showed when I reproduced the error:

    06:01:29 PM: Warning: Mismatch between the program and library build versions detected.
    The library used 3.0 (wchar_t,compiler with C++ ABI 1014,wx containers,compatible with 2.8),
    and your program used 3.0 (wchar_t,compiler with C++ ABI 1016,wx containers,compatible with 2.8).

    (pwsafe:9728): Gtk-WARNING **: 18:01:29.447: Unable to locate theme engine in module_path: "adwaita",

    (pwsafe:9728): Gtk-WARNING **: 18:01:29.469: Unable to locate theme engine in module_path: "murrine",

    (pwsafe:9728): Gtk-WARNING **: 18:01:29.470: Unable to locate theme engine in module_path: "murrine",

    (pwsafe:9728): Gtk-WARNING **: 18:01:29.473: Unable to locate theme engine in module_path: "murrine",

    (pwsafe:9728): Gtk-WARNING **: 18:01:29.474: Unable to locate theme engine in module_path: "murrine",

    (pwsafe:9728): Gtk-WARNING **: 18:01:29.475: Unable to locate theme engine in module_path: "murrine",

     
  • Rony Shapiro

    Rony Shapiro - 2021-10-07

    These lines are unrelated to the error.

    Without the strace file there's not much I can do.

     
  • seth

    seth - 2021-10-07

    Apologies I've never used strace before I will take another stab at it and try to get the file you mention. i thought the output would just be in the terminal window itself.

     

    Last edit: seth 2021-10-07
  • seth

    seth - 2021-10-08

    Here you go; sorry about that. Thanks for your help.

     
  • Rony Shapiro

    Rony Shapiro - 2021-10-12
     
  • Rony Shapiro

    Rony Shapiro - 2021-10-12

    The trace doesn't indicate anything special.
    The "mismatch" warning might indicate the problem: Perhaps the package needs to be rebuilt on Garuda Linux or the specific Arch version from which it's derived?

     
  • seth

    seth - 2021-10-13

    Assuming that compiling from source in Octopi behaves as one would hope; I've rebuilt it from source and am still getting the error. (It scrolled through downloading and building from source in the terminal window built into octopi)

    When the yubikey button on the initial login is pressed; what is the program doing?
    The yubikey is detected because the button is coming up; but maybe its not able to find it or the yubikey libraries for some reason?

    thanks!

     
  • Rony Shapiro

    Rony Shapiro - 2021-10-13

    Is the "mismatch" warning still printed on the version you've built from source?
    Is the "File or path not found" printed to the shell or in the login window?

     
  • seth

    seth - 2021-10-13

    The error comes up when I click the green button on the initial password safe window

    strace file attached
    Terminal output from strace:
    1:28:38 PM: Warning: Mismatch between the program and library build versions detected.
    The library used 3.0 (wchar_t,compiler with C++ ABI 1014,wx containers,compatible with 2.8),
    and your program used 3.0 (wchar_t,compiler with C++ ABI 1016,wx containers,compatible with 2.8).

    ** (pwsafe:11289): WARNING **: 13:28:38.968: Unable to connect to dbus: Error spawning command line “dbus-launch --autolaunch=07a666ec1188482586ec69c20dfa5bdf --binary-syntax --close-stderr”: Child process exited with code 1

    (pwsafe:11289): Gtk-WARNING **: 13:28:38.974: Unable to locate theme engine in module_path: "adwaita",

    (pwsafe:11289): Gtk-WARNING **: 13:28:39.002: Unable to locate theme engine in module_path: "murrine",

    (pwsafe:11289): Gtk-WARNING **: 13:28:39.003: Unable to locate theme engine in module_path: "murrine",

    (pwsafe:11289): Gtk-WARNING **: 13:28:39.006: Unable to locate theme engine in module_path: "murrine",

    (pwsafe:11289): Gtk-WARNING **: 13:28:39.007: Unable to locate theme engine in module_path: "murrine",

    (pwsafe:11289): Gtk-WARNING **: 13:28:39.008: Unable to locate theme engine in module_path: "murrine",

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.015: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.016: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.016: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.020: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.020: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.020: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.025: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.025: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.025: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.030: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.030: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.030: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.187: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.187: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:28:39.187: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:29:47.205: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:29:47.205: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:29:47.205: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:30:05.325: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:30:05.325: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

    (pwsafe:11289): GLib-GIO-CRITICAL **: 13:30:05.326: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

     
  • seth

    seth - 2021-10-13

    here is the stacer file

     
  • seth

    seth - 2021-10-13

    Thats all from the 1.14 version that I just re-compiled after you suggested doing so.

     
    • Rony Shapiro

      Rony Shapiro - 2021-10-14

      This is beginning to look like an environment issue:

      1. According to strace, the library that's causing the warning to be
        printed is /usr/lib/gconv/UTF-32.so. You might want to run "ldd -v which pwsafe" to see how this gets loaded, which could help you upgrade it.
      2. The other warnings + the "file or path not found" popup could be due to
        permission issues. Can you try running PasswordSafe as root and see what
        happens (no need to attach another strace file).
      3. If this doesn't help, you might want to build pwsafe in Debug, run under
        gdb and send a stacktrace when the popup appears. Let me know if you need
        instructions on how to do this.

      On Wed, Oct 13, 2021 at 11:39 PM seth sethicusprime@users.sourceforge.net
      wrote:

      Thats all from the 1.14 version that I just re-compiled after you
      suggested doing so.


      Status: accepted
      Group: Next release
      Labels: linux
      Created: Wed Oct 06, 2021 11:39 AM UTC by seth
      Last Updated: Wed Oct 13, 2021 08:37 PM UTC
      Owner: Rony Shapiro

      "File or path not found" when pressing Yubikey button.
      passwordsafe 1.13.0-1

      OS: Garuda Linux
      Kernel: 5.14.9-zen2-1-zen
      Shell: bash
      DE: Plasma 5.22.5
      WM: KWin

      Yubikey dependencies installed:
      yubico-c 1.13-6
      yubico-c-client 2.15-5
      yubikey-personalization 1.20.0-3


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/passwordsafe/bugs/1548/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

      --
      Ubi dubium, ibi libertas (where there is doubt, there is freedom)

       

      Related

      Bugs: #1548

  • b-schliessmann

    b-schliessmann - 2022-01-29

    Hello, I've run into the same issue with 1.13, installed from deb package on sf.

    It turns out, as soon as you insert the Yubikey, the text field contents where you enter the database's name are ellipsised, meaning the middle part is left out and substituted by "..." so that beginning and end are visible.

    Pressing the Yubikey button evaluates the text field's content verbatim, i.e. the ellipsised name, which might not exist in most cases, theoretically speaking.

    As a workaround, enlarge the window so the whole name fits inside the text field => Yubikey works.

    Please excuse me being not versed in wxWidgets, otherwise I'd have provided a patch. I tried, but I couldn't grasp the weird logic when this "ellipsisation" takes place and where. As a matter of fact, SafeCombinationEntryDlg::OnYubibtnClick uses m_filename as well as ::OnOK, but the latter works as the filename seems to only be ellipsised when using a Yubikey.

    (Also, strangely, I couldn't manage to grab the filename used in the lookup with strace -f. Any idea why?)

     
  • rafaelx

    rafaelx - 2022-01-31

    Just for info. There is an attempt on Github to fix this issue.

     
  • rafaelx

    rafaelx - 2022-02-03
    • status: accepted --> pending
     
  • rafaelx

    rafaelx - 2022-02-03

    Fixed with commit 4b6ae7a.

     
  • Rony Shapiro

    Rony Shapiro - 2022-06-02
    • Status: pending --> closed
     

Log in to post a comment.

MongoDB Logo MongoDB