Bug 419539

As I reproduced it 3 times I attached 3 "debug" group of file.

Each group includes:
1) systemd journal log with verbosity of msgs of 3 and 7 priorities;
2) core dump.

Each group file starts w/ kruX, where X is group number.

Additionally attached: one screenshot of search criteria for all groups.

kru1 core dump compressed file has size of 8.0 MiB. Can't upload it due to server limitation.

Created attachment 127192 [details]
kru1_journalctl_p3_xb

Created attachment 127193 [details]
kru1_journalctl_p7_xb

Created attachment 127194 [details]
kru2 core.krusader.1000.48ccb4b8f5f94681a95bbb70c981860d.71061.1585842691000000000000

Created attachment 127195 [details]
kru2_journalctl_p3_xb

Created attachment 127196 [details]
kru2_journalctl_p7_xb

Created attachment 127197 [details]
kru3 core.krusader.1000.48ccb4b8f5f94681a95bbb70c981860d.71890.1585842911000000000000

Created attachment 127198 [details]
kru3_journalctl_p3_xb

Created attachment 127199 [details]
kru3_journalctl_p7_xb

Created attachment 127200 [details]
kru_all search criteria for all groups

Still happens in Krusader v2.7.2 on
```
Operating System: Manjaro Linux
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.2
Kernel Version: 5.10.0-1-MANJARO
OS Type: 64-bit
```

Backtrace of dumped core:

```
$ gdb /usr/bin/krusader core.krusader.1000.d883f3689ebb4734b4d95af28be6150a.5708.1607817972000000
GNU gdb (GDB) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/krusader...
(No debugging symbols found in /usr/bin/krusader)

warning: Can't open file /memfd:xorg (deleted) during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file /memfd:xshmfence (deleted) during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing
[New LWP 5708]
[New LWP 5751]
[New LWP 5750]
[New LWP 5747]
[New LWP 5748]
[New LWP 5763]
[New LWP 5738]
[New LWP 6596]
[New LWP 5749]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/krusader -qwindowtitle Krusader'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000055b40bdc5a93 in ?? ()
[Current thread is 1 (Thread 0x7fef4cfbb240 (LWP 5708))]
(gdb) bt
#0  0x000055b40bdc5a93 in  ()
#1  0x000055b40bdc9fde in  ()
#2  0x000055b40bdd54d6 in  ()
#3  0x000055b40bdd5848 in  ()
#4  0x000055b40bdd5a46 in  ()
#5  0x000055b40bdd31dd in  ()
#6  0x00007fef5131fe10 in  () at /usr/lib/libQt5Core.so.5
#7  0x00007fef51ebed53 in QAbstractButton::clicked(bool) () at /usr/lib/libQt5Widgets.so.5
#8  0x00007fef51ebf6dc in  () at /usr/lib/libQt5Widgets.so.5
#9  0x00007fef51ec1083 in  () at /usr/lib/libQt5Widgets.so.5
#10 0x00007fef51ec1263 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5
#11 0x00007fef51e0eb0e in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5
#12 0x00007fef51dcd752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#13 0x00007fef51dd487b in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#14 0x00007fef512e8a7a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#15 0x00007fef51dd387e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () at /usr/lib/libQt5Widgets.so.5
#16 0x00007fef51e27249 in  () at /usr/lib/libQt5Widgets.so.5
#17 0x00007fef51e2a63f in  () at /usr/lib/libQt5Widgets.so.5
#18 0x00007fef51dcd752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#19 0x00007fef512e8a7a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#20 0x00007fef516c2594 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5
#21 0x00007fef51697bb5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Gui.so.5
#22 0x00007fef4cbc716c in  () at /usr/lib/libQt5XcbQpa.so.5
#23 0x00007fef4fae78f4 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#24 0x00007fef4fb3b821 in  () at /usr/lib/libglib-2.0.so.0
#25 0x00007fef4fae6121 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#26 0x00007fef513416e1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#27 0x00007fef512e73fc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#28 0x00007fef512ef894 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#29 0x000055b40bcb1015 in  ()
#30 0x00007fef50b6f152 in __libc_start_main () at /usr/lib/libc.so.6
#31 0x000055b40bcb28fe in _start ()
(gdb) 
```

Wasn't resolved.
Now Krusader and Plasma got updates, so the bug is old.

Will looking into newer Krusader version (git).

> Now Krusader and Plasma got updates, so the bug is old.
> Will looking into newer Krusader version (git).            
Thanks, pveax. Please, feel free to reopen this bug report if you still find that problem.

Created attachment 141094 [details]
The crash happens using Kubuntu 20.04 LTS even excluding some special folders (see the screenshot) and using the git version of Krusader.

> Now Krusader and Plasma got updates, so the bug is old.
> Will looking into newer Krusader version (git).  

Does still happen to you?

(In reply to Toni Asensi Esteve from comment #16)
> Does still happen to you?

Hi, Toni! Thanks for reply.

Look, that issue
`Reported:	2020-04-02`
about the Krusader of version from a <how much?> ago. Take a look: https://invent.kde.org/utilities/krusader/-/commits/v2.7.2

I do not want to stuck on so old and never-update-to-release version, so I decided to switch to `-git` latest version to get all fixes and features.

The answer about that old version "from 90s": I do not know - not use it anymore. Just want to use more modern (as bugs-at-last-fixed and feature-rich) version.

I do not meet the bug on `-git` version yet.

Also you mentioned "The crash happens using Kubuntu 20.04 LTS".
"The crash".
For me it is a bit strange: how a user decide that the root reason caused a crash are the same in our cases. Probably you have exactly the same:
-) all of environment, incl. kernel version;
-) backtrace of dumped core.

Also remember the `vlc` package?
> Before you file a new bug, please try a preview development build of our next version on our nightly build website. The bug may already be fixed in those builds.

So try `-git` version first. I promise, developers will be happy to do not switch to so old version, to compile, (where they get the so old environment we used at that moment?), will try to reproduce, even if they fix it in the v2.7.2, after that they should look into current code state, trying to figure out if there is still that lack or not.
But if you report about freshest version it will be much more easier to inspect and debug current version and to ship bugfix.

Also kernels are changing (LTS also got fixes), backtrace engine got updates.
Reproduce a fresh bug and report it if you love a developers and want to support a project to grow faster and easier.

Toni, please, now you manage that ticket as I closed it and switched to current app version, but you decided to re-open it.

Thank you!

Ok. As the problem happens using the git version of Krusader, and using different kernel versions, Qt versions, etc., we can say that this bug is "verified" (although the problem may be outside of Krusader :-) ).

Toni, as me

> I do not meet the bug on `-git` version yet.

(noted in Comment 17th)

and you mentioned

> As the problem happens using the git version of Krusader

in the next comment,
it is a good idea to post the exact version of your `krusader-git` a Backtrace of dumped core to make developers see in which module/line it occurs.

It is not my business anymore, but probably can help to resolve the issue you meet faster.

As I see your current report about git version looks like described as "`krusader-git` crashing while make a search".
If you want to leave it as that, it is you choice how hard you want developers to fix it.
May be I am wrong, but I do not see any detail of now YOUR report, as now you only meet the issue. Currently with the
```
$ pacman -Qi krusader-git | grep Version
Version         : 2.8.0.dev.r6378.gae1bf6b9-1
```
I do not meet the issue I reported earlier while was using the stable version of Krusader released 2.5 years ago (https://invent.kde.org/utilities/krusader/-/commit/f66e9fe2076015804bd4352f8469345d16ecda07).

Cheers!

Good, I tried the git version of Krusader (with other software which is more recent) and the problem wasn't seen.