-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to Enable Browser Intergration Cause App to Crash #1922
Comments
Found the issue. In the meantime you can edit |
Thanks |
Just like to add that this affects the Win64 portable installation on Win 7: When I try to enable browser integration the app crashes when I apply or ok the app crashes Expected Behavior Current Behavior Steps to Reproduce: Click box to enable browser integration Unfortunately the workaround of change browser enabled to true in |
You need to set it to false, not true. |
Sorry I misunderstood the workaround I thought this would allow the use of the browser integration not just enable the app to open again. I did not have the setting enabled initially but would like to be able to use it. |
You can use browser integration if you disable the use of a proxy (either in the settings or via SupportBrowserProxy=false). In that case, however, the browser will try to open a new KeePassXC instance. |
I currently have UseCustomProxy set to false in keepass.ini but setting enabled to true still crashes KeepassXC |
Sorry, my bad. It's not the custom proxy option, but the option to use a proxy which you need to disable. |
Hmmm, disabling that does help resolve the error but there now seems to be no communication between the extension and KeePassXC even if I point the custom proxy location at keepassxc-proxy.exe |
I've also downgraded in order to keep the browser integration |
@hughwilliams94 When you disable the proxy, your browser will start a new KeePassXC instance. That means that you need to quit any running instance and then click "Reload" in the browser. We pulled the 2.3.2 release and will release a fixed 2.3.3 later today. |
I have tried all variants on restarting and reloading both browser and KeePassXC to no avail, I will happily wait for an updated version. |
Setting SupportBrowserProxy=false should work around it. But downgrading for now is a solution, too. |
Updating to version 2.3.3 seems to have fixed it |
2.3.3 does not solve the issue on Win 7 64. There is no error but there is also no connection between KeePassXC and Firefox. |
@hughwilliams94 I will check it out. |
@hughwilliams94 I installed 2.3.3 and uninstalled the old version as suggested. Everything worked. Then disabled all the browsers from the settings and disabled the whole browser integration. Restarted KeePassXC and enabled the browser support again (tried what the browser extension said before, and it was timeout, so no connection). Still worked. If you do the same steps, does it help? |
Yes these steps fixed it, I think I just tried too many different combinations. Win7 64 portable works with browser integration now. Thanks for your help and the speedy fix everybody! |
I got the same error, but in a different action. I have a Keepass db, and move groups one into others; the first, works; second, make KeePassXC crashes. $ keepassxc
QObject::startTimer: Timers cannot have negative intervals
Violación de segmento $ keepassxc -v
keepassxc 2.3.3
$ qmake -v
QMake version 3.0
Using Qt version 5.5.1 in /usr/lib/x86_64-linux-gnu
$ lsb_release --all
LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: LinuxMint
Description: Linux Mint 18.1 Serena
Release: 18.1
Codename: serena ~/.config/keepassxc/keepassxc.ini [General]
AutoReloadOnChange=true
AutoSaveAfterEveryChange=false
AutoSaveOnExit=false
AutoTypeDelay=25
AutoTypeEntryTitleMatch=true
AutoTypeEntryURLMatch=true
AutoTypeStartDelay=500
BackupBeforeSave=false
GlobalAutoTypeKey=0
GlobalAutoTypeModifiers=0
IgnoreGroupExpansion=true
LastChallengeResponse=@Variant(\0\0\0\x1c\0\0\0\0)
LastDatabases=/home/joserprieto/documents/keys.kdbx
LastDir=/home/joserprieto/documents
LastKeyFiles=@Variant(\0\0\0\x1c\0\0\0\0)
MinimizeOnCopy=false
OpenPreviousDatabasesOnStartup=true
RememberLastDatabases=true
RememberLastKeyFiles=true
SSHAgent=false
ShowToolbar=true
SingleInstance=true
UseAtomicSaves=true
UseGroupIconOnEntryCreation=true
[Browser]
AlwaysAllowAccess=false
AlwaysAllowUpdate=false
BestMatchOnly=false
CustomProxyLocation=false
Enabled=false
MatchUrlScheme=true
SearchInAllDatabases=false
ShowNotification=true
SortByUsername=false
SupportBrowserProxy=true
SupportKphFields=true
UnlockDatabase=true
UpdateBinaryPath=false
UseCustomProxy=false
[GUI]
DarkTrayIcon=false
HideDetailsView=false
Language=system
MinimizeOnClose=false
MinimizeOnStartup=false
MinimizeToTray=false
ShowTrayIcon=false
[Http]
AlwaysAllowAccess=false
AlwaysAllowUpdate=false
BestMatchOnly=false
Enabled=false
MatchUrlScheme=true
Port=19455
SearchInAllDatabases=false
ShowNotification=true
SortByUsername=false
SupportKphFields=true
UnlockDatabase=true
generator\EASCII=false
generator\EnsureEvery=true
generator\ExcludeAlike=true
generator\Length=16
generator\LowerCase=true
generator\Numbers=true
generator\SpecialChars=false
generator\UpperCase=true
[generator]
EASCII=false
EnsureEvery=true
ExcludeAlike=true
Length=16
LowerCase=true
Numbers=true
SpecialChars=false
Type=0
UpperCase=true
WordCount=6
WordList=eff_large.wordlist
WordSeparator=" "
[security]
IconDownloadFallbackToGoogle=false
autotypeask=true
clearclipboard=true
clearclipboardtimeout=10
hidenotes=false
hidepassworddetails=true
lockdatabaseidle=false
lockdatabaseidlesec=240
lockdatabaseminimize=false
lockdatabasescreenlock=true
passwordscleartext=false
passwordsrepeat=false
relockautotype=false |
It's a crash, but the problem is a totally different one. Mint 18.1 is based on Ubuntu 16.04, which comes with Qt 5.5. Qt versions prior to 5.6 have a bug that causes an application to crash in the situation you described. Please upgrade your system to a newer version or use our AppImage instead. See #335. |
Same kind of error as joserprieto $ keepassxc $ qmake -v $ lsb_release --all ~/.config/keepassxc/ [General] [Browser] [GUI] [Http] [generator] [security] |
@livier, see comment above from @phoerious. |
When I try to enable browser integration the app crashes when I apply or ok the app crashes
Expected Behavior
Browser integration is enabled
Current Behavior
App crashes and browser integration is not enabled
Steps to Reproduce
Debug Info
KeePassXC - Version 2.3.2
Revision: 2bb72eb
Libraries:
Operating system: Linux Mint 18.3
CPU architecture: x86_64
Kernel: linux 4.13.0-36-generic
Enabled extensions:
The text was updated successfully, but these errors were encountered: