Bug 494723 - plasmashell crash while writing a new email in Thunderbird
Summary: plasmashell crash while writing a new email in Thunderbird
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 5.27.5
Platform: Debian stable Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-10-14 08:40 UTC by stefan
Modified: 2024-11-14 17:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (128.35 KB, text/plain)
2024-10-14 08:40 UTC, stefan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description stefan 2024-10-14 08:40:20 UTC
Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-26-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
I had Firefox and Thunderbird open in the background while writing a new email in Thunderbird. The taskbar disappeared for a few seconds, it reappeared and the 'application crashed' window popped up. This is the second time this issue occurs. During the first time it happened I was writing an email in Thunderbird as well.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#4  0x00007fc4191943f1 in QSGNode::markDirty(QFlags<QSGNode::DirtyStateBit>) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x00007fc418d40455 in QAbstractAnimationJob::setCurrentTime(int) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x00007fc418d40629 in QQmlAnimationTimer::updateAnimationsTime(long long) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x00007fc4174b106b in QUnifiedTimer::updateAnimationTimers(long long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fc4174b2d6c in QAnimationDriver::advanceAnimation(long long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5


The reporter indicates this bug may be a duplicate of or related to bug 493660.

Reported using DrKonqi
Comment 1 stefan 2024-10-14 08:40:21 UTC
Created attachment 174794 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 TraceyC 2024-11-13 20:13:39 UTC
Searchable backtrace

Thread 43 (Thread 0x7fc2c63fd6c0 (LWP 5939)):
[KCrash Handler]
#4  0x00007fc4191943f1 in QSGNode::markDirty(QFlags<QSGNode::DirtyStateBit>) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x00007fc418d40455 in QAbstractAnimationJob::setCurrentTime(int) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x00007fc418d40629 in QQmlAnimationTimer::updateAnimationsTime(long long) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x00007fc4174b106b in QUnifiedTimer::updateAnimationTimers(long long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fc4174b2d6c in QAnimationDriver::advanceAnimation(long long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007fc4192098d4 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x00007fc41920a46f in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x00007fc4174cbd83 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007fc4172a8144 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#13 0x00007fc4173287dc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Comment 3 TraceyC 2024-11-13 20:16:02 UTC
Thank you for the bug report! I'm not able to reproduce this on git-master or Plasma 6.2.3. Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong:

#9  0x00007fc4192098d4 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5

Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
Comment 4 TraceyC 2024-11-14 17:45:11 UTC
I have found out that Debian doesn't provide any packages with debugging symbols for QT5 libraries. Unfortunately, the backtrace isn't complete enough for it to be actionable for us without that.

Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting). The crash appears to be in QT5, and QT has mostly moved development to QT6. It's possible that the bug exists only in Debian at this point. 

Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream.

Thanks for understanding.