Open Morten03Nordbye opened 4 months ago
Are there any debug option?
I can reproduce the issue. For some reason the Bitwarden servers have started falsely rejecting requests simply as “incorrect password” and I don’t know why. I can add the specific headers (both are needed):
Bitwarden-Client-Name: web
Bitwarden-Client-Version: 2024.4.2
and it works again. In theory there might also be other values I can set these headers too that works, but the Desktop client seems to have disabled devtools so I can’t verify anything.
Problem is I’m not so keen on hardcoding dates into the source code. I’ll make a post on a Bitwarden forums about this, maybe I can get some clarity. If Bitwarden themselves are trying to stamp out third-party apps then unfortunately I’ve little interest in maintaining this project (especially since I don’t actually use Bitwarden anymore).
Nevermind, I figured that setting any values for those headers works. Should be fixed in v1.1.3.
Thanks for the help
╔═ 08:14:44 [mnordbye@mnordbye-laptop] ~/Downloads ╚═ $ rofi-bw Warning: failed to load cache
Caused by: decryption failed
Still having some issues.
That message appeared for me as well, but only once and after that it was fine. So I’m not sure what caused it, but I thought it wasn’t a problem. Does it persist for you?
Yes it is persistent.
╔═ 06:01:34 [mnordbye@mnordbye-laptop] ~ ╚═ $ rofi-bw Warning: failed to load cache
Caused by: decryption failed Warning: failed to load cache
Caused by: decryption failed Warning: failed to load cache
Caused by: decryption failed Warning: failed to load cache
Caused by: decryption failed ^C
Each time, does it tell you that the master password was incorrect?
Difficult to debug, since I can’t reproduce.…
╔═ 11:42:09 [mnordbye@mnordbye-laptop] ~
╚═ $ rofi-bw -V
rofi-bw 1.1.3
╔═ 11:42:10 [mnordbye@mnordbye-laptop] ~
╚═ $ rofi -V
Version: 1.7.1
╔═ 11:42:15 [mnordbye@mnordbye-laptop] ~
╚═ $ cat .config/rofi-bw/config.toml
# The time until your vault automatically locks (and the rofi-bw daemon exits).
# Can be set to a duration like `2h` or `15m` or `never`.
# Default: 15m
auto_lock = "8h"
# Whether a notification is sent when a value is copied from the vault.
# Default: true
copy_notification = false
# The Client ID to use with the Bitwarden API.
# Default: "desktop"
client_id = "web"
# The device name to use with the Bitwarden API.
# Default: "linux"
device_name = "linux"
# The device type to use with the Bitwarden API.
# See here for the full list:
# https://github.com/bitwarden/server/blob/master/src/Core/Enums/DeviceType.cs
# Default: "Linux"
device_type = "Linux"
# Optons to pass to Rofi when invoking it
[rofi_options]
# The binary to invoke.
# Default: "/usr/bin/rofi"
#binary = "/usr/local/bin/rofi"
# The number of threads Rofi should use.
# This corresponds to Rofi’s `-threads` option.
# Zero indicates that Rofi should autodetect the number of threads to use.
# Default: 0
#threads = 8
# Whether Rofi should be case sensitive or not.
# This corresponds to Rofi’s `-case-sensitive` option.
# Default: false
#case_sensitive = true
#
# Wheher Rofi should cycle through the item list when it reaches the bottom.
# This corresponds to Rofi’s `-cycle` option.
# Default: same as Rofi, which is currently true.
#cycle = false
#
# The path to the configuration file Rofi should load.
# This corresponds to Rofi’s `-config` option.
# Default: loads Rofi’s default config file
#config = "/home/me/.config/rofi/some-custom-config.rasi"
#
# The scroll method Rofi should use.
# This corresponds to Rofi’s `-scroll-method` option.
# Possible values: "per_page", "continuous"
# Default: same as Rofi, which is currently "per_page"
#scroll_method = "continuous"
# Whether Rofi should normalize the string before matching, allowing `o` to match `ö` and `é` to
# match `e`.
# This corresponds to Rofi’s `-normalize-match` option.
# Enabling this option currently disables highlighting of the matched part.
# Default: false
#normalize_match = false
# Whether Rofi should lazily grab the keyboard, not before the UI is shown.
# This corresponds to Rofi’s `-no-lazy-grab` option.
# Default: true
#lazy_grab = false
#
# Whether Rofi should act like a normal application window.
# This corresponds to Rofi’s `-normal-window` option.
# Default: false
#normal_window = true
#
# The matching algorithm Rofi should use.
# This corresponds to Rofi’s `-matching` option.
# Possible values: "normal", "regex", "glob", "fuzzy", "prefix"
# Default: same as Rofi, which is currently "normal"
#matching = "prefix"
#
# The character that can negate the query. Set to "\u0000" to disable.
# This corresponds to Rofi’s `-matching-negate-char` option.
# Default: same as Rofi, which is currently "-"
#matching_negate_char = "!"
#
# Path to the theme file format to use.
# This corresponds to Rofi’s `-theme` option.
# Default: uses Rofi’s normal theme
#theme = "my_custom_theme"
# Ad-hoc theme configuration to apply.
# This corresponds to Rofi’s `-theme-str` option.
# Default: ""
#theme_str = """
# element {
# children: [element-icon, element-text];
# }
# element-icon {
# size: 2em;
# }
#"""
# Whether clicking outside the Rofi window should cause it to exit.
# This corresponds to Rofi’s `-click-to-exit` and `-no-click-to-exit` options.
# Default: true
click_to_exit = false
╔═ 11:42:37 [mnordbye@mnordbye-laptop] ~
╚═ $ rofi-bw
Warning: failed to load cache
Caused by:
decryption failed
Warning: failed to load cache
Caused by:
decryption failed
Warning: failed to load cache
Caused by:
decryption failed
Warning: failed to load cache
Caused by:
decryption failed
here I tried to sign in 3 times + signing out then trying to sign back in
Yes it keep saying the password is incorrect
Unable to Sign In with Correct Password on rofi-bw v1.1.2
Description
I am currently experiencing an issue with
rofi-bw
version 1.1.2 where I am unable to sign in despite using the correct password. This issue has persisted across multiple attempts, and I've verified that my password is correct.Steps to Reproduce
Expected Behavior
I expect to successfully sign in since the credentials are correct.
Actual Behavior
The sign-in fails, and I am returned to the login prompt without any error message indicating why the authentication failed.
Environment