Bug 430862

> #7  0x00007f2a6809c3e3 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so

Any chance you could install debug packages for kio-extras and attach another bracktrace? It's crashing somewhere in a thimbnailer but I can't tell where without a more complete backtrace.

See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Created attachment 134586 [details]
kdeinit5-20210105-141313-2ndcrash.kcrash.txt

Hi Nate,

First off, thanks so much for your prompt reply, you guys are amazing.
I installed kio-extras-dbgsym, I'm hoping that is the debug package you
recommended, following the info provided on the guidelines and howto
pages.  Could not find the kdelibs5-dbgsym mentioned on the page in the
added repositories.  If there is a package missing, please let me know how
I missed it.

I then restarted the computer and 2 crash reports were generated, they are
attached.

Thanks again,

Steve





On Tue, Jan 5, 2021 at 12:21 PM Nate Graham <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=430862
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |BACKTRACE
>                  CC|                            |nate@kde.org
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #1 from Nate Graham <nate@kde.org> ---
> > #7  0x00007f2a6809c3e3 in ?? () from
> /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so
>
> Any chance you could install debug packages for kio-extras and attach
> another
> bracktrace? It's crashing somewhere in a thimbnailer but I can't tell where
> without a more complete backtrace.
>
> See
>
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
>
> --
> You are receiving this mail because:
> You reported the bug.

Created attachment 134587 [details]
kdeinit5-20210105-141313.kcrash.txt

Thanks! it's somewhere in thumbnail generation:

Thread 1 (Thread 0x7fba354034c0 (LWP 2044)):
[KCrash Handler]
#6  __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:262
#7  0x00007fba394103e3 in memcpy (__len=409600, __src=<optimized out>, __dest=0x7fba24130000) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
#8  ThumbnailProtocol::get (this=0x7ffe23390d40, url=...) at ./thumbnail/thumbnail.cpp:356
#9  0x00007fba34d6bfe6 in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#10 0x00007fba34d6c686 in KIO::SlaveBase::dispatchLoop() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#11 0x00007fba3940cb72 in kdemain (argc=<optimized out>, argv=0x55a4f73d6fa0) at ./thumbnail/thumbnail.cpp:138
#12 0x000055a4f6c9c77d in ?? ()
#13 0x000055a4f6c9d86a in ?? ()
#14 0x000055a4f6c9e25a in ?? ()
#15 0x000055a4f6c9912f in ?? ()
#16 0x00007fba384c50b3 in __libc_start_main (main=0x55a4f6c98750, argc=5, argv=0x7ffe23391548, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe23391538) at ../csu/libc-start.c:308
#17 0x000055a4f6c99d9e in ?? ()
[Inferior 1 (process 2044) detached]

Any chance you could upgrade to Kubuntu 20.10 and see if it still happens? 20.04 has software that's over a year old at this point.

Created attachment 134588 [details]
attachment-31587-0.html

Hi Nate,

When I upgrade to the next LTS, I generally do a fresh install.  I did one
in the fall for 20.04, and have installed a fair bit of other things since
then, so I'm reluctant to the fresh install.  Do you think I can reasonably
proceed with the upgrade approach without breaking too many things?

Thanks,

Steve


On Tue, Jan 5, 2021 at 2:38 PM Nate Graham <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=430862
>
> --- Comment #5 from Nate Graham <nate@kde.org> ---
> Any chance you could upgrade to Kubuntu 20.10 and see if it still happens?
> 20.04 has software that's over a year old at this point.
>
> --
> You are receiving this mail because:
> You reported the bug.

Kubuntu upgrades tend to be pretty stable so I imagine. But I can't promise anything of course. :)

Oh, and be sure to have a backup!

Created attachment 134593 [details]
attachment-3894-0.html

Ok, I'll brave the waters, but backup first.  I'll get back to you in a day
or so.

Bye for now :-)

Steve

On Tue, Jan 5, 2021 at 4:22 PM Nate Graham <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=430862
>
> --- Comment #7 from Nate Graham <nate@kde.org> ---
> Kubuntu upgrades tend to be pretty stable so I imagine. But I can't promise
> anything of course. :)
>
> Oh, and be sure to have a backup!
>
> --
> You are receiving this mail because:
> You reported the bug.

Created attachment 134644 [details]
1st of 2 reports generated after upgrading to 20.10

Upgrading from 20.04 to 20.10 did not resolve the issue.

Darn. Thanks for checking! And at least you have newer version of KDE software now. :)

Created attachment 134645 [details]
2nd of 2 reports after 20.10 upgrade

As noted in the original request, these crash reports are generated every time I boot.  Here is some other info on my configuration:

Thanks!

Operating System: Kubuntu 20.10
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2
Kernel Version: 5.8.0-34-lowlatency
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

*** Bug 434478 has been marked as a duplicate of this bug. ***

> #6  ThumbnailProtocol::get (this=0x7ffd6ede5860, url=...) at /usr/src/debug/kio-extras-20.12.3/thumbnail/thumbnail.cpp:315

line 315 is ThumbnailProtocol::pluginForMimeType(const QString& mimeType) {

I wonder what mimetype it's crashing on.

Kai, I bet this is your thumbnail.so crash. :)

*** Bug 434477 has been marked as a duplicate of this bug. ***

