Crashing upon search #1254

frozenstuff · 2017-12-06T02:56:52Z

Expected Behavior

Search should not crash the program.

Current Behavior

Searching will immediately close the program on Linux Mint 18.3 Cinnamon.

Context

Search did not crash before 2.2.2. I have to re-open Keepass and enter my key as if I was starting the program up.

Debug Info

KeePassXC - Version 2.2.2
Revision: 6d46717

Libraries:

Qt 5.5.1
libgcrypt 1.6.5

Operating system: Linux Mint 18.3
CPU architecture: x86_64
Kernel: linux 4.14.0-041400-generic

Enabled extensions:

KeePassHTTP
Auto-Type
YubiKey

The text was updated successfully, but these errors were encountered:

droidmonkey · 2017-12-06T04:15:48Z

Does this happen in any database, even a brand new one? Any search term at all?

frozenstuff · 2017-12-06T04:20:31Z

Just made a new blank database. It did not crash then.

I quit and reopened my other database. Any search time at all will crash it, even before I finish typing.

droidmonkey · 2017-12-06T20:49:24Z

How did you create your database, was it from keepass 2?

frozenstuff · 2017-12-07T03:33:19Z

I created both databases within Keepassxc.

droidmonkey · 2017-12-07T19:47:35Z

Yikes, i fear the only way for us to debug this is to send us your broken database.... Are you able to compile the application in debug mode and run it through a debugger?

frozenstuff · 2017-12-08T03:31:16Z

That sounds a bit beyond my scope but I could do it if you have some sort of tutorial. And obviously the database has all my passwords so I'm a little weary of sending that...

If my database is at risk of breaking/corrupting, is it easy to fix by creating a new database then doing an export/import?

droidmonkey · 2017-12-08T03:46:14Z

I could build a debug version that works in Mint 18.3 and provide it to you with simple instructions on how to run it in the debugger. Will likely get to that this weekend. We definitely want to fix the crash, so don't delete the database. This would only cause problems if the program crashed before you could save your database after any changes.

TheZ3ro · 2017-12-08T12:20:06Z

Alternatively you can:
(- Always make a backup of your current database and store it safely)

Make another copy of your database and open it
Delete entries one-by-one in the second copy until KeePassXC don't crash anymore
The entry you just deleted is the one that crash the DB

Then you can report to us if this entry has some problem or strange field.

droidmonkey · 2017-12-08T22:03:26Z

OK, please download the following build of KeePassXC and perform the below steps https://www.dropbox.com/s/cqyhjqdybousnou/keepassxc-2.2.2-debug.tar.gz

Extract the files to your downloads folder (or where ever) and then open a terminal in the keepassxc-debug/bin folder.
Type in gdb ./keepassxc then when you get to the (gdb) prompt type in r <enter>.
KeePassXC will open, now select your database, unlock it, and initiate a search. This should crash the application and you'll be dropped back into the terminal at the (gdb) prompt.
Type in bt <enter> and copy/paste the output to this issue. This is the backtrace which shows exactly where the application crashed. It looks like this:

(gdb) bt
#0  0x00007ffff5cc570d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007ffff4c4a38c in g_main_context_iterate (priority=2147483647, n_fds=10, fds=0x555555f7dae0, timeout=<optimized out>, context=0x7fffe40016f0)
    at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4135
#2  0x00007ffff4c4a38c in g_main_context_iterate (context=context@entry=0x7fffe40016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
    at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835

Type in q <enter> and then y <enter> if necessary. You are done!

frozenstuff · 2017-12-10T02:35:08Z

Thanks for the help. If it makes any difference, Keepassxc froze instead and Mint said the program wasn't responding. Normally it just disappears. Here's the output:

(gdb) bt
#0 0x00007ffff67f1ae8 in QSortFilterProxyModel::parent(QModelIndex const&) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1 0x00007ffff792ef7b in QTreeView::isIndexHidden(QModelIndex const&) const ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2 0x00007ffff7930ea7 in QTreeView::visualRect(QModelIndex const&) const ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3 0x00007ffff78d75da in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4 0x00007ffff78d7ae8 in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5 0x00007fffedd909d9 in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6 0x00007fffedd90f49 in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7 0x00007fffedd963ac in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8 0x00007ffff6a9babe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9 0x00007ffff6a9d26e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x00007ffff6856c01 in QObject::event(QEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007ffff769305c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007ffff7698516 in QApplication::notify(QObject*, QEvent*) ()

droidmonkey · 2017-12-10T04:13:27Z

That's odd, it stopped in qt code. See if you can get it to stop/crash a couple of times and see if the output of bt is any different.

The next best option is to do what @TheZ3ro mentioned... Copy your db snd then delete entries or groups one by one to see when it stops crashing.

frozenstuff · 2017-12-10T04:21:10Z

Crashed a couple more times. Looks the same:

