Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57139 - [plasma-workspace] krunner crash at usage (randomly)

Attached to Project: Arch Linux
Opened by Nicolas Gruel (gruel) - Thursday, 18 January 2018, 09:49 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 20 February 2018, 23:43 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:

krunner crash very often when I am writing characters inside. I do not know what is happening. I have another session that I barely use which seems to not have the behaviour. It can be something related to my long term usage of not. I don't know but it is extremely annoying and the only information gave by the crash is: segmentation fault.

It seems to happen mainly when krunner is looking in the DB (baloo?) to find what I am writing. If I am doing simple calculation by starting the line with = it seems to not crash.

The main problem is that sometimes it does work, sometimes not.

Additional info:
* package version(s)

5.42.0

Steps to reproduce:

* alt-tab to start krunner
* start writing the name of a software (konsole for example)

result: total crash of krunner. alt-tab cannot start it but right-click + run command is working to restart it.
This task depends upon

Closed by  Antonio Rojas (arojas)
Tuesday, 20 February 2018, 23:43 GMT
Reason for closing:  Fixed
Additional comments about closing:  plasma-workspace 5.12.2
Comment by Antonio Rojas (arojas) - Thursday, 18 January 2018, 11:33 GMT
I suppose this is the QtSql crash in the bookmarks runner, but it's impossible to know without a backtrace. Please run krunner in gdb and post a backtrace of the crash
Comment by Nicolas Gruel (gruel) - Thursday, 18 January 2018, 13:20 GMT
Here the backtrace. Thanks for looking into it.

gdb krunner
GNU gdb (GDB) 8.0.1
Copyright (C) 2017 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:
<http://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 krunner...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/krunner
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe234d700 (LWP 7693)]
[New Thread 0x7fffdb94d700 (LWP 7694)]
[New Thread 0x7fffd35ef700 (LWP 7695)]
[New Thread 0x7fffbec72700 (LWP 7702)]
[New Thread 0x7fffbe471700 (LWP 7703)]
[New Thread 0x7fffaea87700 (LWP 7704)]
[New Thread 0x7fffaba88700 (LWP 7705)]
[New Thread 0x7fffab287700 (LWP 7706)]
[New Thread 0x7fffaaa86700 (LWP 7707)]
[New Thread 0x7fffaa285700 (LWP 7708)]
[New Thread 0x7fffa9a84700 (LWP 7709)]
[New Thread 0x7fffa9283700 (LWP 7710)]
[New Thread 0x7fffa8a82700 (LWP 7711)]
[New Thread 0x7fff8bfff700 (LWP 7712)]
[New Thread 0x7fff8b7fe700 (LWP 7713)]
[New Thread 0x7fff8affd700 (LWP 7714)]
[New Thread 0x7fff8a7fc700 (LWP 7715)]
[New Thread 0x7fff89ffb700 (LWP 7716)]
[New Thread 0x7fff897fa700 (LWP 7717)]
[New Thread 0x7fff88ff9700 (LWP 7718)]
[New Thread 0x7fff6bfff700 (LWP 7719)]
[New Thread 0x7fff6b7fe700 (LWP 7720)]
kf5.karchive: bzDecompress returned -5
ktp-common-internals: Current presence changed
ktp-common-internals: Current presence changed
QSqlDatabasePrivate::removeDatabase: connection '/home/xxxx/.mozilla/firefox/9ormpz77.default/places.sqlite' is still in use, all queries will cease to work.
QSqlDatabasePrivate::addDatabase: duplicate connection name '/home/xxxx/.mozilla/firefox/9ormpz77.default/places.sqlite', old connection removed.

Thread 21 "GlobalQueue[14]" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff88ff9700 (LWP 7718)]
0x00007fffc1869a23 in ?? () from /usr/lib/libsqlite3.so.0
Comment by Antonio Rojas (arojas) - Thursday, 18 January 2018, 13:22 GMT
That's not the backtrace. Type "bt" in gdb after the crash and post the output.
Comment by Nicolas Gruel (gruel) - Thursday, 18 January 2018, 13:55 GMT
Sorry, here the backtrace:

#0 0x00007fffc1802a23 in () at /usr/lib/libsqlite3.so.0
#1 0x00007fffc180302f in () at /usr/lib/libsqlite3.so.0
#2 0x00007fffc17fdfe1 in () at /usr/lib/libsqlite3.so.0
#3 0x00007fffc1790d28 in () at /usr/lib/libsqlite3.so.0
#4 0x00007fffc1797b4b in sqlite3BtreeMovetoUnpacked () at /usr/lib/libsqlite3.so.0
#5 0x00007fffc182298d in sqlite3VdbeExec () at /usr/lib/libsqlite3.so.0
#6 0x00007fffc18293a0 in sqlite3_step () at /usr/lib/libsqlite3.so.0
#7 0x00007fffc1a85a2e in () at /usr/lib/qt/plugins/sqldrivers/libqsqlite.so
#8 0x00007fffc1a86c13 in () at /usr/lib/qt/plugins/sqldrivers/libqsqlite.so
#9 0x00007fffeed18878 in QSqlQuery::exec() () at /usr/lib/libQt5Sql.so.5
#10 0x00007fffc1c9aa8e in () at /usr/lib/qt/plugins/krunner_bookmarksrunner.so
#11 0x00007fffc1ca28ca in () at /usr/lib/qt/plugins/krunner_bookmarksrunner.so
#12 0x00007fffc1c9ff96 in () at /usr/lib/qt/plugins/krunner_bookmarksrunner.so
#13 0x00007fffd0e247f0 in Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at /usr/lib/libKF5Runner.so.5
#14 0x00007fffd0c03618 in ThreadWeaver::Executor::run(QSharedPointer<ThreadWeaver::JobInterface> const&, ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5
#15 0x00007fffd0c02610 in ThreadWeaver::Job::execute(QSharedPointer<ThreadWeaver::JobInterface> const&, ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5
#16 0x00007fffd0c01d45 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5
#17 0x00007ffff3ce1b2d in () at /usr/lib/libQt5Core.so.5
#18 0x00007ffff15f508c in start_thread () at /usr/lib/libpthread.so.0
#19 0x00007ffff35e9e1f in clone () at /usr/lib/libc.so.6
Comment by Antonio Rojas (arojas) - Thursday, 18 January 2018, 13:58 GMT
So it is indeed the QSql crash. As a workaround disable the bookmarks runner.
Comment by Nicolas Gruel (gruel) - Thursday, 18 January 2018, 14:03 GMT
Thanks again to look at it and for the workaround. Good luck for the correction.
Comment by Marc Cousin (cousinm) - Tuesday, 20 February 2018, 12:01 GMT
Hi,

Deactivating the bookmark plugin didn't do the job for me. Rebuilding the package with the (slightly edited) patch from https://phabricator.kde.org/D10610 did it for me. Attached is the revised PKGBUILD.
Comment by bengt yttergrund (bengt_hak_TFO) - Tuesday, 20 February 2018, 17:53 GMT
Deactivating bookmark plugin didn't help. Managed to work it around by downgrading qt5 to 5.10.0.

Qt fix would be nice

Loading...