*** Bug 414553 has been marked as a duplicate of this bug. ***

*** Bug 420224 has been marked as a duplicate of this bug. ***

*** Bug 407393 has been marked as a duplicate of this bug. ***

*** Bug 427865 has been marked as a duplicate of this bug. ***

I'm curious why the other posts (specifically older) "has been marked as a duplicate of this bug"

I'd think the OG (first) post would be left alone and all of the others would've been considered duplicates.

If you have an orange and put it in a replicator, the new orange is the duplicate, not the original orange.

*** Bug 434157 has been marked as a duplicate of this bug. ***

(In reply to Nate Graham from comment #13)
> > #6  ThumbnailProtocol::get (this=0x7ffd6ede5860, url=...) at /usr/src/debug/kio-extras-20.12.3/thumbnail/thumbnail.cpp:315
> 
> line 315 is ThumbnailProtocol::pluginForMimeType(const QString& mimeType) {
> 
> I wonder what mimetype it's crashing on.
> 
> Kai, I bet this is your thumbnail.so crash. :)

Please note the kio-extras version. On that version, line 315 is memcpy(shmaddr, img.bits(), img.sizeInBytes());. On master, it's line 306.

I can try to compile kio and kio-extras from master, if needed.

Created attachment 136819 [details]
Latest kdeinit5 backtrace, for KDE Frameworks 5.80

Started happening after updating to KF 5.80. Attaching my trace, hope it helps.

*** Bug 434575 has been marked as a duplicate of this bug. ***

That duplicate bug (434575) has useful info, a user managed to isolate the exact commit which introduced this bug.

It's indeed line 306 
#4  __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:262
#5  0x00007f41efb783d9 in memcpy (__len=22016, __src=<optimized out>, __dest=0x7f41e089a000) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
#6  ThumbnailProtocol::get (this=0x7ffc25102aa0, url=...) at ./thumbnail/thumbnail.cpp:306
#7  0x00007f41eb2f7ab6 in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#8  0x00007f41eb2f8156 in KIO::SlaveBase::dispatchLoop() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#9  0x00007f41efb74cc2 in kdemain (argc=<optimized out>, argv=0x555bb92b4df0) at ./thumbnail/thumbnail.cpp:124

Created attachment 136823 [details]
fix_#430862.patch

Patch to fix this issue. I'll submit MR little later.
Because of default value for `cacheSize` is -1, we got size 1 there (width and height both 0): https://invent.kde.org/frameworks/kio/-/blob/v5.80.0/src/widgets/previewjob.cpp#L733.
And after that code creates shared memory segment of size 1.

A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/373

*** Bug 434664 has been marked as a duplicate of this bug. ***

*** Bug 434660 has been marked as a duplicate of this bug. ***

A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/376

*** Bug 434741 has been marked as a duplicate of this bug. ***

*** Bug 434758 has been marked as a duplicate of this bug. ***

Not sure if I'm hitting the same bug. Steps to reproduce:

1. Launch Plasma 5.21.3 in a Wayland session
2. Set ctrl+PrtSc to launch org.kde.Spectacle RectangularRegion(true)) in SystemSettings' Custom Shortcuts
3. Hit ctrl+PrtSc and select a region
4. A notification will pop up
5. Open the hamburger menu of the notification and select Copy (to clipboard)
6. kdeinit5 will segfault:

Application: kdeinit5 (kdeinit5), signal: Segmentation fault

[KCrash Handler]
#4  0x00007ffff71bdaa6 in __memmove_avx_unaligned_erms () from /lib64/libc.so.6
#5  0x00007ffff3a8dbdd in ThumbnailProtocol::get(QUrl const&) () from /usr/lib64/qt5/plugins/kf5/kio/thumbnail.so
#6  0x00007ffff3737386 in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5
#7  0x00007ffff372ec66 in KIO::SlaveBase::dispatchLoop() () from /lib64/libKF5KIOCore.so.5
#8  0x00007ffff3a8a44a in kdemain () from /usr/lib64/qt5/plugins/kf5/kio/thumbnail.so
#9  0x000055555555d5ab in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) ()
#10 0x000055555555ed4b in handle_launcher_request(int, char const*) [clone .constprop.0] ()
#11 0x000055555555f380 in handle_requests(int) ()
#12 0x000055555555a0e1 in main ()

It's the same bug. :)

*** Bug 434799 has been marked as a duplicate of this bug. ***

Git commit a68cb73c4e071ed24b18a95e11fbbbc8d59840b4 by Méven Car.
Committed on 27/03/2021 at 10:43.
Pushed by meven into branch 'master'.

PreviewJob: Initialize cachesSize with 0, only pass size > 0 to shmget, improve createThumbnail

M  +29   -19   src/widgets/previewjob.cpp

https://invent.kde.org/frameworks/kio/commit/a68cb73c4e071ed24b18a95e11fbbbc8d59840b4

*** Bug 435015 has been marked as a duplicate of this bug. ***

*** Bug 435151 has been marked as a duplicate of this bug. ***

*** Bug 435123 has been marked as a duplicate of this bug. ***

*** Bug 435123 has been marked as a duplicate of this bug. ***

*** Bug 435180 has been marked as a duplicate of this bug. ***

Just had the thumbnailer crash again in the same code path with git master.

