Bug 453703 - Plasmashell keeps crashing while CUPS is running
Summary: Plasmashell keeps crashing while CUPS is running
Status: RESOLVED WORKSFORME
Alias: None
Product: print-manager
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 22.04.1
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-05-12 14:47 UTC by Mayeul C.
Modified: 2024-05-04 03:46 UTC (History)
5 users (show)

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


Attachments
plasmashell --replace output. It just keep on looping over this again and again (4.55 KB, text/plain)
2022-05-12 14:48 UTC, Mayeul C.
Details
New crash information added by DrKonqi (3.11 KB, text/plain)
2022-05-12 14:53 UTC, Mayeul C.
Details
New backtrace 2022-11 (11.97 KB, text/plain)
2022-11-12 22:17 UTC, Mayeul C.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mayeul C. 2022-05-12 14:47:44 UTC
Application: plasmashell (5.24.5)

Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.17.5-arch1-2 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
I started the kde plasma session from sddm

- Unusual behavior I noticed:
Flickering desktop background, no taskbar, no desktop icons. Just the wallpaper alternating with a flashing black screen.

I noticed mentions of cups in the logs (which I'm attaching), so I stopped the service. Plasmashell finally started up and displayed the taskbar and everything. Previously, I had tried renaming multiple kde-related dot files.

- Custom settings of the application:
I have a lot of printers configured with CUPS.
I am pretty sure the CUPS plasmoid crashes, which brings down the whole plasmashell with it.

It's notable that it's far from the first time I report the ploblem. I had a very similar issue (CUPS plasmoid-related plasmashell crash) years ago, but it was fixed. Having any integration or plasmoid crash should not bring down the whole shell, regardless of where the issue comes from.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = 0x0}
[KCrash Handler]
#6  PrinterModel::updateDest(QStandardItem*, KCupsPrinter const&) (this=this@entry=0x5616fbff3520, destItem=0x0, printer=...) at /usr/src/debug/print-manager-22.04.1/libkcups/PrinterModel.cpp:249
#7  0x00007f94234c4503 in PrinterModel::getDestsFinished(KCupsRequest*) (this=0x5616fbff3520, request=0x5616fbfe0fe0) at /usr/src/debug/print-manager-22.04.1/libkcups/PrinterModel.cpp:137
#8  0x00007f949418b7d6 in QObject::event(QEvent*) (this=<optimized out>, e=0x5616fc011e70) at kernel/qobject.cpp:1314
#9  0x00007f9494dbd2c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x5616fbff3520, e=0x5616fc011e70) at kernel/qapplication.cpp:3637
#10 0x00007f94941675aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5616fbff3520, event=0x5616fc011e70) at kernel/qcoreapplication.cpp:1064
#11 0x00007f94941680a9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x5616fa0cdf00) at kernel/qcoreapplication.cpp:1821
#12 0x00007f94941af678 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x5616fa216290) at kernel/qeventdispatcher_glib.cpp:277
#13 0x00007f9492535163 in g_main_dispatch (context=0x7f9488005010) at ../glib/glib/gmain.c:3417
#14 g_main_context_dispatch (context=0x7f9488005010) at ../glib/glib/gmain.c:4135
#15 0x00007f949258b9e9 in g_main_context_iterate.constprop.0 (context=context@entry=0x7f9488005010, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4211
#16 0x00007f94925326c5 in g_main_context_iteration (context=0x7f9488005010, may_block=1) at ../glib/glib/gmain.c:4276
#17 0x00007f94941b357a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x5616fa21c470, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#18 0x00007f949415f88b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7fff37afd600, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#19 0x00007f949416afd7 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#20 0x00007f94945381d2 in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1867
#21 0x00007f9494dbb64a in QApplication::exec() () at kernel/qapplication.cpp:2829
#22 0x00005616f9ed0f81 in main(int, char**) (argc=<optimized out>, argv=0x7fff37afd7a0) at /usr/src/debug/plasma-workspace-5.24.5/shell/main.cpp:238
[Inferior 1 (process 213427) detached]

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

Possible duplicates by query: bug 453681, bug 453578, bug 453546, bug 453098, bug 453097.

Reported using DrKonqi
Comment 1 Mayeul C. 2022-05-12 14:48:50 UTC
Created attachment 148766 [details]
plasmashell --replace output. It just keep on looping over this again and again
Comment 2 Mayeul C. 2022-05-12 14:53:48 UTC
Created attachment 148767 [details]
New crash information added by DrKonqi

plasmashell (5.24.5) using Qt 5.15.3

This is a second crash report generated by baloo, the backtrace might be a bit different, I'm attaching it here in case it is useful.

-- Backtrace (Reduced):
#6  PrinterModel::updateDest(QStandardItem*, KCupsPrinter const&) (this=this@entry=0x55a92897a4b0, destItem=0x0, printer=...) at /usr/src/debug/print-manager-22.04.1/libkcups/PrinterModel.cpp:249
#7  0x00007f8b98111503 in PrinterModel::getDestsFinished(KCupsRequest*) (this=0x55a92897a4b0, request=0x55a928967e60) at /usr/src/debug/print-manager-22.04.1/libkcups/PrinterModel.cpp:137
#8  0x00007f8bff19a7d6 in QObject::event(QEvent*) (this=<optimized out>, e=0x55a928998580) at kernel/qobject.cpp:1314
#9  0x00007f8bffdcc2c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x55a92897a4b0, e=0x55a928998580) at kernel/qapplication.cpp:3637
#10 0x00007f8bff1765aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55a92897a4b0, event=0x55a928998580) at kernel/qcoreapplication.cpp:1064
Comment 3 Nate Graham 2022-05-12 15:29:46 UTC
#6  PrinterModel::updateDest(QStandardItem*, KCupsPrinter const&) (this=this@entry=0x5616fbff3520, destItem=0x0, printer=...) at /usr/src/debug/print-manager-22.04.1/libkcups/PrinterModel.cpp:249
#7  0x00007f94234c4503 in PrinterModel::getDestsFinished(KCupsRequest*) (this=0x5616fbff3520, request=0x5616fbfe0fe0) at /usr/src/debug/print-manager-22.04.1/libkcups/PrinterModel.cpp:137
Comment 4 Nicolas Fella 2022-05-12 15:44:52 UTC
See https://bugs.kde.org/show_bug.cgi?id=329918
Comment 5 Nicolas Fella 2022-05-12 16:00:19 UTC
What seems to happen is that in 'updateDest(item(i), printers.at(i))' (PrinterModel.cpp:137) the item(i) returns a nullptr. _Why_ that happens I have no idea
Comment 6 Mayeul C. 2022-11-12 22:17:01 UTC
Created attachment 153699 [details]
New backtrace 2022-11

Well, this is still happening. Unfortunately, I can't look up a bug report within Dr Konqui anymore with the port to QML, only select from the list.

Attaching another backtrace. I am open to sharing my CUPS configuration; most printers in here are obsolete entries.

I encountered this issue on multiple computers that had obsolete printers entries, in unrelated settings (no common printer).

How can an issue with a single plasmoid bring the whole shell down?
Comment 7 Mike 2024-04-04 16:04:29 UTC
We believe this is fixed in a later version of Plasma5 and the recently released Plasma6.  Can you retest this and report back?
Comment 8 Nate Graham 2024-04-04 16:05:36 UTC
Don't forget to kick the bug report into NEEDSINFO FIXED status when asking a question like that. :)
Comment 9 Bug Janitor Service 2024-04-19 03:47:37 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 10 Bug Janitor Service 2024-05-04 03:46:01 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

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