[kmail2] [Bug 470097] KMail crashes on close
https://bugs.kde.org/show_bug.cgi?id=470097 Allan Sandfeld changed: What|Removed |Added Assignee|kdepim-b...@kde.org |k...@carewolf.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 470097] KMail crashes on close
https://bugs.kde.org/show_bug.cgi?id=470097 Allan Sandfeld changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 470097] KMail crashes on close
https://bugs.kde.org/show_bug.cgi?id=470097 --- Comment #14 from Allan Sandfeld --- This crash: https://invent.kde.org/pim/kmail/-/merge_requests/121 Another crash afterwards: https://invent.kde.org/pim/libkdepim/-/merge_requests/17 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 470097] KMail crashes on close
https://bugs.kde.org/show_bug.cgi?id=470097 --- Comment #13 from Allan Sandfeld --- So something is listening to destroyed and then doing an update of the model during the destruction. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 470097] KMail crashes on close
https://bugs.kde.org/show_bug.cgi?id=470097 --- Comment #10 from Allan Sandfeld --- Valgrind memcheck said nothing useful -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 470097] KMail crashes on close
https://bugs.kde.org/show_bug.cgi?id=470097 --- Comment #9 from Allan Sandfeld --- Might need an address sanitized build of Qt to see where we access something already deleted and where it was already deleted. Unless we can get valgrind to do that or have another tool for it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 479640] New: QML not working with Qt 6.7.0 beta 2
https://bugs.kde.org/show_bug.cgi?id=479640
Bug ID: 479640
Summary: QML not working with Qt 6.7.0 beta 2
Classification: Frameworks and Libraries
Product: frameworks-kirigami
Version: Master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: k...@carewolf.com
CC: m...@ratijas.tk, notm...@gmail.com
Target Milestone: Not decided
kf.kcmutils: Error loading QML file qrc:/kcm/kcm_landingpage/main.qml
kf.kcmutils: qrc:/kcm/kcm_landingpage/main.qml:18:1: Type KCM.SimpleKCM
unavailable
KCM.SimpleKCM {
^
kf.kcmutils: qrc:/qt/qml/org/kde/kcmutils/SimpleKCM.qml:33:1: Type
Kirigami.ScrollablePage unavailable
Kirigami.ScrollablePage {
^
kf.kcmutils:
file:///opt/kde6/lib/x86_64-linux-gnu/qml/org/kde/kirigami/ScrollablePage.qml:67:1:
Type Kirigami.Page unavailable
Kirigami.Page {
^
kf.kcmutils:
file:///opt/kde6/lib/x86_64-linux-gnu/qml/org/kde/kirigami/Page.qml:237:13:
Type Kirigami.PageRow unavailable
property Kirigami.PageRow row
^
kf.kcmutils:
file:///opt/kde6/lib/x86_64-linux-gnu/qml/org/kde/kirigami/PageRow.qml:180:5:
Type OverlayDrawer unavailable
property OverlayDrawer leftSidebar
^
kf.kcmutils:
file:///opt/kde6/lib/x86_64-linux-gnu/qml/org/kde/kirigami/OverlayDrawer.qml:22:1:
Type KT.OverlayDrawer unavailable
KT.OverlayDrawer {
^
kf.kcmutils:
file:///opt/kde6/lib/x86_64-linux-gnu/qml/org/kde/kirigami/templates/OverlayDrawer.qml:120:56:
Cannot assign object of type "KTP.IconPropertiesGroup" to property of type
"IconPropertiesGroup_QMLTYPE_91*" as the former is neither the same as the
latter nor a sub-class of it.
property KTP.IconPropertiesGroup handleClosedIcon:
KTP.IconPropertiesGroup {
^
So the type given to the property is somehow not the same as the one used for
constructing the object. When commented out the next error is:
kf.kcmutils:
file:///opt/kde6/lib/x86_64-linux-gnu/qml/org/kde/kirigami/templates/OverlayDrawer.qml:101:63:
Cannot assign object of type "KTP.IconPropertiesGroup" to property of type
"IconPropertiesGroup_QMLTYPE_58*" as the former is neither the same as the
latter nor a sub-class of it.
readonly property KTP.IconPropertiesGroup handleOpenIcon:
KTP.IconPropertiesGroup
And once that is commented out, things work but we still get these errors in
the konsole:
ile:///opt/kde6/lib/x86_64-linux-gnu/qml/org/kde/kirigami/ApplicationItem.qml:95:
TypeError: Cannot call method 'forceActiveFocus' of null
file:///opt/kde6/lib/x86_64-linux-gnu/qml/org/kde/kirigami/templates/AbstractApplicationHeader.qml:39:5:
Unable to assign PageRow_QMLTYPE_213_QML_250 to PageRow_QMLTYPE_9
file:///opt/kde6/lib/x86_64-linux-gnu/qml/org/kde/kirigami/private/globaltoolbar/PageRowGlobalToolBarUI.qml:138:13:
Unable to assign PageRow_QMLTYPE_213_QML_250 to PageRow_QMLTYPE_9
file:///opt/kde6/lib/x86_64-linux-gnu/qml/org/kde/kirigami/Page.qml:203: Error:
Cannot assign QObject* to PageRow_QMLTYPE_9*
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 479639] Crash on exit
https://bugs.kde.org/show_bug.cgi?id=479639 --- Comment #1 from Allan Sandfeld --- Note this with Qt 6.7.0 Beta2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 479639] New: Crash on exit
https://bugs.kde.org/show_bug.cgi?id=479639 Bug ID: 479639 Summary: Crash on exit Classification: Applications Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@carewolf.com Target Milestone: --- SUMMARY *** 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. exit kmail 2. observe crash 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 Thread 1 "kmail" received signal SIGSEGV, Segmentation fault. 0x7fffeb696b80 in QObject::staticMetaObject () from /opt/qt6/lib/libQt6Core.so.6 (gdb) bt #0 0x7fffeb696b80 in QObject::staticMetaObject () at /opt/qt6/lib/libQt6Core.so.6 #1 0x7fffe8a2e643 in KSelectionProxyModel::columnCount(QModelIndex const&) const (this=0x55eb51c0, index=...) at /src/kdesrc/kitemmodels/src/core/kselectionproxymodel.cpp:2362 #2 0x7fffeb446371 in QSortFilterProxyModelPrivate::find_source_sort_column() const (this=this@entry=0x55e956d0) at /src/qt5/qtbase/src/corelib/itemmodels/qsortfilterproxymodel.cpp:660 #3 0x7fffeb44fd51 in QSortFilterProxyModelPrivate::_q_clearMapping() (this=0x55e956d0) at /src/qt5/qtbase/src/corelib/itemmodels/qsortfilterproxymodel.cpp:468 #4 0x7fffeb45403e in QSortFilterProxyModelPrivate::_q_sourceReset() (this=0x55e956d0) at /src/qt5/qtbase/src/corelib/itemmodels/qsortfilterproxymodel.cpp:1587 #5 0x7fffeb1dc4dd in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffbb10, r=0x55f4e570, this=) at /src/qt5/build2/qtbase/include/QtCore/../../../../qtbase/src/corelib/kernel/qobjectdefs_impl.h:469 #6 doActivate(QObject*, int, void**) (sender=0x55eb51c0, signal_index=21, argv=0x7fffbb10) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:4043 #7 0x7fffeb1d3f07 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7fffeb6a0c80 , local_signal_index=local_signal_index@entry=18, argv=argv@entry=0x7fffbb10) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:4103 #8 0x7fffeb3febd1 in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) (this=, _t1=...) at /src/qt5/build2/qtbase/src/corelib/Core_autogen/include/moc_qabstractitemmodel.cpp:1110 #9 0x7fffeb1dc4dd in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffbc20, r=0x55eb51c0, this=) at /src/qt5/build2/qtbase/include/QtCore/../../../../qtbase/src/corelib/kernel/qobjectdefs_impl.h:469 #10 doActivate(QObject*, int, void**) (sender=0x55f64970, signal_index=7, argv=0x7fffbc20) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:4043 #11 0x7fffeb1d3f07 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7fffeb6a18c0 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fffbc20) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:4103 #12 0x7fffeb41aa66 in QItemSelectionModel::modelChanged(QAbstractItemModel*) (this=, _t1=) at /src/qt5/build2/qtbase/src/corelib/Core_autogen/include/moc_qitemselectionmodel.cpp:518 #13 0x7fffeb1dc4dd in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffbd30, r=0x55f64970, this=) at /src/qt5/build2/qtbase/include/QtCore/../../../../qtbase/src/corelib/kernel/qobjectdefs_impl.h:469 #14 doActivate(QObject*, int, void**) (sender=0x55b523d0, signal_index=0, argv=0x7fffbd30) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:4043 #15 0x7fffeb1d3f07 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) --Type for more, q to quit, c to continue without paging-- (sender=sender@entry=0x55b523d0, m=m@entry=0x7fffeb696b80 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffbd30) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:4103 #16 0x7fffeb1d3fc3 in QObject::destroyed(QObject*) (this=this@entry=0x55b523d0, _t1=, _t1@entry=0x55b523d0) at /src/qt5/build2/qtbase/src/corelib/kernel/moc_qobject.cpp:227 #17 0x7fffeb1d9c62 in QObject::~QObject() (this=0x55b523d0, __in_chrg=) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:1070 #18 0x7fffea52e06d in MailCommon::FolderTreeWidgetProxyModel::~FolderTreeWidgetProxyModel() (this=0x55b523d0, __in_chrg=) at /src/kdesrc/mailcommon/src/folder/foldertreewidgetproxymodel.cpp:91 #19 0x7fffeb1d4ba9 in QObjectPrivate::deleteChildren() (this=this@entry=0x55b17180) at
[Welcome Center] [Bug 472345] New: Crash on launch on first logon to Plasma6
https://bugs.kde.org/show_bug.cgi?id=472345
Bug ID: 472345
Summary: Crash on launch on first logon to Plasma6
Classification: Applications
Product: Welcome Center
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: k...@carewolf.com
CC: n...@kde.org
Target Milestone: ---
Application: plasma-welcome (5.27.80)
(Compiled from sources)
Qt Version: 6.5.2
Frameworks Version: 5.240.0
Operating System: Linux 6.2.0-23-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.04
DrKonqi: 5.27.80 [KCrashBackend]
-- Information about the crash:
The welcome app comes up as a crash immediately on first login.
The crash can be reproduced every time.
-- Backtrace:
Application: Welcome Center (plasma-welcome), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 0x7f082ff21aec in std::__uniq_ptr_impl >::_M_ptr (this=) at
/usr/include/c++/12/bits/unique_ptr.h:191
#7 std::unique_ptr >::get (this=) at
/usr/include/c++/12/bits/unique_ptr.h:462
#8 qGetPtrHelper > const> (ptr=...) at
/opt/qt6/include/QtCore/qtclasshelpermacros.h:79
#9 KSycocaEntry::d_func (this=) at
/src/kdesrc/frameworks/kservice/src/sycoca/ksycocaentry.h:137
#10 KSycocaEntry::name (this=0x0) at
/src/kdesrc/frameworks/kservice/src/sycoca/ksycocaentry.cpp:92
#11 0x5559d046df04 in ApplicationInfo::setDesktopName (this=0x5559d1bec7d0,
desktopName=...) at /opt/qt6/include/QtCore/qshareddata.h:132
#12 0x7f082f2dcb06 in QQmlPropertyData::writeProperty (this=, target=, value=, flags=) at
/src/qt5/build2/qtbase/include/QtQml/6.5.2/QtQml/private/../../../../../../../qtdeclarative/src/qml/qml/qqmlpropertydata_p.h:339
#13 0x7f082f2dbedb in GenericBinding<10>::doStore (flags=...,
pd=0x7f081423b780, value=..., this=0x5559d1acdcb0) at
/src/qt5/qtdeclarative/src/qml/qml/qqmlbinding.cpp:275
#14 GenericBinding<10>::write (this=0x5559d1acdcb0, result=...,
isUndefined=, flags=...) at
/src/qt5/qtdeclarative/src/qml/qml/qqmlbinding.cpp:256
#15 0x7f082f2d73a8 in QQmlBinding::doUpdate (this=0x5559d1acdcb0,
watcher=..., flags=..., scope=...) at
/src/qt5/qtdeclarative/src/qml/qml/qqmlbinding.cpp:700
#16 0x7f082f2d93c1 in QQmlBinding::update (this=0x5559d1acdcb0, flags=...)
at /src/qt5/qtdeclarative/src/qml/qml/qqmlbinding.cpp:164
#17 0x7f082f374ef3 in QQmlObjectCreator::finalize (this=0x5559d18f6200,
interrupt=...) at /src/qt5/qtdeclarative/src/qml/qml/qqmlobjectcreator.cpp:1434
#18 0x7f082f2f1715 in QQmlComponentPrivate::complete
(enginePriv=0x5559d161df40, state=state@entry=0x5559d1671c30) at
/src/qt5/build2/qtbase/include/QtQml/6.5.2/QtQml/private/../../../../../../../qtdeclarative/src/qml/qml/ftw/qbipointer_p.h:131
#19 0x7f082f2f7491 in QQmlComponentPrivate::completeCreate
(this=0x5559d1671b80) at
/src/qt5/qtdeclarative/src/qml/qml/qqmlcomponent.cpp:1241
#20 0x7f082f2f7d29 in QQmlComponent::completeCreate (this=0x5559d1672950)
at /src/qt5/qtdeclarative/src/qml/qml/qqmlcomponent.cpp:1219
#21 QQmlComponentPrivate::createWithProperties (this=0x5559d1671b80,
parent=parent@entry=0x0, properties=..., context=,
behavior=behavior@entry=QQmlComponentPrivate::CreateDefault) at
/src/qt5/qtdeclarative/src/qml/qml/qqmlcomponent.cpp:957
#22 0x7f082f2f7fcc in QQmlComponent::create (this=,
context=) at
/src/qt5/qtdeclarative/src/qml/qml/qqmlcomponent.cpp:908
#23 0x7f082f2d4df3 in QQmlApplicationEnginePrivate::finishLoad
(this=0x5559d161df40, c=0x5559d1672950) at
/src/qt5/qtdeclarative/src/qml/qml/qqmlapplicationengine.cpp:135
#24 0x7f082f2d4ff3 in QQmlApplicationEnginePrivate::ensureLoadingFinishes
(this=, c=) at
/src/qt5/qtdeclarative/src/qml/qml/qqmlapplicationengine.cpp:162
#25 0x7f082f2d5190 in QQmlApplicationEnginePrivate::startLoad
(this=, url=..., data=..., dataFlag=) at
/src/qt5/qtdeclarative/src/qml/qml/qqmlapplicationengine.cpp:109
#26 0x7f082f2d5420 in QQmlApplicationEngine::load
(this=this@entry=0x7ffc391ae880, url=...) at
/src/qt5/qtdeclarative/src/qml/qml/qqmlapplicationengine.cpp:324
#27 0x5559d0469f38 in main (argc=, argv=) at
/src/kdesrc/kde/workspace/plasma-welcome/src/main.cpp:88
[Inferior 1 (process 8354) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kdelibs] [Bug 76082] smooth scrolling in all apps
https://bugs.kde.org/show_bug.cgi?id=76082 Allan Sandfeld changed: What|Removed |Added CC|k...@carewolf.com| -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461410] New: Crash on closing ssh connection
https://bugs.kde.org/show_bug.cgi?id=461410
Bug ID: 461410
Summary: Crash on closing ssh connection
Classification: Applications
Product: konsole
Version: 22.08.1
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: konsole-de...@kde.org
Reporter: k...@carewolf.com
Target Milestone: ---
Application: konsole (22.08.1)
(Compiled from sources)
Qt Version: 5.15.11
Frameworks Version: 5.100.0
Operating System: Linux 5.15.0-52-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04.1 LTS
DrKonqi: 5.25.5 [KCrashBackend]
-- Information about the crash:
Seems the whole of konsole now crashes when I close an ssh connection with
CTRL+D.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 QHash::findNode (ahp=0x0,
akey=: Konsole::Profile::Name, this=0x55a7e4281800) at
/opt/qt5/include/QtCore/qhash.h:940
#7 QHash::contains (akey=: Konsole::Profile::Name, this=0x55a7e4281800) at
/opt/qt5/include/QtCore/qhash.h:920
#8 Konsole::Profile::property (p=Konsole::Profile::Name,
this=0x55a7e42817f0) at
/src/kdesrc/kde/applications/konsole/src/profile/Profile.h:830
#9 Konsole::Profile::property (p=Konsole::Profile::Name,
this=0x55a7e42817f0) at
/src/kdesrc/kde/applications/konsole/src/profile/Profile.h:824
#10 Konsole::Profile::name (this=0x55a7e42817f0) at
/src/kdesrc/kde/applications/konsole/src/profile/Profile.h:469
#11 operator() (pr=..., __closure=, pr=..., __closure=) at
/src/kdesrc/kde/applications/konsole/src/plugins/SSHManager/sshmanagermodel.cpp:232
#12 0x7f6ac4f5bb88 in
__gnu_cxx::__ops::_Iter_pred
>::operator() >::iterator>
(__it=..., this=) at
/usr/include/c++/11/bits/predefined_ops.h:317
#13 std::__find_if
>::iterator,
__gnu_cxx::__ops::_Iter_pred > > (__pred=..., __last=..., __first=...) at
/usr/include/c++/11/bits/stl_algobase.h:2094
#14 std::__find_if
>::iterator,
__gnu_cxx::__ops::_Iter_pred > > (__first=..., __last=..., __first=...,
__last=..., __pred=...) at /usr/include/c++/11/bits/stl_algobase.h:2115
#15 std::find_if
>::iterator, SSHManagerModel::triggerProfileChange(const
QString&):: > (__first=..., __last=..., __first=...,
__last=..., __pred=...) at /usr/include/c++/11/bits/stl_algo.h:3911
#16 SSHManagerModel::triggerProfileChange (this=0x55a7e41e0f90, sshHost=...) at
/src/kdesrc/kde/applications/konsole/src/plugins/SSHManager/sshmanagermodel.cpp:233
#17 0x7f6accb295ce in QtPrivate::QSlotObjectBase::call (a=0x7ffed2929e10,
r=0x55a7e41e0f90, this=0x55a7e48d2560) at
../../include/QtCore/../../../../qtbase/src/corelib/kernel/qobjectdefs_impl.h:398
#18 doActivate (sender=0x55a7e4714e40, signal_index=22,
argv=0x7ffed2929e10) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:3925
#19 0x7f6accb223c7 in QMetaObject::activate
(sender=sender@entry=0x55a7e4714e40, m=m@entry=0x7f6ace0470e0
,
local_signal_index=local_signal_index@entry=19, argv=argv@entry=0x7ffed2929e10)
at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:3985
#20 0x7f6acdf943a9 in Konsole::Session::hostnameChanged
(this=this@entry=0x55a7e4714e40, _t1=...) at
/src/kdesrc/build/kde/applications/konsole/src/session/konsolesession_autogen/EWIEGA46WW/moc_Session.cpp:833
#21 0x7f6acdf9b95d in Konsole::Session::getDynamicTitle
(this=0x55a7e4714e40) at
/src/kdesrc/kde/applications/konsole/src/session/Session.cpp:1132
#22 0x7f6acdfb0460 in Konsole::SessionController::snapshot
(this=0x55a7e469d9d0) at
/src/kdesrc/kde/applications/konsole/src/session/SessionController.cpp:329
#23 0x7f6accb295ce in QtPrivate::QSlotObjectBase::call (a=0x7ffed292a100,
r=0x55a7e469d9d0, this=0x55a7e47b5220) at
../../include/QtCore/../../../../qtbase/src/corelib/kernel/qobjectdefs_impl.h:398
#24 doActivate (sender=0x55a7e45f5db0, signal_index=3,
argv=0x7ffed292a100) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:3925
#25 0x7f6accb223c7 in QMetaObject::activate (sender=,
m=m@entry=0x7f6accdd5cc0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffed292a100)
at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:3985
#26 0x7f6accb2d6ce in QTimer::timeout (this=, _t1=...) at
.moc/moc_qtimer.cpp:205
#27 0x7f6accb1ec1f in QObject::event (this=0x55a7e45f5db0,
e=0x7ffed292a280) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:1369
#28 0x7f6acd737e33 in QApplicationPrivate::notify_helper (this=, receiver=0x55a7e45f5db0, e=0x7ffed292a280) at
/src/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3640
#29 0x7f6accaf03e8 in QCoreApplication::notifyInternal2
(receiver=0x55a7e45f5db0, event=0x7ffed292a280) at
/src/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:1064
#30 0x7f6accb4bf91 in QTimerInfoList::activateTimers (this=0x55a7e4161c30)
at
[KScreen] [Bug 406377] Add "Extend to top/bottom" options to OSD and applet
https://bugs.kde.org/show_bug.cgi?id=406377 Allan Sandfeld changed: What|Removed |Added CC||hsan...@gmail.com --- Comment #12 from Allan Sandfeld --- *** Bug 395716 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 395716] Option to extend up or extend down
https://bugs.kde.org/show_bug.cgi?id=395716 Allan Sandfeld changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||k...@carewolf.com Resolution|--- |DUPLICATE --- Comment #1 from Allan Sandfeld --- *** This bug has been marked as a duplicate of bug 406377 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401581] Win+P still assumes the monitors position wrongly, ignoring the Display Configuration.
https://bugs.kde.org/show_bug.cgi?id=401581 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Allan Sandfeld --- I believe I have fixed that with my recent patch. It will now extend from the primary screen, and not change primary screeen. As far as I know the fix will be in 5.27.. Reopen if this isnt a sufficient solution. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 404244] Select primary display from display switch OSD
https://bugs.kde.org/show_bug.cgi?id=404244 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com --- Comment #1 from Allan Sandfeld --- I have changed the logic to extend from the primary screen. So one way to set primary screen now, is clicking to "only" the screen you want primary, and then click extend. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 458024] When extended left/right, external monitor is placed with top edge aligned to internal monitor, not bottom edge
https://bugs.kde.org/show_bug.cgi?id=458024 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com --- Comment #2 from Allan Sandfeld --- Personally I prefer to have it smaller screens centered compared to the big screen. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 454322] New: Crash on checking IMAP
https://bugs.kde.org/show_bug.cgi?id=454322
Bug ID: 454322
Summary: Crash on checking IMAP
Product: Akonadi
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: IMAP resource
Assignee: kdepim-b...@kde.org
Reporter: k...@carewolf.com
Target Milestone: ---
Application: akonadi_imap_resource (5.20.2 (22.04.2))
(Compiled from sources)
Qt Version: 5.15.10
Frameworks Version: 5.95.0
Operating System: Linux 5.17.0-1-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux bookworm/sid
DrKonqi: 5.24.90 [KCrashBackend]
-- Information about the crash:
On work account not used for over a year, updated KDE, first check on one of
the accounts crashed in an assert.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Allstar (akonadi_imap_resource), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#6 0x7f2c59832546 in __GI_abort () at abort.c:79
#7 0x7f2c59cba0b5 in QMessageLogger::fatal(char const*, ...) const () from
/opt/qt-5.15/lib/libQt5Core.so.5
#8 0x7f2c59cb952e in qt_assert(char const*, char const*, int) () from
/opt/qt-5.15/lib/libQt5Core.so.5
#9 0x7f2c5c010894 in KIMAP::ImapSet::add (this=0x7ffddb16ab20, values=...)
at /src/kdesrc/kde/pim/kimap/src/imapset.cpp:240
#10 0x7f2c5c0105a4 in KIMAP::ImapSet::ImapSet (this=0x7ffddb16ab20,
value=-1) at /src/kdesrc/kde/pim/kimap/src/imapset.cpp:194
#11 0x55dbd65159dd in RetrieveItemTask::triggerFetchJob
(this=0x7f2c4402c370) at
/src/kdesrc/kde/pim/kdepim-runtime/resources/imap/retrieveitemtask.cpp:63
#12 0x55dbd6515949 in RetrieveItemTask::onSelectDone (this=0x7f2c4402c370,
job=0x55dbd791bd00) at
/src/kdesrc/kde/pim/kdepim-runtime/resources/imap/retrieveitemtask.cpp:54
#13 0x55dbd6516b50 in QtPrivate::FunctorCall,
QtPrivate::List, void, void (RetrieveItemTask::*)(KJob*)>::call (f=(void
(RetrieveItemTask::*)(RetrieveItemTask * const, KJob *)) 0x55dbd65158d8
, o=0x7f2c4402c370, arg=0x7ffddb16ad70)
at /opt/qt-5.15/include/QtCore/qobjectdefs_impl.h:152
#14 0x55dbd6516a8c in QtPrivate::FunctionPointer::call, void> (f=(void
(RetrieveItemTask::*)(RetrieveItemTask * const, KJob *)) 0x55dbd65158d8
, o=0x7f2c4402c370, arg=0x7ffddb16ad70)
at /opt/qt-5.15/include/QtCore/qobjectdefs_impl.h:185
#15 0x55dbd65168a9 in QtPrivate::QSlotObject, void>::impl (which=1,
this_=0x55dbd7bbb5e0, r=0x7f2c4402c370, a=0x7ffddb16ad70, ret=0x0) at
/opt/qt-5.15/include/QtCore/qobjectdefs_impl.h:418
#16 0x7f2c59f01293 in QtPrivate::QSlotObjectBase::call (a=0x7ffddb16ad70,
r=0x7f2c4402c370, this=0x55dbd7bbb5e0) at
../../include/QtCore/../../../../qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398
#17 doActivate (sender=0x55dbd791bd00, signal_index=6,
argv=0x7ffddb16ad70) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:3923
#18 0x7f2c5b609f63 in KJob::result (this=0x55dbd791bd00,
_t1=0x55dbd791bd00, _t2=...) at
/src/kdesrc/build/frameworks/kcoreaddons/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#19 0x7f2c5b6076c5 in KJob::finishJob (this=0x55dbd791bd00,
emitResult=true) at /src/kdesrc/frameworks/kcoreaddons/src/lib/jobs/kjob.cpp:98
#20 0x7f2c5b608275 in KJob::emitResult (this=0x55dbd791bd00) at
/src/kdesrc/frameworks/kcoreaddons/src/lib/jobs/kjob.cpp:337
#21 0x7f2c5c01999c in KIMAP::Job::handleErrorReplies (this=0x55dbd791bd00,
response=...) at /src/kdesrc/kde/pim/kimap/src/job.cpp:72
#22 0x7f2c5c02f8b8 in KIMAP::SelectJob::handleResponse
(this=0x55dbd791bd00, response=...) at
/src/kdesrc/kde/pim/kimap/src/selectjob.cpp:222
#23 0x7f2c5c032801 in KIMAP::SessionPrivate::responseReceived
(this=0x55dbd7b06b40, response=...) at
/src/kdesrc/kde/pim/kimap/src/session.cpp:288
#24 0x7f2c5c0375c1 in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(KIMAP::SessionPrivate::*)(KIMAP::Response const&)>::call (f=(void
(KIMAP::SessionPrivate::*)(KIMAP::SessionPrivate * const, const KIMAP::Response
&)) 0x7f2c5c031f60 , o=0x55dbd7b06b40, arg=0x7f2c28042a38) at
/opt/qt-5.15/include/QtCore/qobjectdefs_impl.h:152
#25 0x7f2c5c036fb6 in QtPrivate::FunctionPointer::call, void> (f=(void
(KIMAP::SessionPrivate::*)(KIMAP::SessionPrivate * const, const KIMAP::Response
&)) 0x7f2c5c031f60 , o=0x55dbd7b06b40, arg=0x7f2c28042a38) at
/opt/qt-5.15/include/QtCore/qobjectdefs_impl.h:185
#26 0x7f2c5c0364ed in QtPrivate::QSlotObject, void>::impl (which=1,
this_=0x55dbd7c2a280, r=0x55dbd7b06b40, a=0x7f2c28042a38, ret=0x0) at
/opt/qt-5.15/include/QtCore/qobjectdefs_impl.h:418
#27 0x7f2c59ef74a6 in QObject::event (this=0x55dbd7b06b40,
e=0x7f2c280429f0) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:1347
#28 0x7f2c5ab0b82f in
[Breeze] [Bug 453692] Window drag from style doesn't work with QtWebEngine
https://bugs.kde.org/show_bug.cgi?id=453692 Allan Sandfeld changed: What|Removed |Added CC||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 453692] New: Window drag from style doesn't work with QtWebEngine
https://bugs.kde.org/show_bug.cgi?id=453692 Bug ID: 453692 Summary: Window drag from style doesn't work with QtWebEngine Product: Breeze Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: plasma-b...@kde.org Reporter: k...@carewolf.com CC: noaha...@gmail.com Target Milestone: --- SUMMARY If you click inside a QWebEngineView you can no longer drag the window from unused parts of the menu or toolbar ADDITIONAL INFORMATION This bug appears to have been introduced in 2021 with the commit 614a780d45fc600735c1893e3a0aa2a633cd31e1 "Start the window drag from the QStyle" In particular a logic bug means that _eventInQQuickWidget is never set to false (it is set to false after an if statement that exits), see kstyle/breezewindowmanager.cpp:340-350 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 440936] New: Konversation crashes on network reconfiguration and laptop sleep
https://bugs.kde.org/show_bug.cgi?id=440936 Bug ID: 440936 Summary: Konversation crashes on network reconfiguration and laptop sleep Product: konversation Version: 1.8.21041 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: k...@carewolf.com Target Milestone: --- Application: konversation (1.8.21041) (Compiled from sources) Qt Version: 5.15.4 Frameworks Version: 5.83.0 Operating System: Linux 5.11.0-25-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: Enabling a new network in plasma-nm or. Waking the laptop a place with a new already known network. The crash can be reproduced every time. -- Backtrace: Application: Konversation (konversation), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f3f6dcae000 (LWP 920276))] [KCrash Handler] #6 0x7f3f721e975a in operator== (s1=..., s2=...) at /src/qt5/qtbase/src/corelib/text/qstring.cpp:3432 #7 0x563b52d00b0d in NickInfo::setAccount (this=0x0, name=...) at /src/kdesrc/kde/kdenetwork/konversation/src/irc/nickinfo.cpp:250 #8 0x563b52d180ac in InputFilter::parseClientCommand (this=this@entry=0x563b54121c60, prefix=..., command=..., parameterList=..., messageTags=...) at /opt/qt5/include/QtCore/qshareddata.h:160 #9 0x563b52d1966a in InputFilter::parseLine (this=this@entry=0x563b54121c60, line=...) at /src/kdesrc/kde/kdenetwork/konversation/src/irc/inputfilter.cpp:123 #10 0x563b52ccf521 in Server::processIncomingData (this=0x563b54121b40) at /src/kdesrc/kde/kdenetwork/konversation/src/irc/server.cpp:1366 #11 0x7f3f7238a911 in QtPrivate::QSlotObjectBase::call (a=0x7ffe039e7260, r=0x563b54121b40, this=0x563b54333c20) at ../../include/QtCore/../../../../qtbase/src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x563b54121bb0, signal_index=3, argv=argv@entry=0x7ffe039e7260) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:3886 #13 0x7f3f72383748 in QMetaObject::activate (sender=, m=m@entry=0x7f3f72644c60 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe039e7260) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:3946 #14 0x7f3f7238ea5e in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #15 0x7f3f7237fbbf in QObject::event (this=0x563b54121bb0, e=0x7ffe039e73c0) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:1336 #16 0x7f3f72eba583 in QApplicationPrivate::notify_helper (this=, receiver=0x563b54121bb0, e=0x7ffe039e73c0) at /src/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3637 #17 0x7f3f72351ca8 in QCoreApplication::notifyInternal2 (receiver=0x563b54121bb0, event=0x7ffe039e73c0) at /src/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:1064 #18 0x7f3f723ad839 in QTimerInfoList::activateTimers (this=0x563b54028170) at /src/qt5/qtbase/src/corelib/kernel/qtimerinfo_unix.cpp:643 #19 0x7f3f723ae1c4 in timerSourceDispatch (source=) at /src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:183 #20 idleTimerSourceDispatch (source=) at /src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:230 #21 0x7f3f706cd8eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f3f70720d28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f3f706cb023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f3f723ae55f in QEventDispatcherGlib::processEvents (this=0x563b54028e40, flags=...) at /src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:423 #25 0x7f3f7235055b in QEventLoop::exec (this=this@entry=0x7ffe039e7600, flags=..., flags@entry=...) at ../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:69 #26 0x7f3f72358d94 in QCoreApplication::exec () at ../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:121 #27 0x563b52c2477b in main (argc=, argv=) at /src/kdesrc/kde/kdenetwork/konversation/src/main.cpp:149 [Inferior 1 (process 920276) detached] Possible duplicates by query: bug 422092, bug 419229, bug 416379, bug 410586, bug 353672. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438602] Crash on opening system settings from plasma network applet
https://bugs.kde.org/show_bug.cgi?id=438602 --- Comment #2 from Allan Sandfeld --- It already stopped happening yesterday. It was only every time Monday.. No idea. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438602] New: Crash on opening system settings from plasma network applet
https://bugs.kde.org/show_bug.cgi?id=438602 Bug ID: 438602 Summary: Crash on opening system settings from plasma network applet Product: systemsettings Version: 5.21.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@carewolf.com Target Milestone: --- Application: systemsettings5 (5.21.5) (Compiled from sources) Qt Version: 5.15.4 Frameworks Version: 5.83.0 Operating System: Linux 5.11.0-17-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: I clicked the configure option for network settings, in the popup window for network in the system tray. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f80ca230d00 (LWP 8879))] [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #7 0x7f80ce172864 in __GI_abort () at abort.c:79 #8 0x7f80ce75c33f in qt_message_fatal (message=..., context=...) at /src/qt5/qtbase/src/corelib/global/qlogging.cpp:1914 #9 QMessageLogger::fatal (this=this@entry=0x7ffce6321020, msg=msg@entry=0x7f80c003f1d0 "Fatal error while loading the sidebar view qml component") at /src/qt5/qtbase/src/corelib/global/qlogging.cpp:893 #10 0x7f80c002eff4 in SidebarMode::initWidget (this=this@entry=0x564220e17200) at /src/kdesrc/kde/workspace/systemsettings/sidebar/SidebarMode.cpp:785 #11 0x7f80c002f021 in SidebarMode::mainWidget (this=0x564220e17200) at /src/kdesrc/kde/workspace/systemsettings/sidebar/SidebarMode.cpp:335 #12 0x56421f64fca5 in SettingsBase::changePlugin (this=0x564220c97be0) at /src/kdesrc/kde/workspace/systemsettings/app/SettingsBase.cpp:421 #13 0x56421f651c7b in SettingsBase::initApplication (this=0x564220c97be0) at /src/kdesrc/kde/workspace/systemsettings/app/SettingsBase.cpp:158 #14 0x7f80ce9b8c7d in QObject::event (this=this@entry=0x564220c97be0, e=e@entry=0x564220e374f0) at /src/qt5/qtbase/src/corelib/kernel/qobject.cpp:1314 #15 0x7f80cf64d5c9 in QWidget::event (this=this@entry=0x564220c97be0, event=event@entry=0x564220e374f0) at /src/qt5/qtbase/src/widgets/kernel/qwidget.cpp:9094 #16 0x7f80cf75e8d0 in QMainWindow::event (this=this@entry=0x564220c97be0, event=event@entry=0x564220e374f0) at /src/qt5/qtbase/src/widgets/widgets/qmainwindow.cpp:1341 #17 0x7f80d023f4e5 in KMainWindow::event (this=this@entry=0x564220c97be0, ev=ev@entry=0x564220e374f0) at /src/kdesrc/frameworks/kxmlgui/src/kmainwindow.cpp:916 #18 0x7f80d027b7fb in KXmlGuiWindow::event (this=0x564220c97be0, ev=0x564220e374f0) at /src/kdesrc/frameworks/kxmlgui/src/kxmlguiwindow.cpp:110 #19 0x7f80cf60c583 in QApplicationPrivate::notify_helper (this=, receiver=0x564220c97be0, e=0x564220e374f0) at /src/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3637 #20 0x7f80ce98aca8 in QCoreApplication::notifyInternal2 (receiver=0x564220c97be0, event=0x564220e374f0) at /src/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:1064 #21 0x7f80ce98d900 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x564220c56810) at /src/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:1821 #22 0x7f80ce9e7f07 in postEventSourceDispatch (s=0x564220cb96a0) at /src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:277 #23 0x7f80cc5e184b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f80cc634c68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f80cc5def83 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f80ce9e755f in QEventDispatcherGlib::processEvents (this=0x564220cce5f0, flags=...) at /src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:423 #27 0x7f80ce98955b in QEventLoop::exec (this=this@entry=0x7ffce6321750, flags=..., flags@entry=...) at ../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:69 #28 0x7f80ce991d94 in QCoreApplication::exec () at ../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:121 #29 0x7f80ceed2d20 in QGuiApplication::exec () at /src/qt5/qtbase/src/gui/kernel/qguiapplication.cpp:1867 #30 0x7f80cf60c4f9 in QApplication::exec () at /src/qt5/qtbase/src/widgets/kernel/qapplication.cpp:2829 #31 0x56421f64c3b0 in main (argc=, argv=0x7ffce6321880) at /src/kdesrc/kde/workspace/systemsettings/app/main.cpp:222 [Inferior 1 (process 8879) detached] Possible duplicates by query: bug 429344, bug 427384, bug 424911, bug 423222, bug 423132. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 436347] SQL injection fail?
https://bugs.kde.org/show_bug.cgi?id=436347 --- Comment #1 from Allan Sandfeld --- It appears it is also present in more recent versions. It has just moved to .cache/krunner -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 436347] New: SQL injection fail?
https://bugs.kde.org/show_bug.cgi?id=436347 Bug ID: 436347 Summary: SQL injection fail? Product: krunner Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: k...@carewolf.com CC: plasma-b...@kde.org Target Milestone: --- Found this directory: carewolf@twilight% ls -l ~/.cache/plasmashell total 96 drwxrwxr-x 4 carewolf carewolf 4096 Mai 29 2017 attica drwxrwxr-x 4 carewolf carewolf 4096 Mai 29 2017 knewstuff drwxrwxr-x 2 carewolf carewolf 4096 Mai 29 2017 KRunner-Favicons-firefox-default drwxrwxr-x 2 carewolf carewolf 4096 Feb 8 16:15 'KRunner-Favicons-SELECT icon FROM icons WHERE url = :url LIMIT 1;' drwxrwxr-x 2 carewolf carewolf 77824 Apr 15 09:55 qmlcache I don't think SQL queries were meant to be in the file-system names. The creation date fits my 5.20.90 build, so it might already be fixed. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418352] Kate crashes when moving selections of text with Crtl+Shift+Arrow keys
https://bugs.kde.org/show_bug.cgi?id=418352 --- Comment #17 from Allan Sandfeld --- (In reply to Dominik Haumann from comment #16) > @Allan: you likely already tested with Qt 5.15.1 or so back then, right? > > I'd assume this issue is fixed then. In October I probably tested with 5.15.2, but yes, couldn't reproduce. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429111] Crash on switching screen profiles
https://bugs.kde.org/show_bug.cgi?id=429111 Allan Sandfeld changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Allan Sandfeld --- *** This bug has been marked as a duplicate of bug 416005 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416005] Crash while adjusting monitor layout and refresh rate in kscreen
https://bugs.kde.org/show_bug.cgi?id=416005 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com --- Comment #12 from Allan Sandfeld --- *** Bug 429111 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429111] New: Crash on switching screen profiles
https://bugs.kde.org/show_bug.cgi?id=429111 Bug ID: 429111 Summary: Crash on switching screen profiles Product: systemsettings Version: 5.20.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@carewolf.com Target Milestone: --- Application: systemsettings5 (5.20.0) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.76.0 Operating System: Linux 5.4.0-53-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Was trying to figure out why the duplicate kscreen entry wasn't working. The crash happened as I was editing the details of disabled screen. The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [New LWP 18763] [New LWP 18764] [New LWP 18769] [New LWP 18770] [New LWP 18774] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f7557913aff in __GI___poll (fds=fds@entry=0x7fff359e85f8, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f75536a3840 (LWP 18761))] Thread 6 (Thread 0x7f7523fff700 (LWP 18774)): #0 0x7f7557913aff in __GI___poll (fds=0x7f751c004a60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f75559701ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f75559702e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7557f2005b in QEventDispatcherGlib::processEvents (this=0x7f751c000b60, flags=...) at /src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7557ec1c8b in QEventLoop::exec (this=this@entry=0x7f7523ffed40, flags=..., flags@entry=...) at ../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:141 #5 0x7f7557cd8b82 in QThread::exec (this=this@entry=0x556e500564b0) at ../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:121 #6 0x7f7556e483f9 in QQmlThreadPrivate::run (this=0x556e500564b0) at /src/qt5/qtdeclarative/src/qml/qml/ftw/qqmlthread.cpp:155 #7 0x7f7557cd9d3b in QThreadPrivate::start (arg=0x556e500564b0) at /src/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:329 #8 0x7f7556293609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f7557920293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f752700 (LWP 18770)): #0 0x7f7557913aff in __GI___poll (fds=0x7f7524004a30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f75559701ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f75559702e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7557f2005b in QEventDispatcherGlib::processEvents (this=0x7f7524000b60, flags=...) at /src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7557ec1c8b in QEventLoop::exec (this=this@entry=0x7f752fffed40, flags=..., flags@entry=...) at ../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:141 #5 0x7f7557cd8b82 in QThread::exec (this=this@entry=0x556e4dac2e40) at ../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:121 #6 0x7f7556e483f9 in QQmlThreadPrivate::run (this=0x556e4dac2e40) at /src/qt5/qtdeclarative/src/qml/qml/ftw/qqmlthread.cpp:155 #7 0x7f7557cd9d3b in QThreadPrivate::start (arg=0x556e4dac2e40) at /src/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:329 #8 0x7f7556293609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f7557920293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f7542643700 (LWP 18769)): #0 0x7f7557913aff in __GI___poll (fds=0x7f7528005240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f75559701ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f75559702e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7557f2005b in QEventDispatcherGlib::processEvents (this=0x7f7528000b60, flags=...) at /src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7557ec1c8b in QEventLoop::exec (this=this@entry=0x7f7542642d40, flags=..., flags@entry=...) at ../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:141 #5 0x7f7557cd8b82 in QThread::exec (this=this@entry=0x556e4dc5b8c0) at ../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:121 #6 0x7f7556e483f9 in QQmlThreadPrivate::run (this=0x556e4dc5b8c0) at /src/qt5/qtdeclarative/src/qml/qml/ftw/qqmlthread.cpp:155 #7
[plasma-pa] [Bug 427936] Audio output reconfigures and fails to restore after KVM swtich
https://bugs.kde.org/show_bug.cgi?id=427936 Allan Sandfeld changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #3 from Allan Sandfeld --- Seems to have been something else being wrong for a period of time. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 427936] Audio output reconfigures and fails to restore after KVM swtich
https://bugs.kde.org/show_bug.cgi?id=427936 --- Comment #2 from Allan Sandfeld --- Not sure what happened. It seems to be working again now. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409183] Using Password based authentication when Oauth2 is selected
https://bugs.kde.org/show_bug.cgi?id=409183 --- Comment #6 from Allan Sandfeld --- Yeah. I looked into it. We basically have two different OAuth2 hacks, one for gmail and one for ews. There is code for in the IMAP and SMTP code but it is all tied up in the GMail specific hack. Then again OAUTH2 is mostly a scam to collect more data on you, which is why they require your already tracked browser to log in. So it is no wonder it isn't properly standardized. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418352] Kate crashes when moving selections of text with Crtl+Shift+Arrow keys
https://bugs.kde.org/show_bug.cgi?id=418352 --- Comment #11 from Allan Sandfeld --- I can't seem to reproduce it. Perhaps it requires a special kate settings? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418352] Kate crashes when moving selections of text with Crtl+Shift+Arrow keys
https://bugs.kde.org/show_bug.cgi?id=418352 --- Comment #10 from Allan Sandfeld --- It is in the garbage collector. Perhaps we have injected an object with the wrong ownership policy and then deleted it underneath JS? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 427936] New: Audio output reconfigures and fails to restore after KVM swtich
https://bugs.kde.org/show_bug.cgi?id=427936 Bug ID: 427936 Summary: Audio output reconfigures and fails to restore after KVM swtich Product: plasma-pa Version: 5.20.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: k...@carewolf.com CC: plasma-b...@kde.org Target Milestone: --- Since updating KDE/Plasma a few days ago, the audio output now remaps every time I switch away from my KDE desktop, and doesn't restore when switching back. The setup is a ThinkPad in a dock, with a KVM connected to the dock and the KVM connected to external speakers. The recent Audio KCM, also lists the external speakers output as "Headphones (unplugged)" for some reason, which is also a recent change. It might get confused from there being both outputs on the laptop and the dock. After switching away and back, the entire audio profile switches from "Analogue Stereo Duplex" to "Digital Stereo (HDMI 2) Output". When selecting back to "Analogue Stereo Duplex" the default output is also "Internal speakers" though speakers are connected to the external port. This used to work with KDE just using the internal speakers when the KVM was handling another computer. The last version I was running was 5.19.4 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427792] New: Crash on exit
https://bugs.kde.org/show_bug.cgi?id=427792 Bug ID: 427792 Summary: Crash on exit Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@carewolf.com Target Milestone: --- Application: kmail (5.15.3 (20.08.3)) (Compiled from sources) Qt Version: 5.15.1 Frameworks Version: 5.76.0 Operating System: Linux 5.4.0-47-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Exiting the application. It looks like a config callback is trying to update some widgets, while the application is deleting itself. Should probably have detached those signal before. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [New LWP 158289] [New LWP 158290] [New LWP 158291] [New LWP 158292] [New LWP 158293] [New LWP 158321] [New LWP 158323] [New LWP 158329] [New LWP 158330] [New LWP 158331] [New LWP 158332] [New LWP 158333] [New LWP 158334] [New LWP 158352] [New LWP 158364] [New LWP 158376] [New LWP 158380] [New LWP 186893] [New LWP 188499] [New LWP 188582] [New LWP 188583] [New LWP 188584] [New LWP 188585] [New LWP 188587] [New LWP 188588] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7ff40dbf396f in __GI___poll (fds=fds@entry=0x7ffc911716f8, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7ff3fe8221c0 (LWP 158287))] Thread 26 (Thread 0x7ff3e4db5700 (LWP 188588)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7ff3e4db4150, clockid=, expected=0, futex_word=0x7ff3e4db42e8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7ff3e4db4150, clockid=, mutex=0x7ff3e4db4298, cond=0x7ff3e4db42c0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7ff3e4db42c0, mutex=0x7ff3e4db4298, abstime=0x7ff3e4db4150) at pthread_cond_wait.c:656 #3 0x7ff4120eefc2 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127 #4 0x7ff4120f01bf in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:213 #5 0x7ff41209e876 in base::internal::WorkerThread::Delegate::WaitForWork(base::WaitableEvent*) () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/task/thread_pool/worker_thread.cc:36 #6 0x7ff4120a6769 in base::internal::WorkerThread::RunWorker() () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/task/thread_pool/worker_thread.cc:311 #7 0x7ff4120a6ea8 in base::internal::WorkerThread::RunPooledWorker() () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/task/thread_pool/worker_thread.cc:224 #8 0x7ff4120f0cde in ThreadFunc() () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/threading/platform_thread_posix.cc:81 #9 0x7ff40a9a8609 in start_thread (arg=) at pthread_create.c:477 #10 0x7ff40dc00103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7ff3cd041700 (LWP 188587)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7ff3cd040150, clockid=, expected=0, futex_word=0x7ff3cd0402e8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7ff3cd040150, clockid=, mutex=0x7ff3cd040298, cond=0x7ff3cd0402c0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7ff3cd0402c0, mutex=0x7ff3cd040298, abstime=0x7ff3cd040150) at pthread_cond_wait.c:656 #3 0x7ff4120eefc2 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127 #4 0x7ff4120f01bf in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:213 #5 0x7ff41209e876 in base::internal::WorkerThread::Delegate::WaitForWork(base::WaitableEvent*) () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/task/thread_pool/worker_thread.cc:36 #6 0x7ff4120a69dc in base::internal::WorkerThread::RunWorker() () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/task/thread_pool/worker_thread.cc:334 #7 0x7ff4120a6ea8 in base::internal::WorkerThread::RunPooledWorker() () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/task/thread_pool/worker_thread.cc:224 #8 0x7ff4120f0cde in ThreadFunc() () at
[Akonadi] [Bug 409183] Using Password based authentication when Oauth2 is selected
https://bugs.kde.org/show_bug.cgi?id=409183 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com --- Comment #4 from Allan Sandfeld --- What OAuth2 support is that? All I could find was specific google oauth support. I think generic OAuth2 is basically missing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 416728] Konsole and Okular with multiple tabs pop up an unnecessary "N open terminals/tabs" warning on logout or shutdown when session restore is in use
https://bugs.kde.org/show_bug.cgi?id=416728 --- Comment #7 from Allan Sandfeld --- Should be fixed by https://phabricator.kde.org/D29873 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 416728] Konsole and Okular with multiple tabs pop up an unnecessary "N open terminals/tabs" warning on logout or shutdown when session restore is in use
https://bugs.kde.org/show_bug.cgi?id=416728 --- Comment #6 from Allan Sandfeld --- (In reply to Allan Sandfeld from comment #5) > So it is a change in what plasma does when logging out? Ah right, read the comments again. So a change in how Qt closes applications. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 416728] Konsole and Okular with multiple tabs pop up an unnecessary "N open terminals/tabs" warning on logout or shutdown when session restore is in use
https://bugs.kde.org/show_bug.cgi?id=416728 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com --- Comment #5 from Allan Sandfeld --- So it is a change in what plasma does when logging out? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422173] Handling missing 'date' in email headers
https://bugs.kde.org/show_bug.cgi?id=422173 --- Comment #7 from Allan Sandfeld --- (In reply to Laurent Montel from comment #1) > Hello, > You're idea is to use "received date" in messagelib for sorting message or > replacing in message directly unknown date by "received date" ? > Regards I seem to remember an option for this back in the day (perhaps in kmail1?). In any case I wouldn't change the mail these days to not break possible signatures. But use this new fallback date in the C++ and user interface when reading the date field. That way missing (or invalid) dates get a valid useful date for sorting and displaying. Though it might be useful if dates in the future are marked as invalid early so they don't become valid later. But it could be changed in stages. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422173] Handling missing 'date' in email headers
https://bugs.kde.org/show_bug.cgi?id=422173 --- Comment #6 from Allan Sandfeld --- I guess the reason I prefer the latest received is that I trust the email-servers closer to home more. The earlier it gets the more likely it could have been spoofed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422173] Handling missing 'date' in email headers
https://bugs.kde.org/show_bug.cgi?id=422173 --- Comment #5 from Allan Sandfeld --- Sure, it shouldn't matter much, as long as it has an appropriate date in the right time span. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422173] Handling missing 'date' in email headers
https://bugs.kde.org/show_bug.cgi?id=422173 --- Comment #2 from Allan Sandfeld --- I think the safest would be to used that latest received date, when date is invalid or missing. It seems to be what other mail clients do. The notes about filtering is mostly suggestions for improvements, like a match on missing headers. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422173] Handling missing 'date' in email headers
https://bugs.kde.org/show_bug.cgi?id=422173 --- Comment #3 from Allan Sandfeld --- I think the safest would be to used that latest received date, when date is invalid or missing. It seems to be what other mail clients do. The notes about filtering is mostly suggestions for improvements, like a match on missing headers. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422173] New: Handling missing 'date' in email headers
https://bugs.kde.org/show_bug.cgi?id=422173 Bug ID: 422173 Summary: Handling missing 'date' in email headers Product: kmail2 Version: 5.14.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@carewolf.com Target Milestone: --- I have one particular type of email that always get send without a date header, and always ends up being misordered by kmail. It would be nice if kmail would fall back to a received date when an explicit date is missing or invalid (in the future). I tried fixing it with filtering, but a) I couldn't match on missing headers, or match date: on being empty b) Couldn't set the date to the current time, and only to hardcoded times. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 422165] New: Crashed while running in background (probably trying to notify)
https://bugs.kde.org/show_bug.cgi?id=422165 Bug ID: 422165 Summary: Crashed while running in background (probably trying to notify) Product: kdeconnect Version: 1.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: k...@carewolf.com Target Milestone: --- Created attachment 128853 --> https://bugs.kde.org/attachment.cgi?id=128853=edit backtrace Crashed when I started reading an article on the phone. Compiled from sources about a weak ago against Qt 5.15.0. The crash happens in KNotification though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420801] Muting audio device in the system tray applet crash plasma
https://bugs.kde.org/show_bug.cgi?id=420801 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417728] The date is initially (after login) too big and wraps when the panel is vertical.
https://bugs.kde.org/show_bug.cgi?id=417728 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com --- Comment #2 from Allan Sandfeld --- I had literally the opposite regression. The text is now too small. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417073] plasma-nm prevents most other systray applets
https://bugs.kde.org/show_bug.cgi?id=417073 Allan Sandfeld changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Allan Sandfeld --- I can no longer reproduce it. Something else in my configuration must have interfered and been a part of the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417073] plasma-nm prevents most other systray applets
https://bugs.kde.org/show_bug.cgi?id=417073 --- Comment #5 from Allan Sandfeld --- I am using kdesrc-build stable. Currently that appears to be a prerelease of 5.18. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417073] plasma-nm prevents most other systray applets
https://bugs.kde.org/show_bug.cgi?id=417073 --- Comment #2 from Allan Sandfeld --- Note I am using Qt 5.14.1 if that makes any difference -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417073] plasma-nm prevents most other systray applets
https://bugs.kde.org/show_bug.cgi?id=417073 --- Comment #1 from Allan Sandfeld --- Reverting to the v5.17.5 git tag, solved the issue for me. If you want me too I could probably bisect which commit caused the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417073] plasma-nm prevents most other systray applets
https://bugs.kde.org/show_bug.cgi?id=417073 Allan Sandfeld changed: What|Removed |Added Version|5.17.5 |5.17.90 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417073] New: plasma-nm prevents most other systray applets
https://bugs.kde.org/show_bug.cgi?id=417073 Bug ID: 417073 Summary: plasma-nm prevents most other systray applets Product: plasma-nm Version: 5.17.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: k...@carewolf.com Target Milestone: --- With the lastest update of plasma I found most of the systray icons absent from the systray. I traced it down to plasma-nm, and uninstalling the plasma-nm applet restores the rest of the applet. During launch or relaunch of plasmashell, all the systray apps an be seen shortly before plasma-nm starts and nukes the rest. Unfortunately there is nothing in the log that suggest what is going on. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 412861] WebEngine crashes, KHTML not for daily usage
https://bugs.kde.org/show_bug.cgi?id=412861 Allan Sandfeld changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||k...@carewolf.com --- Comment #1 from Allan Sandfeld --- You are using a buggy OpenGL driver, and said driver crashes: Use one that isn't buggy. Note if you use Qt 5.12, QtWebEngine would automatically disable OpenGL with said driver because it is so buggy, if you use 5.13, it would switch to single-threaded mode and work around the bugs. -- You are receiving this mail because: You are watching all bug changes.
[grantlee] [Bug 411515] Crash in kitinary on EasyJet confirmations
https://bugs.kde.org/show_bug.cgi?id=411515 Allan Sandfeld changed: What|Removed |Added Resolution|--- |FIXED Assignee|kdepim-b...@kde.org |steve...@gmail.com Version|5.12.0 |unspecified Product|kmail2 |grantlee Status|REPORTED|RESOLVED Component|general |general --- Comment #3 from Allan Sandfeld --- Already fixed -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411515] Crash in kitinary on EasyJet confirmations
https://bugs.kde.org/show_bug.cgi?id=411515 --- Comment #2 from Allan Sandfeld --- It is possible. I just tried rebuilding grantlee and now the issue doesn't reproduce. Though supposedly my last build was from 22nd of August. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411515] New: Crash in kitinary on EasyJet confirmations
https://bugs.kde.org/show_bug.cgi?id=411515 Bug ID: 411515 Summary: Crash in kitinary on EasyJet confirmations Product: kmail2 Version: 5.12.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@carewolf.com Target Milestone: --- Application: kmail (5.12.0) (Compiled from sources) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 4.19.0-5-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: - What I was doing when the application crashed: KMail crashes when clicking on an email containing a confirmation from EasyJet. This happened on two different matchines both with different versions of stable kdesrc-build with around KDE 19.08 The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7433e12cc0 (LWP 15784))] Thread 25 (Thread 0x7f739df18700 (LWP 2641)): #0 0x7f7440652829 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f7440607331 in g_main_context_query () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7440607b77 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7440607d1c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f744da2f90b in QEventDispatcherGlib::processEvents (this=0x7f73fc0077f0, flags=...) at /src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #5 0x7f744d9ddca3 in QEventLoop::exec (this=this@entry=0x7f739df17900, flags=..., flags@entry=...) at ../../include/QtCore/../../../../qt5/qtbase/src/corelib/global/qflags.h:140 #6 0x7f744d82e2a6 in QThread::exec (this=) at ../../include/QtCore/../../../../qt5/qtbase/src/corelib/global/qflags.h:120 #7 0x7f744d82f512 in QThreadPrivate::start (arg=0x55711017bb10) at /src/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:360 #8 0x7f744bf25fa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7f744d2e54cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f739d717700 (LWP 2614)): #0 futex_reltimed_wait_cancelable (private=0, reltime=0x7f739d7165f0, expected=0, futex_word=0x7f739d7167c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f739d716690, mutex=0x7f739d716778, cond=0x7f739d7167a0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f739d7167a0, mutex=0x7f739d716778, abstime=0x7f739d716690) at pthread_cond_wait.c:667 #3 0x7f744664c466 in base::ConditionVariable::TimedWait () at ./../../../../../qt5/qtwebengine/src/3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127 #4 0x7f744664cdfd in base::WaitableEvent::TimedWaitUntil () at ./../../../../../qt5/qtwebengine/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230 #5 0x7f744664cf92 in base::WaitableEvent::TimedWait () at ./../../../../../qt5/qtwebengine/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162 #6 0x7f7446607f21 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../../../../qt5/qtwebengine/src/3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37 #7 0x7f7446609494 in base::internal::SchedulerWorker::RunWorker () at ./../../../../../qt5/qtwebengine/src/3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303 #8 0x7f7446609b84 in base::internal::SchedulerWorker::RunPooledWorker () at ./../../../../../qt5/qtwebengine/src/3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229 #9 0x7f744664ea25 in ThreadFunc () at ./../../../../../qt5/qtwebengine/src/3rdparty/chromium/base/threading/platform_thread_posix.cc:81 #10 0x7f744bf25fa3 in start_thread (arg=) at pthread_create.c:486 #11 0x7f744d2e54cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f739b713700 (LWP 2562)): #0 futex_reltimed_wait_cancelable (private=0, reltime=0x7f739b7125f0, expected=0, futex_word=0x7f739b7127c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f739b712690, mutex=0x7f739b712778, cond=0x7f739b7127a0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f739b7127a0, mutex=0x7f739b712778, abstime=0x7f739b712690) at pthread_cond_wait.c:667 #3 0x7f744664c466 in base::ConditionVariable::TimedWait () at ./../../../../../qt5/qtwebengine/src/3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127 #4 0x7f744664cdfd in base::WaitableEvent::TimedWaitUntil () at ./../../../../../qt5/qtwebengine/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
[kwin] [Bug 406918] Freeze on certain effects (NVidia)
https://bugs.kde.org/show_bug.cgi?id=406918 --- Comment #11 from Allan Sandfeld --- (In reply to David Edmundson from comment #10) > > I can't see that deadlock when breaking in gdb > > It'll be blocking in the render thread. Thread 0 will be polling on that. None of the threads were blocking, but I was running it in the ALT+2 terminal, so perhaps it unblocked whenever I changed screens. I couldn't run it in X11 as everything freezes when the issue happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406918] Freeze on certain effects (NVidia)
https://bugs.kde.org/show_bug.cgi?id=406918 --- Comment #9 from Allan Sandfeld --- I can't see that deadlock when breaking in gdb, but if I enable debug logging for qt.scenegraph.time.renderloop I get output like this: qt.scenegraph.renderloop: (RT) - rendering started qt.scenegraph.renderloop: (RT) - rendering done qt.scenegraph.renderloop: (RT) - wake Gui after initial expose qt.scenegraph.time.renderloop: Frame rendered with 'threaded' renderloop in 13148ms, sync=0, render=0, swap=13148 - (on render thread) So it waits 13 seconds apperently doing gl->swapBuffer() -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406918] Freeze on certain effects (NVidia)
https://bugs.kde.org/show_bug.cgi?id=406918 --- Comment #7 from Allan Sandfeld --- Yes, I use kdesrc-build. I can also patch and build separately if you want to test something -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406918] Freeze on certain effects (NVidia)
https://bugs.kde.org/show_bug.cgi?id=406918 --- Comment #4 from Allan Sandfeld --- Yes disabling those two options for those effects fixes the issue for them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406918] Freeze on certain effects (NVidia)
https://bugs.kde.org/show_bug.cgi?id=406918 --- Comment #2 from Allan Sandfeld --- Created attachment 119649 --> https://bugs.kde.org/attachment.cgi?id=119649=edit Kwin support info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406918] New: Freeze on certain effects (NVidia)
https://bugs.kde.org/show_bug.cgi?id=406918 Bug ID: 406918 Summary: Freeze on certain effects (NVidia) Product: kwin Version: 5.15.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: k...@carewolf.com Target Milestone: --- Certain screen edge effects: Tiling a window, triggering Desktop Grid, and mouse-over on a window in Present Windows (before it zooms in a little), causes KWin to freeze for ~10s before resuming. Doing the same effect immediately after has no such stall, but doing it again a few minutes later will have the stall once more. Has only been observed with proprietary NVidia drivers. With both OpenGL 2.0 and 3.1 backends. Using KDE stable from kdesrc-build, and Qt 5.13 from git. Has been observed for a few months. Kwin produces no relevant console log output. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #125 from Allan Sandfeld --- Btw. I believe the underlying cause is the same that causes emails you are currently reading to be marked unread again while you are reading it. A sync is often started in parallel with other actions, so for instance you click on a folder it starts syncing, and you are reading an email and it is marked read. You mark it read, but the sync then marks it unread (race condition). The same can happen when moving emails, it might be moved, only to be recreated by the parallel sync, and then moved again, causing two exact copies to exist in the target folder. The transactional atomicy of Akonadi is somewhat questionable with several jobs that consists of multiple database transactions, or is combined with syncing remote servers. I tried looking at the move job, but it is pretty messy. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #124 from Allan Sandfeld --- (In reply to Matthias Kretz from comment #123) > (In reply to Allan Sandfeld from comment #122) > > With my patch in place the duplicates can be removed by simply calling > > "remove duplicates" from KMail. > > "Folder -> Remove Duplicates"? If that removes stales in the pimitemtable > it's somewhat misleadingly named. I was expecting it to search for copies of > the same mail (i.e. different local & remote ID but equal payload data). It is not what it is supposed to do, but those exact copies of a single remote entry also match as if they are just normal copies of the same email. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #122 from Allan Sandfeld --- With my patch in place the duplicates can be removed by simply calling "remove duplicates" from KMail. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 401692] Akonadi components crash on logout
https://bugs.kde.org/show_bug.cgi?id=401692 --- Comment #9 from Allan Sandfeld --- Something is throwing an exception inside a QThread::run() -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 401495] CTRL+Q to only close window
https://bugs.kde.org/show_bug.cgi?id=401495 --- Comment #5 from Allan Sandfeld --- Looking to redefine the binding, I just found an existing Falkon option to not close the application on CTRL+Q, apparently other people have thought it problematic. Unfortunately it completely disables the short-cut instead of mapping it to close window. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 401495] CTRL+Q to only close window
https://bugs.kde.org/show_bug.cgi?id=401495 --- Comment #4 from Allan Sandfeld --- Okay, if that is how you define in in Falkon, it is just not how most other KDE applications work in particular konqueror that Falkon replaces. The idea in konqueror was that we didn't want people to think about which windows belong to with process, and you could configure it to make new window be other processes, or make determine it on the fly. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 401495] CTRL+Q to only close window
https://bugs.kde.org/show_bug.cgi?id=401495 --- Comment #2 from Allan Sandfeld --- Alt+F4 is that just the Windows binding of CTRL+Q? They tend to be the same thing. I am just comparing to what other KDE applications do like KWrite or Konqueror. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 401495] New: CTRL+Q to only close window
https://bugs.kde.org/show_bug.cgi?id=401495 Bug ID: 401495 Summary: CTRL+Q to only close window Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: k...@carewolf.com Target Milestone: --- I would prefer if CTRL+Q only closed the current window, and not all falkon windows as that feels more like multiple applications. Then CTRL+W would close tab, and CTRL+Q the window. It is just a wish though. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 400400] Crash on launch
https://bugs.kde.org/show_bug.cgi?id=400400 Allan Sandfeld changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Allan Sandfeld --- Fixed by https://commits.kde.org/kdepim-runtime/a4316a290e243fd71a565a9b936012d27f116029 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 400601] New: Crash on exit with hanging folder sync
https://bugs.kde.org/show_bug.cgi?id=400601 Bug ID: 400601 Summary: Crash on exit with hanging folder sync Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@carewolf.com Target Milestone: --- Application: kmail (5.9.3) (Compiled from sources) Qt Version: 5.12.0 Frameworks Version: 5.52.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Closing KMail because it was acting strange - Unusual behavior I noticed: Something about the outlook365 server had changed so that akonadi couldn't connect to it. The resulted in two different bugs in KMail. 1) The existing messages were not readable even though I had offline caching enabled. This could be worked around by moving KMail to offline mode, but it really should be possible to read messages while a sync is working. 2) Closing KMail causes it to hang for a long while until some kind of timeout triggers and it crashes. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f52868582c0 (LWP 6037))] Thread 19 (Thread 0x7f51f7df9700 (LWP 6091)): #0 0x7f52a178bd79 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f52a1746538 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f52adfc5f5b in QEventDispatcherGlib::processEvents (this=0x7f51ec000b20, flags=...) at /src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:424 #3 0x7f52adf664fa in QEventLoop::exec (this=this@entry=0x7f51f7df8d20, flags=..., flags@entry=...) at /src/qt5/qtbase/src/corelib/kernel/qeventloop.cpp:225 #4 0x7f52add8a1aa in QThread::exec (this=) at /src/qt5/qtbase/src/corelib/thread/qthread.cpp:534 #5 0x7f52add8b982 in QThreadPrivate::start (arg=0x562e139a7830) at /src/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:361 #6 0x7f52a339b6db in start_thread (arg=0x7f51f7df9700) at pthread_create.c:463 #7 0x7f52ad68988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f51fe222700 (LWP 6068)): #0 0x7f52a33a19f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f51fe221c58) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f51fe221c08, cond=0x7f51fe221c30) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f51fe221c30, mutex=0x7f51fe221c08) at pthread_cond_wait.c:655 #3 0x7f5298d109b9 in base::ConditionVariable::Wait () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/synchronization/condition_variable_posix.cc:71 #4 0x7f5298d1142c in base::WaitableEvent::TimedWaitUntil () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:223 #5 0x7f5298d114bf in base::WaitableEvent::Wait () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:154 #6 0x7f5298ccbe75 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:35 #7 0x7f5298ccdb70 in base::internal::SchedulerWorker::RunWorker () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:324 #8 0x7f5298ccde84 in base::internal::SchedulerWorker::RunDedicatedWorker () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:248 #9 0x7f5298d13761 in ThreadFunc () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/threading/platform_thread_posix.cc:76 #10 0x7f52a339b6db in start_thread (arg=0x7f51fe222700) at pthread_create.c:463 #11 0x7f52ad68988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f5235ffb700 (LWP 6067)): #0 0x7f52ad67cbf9 in __GI___poll (fds=0x7f520c007130, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5291346451 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f5291337e10 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f52913384a0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f5291338530 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f5291346399 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f528b7502a8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7f52a339b6db in start_thread (arg=0x7f5235ffb700) at pthread_create.c:463
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #119 from Allan Sandfeld --- I pushed my patch for review. One side effect I have noticed though, is that affected folders ends up being redownloaded frequently as the number of messages doesn't match upstream, but the duplicates are not deleted during the sync, so it happens again and again. That should probably be fixed, at least a full sync from remote should get rid of the duplicate. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 400400] Crash on launch
https://bugs.kde.org/show_bug.cgi?id=400400 --- Comment #1 from Allan Sandfeld --- Fix in https://phabricator.kde.org/D16493 Somehow arcanist fucked up, and refused to then do anything at all, so I had to make a review manually. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 400400] Crash on launch
https://bugs.kde.org/show_bug.cgi?id=400400 Allan Sandfeld changed: What|Removed |Added Assignee|dvra...@kde.org |k...@carewolf.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 400400] New: Crash on launch
https://bugs.kde.org/show_bug.cgi?id=400400 Bug ID: 400400 Summary: Crash on launch Product: Akonadi Version: 5.9.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Gmail resource Assignee: dvra...@kde.org Reporter: k...@carewolf.com CC: kdepim-b...@kde.org Target Milestone: --- Created attachment 115935 --> https://bugs.kde.org/attachment.cgi?id=115935=edit Backtrace The GMail akonadi resources consistently crashes STEPS TO REPRODUCE 1. Try to launch or restart akonadi OBSERVED RESULT Gmail resource crashes -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 400371] New: Crash on akonadi restart
https://bugs.kde.org/show_bug.cgi?id=400371 Bug ID: 400371 Summary: Crash on akonadi restart Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@carewolf.com Target Milestone: --- Application: kmail (5.9.3) Qt Version: 5.12.0 Frameworks Version: 5.52.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I called akonadictl restart - Unusual behavior I noticed: Akonadi had one of it is extremely regular breakdowns where it required a restart. In this case like it is most of the time, Kmail not able to show emails because akonadi was working, though it could show them perfectily fine if akonadi wasn't running at all. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 [Current thread is 1 (Thread 0x7f2c6a9862c0 (LWP 24583))] Thread 19 (Thread 0x7f2bcdfd3700 (LWP 24642)): #0 0x7f2c917d2bf9 in __GI___poll (fds=0x7f2bbc0049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2c8589c439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2c8589c54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2c9211bf5b in QEventDispatcherGlib::processEvents (this=0x7f2bbc000b20, flags=...) at /src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:424 #4 0x7f2c920bc4fa in QEventLoop::exec (this=this@entry=0x7f2bcdfd2d20, flags=..., flags@entry=...) at /src/qt5/qtbase/src/corelib/kernel/qeventloop.cpp:225 #5 0x7f2c91ee01aa in QThread::exec (this=) at /src/qt5/qtbase/src/corelib/thread/qthread.cpp:534 #6 0x7f2c91ee1982 in QThreadPrivate::start (arg=0x55f56910f270) at /src/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:361 #7 0x7f2c874f16db in start_thread (arg=0x7f2bcdfd3700) at pthread_create.c:463 #8 0x7f2c917df88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f2bdbdf9700 (LWP 24634)): #0 0x7f2c917d2bf9 in __GI___poll (fds=0x7f2bc8006800, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2c8589c439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2c8589c54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2c9211bf5b in QEventDispatcherGlib::processEvents (this=0x7f2bdb20, flags=...) at /src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:424 #4 0x7f2c920bc4fa in QEventLoop::exec (this=this@entry=0x7f2bdbdf8d20, flags=..., flags@entry=...) at /src/qt5/qtbase/src/corelib/kernel/qeventloop.cpp:225 #5 0x7f2c91ee01aa in QThread::exec (this=) at /src/qt5/qtbase/src/corelib/thread/qthread.cpp:534 #6 0x7f2c91ee1982 in QThreadPrivate::start (arg=0x55f5655c2a80) at /src/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:361 #7 0x7f2c874f16db in start_thread (arg=0x7f2bdbdf9700) at pthread_create.c:463 #8 0x7f2c917df88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f2be700 (LWP 24614)): #0 0x7f2c874f79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f2be2221c58) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f2be2221c08, cond=0x7f2be2221c30) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f2be2221c30, mutex=0x7f2be2221c08) at pthread_cond_wait.c:655 #3 0x7f2c7ce5aff9 in base::ConditionVariable::Wait () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/synchronization/condition_variable_posix.cc:71 #4 0x7f2c7ce5ba6c in base::WaitableEvent::TimedWaitUntil () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:223 #5 0x7f2c7ce5baff in base::WaitableEvent::Wait () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:154 #6 0x7f2c7ce164b5 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:35 #7 0x7f2c7ce181b0 in base::internal::SchedulerWorker::RunWorker () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:324 #8 0x7f2c7ce184c4 in base::internal::SchedulerWorker::RunDedicatedWorker () at ./../../../../../qtwebengine/src/3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:248 #9 0x7f2c7ce5dda1 in ThreadFunc () at
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #115 from Allan Sandfeld --- I think it is a safe and it works, but it doesn't solve the underlying issue, it just makes kmail keep working when the data is wrong. --- Comment #116 from Allan Sandfeld --- I think it is a safe and it works, but it doesn't solve the underlying issue, it just makes kmail keep working when the data is wrong. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #115 from Allan Sandfeld --- I think it is a safe and it works, but it doesn't solve the underlying issue, it just makes kmail keep working when the data is wrong. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #113 from Allan Sandfeld --- Created attachment 115298 --> https://bugs.kde.org/attachment.cgi?id=115298=edit experimental patch I have been using this patch for months to keep akonadi working on my machine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398229] Popups freezes plasma
https://bugs.kde.org/show_bug.cgi?id=398229 Allan Sandfeld changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #5 from Allan Sandfeld --- Ah nevermind. I had some old libGL driver in /usr/local, seems to have been working for a long time, but removing it now fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398229] Popups freezes plasma
https://bugs.kde.org/show_bug.cgi?id=398229 Allan Sandfeld changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #4 from Allan Sandfeld --- Seems to be some interaction between Intel drivers, QML and whatever it is plasma does that triggers it. #0 0x75649227 in __libc_recvmsg (fd=3, msg=0x7fffc920, flags=0) at ../sysdeps/unix/sysv/linux/recvmsg.c:28 #1 0x7790fe08 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7790dfb5 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7790f9fa in xcb_wait_for_special_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #4 0x7370a3fb in dri3_wait_for_event_locked () at /usr/local/lib/libGL.so.1 #5 0x7370a558 in dri3_find_back () at /usr/local/lib/libGL.so.1 #6 0x7370ae36 in dri3_get_buffer.isra () at /usr/local/lib/libGL.so.1 #7 0x7370ba50 in loader_dri3_get_buffers () at /usr/local/lib/libGL.so.1 #8 0x7fff5ac3d7f5 in intel_update_renderbuffers () at /usr/local/lib/dri/i965_dri.so #9 0x7fff5ac3dbd1 in intel_prepare_render () at /usr/local/lib/dri/i965_dri.so #10 0x7fff5ac3967c in brw_clear () at /usr/local/lib/dri/i965_dri.so #11 0x774ff6a2 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x77504f02 in QSGBatchRenderer::Renderer::render() () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x774f552c in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x774f59eb in QSGRenderer::renderScene(unsigned int) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7752f370 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x77591310 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #17 0x7752189e in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7759c8e6 in QQuickWindow::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x77f55a33 in PlasmaQuick::Dialog::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libKF5PlasmaQuick.so.5 #20 0x765334a1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7653aae0 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x75afb579 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x75ea68c1 in QWindowPrivate::deliverUpdateRequest() () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #24 0x75ea6df9 in QWindow::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #25 0x7759c83b in QQuickWindow::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #26 0x77f55a33 in PlasmaQuick::Dialog::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libKF5PlasmaQuick.so.5 #27 0x765334a1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7653aae0 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x75afb579 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x75b4c638 in QTimerInfoList::activateTimers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x75b4ce94 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x72410287 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x724104c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7241054c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x75b4d223 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7fffec37ce51 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #37 0x75afa24b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x75b023c2 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #39 0x5557432b in () #40 0x75572b17 in __libc_start_main (main= 0x55573820, argc=1, argv=0x7fffdf18, init=, fini=, rtld_fini=, stack_end=0x7fffdf08) at ../csu/libc-start.c:310 #41 0x5557477a in _start () -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398229] Popups freezes plasma
https://bugs.kde.org/show_bug.cgi?id=398229 --- Comment #3 from Allan Sandfeld --- Also, restarting kwin does nothing. It was the first thing I tried as it used to have similar issues. Only restarting plasmashell did anything. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398229] Popups freezes plasma
https://bugs.kde.org/show_bug.cgi?id=398229 --- Comment #2 from Allan Sandfeld --- It is Debian testing, and I updated everything as the first issue I had was the systray missing and crashing after only a few things was accidently updated, but after updating everything this freezing started. I didnt see anything interesting in the console output, but the next step will be to attach gdb and see if I can recognize which thread is stuck and how. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398229] New: Popups freezes plasma
https://bugs.kde.org/show_bug.cgi?id=398229 Bug ID: 398229 Summary: Popups freezes plasma Product: plasmashell Version: 5.13.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: k...@carewolf.com CC: plasma-b...@kde.org Target Milestone: 1.0 Since upgrading to 5.13.x plasma, the plasmashell regularly freezes when one its popups are open. Both the application menu and task-manager overviews of similar windows can trigger this, but I find the most predictable way to reproduce it is if you have a lot of kwrite windows open and click on the kwrite icon in the task bar, and then move the mouse up and down the list of open windows. The problem goes away by killing plasmashell and relaunching it. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #102 from Allan Sandfeld --- I also see this on a regular basis, though it doesn't always completely stall imap account, or at least didn't with my last version, but now does so again. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 395249] Akonadi 5.8.2 breaks existing IMAP/STARTTLS account
https://bugs.kde.org/show_bug.cgi?id=395249 --- Comment #6 from Allan Sandfeld --- It probably also doesn't advertise STARTTLS support. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 395249] Akonadi 5.8.2 breaks existing IMAP/STARTTLS account
https://bugs.kde.org/show_bug.cgi?id=395249 --- Comment #4 from Allan Sandfeld --- Created attachment 113224 --> https://bugs.kde.org/attachment.cgi?id=113224=edit Hacky fix This patch fixes it for outlook 365, but more generally I think it is probably a mistake not to try starttls unconditionaly if the mailtransport was configured to use starttls. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 395249] Akonadi 5.8.2 breaks existing IMAP/STARTTLS account
https://bugs.kde.org/show_bug.cgi?id=395249 --- Comment #3 from Allan Sandfeld --- It appears outlook doesn't return a response.responseCode == "STARTTLS". Instead the only response code it sends is a base64 unicode16 string that ends in OUTLOOK.com :/ -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 395249] Akonadi 5.8.2 breaks existing IMAP/STARTTLS account
https://bugs.kde.org/show_bug.cgi?id=395249 Allan Sandfeld changed: What|Removed |Added Assignee|chrig...@fastmail.fm|dvra...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 395249] Akonadi 5.8.2 breaks existing IMAP/STARTTLS account
https://bugs.kde.org/show_bug.cgi?id=395249 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com --- Comment #2 from Allan Sandfeld --- I see the same. Though not with all IMAP servers with at least with outlook 365 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 394464] New: Count action messages
https://bugs.kde.org/show_bug.cgi?id=394464 Bug ID: 394464 Summary: Count action messages Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: k...@carewolf.com Target Milestone: --- A feature I have been missing for a long time is a better way to find and track messages marked todo/action. One simple way would be to allow the folder list to mark folders with action messages like it does with folders with unread messages. For instance having another optional column for action messages in the overview or simply adding it to the unread count (perhaps with a different color). E.g. Inbox(5 + 1) with 5 being blue for unread and 1 red for action. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393101] Graphical corruption with depth 30
https://bugs.kde.org/show_bug.cgi?id=393101 --- Comment #6 from Allan Sandfeld <k...@carewolf.com> --- Okay. I knew X11 was closed for development. I only reported it after I noted the lack of some of the underlying things such as image format in Screen, and detection of window format. The pixel corruption wouldn't happen for wayland, but if we later support colorspaces for HDR, they would need corrections based on that. My assumption was that once you hook up these basic things, you are likely to need anyway, I could fix the X11 side with a 10 line patch that just uses the tracked image formats. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393101] Graphical corruption with depth 30
https://bugs.kde.org/show_bug.cgi?id=393101 --- Comment #4 from Allan Sandfeld <k...@carewolf.com> --- So not going to fix it for wayland either? The underlying problem is the same, and you will need the underlying fixes anyway in the near future to support HDR. You need to be aware of the screen format and the format of application windows. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393101] Graphical corruption with depth 30
https://bugs.kde.org/show_bug.cgi?id=393101 --- Comment #2 from Allan Sandfeld <k...@carewolf.com> --- Created attachment 112001 --> https://bugs.kde.org/attachment.cgi?id=112001=edit screenshot showing bad window decoration -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393101] Graphical corruption with depth 30
https://bugs.kde.org/show_bug.cgi?id=393101 --- Comment #1 from Allan Sandfeld <k...@carewolf.com> --- Btw. An easy way of seeing the corruption without changing Qt is launching Chromium. It will render its internal corrupt because GTK has terrible support for the same, but the window decoration by Kwin will also be wrong. -- You are receiving this mail because: You are watching all bug changes.