:(

Méven, any ideas?

Confirmed crash here...even worse, usually leaves the panel (plasma) frozen for about 5 exasperating seconds.

Fresh Install Arch Linux (5.10.27-1-LTS)

I didn't reproduce with neon unstable/dev (in a VM) with dpr 1, 1.75 and 2. I did vary a little the spectacle's copy to clipboard settings as well.

With steps:
1. Launch Plasma 5.21.3 in a Wayland session
2. Set ctrl+PrtSc to launch org.kde.Spectacle RectangularRegion(true)) in SystemSettings' Custom Shortcuts (I used spectacle shortcuts settings)
3. Hit ctrl+PrtSc and select a region
4. A notification will pop up
5. Open the hamburger menu of the notification and select Copy (to clipboard)

I also tested replacing step 3 with running "spectacle -rb" (region capture, background)

Kai could you ensure you were running from master (maybe you forgot to reboot/logout ?) and spectacle as well, and could you send the stack trace you encountered if you still reproduce (and is different).

Kabus
> Confirmed crash here...

What versions of KIO are you using ?
The fix will be available in KDE Frameworks 5.81 but is currently only available in git / kde neon unstable.

I can confirm that applying patch from MR 376 helps.
Bug is gone after it.

*** Bug 435451 has been marked as a duplicate of this bug. ***

*** Bug 435422 has been marked as a duplicate of this bug. ***

*** Bug 435605 has been marked as a duplicate of this bug. ***

*** Bug 435566 has been marked as a duplicate of this bug. ***

*** Bug 435688 has been marked as a duplicate of this bug. ***

3 duplicates from people using 5.81; re-opening. I guess it's not fixed yet. :(