Thread 1 "keepassxc" received signal SIGSEGV, Segmentation fault.
0x00007ffff67f1ae8 in QSortFilterProxyModel::parent(QModelIndex const&) const
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) bt
#0 0x00007ffff67f1ae8 in QSortFilterProxyModel::parent(QModelIndex const&) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1 0x00007ffff792ef7b in QTreeView::isIndexHidden(QModelIndex const&) const ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2 0x00007ffff7930ea7 in QTreeView::visualRect(QModelIndex const&) const ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3 0x00007ffff78d75da in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4 0x00007ffff78d7ae8 in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5 0x00007fffedd909d9 in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6 0x00007fffedd90f49 in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7 0x00007fffedd963ac in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8 0x00007ffff6a9babe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9 0x00007ffff6a9d26e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x00007ffff6856c01 in QObject::event(QEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007ffff769305c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007ffff7698516 in QApplication::notify(QObject*, QEvent*) ()

phoerious · 2017-12-10T08:46:56Z

It's probably the same issue as #335, which may be the same as or related to https://bugreports.qt.io/browse/QTBUG-52601
I had another guy on IRC this week with the same problem on Mint 18.1.
You should try out the AppImage, which should work without crashes.

frozenstuff · 2017-12-12T02:40:18Z

Huh, mine crashes between groups too. I used to use it but stopped so I never noticed.

dmiwell · 2018-01-18T17:33:16Z

Thanks @phoerious

AppImage seems to work fine for me on Mint 18.3. I don't get crashes.

thomaspasser · 2018-01-18T22:40:11Z

I have the same problem:

Thread 1 "keepassxc" received signal SIGSEGV, Segmentation fault.
0x00007ffff6a03ae8 in QSortFilterProxyModel::parent(QModelIndex const&) const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) bt
#0  0x00007ffff6a03ae8 in QSortFilterProxyModel::parent(QModelIndex const&) const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x00007ffff7b40f7b in QTreeView::isIndexHidden(QModelIndex const&) const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2  0x00007ffff7b42ea7 in QTreeView::visualRect(QModelIndex const&) const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3  0x00007ffff7ae95da in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x00007ffff7ae9ae8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x00007fffefaf39d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6  0x00007fffefaf3f49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7  0x00007fffefaf93ac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x00007ffff6cadabe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x00007ffff6caf26e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x00007ffff6a68c01 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007ffff78a505c in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007ffff78aa516 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007ffff6a3938b in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007ffff6a3b786 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007ffff6a8f3c3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007ffff5406197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff54063f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007ffff540649c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff6a8f7cf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007ffff6a36b4a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007ffff6a3ebec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x0000555555596e38 in main (argc=1, argv=0x7fffffffde48) at /home/*****/builds/keepassxc-2.2.4/src/main.cpp:153
(gdb)

phoerious · 2018-01-19T08:47:26Z

It's the same problem and a bug in Qt 5.5. To get rid of it, either use the AppImage or upgrade to an Ubuntu version that ships at least 5.6.

phoerious · 2018-05-24T07:43:09Z

Closing this, since it appears to be the same issue and we cannot fix it.

clippclopp · 2018-05-25T03:41:22Z

@phoerious

Some more info to share on the above as I have been running KeepassXC successfully on Mint 18.3 and also experienced the same issues as above.

I have multiple devices running identical mirrors of Linux Mint. Same libraries, programs, etc. This issue described by the OP has occurred 3x now on different machines for me at the application level.

The database crash isn't reproduced on other machines and I can use the databases just fine on "working" machines. Meanwhile the machine experiencing the crashes has the same behaviour with any KeepassXC database. Including new ones created for testing. A full, clean install of the OS resolves the issue, but beyond that have not been able to fix.

As weird as this may sound, I believe the issue happens when I update too many entries too fast while having the "automatic save on every change" and/or "backup database before saving" features enabled. It seems that if a change is made before the previous change is finished saving, the application crashes. And anytime the application is launched going forward, it crashes on searches and directory/folder navigation.

I can't seem to pinpoint where it's getting hung up, but it doesn't seem to be the QT issue as mentioned earlier (at least in my case) since I'm successfully running the same database on the same version of Linux Mint on other machines (exactly the same).

It isn't until something goes haywire once on the particular KeepassXC install that it then continues to have issues. Or there's a unusual coincidence.

phoerious · 2018-05-25T04:30:17Z

It is a Qt bug and we cannot fix it. Mint 18.3 is also based on Ubuntu 16.04, which has Qt 5.5. Use our AppImage if you cannot upgrade your system.

droidmonkey · 2018-05-25T10:24:54Z

For the record, you can't possibly do anything with KeePassXC until the save is complete since it's a synchronous function.

clippclopp · 2018-05-25T11:58:08Z

Ok got it. Thank you both for the reply. So strange it works without a hitch on some devices running Mint 18.3 but not others. I'll use the AppImage for now and try upgrading the system to see if that resolve.

