[kontact] [Bug 440917] New: KMail freshly set up, immediate crash.
https://bugs.kde.org/show_bug.cgi?id=440917 Bug ID: 440917 Summary: KMail freshly set up, immediate crash. Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: br...@huisman.pl Target Milestone: --- Application: kontact (5.17.3 (21.04.3)) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.13.8-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I had just started Kontact for the first time, configured an email account, and after that some syncing seemed to take place and an immediate crash after that. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f29b0f2e040 (LWP 21063))] [KCrash Handler] #6 0x7f296622b2d2 in QExplicitlySharedDataPointer::operator! (this=) at /usr/include/qt5/QtCore/qshareddata.h:231 #7 KMKernel::config (this=0x55e7a0cf66d0) at /usr/src/debug/kmail-21.04.3-1.1.x86_64/src/kmkernel.cpp:1393 #8 0x7f2966064d70 in MailCommon::FolderSettings::writeConfig (this=0x55e7a0520e50) at /usr/src/debug/mailcommon-21.04.3-1.1.x86_64/src/folder/foldersettings.cpp:222 #9 0x7f29662539cb in KMMainWidget::writeFolderConfig (this=this@entry=0x55e7987bbd20) at /usr/src/debug/kmail-21.04.3-1.1.x86_64/src/kmmainwidget.cpp:606 #10 0x7f2966257040 in KMMainWidget::folderSelected (this=0x55e7987bbd20, col=...) at /usr/src/debug/kmail-21.04.3-1.1.x86_64/src/kmmainwidget.cpp:518 #11 0x7f29662572b0 in KMMainWidget::slotFolderChanged (this=0x55e7987bbd20, collection=...) at /usr/src/debug/kmail-21.04.3-1.1.x86_64/src/kmmainwidget.cpp:470 #12 0x7f29c3740fb3 in QtPrivate::QSlotObjectBase::call (a=0x7ffe160c9b50, r=0x55e7987bbd20, this=0x55e7984d8e70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x55e79849ff60, signal_index=20, argv=0x7ffe160c9b50) at kernel/qobject.cpp:3886 #14 0x7f29c373a47f in QMetaObject::activate (sender=, m=m@entry=0x7f296c50bea0 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7ffe160c9b50) at kernel/qobject.cpp:3946 #15 0x7f296c4ad625 in Akonadi::EntityTreeView::currentChanged (this=, _t1=...) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/build/src/widgets/KF5AkonadiWidgets_autogen/include/moc_entitytreeview.cpp:218 #16 0x7f296c4b10ab in Akonadi::EntityTreeView::Private::itemCurrentChanged (index=..., this=0x55e79852e8d0) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/widgets/entitytreeview.cpp:165 #17 operator() (index=..., __closure=) at /usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/widgets/entitytreeview.cpp:207 #18 QtPrivate::FunctorCall, QtPrivate::List, void, Akonadi::EntityTreeView::setModel(QAbstractItemModel*):: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #19 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #20 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl (which=, r=, ret=, a=, this_=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #21 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:436 #22 0x7f29c3740fb3 in QtPrivate::QSlotObjectBase::call (a=0x7ffe160c9cc0, r=0x55e79849ff60, this=0x55e798663cd0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #23 doActivate (sender=0x55e798664140, signal_index=4, argv=0x7ffe160c9cc0) at kernel/qobject.cpp:3886 #24 0x7f29c373a47f in QMetaObject::activate (sender=sender@entry=0x55e798664140, m=m@entry=0x7f29c39d9080 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffe160c9cc0) at kernel/qobject.cpp:3946 #25 0x7f29c36b52b3 in QItemSelectionModel::currentChanged (this=this@entry=0x55e798664140, _t1=..., _t2=...) at .moc/moc_qitemselectionmodel.cpp:482 #26 0x7f29c36b8c99 in QItemSelectionModel::setCurrentIndex (this=0x55e798664140, index=..., command=...) at itemmodels/qitemselectionmodel.cpp:1416 #27 0x7f29c4526703 in QAbstractItemView::mousePressEvent (this=0x55e79849ff60, event=) at itemviews/qabstractitemview.cpp:1786 #28 0x7f29c42f571e in QWidget::event (this=this@entry=0x55e79849ff60, event=event@entry=0x7ffe160ca370) at kernel/qwidget.cpp:9020 #29 0x7f29c43a1dfe in QFrame::event (this=0x55e79849ff60, e=0x7ffe160ca370) at widgets/qframe.cpp:550 #30 0x7f29c370a6d2 in QCoreApplicationPrivate::sendThroughObjectEventFilters (event=, receiver=)
[akregator] [Bug 416983] OPML extension mistranslated? Extra comma appended.
https://bugs.kde.org/show_bug.cgi?id=416983 --- Comment #3 from Brent --- Thanks mate! -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 416983] New: OPML extension mistranslated? Extra comma appended.
https://bugs.kde.org/show_bug.cgi?id=416983 Bug ID: 416983 Summary: OPML extension mistranslated? Extra comma appended. Product: akregator Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@brenthuisman.net Target Milestone: --- Created attachment 125568 --> https://bugs.kde.org/attachment.cgi?id=125568=edit Print screen showing the extension is mistranslated. SUMMARY Upon import of feeds, the filedialog doesn't show OPML files. Upon export the extensions `opml,` is added. Note the extra comma. I've added a screenshot of the save dialog that demonstrating `.opnl,` is automatically added. SOFTWARE/OS VERSIONS Updated KDE Neon User. ADDITIONAL INFORMATION In the source code I see no typo that explains this: https://phabricator.kde.org/source/akregator/browse/master/src/akregator_part.cpp:602 https://phabricator.kde.org/source/akregator/browse/master/src/akregator_part.cpp:611 The only thing I can imagine is that the translation function `i18n()` adds the extra comma. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411591] New: Different defaults for reply and forward modes
https://bugs.kde.org/show_bug.cgi?id=411591 Bug ID: 411591 Summary: Different defaults for reply and forward modes Product: kmail2 Version: 5.12.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: m...@brenthuisman.net Target Milestone: --- Under the Reply and Forward buttons on the toolbar there are a few ways to do it. You need to hold-click to activate one of those alternative modes. Would it be possible to change the default mode, activated by single clicking? For instance, I'd like to have the reply-to-all mode to be the default, as well as forward-inline. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409736] After upgrade to Applications 19.04.3: Akonadi can't connect to local MySQL server any more
https://bugs.kde.org/show_bug.cgi?id=409736 --- Comment #5 from Brent --- I think updates were just released that fix it. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409736] After upgrade to Applications 19.04.3: Akonadi can't connect to local MySQL server any more
https://bugs.kde.org/show_bug.cgi?id=409736 --- Comment #2 from Brent --- Perhaps I should have added that I tried to fixes permissions for /var/lib/mysql (if you run /usr/bin/akonadiserver you'll get an error about that), to remove ~/.local/share/akonadi, but nothing helped or led to more info (to me). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409736] After upgrade to Applications 19.04.3: Akonadi can't connect to local MySQL server any more
https://bugs.kde.org/show_bug.cgi?id=409736 Brent changed: What|Removed |Added CC||m...@brenthuisman.net --- Comment #1 from Brent --- Same here, on two similarly configured machines all PIM applications were rendered unusable. Stopgap solution that worked for me: install akonadi-backend-sqlite and then remove akonadi-backend-mysql. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 407365] New: Viewing IMAP folder: fine in KMail, freeze in Kontact
https://bugs.kde.org/show_bug.cgi?id=407365 Bug ID: 407365 Summary: Viewing IMAP folder: fine in KMail, freeze in Kontact Product: kontact Version: 5.11.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: m...@brenthuisman.net Target Milestone: --- SUMMARY Since either since last update to Kmail (yesterday I pulled in the 5.15.5 update) or since moving an email into the folder, I am experiencing a consistent freeze of the Kontact application upon attempting to view the contents of an email folder. The Kontact gui freezes, and corrupts when minimizing/maximizing/etc. Viewing the folder in Kmail works perfectly fine however. Running Kontact from the commandline does not produce any (helpful) output, so I'm at a loss. The folder is a custom folder on an IMAP server. STEPS TO REPRODUCE 1. Start Kontact 2. Visit one particular folder. OBSERVED RESULT 1. Gui freeze EXPECTED RESULT No freeze. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57 Qt Version: 5.12 ADDITIONAL INFORMATION None at this time. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 406840] Crash report
https://bugs.kde.org/show_bug.cgi?id=406840 --- Comment #1 from Brent --- Created attachment 119622 --> https://bugs.kde.org/attachment.cgi?id=119622=edit Second crash Small update: it happened again. Attached another log. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 406840] New: Crash report
https://bugs.kde.org/show_bug.cgi?id=406840 Bug ID: 406840 Summary: Crash report Product: kontact Version: 5.11.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@brenthuisman.net Target Milestone: --- Created attachment 119603 --> https://bugs.kde.org/attachment.cgi?id=119603=edit Crash log SUMMARY Occasionally, upon starting Kontact, where I have mail, card-/caldav and feeds configured, it crashes immediately. Relaunching works fine. There is not specific reason that I can identify, so I thought I'd submit the crashlog. About that: the error report form offers to install debug symbols, which I did, but even after reloading (and reclicking install debug symbols) the 'report bug' button remains greyed out. So I submit it here in case it's usefull (there's a two star rating on the 'bugreport usability'). STEPS TO REPRODUCE 1. Start Kontact OBSERVED RESULT Crash. The report does not specify causes. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.11.4 KDE Frameworks Version: 5.57 Qt Version: 5.12 ADDITIONAL INFORMATION See attached crashl og. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388036] Include support for autocrypt
https://bugs.kde.org/show_bug.cgi?id=388036 Brent changed: What|Removed |Added CC||m...@brenthuisman.net --- Comment #4 from Brent --- +1! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 Brent changed: What|Removed |Added CC||brenthuis...@gmail.com --- Comment #40 from Brent --- +1 for removing HTML-view feedback (aka the bar, vignet). I think users understand their own preferences without it. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 295563] Kleopatra Certification error in windows for one of the user
https://bugs.kde.org/show_bug.cgi?id=295563 Brent breff...@sourcelink.com changed: What|Removed |Added CC||breff...@sourcelink.com --- Comment #1 from Brent breff...@sourcelink.com --- I too had a problem while importing a secret key. It did not successfully import the public portion. I cannot delete the key and re-importing does not fix the issue. Upon delete I get the error message: OpenPGP backend: No public key On another computer, the secret key imports successfully and allows me to remove. In addition, other keys on the problem computer can be deleted. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