(In reply to Nate Graham from comment #52)
> 3 duplicates from people using 5.81; re-opening. I guess it's not fixed yet.
> :(

While I don't see kdeinit5 crashing anymore in journalctl, I still have the same issue described here https://bugs.kde.org/show_bug.cgi?id=435123 (I'm on 5.81.0)

Created attachment 137571 [details]
attachment-19689-0.html

Hi Nate,

I have not experienced the bug for some time now.  At first, I assumed it
was because I had removed some images which appeared as thumbnails from my
desktop, but I have other thumbnails there now and the problem is not
appearing.  I am very appreciative of the work that is being done and I
have faith you guys will sort it out eventually.

Thanks,

Stephen

On Tue, Apr 13, 2021 at 1:13 PM Nate Graham <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=430862
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>    Version Fixed In|5.81                        |
>          Resolution|WAITINGFORINFO              |---
>              Status|NEEDSINFO                   |CONFIRMED
>
> --- Comment #52 from Nate Graham <nate@kde.org> ---
> 3 duplicates from people using 5.81; re-opening. I guess it's not fixed
> yet. :(
>
> --
> You are receiving this mail because:
> You reported the bug.

I don't know if this helps however, like everyone else on the planet I have a key marked in two rows "prt sc" and "sysrq" so I've been using shift "prt sc" to take a screenshot.

This causes kinit to crash 

I've just discovered that shift is not needed and then kinit doesn't crash.

as reported in *[Bug 435566] kdeinit5 crash* it's still happening after the latest updates 

the PrtSCr problem I never had and use it often often

also restart or reboot of the PC is not necessary since kdeinit5 restarts itself

*** Bug 435750 has been marked as a duplicate of this bug. ***

Git commit 5d81c41eb704a85fc92a3e1e3c3c9dbd4c54cfe1 by Kai Uwe Broulik.
Committed on 15/04/2021 at 18:43.
Pushed by broulik into branch 'master'.

[Notifications] Don't generate previews of zero size

A `QSize(0,0)` is still valid... Fixes sometimes preview not showing
and other problems with the thumbnailer.

M  +1    -1    applets/notifications/thumbnailer.cpp

https://invent.kde.org/plasma/plasma-workspace/commit/5d81c41eb704a85fc92a3e1e3c3c9dbd4c54cfe1

Git commit 18273cd8fae51cf66546f5e4ade51f527ab80e50 by Kai Uwe Broulik.
Committed on 15/04/2021 at 19:11.
Pushed by broulik into branch 'Plasma/5.21'.

[Notifications] Don't generate previews of zero size

A `QSize(0,0)` is still valid... Fixes sometimes preview not showing
and other problems with the thumbnailer.


(cherry picked from commit 5d81c41eb704a85fc92a3e1e3c3c9dbd4c54cfe1)

M  +1    -1    applets/notifications/thumbnailer.cpp

https://invent.kde.org/plasma/plasma-workspace/commit/18273cd8fae51cf66546f5e4ade51f527ab80e50

Git commit 57a4845c4d761a1372f3b2ee48e137e8ca2e9c50 by Kai Uwe Broulik.
Committed on 15/04/2021 at 19:12.
Pushed by broulik into branch 'Plasma/5.18'.

[Notifications] Don't generate previews of zero size

A `QSize(0,0)` is still valid... Fixes sometimes preview not showing
and other problems with the thumbnailer.


(cherry picked from commit 5d81c41eb704a85fc92a3e1e3c3c9dbd4c54cfe1)

M  +1    -1    applets/notifications/thumbnailer.cpp

https://invent.kde.org/plasma/plasma-workspace/commit/57a4845c4d761a1372f3b2ee48e137e8ca2e9c50

*** Bug 436000 has been marked as a duplicate of this bug. ***

*** Bug 436025 has been marked as a duplicate of this bug. ***

I also have this problem, I'm attaching the error logs

Created attachment 137897 [details]
error logs after crash

Delete folder ~.local/share/baloo/ solved this problem.

*** Bug 436116 has been marked as a duplicate of this bug. ***

*** Bug 436263 has been marked as a duplicate of this bug. ***

(In reply to Allexus J from comment #65)
> Delete folder ~.local/share/baloo/ solved this problem.

This is probably random, not a workaround.

I can't reproduce this bug.
For dolphin or the file open dialog, I would need to have a file that triggers it or precise steps.

Did you reboot or logout since upgrading ?

hello,
I think, i have the same bug.
kdeinit5 crashes very often since a few days when I save a file from firefox, okular or from another application...

I got this message:

Application: kdeinit5 (kdeinit5), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f715a91fcc0 (LWP 31919))]
[KCrash Handler]
#6  __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:269
#7  0x00007f71589b6f81 in memcpy (__len=46080, __src=<optimized out>, __dest=0x7f7148624000) at /usr/include/bits/string_fortified.h:29
#8  ThumbnailProtocol::get (this=0x7ffc679ae0a0, url=...) at /usr/src/debug/kio-extras5-21.04.0-1.1.x86_64/thumbnail/thumbnail.cpp:301
#9  0x00007f7158a42ee6 in KIO::SlaveBase::dispatch (this=0x7ffc679ae0a0, command=67, data=...) at /usr/src/debug/kio-5.81.0-1.2.x86_64/src/core/slavebase.cpp:1215
#10 0x00007f7158a3a8c6 in KIO::SlaveBase::dispatchLoop (this=0x7ffc679ae0a0) at /usr/src/debug/kio-5.81.0-1.2.x86_64/src/core/slavebase.cpp:336
#11 0x00007f71589b3786 in kdemain (argc=<optimized out>, argv=0x5636a63e0d40) at /usr/src/debug/kio-extras5-21.04.0-1.1.x86_64/thumbnail/thumbnail.cpp:124
#12 0x00005636a477cc07 in launch (argc=argc@entry=4, _name=_name@entry=0x5636a63a1f38 "/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so", args=<optimized out>, args@entry=0x5636a63a1f64 "thumbnail", cwd=cwd@entry=0x0, envc=envc@entry=0, envs=envs@entry=0x5636a63a1fdb "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x5636a477f175 "0") at /usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:692
#13 0x00005636a477e3a8 in handle_launcher_request (sock=8, who=<optimized out>) at /usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:1130
#14 0x00005636a477ea36 in handle_requests (waitForPid=waitForPid@entry=0) at /usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:1323
#15 0x00005636a4779623 in main (argc=3, argv=<optimized out>) at /usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:1761
[Inferior 1 (process 31919) detached]

My OS and hardware:
Operating System: openSUSE Tumbleweed 20210427
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
Kernel Version: 5.11.16-1-default
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
Memory: 7.5 Gio of RAM
Graphics Processor: Mesa Intel® Xe Graphics

(In reply to Allexus J from comment #65)
> Delete folder ~.local/share/baloo/ solved this problem.

As @Méven stated above, I confirm this does NOT resolve anything.

Besides, my issue was previously marked as duplicate to this issue, but I reported KDialog's Segmentation fault as well, which this bug report doesn't mention: https://bugs.kde.org/show_bug.cgi?id=436025

I hope it was intentional and the same patch should resolve both: KDialog and Kde5init issue.

I haven't seen this bug in a couple of weeks, so I believe it's been fixed in kio-extras 20.12.2.

People sending new reports should ensure they're running at least this release.

I am running kio-extras 21.04.0 on OpenSUSE TW and I still have the problem, so I believe it has not been fixed. I have a few directories upon which it reproducibly crashes when I navigate to the directory in the fileselector from Qutebrowser.

These directories have in common that they contain subdirectories with image files in them. However, if I begin individually removing files and subdirectories, it's no longer reproducible - e.g. I have a configuration where it crashes, I remove a subdirectory and it no longer crashes, I copy the subdirectory in again and it still doesn't crash. I don't know enough about how the thumbnailer works to come up with a reliable strategy to produce a minimal configuration.

I can send a zip file of such a directory, however as it's rather large and contains sensitive files I would rather not post it online.

I can't reproduce the issue on my side (kio-extras 21.04.0-1, manjaro testing) anymore - i only encountered it when taking a screenshot that shows the thumbnail in a notification though. Are you sure your issues are related to this bug?

(In reply to Bernie Innocenti from comment #71)
> I haven't seen this bug in a couple of weeks, so I believe it's been fixed
> in kio-extras 20.12.2.
> 
> People sending new reports should ensure they're running at least this
> release.

No, I have always this bug with kio-extras5-21.04.0-1.1
See message #69

Created attachment 138028 [details]
log kdeinit5 after crash

With Okular, I browse the folders to save a PDF file and waiting a few seconds kdeinit5 crashes

Created attachment 138029 [details]
command journalctl

journactl --user command returns this log.

My use case now not only works but now has an added feature 

shift PrtScr no longer causes kde5init to crash but automatically saves the screenshot to ~/home/Pictures

Strangely I've not been hit by this trouble since months and weeks.
Suddendly yesterday I've open-up kdenlive and got numerous kdeinit5 crashes until I close again kdenlive.

Trace from the crash indicates

Application: kdeinit5 (kdeinit5), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fc41a08ccc0 (LWP 1416))]
[KCrash Handler]
#6  __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:269
#7  0x00007fc418123f81 in memcpy (__len=36864, __src=<optimized out>, __dest=0x7fc401775000) at /usr/include/bits/string_fortified.h:29
#8  ThumbnailProtocol::get(QUrl const&) (this=0x7ffc72098970, url=...) at /usr/src/debug/kio-extras5-21.04.0-1.1.x86_64/thumbnail/thumbnail.cpp:301
#9  0x00007fc4181afee6 in KIO::SlaveBase::dispatch(int, QByteArray const&) (this=0x7ffc72098970, command=67, data=...) at /usr/src/debug/kio-5.81.0-1.2.x86_64/src/core/slavebase.cpp:1215
#10 0x00007fc4181a78c6 in KIO::SlaveBase::dispatchLoop() (this=0x7ffc72098970) at /usr/src/debug/kio-5.81.0-1.2.x86_64/src/core/slavebase.cpp:336
#11 0x00007fc418120786 in kdemain(int, char**) (argc=<optimized out>, argv=0x55f2035fcf90) at /usr/src/debug/kio-extras5-21.04.0-1.1.x86_64/thumbnail/thumbnail.cpp:124
#12 0x000055f201eb0c07 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) (argc=argc@entry=4, _name=_name@entry=0x55f2035f0958 "/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so", args=<optimized out>, args@entry=0x55f2035f0984 "thumbnail", cwd=cwd@entry=0x0, envc=envc@entry=0, envs=envs@entry=0x55f2035f09fe "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x55f201eb3175 "0") at /usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:692
#13 0x000055f201eb23a8 in handle_launcher_request(int, char const*) (sock=8, who=<optimized out>) at /usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:1130
#14 0x000055f201eb2a36 in handle_requests(pid_t) (waitForPid=waitForPid@entry=0) at /usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:1323
#15 0x000055f201ead623 in main(int, char**) (argc=3, argv=<optimized out>) at /usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:1761
[Inferior 1 (process 1416) detached]

On user side journal contain a few informations

mai 04 08:39:25 qt-kt kdeinit5[1022]: Qt: Session management error: networkIdsList argument is NULL
mai 04 08:39:37 qt-kt kdeinit5[1012]: [107B blob data]
mai 04 08:39:37 qt-kt kdeinit5[1012]: kf.kio.slaves.file: copy() QUrl("file:///tmp/drkonqi.MXFOqu") to QUrl("file:///ioda/home/bruno/oc/personnel/Crashes/kdeinit5-20210503-211933.kcrash") mode>
mai 04 08:39:37 qt-kt kdeinit5[1012]: kf.kio.slaves.file: the file doesn't have any xattr
mai 04 08:40:00 qt-kt kdeinit5[1284]: Qt: Session management error: networkIdsList argument is NULL
mai 04 08:40:01 qt-kt kdeinit5[1284]: Using  18432  steps
mai 04 08:40:01 qt-kt drkonqi[1316]: Qt: Session management error: networkIdsList argument is NULL
mai 04 08:40:01 qt-kt kdeinit5[1315]: Qt: Session management error: networkIdsList argument is NULL
mai 04 08:40:01 qt-kt kded5[2564]: Registering ":1.505/StatusNotifierItem" to system tray
mai 04 08:40:01 qt-kt plasmashell[2622]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for pro>
mai 04 08:40:01 qt-kt kdeinit5[1315]: Using  18432  steps
mai 04 08:40:01 qt-kt kdeinit5[1315]: Using  18432  steps
mai 04 08:40:01 qt-kt kdeinit5[1315]: Using  18432  steps
mai 04 08:40:01 qt-kt drkonqi[1355]: Qt: Session management error: networkIdsList argument is NULL
mai 04 08:40:01 qt-kt kdeinit5[1354]: Qt: Session management error: networkIdsList argument is NULL
mai 04 08:40:01 qt-kt kded5[2564]: Registering ":1.508/StatusNotifierItem" to system tray
mai 04 08:40:02 qt-kt kdeinit5[1354]: Using  18432  steps
mai 04 08:40:02 qt-kt drkonqi[1386]: Qt: Session management error: networkIdsList argument is NULL
mai 04 08:40:02 qt-kt kded5[2564]: Registering ":1.510/StatusNotifierItem" to system tray

I'm using systemd-networkd which explain the network null list.



My system is quite up to date being openSUSE Tumbleweed

Linux 5.12.0-1-default x86_64 GNU/Linux
nvidia: 460.73.01
Qt: 5.15.2
KDE Frameworks: 5.81.0
Plasma: 5.21.4
kmail2 5.17.0 (21.04.0)
kinit 5.81.0

The biggest changes occuring in Tumbleweed last week was the introduction of LLVM12 and Boost 1.76

to add information to my previous comment.
during kdenlive there's those process who crash
bruno     6370 24.4  0.5 2201200 343504 ?      Tl   17:14   0:07 thumbnail.so [kdeinit5] thumbnail local:/run/user/1502/klaunchergpuFVJ.1.slave-socket local:/run/user/1502/kdenliveHHBSMn.33.slave-socket

A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/436

I’ve noticed that deleting folders with images causes the thumbnailer to crash as well, happens with both dolphin and gwenview.

*** Bug 436651 has been marked as a duplicate of this bug. ***

Git commit bc02b2528c97eab0961b3ad608a4914d3ce4b46c by Fabian Vogt.
Committed on 04/05/2021 at 20:25.
Pushed by fvogt into branch 'master'.

PreviewJob: Create a larger SHM when necessary

It's possible that during the lifetime of a PreviewJob thumbnails with
different sizes are created. The SHM was created to match the size of the first
(non-empty) thumbnail, so any larger ones after that would reuse the SHM with
insufficient size.

M  +9    -5    src/widgets/previewjob.cpp

https://invent.kde.org/frameworks/kio/commit/bc02b2528c97eab0961b3ad608a4914d3ce4b46c

*** Bug 436747 has been marked as a duplicate of this bug. ***

*** Bug 421449 has been marked as a duplicate of this bug. ***

*** Bug 414106 has been marked as a duplicate of this bug. ***

*** Bug 436829 has been marked as a duplicate of this bug. ***

Hi Guys,

Probably related.
I experiment continuous crashes in kdeinit5 opening simple text files with kate. The crashes happen when (and only when) some particular pdf are in my home directory (for example this one: https://arxiv.org/pdf/2010.08895). Other pdf does not causes the crash. Also, Kwrite does not cause the crash, and if I move the "critical pdf" under a subdir of my home, even kate does not causes the crash anymore.

I am on Manjaro stable, with latest updates (plasma 5.21.4, kde framework 5.81.0, kde apps 21.04.0)

Hoping this help.
Many thanks for your work on this wonderful DE.

Flavio


Application: kdeinit5 (kdeinit5), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f97481d1e08 in __memmove_sse2_unaligned_erms () from /usr/lib/libc.so.6
#5  0x00007f9749175482 in ?? () from /usr/lib/qt/plugins/kf5/kio/thumbnail.so
#6  0x00007f97448db6df in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /usr/lib/libKF5KIOCore.so.5
#7  0x00007f97448dc006 in KIO::SlaveBase::dispatchLoop() () from /usr/lib/libKF5KIOCore.so.5
#8  0x00007f9749172ff6 in kdemain () from /usr/lib/qt/plugins/kf5/kio/thumbnail.so
#9  0x000055d5194cf5bd in ?? ()
#10 0x000055d5194d0a59 in ?? ()
#11 0x000055d5194d1237 in ?? ()
#12 0x000055d5194ccb54 in ?? ()
#13 0x00007f9748150b25 in __libc_start_main () from /usr/lib/libc.so.6
#14 0x000055d5194cd6be in ?? ()
[Inferior 1 (process 85746) detached]

You're welcome.

You're not using either of the versions where this is fixed (listed in the "Version fixed in" field); closing again.

I simply want to thank you all, I've never participated in a bug resolution, but I've been a faithful Linux user since early Slackware days.

Keep up the great work and glad it was fixed.

Stephen

(In reply to vindicator from comment #19)
> I'm curious why the other posts (specifically older) "has been marked as a
> duplicate of this bug"

Bug is resolved/fixed (and my curiosity upon seeing it referenced in the git logs is why I'm here) but I don't see that this question was ever answered.  So here's my (explicitly unofficial as I'm just another bugfiler, here and elsewhere) attempt at an answer...

There are (at least) two general bug-duplicate policies that can be employed by devs choosing which bugs to mark as duplicates.  Some products or bug installations use one, some the other, and others may default to the first but choose the second given a strong enough reason on an individual bug basis.

1) Chronological order policy.  Newer bugs are always duplicates of the oldest, original bug.

This could be argued to be the most "correct", but often has the practical issue described/solved by the more pragmatic policy below.  Still it's the most reasonable default in the absence of a solid reason to override and is thus favored where such priority-overrides are less common.  In my experience distros commonly have this policy, probably because of their function as accumulators/packagers of software from various upstream sources.

2) Pragmatic "most useful information" policy.  The "original" bug is defined as the one with the most useful information already posted to it at the time of the duplicate marking, regardless of which one was actually filed first.

In my experience this policy is more common on upstream original software source providers, I'd suggest due to reasoning below, but extended to the more general case (that is, not always will the most informative bug-filing be the one with the commit-ID attached).

Especially where (semi-)automated crash-report filing is used (as it is with some kde components and apps, with the user's consent of course), the often-automated chronologically first bugs may have very little additional information, while a bug filed later, sometimes only because its author took the time to collect and add additional information, has more practically useful information in terms of actually fixing the bug.

A recent bug I filed where earlier bugs were marked duplicates of mine is a good example. For kde I run live-git versions built myself (using the gentoo/kde project's build scripts so it's pretty automated) and I normally update once or twice a week.  I found a regression that wasn't there before my last update, so I checked the git logs to see what changed and then bisected the problem down to an individual commit.  When I filed the bug it had the git commit ID that triggered the problem in the subject line.  There was other information in the bug as well but honestly the commit ID was probably the most helpful and the reason earlier bugs were marked dupes of mine.

But bisecting to an individual commit is a non-trivial amount of work and takes time.  By the time I did that there were other bugs reporting the problem.  But despite not being first, my bug was (presumably) considered to have more useful info attached, as I said, likely the commit ID alone was enough, so other bugs, including some filed earlier, were declared duplicates of mine.

(In reply to Flavio Cappelli from comment #88)
> Hi Guys,
> 
Hey Flavio,

> Probably related.

If you are not sure this sounds like a different bug, please open new bugs laser focused on your issue when you don't see duplicates with very close symptoms.
Triagers and devs will mark them as duplicate if needed, but reporters can't do that and bugs reported as comments will very unlikely be fixed.
See https://community.kde.org/Get_Involved/Issue_Reporting#Step_6:_File_a_high-quality_Bugzilla_ticket

> I experiment continuous crashes in kdeinit5 opening simple text files with
> kate. The crashes happen when (and only when) some particular pdf are in my
> home directory (for example this one: https://arxiv.org/pdf/2010.08895).

Do you mean in the Open/File dialog with previews enabled ?

> Other pdf does not causes the crash. Also, Kwrite does not cause the crash,
> and if I move the "critical pdf" under a subdir of my home, even kate does
> not causes the crash anymore.
> 
> I am on Manjaro stable, with latest updates (plasma 5.21.4, kde framework
> 5.81.0, kde apps 21.04.0)

A crash without backtrace is really hard/impossible to fix.

Seems it could be this bug though. If you don't experience it with KDE Frameworks 5.82, it is not worth reporting/investigating anymore.

> I experiment continuous crashes in kdeinit5 opening simple text files with kate. The crashes happen when (and only when) some particular pdf are > in my home directory (for example this one: https://arxiv.org/pdf/2010.08895). Other pdf does not causes the crash. Also, Kwrite does not cause
> the crash, and if I move the "critical pdf" under a subdir of my home, even kate does not causes the crash anymore.

Please report that 
(In reply to Duncan from comment #91)
> (In reply to vindicator from comment #19)
> > I'm curious why the other posts (specifically older) "has been marked as a
> > duplicate of this bug"
> 
> Bug is resolved/fixed (and my curiosity upon seeing it referenced in the git
> logs is why I'm here) but I don't see that this question was ever answered. 
> So here's my (explicitly unofficial as I'm just another bugfiler, here and
> elsewhere) attempt at an answer...
> 
> There are (at least) two general bug-duplicate policies that can be employed
> by devs choosing which bugs to mark as duplicates.  Some products or bug
> installations use one, some the other, and others may default to the first
> but choose the second given a strong enough reason on an individual bug
> basis.
> 
> 1) Chronological order policy.  Newer bugs are always duplicates of the
> oldest, original bug.
> 
> This could be argued to be the most "correct", but often has the practical
> issue described/solved by the more pragmatic policy below.  Still it's the
> most reasonable default in the absence of a solid reason to override and is
> thus favored where such priority-overrides are less common.  In my
> experience distros commonly have this policy, probably because of their
> function as accumulators/packagers of software from various upstream sources.
> 
> 2) Pragmatic "most useful information" policy.  The "original" bug is
> defined as the one with the most useful information already posted to it at
> the time of the duplicate marking, regardless of which one was actually
> filed first.
> 
> In my experience this policy is more common on upstream original software
> source providers, I'd suggest due to reasoning below, but extended to the
> more general case (that is, not always will the most informative bug-filing
> be the one with the commit-ID attached).
> 
> Especially where (semi-)automated crash-report filing is used (as it is with
> some kde components and apps, with the user's consent of course), the
> often-automated chronologically first bugs may have very little additional
> information, while a bug filed later, sometimes only because its author took
> the time to collect and add additional information, has more practically
> useful information in terms of actually fixing the bug.
> 
> A recent bug I filed where earlier bugs were marked duplicates of mine is a
> good example. For kde I run live-git versions built myself (using the
> gentoo/kde project's build scripts so it's pretty automated) and I normally
> update once or twice a week.  I found a regression that wasn't there before
> my last update, so I checked the git logs to see what changed and then
> bisected the problem down to an individual commit.  When I filed the bug it
> had the git commit ID that triggered the problem in the subject line.  There
> was other information in the bug as well but honestly the commit ID was
> probably the most helpful and the reason earlier bugs were marked dupes of
> mine.
> 
> But bisecting to an individual commit is a non-trivial amount of work and
> takes time.  By the time I did that there were other bugs reporting the
> problem.  But despite not being first, my bug was (presumably) considered to
> have more useful info attached, as I said, likely the commit ID alone was
> enough, so other bugs, including some filed earlier, were declared
> duplicates of mine.

Bug triaging is not a science and both triagers and reporters can make mistakes creating duplicates.

Sometimes we peek earlier, sometimes best quality, sometimes just popularity or naming of the bug, there is no definitive rule, expect we want to limit the number of bugs, because a cacophony of bugs makes it harder to fix the bug, and harder for the bug reporters to see their bugs fixed.

When we mark something as duplicate, triagers can copy over some data, and if he doesn't original reporters can copy or highlight it in the new main bug, I would encourage you to if you found value in it.

You did some great job bisecting the origin of the bug, still the bug fix wasn't evident based on just that.
Here the best stacktrace were sufficient to see approximately where the crash happened, and this was not sufficient to make the crash fix evident.
With some effort, Fabian found it in the end.

>> I experiment continuous crashes in kdeinit5 opening simple text files with
>> kate. The crashes happen when (and only when) some particular pdf are in my
>> home directory (for example this one: https://arxiv.org/pdf/2010.08895).
>
>Do you mean in the Open/File dialog with previews enabled ?

No, I mean in dolphin, clicking with the left mouse button on a simple text file (I have kate as default text editor configured). Anyway, if I click with the right mouse button on the same text file, and choose "open with" -> "kwrite", kdeinit5 does not crash.


>A crash without backtrace is really hard/impossible to fix.

I know that, but unfortunately having debug symbols on Manjaro is not an easy task, expecially for a big software like KDE (see https://forum.manjaro.org/t/debug-symbols-on-manjaro/61157).


>Seems it could be this bug though. If you don't experience it with KDE >Frameworks 5.82, it is not worth reporting/investigating anymore.

Of course. I will wait for framework 5.82 to arrive in Manjaro stable, and if the issue will still occur I will open a new bug report and try to provide a better backtrace.

Regards

Flavio

*** Bug 437279 has been marked as a duplicate of this bug. ***

Git commit 112b67ae7895bdc4f32d851c09a4d6baecbb6666 by Nate Graham, on behalf of Fabian Vogt.
Committed on 29/05/2021 at 22:13.
Pushed by ngraham into branch 'master'.

thumbnail: Check shm size before writing to it

The SHM is created by the application, which might've done a different size
calculation. Verify that the data fits instead of writing past the end and
crashing.

M  +5    -4    thumbnail/thumbnail.cpp

https://invent.kde.org/network/kio-extras/commit/112b67ae7895bdc4f32d851c09a4d6baecbb6666

Git commit a288a7ba4283b2102a4602aa105072f33bc25645 by Fabian Vogt.
Committed on 30/05/2021 at 09:20.
Pushed by fvogt into branch 'release/21.04'.

thumbnail: Check shm size before writing to it

The SHM is created by the application, which might've done a different size
calculation. Verify that the data fits instead of writing past the end and
crashing.


(cherry picked from commit 112b67ae7895bdc4f32d851c09a4d6baecbb6666)

M  +5    -4    thumbnail/thumbnail.cpp

https://invent.kde.org/network/kio-extras/commit/a288a7ba4283b2102a4602aa105072f33bc25645

*** Bug 437815 has been marked as a duplicate of this bug. ***

The problem persist in kubuntu 21.10 

Operating System: Kubuntu 21.04
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.0-25-generic
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-4430 CPU @ 3.00GHz
Memory: 15,4 GiB of RAM
Graphics Processor: GeForce GT 610/PCIe/SSE2

After take a Window-Screenshot by keyboard shortcuts Meta+PrintScrn the thumbnail has problem to appear then DrKonki say 
kdeinit5 closed unexpectedly


generated crash information
Application: kdeinit5 (kdeinit5), signal: Segmentation fault

[KCrash Handler]
#4  __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:269
#5  0x00007f7cf3d01c99 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so
#6  0x00007f7cef1789de in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#7  0x00007f7cef1792c6 in KIO::SlaveBase::dispatchLoop() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#8  0x00007f7cf3cff961 in kdemain () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so
#9  0x0000564864d30a5e in ?? ()
#10 0x0000564864d31e51 in ?? ()
#11 0x0000564864d325fc in ?? ()
#12 0x0000564864d2e0ef in ?? ()
#13 0x00007f7cf2cdc565 in __libc_start_main (main=0x564864d2d750, argc=1, argv=0x7ffd9f45df88, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd9f45df78) at ../csu/libc-start.c:332
#14 0x0000564864d2ebee in ?? ()
[Inferior 1 (process 28301) detached]

As the "Version Fixed Un" field says, this is fixed in Frameworks 5.82 and/or Plasma 5.22; you appear to have neither.

Thanks I am learning, very appreciate your comments and time.

No problem. :)

*** Bug 441853 has been marked as a duplicate of this bug. ***

(In reply to Nate Graham from comment #99)
> As the "Version Fixed Un" field says, this is fixed in Frameworks 5.82
> and/or Plasma 5.22; you appear to have neither.

Hello.  Is there any patch I can apply or package I can update w/o upgrading my whole plasma/kde framework?

(In reply to Daniel Santos from comment #103)
> Hello.  Is there any patch I can apply or package I can update w/o upgrading
> my whole plasma/kde framework?

No, sorry.

*** Bug 443405 has been marked as a duplicate of this bug. ***

(In reply to Bharadwaj Raju from comment #104)
> No, sorry.

Thanks.  Gentoo *did* let me upgrade to kde-apps/kio-extras-21.04.3-r2, but I will presume any failures are unsupported until I upgrade my whole framework.

Current stable Gentoo packages:
KDE Frameworks 5.85
KDE Plasma 5.22.5
KDE Gear 21.04.3

kde-apps/kio-extras-21.04.3-r2 is part of the latter and not involved in this bug.

*** Bug 439034 has been marked as a duplicate of this bug. ***