Bug 449683

Summary:	Segmentation Fault on Wayland
Product:	[Unmaintained] lattedock	Reporter:	ryu.ketsueki
Component:	application	Assignee:	Michail Vourlakos <mvourlakos>
Status:	RESOLVED UPSTREAM
Severity:	crash
Priority:	NOR
Version First Reported In:	git (master)
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description ryu.ketsueki 2022-02-06 04:38:21 UTC

SUMMARY
Sometimes, when just using Latte normally, such as when entering edit mode (not even changing anything, just entering edit mode), Latte will simply close with a Segmentation Fault (core dumped) reported. I tried getting a backtrace with gdb since DrKonqi didn't get launched or anything but it says there is no stack, so I don't know how to make this more useful. Note this also only happens on Wayland. Never got this issue under X11.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220204
KDE Plasma Version: 5.23.90
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.4-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-7020U CPU @ 2.30GHz
Memory: 11.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620

Comment 1 Michail Vourlakos 2022-02-12 11:53:41 UTC

https://userbase.kde.org/LatteDock/HowToReportCrashes

Comment 2 ryu.ketsueki 2022-02-12 19:38:42 UTC

(In reply to Michail Vourlakos from comment #1)
> https://userbase.kde.org/LatteDock/HowToReportCrashes

The exact same thing appeared for me on ddd. No Stack

Comment 3 ryu.ketsueki 2022-02-17 03:40:51 UTC

I used coredumpctl as suggested for debugging another bug report I submitted but for a third party kwin effect, hoping it would work and I managed to get a backtrace from gdb. The backtrace was gigantic, though, pointing to memory addresses. What I could make out, are the following lines

#1  qGetPtrHelper<QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> > >(QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >&) (ptr=<optimized out>)
    at ../../include/QtCore/../../src/corelib/global/qglobal.h:1143
#2  QApplication::d_func() (this=<optimized out>) at kernel/qapplication.h:217
#3  QApplication::notify(QObject*, QEvent*)
    (this=0x7ffd909f10e0, receiver=0x55d87227d8d0, e=0x7ffd901f3210)
    at kernel/qapplication.cpp:2859

Comment 4 Michail Vourlakos 2022-02-18 17:12:54 UTC

(In reply to ryu.ketsueki from comment #3)
> I used coredumpctl as suggested for debugging another bug report I submitted
> but for a third party kwin effect, hoping it would work and I managed to get
> a backtrace from gdb. The backtrace was gigantic, though, pointing to memory
> addresses. What I could make out, are the following lines
> 
> #1  qGetPtrHelper<QScopedPointer<QObjectData,
> QScopedPointerDeleter<QObjectData> > >(QScopedPointer<QObjectData,
> QScopedPointerDeleter<QObjectData> >&) (ptr=<optimized out>)
>     at ../../include/QtCore/../../src/corelib/global/qglobal.h:1143
> #2  QApplication::d_func() (this=<optimized out>) at
> kernel/qapplication.h:217
> #3  QApplication::notify(QObject*, QEvent*)
>     (this=0x7ffd909f10e0, receiver=0x55d87227d8d0, e=0x7ffd901f3210)
>     at kernel/qapplication.cpp:2859

out of latte responsibility...