Bug 480248

Summary:	Plasma shell crashed with signal 11 (segfault)
Product:	[Plasma] plasmashell	Reporter:	Mark Rooks <rooksy>
Component:	generic-crash	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	kde, nate
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	5.27.10
Target Milestone:	1.0
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Mark Rooks 2024-01-24 00:22:25 UTC

Application: plasmashell (5.27.10)

Qt Version: 5.15.12
Frameworks Version: 5.114.0
Operating System: Linux 6.6.11-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.10 [CoredumpBackend]

-- Information about the crash:
I had just imported 3 new VPN connections. I was (quickly) jumping between one connection to another, testing particular functions, around curl and openssl on each.
I have done the same behaviour on three seoarate occassions over the last two days and only today, after some new patches were applied, did this start to happen.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#6  0x00007f70209f04ea in VDMModelDelegateDataType::notify (this=<optimized out>, items=..., index=<optimized out>, count=<optimized out>, roles=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qmlmodels/qqmladaptormodel.cpp:175
#7  0x00007f70209f929b in QQmlAdaptorModel::notify (roles=..., count=14, index=0, items=..., this=0x55824bbd0310) at ../../include/QtQmlModels/5.15.12/QtQmlModels/private/../../../../../../src/qmlmodels/qqmladaptormodel_p.h:163
#8  QQmlDelegateModel::_q_itemsChanged (this=this@entry=0x55824bbd01d0, index=index@entry=0, count=14, roles=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qmlmodels/qqmldelegatemodel.cpp:1499
#9  0x00007f7020a03cf9 in QQmlDelegateModel::_q_layoutChanged (this=0x55824bbd01d0, parents=..., hint=<optimized out>) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qmlmodels/qqmldelegatemodel.cpp:2057
#10 0x00007f7020a04643 in QQmlDelegateModel::qt_metacall (this=0x55824bbd01d0, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7ffc6c258b60) at .moc/moc_qqmldelegatemodel_p.cpp:371


The reporter indicates this bug may be a duplicate of or related to bug 407304, bug 407984, bug 408030, bug 409305, bug 406459, bug 410435, bug 410901, bug 411610, bug 412449, bug 411639, bug 412198, bug 412531, bug 412938, bug 415451, bug 418687, bug 426126, bug 427570, bug 431718, bug 433067, bug 436765, bug 468183, bug 471420, bug 477403, bug 479882.

Reported using DrKonqi

Comment 1 Mark Rooks 2024-01-24 00:22:27 UTC

Created attachment 165173 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 Nate Graham 2024-02-15 19:10:35 UTC

> after some new patches were applied
Can you clarify what this means? What kind of patches, and who applied them, and what to they do?

Comment 3 Bug Janitor Service 2024-03-01 03:46:52 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Mark Rooks 2024-03-04 02:34:03 UTC

Tumbleweed is an "evergeeen" distro. Releases come every other day or daily. What "after some new patches were applied" means, is that on the date that I raised this bug, I applied some updates to the system using:

zypper dup, or zypper up, 

depending on whether it was just updates to rpms or also an update to the distro version.

You can see the changelogs for yourself.  I was just raising it bc it was an easy thing to do. I don't really care if you fix it or not TBH.

Comment 5 Nate Graham 2024-03-04 17:17:07 UTC

Ok, thanks. System updates are different from patches, which is why I was confused.

Since you're on Tumbleweed, can you update to Plasma 6 and see if the issue still happens there?

Comment 6 Bug Janitor Service 2024-03-19 03:46:19 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 7 Mark Rooks 2024-03-22 03:57:22 UTC

It's TW, like Rawhide. It changes almost every day. The issue no longer occurs on the current QT version. I am not going to bother raising bugs against TW any more. It's futile.