[kmail2] [Bug 371697] New: kmail 16.08.2 save sieve script after edit lead to crash
https://bugs.kde.org/show_bug.cgi?id=371697 Bug ID: 371697 Summary: kmail 16.08.2 save sieve script after edit lead to crash Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.8.3-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was editing (adding rules) to my sieve script. When I click the ok button the indicator apps said script upload successful. and right after that when the account list should be closed, the application completely crash. my autosieve file on server was correctly uploaded, and a .sos copy of previous state was created. Server is dovecot 2.2.25 -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0e8b502e00 (LWP 1997))] Thread 50 (Thread 0x7f0c811a3700 (LWP 9099)): #0 0x7f0e88336ad9 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f0e7c43d12a in g_cond_wait_until (cond=cond@entry=0x160e418, mutex=mutex@entry=0x160e410, end_time=end_time@entry=81361281793) at gthread-posix.c:1442 #2 0x7f0e7c3cbc69 in g_async_queue_pop_intern_unlocked (queue=queue@entry=0x160e410, wait=wait@entry=1, end_time=end_time@entry=81361281793) at gasyncqueue.c:422 #3 0x7f0e7c3cc28c in g_async_queue_timeout_pop (queue=0x160e410, timeout=timeout@entry=1500) at gasyncqueue.c:543 #4 0x7f0e7c41fc8d in g_thread_pool_thread_proxy () at gthreadpool.c:167 #5 0x7f0e7c41fc8d in g_thread_pool_thread_proxy (data=) at gthreadpool.c:364 #6 0x7f0e7c41f1c5 in g_thread_proxy (data=0x7f0c78003590) at gthread.c:784 #7 0x7f0e7e1cd454 in start_thread (arg=0x7f0c811a3700) at pthread_create.c:333 #8 0x7f0e8833b39f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 49 (Thread 0x7f0c9700 (LWP 8791)): #0 0x7f0e7c43cea9 in g_mutex_lock (mutex=mutex@entry=0x7f0c98000990) at gthread-posix.c:1336 #1 0x7f0e7c3f6d85 in g_main_context_prepare (context=context@entry=0x7f0c98000990, priority=priority@entry=0x7f0c9fffeb40) at gmain.c:3504 #2 0x7f0e7c3f779b in g_main_context_iterate (context=context@entry=0x7f0c98000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3909 #3 0x7f0e7c3f798c in g_main_context_iteration (context=0x7f0c98000990, may_block=may_block@entry=1) at gmain.c:3990 #4 0x7f0e88e6879b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f0c980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f0e88e121ea in QEventLoop::exec(QFlags) (this=this@entry=0x7f0c9fffec80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f0e88c408b3 in QThread::exec() (this=) at thread/qthread.cpp:507 #7 0x7f0e88c45558 in QThreadPrivate::start(void*) (arg=0x40be570) at thread/qthread_unix.cpp:344 #8 0x7f0e7e1cd454 in start_thread (arg=0x7f0c9700) at pthread_create.c:333 #9 0x7f0e8833b39f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 48 (Thread 0x7f0cc4cbb700 (LWP 8790)): #0 0x7f0e8833268d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0e7c3f7876 in g_main_context_iterate (priority=, n_fds=1, fds=0x7f0ca4002e20, timeout=, context=0x7f0ca4000990) at gmain.c:4228 #2 0x7f0e7c3f7876 in g_main_context_iterate (context=context@entry=0x7f0ca4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3924 #3 0x7f0e7c3f798c in g_main_context_iteration (context=0x7f0ca4000990, may_block=may_block@entry=1) at gmain.c:3990 #4 0x7f0e88e6879b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f0ca40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f0e88e121ea in QEventLoop::exec(QFlags) (this=this@entry=0x7f0cc4cbac80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f0e88c408b3 in QThread::exec() (this=) at thread/qthread.cpp:507 #7 0x7f0e88c45558 in QThreadPrivate::start(void*) (arg=0x15370920) at thread/qthread_unix.cpp:344 #8 0x7f0e7e1cd454 in start_thread (arg=0x7f0cc4cbb700) at pthread_create.c:333 #9 0x7f0e8833b39f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 47 (Thread 0x7f0cc54bc700 (LWP 8789)): #0 0x7f0e7c43cea9 in g_mutex_lock (mutex=mutex@entry=0x7f0ca990) at gthread-posix.c:1336 #1 0x7f0e7c3f6d85 in g_main_context_prepare (context=context@entry=0x7f0ca990, priority=priority@entry=0x7f0cc54bbb40) at gmain.c:3504 #2 0x7f0e7c3f779b in g_ma
[kmail2] [Bug 371697] kmail 16.08.2 save sieve script after edit lead to crash
https://bugs.kde.org/show_bug.cgi?id=371697
--- Comment #2 from Bruno Friedmann ---
Laurent anything else I can retry (full gdb session but only with the useful
component ?)
The only relative sieve events in xsession-erros:-0.log I found are
log_kmanagersieve: "session2" No job for reporting this error message! "Could
not connect to host Unknown error."
QVariant(QString, "Product.get.versions") (QVariant(QVariantMap,
QMap(("products", QVariant(QVariantList, (QVariant(QVariantMap,
QMap(("components", QVariant(QVariantList, (QVariant(QVariantMap,
QMap(("default_assigned_to", QVariant(QString,
"kdepim-b...@kde.org"))("default_qa_contact", QVariant(QString,
""))("description", QVariant(QString, "KMail 2 - commands and actions: Actions
that operate on mails, usually those found in the context menu of the mail
viewer or mail list"))("flag_types", QVariant(QVariantMap, QMap(("attachment",
QVariant(QVariantList, ()))("bug", QVariant(QVariantList,
(QVariant(QVariantMap, QMap(("cc_list", QVariant(QString, ""))("description",
QVariant(QString, "Allows to set flags to bug fixes that need to be
backported."))("grant_group", QVariant(int, 6))("id", QVariant(int,
23))("is_active", QVariant(bool, true))("is_multiplicable", QVariant(bool,
true))("is_requestable", QVariant(bool, false))("is_requesteeble",
QVariant(bool, true))("name", QVariant(QString, "Backport"))("sort_key",
QVariant(int, 1, QVariant(QVariantMap, QMap(("cc_list", QVariant(QString,
""))("description", QVariant(QString, "All wishes submitted originating from
the forum Brainstorm"))("grant_group", QVariant(int, 7))("id", QVariant(int,
21))("is_active", QVariant(bool, true))("is_multiplicable", QVariant(bool,
true))("is_requestable", QVariant(bool, true))("is_requesteeble",
QVariant(bool, true))("name", QVariant(QString, "Brainstorm"))("request_group",
QVariant(int, 7))("sort_key", QVariant(int, 1, QVariant(QVariantMap,
QMap(("cc_list", QVariant(QString, ""))("description", QVariant(QString, "Bugs
that are not obvious on all setups, only reproducible in very uncommon
settings"))("grant_group", QVariant(int, 6))("id", QVariant(int,
24))("is_active", QVariant(bool, true))("is_multiplicable", QVariant(bool,
true))("is_requestable", QVariant(bool, false))("is_requesteeble",
QVariant(bool, true))("name", QVariant(QString, "corner_case"))("sort_key",
QVariant(int, 1, QVariant(QVariantMap, QMap(("cc_list", QVariant(QString,
""))("description", QVariant(QString, "the strings are not
translatable"))("grant_group", QVariant(int, 6))("id", QVariant(int,
20))("is_active", QVariant(bool, true))("is_multiplicable", QVariant(bool,
true))("is_requestable", QVariant(bool, true))("is_requesteeble",
QVariant(bool, true))("name", QVariant(QString,
"Translation_missing"))("request_group", QVariant(int, 7))("sort_key",
QVariant(int, 1, QVariant(QVariantMap, QMap(("cc_list", QVariant(QString,
"kde-usabil...@kde.org"))("description", QVariant(QString, "This flag should be
added to all reports that are usability issues"))("grant_group", QVariant(int,
6))("id", QVariant(int, 4))("is_active", QVariant(bool,
true))("is_multiplicable", QVariant(bool, true))("is_requestable",
QVariant(bool, true))("is_requesteeble", QVariant(bool, true))("name",
QVariant(QString, "Usability"))("request_group", QVariant(int, 6))("sort_key",
QVariant(int, 1))("id", QVariant(int, 1591))("is_active",
QVariant(bool, true))("name", QVariant(QString, "commands and
actions"))("sort_key", QVariant(int, 0, QVariant(QVariantMap,
QMap(("default_assigned_to", QVariant(QString,
"kdepim-b...@kde.org"))("default_qa_contact", QVariant(QString,
""))("description", QVariant(QString, "KMail 2 - composer: Everything related
to the composer GUI, including the recipient picker"))("flag_types",
QVariant(QVariantMap, QMap(("attachment", QVariant(QVariantList, ()))("bug",
QVariant(QVariantList, (QVariant(QVariantMap, QMap(("cc_list",
QVariant(QString, ""))("description", QVariant(QString, "Allows to set flags t
[kmail2] [Bug 371006] Printed website uses wrong encoding
https://bugs.kde.org/show_bug.cgi?id=371006 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #1 from Bruno Friedmann --- It's even worse, if the message is text + html. You select view html + image in messageviewer and decide to print it (Maybe an invoice like what paypal send) the print in browser take only the text part. not the last state of messageviewer. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 371006] Printed website uses wrong encoding
https://bugs.kde.org/show_bug.cgi?id=371006 --- Comment #3 from Bruno Friedmann --- What about the new complete integration again directly in kmail ? is it for 16.12 ? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 353240] Day numbers are cropped at the bottom in month view in korganizer
https://bugs.kde.org/show_bug.cgi?id=353240 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #6 from Bruno Friedmann --- Created attachment 102213 --> https://bugs.kde.org/attachment.cgi?id=102213&action=edit Month view in HiDPI Dates are cropped, but my xorg dpi is fixed at 192dpi and fonts in systemsettings are also forced to 192dpi. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449869] New: systemsettings crash when applying configuration to screen and countdown don't popup
https://bugs.kde.org/show_bug.cgi?id=449869
Bug ID: 449869
Summary: systemsettings crash when applying configuration to
screen and countdown don't popup
Product: systemsettings
Version: 5.23.5
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: br...@ioda-net.ch
Target Milestone: ---
Application: systemsettings5 (5.23.5)
Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.16.4-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.5 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I was configuring my second screen, placement right of, position bottom, not
primary.
hit the apply button and the crash occur.
The changes were applied (I mean the screen are configured) but the crash was
there.
I'm using nvidia, and xorg.
Maybe related to 447199
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = { >> = { >> = {, true>> = {_M_head_impl = {}}, },
> = {_M_head_impl = }, }, }}, }}
[KCrash Handler]
#6 QSharedPointer::data (this=) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:301
#7 QSharedPointer::operator-> (this=) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:307
#8 KScreen::Config::clone (this=0x0) at
/usr/src/debug/libkscreen2-5.23.5-1.1.x86_64/src/config.cpp:205
#9 0x7f45bc5f4a28 in ConfigHandler::revertConfig (this=0x55e12090b200) at
/usr/src/debug/kscreen5-5.23.5-1.1.x86_64/kcm/config_handler.h:45
#10 KCMKScreen::revertSettings (this=0x55e118a94190) at
/usr/src/debug/kscreen5-5.23.5-1.1.x86_64/kcm/kcm.cpp:99
#11 KCMKScreen::qt_static_metacall (_o=0x55e118a94190, _c=,
_id=, _a=) at
/usr/src/debug/kscreen5-5.23.5-1.1.x86_64/build/kcm/kcm_kscreen_autogen/EWIEGA46WW/moc_kcm.cpp:223
#12 0x7f45bc5f5ebb in KCMKScreen::qt_metacall (this=0x55e118a94190,
_c=QMetaObject::InvokeMetaMethod, _id=22, _a=0x7ffd0a1bf700) at
/usr/src/debug/kscreen5-5.23.5-1.1.x86_64/build/kcm/kcm_kscreen_autogen/EWIEGA46WW/moc_kcm.cpp:425
#13 0x7f45d43bf1cd in QQmlObjectOrGadget::metacall
(this=this@entry=0x7ffd0a1bf940, type=type@entry=QMetaObject::InvokeMetaMethod,
index=, argv=argv@entry=0x7ffd0a1bf700) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/qml/qqmlobjectorgadget.cpp:51
#14 0x7f45d429cd4e in CallMethod (callType=QMetaObject::InvokeMetaMethod,
callArgs=0x7f459cb1d6f0, engine=0x55e11899c660, argTypes=0x0, argCount=0,
returnType=43, index=, object=...) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1319
#15 CallPrecise (object=..., data=..., engine=engine@entry=0x55e11899c660,
callArgs=callArgs@entry=0x7f459cb1d6f0,
callType=callType@entry=QMetaObject::InvokeMetaMethod) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1573
#16 0x7f45d429ffdb in CallOverloaded (callType=,
propertyCache=, callArgs=, engine=, data=..., object=...) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1645
#17 QV4::QObjectMethod::callInternal (this=,
thisObject=, argv=, argc=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:2133
#18 0x7f45d42bcc43 in QV4::FunctionObject::call (argc=,
argv=, thisObject=, this=) at
../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/jsruntime/qv4functionobject_p.h:202
#19 QV4::Moth::VME::interpret (frame=0x7ffd0a1bfc00, engine=0x55e11899c660,
code=0x7f459cb1d6a8 "") at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:754
#20 0x7f45d42bf917 in QV4::Moth::VME::exec
(frame=frame@entry=0x7ffd0a1bfc00, engine=engine@entry=0x55e11899c660) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:463
#21 0x7f45d4252d3e in QV4::Function::call (this=this@entry=0x55e1185689c0,
thisObject=, argv=argv@entry=0x7f459cb1d670, argc=, context=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/jsruntime/qv4function.cpp:69
#22 0x7f45d43d9b45 in QQmlJavaScriptExpression::evaluate
(this=this@entry=0x55e118505e10, callData=callData@entry=0x7f459cb1d640,
isUndefined=isUndefined@entry=0x0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/qml/qml/qqmljavascriptexpression.cpp:212
#23 0x7f45d438b8ab in QQmlBoundSignalExpression::evaluate (this=, a=) at
../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/jsruntime/qv4jscall_p.h:95
#24 0x7f45d438ca98 in QQmlBoundSignal_callback (e=0x55e118505e80,
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #49 from Bruno Friedmann --- I've been "forced" to move now to wayland to get the per screen scale factor as it will never be implemented on X11. But loosing restore session is a pain. It seems we miss a global review on plasma development, with clear objectives for each release, to make all users (and developers) happy. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 415956] Akonadi 19.12.x crash when socket file for connection to postgresql database disappear
https://bugs.kde.org/show_bug.cgi?id=415956 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #5 from Bruno Friedmann --- Seems fixed with actual version Version 5.21.1 (22.08.1) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422433] akonadi constanly crash when updating database (due to rollback)
https://bugs.kde.org/show_bug.cgi?id=422433 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Bruno Friedmann --- Works at least with openSUSE Tumbleweed - 20220930 Linux 5.19.12-1-default x86_64 GNU/Linux nvidia: 515.65.01 Qt: 5.15.6 KDE Frameworks: 5.98.0 Plasma: 5.25.5 kmail2 5.21.1 (22.08.1) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413528] akonadi crashes after changing imap server
https://bugs.kde.org/show_bug.cgi?id=413528 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bruno Friedmann --- Closing not seen since a long time. Works with at least openSUSE Tumbleweed - 20220930 Linux 5.19.12-1-default x86_64 GNU/Linux nvidia: 515.65.01 Qt: 5.15.6 KDE Frameworks: 5.98.0 Plasma: 5.25.5 kmail2 5.21.1 (22.08.1) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #71 from Bruno Friedmann --- > Does Konsole save session (the windows and tabs and the current directory of > each tab) by itself? My experience is that it does not, but given that things > like Kate does, why can't Konsole, which is also a KDE app, do that? > Am I missing something? Yes my experience proove it, I usually have 10 tabs opened in konsole, most of them are dedicated to a relative work, and as such the directory in which the last session was run, and is restored on the right desktop. That IS the most reason I don't use (yet) Wayland. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 487601] New: Deleting an event (stored on nextcloud) in month view crash kalendar
https://bugs.kde.org/show_bug.cgi?id=487601 Bug ID: 487601 Summary: Deleting an event (stored on nextcloud) in month view crash kalendar Classification: Applications Product: korganizer Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: korganizer (6.0.2 (24.02.2)) Qt Version: 5.15.13 Frameworks Version: 5.116.0 Operating System: Linux 6.9.1-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: This is really easy to reproduce, with a remote nextcloud agenda, set kalendar in month view (maybe other view have the same result), select an event then clic delete (keyboard del) as soon as the event is going away the crash is present. This (mis)behavior appear once my plasma setup was moved to qt6/wayland (was working well before with qt5/X11) The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault [KCrash Handler] #4 QScopedPointer >::get() const (this=0x8) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/tools/qscopedpointer.h:110 #5 qGetPtrHelper > >(QScopedPointer >&) (ptr=...) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/global/qtclasshelpermacros.h:79 #6 QObject::d_func() (this=0x0) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.h:107 #7 QObject::deleteLater() (this=0x0) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.cpp:2456 #8 0x7f4bd45673d5 in Akonadi::IncidenceChangerPrivate::handleInvitationsAfterChange(QSharedPointer const&) (this=this@entry=0x55692b378270, change=...) at /usr/src/debug/akonadi-calendar-24.02.2/src/incidencechanger.cpp:658 #9 0x7f4bd45686f8 in Akonadi::IncidenceChangerPrivate::handleDeleteJobResult(KJob*) (this=0x55692b378270, job=) at /usr/src/debug/akonadi-calendar-24.02.2/src/incidencechanger.cpp:358 #10 0x7f4bd4fd232e in QObject::event(QEvent*) (this=0x55692b378270, e=0x55692bb85bb0) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.cpp:1446 #11 0x7f4bd61c2f1e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55692b378270, e=0x55692bb85bb0) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qapplication.cpp:3287 #12 0x7f4bd4f8f060 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55692b378270, event=0x55692bb85bb0) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1134 #13 0x7f4bd4f8f099 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1575 #14 0x7f4bd4f8f3c0 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x55692aff9960) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1932 #15 0x7f4bd51c2053 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x55692b006840) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qeventdispatcher_glib.cpp:244 #16 0x7f4bd33fa740 in () at /lib64/libglib-2.0.so.0 #17 0x7f4bd33fc388 in () at /lib64/libglib-2.0.so.0 #18 0x7f4bd33fca3c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #19 0x7f4bd51c0b0c in QEventDispatcherGlib::processEvents(QFlags) (this=0x55692af9d350, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qeventdispatcher_glib.cpp:394 #20 0x7f4bd4f997db in QEventLoop::exec(QFlags) (this=0x7ffefce705e0, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/global/qflags.h:34 #21 0x7f4bd4f92fe6 in QCoreApplication::exec() () at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/global/qflags.h:74 #22 0x5569128c19d9 in main(int, char**) (argc=, argv=) at /usr/src/debug/korganizer-24.02.2/src/main.cpp:62 [Inferior 1 (process 5044) detached] The reporter indicates this bug may be a duplicate of or related to bug 487484. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450337] Multiple issues when primary screen is turned on & off in a multi-screen setup
https://bugs.kde.org/show_bug.cgi?id=450337 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450337] Multiple issues when primary screen is turned on & off in a multi-screen setup
https://bugs.kde.org/show_bug.cgi?id=450337 --- Comment #15 from Bruno Friedmann --- Created attachment 148115 --> https://bugs.kde.org/attachment.cgi?id=148115&action=edit New crash information added by DrKonqi kwin_x11 (5.24.4) using Qt 5.15.2 - What I was doing when the application crashed: With a setup of two screen attached and linked by dp port, if you poweroff poweron too quickly one or both monitor you get a crash. Happen 75% of the time. If you do the power on/off slowly (2-4 seconds) kwin doesn't crash. -- Backtrace (Reduced): #6 0x7f577d29c5bc in KWin::Toplevel::isOnOutput(KWin::AbstractOutput*) const (this=0x56137d1c4990, output=0x56137c2c9890) at /usr/src/debug/kwin5-5.24.4-1.1.x86_64/src/toplevel.cpp:423 #7 0x7f577d2d4b49 in KWin::Workspace::activeOutput() const (this=0x56137c07c6c0) at /usr/src/debug/kwin5-5.24.4-1.1.x86_64/src/workspace.cpp:2419 #8 0x7f577d2e1c7f in KWin::X11Client::manage(unsigned int, bool) (this=0x56137c50d6c0, w=, isMapped=) at /usr/src/debug/kwin5-5.24.4-1.1.x86_64/src/workspace.h:811 #9 0x7f577d2c7863 in KWin::Workspace::createClient(unsigned int, bool) (this=0x56137c07c6c0, w=37749316, is_mapped=) at /usr/src/debug/kwin5-5.24.4-1.1.x86_64/src/workspace.cpp:654 #10 0x7f577d1ffb4d in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) (this=0x56137c07c6c0, e=0x7f5770008fd0) at /usr/src/debug/kwin5-5.24.4-1.1.x86_64/src/events.cpp:223 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448064] KWin crashes inKWin::Toplevel::isOnOutput() when (un)plugging HDMI while plasmashell was restarting
https://bugs.kde.org/show_bug.cgi?id=448064 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #11 from Bruno Friedmann --- So also available if you play with dp port (in my case daisy chained screen) X11 + nvidia My last dump is attached to 450337 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 430780] With multiple identity, reply doesn't check or use the right one
https://bugs.kde.org/show_bug.cgi?id=430780 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from Bruno Friedmann --- Hello Sandro, while I was annoyed during months(years?) the solution was in fact really simple. Once you give me the related config file and the code, I've located the source of my troubles. My main account had also the second identity email in the aliases :-( I remove any double entry and now everything is working as expected. Big thanks and have a nice day. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414528] kmail moving mail (delete, move, read) crash akonadi
https://bugs.kde.org/show_bug.cgi?id=414528 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Bruno Friedmann --- Logs have been since long time rotated. Have not been able to reproduce since a few weeks Running now with following stack openSUSE Tumbleweed 20200910 Linux 5.8.7-1-default x86_64 GNU/Linux nvidia: 450.66 Qt: 5.15.0 KDE Frameworks: 5.73.0 Plasma: 5.19.5 Kmail2 5.15.1 (20.08.1) Akonadi with PostgreSQL 12.4 -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 441757] New: ruqola doesn't store password
https://bugs.kde.org/show_bug.cgi?id=441757 Bug ID: 441757 Summary: ruqola doesn't store password Product: Ruqola Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- SUMMARY I've to connect to a private rocket chat entreprise server, with a login/password credential. rukola on reopening present the full login information but the password field is empty, and as it try to connect, failed with error. You have to enter your credentials each time. Would be cool if it can use kwallet or sort of password vault. STEPS TO REPRODUCE 1. step a connection to secured rocket.chat server 2. close rukola, start again rukola 3. see password need to be reenter. SOFTWARE/OS VERSIONS openSUSE Tumbleweed - 20210828 Linux 5.13.12-2-default x86_64 GNU/Linux, nvidia: 470.57.02 Qt: 5.15.2, KDE Frameworks: 5.85.0, Plasma: 5.22.4, kmail2 5.18.0 (21.08.0) rukola 1.1~git.20200520-1.9 -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 441757] ruqola doesn't store password
https://bugs.kde.org/show_bug.cgi?id=441757 --- Comment #2 from Bruno Friedmann --- ruqola is version 1.1-git.20200520 qt5keychain is also installed. i+ | libqt5keychain1 | package | 0.12.0-2.5 | x86_64 | oss I've never connect rocket.chat default server, and directly replace by my wanted server. Perhaps this has an unknown effect. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 441757] ruqola doesn't store password
https://bugs.kde.org/show_bug.cgi?id=441757 --- Comment #4 from Bruno Friedmann --- Thanks Laurent for the checking, in the meanwhile I will review the package we have in openSUSE to align it to then last version and report back if ok or not here. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 441757] ruqola doesn't store password
https://bugs.kde.org/show_bug.cgi?id=441757 --- Comment #6 from Bruno Friedmann --- Created attachment 141180 --> https://bugs.kde.org/attachment.cgi?id=141180&action=edit Unnamed login failed After a restart of version 1.5.0 there's still the first login failed tab. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 441757] ruqola doesn't store password
https://bugs.kde.org/show_bug.cgi?id=441757 --- Comment #7 from Bruno Friedmann --- Update of the status : Actually testing version 1.5.40 alpha, I've still a strange tab at start which contain a part of the already connected and defined server. Shall I try a more recent version ? -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 441757] ruqola doesn't store password
https://bugs.kde.org/show_bug.cgi?id=441757 Bruno Friedmann changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #9 from Bruno Friedmann --- Thanks so much Laurent, that was the trick. it not work as expected. Nice tools, and brave developer, thanks opensource, and hope to meet you again one day in the future. I close now the ticket. And will continue to push the new version on obs for openSUSE. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 441757] ruqola doesn't store password
https://bugs.kde.org/show_bug.cgi?id=441757 --- Comment #10 from Bruno Friedmann --- Oh last point is it better to use release made on github mirror than kde git ? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 439228] PC and phone cannot see each other - previously working
https://bugs.kde.org/show_bug.cgi?id=439228 --- Comment #10 from Bruno Friedmann --- It is related to a change in qca and so how the device password was encoded. That's why starting from scratch resolve the trouble. But the software should never ask to reset at that point its configuration. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 439228] PC and phone cannot see each other - previously working
https://bugs.kde.org/show_bug.cgi?id=439228 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #5 from Bruno Friedmann --- Thanks to have reported this bug, I've also seen exactly the same things. There was one time a notification about not being able to open the private key and afterwards nothing was working. openSUSE Tumbleweed - 20210629 Linux 5.12.13-1-default x86_64 GNU/Linux, nvidia: 460.84 Qt: 5.15.2, KDE Frameworks: 5.83.0, Plasma: 5.22.2, kmail2 5.17.2 (21.04.2) kdeconnect 21.04.2-2.1 Deleting the ~/.config/kdeconfig folder and killing the running process help to get a new configuration and start again pairing everything. The root cause is still unknown it happenned around 20210625 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430862] Kde5init crashes in ThumbnailProtocol::get() every time I take a screenshot or start the computer
https://bugs.kde.org/show_bug.cgi?id=430862
Bruno Friedmann changed:
What|Removed |Added
CC||br...@ioda-net.ch
--- Comment #78 from Bruno Friedmann ---
Strangely I've not been hit by this trouble since months and weeks.
Suddendly yesterday I've open-up kdenlive and got numerous kdeinit5 crashes
until I close again kdenlive.
Trace from the crash indicates
Application: kdeinit5 (kdeinit5), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fc41a08ccc0
(LWP 1416))]
[KCrash Handler]
#6 __memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:269
#7 0x7fc418123f81 in memcpy (__len=36864, __src=,
__dest=0x7fc401775000) at /usr/include/bits/string_fortified.h:29
#8 ThumbnailProtocol::get(QUrl const&) (this=0x7ffc72098970, url=...) at
/usr/src/debug/kio-extras5-21.04.0-1.1.x86_64/thumbnail/thumbnail.cpp:301
#9 0x7fc4181afee6 in KIO::SlaveBase::dispatch(int, QByteArray const&)
(this=0x7ffc72098970, command=67, data=...) at
/usr/src/debug/kio-5.81.0-1.2.x86_64/src/core/slavebase.cpp:1215
#10 0x7fc4181a78c6 in KIO::SlaveBase::dispatchLoop() (this=0x7ffc72098970)
at /usr/src/debug/kio-5.81.0-1.2.x86_64/src/core/slavebase.cpp:336
#11 0x7fc418120786 in kdemain(int, char**) (argc=,
argv=0x55f2035fcf90) at
/usr/src/debug/kio-extras5-21.04.0-1.1.x86_64/thumbnail/thumbnail.cpp:124
#12 0x55f201eb0c07 in launch(int, char const*, char const*, char const*,
int, char const*, bool, char const*, bool, char const*) (argc=argc@entry=4,
_name=_name@entry=0x55f2035f0958 "/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so",
args=, args@entry=0x55f2035f0984 "thumbnail", cwd=cwd@entry=0x0,
envc=envc@entry=0, envs=envs@entry=0x55f2035f09fe "", reset_env=false, tty=0x0,
avoid_loops=false, startup_id_str=0x55f201eb3175 "0") at
/usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:692
#13 0x55f201eb23a8 in handle_launcher_request(int, char const*) (sock=8,
who=) at
/usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:1130
#14 0x55f201eb2a36 in handle_requests(pid_t)
(waitForPid=waitForPid@entry=0) at
/usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:1323
#15 0x55f201ead623 in main(int, char**) (argc=3, argv=) at
/usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:1761
[Inferior 1 (process 1416) detached]
On user side journal contain a few informations
mai 04 08:39:25 qt-kt kdeinit5[1022]: Qt: Session management error:
networkIdsList argument is NULL
mai 04 08:39:37 qt-kt kdeinit5[1012]: [107B blob data]
mai 04 08:39:37 qt-kt kdeinit5[1012]: kf.kio.slaves.file: copy()
QUrl("file:///tmp/drkonqi.MXFOqu") to
QUrl("file:///ioda/home/bruno/oc/personnel/Crashes/kdeinit5-20210503-211933.kcrash")
mode>
mai 04 08:39:37 qt-kt kdeinit5[1012]: kf.kio.slaves.file: the file doesn't have
any xattr
mai 04 08:40:00 qt-kt kdeinit5[1284]: Qt: Session management error:
networkIdsList argument is NULL
mai 04 08:40:01 qt-kt kdeinit5[1284]: Using 18432 steps
mai 04 08:40:01 qt-kt drkonqi[1316]: Qt: Session management error:
networkIdsList argument is NULL
mai 04 08:40:01 qt-kt kdeinit5[1315]: Qt: Session management error:
networkIdsList argument is NULL
mai 04 08:40:01 qt-kt kded5[2564]: Registering ":1.505/StatusNotifierItem" to
system tray
mai 04 08:40:01 qt-kt plasmashell[2622]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15:
QML QQuickItem: Binding loop detected for pro>
mai 04 08:40:01 qt-kt kdeinit5[1315]: Using 18432 steps
mai 04 08:40:01 qt-kt kdeinit5[1315]: Using 18432 steps
mai 04 08:40:01 qt-kt kdeinit5[1315]: Using 18432 steps
mai 04 08:40:01 qt-kt drkonqi[1355]: Qt: Session management error:
networkIdsList argument is NULL
mai 04 08:40:01 qt-kt kdeinit5[1354]: Qt: Session management error:
networkIdsList argument is NULL
mai 04 08:40:01 qt-kt kded5[2564]: Registering ":1.508/StatusNotifierItem" to
system tray
mai 04 08:40:02 qt-kt kdeinit5[1354]: Using 18432 steps
mai 04 08:40:02 qt-kt drkonqi[1386]: Qt: Session management error:
networkIdsList argument is NULL
mai 04 08:40:02 qt-kt kded5[2564]: Registering ":1.510/StatusNotifierItem" to
system tray
I'm using systemd-networkd which explain the network null list.
My system is quite up to date being openSUSE Tumbleweed
Linux 5.12.0-1-default x86_64 GNU/Linux
nvidia: 460.73.01
Qt: 5.15.2
KDE Frameworks: 5.81.0
Plasma: 5.21.4
kmail2 5.17.0 (21.04.0)
kinit 5.81.0
The biggest changes occuring in Tumbleweed last week was the introduction of
LLVM12 and Boost 1.76
--
You are receiving this mail because:
You are watching all bug changes.
[Elisa] [Bug 433449] Elisa crashes when navigating through big music directory in Files tab
https://bugs.kde.org/show_bug.cgi?id=433449 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 433449] Elisa crashes when navigating through big music directory in Files tab
https://bugs.kde.org/show_bug.cgi?id=433449 --- Comment #3 from Bruno Friedmann --- Created attachment 138142 --> https://bugs.kde.org/attachment.cgi?id=138142&action=edit New crash information added by DrKonqi elisa (21.04.0) using Qt 5.15.2 - What I was doing when the application crashed: Started elisa, (not run since a long long time) and start browsing a collection in files mode) -- Backtrace (Reduced): #6 0x7fe3161332dd in QHash::isEmpty() const (this=) at /usr/include/qt5/QtCore/qhash.h:285 #7 QHash::empty() const (this=) at /usr/include/qt5/QtCore/qhash.h:544 #8 QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) (this=0x563694ee0290, i=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-4.1.x86_64/src/qml/qml/qqmlincubator.cpp:333 #9 0x7fe316133942 in QQmlIncubationController::incubateFor(int) (this=0x563692e9fe00, msecs=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-4.1.x86_64/src/qml/qml/qqmlincubator.cpp:409 #10 0x7fe315bcfc50 in doActivate(QObject*, int, void**) (sender=0x563692cbe310, signal_index=3, argv=0x7ffd61719830, argv@entry=0x0) at kernel/qobject.cpp:3898 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430862] Kde5init crashes in ThumbnailProtocol::get() every time I take a screenshot or start the computer
https://bugs.kde.org/show_bug.cgi?id=430862 --- Comment #79 from Bruno Friedmann --- to add information to my previous comment. during kdenlive there's those process who crash bruno 6370 24.4 0.5 2201200 343504 ? Tl 17:14 0:07 thumbnail.so [kdeinit5] thumbnail local:/run/user/1502/klaunchergpuFVJ.1.slave-socket local:/run/user/1502/kdenliveHHBSMn.33.slave-socket -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422552] Auto-detect appropriate scale factor for the easy cases (e.g. 4k screen) on X11
https://bugs.kde.org/show_bug.cgi?id=422552 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #4 from Bruno Friedmann --- Hi I'm more than interested to have hidpi issues fixed. I'm using a laptop Dell Precision 7510 which has a internal seiko 15" lcd panel with a 288dpi. Externally I use two monitor : one 4k Dell 2715Q which has 163dpi and a 24" inch FHD HP zr2240w I'm waiting since the last 5 years (oh yeah babe) to be able to use those 3 screens correctly each with it's full resolution at its correct dpi so image, film fonts and graphic element are all handled. I don't really understand how a blind 200% scale factor would be great ? It's would only be ok on the internal screen, but 150% is better for the 27" external and 100% on the 24" FHD... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 474720] New: Kdevelop crashes after screen resume
https://bugs.kde.org/show_bug.cgi?id=474720 Bug ID: 474720 Summary: Kdevelop crashes after screen resume Classification: Applications Product: kdevelop Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: kdevelop (5.12.230801 (23.08.1)) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.3-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: I was working with a few python3 file (without being a project, just opening and working with those). I left my computer for lunch, and when I woke up the screen (computer still running) and unlock the screen, kdevelop crash a few moment after. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f8b30d6939d in __memmove_avx_unaligned_erms () at /lib64/libc.so.6 #5 0x7f8b1bb0f93a in memmove (__len=262100, __src=0x7f8615de6510, __dest=) at /usr/include/bits/string_fortified.h:36 #6 copy_unswapped (rect=..., img=..., dstBytesPerLine=262100, dst=) at qxcbbackingstore.cpp:547 #7 native_sub_image (swap=false, rect=..., src=, dstStride=262100, buffer=) at qxcbbackingstore.cpp:590 #8 QXcbBackingStoreImage::flushPixmap(QRegion const&, bool) (this=0x55b7196964e0, region=, fullRegion=) at qxcbbackingstore.cpp:669 #9 0x7f8b1bb0ff39 in QXcbBackingStoreImage::flushPixmap(QRegion const&, bool) (fullRegion=false, region=..., this=0x55b7196964e0) at qxcbbackingstore.cpp:627 #10 QXcbBackingStoreImage::put(unsigned int, QRegion const&, QPoint const&) (this=0x55b7196964e0, dst=67108876, region=..., offset=) at qxcbbackingstore.cpp:741 #11 0x7f8b1bb10869 in QXcbBackingStore::flush(QWindow*, QRegion const&, QPoint const&) (this=0x55b718736450, window=, region=, offset=...) at qxcbbackingstore.cpp:877 #12 0x7f8b31d5a5d4 in QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) (this=this@entry=0x7f8b0c003210, region=..., window=0x55b718724bf0, offset=...) at painting/qbackingstore.cpp:263 #13 0x7f8b323b294f in QWidgetRepaintManager::flush(QWidget*, QRegion const&, QPlatformTextureList*) (this=this@entry=0x55b718750dd0, widget=0x55b7142a3090, region=..., widgetTextures=) at kernel/qwidgetrepaintmanager.cpp:1198 #14 0x7f8b323b44c9 in QWidgetRepaintManager::flush() (this=0x55b718750dd0) at kernel/qwidgetrepaintmanager.cpp:1096 #15 0x7f8b323b6528 in QWidgetRepaintManager::paintAndFlush() (this=0x55b718750dd0) at kernel/qwidgetrepaintmanager.cpp:1028 #16 0x7f8b323ff051 in QWidgetWindow::handleResizeEvent(QResizeEvent*) (this=this@entry=0x55b718724bf0, event=event@entry=0x7ffdf6c18000) at kernel/qwidgetwindow.cpp:842 #17 0x7f8b32402f02 in QWidgetWindow::event(QEvent*) (this=0x55b718724bf0, event=0x7ffdf6c18000) at kernel/qwidgetwindow.cpp:322 #18 0x7f8b323a519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55b718724bf0, e=0x7ffdf6c18000) at kernel/qapplication.cpp:3640 #19 0x7f8b316ed568 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55b718724bf0, event=0x7ffdf6c18000) at kernel/qcoreapplication.cpp:1064 #20 0x7f8b316ed73e in QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) (receiver=, event=) at kernel/qcoreapplication.cpp:1474 #21 0x7f8b31b7959c in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) (e=) at kernel/qguiapplication.cpp:2610 #22 0x7f8b31b5036c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169 #23 0x7f8b1bb1b1aa in xcbSourceDispatch(GSource*, GSourceFunc, gpointer) (source=) at qxcbeventdispatcher.cpp:105 #24 0x7f8b2d3169d8 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #25 0x7f8b2d316de8 in () at /lib64/libglib-2.0.so.0 #26 0x7f8b2d316e7c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #27 0x7f8b317464a6 in QEventDispatcherGlib::processEvents(QFlags) (this=0x55b713d7f1e0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f8b316ebffb in QEventLoop::exec(QFlags) (this=this@entry=0x7ffdf6c18280, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #29 0x7f8b316f4490 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #30 0x7f8b31b7055c in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1870 #31 0x7f8b323a5115 in QApplication::exec() () at kernel/qapplication.cpp:2832 #32 0x55b713a2d61b in main(int, char**) (argc=, argv=) at /usr/src/debug/kdevelop-23.08.1/a
[KScreen] [Bug 422552] Auto-detect appropriate scale factor for the easy cases (e.g. 4k screen) on X11
https://bugs.kde.org/show_bug.cgi?id=422552 --- Comment #18 from Bruno Friedmann --- I'm a bit sad to see this kind of conclusion, especially waiting on that since 2015. At no Wayland is a no go: because after waiting the same amount time wayland and nvidia are just not usable. And intel with wayland look like its works, if you accept to loose main functionality, like being able to restore your last session. 2023 start with mitigated feeling. At least thanks to have tried, I would not care about first time, first time is a one shot, opening your session day by day and get it configured exactly like yesterday would have been magic. Regards and again thanks a lot for the whole effort made on this. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361332] Upgrade from 4.14.2 to 15.12.3 breaks syncing with original ICS calendar file
https://bugs.kde.org/show_bug.cgi?id=361332 --- Comment #3 from Bruno Friedmann --- Can't tell you anymore, this method of work has been replaced by other (nextcloud) way. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 400304] akonadi_imap_resource segmentation fault crash when idle on GMail account
https://bugs.kde.org/show_bug.cgi?id=400304 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #8 from Bruno Friedmann --- Not seen recently with following software stack openSUSE Tumbleweed - 20221024 Linux 6.0.3-1-default x86_64 GNU/Linux, nvidia: 515.76 Qt: 5.15.6, KDE Frameworks: 5.99.0, Plasma: 5.26.1, kmail2 5.21.2 (22.08.2) akonadi 5.21.2 (22.08.2) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 371006] Printed website uses wrong encoding
https://bugs.kde.org/show_bug.cgi?id=371006 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #7 from Bruno Friedmann --- Tested and work with openSUSE Tumbleweed - 20221029 Linux 6.0.5-1-default x86_64 GNU/Linux nvidia: 515.76 Qt: 5.15.6 KDE Frameworks: 5.99.0 Plasma: 5.26.2 kmail2 5.21.2 (22.08.2) Closing. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 410021] Various hi-dpi problems
https://bugs.kde.org/show_bug.cgi?id=410021 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #2 from Bruno Friedmann --- With Ruqola 1.5.54(alpha) on openSUSE Tumbleweed. Linux 5.16.0-1-default x86_64 GNU/Linux nvidia: 470.94 Qt: 5.15.2 KDE Frameworks: 5.90.0 Plasma: 5.23.5 kmail2 5.19.1 (21.12.1) QT_SCREEN_SCALE_FACTORS=DP-5.8=1.5;DP-5.1=1.0;DP-0=1.5 I'm using ruqola on my second screen (hp zr2240w which should have a 96dpi DP-5.1 with normally a scale at 1.0 My main screen is a dell P2715Q 4K (DP-5.8 with a scale factor 1.5) I'm still using X11 with nvidia drivers. Recently I remove all forced dpi parameter (launch x11 with --dpi=144, font rendering forced at 144dpi, and remove the scale for the additional screen). I know that multi scaling under X11 is not that well supported, but here it seems that different parts of the software are rendered with non consistent way Due to some privacy I can expose the whole conversation, but it's visible that between nickname (big + bold) and conversation text (two time too small) there's differences. I hope you will be able to track down those glitches. ps : if you need more printscreen I can provide you some by private channel. Just ask. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 410021] Various hi-dpi problems
https://bugs.kde.org/show_bug.cgi?id=410021 --- Comment #3 from Bruno Friedmann --- Created attachment 145577 --> https://bugs.kde.org/attachment.cgi?id=145577&action=edit ruqola inconsistend dpi rendering Illustrating rendering glitches. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401744] Delete message lead to crash
https://bugs.kde.org/show_bug.cgi?id=401744 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Bruno Friedmann --- Actually work with openSUSE Tumbleweed Linux 5.10.4-1-default x86_64 GNU/Linux, nvidia: 460.32.03 Qt: 5.15.2 KDE Frameworks: 5.77.0 Plasma: 5.20.5 kmail2 5.16.0 (20.12.0) -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 437595] New: konversation crash when editing defaut identities
https://bugs.kde.org/show_bug.cgi?id=437595 Bug ID: 437595 Summary: konversation crash when editing defaut identities Product: konversation Version: 1.8.21041 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: konversation (1.8.21041) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.3-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was firstly adding new server (lberachat). I've clicked on the edit buton of idendity (default) To renew my password. Once I close the 3 modal windows the crash occurs. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konversation (konversation), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f22ff964880 (LWP 3402))] [KCrash Handler] #6 0x7f2302347996 in operator== (s1=..., s2=...) at text/qstring.cpp:3437 #7 0x562da9701579 in NickInfo::setAccount (this=0x0, name=...) at /usr/src/debug/konversation-21.04.1-1.1.x86_64/src/irc/nickinfo.cpp:250 #8 0x562da970e155 in InputFilter::parseClientCommand (this=0x562dabf97df0, prefix=..., command=..., parameterList=..., messageTags=...) at /usr/include/qt5/QtCore/qshareddata.h:160 #9 0x562da96cb4ad in InputFilter::parseLine (line=..., this=0x562dabf97df0) at /usr/src/debug/konversation-21.04.1-1.1.x86_64/src/irc/inputfilter.cpp:123 #10 Server::processIncomingData (this=0x7ffd9a0fbc10) at /usr/src/debug/konversation-21.04.1-1.1.x86_64/src/irc/server.cpp:1366 #11 0x7f23024ddc17 in QtPrivate::QSlotObjectBase::call (a=0x7ffd9a0fbe30, r=0x562dabf97cd0, this=0x562db22666a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x562dabf97d40, signal_index=3, argv=argv@entry=0x7ffd9a0fbe30) at kernel/qobject.cpp:3886 #13 0x7f23024d6f60 in QMetaObject::activate (sender=, m=m@entry=0x7f230278cba0, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd9a0fbe30) at kernel/qobject.cpp:3946 #14 0x7f23024e1b9a in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #15 0x7f23024d394f in QObject::event (this=0x562dabf97d40, e=0x7ffd9a0fbfa0) at kernel/qobject.cpp:1336 #16 0x7f2303069aff in QApplicationPrivate::notify_helper (this=, receiver=0x562dabf97d40, e=0x7ffd9a0fbfa0) at kernel/qapplication.cpp:3632 #17 0x7f23024a713a in QCoreApplication::notifyInternal2 (receiver=0x562dabf97d40, event=0x7ffd9a0fbfa0) at kernel/qcoreapplication.cpp:1063 #18 0x7f23024fe0f3 in QTimerInfoList::activateTimers (this=0x562dab2078f0) at kernel/qtimerinfo_unix.cpp:643 #19 0x7f23024fe9ac in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #20 idleTimerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:230 #21 0x7f23003b28b7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #22 0x7f23003b2c38 in ?? () from /usr/lib64/libglib-2.0.so.0 #23 0x7f23003b2cef in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #24 0x7f23024fed30 in QEventDispatcherGlib::processEvents (this=0x562dab207bd0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #25 0x7f23024a5b7b in QEventLoop::exec (this=this@entry=0x7ffd9a0fc1e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #26 0x7f23024addb0 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #27 0x7f2302908a9c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #28 0x7f2303069a75 in QApplication::exec () at kernel/qapplication.cpp:2824 #29 0x562da9647d3f in main (argc=, argv=0x7ffd9a0fc300) at /usr/src/debug/konversation-21.04.1-1.1.x86_64/src/main.cpp:149 [Inferior 1 (process 3402) 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.
[karbon] [Bug 305627] work with your file, set some tranparency, export to pdf, save and crash
https://bugs.kde.org/show_bug.cgi?id=305627 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #5 from Bruno Friedmann --- Due to lack of response, Karbon was drop here. So I'm not able to test it 8 years after. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 305427] Karbon: moving lines / playing with undo undo, one redo -> crash
https://bugs.kde.org/show_bug.cgi?id=305427 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UNMAINTAINED --- Comment #6 from Bruno Friedmann --- Due to lack of response, Karbon was drop here. So I'm not able to test it 8 years after. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 305447] Playing with Artistic text after a long period of work with shapes
https://bugs.kde.org/show_bug.cgi?id=305447 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UNMAINTAINED --- Comment #4 from Bruno Friedmann --- Due to lack of response, Karbon was drop here. So I'm not able to test it 8 years after. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 361679] kmail2 stuck on quit
https://bugs.kde.org/show_bug.cgi?id=361679 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Bruno Friedmann --- Seems to work now, even with the failing component (option empty local trash when leaving) System is now openSUSE Tumbleweed with Linux 5.9.12-1-default x86_64 GNU/Linux, nvidia: 450.80.02, Qt: 5.15.2, KDE Frameworks: 5.76.0, Plasma: 5.20.4, kmail2 5.15.3 (20.08.3) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376822] empty trash or all trash on imap account akonadi doesn't continue
https://bugs.kde.org/show_bug.cgi?id=376822 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Bruno Friedmann --- Work wtih Linux 5.9.12-1-default x86_64 GNU/Linux, nvidia: 450.80.02 Qt: 5.15.2, KDE Frameworks: 5.76.0, Plasma: 5.20.4, kmail2 5.15.3 (20.08.3) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358866] Kmail5 crash dialog box at starting
https://bugs.kde.org/show_bug.cgi?id=358866 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Bruno Friedmann --- Work with Linux 5.9.12-1-default x86_64 GNU/Linux, nvidia: 450.80.02 Qt: 5.15.2, KDE Frameworks: 5.76.0, Plasma: 5.20.4, kmail2 5.15.3 (20.08.3) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359260] Launching kmail5 give crash
https://bugs.kde.org/show_bug.cgi?id=359260 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Bruno Friedmann --- Works with openSUSE Tumbleweed Linux 5.9.12-1-default x86_64 GNU/Linux nvidia: 450.80.02 Qt: 5.15.2 KDE Frameworks: 5.76.0 Plasma: 5.20.4 kmail2 5.15.3 (20.08.3) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359553] Lauching kmail5 crash
https://bugs.kde.org/show_bug.cgi?id=359553 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Bruno Friedmann --- Works with openSUSE Tumbleweed Linux 5.9.12-1-default x86_64 GNU/Linux nvidia: 450.80.02 Qt: 5.15.2 KDE Frameworks: 5.76.0 Plasma: 5.20.4 kmail2 5.15.3 (20.08.3) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358815] Kmail5 crash at closing
https://bugs.kde.org/show_bug.cgi?id=358815 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Bruno Friedmann --- Works with openSUSE Tumbleweed Linux 5.9.12-1-default x86_64 GNU/Linux nvidia: 450.80.02 Qt: 5.15.2 KDE Frameworks: 5.76.0 Plasma: 5.20.4 kmail2 5.15.3 (20.08.3) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 361675] Akonadictl stop return exit 255 (postgresql)
https://bugs.kde.org/show_bug.cgi?id=361675 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Bruno Friedmann --- Works with openSUSE Tumbleweed Linux 5.9.12-1-default x86_64 GNU/Linux nvidia: 450.80.02 Qt: 5.15.2 KDE Frameworks: 5.76.0 Plasma: 5.20.4 kmail2 5.15.3 (20.08.3) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 276214] Crash when dbus exits (crash in QDBusAbstractInterfacePrivate dtor)
https://bugs.kde.org/show_bug.cgi?id=276214 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #9 from Bruno Friedmann --- Works with openSUSE Tumbleweed Linux 5.9.12-1-default x86_64 GNU/Linux nvidia: 450.80.02 Qt: 5.15.2 KDE Frameworks: 5.76.0 Plasma: 5.20.4 kmail2 5.15.3 (20.08.3) -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 329814] Eclipse crashes when closing the find dialog and using the oxygen-gtk GTK2 theme
https://bugs.kde.org/show_bug.cgi?id=329814 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME --- Comment #30 from Bruno Friedmann --- Works with openSUSE Tumbleweed Linux 5.9.12-1-default x86_64 GNU/Linux nvidia: 450.80.02 Qt: 5.15.2 KDE Frameworks: 5.76.0 Plasma: 5.20.4 kmail2 5.15.3 (20.08.3) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 430780] New: With multiple identity, reply doesn't check or use the right one
https://bugs.kde.org/show_bug.cgi?id=430780 Bug ID: 430780 Summary: With multiple identity, reply doesn't check or use the right one Product: kmail2 Version: 5.15.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- SUMMARY When you have several (for example 2 identities for one account) when you reply to a message received for identity B, it always use the default. STEPS TO REPRODUCE 1. Create two identities for one email account, domain A.org and B.org are aliases and you have 2 email: a...@a.org and b...@b.org both using the same account on your server. a...@a.org is the main default email for that account 2. Write a mail and send it with b...@b.org (selecting this identity in composer) ask your recipient to reply to it. 3. When you receive the reply, you want also to reply. The composer will use the a...@a.org indentity even if the mail is addressed to b...@b.org OBSERVED RESULT The wrong identity is used. EXPECTED RESULT If matching use the right identity, when multiple identity exist, by default. SOFTWARE/OS VERSIONS Linux 5.9.14-1-default x86_64 GNU/Linux, nvidia: 460.27.04 Qt: 5.15.2, KDE Frameworks: 5.77.0, Plasma: 5.20.4, kmail2 5.15.3 (20.08.3) ADDITIONAL INFORMATION Bonus point, if you start your reply and change whatever character in subject or body, changing identity afterwards will not apply the Signature of the new choosed identity. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361332] Upgrade from 4.14.2 to 15.12.3 breaks syncing with original ICS calendar file
https://bugs.kde.org/show_bug.cgi?id=361332 --- Comment #6 from Bruno Friedmann --- I'm not the reporter, and don't use anymore this technics, so I can't tell you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422552] Auto-detect appropriate scale factor for the easy cases (e.g. 4k screen) on X11
https://bugs.kde.org/show_bug.cgi?id=422552 --- Comment #9 from Bruno Friedmann --- @soredake maybe you miss the subject of this bug "on X11" ;-) -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 363676] Each time a plasma5 session is started one or more drkonqi segfault
https://bugs.kde.org/show_bug.cgi?id=363676 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UNMAINTAINED --- Comment #3 from Bruno Friedmann --- This is no more seen with drkonqi 5.16 Most of crashes seen at startup time are now akonadi or baloo/miloo related. -- 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 #37 from Bruno Friedmann --- Created attachment 121413 --> https://bugs.kde.org/attachment.cgi?id=121413&action=edit New crash information added by DrKonqi akonadiserver (5.11.2) using Qt 5.13.0 - What I was doing when the application crashed: As usual to reproduce the crash, delete some mail, then move some others, and suddently the application become freeze (no action). Related information found in ~/.local/share/sddm/xorg-session.log ProtocolException thrown:Timeout while waiting for data ProtocolException thrown:ProtocolException thrown:LOGIN CALLBACK in libCVP11LCB: CK_RV CB_Initialize(CK_CONTEXT_PTR, CK_C_INITIALIZE_ARGS_PTR, CK_ULONG_PTR) ProtocolException thrown:Timeout while waiting for dataTimeout while waiting for dataProtocolException thrown:Timeout while waiting for data Timeout while waiting for data ProtocolException thrown:Timeout while waiting for data ProtocolException thrown:Timeout while waiting for data ProtocolException thrown:Timeout while waiting for data ProtocolException thrown:Timeout while waiting for data ProtocolException thrown:Timeout while waiting for data ProtocolException thrown:Timeout while waiting for data ProtocolException thrown:Timeout while waiting for data ProtocolException thrown:ProtocolException thrown:Timeout while waiting for dataTimeout while waiting for data ProtocolException thrown:Failed to write data to stream terminate called after throwing an instance of 'Akonadi::ProtocolException' what(): Failed to write data to stream KCrash: Application 'akonadiserver' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit ProtocolException thrown:Timeout while waiting for data Server is dovecot imap on TLS -- Backtrace (Reduced): #11 0x7f8a193c5e7b in qTerminate () at global/qglobal.cpp:3245 #12 0x7f8a193c78c2 in QThreadPrivate::start (arg=0x556afc0bcd60) at thread/qthread_unix.cpp:372 [...] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413252] New: Plama crash dialog
https://bugs.kde.org/show_bug.cgi?id=413252 Bug ID: 413252 Summary: Plama crash dialog Product: plasmashell Version: 5.17.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: br...@ioda-net.ch CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.5-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: After login into my session icon of plasma crash was there. I'm using also slideshow with random order on several folders of images. If it has any interest, images are link to original destination all on btrfs partition. Konsole has also now an error bash: mc: line 1: syntax error: unexpected end of file bash: error importing function definition for `mc' This is the new Tumbleweed 20191016 version -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f97d217b680 (LWP 4397))] Thread 5 (Thread 0x7f97b7fff700 (LWP 4503)): #0 0x7f97d39e66a5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f97d45090af in QWaitConditionPrivate::wait (deadline=..., this=0x7f97c41d0eb0) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x557a25d35e60, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f97d4509199 in QWaitCondition::wait (this=0x557a25d35e68, mutex=0x557a25d35e60, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f97d62052f9 in ?? () from /usr/lib64/libQt5Quick.so.5 #5 0x7f97d620559d in ?? () from /usr/lib64/libQt5Quick.so.5 #6 0x7f97d45031a2 in QThreadPrivate::start (arg=0x557a25d35de0) at thread/qthread_unix.cpp:360 #7 0x7f97d39dff2a in start_thread () from /lib64/libpthread.so.0 #8 0x7f97d418a4af in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f97ce299700 (LWP 4450)): #0 0x7f97d417fbdf in poll () from /lib64/libc.so.6 #1 0x7f97d2cee3ce in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f97d2cee49f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f97d472199b in QEventDispatcherGlib::processEvents (this=0x7f97c4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f97d46ca0db in QEventLoop::exec (this=this@entry=0x7f97ce298c80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f97d4502021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f97d5e8b3f5 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7f97d45031a2 in QThreadPrivate::start (arg=0x557a26025dd0) at thread/qthread_unix.cpp:360 #8 0x7f97d39dff2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f97d418a4af in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f97cf536700 (LWP 4428)): #0 0x7f97d417fbdf in poll () from /lib64/libc.so.6 #1 0x7f97d2cee3ce in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f97d2cee49f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f97d472199b in QEventDispatcherGlib::processEvents (this=0x7f97cb60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f97d46ca0db in QEventLoop::exec (this=this@entry=0x7f97cf535c70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f97d4502021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f97d4ff64f6 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f97d45031a2 in QThreadPrivate::start (arg=0x7f97d5078d80) at thread/qthread_unix.cpp:360 #8 0x7f97d39dff2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f97d418a4af in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f97d012b700 (LWP 4405)): #0 0x7f97d417fbdf in poll () from /lib64/libc.so.6 #1 0x7f97d6613742 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f97d66143fa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f97d0302f90 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f97d45031a2 in QThreadPrivate::start (arg=0x557a25d39d80) at thread/qthread_unix.cpp:360 #5 0x7f97d39dff2a in start_thread () from /lib64/libpthread.so.0 #6 0x7f97d418a4af in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f97d217b680 (LWP 4397)): [KCrash Handler] #6 QSortFilterProxyModelPrivate::build_source_to_proxy_mapping (proxy_to_source=..., source_to_proxy=..., this=0x557a26286bb0) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #7 0x7f97d469f95a in QSortFilterProxyModelPr
[Akonadi] [Bug 413528] New: akonadi crashes after changing imap server
https://bugs.kde.org/show_bug.cgi?id=413528 Bug ID: 413528 Summary: akonadi crashes after changing imap server Product: Akonadi Version: 5.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: akonadiserver (5.12.2) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.6-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I moved (with imapsync) my email to a new server openSUSE Tumbleweed dovecot 2.3.8 after changing the name of the server kmail & akonadi start behaving strangely with crash, or telling that the certificates has problem when no other programs (like thunderbird k9-mail and so on doesn't have) Most to the crashes are not captured due to drkonqi crashing too. The crash can be reproduced every time. -- Backtrace (Reduced): #11 0x7fd92d444ea3 in qTerminate () at global/qglobal.cpp:3252 #12 0x7fd92d446900 in QThreadPrivate::start (arg=0x562e0a555930) at thread/qthread_unix.cpp:372 [...] The reporter indicates this bug may be a duplicate of or related to bug 413205. Possible duplicates by query: bug 413355, bug 413349, bug 413345, bug 413319, bug 413291. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404641] Lots of crud left in plasma.org.kde.plasma.desktopappletsrc left over from no-longer used desktop applets.
https://bugs.kde.org/show_bug.cgi?id=404641 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #1 from Bruno Friedmann --- +1 for a nice way of cleaning (maybe export a backup of only running actual session is easier?) About you plasma black screen, it sometimes also happen here but I wasn't able to find a pattern to make it reproducible. You can use the plasmashell --replace to restart your desktop (and at that time everything works). My ~/.config/plasma-org.kde.plasma.desktop-appletsrc is 12k only. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 403757] Changing mail signature script cause korganizer to crash (akonadi?)
https://bugs.kde.org/show_bug.cgi?id=403757 Bruno Friedmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Bruno Friedmann --- Hi Laurent, with newer version there's no more crashes openSUSE Tumbleweed Linux 5.2.8-1-default x86_64 GNU/Linux, nvidia: 430.34 Qt: 5.13.0, KDE Frameworks: 5.60.0, Plasma: 5.16.4, kmail2 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406117] New: kmail & akonadi crashes
https://bugs.kde.org/show_bug.cgi?id=406117 Bug ID: 406117 Summary: kmail & akonadi crashes Product: kmail2 Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: kmail (5.10.3) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 5.0.3-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: When I delete several mail or move several mail at once with multiple select and or keyboard shortcut m there's a hang (messages become greyed) but nothing change, and the interface freeze, you can click on other folders but nothing happend except akonadi or kmail crashes. This behaviour is increasing since the last few weeks, becoming more and more frequent. Database used PostgreSQL 10.7 (libpq is 11.2) baloo is disabled by balooctl disable as it doesn't work. Running akonadictl fsck or vacuum help sometime but not always. All email parts are stored inside the database. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa6e7be7a40 (LWP 3736))] Thread 35 (Thread 0x7fa597fff700 (LWP 30716)): #0 0x7fa6f65f4428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6f024a7e7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fa6f024b13a in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fa6f024b222 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fa6f0208bd1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fa6f020b516 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fa6f020b7d4 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fa6f024d341 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fa6f65edfab in start_thread () at /lib64/libpthread.so.0 #9 0x7fa6f8c486af in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7fa6b67fc700 (LWP 30715)): #0 0x7fa6f65f4428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6f024a7e7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fa6f024b13a in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fa6f024b222 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fa6f0208bd1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fa6f020b516 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fa6f020b7d4 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fa6f024d341 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fa6f65edfab in start_thread () at /lib64/libpthread.so.0 #9 0x7fa6f8c486af in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7fa637bff700 (LWP 30714)): #0 0x7fa6f65f4428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6f024a7e7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fa6f024b13a in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fa6f024b222 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fa6f0208bd1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fa6f020b516 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fa6f020b7d4 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fa6f024d341 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fa6f65edfab in start_thread () at /lib64/libpthread.so.0 #9 0x7fa6f8c486af in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7fa595e0a700 (LWP 30713)): #0 0x7fa6f65f4428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6f024a7e7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fa6f024b13a in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fa6f024b222 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fa6f0208bd1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fa6f020b516 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fa6f020b7d4 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fa6f024d341 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fa6f65edfab in start_thread () at /lib64/libpthread.so.0 #9 0x7fa6f8c486af in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7fa596e0c700 (LWP 18470)): #0 0x7fa6f65f4428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6f024a7e7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fa6f024b13a in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fa6f024b222 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fa6f0208bd1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fa6f020b516 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fa6f020b7d4 in ()
[Akonadi] [Bug 400304] akonadi_imap_resource segmentation fault crash when idle on GMail account
https://bugs.kde.org/show_bug.cgi?id=400304 Bruno Friedmann changed: What|Removed |Added Version|5.9.1 |5.9.2 CC||br...@ioda-net.ch --- Comment #1 from Bruno Friedmann --- As I have 12 imap account and one of them is gmail I've seen also crashes like the following one Application: akonadi_imap_resource (akonadi_imap_resource), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8ac732f9c0 (LWP 2820))] Thread 8 (Thread 0x7f8aa7fff700 (LWP 3137)): #0 0x7f8ada40e2c9 in __GI___poll (fds=0x7f8a9c005e30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8ad7cc4f46 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8ad7cc506c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8adab4cadb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8adaaf9adb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ada948de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8ada9529b7 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f8ad943f554 in start_thread (arg=) at pthread_create.c:463 #8 0x7f8ada418ccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f8ab5dcd700 (LWP 3027)): #0 0x7f8ada413739 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f8ada947a24 in QSemaphore::acquire(int) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8adae75d14 in () at /usr/lib64/libQt5Network.so.5 #3 0x7f8ada9529b7 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f8ad943f554 in start_thread (arg=) at pthread_create.c:463 #5 0x7f8ada418ccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f8ab65ce700 (LWP 3023)): #0 0x7f8ada40e2c9 in __GI___poll (fds=0x7f8aac004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8ad7cc4f46 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8ad7cc506c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8adab4cadb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8adaaf9adb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ada948de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8ada9529b7 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f8ad943f554 in start_thread (arg=) at pthread_create.c:463 #8 0x7f8ada418ccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f8ab6dee700 (LWP 2979)): #0 0x7f8ada409d34 in __GI___libc_read (fd=25, buf=0x7f8ab6ded9b0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f8ad7d0a4b0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8ad7cc4a4b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8ad7cc4ef0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8ad7cc506c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8adab4cadb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8adaaf9adb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f8ada948de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f8ada9529b7 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f8ad943f554 in start_thread (arg=) at pthread_create.c:463 #10 0x7f8ada418ccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f8ab7fff700 (LWP 2932)): [KCrash Handler] #6 0x7f8ada35608b in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7f8ada33f4e9 in __GI_abort () at abort.c:79 #8 0x7f8ada78c943 in () at /usr/lib64/libstdc++.so.6 #9 0x7f8ada792898 in () at /usr/lib64/libstdc++.so.6 #10 0x7f8ada7928e3 in () at /usr/lib64/libstdc++.so.6 #11 0x7f8ada910dc5 in qt_assert(char const*, char const*, int) () at /usr/lib64/libQt5Core.so.5 #12 0x7f8ada913198 in () at /usr/lib64/libQt5Core.so.5 #13 0x7f8ad943f554 in start_thread (arg=) at pthread_create.c:463 #14 0x7f8ada418ccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f8abc86d700 (LWP 2922)): #0 0x7f8ad7d0b854 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f8ad7cc4afb in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8ad7cc4fd8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8ad7cc506c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8adab4cadb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8adaaf9adb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8ada948de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x
[kdelibs] [Bug 277249] Applications are unable to launch as root
https://bugs.kde.org/show_bug.cgi?id=277249 Bruno Friedmann changed: What|Removed |Added Resolution|WAITINGFORINFO |DOWNSTREAM Status|NEEDSINFO |RESOLVED --- Comment #10 from Bruno Friedmann --- The distribution version involved here are long time out of maintenance. So closing. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422433] New: akonadi constanly crash when updating database (due to rollback)
https://bugs.kde.org/show_bug.cgi?id=422433
Bug ID: 422433
Summary: akonadi constanly crash when updating database (due to
rollback)
Product: Akonadi
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: server
Assignee: kdepim-b...@kde.org
Reporter: br...@ioda-net.ch
Target Milestone: ---
Application: akonadiserver (5.14.1 (20.04.0))
Qt Version: 5.14.1
Frameworks Version: 5.70.0
Operating System: Linux 5.6.14-1-default x86_64
Windowing system: X11
Distribution: "openSUSE Tumbleweed"
-- Information about the crash:
- What I was doing when the application crashed: Start deleting several mails
and going back and forth on 3 differents accounts.
Akonadi crash constantly even after executing an fsck action.
Error found on console
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver: Error code: ""
org.kde.pim.akonadiserver: Database error: DataStore::commitTransaction
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver: DB error: "could not receive data from server:
Bad file descriptor\n()"
org.kde.pim.akonadiserver: Error text: "could not receive data from server:
Bad file descriptor\n() QPSQL: Unable to create query"
org.kde.pim.akonadiserver: Values: QMap((":0", QVariant(QDateTime,
QDateTime(2020-06-03 19:52:26.642 UTC Qt::UTC)))(":1", QVariant(qlonglong,
1348604)))
org.kde.pim.akonadiserver: Query: "UPDATE PimItemTable SET atime = :0 WHERE (
( PimItemTable.id = :1 ) )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.akonadiserver: Database error: DataStore::rollbackTransaction
org.kde.pim.akonadiserver: Last driver error: "QPSQL: Could not rollback
transaction"
org.kde.pim.akonadiserver: Last database error: "could not receive data from
server: Bad file descriptor\n()"
org.kde.pim.akonadiserver: Last driver error: "QPSQL: Could not commit
transaction"
org.kde.pim.akonadiserver: Last database error: "could not receive data from
server: Bad file descriptor\n()"
org.kde.pim.akonadiserver: Error code: ""
org.kde.pim.akonadiserver: DB error: "could not receive data from server:
Bad file descriptor\n()"
org.kde.pim.akonadiserver: Error text: "could not receive data from server:
Bad file descriptor\n() QPSQL: Unable to create query"
org.kde.pim.akonadiserver: Values: QMap((":0", QVariant(qlonglong, 2))(":1",
QVariant(qlonglong, 33))(":2", QVariant(qlonglong, 660)))
org.kde.pim.akonadiserver: Query: "SELECT count(DISTINCT PimItemTable.id),
sum(PimItemTable.size), sum(CASE WHEN ( SeenFlags.Flag_id IS NOT NULL OR
IgnoredFlags.Flag_id IS NOT NULL ) THEN 1 ELSE 0 END) FROM PimItemTable LEFT
JOIN PimItemFlagRelation AS SeenFlags ON ( PimItemTable.id =
SeenFlags.PimItem_id AND SeenFlags.Flag_id = :0 ) LEFT JOIN PimItemFlagRelation
AS IgnoredFlags ON ( PimItemTable.id = IgnoredFlags.PimItem_id AND
IgnoredFlags.Flag_id = :1 ) WHERE ( collectionId = :2 )"
org.kde.pim.akonadiserver: Database error: DataStore::rollbackTransaction
org.kde.pim.akonadiserver: Last driver error: "QPSQL: Could not rollback
transaction"
org.kde.pim.akonadiserver: Last database error: "could not receive data from
server: Bad file descriptor\n()"
The crash can be reproduced every time.
-- Backtrace (Reduced):
#4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5 0x7f87793a253d in __GI_abort () at abort.c:79
#6 0x7f87795ff816 in __gnu_cxx::__verbose_terminate_handler () at
../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#7 0x7f877960a918 in __cxxabiv1::__terminate (handler=) at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48
#8 0x7f877960a983 in std::terminate () at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:58
The reporter indicates this bug may be a duplicate of or related to bug 422017.
Possible duplicates by query: bug 422017, bug 421576, bug 420414, bug 419798,
bug 418804.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 422433] akonadi constanly crash when updating database (due to rollback)
https://bugs.kde.org/show_bug.cgi?id=422433 --- Comment #1 from Bruno Friedmann --- Created attachment 129040 --> https://bugs.kde.org/attachment.cgi?id=129040&action=edit Full trace Someone should ask admin why kcrash attachement can't be uploaded directly. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 415956] New: Akonadi crash when reading and moving mail
https://bugs.kde.org/show_bug.cgi?id=415956 Bug ID: 415956 Summary: Akonadi crash when reading and moving mail Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: akonadiserver (5.13.0 (19.12.0)) Qt Version: 5.13.1 Frameworks Version: 5.65.0 Operating System: Linux 5.3.12-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: After a night where kmail was running I was sorting my email, some trashed some moved around in folders, after the second delete the mail stay in inbox, and then some seconds after 5 to 10 the crash occurs. No special messages found in system logs except the traditionnal ProtocolException thrown:Timeout while waiting for data Nor any special message from the database (central postgresql) The crash can be reproduced every time. -- Backtrace (Reduced): #11 0x7f511be9bea3 in qTerminate () at global/qglobal.cpp:3252 #12 0x7f511be9d900 in QThreadPrivate::start (arg=0x55eed7568160) at thread/qthread_unix.cpp:372 [...] The reporter indicates this bug may be a duplicate of or related to bug 414974, bug 414885. Possible duplicates by query: bug 415930, bug 415815, bug 415634, bug 415339, bug 415068. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 415956] Akonadi crash when reading and moving mail
https://bugs.kde.org/show_bug.cgi?id=415956 --- Comment #1 from Bruno Friedmann --- Created attachment 124952 --> https://bugs.kde.org/attachment.cgi?id=124952&action=edit Complete backtrace This as to be done manually drkonqi getting an error when it submit the bug about can't create attachement or private comment. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 415956] Akonadi crash when reading and moving mail
https://bugs.kde.org/show_bug.cgi?id=415956 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 415956] Akonadi 19.12.x crash when socket file for connection to postgresql database disappear
https://bugs.kde.org/show_bug.cgi?id=415956
Bruno Friedmann changed:
What|Removed |Added
Summary|Akonadi crash when reading |Akonadi 19.12.x crash when
|and moving mail |socket file for connection
||to postgresql database
||disappear
--- Comment #2 from Bruno Friedmann ---
Application: akonadiserver (5.13.0 (19.12.0))
Qt Version: 5.13.1
Frameworks Version: 5.65.0
Operating System: Linux 5.3.12-2-default x86_64
Distribution: "openSUSE Tumbleweed"
-- Information about the crash:
- What I was doing when the application crashed:
Reading mail after having let kmail2 open and idle during 2,3 hours.
One interesting log in console
ProtocolException thrown:Timeout while waiting for data
ProtocolException thrown:ProtocolException thrown:Timeout while waiting for
dataProtocolException thrown:Timeout while waiting for data
Timeout while waiting for data
ProtocolException thrown:ProtocolException thrown:Timeout while waiting for
dataTimeout while waiting for data
ProtocolException thrown:Timeout while waiting for data
org.kde.pim.akonadiserver: NotificationSubscriber for
"MailFilterCollectionMonitor - 94151401733072" : timeout writing into stream
org.kde.pim.akonadiserver: Subscriber "SpecialCollectionsMonitor -
94000591742048" disconnected
org.kde.pim.akonadiserver: Subscriber "KMail Kernel ETM - 94000592474800"
disconnected
ProtocolException thrown:Failed to write data to stream
terminate called after throwing an instance of 'Akonadi::ProtocolException'
what(): Failed to write data to stream
KCrash: Application 'akonadiserver' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
sock_file=/run/user/1502/kdeinit5__0
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver: Error code: ""
org.kde.pim.akonadiserver: DB error: "could not receive data from server:
Bad file descriptor\n()"
org.kde.pim.akonadiserver: Error text: "could not receive data from server:
Bad file descriptor\n() QPSQL: Unable to create query"
org.kde.pim.akonadiserver: Values: QMap((":0", QVariant(qlonglong, 555)))
org.kde.pim.akonadiserver: Query: "SELECT
CollectionMimeTypeRelation.Collection_id,
CollectionMimeTypeRelation.MimeType_id, MimeTypeTable.name FROM
CollectionMimeTypeRelation LEFT JOIN MimeTypeTable ON ( MimeTypeTable.id =
CollectionMimeTypeRelation.MimeType_id ) WHERE (
CollectionMimeTypeRelation.Collection_id IN ( :0 ) ) ORDER BY
CollectionMimeTypeRelation.Collection_id ASC"
org.kde.pim.akonadiserver: Handler exception when handling command
FetchCollections on connection akonadi_mailfilter_agent (0x55ba851efb50) :
Unable to retrieve mimetypes for listing
org.kde.pim.akonadiserver: Shutting down "akonadi_mailfilter_agent" ...
ProtocolException thrown:Timeout while waiting for data
ProtocolException thrown:Timeout while waiting for data
Database inside log
Jan 09 14:12:05 qt-kt postgres[21454]: [7-1] 2020-01-09 14:12:05.264 CET 1
21454 bf_akonadi bf_akonadi LOG: could not receive data from client:
Connection reset by peer
The socket file has been recreated at crash time
ll /run/postgresql/
total 8
srwxrwxrwx 1 postgres postgres 0 Jan 9 14:09 .s.PGSQL.5432
-rw--- 1 postgres postgres 60 Jan 9 14:09 .s.PGSQL.5432.lock
-rw-r--r-- 1 postgres postgres 5 Jan 7 20:23 postmaster.pid
while the server is up since Jan 5th.
So while it is certainly not ideal to have the socket file that disappear,
akonadi should be resilient to this error, and not crash as it do.
The crash can be reproduced every time.
Possible duplicates by query: bug 415991, bug 415962, bug 415956, bug 415930,
bug 415815.
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 415956] Akonadi 19.12.x crash when socket file for connection to postgresql database disappear
https://bugs.kde.org/show_bug.cgi?id=415956 --- Comment #3 from Bruno Friedmann --- Created attachment 124997 --> https://bugs.kde.org/attachment.cgi?id=124997&action=edit Related backtrace Related backtrace -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416306] New: send later agent wrongly store sended message to local storage
https://bugs.kde.org/show_bug.cgi?id=416306 Bug ID: 416306 Summary: send later agent wrongly store sended message to local storage Product: kmail2 Version: 5.13.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- SUMMARY When send later agent is used, the sended message in not stored on the sent folder of the account used. Instead you have a copy stored in the local folder. STEPS TO REPRODUCE 1. Have at least 2 different indentity, using different sender : for example one google and one your provider 2. Use google identity to start a new message sended to your second email use the send later (optionnal via google smtp service) and use 10minutes to one hour later option 3. Once the email is sended by kmail2 look at Sent folder on your google account, the message is not there. 4. Open local folder Sent you will find the wrongly stored message here. 5. Open local and sent google message header and you will see the same id for identity and Transport. Like for example in my case X-KMail-Identity: 948660293 X-KMail-Transport: 464288440 X-KMail-Identity-Name: BF Gmail X-KMail-Transport-Name: smtp.gmail.com Kmail2 has all the informations to store the sended message to the right folder (Sent of the Identity, in my case) Notice : this deviant behaviour has been seen this year if my memory is right. I didn't got this trouble before. Sorry for the quantic precision ;-) OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416306] send later agent wrongly store sended message to local storage
https://bugs.kde.org/show_bug.cgi?id=416306 --- Comment #1 from Bruno Friedmann --- Software used openSUSE Tumbleweed - 20200111 Linux 5.4.7-1-default x86_64 GNU/Linux nvidia: 440.44 Qt: 5.13.1 KDE Frameworks: 5.65.0 Plasma: 5.17.5 kmail2 5.13.1 (19.12.1) Akonadi on central postgresql11 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414528] kmail moving mail (delete, move, read) crash akonadi
https://bugs.kde.org/show_bug.cgi?id=414528 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414885] New: akonadi crash after reading a new mail
https://bugs.kde.org/show_bug.cgi?id=414885 Bug ID: 414885 Summary: akonadi crash after reading a new mail Product: Akonadi Version: 5.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: akonadiserver (5.12.3) Qt Version: 5.13.1 Frameworks Version: 5.64.0 Operating System: Linux 5.3.12-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: After having moved several mail to trash, junk and read others in multiple folders, I've jump to the gmail imap account and read one mail and want to trash the second new. Here what I've found in system log akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search "searchUpdate-1575619077" done (without remote search) akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search update for collection "OpenInvitations" ( 457 ) finished: all results: 0 , removed results: 0 akonadiserver[3832]: org.kde.pim.akonadiserver.search: Executing search "searchUpdate-1575619077" akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search "searchUpdate-1575619077" done (without remote search) akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search update for collection "DeclinedInvitations" ( 458 ) finished: all results: 0 , removed results: 0 akonadiserver[3832]: org.kde.pim.akonadiserver.search: Executing search "searchUpdate-1575619077" akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search "searchUpdate-1575619077" done (without remote search) akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search update for collection "Last Search" ( 492 ) finished: all results: 0 , removed results: 0 akonadiserver[3832]: org.kde.pim.akonadiserver.search: Executing search "kmail2-48271-SearchSession" akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search "kmail2-48271-SearchSession" done (without remote search) kmail[24391]: QFont::setPixelSize: Pixel size <= 0 (0) akonadiserver[3832]: org.kde.pim.akonadiserver.search: Executing search "kmail2-48271-SearchSession" akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search "kmail2-48271-SearchSession" done (without remote search) akonadiserver[3832]: org.kde.pim.akonadiserver.search: Executing search "kmail2-48271-SearchSession" akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search "kmail2-48271-SearchSession" done (without remote search) kmail[24391]: qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 9570, resource id: 106954806, major code: 130 (Unknown), minor code: 3 kmail[24391]: qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 9590, resource id: 106954806, major code: 130 (Unknown), minor code: 3 kmail[24391]: qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 9593, resource id: 106954806, major code: 130 (Unknown), minor code: 3 akonadiserver[3832]: org.kde.pim.akonadiserver.search: Executing search "kmail2-48271-SearchSession" akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search "kmail2-48271-SearchSession" done (without remote search) akonadiserver[3832]: org.kde.pim.akonadiserver.search: Executing search "kmail2-48271-SearchSession" akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search "kmail2-48271-SearchSession" done (without remote search) akonadiserver[3832]: org.kde.pim.akonadiserver.search: Executing search "kmail2-48271-SearchSession" akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search "kmail2-48271-SearchSession" done (without remote search) akonadiserver[3832]: org.kde.pim.akonadiserver.search: Executing search "kmail2-48271-SearchSession" akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search "kmail2-48271-SearchSession" done (without remote search) akonadiserver[3832]: org.kde.pim.akonadiserver.search: Executing search "kmail2-48271-SearchSession" akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search "kmail2-48271-SearchSession" done (without remote search) akonadiserver[3832]: org.kde.pim.akonadiserver.search: Executing search "kmail2-48271-SearchSession" akonadiserver[3832]: org.kde.pim.akonadiserver.search: Search "kmail2-48271-SearchSession" done (without remote search) akonadiserver[3832]: QIODevice::write (QLocalSocket): device not open akonadiserver[3832]: Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must not let any exception whatsoever propagate through Qt code. If that is not possible, in Qt 5 you must at least reimplement QCoreApplication::notify() and catch all exceptions there. kdeinit5[1943]: Registering ":1.272/StatusNotifierIte
[Akonadi] [Bug 414885] akonadi crash after reading a new mail
https://bugs.kde.org/show_bug.cgi?id=414885 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 415741] New: Akonadi crash : event handler is not supported in Qt
https://bugs.kde.org/show_bug.cgi?id=415741 Bug ID: 415741 Summary: Akonadi crash : event handler is not supported in Qt Product: Akonadi Version: 5.13.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Created attachment 124806 --> https://bugs.kde.org/attachment.cgi?id=124806&action=edit Backtrace from drkonqi Application: akonadiserver (5.13.0 (19.12.0)) Qt Version: 5.13.1 Frameworks Version: 5.65.0 Operating System: Linux 5.3.12-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Sorting new email by delete, reading, moving them around, on the second action, the email stay in inbox folder and afterwards akonadi crash appear - Custom settings of the application: akonadi is using postgresql11 central (highly beefy) server kde is using breeze dark setting video is nvidia in xorg-session.log there those messages LOGIN CALLBACK in libCVP11LCB: CK_RV CB_Initialize(CK_CONTEXT_PTR, CK_C_INITIALIZE_ARGS_PTR, CK_ULONG_PTR) [Parent 20988, Gecko_IOThread] WARNING: pipe error (112): Connection reset by peer: file /home/abuild/rpmbuild/BUILD/firefox-70.0.1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358 ProtocolException thrown:ProtocolException thrown:ProtocolException thrown:ProtocolException thrown:ProtocolException thrown:ProtocolException thrown:Timeout while waiting for dataProtocolException thrown:Timeout while waiting for dataTimeout while waiting for dataProtocolException thrown:Timeout while waiting for data Timeout while waiting for data Timeout while waiting for data Timeout while waiting for data Timeout while waiting for data ProtocolException thrown:Timeout while waiting for data ProtocolException thrown:Failed to write data to stream terminate called after throwing an instance of 'Akonadi::ProtocolException' what(): Failed to write data to stream ProtocolException thrown:Timeout while waiting for data KCrash: Application 'akonadiserver' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit postgresql log : bf_akonadi bf_akonadi LOG: could not receive data from client: Connection reset by peer and in system log Dec 31 12:41:00 qt-kt akonadiserver[13775]: org.kde.pim.akonadiserver.search: Executing search "kmail2-48271-SearchSession" Dec 31 12:41:00 qt-kt akonadiserver[13775]: org.kde.pim.akonadiserver.search: Search "kmail2-48271-SearchSession" done (without remote search) Dec 31 12:41:02 qt-kt akonadiserver[13775]: QIODevice::write (QLocalSocket): device not open Dec 31 12:41:02 qt-kt akonadiserver[13775]: Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must not let any exception whatsoever propagate through Qt code. If that is not possible, in Qt 5 you must at least reimplement QCoreApplication::notify() and catch all exceptions there. The crash can be reproduced every time. See Attached backtrace The reporter indicates this bug may be a duplicate of or related to bug 414974, bug 414528. Possible duplicates by query: bug 415634, bug 415339, bug 415068, bug 414974, bug 414885. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 127321] Allow to use another database backends such as PostgreSQL through QtSQL plugin
https://bugs.kde.org/show_bug.cgi?id=127321 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #39 from Bruno Friedmann --- I'm also very much interested by this implemented. I've quite no clue about the level of difficulties that can be and the programing effort it can when you start from almost zero (IDE, git, kde account ok and being able to build the software ok) Otherwise never touch C++ nor Qt :-) Spending now much time on photography activity (will it be my main activity is still a mystery ;-). I will first check what I can obtain with foreign datawrapper and with pg_loader against a mariadb or sqlite digikam db and check schema. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 127321] Allow to use another database backends such as PostgreSQL through QtSQL plugin
https://bugs.kde.org/show_bug.cgi?id=127321 --- Comment #41 from Bruno Friedmann --- Hi Maïk, the SQL part should be for me the easy part, and I'm also in favor of having the right sql dialect (even if pg is the most closer to the norm) adapted for each engine. I have to also recheck the whole thread (like the proposal with foreign keys). Could you confirm to me that the sql code is located all at the same place in libs/database ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 127321] Allow to use another database backends such as PostgreSQL through QtSQL plugin
https://bugs.kde.org/show_bug.cgi?id=127321 --- Comment #43 from Bruno Friedmann --- Hi Gilles, thanks for the whole information. To get the job done, it seems to be a bit more complicated than I was thinking, and would be a perfect job during a Randa Meeting :-( So in the meantime I will get more familiarized with the program and its data model, and check with pgloader if I encounter big troubles. Also if remote can't actually handle concurrent access (which was one of my goal and desire) I will have certainly to wait for it. Hope to see you again soon somewhere irl! Take care and all good for 7x final release. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414528] New: kmail moving mail (delete, move, read) crash akonadi
https://bugs.kde.org/show_bug.cgi?id=414528 Bug ID: 414528 Summary: kmail moving mail (delete, move, read) crash akonadi Product: Akonadi Version: 5.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: akonadiserver (5.12.3) Qt Version: 5.13.1 Frameworks Version: 5.64.0 Operating System: Linux 5.3.11-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: reading mail quickly (with preview open on right), move some, delete other, then the waiting operation dialog box appear, and after some time 10 to 30 seconds late akonadi crash. This is reproductible (at least appear most of the time) since months. Use nvidia rpm openSUSE drivers G04. The crash can be reproduced sometimes. -- Backtrace (Reduced): #10 0x7f3c85fd8ea3 in qTerminate () at global/qglobal.cpp:3252 #11 0x7f3c85fda900 in QThreadPrivate::start (arg=0x56517ede6160) at thread/qthread_unix.cpp:372 [...] The reporter indicates this bug may be a duplicate of or related to bug 414436, bug 413664, bug 413291, bug 412439. Possible duplicates by query: bug 414454, bug 414436, bug 414388, bug 414137, bug 414102. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414528] kmail moving mail (delete, move, read) crash akonadi
https://bugs.kde.org/show_bug.cgi?id=414528 --- Comment #1 from Bruno Friedmann --- Created attachment 124124 --> https://bugs.kde.org/attachment.cgi?id=124124&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 391253] New: a baloo_file process continue to run when X session is stopped
https://bugs.kde.org/show_bug.cgi?id=391253 Bug ID: 391253 Summary: a baloo_file process continue to run when X session is stopped Product: frameworks-baloo Version: 5.43.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Created attachment 07 --> https://bugs.kde.org/attachment.cgi?id=07&action=edit baloo_file gdb trace with thread apply all bt I've detected that there's always a running baloo_file process belonging to my userid even if I've logout from Xorg, and no sessions are still running. We tried to fix it (see proposed patch) but there's still problems. Can we have some inputs from upstream ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 391253] a baloo_file process continue to run when X session is stopped
https://bugs.kde.org/show_bug.cgi?id=391253 --- Comment #1 from Bruno Friedmann --- Created attachment 08 --> https://bugs.kde.org/attachment.cgi?id=08&action=edit Patch helping in closing baloo_file -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 391253] a baloo_file process continue to run when X session is stopped
https://bugs.kde.org/show_bug.cgi?id=391253 --- Comment #2 from Bruno Friedmann --- Created attachment 09 --> https://bugs.kde.org/attachment.cgi?id=09&action=edit baloo_file lsof example Here the list of file open by baloo_file -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 391253] a baloo_file process continue to run when X session is stopped
https://bugs.kde.org/show_bug.cgi?id=391253 Bruno Friedmann changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #3 from Bruno Friedmann --- balooctl status Baloo File Indexer is running Indexer state: Idle Indexed 186431 / 186431 files Current size of index is 11,41 GiB balooctl indexSize Actual Size: 11,41 GiB Expected Size: 8,73 GiB PostingDB: 2,19 GiB 298.355 % PosistionDB: 3,50 GiB 477.935 % DocTerms: 1,66 GiB 226.418 % DocFilenameTerms: 17,77 MiB 2.366 % DocXattrTerms:0 B 0.000 % IdTree: 3,45 MiB 0.460 % IdFileName: 13,59 MiB 1.811 % DocTime: 8,30 MiB 1.106 % DocData: 20,01 MiB 2.666 % ContentIndexingDB:0 B 0.000 % FailedIdsDB:0 B 0.000 % MTimeDB: 3,84 MiB 0.512 % To be clear, if I issue the balooctl stop command the process die correctly. But that should be the case if I logout of plasma5. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 391253] a baloo_file process continue to run when X session is stopped
https://bugs.kde.org/show_bug.cgi?id=391253 --- Comment #5 from Bruno Friedmann --- Hi Michael, unfortunately the patch is not ok. the gdb attached is after applying it. And credits goes to Fabian. We can eventually work on phab, but I guess once we have a real and complete solution. If you find complementary code to fix, I can quite easily integrate it, build and test. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385770] openSUSE TW (+nvidia) kmail crash when searching To: contact
https://bugs.kde.org/show_bug.cgi?id=385770 Bruno Friedmann changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #3 from Bruno Friedmann --- Closed will be reopen if after resetting completely the setup it will be again produced -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 375461] New: akonadi_davgroupware_resource signal: Segmentation fault 16.12.0 during start up
https://bugs.kde.org/show_bug.cgi?id=375461 Bug ID: 375461 Summary: akonadi_davgroupware_resource signal: Segmentation fault 16.12.0 during start up Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- on openSUSE Tumbleweed 20170121 at startup akonadi_groupware agent crash Application: akonadi_davgroupware_resource (akonadi_davgroupware_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcb6ea54940 (LWP 3153))] Thread 5 (Thread 0x7fcb42ffd700 (LWP 3299)): #0 0x7fcb68ffc66d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcb615d6886 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcb615d699c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcb69b3318b in QEventDispatcherGlib::processEvents (this=0x7fcb380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fcb69adcaea in QEventLoop::exec (this=this@entry=0x7fcb42ffcc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fcb6990a813 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7fcb6990f4c8 in QThreadPrivate::start (arg=0xb59e30) at thread/qthread_unix.cpp:368 #7 0x7fcb63323454 in start_thread (arg=0x7fcb42ffd700) at pthread_create.c:333 #8 0x7fcb6900537f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7fcb437fe700 (LWP 3239)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67 #1 0x7fcb68ffc662 in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0x7fcb615d6886 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcb615d699c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fcb69b3318b in QEventDispatcherGlib::processEvents (this=0x7fcb340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fcb69adcaea in QEventLoop::exec (this=this@entry=0x7fcb437fdc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7fcb6990a813 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7fcb6990f4c8 in QThreadPrivate::start (arg=0xb48d80) at thread/qthread_unix.cpp:368 #8 0x7fcb63323454 in start_thread (arg=0x7fcb437fe700) at pthread_create.c:333 #9 0x7fcb6900537f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7fcb43fff700 (LWP 3235)): #0 0x7fcb68ffc66d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcb615d6886 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcb615d699c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcb69b3318b in QEventDispatcherGlib::processEvents (this=0x7fcb3c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fcb69adcaea in QEventLoop::exec (this=this@entry=0x7fcb43ffec50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fcb6990a813 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7fcb69f45385 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fcb6990f4c8 in QThreadPrivate::start (arg=0x7fcb6a1b6d20) at thread/qthread_unix.cpp:368 #8 0x7fcb63323454 in start_thread (arg=0x7fcb43fff700) at pthread_create.c:333 #9 0x7fcb6900537f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fcb4c3cb700 (LWP 3187)): #0 0x7fcb68ffc66d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcb637493e0 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fcb6374b179 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fcb4e2be889 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fcb6990f4c8 in QThreadPrivate::start (arg=0x742e90) at thread/qthread_unix.cpp:368 #5 0x7fcb63323454 in start_thread (arg=0x7fcb4c3cb700) at pthread_create.c:333 #6 0x7fcb6900537f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fcb6ea54940 (LWP 3153)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/6/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=) at /usr/include/qt5/QtCore/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=) at /usr/include/qt5/QtCore/qbasicatomic.h:99 #9 QtPrivate::RefCount::isShared (this=) at /usr/include/qt5/QtCore/qrefcount.h:101 #10 QMap::detach (this=0x10) at /usr/include/qt5/QtCore/qmap.h:366 #11 QMap::operator[] (akey=..., this=0x10) at /usr/include/qt5/QtCore/qmap.h:664 #12 EtagCache::setEtag (this=this@entry=0x0, remoteId=..., etag=...) at /usr/src/debug/kdepim-runtime-16.12.0/resources/dav/common/etagcache.cpp:38 #13 0x0046427f in DavGroupwareResource::onItemFetched (this=0xb4da10, job=, upd
[Akonadi] [Bug 375461] akonadi_davgroupware_resource signal: Segmentation fault 16.12.0 during start up
https://bugs.kde.org/show_bug.cgi?id=375461 Bruno Friedmann changed: What|Removed |Added Version|unspecified |5.4.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376113] New: After monitor suspend (dual monitor with one normal one hidpi) plasma5 crash
https://bugs.kde.org/show_bug.cgi?id=376113 Bug ID: 376113 Summary: After monitor suspend (dual monitor with one normal one hidpi) plasma5 crash Product: plasmashell Version: 5.9.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: br...@ioda-net.ch CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.0) Qt Version: 5.7.1 Frameworks Version: 5.30.0 Operating System: Linux 4.9.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I move my mouse to wake up both screen. Notice : It was working before 5.9.0 (even if at that time plasma was mixing which screen is primary or not) Since then, the screen returns 3 times to sleep and has been wake up without any plasma5 crash. I will see tomorrow if it appear the first time the sleep event occur. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe46033a8c0 (LWP 2576))] Thread 22 (Thread 0x7fe32d3fd700 (LWP 19813)): #0 0x7fe458fdb4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fe4361c9dc4 in () at /usr/lib64/libGLX_nvidia.so.0 #2 0x7fe3aefd5cd4 in () at /usr/lib64/libnvidia-glcore.so.378.09 #3 0x7fe4361c90ac in () at /usr/lib64/libGLX_nvidia.so.0 #4 0x7fe458fd5454 in start_thread (arg=0x7fe32d3fd700) at pthread_create.c:333 #5 0x7fe459a1b37f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 21 (Thread 0x7fe32dbfe700 (LWP 19812)): #0 0x7fe458fdb10f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe45a10f37b in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x5100180) at thread/qwaitcondition_unix.cpp:143 #2 0x7fe45a10f37b in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x513b310, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fe45ddfa2a5 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fe45ddfab9a in () at /usr/lib64/libQt5Quick.so.5 #5 0x7fe45a10e4c8 in QThreadPrivate::start(void*) (arg=0x513b290) at thread/qthread_unix.cpp:368 #6 0x7fe458fd5454 in start_thread (arg=0x7fe32dbfe700) at pthread_create.c:333 #7 0x7fe459a1b37f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 20 (Thread 0x7fe3412fc700 (LWP 16881)): #0 0x7fe458fdb4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fe4361c9dc4 in () at /usr/lib64/libGLX_nvidia.so.0 #2 0x7fe3aefd5cd4 in () at /usr/lib64/libnvidia-glcore.so.378.09 #3 0x7fe4361c90ac in () at /usr/lib64/libGLX_nvidia.so.0 #4 0x7fe458fd5454 in start_thread (arg=0x7fe3412fc700) at pthread_create.c:333 #5 0x7fe459a1b37f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 19 (Thread 0x7fe343fff700 (LWP 16880)): #0 0x7fe458fdb10f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe45a10f37b in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x328bfc0) at thread/qwaitcondition_unix.cpp:143 #2 0x7fe45a10f37b in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x2dad400, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fe45ddfa2a5 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fe45ddfab9a in () at /usr/lib64/libQt5Quick.so.5 #5 0x7fe45a10e4c8 in QThreadPrivate::start(void*) (arg=0x2dad380) at thread/qthread_unix.cpp:368 #6 0x7fe458fd5454 in start_thread (arg=0x7fe343fff700) at pthread_create.c:333 #7 0x7fe459a1b37f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 18 (Thread 0x7fe342ffd700 (LWP 4896)): #0 0x7fe458fdb4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fe4361c9dc4 in () at /usr/lib64/libGLX_nvidia.so.0 #2 0x7fe3aefd5cd4 in () at /usr/lib64/libnvidia-glcore.so.378.09 #3 0x7fe4361c90ac in () at /usr/lib64/libGLX_nvidia.so.0 #4 0x7fe458fd5454 in start_thread (arg=0x7fe342ffd700) at pthread_create.c:333 #5 0x7fe459a1b37f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 17 (Thread 0x7fe3437fe700 (LWP 4895)): #0 0x7fe458fdb10f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe45a10f37b in QWaitCondition::wait(QMutex*, unsigned long) (time=1844
[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]
https://bugs.kde.org/show_bug.cgi?id=339214 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #20 from Bruno Friedmann --- I've 12 imap account each setup to move deleted message to their own trash folder. Long ago, I was getting crash and background running kmail. To by pass this problem I've used the setting to not empty trash folder on exit, and after kmail never crashed again on exit. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch --- Comment #2 from Bruno Friedmann --- The test message is precisely located at https://lists.opensuse.org/opensuse-factory/2017-11/msg00487.html It's a 1.06MB text (or see the attachement here) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 400304] akonadi_imap_resource segmentation fault crash when idle on GMail account
https://bugs.kde.org/show_bug.cgi?id=400304 --- Comment #2 from Bruno Friedmann --- Also seen crash (not sure if 100% related) but exactly same circumstance. Gmail in idle, then I read a mail, try to delete and nothing happen except the crash. Application: akonadi_imap_resource (akonadi_imap_resource), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". __GI___libc_read (fd=5, buf=buf@entry=0x7fffa2069c70, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:27 [Current thread is 1 (Thread 0x7fe06d464a40 (LWP 2941))] Thread 8 (Thread 0x7fe060a12700 (LWP 1485)): #0 0x7fe07e3622c9 in __GI___poll (fds=0x7fe04c031f50, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe07bfe0fb6 in g_main_context_poll (priority=, n_fds=1, fds=0x7fe04c031f50, timeout=, context=0x7fe04c0a85d0) at gmain.c:4221 #2 0x7fe07bfe0fb6 in g_main_context_iterate (context=context@entry=0x7fe04c0a85d0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3915 #3 0x7fe07bfe10dc in g_main_context_iteration (context=0x7fe04c0a85d0, may_block=may_block@entry=1) at gmain.c:3981 #4 0x7fe07eaac88b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fe04c034000, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7fe07ea5702b in QEventLoop::exec(QFlags) (this=this@entry=0x7fe060a11b60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7fe07e8a13b6 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7fe07e8a2702 in QThreadPrivate::start(void*) (arg=0x55f61413dbf0) at thread/qthread_unix.cpp:361 #8 0x7fe07d56f554 in start_thread (arg=) at pthread_create.c:463 #9 0x7fe07e36cccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fe0525f6700 (LWP 992)): #0 0x7fe07e35dd34 in __GI___libc_read (fd=30, buf=buf@entry=0x7fe0525f5930, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fe07c026b20 in read (__nbytes=16, __buf=0x7fe0525f5930, __fd=) at /usr/include/bits/unistd.h:44 #2 0x7fe07c026b20 in g_wakeup_acknowledge (wakeup=0x7fe04800e280) at gwakeup.c:210 #3 0x7fe07bfe0abb in g_main_context_check (context=context@entry=0x7fe04002e5d0, max_priority=2147483647, fds=fds@entry=0x7fe040005b90, n_fds=n_fds@entry=1) at gmain.c:3698 #4 0x7fe07bfe0f60 in g_main_context_iterate (context=context@entry=0x7fe04002e5d0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3917 #5 0x7fe07bfe10dc in g_main_context_iteration (context=0x7fe04002e5d0, may_block=may_block@entry=1) at gmain.c:3981 #6 0x7fe07eaac88b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fe040005ed0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x7fe07ea5702b in QEventLoop::exec(QFlags) (this=this@entry=0x7fe0525f5b60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #8 0x7fe07e8a13b6 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #9 0x7fe07e8a2702 in QThreadPrivate::start(void*) (arg=0x55f6140eef70) at thread/qthread_unix.cpp:361 #10 0x7fe07d56f554 in start_thread (arg=) at pthread_create.c:463 #11 0x7fe07e36cccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fe053fff700 (LWP 3187)): #0 0x7fe07e367739 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fe07e8a4a24 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long long, int*, int) (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:105 #2 0x7fe07e8a4a24 in QtLinuxFutex::futexWait >(QBasicAtomicInteger&, QBasicAtomicInteger::Type) (expectedValue=, futex=...) at thread/qfutex_p.h:107 #3 0x7fe07e8a4a24 in futexSemaphoreTryAcquire_loop(QBasicAtomicInteger&, unsigned long long, unsigned long long, int) (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:219 #4 0x7fe07e8a4a24 in futexSemaphoreTryAcquire(QBasicAtomicInteger&, int, int) (timeout=-1, n=n@entry=1, u=...) at thread/qsemaphore.cpp:262 #5 0x7fe07e8a4a24 in QSemaphore::acquire(int) (this=this@entry=0x7fe07eec6440 <(anonymous namespace)::Q_QGS_libProxyWrapper::innerFunction()::holder+32>, n=n@entry=1) at thread/qsemaphore.cpp:326 #6 0x7fe07edfab84 in QLibProxyWrapper::run() (this=0x7fe07eec6420 <(anonymous namespace)::Q_QGS_libProxyWrapper::innerFunction()::holder>) at kernel/qnetworkproxy_libproxy.cpp:179 #7 0x7fe07e8a2702 in QThreadPrivate::start(void*) (arg=0x7fe07eec6420 <(anonymous namespace)::Q_QGS_libProxyWrapper::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #8 0x7fe07d56f554 in start_thread (arg=) at pthread_create.c:463 #9 0x7fe07e36cccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fe061213700 (LWP 3096)): #0 0x7fe07c027ea9 in g_m
[Akonadi] [Bug 400304] akonadi_imap_resource segmentation fault crash when idle on GMail account
https://bugs.kde.org/show_bug.cgi?id=400304 Bruno Friedmann changed: What|Removed |Added CC||lbeltr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 403710] New: baloo_file_Extractor crash at startup
https://bugs.kde.org/show_bug.cgi?id=403710 Bug ID: 403710 Summary: baloo_file_Extractor crash at startup Product: frameworks-baloo Version: 5.54.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: baloo_file_extractor (5.54.0) Qt Version: 5.12.0 Frameworks Version: 5.54.0 Operating System: Linux 4.20.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: the desktop was loading (autologin used here) at the same time plasma was finising it's statup (systray applet there) the crash debug was already there The crash can be reproduced sometimes. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe518cb3940 (LWP 2854))] Thread 2 (Thread 0x7fe50b249700 (LWP 2888)): #0 g_mutex_unlock (mutex=0x7fe504000bf0) at gthread-posix.c:1355 #1 0x7fe519c544a1 in g_main_context_prepare (context=context@entry=0x7fe504000bf0, priority=priority@entry=0x7fe50b248ae0) at gmain.c:3560 #2 0x7fe519c54eeb in g_main_context_iterate (context=context@entry=0x7fe504000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3900 #3 0x7fe519c550dc in g_main_context_iteration (context=0x7fe504000bf0, may_block=may_block@entry=1) at gmain.c:3981 #4 0x7fe51bc4188b in QEventDispatcherGlib::processEvents (this=0x7fe504000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7fe51bbec02b in QEventLoop::exec (this=this@entry=0x7fe50b248c30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7fe51ba363b6 in QThread::exec (this=this@entry=0x7fe51cc5dd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7fe51cbe3565 in QDBusConnectionManager::run (this=0x7fe51cc5dd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7fe51ba37702 in QThreadPrivate::start (arg=0x7fe51cc5dd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #9 0x7fe51aef6554 in start_thread (arg=) at pthread_create.c:463 #10 0x7fe51b51bccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fe518cb3940 (LWP 2854)): [KCrash Handler] #6 0x7fe50bcd3bba in KFileMetaData::TagLibExtractor::extract (this=, result=0x7ffdbe677d90) at /usr/src/debug/kfilemetadata5-5.54.0-1.1.x86_64/src/extractors/taglibextractor.cpp:857 #7 0x56055bea7e6b in Baloo::App::index (this=this@entry=0x7ffdbe678500, tr=0x56055d6195b0, url=..., id=id@entry=1433818997194801) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/file/extractor/app.cpp:191 #8 0x56055bea9d07 in Baloo::App::processNextFile (this=0x7ffdbe678500) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/file/extractor/app.cpp:111 #9 0x7fe51bc22ea6 in QtPrivate::QSlotObjectBase::call (a=0x7ffdbe677ee0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #10 QSingleShotTimer::timerEvent (this=0x56055d7f3a90) at kernel/qtimer.cpp:318 #11 0x7fe51bc1791b in QObject::event (this=0x56055d7f3a90, e=) at kernel/qobject.cpp:1230 #12 0x7fe51c5de591 in QApplicationPrivate::notify_helper (this=this@entry=0x56055d4d7b90, receiver=receiver@entry=0x56055d7f3a90, e=e@entry=0x7ffdbe678200) at kernel/qapplication.cpp:3753 #13 0x7fe51c5e5b50 in QApplication::notify (this=0x7ffdbe6784f0, receiver=0x56055d7f3a90, e=0x7ffdbe678200) at kernel/qapplication.cpp:3500 #14 0x7fe51bbed359 in QCoreApplication::notifyInternal2 (receiver=0x56055d7f3a90, event=0x7ffdbe678200) at ../../include/QtCore/5.12.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:322 #15 0x7fe51bc40c83 in QTimerInfoList::activateTimers (this=0x56055d58b700) at kernel/qtimerinfo_unix.cpp:643 #16 0x7fe51bc4150c in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #17 idleTimerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:229 #18 0x7fe519c54c85 in g_main_dispatch (context=0x7fe510004ff0) at gmain.c:3182 #19 g_main_context_dispatch (context=context@entry=0x7fe510004ff0) at gmain.c:3847 #20 0x7fe519c55048 in g_main_context_iterate (context=context@entry=0x7fe510004ff0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3920 #21 0x7fe519c550dc in g_main_context_iteration (context=0x7fe510004ff0, may_block=may_block@entry=1) at gmain.c:3981 #22 0x7fe51bc41873 in QEventDispatcherGlib::processEvents (this=0x56055d4b8d20
[frameworks-baloo] [Bug 403710] baloo_file_Extractor crash at startup
https://bugs.kde.org/show_bug.cgi?id=403710 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 403710] baloo_file_Extractor crash at startup
https://bugs.kde.org/show_bug.cgi?id=403710 --- Comment #1 from Bruno Friedmann --- Created attachment 117708 --> https://bugs.kde.org/attachment.cgi?id=117708&action=edit New crash information added by DrKonqi baloo_file_extractor (5.54.0) using Qt 5.12.0 Second reboot after last Tumbleweed snapshot 20190125 same crash This time also plamashell didn't finished its startup (no desktop wallpaper plugin running) -- Backtrace (Reduced): #6 0x7ff185acabba in KFileMetaData::TagLibExtractor::extract (this=, result=0x7ffecc9725a0) at /usr/src/debug/kfilemetadata5-5.54.0-1.1.x86_64/src/extractors/taglibextractor.cpp:857 #7 0x55cff6deae6b in Baloo::App::index (this=this@entry=0x7ffecc972d10, tr=0x55cff80d3940, url=..., id=id@entry=1433818997194801) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/file/extractor/app.cpp:191 #8 0x55cff6decd07 in Baloo::App::processNextFile (this=0x7ffecc972d10) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/file/extractor/app.cpp:111 #9 0x7ff195a18ea6 in QtPrivate::QSlotObjectBase::call (a=0x7ffecc9726f0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #10 QSingleShotTimer::timerEvent (this=0x55cff81e6bd0) at kernel/qtimer.cpp:318 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 403757] New: Changing mail signature script cause korganizer to crash (akonadi?)
https://bugs.kde.org/show_bug.cgi?id=403757 Bug ID: 403757 Summary: Changing mail signature script cause korganizer to crash (akonadi?) Product: korganizer Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: korganizer (5.10.1) Qt Version: 5.12.0 Frameworks Version: 5.54.0 Operating System: Linux 4.20.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was modifying one identities under kmail2 (changing the location of my signature script) once I click on apply, korganiser crashed immediately -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f984da01000 (LWP 7764))] Thread 5 (Thread 0x7f983bfff700 (LWP 7770)): #0 0x7f98548c92c9 in __GI___poll (fds=0x7f9834003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f98514bbfb6 in g_main_context_poll (priority=, n_fds=1, fds=0x7f9834003ce0, timeout=, context=0x7f9834000bf0) at gmain.c:4221 #2 g_main_context_iterate (context=context@entry=0x7f9834000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3915 #3 0x7f98514bc0dc in g_main_context_iteration (context=0x7f9834000bf0, may_block=may_block@entry=1) at gmain.c:3981 #4 0x7f985501388b in QEventDispatcherGlib::processEvents (this=0x7f9834000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f9854fbe02b in QEventLoop::exec (this=this@entry=0x7f983bffec60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f9854e083b6 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f9854e09702 in QThreadPrivate::start (arg=0x55da7ee304a0) at thread/qthread_unix.cpp:361 #8 0x7f98526f3554 in start_thread (arg=) at pthread_create.c:463 #9 0x7f98548d3ccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f98488ff700 (LWP 7767)): #0 0x7f98548c92c9 in __GI___poll (fds=0x7f9840006ba0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f98514bbfb6 in g_main_context_poll (priority=, n_fds=1, fds=0x7f9840006ba0, timeout=, context=0x7f984bf0) at gmain.c:4221 #2 g_main_context_iterate (context=context@entry=0x7f984bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3915 #3 0x7f98514bc0dc in g_main_context_iteration (context=0x7f984bf0, may_block=may_block@entry=1) at gmain.c:3981 #4 0x7f985501388b in QEventDispatcherGlib::processEvents (this=0x7f984b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f9854fbe02b in QEventLoop::exec (this=this@entry=0x7f98488fec60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f9854e083b6 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f9854e09702 in QThreadPrivate::start (arg=0x55da7ed6ed00) at thread/qthread_unix.cpp:361 #8 0x7f98526f3554 in start_thread (arg=) at pthread_create.c:463 #9 0x7f98548d3ccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f9849b10700 (LWP 7766)): #0 0x7f98548c92c9 in __GI___poll (fds=0x7f983c021c70, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f98514bbfb6 in g_main_context_poll (priority=, n_fds=1, fds=0x7f983c021c70, timeout=, context=0x7f983c000bf0) at gmain.c:4221 #2 g_main_context_iterate (context=context@entry=0x7f983c000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3915 #3 0x7f98514bc0dc in g_main_context_iteration (context=0x7f983c000bf0, may_block=may_block@entry=1) at gmain.c:3981 #4 0x7f985501388b in QEventDispatcherGlib::processEvents (this=0x7f983c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f9854fbe02b in QEventLoop::exec (this=this@entry=0x7f9849b0fc30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f9854e083b6 in QThread::exec (this=this@entry=0x7f98545b5d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f985453b565 in QDBusConnectionManager::run (this=0x7f98545b5d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f9854e09702 in QThreadPrivate::start (arg=0x7f98545b5d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #9 0x7f98526f3554
[kmail2] [Bug 403762] New: signature script failed and don't work anymore
https://bugs.kde.org/show_bug.cgi?id=403762
Bug ID: 403762
Summary: signature script failed and don't work anymore
Product: kmail2
Version: Git (master)
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: composer
Assignee: kdepim-b...@kde.org
Reporter: br...@ioda-net.ch
Target Milestone: ---
Use one of you account (for me Gmail) and in indentities define signature as
output of script.
Expected result the signature is applied to new message
Actual result : error dialog box (3 times) with
Failed to execute signature script
/ioda/home/bruno/bin/signature_email.sh:
Here the script
source /etc/os-release
cat /ioda/data/user-data/Bruno/Signatures/Standard.txt
echo ${PRETTY_NAME} - ${VERSION_ID}
echo "$(uname -srmo), nvidia: $(modinfo --field=version nvidia)"
X5="$( echo $(kf5-config -v) | awk '{print $1, $2",", $3, $4, $5}' )"
echo "${X5}, Plasma: $(plasmashell -v | awk '{print $2}'), $(kmail -v)"
and the output
Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch
Bareos Partner, openSUSE Member, fsfe supporter
GPG KEY : D5C9B751C4653227
irc: tigerfoot
openSUSE Tumbleweed - 20190125
Linux 4.20.2-1-default x86_64 GNU/Linux, nvidia: 410.93
Qt: 5.12.0, KDE Frameworks: 5.54.0, Plasma: 5.14.5, kmail2 5.10.1
echo $? return 0 as expected.
Don't remember when I saw this the first time (around 5.4x version I guess, one
year ago at least)
--
You are receiving this mail because:
You are watching all bug changes.