Edit: Also forgot to note that the Linux Mint device that KeepassXC is crashing on only crashes for one user. Installs for other regular and sudo users on the same device are not experiencing the crash issue.

lagagain · 2018-07-17T15:09:41Z

Note the temp solution:

I got the same question, and my OS is LinuxMint 18.3. Before today I haven't the question, but it happened today(I guess because that some Qt composes upgrade auto, but not sure).

And using AppImage is good, no this question. If someone gets the same question, can use AppImage temp.

louib mentioned this issue Jan 18, 2018

KeepassXC 2.2.4 crashes on search attempt #1399

Closed

phoerious mentioned this issue Feb 28, 2018

Crash when selecting another group in the tree on the left. #1554

Closed

StevenMapes mentioned this issue Apr 12, 2018

segfault in libQt5Core.so.5.5.1 for version 2.3.1 #1839

Closed

phoerious closed this as completed May 24, 2018

phoerious added the duplicate label May 24, 2018

phoerious mentioned this issue Jun 2, 2018

Segmentation fault #2018

Closed

phoerious mentioned this issue Aug 10, 2018

"Segmentation fault" after two or more clicks in the gui #2195

Closed

phoerious mentioned this issue Aug 18, 2018

Segfault when searching #2208

Closed

droidmonkey mentioned this issue Aug 18, 2018

Provide warning to users with Qt 5.5.x about potential crash #2211

Merged

droidmonkey mentioned this issue Sep 18, 2018

keepassxc crashes on Ubuntu 18.04.1: error while loading shared libraries: libQt5Network.so.5 #2241

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Crashing upon search #1254

Crashing upon search #1254

frozenstuff commented Dec 6, 2017 •

edited

Loading

droidmonkey commented Dec 6, 2017

frozenstuff commented Dec 6, 2017

droidmonkey commented Dec 6, 2017

frozenstuff commented Dec 7, 2017

droidmonkey commented Dec 7, 2017

frozenstuff commented Dec 8, 2017

droidmonkey commented Dec 8, 2017 •

edited

Loading

TheZ3ro commented Dec 8, 2017

droidmonkey commented Dec 8, 2017 •

edited

Loading

frozenstuff commented Dec 10, 2017 •

edited

Loading

droidmonkey commented Dec 10, 2017 •

edited

Loading

frozenstuff commented Dec 10, 2017

phoerious commented Dec 10, 2017 •

edited

Loading

frozenstuff commented Dec 12, 2017

dmiwell commented Jan 18, 2018

thomaspasser commented Jan 18, 2018 •

edited

Loading

phoerious commented Jan 19, 2018

phoerious commented May 24, 2018

clippclopp commented May 25, 2018 •

edited

Loading

phoerious commented May 25, 2018

droidmonkey commented May 25, 2018

clippclopp commented May 25, 2018 •

edited

Loading

lagagain commented Jul 17, 2018

Crashing upon search #1254

Crashing upon search #1254

Comments

frozenstuff commented Dec 6, 2017 • edited Loading

Expected Behavior

Current Behavior

Context

Debug Info

droidmonkey commented Dec 6, 2017

frozenstuff commented Dec 6, 2017

droidmonkey commented Dec 6, 2017

frozenstuff commented Dec 7, 2017

droidmonkey commented Dec 7, 2017

frozenstuff commented Dec 8, 2017

droidmonkey commented Dec 8, 2017 • edited Loading

TheZ3ro commented Dec 8, 2017

droidmonkey commented Dec 8, 2017 • edited Loading

frozenstuff commented Dec 10, 2017 • edited Loading

droidmonkey commented Dec 10, 2017 • edited Loading

frozenstuff commented Dec 10, 2017

phoerious commented Dec 10, 2017 • edited Loading

frozenstuff commented Dec 12, 2017

dmiwell commented Jan 18, 2018

thomaspasser commented Jan 18, 2018 • edited Loading

phoerious commented Jan 19, 2018

phoerious commented May 24, 2018

clippclopp commented May 25, 2018 • edited Loading

phoerious commented May 25, 2018

droidmonkey commented May 25, 2018

clippclopp commented May 25, 2018 • edited Loading

lagagain commented Jul 17, 2018

frozenstuff commented Dec 6, 2017 •

edited

Loading

droidmonkey commented Dec 8, 2017 •

edited

Loading

droidmonkey commented Dec 8, 2017 •

edited

Loading

frozenstuff commented Dec 10, 2017 •

edited

Loading

droidmonkey commented Dec 10, 2017 •

edited

Loading

phoerious commented Dec 10, 2017 •

edited

Loading

thomaspasser commented Jan 18, 2018 •

edited

Loading

clippclopp commented May 25, 2018 •

edited

Loading

clippclopp commented May 25, 2018 •

edited

Loading