[plasmashell] [Bug 483628] Plasma 6.0.2 crashing
https://bugs.kde.org/show_bug.cgi?id=483628 --- Comment #11 from dexter --- Yes good guess -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483628] Plasma 6.0.2 crashing
https://bugs.kde.org/show_bug.cgi?id=483628 --- Comment #16 from dexter --- (In reply to Fushan Wen from comment #14) > Git commit 0350e4468502f10a9530e41850cf929db20f5bb9 by Fushan Wen. > Committed on 26/03/2024 at 00:28. > Pushed by fusionfuture into branch 'Plasma/6.0'. > > applets/weather: remove invalid bindings on Layout properties > > Those weather views are in the SwipeView, not in a layout. > Related: bug 483791 > > > (cherry picked from commit 8581674ee8fb2b0a17619302fa5a4e8f59669100) > > 916d5ab8 applets/weather: remove invalid bindings on Layout properties > > M +0-2applets/weather/package/contents/ui/ForecastView.qml > M +2-2applets/weather/package/contents/ui/SwitchPanel.qml > M +1-1applets/weather/package/contents/ui/TopPanel.qml > > https://invent.kde.org/plasma/kdeplasma-addons/-/commit/ > 0350e4468502f10a9530e41850cf929db20f5bb9 Testing... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483628] Plasma 6.0.2 crashing
https://bugs.kde.org/show_bug.cgi?id=483628 --- Comment #18 from dexter --- (In reply to Fushan Wen from comment #17) > Is there any new crash? No it's been rock solid. I think you may have cracked it. Famous last words. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483628] Plasma 6.0.2 crashing
https://bugs.kde.org/show_bug.cgi?id=483628 --- Comment #20 from dexter --- Closed QT bug. Thanks for coming. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483628] New: Plasma 6.0.2 crashing
https://bugs.kde.org/show_bug.cgi?id=483628 Bug ID: 483628 Summary: Plasma 6.0.2 crashing Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: dex.m...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.0.2) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.8.0-63.fc40.1.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora release 40 (Forty)" DrKonqi: 6.0.2 [CoredumpBackend] -- Information about the crash: Random crashes in floating planel since v6.0 The crash can be reproduced sometimes. -- Backtrace (Reduced): #8 qobject_cast (object=) at /usr/include/qt6/QtCore/qobject.h:393 #9 QQuickLayout::effectiveSizePolicy_helper (item=, orientation=, info=) at /usr/src/debug/qt6-qtdeclarative-6.6.2-1.fc40.x86_64/src/quicklayouts/qquicklayout.cpp:1269 #10 0x7feb81f5f13b in QGridLayoutItem::stretchFactor (this=, orientation=) at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/gui/util/qgridlayoutengine.cpp:533 #11 QGridLayoutItem::stretchFactor (this=, orientation=) at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/gui/util/qgridlayoutengine.cpp:527 #12 0x7feb81f66396 in QGridLayoutEngine::fillRowData (this=this@entry=0x558c1769c288, rowData=rowData@entry=0x558c1769c428, colPositions=colPositions@entry=0x0, colSizes=colSizes@entry=0x0, orientation=orientation@entry=Qt::Horizontal, styleInfo=styleInfo@entry=0x558c1769be10) at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/gui/util/qgridlayoutengine.cpp:1395 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483628] Plasma 6.0.2 crashing
https://bugs.kde.org/show_bug.cgi?id=483628 --- Comment #1 from dexter --- Created attachment 167233 --> https://bugs.kde.org/attachment.cgi?id=167233&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483628] Plasma 6.0.2 crashing
https://bugs.kde.org/show_bug.cgi?id=483628 --- Comment #3 from dexter --- (In reply to Fushan Wen from comment #2) > What were you doing when the crash happened it's random, but it feels like when I move to activate the main floating panel which is auto hidden it's likely to crash or not. here is another trace since the last crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483628] Plasma 6.0.2 crashing
https://bugs.kde.org/show_bug.cgi?id=483628 --- Comment #4 from dexter --- Created attachment 167285 --> https://bugs.kde.org/attachment.cgi?id=167285&action=edit new trace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483628] Plasma 6.0.2 crashing
https://bugs.kde.org/show_bug.cgi?id=483628 --- Comment #5 from dexter --- I just got a crash while 30mins into a fullscreen video, the screen flashed black & audio kept playing. I got out of fullscreen to find drkonqi so no input from me this time. trace included. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483628] Plasma 6.0.2 crashing
https://bugs.kde.org/show_bug.cgi?id=483628 --- Comment #6 from dexter --- Created attachment 167306 --> https://bugs.kde.org/attachment.cgi?id=167306&action=edit trace 3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483628] Plasma 6.0.2 crashing
https://bugs.kde.org/show_bug.cgi?id=483628 --- Comment #7 from dexter --- I've also filed this against QT https://bugreports.qt.io/browse/QTBUG-123638 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483628] Plasma 6.0.2 crashing
https://bugs.kde.org/show_bug.cgi?id=483628 dexter changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444468] Sometimes a context menu won't go away even after it's program is closed.
https://bugs.kde.org/show_bug.cgi?id=68 dexter changed: What|Removed |Added CC||dex.m...@gmail.com --- Comment #2 from dexter --- I'm seeing this now in Fedora F35 & previously, in all applications randomly plasma version 5.24.2 frameworks 5.91 Qt 5.15.2 X11 kernel 5.16.12 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444468] Sometimes a context menu won't go away even after it's program is closed.
https://bugs.kde.org/show_bug.cgi?id=68 --- Comment #3 from dexter --- Created attachment 147285 --> https://bugs.kde.org/attachment.cgi?id=147285&action=edit screen as I wrote this bug -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 445274] New: Kontact crashes on opening
https://bugs.kde.org/show_bug.cgi?id=445274 Bug ID: 445274 Summary: Kontact crashes on opening Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dex...@midsummervet.co.uk Target Milestone: --- Application: kontact (5.14.2 (20.04.2)) Qt Version: 5.12.7 Frameworks Version: 5.76.0 Operating System: Linux 5.3.18-59.27-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.3" -- Information about the crash: - What I was doing when the application crashed: Opening Kontact. Follows upgrade from Opensuse 15.2 to 15.3 The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f8aeb9198e0 in ?? () from /usr/lib64/libQt5Widgets.so.5 #5 0x7f8aeb945858 in QWidget::insertAction(QAction*, QAction*) () from /usr/lib64/libQt5Widgets.so.5 #6 0x7f8aec80cfd2 in KXMLGUI::ActionList::plug(QWidget*, int) const () from /usr/lib64/libKF5XmlGui.so.5 #7 0x7f8aec810912 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&, QTypedArrayData::iterator const&) () from /usr/lib64/libKF5XmlGui.so.5 #8 0x7f8aec810ad6 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) () from /usr/lib64/libKF5XmlGui.so.5 #9 0x7f8aec810b13 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) () from /usr/lib64/libKF5XmlGui.so.5 #10 0x7f8aec810b13 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) () from /usr/lib64/libKF5XmlGui.so.5 #11 0x7f8aec80a3eb in KXMLGUIFactory::plugActionList(KXMLGUIClient*, QString const&, QList const&) () from /usr/lib64/libKF5XmlGui.so.5 #12 0x7f8a48309b5d in PimCommon::PluginInterface::initializePluginActions (this=, prefix=..., guiClient=0x557e6dfa2b80) at /usr/src/debug/pimcommon-20.04.2-bp153.2.2.1.x86_64/src/pimcommonakonadi/genericplugins/plugininterface.cpp:168 #13 0x7f8a4b3e33fe in KMMainWidget::initializePluginActions (this=) at /usr/src/debug/kmail-20.04.2-bp153.3.2.1.x86_64/src/kmmainwidget.cpp:4217 #14 0x7f8a4b7ae175 in KMailPart::guiActivateEvent (this=0x557e6dfa2b50, e=) at /usr/src/debug/kmail-20.04.2-bp153.3.2.1.x86_64/src/kmail_part.cpp:133 #15 0x7f8aeaab8a1b in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #16 0x7f8aeb90df9c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x7f8aeb9155b0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x7f8aeaa883a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #19 0x7f8ae881b071 in KParts::MainWindow::createGUI (this=0x557e695da630, part=0x557e6dfa2b50) at /usr/src/debug/kparts-5.76.0-bp153.2.2.1.x86_64/src/mainwindow.cpp:108 #20 0x7f8aed142803 in Kontact::MainWindow::selectPlugin (this=0x557e695da630, plugin=0x557e6dd728f0) at /usr/src/debug/kontact-20.04.2-bp153.2.2.1.x86_64/src/mainwindow.cpp:704 #21 0x7f8aed13c178 in Kontact::MainWindow::qt_static_metacall (_o=, _c=, _id=, _a=) at /usr/src/debug/kontact-20.04.2-bp153.2.2.1.x86_64/build/src/kontactprivate_autogen/EWIEGA46WW/moc_mainwindow.cpp:156 #22 0x7f8aeaab7eb5 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #23 0x7f8aed13bb4f in Kontact::SidePaneBase::pluginSelected (this=, _t1=) at /usr/src/debug/kontact-20.04.2-bp153.2.2.1.x86_64/build/src/kontactprivate_autogen/EWIEGA46WW/moc_sidepanebase.cpp:140 #24 0x7f8aeaab7fcf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #25 0x7f8aed13baef in Kontact::Navigator::pluginActivated (this=, _t1=) at /usr/src/debug/kontact-20.04.2-bp153.2.2.1.x86_64/build/src/kontactprivate_autogen/EWIEGA46WW/moc_iconsidepane.cpp:160 #26 0x7f8aeaab7fcf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #27 0x7f8aeaa3da7a in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) () from /usr/lib64/libQt5Core.so.5 #28 0x7f8aeaa3dd06 in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags) () from /usr/lib64/libQt5Core.so.5 #29 0x7f8aed149501 in Kontact::Navigator::setCurrentPlugin (this=0x557e695368b0, plugin=...) at /usr/src/debug/kontact-20.04.2-bp153.2.2.1.x86_64/src/iconsidepane.cpp:420 #30 0x7f8aed142730 in Kontact::MainWindow::selectPlugin (this=0x557e695da630, plugin=0x557e6dd728f0) at /usr/src/debug/kontact-20.04.2-bp153.2.2.1.x86_64/src/mainwindow.cpp:675 #31 0x7f8aed1410ac in Kontact::MainWindow::loadSettings (this=0x557e695da630) at /usr/src/debug/kontact-20.04.2-bp153.2.2.1.x86_64/src/mainwindow.cpp:780 #32 0x7f8aed144ddd in Kontact::MainWindow::initObject
[Akonadi] [Bug 434725] Crashed when starting Kontact being started
https://bugs.kde.org/show_bug.cgi?id=434725 Dexter changed: What|Removed |Added CC||dex...@midsummervet.co.uk -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 434725] Crashed when starting Kontact being started
https://bugs.kde.org/show_bug.cgi?id=434725 --- Comment #2 from Dexter --- Created attachment 137160 --> https://bugs.kde.org/attachment.cgi?id=137160&action=edit New crash information added by DrKonqi akonadiserver (5.14.2 (20.04.2)) using Qt 5.12.7 - What I was doing when the application crashed: Logging into destktop. Akonadi started in the background then crashed -- Backtrace (Reduced): #4 0x7f4e477731ec in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x35) at /usr/include/c++/7/bits/atomic_base.h:396 #5 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #6 QBasicAtomicInteger::load (this=0x35) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 [...] #8 QString::operator= (this=0x7f4dfc067a48, other=...) at tools/qstring.cpp:2417 [...] #10 0x7f4e478f5f4f in QtPrivate::QSlotObjectBase::call (a=0x7f4e37ffe710, r=0x55d807f07be0, this=0x7f4e180257e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 435992] New: Akonadi crashed : Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=435992 Bug ID: 435992 Summary: Akonadi crashed : Segmentation fault Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: dex...@midsummervet.co.uk Target Milestone: --- Application: akonadiserver (5.14.2 (20.04.2)) Qt Version: 5.12.7 Frameworks Version: 5.71.0 Operating System: Linux 5.3.18-lp152.69-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.2" -- Information about the crash: - What I was doing when the application crashed: Nothing. Akonadi was running in the background with Kontact on the desktop -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x7fdbf33bb1ec in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x7fdb003b) at /usr/include/c++/7/bits/atomic_base.h:396 #5 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #6 QBasicAtomicInteger::load (this=0x7fdb003b) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 #7 QtPrivate::RefCount::deref (this=0x7fdb003b) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:66 #8 QString::operator= (this=0x7fdba0147df8, other=...) at tools/qstring.cpp:2417 #9 0x5613345df855 in ?? () #10 0x7fdbf353df4f in QtPrivate::QSlotObjectBase::call (a=0x7fdbe3ffe710, r=0x56133510f0f0, this=0x7fdbd0006b90) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #11 QMetaObject::activate (sender=0x7fdbd0007680, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3784 #12 0x561334630764 in ?? () #13 0x5613345e3164 in ?? () #14 0x7fdbf353df4f in QtPrivate::QSlotObjectBase::call (a=0x7fdbe3ffe900, r=0x7fdbd0007680, this=0x7fdbd000b960) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #15 QMetaObject::activate (sender=0x7fdbe4020070, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fdbe3ffe900) at kernel/qobject.cpp:3784 #16 0x7fdbf353e547 in QMetaObject::activate (sender=, m=m@entry=0x7fdbf3e975c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fdbe3ffe900) at kernel/qobject.cpp:3657 #17 0x7fdbf3c7ad5f in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:157 #18 0x7fdbf353e9e2 in QObject::event (this=0x7fdbe4020070, e=) at kernel/qobject.cpp:1261 #19 0x7fdbf350e311 in doNotify (event=0x7fdba00802c0, receiver=0x7fdbe4020070) at kernel/qcoreapplication.cpp:1178 #20 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1164 #21 QCoreApplication::notifyInternal2 (receiver=0x7fdbe4020070, event=0x7fdba00802c0) at kernel/qcoreapplication.cpp:1088 #22 0x7fdbf350e4fe in QCoreApplication::sendEvent (receiver=, event=event@entry=0x7fdba00802c0) at kernel/qcoreapplication.cpp:1476 #23 0x7fdbf3510ee7 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x56133511b650) at kernel/qcoreapplication.cpp:1825 #24 0x7fdbf3511488 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1679 #25 0x7fdbf356bd93 in postEventSourceDispatch (s=0x7fdbd0004b70) at kernel/qeventdispatcher_glib.cpp:276 #26 0x7fdbef0dc624 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #27 0x7fdbef0dc9c0 in ?? () from /usr/lib64/libglib-2.0.so.0 #28 0x7fdbef0dca4c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #29 0x7fdbf356b3af in QEventDispatcherGlib::processEvents (this=0x7fdbdb10, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #30 0x7fdbf350c57a in QEventLoop::exec (this=this@entry=0x7fdbe3ffecb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #31 0x7fdbf333190a in QThread::exec (this=) at thread/qthread.cpp:531 #32 0x7fdbf0b2 in QThreadPrivate::start (arg=0x561335102910) at thread/qthread_unix.cpp:361 #33 0x7fdbf16da4f9 in start_thread () from /lib64/libpthread.so.0 #34 0x7fdbf29b2ecf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fdbe8809700 (LWP 12966) "CacheCleaner-Th"): #1 0x7fdbef124090 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fdbef0dc458 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fdbef0dc8e0 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fdbef0dca4c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fdbf356b3cb in QEventDispatcherGlib::processEvents (this=0x7fdbd8000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fdbf350c57a in QEventLoop::exec (this=this@entry=0x7fdbe8808cb0, f
[plasmashell] [Bug 489993] New: plasma crash
https://bugs.kde.org/show_bug.cgi?id=489993 Bug ID: 489993 Summary: plasma crash Classification: Plasma Product: plasmashell Version: 6.1.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: dex.m...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.1.1) Qt Version: 6.7.2 Frameworks Version: 6.3.0 Operating System: Linux 6.9.8-200.fc40.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora release 40 (Forty)" DrKonqi: 6.1.1 [CoredumpBackend] -- Information about the crash: Random crash when accessing the main panel, two occurances in as many days The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 dri2_invalidate_drawable (dPriv=0x0) at ../src/gallium/frontends/dri/dri2.c:100 #6 0x7ff97af66127 in QtWaylandClient::QWaylandEglWindow::updateSurface (this=0x55bfd8954210, create=false) at /usr/include/qt6/QtCore/qpoint.h:129 #7 0x7ff981e41e43 in QWindow::resize (this=0x55bfd8285510, newSize=...) at /usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/gui/kernel/qwindow.cpp:2027 #8 0x7ff98431b4ab in PlasmaQuick::DialogPrivate::syncToMainItemSize (this=0x55bfd9039c80) at /usr/src/debug/libplasma-6.1.1-1.fc40.x86_64/src/plasmaquick/dialog.cpp:664 #9 0x7ff9815fcbe0 in doActivate (sender=0x55bfd5a19940, signal_index=26, argv=0x7ffcbfff9c68) at /usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/kernel/qobject.cpp:4098 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489993] plasma crash
https://bugs.kde.org/show_bug.cgi?id=489993 --- Comment #1 from dexter --- Created attachment 171511 --> https://bugs.kde.org/attachment.cgi?id=171511&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 505201] Black screen with cursor periodically on resume from suspend
https://bugs.kde.org/show_bug.cgi?id=505201 dexter changed: What|Removed |Added CC||dex.m...@gmail.com --- Comment #10 from dexter --- I'm now seeing this bug on two systems in fedora since 6.4.1 on resume. Jul 01 01:59:05 kernel: kscreenlocker_g[21849]: segfault at f2c ip 7f21f834219d sp 7ffcae3d0da0 error 4 in libLayerShellQtInterface.so.6.4.1[319d,7f21f833f000+7000] likely on CPU 3 (core 3, socket 0) Jul 01 01:59:05 kernel: Code: be 02 00 00 00 4c 89 e7 31 c0 e8 2e da ff ff 49 83 7e 10 00 0f 85 8b 00 00 00 49 8b 87 b0 01 00 00 48 85 c0 74 32 4c 8b 63 18 <4c> 8b 70 18 44 8b 6d a8 4c 89 e7 e8 53 d9 ff ff 48 83 ec 08 31 d2 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 481942] New: Login WebView does not work on Flatpak Nightly (24.02 basically)
https://bugs.kde.org/show_bug.cgi?id=481942 Bug ID: 481942 Summary: Login WebView does not work on Flatpak Nightly (24.02 basically) Classification: Applications Product: Tokodon Version: 24.02.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dreed4...@proton.me CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- Created attachment 166159 --> https://bugs.kde.org/attachment.cgi?id=166159&action=edit Screenshot of an error likely to do with QtWebView and logging in *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 481942] Login WebView does not work on Flatpak Nightly (24.02 basically)
https://bugs.kde.org/show_bug.cgi?id=481942 --- Comment #1 from Dexter Reed --- Oops I submitted it by accident :( -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 481942] Login WebView does not work on Flatpak Nightly (24.02 basically)
https://bugs.kde.org/show_bug.cgi?id=481942 --- Comment #2 from Dexter Reed --- STEPS TO REPRODUCE: 1. Click `Login` 2. Input any server URL 3. Click `Continue` OBSERVED RESULT: The app doesn't seem to do anything on the GUI, but shows this error in the terminal: ``` file:///usr/qml/org/kde/kirigami/PageRow.qml:718:5: QML StackView: push: qrc:/qt/qml/org/kde/tokodon/content/ui/LoginFlow/AuthorizationPage.qml:5 module "QtWebView" is not installed ``` EXPECTED RESULT: Tokodon shows the login screen fine and lets me log in. SOFTWARE/OS VERSIONS: Qt Version: 6.6(probably .2) KDE Frameworks Version: 6.0.0 KDE Plasma Version: Not using Plasma (GNOME 45) Flatpak: 1.15.6 Tokodon: Nightly Flatpak -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 481942] Login WebView does not work on Flatpak Nightly (24.02 basically)
https://bugs.kde.org/show_bug.cgi?id=481942 --- Comment #4 from Dexter Reed --- (In reply to Joshua Goins from comment #3) > Where did you source this flatpak version? Our qt6 nightly repository or did > it release on Flathub without me knowing? :D By `qt6 nightly repository`, I believe you mean this: https://cdn.kde.org/flatpak/tokodon-nightly/ ? If so, I got it from there :) -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 481942] Login WebView does not work on Flatpak Nightly (24.02 basically)
https://bugs.kde.org/show_bug.cgi?id=481942 --- Comment #5 from Dexter Reed --- I don't know if this helps at all, but adding the env `QML_IMPORT_PATH=/app/qml/` makes Tokodon go to the Authorization page and give this error instead: `No WebView plug-in found!` -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445523] lfe sound not working for 5.1 or 7.1 multichannel audio
https://bugs.kde.org/show_bug.cgi?id=445523 Sophie Dexter changed: What|Removed |Added CC||wothum...@gmx.de --- Comment #4 from Sophie Dexter --- This bug and a proposed fix has been around for a while now. @gnagflow are you able to submit a merge request with your proposed changes for this bug? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445523] lfe sound not working for 5.1 or 7.1 multichannel audio
https://bugs.kde.org/show_bug.cgi?id=445523 --- Comment #6 from Sophie Dexter --- (In reply to Ismael Asensio from comment #5) > (In reply to Sophie Dexter from comment #2) > > > > I'm happy to test any fixes. > > I just got aware of this bug report now. > > Since I don't have a system with a subwoofer, could you please try > https://invent.kde.org/plasma/plasma-pa/-/merge_requests/121 to see if that > fixes the issue? > > Thanks Hi Ismael, I have re-compiled plasma-pa with your changes and can confirm that Speakertest now works for my 5.1 setup, spoken 'rear-center' audio is played through the subwoofer, albeit that it sounds rather muffled of course :rolleyes: :-). Many thanks to you for preparing the merge request and to Nicolas for reviewing. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445523] lfe sound not working for 5.1 or 7.1 multichannel audio
https://bugs.kde.org/show_bug.cgi?id=445523 Sophie Dexter changed: What|Removed |Added CC||sophie.dexte...@yahoo.co.uk --- Comment #2 from Sophie Dexter --- I experience the same with Fedora 35, Plasma 24 and Pipewire. Perhaps even more so; not only does the subwoofer button not work, but my system then becomes unresponsive until I 'kill' System Settings. I'm happy to test any fixes. Kernel 5.16.12 KDE Plasma: 5.24.2 Frameworks: 5.91.0 Qt: 5.15.2 Pipewire: 0.3.47 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445523] lfe sound not working for 5.1 or 7.1 multichannel audio
https://bugs.kde.org/show_bug.cgi?id=445523 Sophie Dexter changed: What|Removed |Added Version|5.23.3 |5.24.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445523] lfe sound not working for 5.1 or 7.1 multichannel audio
https://bugs.kde.org/show_bug.cgi?id=445523 Sophie Dexter changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Sophie Dexter --- I have now installed KDE development tools and built against today's origin master: KDE Plasma: 5.24.80 Frameworks: 5.93.0 Qt: 5.15.2 The problem still exists and I went on to re-compile plasma-pa with gnagflow's proposed changes and can confirm that replacing onClicked: tester.testChannel(modelData === "lfe" ? "rear-center" : modelData) (NOTE now at line 409) with either onClicked: tester.testChannel(modelData === "lfe" ? "lfe" : modelData) or simply onClicked: tester.testChannel(modelData) does indeed work - for me. Is this a regression relating to what was apparently fixed by https://invent.kde.org/plasma/plasma-pa/-/commit/bc79ca3289903cb641fd29a0b9cf8da17427421a for https://bugs.kde.org/show_bug.cgi?id=427038 ? Personally I prefer the fallback audio-test-signal's 'white noise' for the subwoofer test sound to a rather muffled spoken 'rear center' so I didn't link 'audio-channel-lfe.oga' to 'audio-channel-rear-center.oga'. For me this is a 15-minute-bug because it causes KDE's 'systemsettings' to hang hint @Nate :-) https://pointieststick.com/2022/01/18/the-15-minute-bug-initiative/ 5. I’m experiencing this annoying issue that’s not on the list! Can you add it? Maybe. Mention the 15-minute bug initiative in the bug report for it, and KDE’s bug triagers will see if it makes the cut. I'd fix this in the KDE repository if I knew how, but (noob alert) I don't... and I'm not even sure if this is a good fix or a nasty hack (no offence gnagflow) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #24 from Sophie Dexter --- (In reply to Fabian Vogt from comment #23) > (In reply to Sophie Dexter from comment #19) > > (In reply to Fabian Vogt from comment #18) > > > I used 'sudo vi /etc/authselect/password-auth' when editing, unsure what I > > > was supposed to do/see with the root shell though,? > > > > The (extra) open root shell would have enabled you to use it to fix the PAM > > configuration in case you made a mistake, making you unable to login. > > Exactly that! password-auth is likely used by all authentication methods > (tty + graphical login, ssh), so if there's a typo or other issue you'd lock > yourself out of your system. Understood! - I did have a TTY3 session logged in with my normal user account but I now realise that may not have been enough if I needed root access but had 'broken' my PAM configuration. Thank you both for explaining :-) (In reply to Fabian Vogt from comment #23) > (In reply to Sophie Dexter from comment #19) > > (In reply to Fabian Vogt from comment #18) > > > The fix would be to return PAM_CONV_ERR until pam_authenticate returns > > > failure. > > Great!, umm, how :?: > > Like this: https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/240 > Can you please check whether this MR fixes the issue for you? > Unfortunately not really, but behaviour is different: The lock screen almost works with authselect 'local' profile with the peculiarity that the lock screen shakes and informs 'Unlocking Failed' then sleeps after that message's timeout expires. However, with authselect's 'sssd' profile I have to press the sleep button twice before my system will sleep. I see the screen shake and an 'Unlocking Failed' message each time I press sleep. The better news is that unlocking works at the first attempt with either profile. the plot thickens... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #25 from Sophie Dexter --- (In reply to Sophie Dexter from comment #24) > However, with authselect's 'sssd' profile I have to press the sleep button > twice before my system will sleep. I see the screen shake and an 'Unlocking > Failed' message each time I press sleep. > Update - behaviour with authselect's sssd profile is variable - I initially thought that I had to press the sleep button twice but I was impatient as my system does always seem to sleep after the first press sometimes immediately after the lockscreen shakes and protests 'Unlocking Failed' but sometimes not for a few 10s of seconds if I wait... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490924] New: The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 Bug ID: 490924 Summary: The first password attempt is rejected after system wakes from sleep. Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs URL: https://github.com/sddm/sddm/issues/1941 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sophie.dexte...@yahoo.co.uk Target Milestone: --- SUMMARY The first password attempt is rejected when I resume my system from sleep after it was put to sleep from the lock screen even though my password appears to be correct when I make it visible using the show password function. I am always able to log in on the second attempt. My system is unlocked as expected, i.e. without a rejected attempt, when I put my system to sleep using the application menu launcher's sleep icon or when unlocking without sleeping. STEPS TO REPRODUCE 1. Wait for screen to lock automatically after a period of inactivity or lock with Meta-L key combination 2. Put system to sleep using the Sleep icon on the lock screen 3. Wake system and enter correct password to unlock OBSERVED RESULT My password is rejected the first time it is entered, the login screen shakes and an 'Unlocking failed' message is shown. I am able to login only when I enter my password a second time. EXPECTED RESULT The desktop should be unlocked the first time a correct password is entered. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 - 6.9.10-200.fc40.x86_64 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION I think this may have started when I upgraded my system from Fedora 39 to Fedora 40, but my journal logs only go back 3 months so I can't be sure, the oldest record from journalctl output I can find is from shortly after I upgraded: May 01 06:32:09 Just4pLeisure kscreenlocker_greet[276611]: pam_unix(kde:auth): unexpected response from failed conversation function May 01 06:32:09 Just4pLeisure kscreenlocker_greet[276611]: pam_unix(kde:auth): conversation failed May 01 06:32:09 Just4pLeisure kscreenlocker_greet[276611]: pam_unix(kde:auth): auth could not identify password for [sophie] The issue persists to this day despite numerous updates to Plasma, Frameworks and Qt: Jul 27 17:39:35 Just4pLeisure kscreenlocker_greet[21299]: pam_unix(kde:auth): unexpected response from failed conversation function Jul 27 17:39:35 Just4pLeisure kscreenlocker_greet[21299]: pam_unix(kde:auth): conversation failed Jul 27 17:39:35 Just4pLeisure kscreenlocker_greet[21299]: pam_unix(kde:auth): auth could not identify password for [sophie] Lee Head has submitted a complete journalctl log here :https://github.com/sddm/sddm/issues/1941#issuecomment-2156369683 Fabian Vogt (Vogtinator) suspects sleeping from the lock screen somehow triggers a broken PAM conversation: https://github.com/sddm/sddm/issues/1941#issuecomment-2254224974 I can supply log files as required and would love to try to debug this, although I may need a bit of guidance... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 Sophie Dexter changed: What|Removed |Added Component|general |general Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Product|kde |kscreenlocker -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #3 from Sophie Dexter --- (In reply to Fabian Vogt from comment #1) > If the broken PAM conversation is the cause, this should avoid it: > > diff --git a/greeter/greeterapp.cpp b/greeter/greeterapp.cpp > index eb088cc..6c016cb 100644 > --- a/greeter/greeterapp.cpp > +++ b/greeter/greeterapp.cpp > @@ -527,7 +527,6 @@ void UnlockApp::suspendToRam() > > m_ignoreRequests = true; > m_resetRequestIgnoreTimer->start(); > -m_authenticators->cancel(); > > PowerManagement::instance()->suspend(); > } Thank you Fabian, I have compiled kscreenlocker_greet with your patch and it resolves the rejected password issue for me :-) > Probably not a proper fix though, at least the noninteractive authenticators > running in the background should probably be stopped before suspending. > Currently that's not guaranteed either though, it's all async. I understand at a very abstract level why you are concerned that this is a rough workaround but don't understand in any of the detail. With enough the time I'd love to learn one day as I've raised a few bug reports now and have graduated to the level of 'can compile with supplied patches' :-D. Until I achieve my next badge (or 3) I'll have to leave a proper, or at least acceptable, fix to you as professionals. In the mean time I'll watch this bug report and test any developments too. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 Sophie Dexter changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Sophie Dexter --- (In reply to Fabian Vogt from comment #4) > It would be useful if you could run > > QT_LOGGING_RULES=kscreenlocker_greet.debug=true > /usr/libexec/kscreenlocker_greet --testing -platform xcb > > and reproduce the issue. Hmm, running that is proving to be tricky since this only occurs immediately after waking my system from sleep and I don't know how to do what you ask. I've tried running from a different TTY but I am greeted with: >> kscreenlocker_greet: Greeter is starting up. >> qt.qpa.xcb: could not connect to display >> qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load >> the Qt xcb platform plugin. >> qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though >> it was found. >> This application failed to start because no Qt platform plugin could be >> initialized. Reinstalling the application may fix this problem. >> >> Available platform plugins are: wayland-egl, wayland, eglfs, linuxfb, >> minimal, minimalegl, offscreen, vkkhrdisplay, vnc, xcb. Exporting DISPLAY=0 beforehand doesn't help. Thinking perhaps this is due to Fedora 40 being Wayland only I then tried wayland and wayland-egl instead of xcb. For reference, this is the output from running with --testing -platform wayland-egl (output is similar with -platform wayland option): >> kscreenlocker_greet: Greeter is starting up. >> qt.qpa.wayland: qtvirtualkeyboard currently is not supported at client-side, >> use QT_IM_MODULE=qtvirtualkeyboard at compositor-side. >> kscreenlocker_greet: [PAM worker kde-smartcard] start: successfully started >> kscreenlocker_greet: Greeter is running in testing mode >> kscreenlocker_greet: Testing mode enabled: true >> kscreenlocker_greet: [PAM worker kde] start: successfully started >> kscreenlocker_greet: [PAM worker kde-fingerprint] start: successfully started >> kf.guiaddons: No modifierkeyinfo backend for platform "wayland-egl" >> org.kde.plasma.keyboardindicator: Unknown key Qt::Key_CapsLock >> kf.guiaddons: No modifierkeyinfo backend for platform "wayland-egl" >> org.kde.plasma.keyboardindicator: Unknown key Qt::Key_CapsLock >> kf.guiaddons: No modifierkeyinfo backend for platform "wayland-egl" >> org.kde.plasma.keyboardindicator: Unknown key Qt::Key_CapsLock >> Locked at 1722345401 >> kscreenlocker_greet: PamAuthenticators: starting authenticators >> kscreenlocker_greet: PamAuthenticators: state changing from >> PamAuthenticators::Idle to PamAuthenticators::Authenticating >> kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Starting >> authentication >> kscreenlocker_greet: [PAM worker kde] Authenticate: Starting authentication >> kscreenlocker_greet: [PAM worker kde-smartcard] Message: Info message: >> auth=authinfo_unavail >> kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Starting >> authentication >> kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Authentication >> done, result code: 9 (Authentication service cannot retrieve authentication >> info) >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-smartcard true >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-fingerprint true >> kscreenlocker_greet: PamAuthenticators: Info message from non-interactive >> authenticator kde-smartcard >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-smartcard false >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-smartcard false >> kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password: >> kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await >> response >> kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive >> authenticator kde >> kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: >> Authentication done, result code: 9 (Authentication service cannot retrieve >> authentication info) >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-fingerprint false >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> n
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 Sophie Dexter changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #7 from Sophie Dexter --- (In reply to Fabian Vogt from comment #6) > You should be able to run the command and try the sleep button. Ha! That was _embarassingly_ obvious :o) Unfortunately it wasn't much help however. I se the testing lockscreen on waking my system which accepted my password first time, followed by the 'real' lockscreen which rejected my password before accepting... Qt logging messages were similar to before. But faking suspend with > It's also possible to "fake" the suspend by removing the call to > PowerManagement::instance()->suspend(); instead of > m_authenticators->cancel(); shows more promise and I see my password being rejected with lockscreen testing. I've tried to annotate logged output, three messages in particular seem to indicate trouble: >> kscreenlocker_greet: Greeter is starting up. >> kscreenlocker_greet: [PAM worker kde-smartcard] start: successfully started >> kscreenlocker_greet: Greeter is running in testing mode >> kscreenlocker_greet: Testing mode enabled: true >> kscreenlocker_greet: [PAM worker kde-fingerprint] start: successfully started >> kscreenlocker_greet: [PAM worker kde] start: successfully started >> Locked at 1722370491 >> kscreenlocker_greet: PamAuthenticators: starting authenticators >> kscreenlocker_greet: PamAuthenticators: state changing from >> PamAuthenticators::Idle to PamAuthenticators::Authenticating >> kscreenlocker_greet: [PAM worker kde] Authenticate: Starting authentication >> kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Starting >> authentication >> kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Starting >> authentication >> kscreenlocker_greet: [PAM worker kde-smartcard] Message: Info message: >> auth=authinfo_unavail >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-fingerprint true >> kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Authentication >> done, result code: 9 (Authentication service cannot retrieve authentication >> info) >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-smartcard true >> kscreenlocker_greet: PamAuthenticators: Info message from non-interactive >> authenticator kde-smartcard >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-smartcard false >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-smartcard false >> kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: >> Authentication done, result code: 9 (Authentication service cannot retrieve >> authentication info) >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-fingerprint false >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-fingerprint false This relates to Password box before pressing (faked) sleep icon >> kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password: >> kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await >> response >> kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive >> authenticator kde These three messages could be telling >> kscreenlocker_greet: PamAuthenticators: cancelling interactive authenticator >> kscreenlocker_greet: [PAM worker kde] Received cancellation, exiting with >> PAM_CONV_ERR >> kscreenlocker_greet: [PAM worker kde] Nested event loop's exit code was not >> zero, bailing This relates to the failing first password attempt after (faked) resume >> kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password: >> kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await >> response >> kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive >> authenticator kde >> kscreenlocker_greet: PamAuthenticators: responding to interactive >> authenticator >> kscreenlocker_greet: [PAM worker kde] Received response, exiting nested >> event loop >> kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde >> changed business >> kscreenlocker_greet: [PAM worker kde] Authenticate: Authentication done, >> result code: 7 (Authentication failure) >> kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde >> changed business >> kscreenlocker_greet: PamAuthenticators: Failure from interactive >> authenticator kde >&g
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #9 from Sophie Dexter --- Created attachment 172221 --> https://bugs.kde.org/attachment.cgi?id=172221&action=edit Messages reported by 'kscreenlocker_greet -testing' -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #10 from Sophie Dexter --- Created attachment 17 --> https://bugs.kde.org/attachment.cgi?id=17&action=edit PAM debug messages during kscreenlocker_greet --testing -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #11 from Sophie Dexter --- (In reply to Fabian Vogt from comment #8) > Ok, that confirms it's indeed the PAM module refusing to authenticate. > Question is why. > > You could try creating /etc/pam_debug or adding debug to the pam_unix line > in the kde pam module. Not sure where the debug output ends up though, might > be in the journal or somewhere in /var/log/... It took all of the above and a bit more, combining information from these two sources, debug messages appear in /var/log/debug.log (maybe not everything is needed): https://www.ibm.com/docs/en/aix/7.3?topic=modules-enabling-pam-debug https://help.duo.com/s/article/5095?language=en_US /etc/pam.d/kde file doesn't include an entry for pam_unix.so but references password-auth which has multiple entries and I added 'debug' to each entry. Unfortunately I don't really know how to decipher these dubug messages :-( -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #13 from Sophie Dexter --- Created attachment 172304 --> https://bugs.kde.org/attachment.cgi?id=172304&action=edit /etc/pam.d/kde file -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #14 from Sophie Dexter --- Created attachment 172305 --> https://bugs.kde.org/attachment.cgi?id=172305&action=edit /etc/authselect/password-auth - sssd version -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #15 from Sophie Dexter --- Created attachment 172306 --> https://bugs.kde.org/attachment.cgi?id=172306&action=edit /etc/authselect/password-auth - local version -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #16 from Sophie Dexter --- (In reply to Fabian Vogt from comment #12) > I don't see any new info in either of those logs unfortunately. What's the > full content of both kde and password-auth PAM configs? Files in attachments with 2 versions of 'password-auth' file, one for the 'sssd' profile, the other for the 'local' profile. I read Fedora Magazine's article on Fedora 40 migrating to the new 'local' profile and noticed the default local profile does not include fingerprint readers which piqued my interest since the logs mention both fingerprint and smartcard readers, but I don't have either. Long story short, I switched to authselect's local profile and the problem almost goes away... With the local profile I see the locks screen shake when I press the sleep button and my system then sleeps without any further action on my part. My password is accepted at the first attempt when I wake my system as it should be. I do however still see broken PAM conversation errors in journalctl indicating this is not a true fix. If you are using authselect's local profile it may explain why you haven't noticed your password being rejected. I'd still like to track down the cause and help fix whatever the issue is :-) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #17 from Sophie Dexter --- (In reply to Sophie Dexter from comment #16) Just to add, fingerprint readers do not seem to be the issue since en/disabling their use through authselect makes no difference -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490924] The first password attempt is rejected after system wakes from sleep.
https://bugs.kde.org/show_bug.cgi?id=490924 --- Comment #19 from Sophie Dexter --- (In reply to Fabian Vogt from comment #18) > Can you please try this (with the working local config as base): > > "authsufficient pam_sss.so > forward_pass" > > after pam_unix (this should bring the issue back) and then Yes it did! > > "authsufficient pam_sss.so > use_first_pass" > > instead? I wonder whether that avoids the issue as well. Please keep a local > root shell open when editing PAM config. and, yes it did :-) I used 'sudo vi /etc/authselect/password-auth' when editing, unsure what I was supposed to do/see with the root shell though,? > If this works, the PAM_CONV_ERR return does not fully quit the PAM stack and > it just gets stuck at pam_sss. > The fix would be to return PAM_CONV_ERR until pam_authenticate returns > failure. Great!, umm, how :?: -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 502212] New: Password asked twice when updating both snap and regular packages
https://bugs.kde.org/show_bug.cgi?id=502212 Bug ID: 502212 Summary: Password asked twice when updating both snap and regular packages Classification: Applications Product: Discover Version: 6.1.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: dextermagni...@yahoo.fr CC: aleix...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Ensure there are both Snap and regular packages to update 2. select all and run the update OBSERVED RESULT sudo password twice, one time for updating the snap packages, and another time for updating the regular packages EXPECTED RESULT password asked once and kept cached for some period of time SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: 6.11.0-19-generic (64-bit) KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 501131] New: Color picking Cross not shown on click
https://bugs.kde.org/show_bug.cgi?id=501131 Bug ID: 501131 Summary: Color picking Cross not shown on click Classification: Plasma Product: kdeplasma-addons Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color Picker Assignee: plasma-b...@kde.org Reporter: dextermagni...@yahoo.fr CC: k...@privat.broulik.de Target Milestone: --- SUMMARY Picking a color through the color picker plasma widget does not work anymore. STEPS TO REPRODUCE 1. Click on on the "pick a color from the desktop" part of the color picker OBSERVED RESULT Nothing happens. Cross to pick color not shown. Cannot pick color. Behavior is as if the button had not effect at all: even the toolitp does not disappear. EXPECTED RESULT Cross to pick color appears and widget waits for the user to click somewhere SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 24.10, Kernel 6.11.0-18-generic (64-bit) KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 140163] HTML Export : better export using appropriate classes
https://bugs.kde.org/show_bug.cgi?id=140163 Dexter Magnific changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 309538] Konqueror does not offer a 'clean data on exit' preference
https://bugs.kde.org/show_bug.cgi?id=309538 Dexter Magnific changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 132854] Make the status bar text widget selectable
https://bugs.kde.org/show_bug.cgi?id=132854 Dexter Magnific changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 132860] structure view should only unfold the last element recursively
https://bugs.kde.org/show_bug.cgi?id=132860 Dexter Magnific changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 156220] page encoding settings lost when opening link in a new tab
https://bugs.kde.org/show_bug.cgi?id=156220 Dexter Magnific changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 142720] remember how document structure is collapsed
https://bugs.kde.org/show_bug.cgi?id=142720 Dexter Magnific changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[calligraformula] [Bug 136710] TeX export : WARNING: malformed data: sequence inside sequence.
https://bugs.kde.org/show_bug.cgi?id=136710 Dexter Magnific changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 136762] preprocessing for html content
https://bugs.kde.org/show_bug.cgi?id=136762 Dexter Magnific changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356090] Plasmashell crashes often
https://bugs.kde.org/show_bug.cgi?id=356090 Gordon Dexter changed: What|Removed |Added CC||kmputer...@gmail.com --- Comment #4 from Gordon Dexter --- This shouldn't be marked as a duplicate of that bug. It has nothing to do with POP or Akondai as far as I can tell. I'm getting crashes of plasma shell as much as several times an hour during normal use in my Proxmox KVM running Kubuntu 16.04 (just upgraded from 14.04) with qxl display driver. I've tried to attach the crash report to this bug but the crash reporter doesn't seem to want to let me because it's marked as a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356090] Plasmashell crashes often
https://bugs.kde.org/show_bug.cgi?id=356090 --- Comment #5 from Gordon Dexter --- Just copied and pasted this from DrKonqui Backtrace of the crash I experienced: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f258db378c0 (LWP 2796))] Thread 10 (Thread 0x7f24c3600700 (LWP 3050)): #0 0x7f258823ee8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f2584fd439c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2584fd44ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2588b6ba9b in QEventDispatcherGlib::processEvents (this=0x7f24bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f2588b12dea in QEventLoop::exec (this=this@entry=0x7f24c35ffcc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f258892f8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f24c5ade7d7 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f258893484e in QThreadPrivate::start (arg=0x34e32a0) at thread/qthread_unix.cpp:331 #8 0x7f2587a216fa in start_thread (arg=0x7f24c3600700) at pthread_create.c:333 #9 0x7f258824ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f25589fe700 (LWP 2898)): #0 0x7f258823a9cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f2585017740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2584fd3e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2584fd4340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2584fd44ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2588b6ba9b in QEventDispatcherGlib::processEvents (this=0x7f24d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f2588b12dea in QEventLoop::exec (this=this@entry=0x7f25589fdc90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f258892f8a4 in QThread::exec (this=this@entry=0x2ac6ce0) at thread/qthread.cpp:503 #8 0x7f258bb5ded6 in QQuickPixmapReader::run (this=0x2ac6ce0) at util/qquickpixmapcache.cpp:817 #9 0x7f258893484e in QThreadPrivate::start (arg=0x2ac6ce0) at thread/qthread_unix.cpp:331 #10 0x7f2587a216fa in start_thread (arg=0x7f25589fe700) at pthread_create.c:333 #11 0x7f258824ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f255b3ef700 (LWP 2873)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f258d57cbd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f258d57cc19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f2587a216fa in start_thread (arg=0x7f255b3ef700) at pthread_create.c:333 #4 0x7f258824ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f2560d3d700 (LWP 2868)): #0 0x7f2584fd13c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2584fd3cfa in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2584fd4340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2584fd44ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2588b6ba9b in QEventDispatcherGlib::processEvents (this=0x7f25540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f2588b12dea in QEventLoop::exec (this=this@entry=0x7f2560d3cce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f258892f8a4 in QThread::exec (this=this@entry=0x28f3490) at thread/qthread.cpp:503 #7 0x7f258b1d73c5 in QQmlThreadPrivate::run (this=0x28f3490) at qml/ftw/qqmlthread.cpp:141 #8 0x7f258893484e in QThreadPrivate::start (arg=0x28f3490) at thread/qthread_unix.cpp:331 #9 0x7f2587a216fa in start_thread (arg=0x7f2560d3d700) at pthread_create.c:333 #10 0x7f258824ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f2562bf6700 (LWP 2843)): #0 0x7f2584fd3dd1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2584fd4340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2584fd44ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2588b6ba9b in QEventDispatcherGlib::processEvents (this=0x7f255c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f2588b12dea in QEventLoop::exec (this=this@entry=0x7f2562bf5ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f258892f8a4 in QThread::exec (this=this@entry=0x2824130) at thread/qthread.cpp:503 #6 0x7f258b1d73c5 in QQmlThreadPrivate::run (this=0x2824130) at qml/ftw/qqmlthread.cpp:141 #7 0x7f258893484e in QThreadPrivate::start (arg=0x2824130) at thread/qthrea
