[korganizer] [Bug 453121] Flatpak calender can't connect to nextcloud
https://bugs.kde.org/show_bug.cgi?id=453121 gjditchfi...@acm.org changed: What|Removed |Added Summary|Kontact calender can't |Flatpak calender can't |connect to nextcloud|connect to nextcloud -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452631] Non-Gregorian Calendars
https://bugs.kde.org/show_bug.cgi?id=452631 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org Summary|Calendar|Non-Gregorian Calendars -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 453344] Some recurring meetings on CalDAV do not show up
https://bugs.kde.org/show_bug.cgi?id=453344 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from gjditchfi...@acm.org --- (In reply to Syiad from comment #2) > Here is one such meeting, which I have accepted via Thunderbird, because the > invite e-mail was not properly rendered in KMail (probably a separate new > bug). That is probably bug 452480, which will be fixed in the next release (or earlier if your packager picks up the patch). > ATTENDEE;CN='Syiad T. Al-Duri';RSVP=TRUE;PARTSTAT=NEEDS-ACTION; > ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;X-UID=94871628180400:mailto: > syiad.al-d...@some.com I believe this is the problem. Akonadi does not know you accepted the invitation, so it is still marked "NEEDS-ACTION", and KOrganizer currently doesn't display events unless it knows they have been accepted -- a known bug. *** This bug has been marked as a duplicate of bug 436812 *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 436812] Event not shown in KOrganizer, when the user is attendee and invitation needs action
https://bugs.kde.org/show_bug.cgi?id=436812 gjditchfi...@acm.org changed: What|Removed |Added CC||syiad.al-d...@web.de --- Comment #10 from gjditchfi...@acm.org --- *** Bug 453344 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 453367] Can't start KMail, KContacts, KOrganizer or any app from that suite.
https://bugs.kde.org/show_bug.cgi?id=453367 Mattias Högfjäll changed: What|Removed |Added Resolution|UPSTREAM|FIXED --- Comment #3 from Mattias Högfjäll --- Hi, I got all the K-apps working now. I uninstalled a whole lot of Gnome-stuff and reinstalled the K-Suite. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 418811] Events stored in the database not displayed in KOrganizer
https://bugs.kde.org/show_bug.cgi?id=418811 Tobias Klaus changed: What|Removed |Added CC||ek+...@meskal.net --- Comment #10 from Tobias Klaus --- This still happens with kdepim-22.04.0 (gentoo/qt-5.15.3/plasma-5.24.4//kde-framework-5.93) This is a major blocker for usage of kde-pim with ews, as most of my companies events are not displayed. Can someone give me a hint, where one could look for the code that is responsible for filtering? As this bug can also be observed when using Kalendar, I suppose it is within akonadi itself? -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 451733] Can't import directory with vcard files
https://bugs.kde.org/show_bug.cgi?id=451733 --- Comment #3 from Juha Tuomala --- Ha, now it works. So, I run this console (/usr/bin/akonadiconsole) GUI and there are - Agents - Browser tab and others. In Agents, choose the right Contacts resource, RMB-click it -> Configure Remotely. There is Path setting. I had it empty, even it was set if I open the Configure Natively. I put the same directory there. In Browser tab, Contacts numbers are still 0. I RMB-click the Contacts, choose Synchronize and in shell where I'm running Akonadi, stuff starts to happen. I takes a bit since I've over 1k contacts. Then the kaddressbook is still empty. I tickled it a bit but no luck. Chose File -> Quit, started it again and yes, all my contacts where there again. Happy days. When the problem was still on, in empty addressbook I created a new entry. It appeared into list, I could even see it in console. One single vcard. But it was not in my vcard directory. It even survived if I restarted everything. No idea where it saved it but it was/is somewhere. That lead me to think that path is incorrect and even it was in "native" interface and setting, it was not in "remote" - whatever those are, go figure. Anyway. I don't know what broke it. It sure was not me. I hope I wont waste hours with this again. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 275261] Akonadi on NFS mounted home directories is very fragile
https://bugs.kde.org/show_bug.cgi?id=275261 Juha Tuomala changed: What|Removed |Added CC||t...@iki.fi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 453383] New: Reply mails are shown in wrong thread after being moved to a different folder (in Kontact)
https://bugs.kde.org/show_bug.cgi?id=453383 Bug ID: 453383 Summary: Reply mails are shown in wrong thread after being moved to a different folder (in Kontact) Product: kmail2 Version: 5.20.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: dev-...@felsenfleischer.de Target Milestone: --- Created attachment 148558 --> https://bugs.kde.org/attachment.cgi?id=148558=edit Comparison of inbox view between Kontact and Kmail I’ve been observing this issue now for a very long time now. I thought something this obvious must be noticed easily. But it seems I hit a niche and it just happened again, so I finally decided to report it. STEPS TO REPRODUCE I just sent replies to two different mail threads in an IMAP account. KMail stored the replies in the Sent folder, as usual. I went to the folder, selected both mails and moved them to the Inbox folder, so they may be shown within their respective threads. OBSERVED RESULT The mails were shown in the wrong thread: replay to thread A is shown in thread B and vice versa. EXPECTED RESULT The mails should appear as reply to the correct mail. Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.5-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 ADDITIONAL INFORMATION One very interesting bit of info that I found out just now: the issue only appears in Kontakt. I closed Kontact and opened KMail as standalone application, and in there the threads were correct. Then I closed KMail and reopened Kontact, and the mails were mixed up again. I did this twice, both times with the same result. So perhaps this is a Kontact thing, or an Akonadi bug? I haven’t tested yet what happens if I move mail in standalone-KMail, so whether the (akonadi?) data is garbled during the move or during display. I also looked at the mail source to make sure the In-Reply-To header was correct. But I already knew it was so, because when I sync the account with offlineimap and view it in mutt, the thread is also correct. I have akonadiconsole installed, so I am happy to provide deeper info if required. While preparing the screenshots, I also noticed that the structure of the lower thread is different between the two programs (see circles in the image). Apparently there has been a similar hickup in the thread before. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 451733] Can't import directory with vcard files
https://bugs.kde.org/show_bug.cgi?id=451733 Juha Tuomala changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 451733] Can't import directory with vcard files
https://bugs.kde.org/show_bug.cgi?id=451733 --- Comment #2 from Juha Tuomala --- My system is Fedora: # cat /etc/system-release Fedora release 35 (Thirty Five) # rpm -qa|grep akonadi kf5-akonadi-notes-21.12.2-1.fc35.x86_64 kf5-akonadi-server-mysql-21.12.2-1.fc35.x86_64 kf5-akonadi-server-21.12.2-1.fc35.x86_64 kf5-akonadi-mime-21.12.2-1.fc35.x86_64 kf5-akonadi-contacts-21.12.2-1.fc35.x86_64 kf5-akonadi-search-21.12.2-1.fc35.x86_64 kf5-pimcommon-akonadi-21.12.2-1.fc35.x86_64 kf5-mailimporter-akonadi-21.12.2-1.fc35.x86_64 kf5-kmailtransport-akonadi-21.12.2-1.fc35.x86_64 kf5-akonadi-calendar-21.12.2-1.fc35.x86_64 akonadi-import-wizard-21.12.2-1.fc35.x86_64 akonadi-calendar-tools-21.12.2-1.fc35.x86_64 akonadiconsole-21.12.2-1.fc35.x86_64 Hmm should I have kf5-akonadi-server-pgsql-21.12.2-1.fc35.x86_64 installed - which is not available? My system is configured to Postgresql more or less like this https://jpmrblood.github.io/notes/akonadi-postgresql/ -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 453367] Can't start KMail, KContacts, KOrganizer or any app from that suite.
https://bugs.kde.org/show_bug.cgi?id=453367 Mattias Högfjäll changed: What|Removed |Added CC||mattias.hogfj...@outlook.co ||m Platform|Ubuntu Packages |Kubuntu Packages Version|unspecified |5.19.3 -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 451733] Can't import directory with vcard files
https://bugs.kde.org/show_bug.cgi?id=451733 Juha Tuomala changed: What|Removed |Added CC||t...@iki.fi --- Comment #1 from Juha Tuomala --- I confirm this. Some recent update broke it. I'm using pgsql backend, but most likely it's not the cause, but VCARD type resource which is Directory of VCARD files. While running akonadi daemon at console and looking at those vcard entries in akonadiconsole GUI-tool, tab "Item Search", I get this error into daemon stdout/err: org.kde.pim.akonadiserver: Handler exception when handling command FetchItems on connection akonadiconsole-2719277638 (0x55fd557d1fc0) : Item query returned empty result set and GUI says: "Error on fetching item". GUI however has those lower Results (Documents) set full of six digit numbers. Maybe they are from cache, can't say. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 --- Comment #14 from Till Schäfer --- Created attachment 148553 --> https://bugs.kde.org/attachment.cgi?id=148553=edit screenshot of hamburger menu in notifications (In reply to Volker Krause from comment #13) > We cannot have the same level of detail for the suspend time UI as the old > dialog had, system notifications are much more restricted in that regard. > However, there is certainly room to improve the current system. > > The 5 minute interval makes sense for events at a fixed time in say the next > hour or so (eg. meetings or calls) I think. For events in the more distant > future, all day events, todos (or events used to represent tasks) we can > probably find better defaults. Something proportional to the distance to the > event would seem like it would address at least some of the problems? That does not really fit my use cases (see also Bug 453298). For example, the duration of a phone call or meeting does not depend on distance of the event. What would make more sense to me is a constant distance before the event. But also in this case a single duration would most probably be not enough to be useful in the majority of use cases. Some Ideas here (I am not very familiar with the implementation specific limitations, so please say if they are not worthwhile to consider). A) Is it possible to have a drop down button that let you select a list of default snooze times? Having just multiple intervals with good (maybe configurable defaults) would make more sense to me, if a custom input is not possible. For example: 5 Minutes, 30 Minutes, 1 Hour, 2 Hours, 5 Hours, 1 Day, 1 Hour before the even, 30 minutes before the event start, 5 minuted before the event, when the event starts. B) When copying a file, there is a hamburger menu in the notification area, where i get full access to file operations about the copied file (see screenshot). If a direct drop down button is not possible for the snooze button (see A), it maybe possible to give advanced options in such an hamburger menu. I think such a drop down menu would also make sense for things like a direct editing of events (see Bug ). C) maybe it is possible to open another message box that asks about a custom delay if such an option is available (e.g., through A or B) D) Is it possible to display more complex widgets than a simple line based menu for the hamburger? -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 453367] Can't start KMail, KContacts, KOrganizer or any app from that suite.
https://bugs.kde.org/show_bug.cgi?id=453367 --- Comment #2 from Mattias Högfjäll --- The style, if you mean Kvantum, is one I made my self but if I remember correctly, is for the most part, bits from Breeze Air. I get an error saying that Akonadis Service and is “not operational”. The instructions are to get more information by pressing the detail button but nothing happens. I haven’t had time to look into this yet. Is there some further information I can gather for you I’d be happy to help. I’ve been using this style a couple of months without any issue. To me, ad a none developer, and a total layman, I would have guessed that Akonadi’s issue is not with Kvantum but something else. Everything around that K-suite of programs seems completely dead. Dead. Like it’s only half installed. To be fair, my installation is quite messy. I have installed A BUNCH of apps from all distros trying out all the window decorators and compositors so there’s an epic battle for supremacy on every boot. The plan was to do a fresh install of Kubuntu with 22.04 but I happened to stumble on the “upgrade” command so I thought I’d give it a go first. But as I said. If there’s any further information I can give, or tests I can run, I’d be happy to oblige. Kind regards, Mattias -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 453376] New: KMail crash
https://bugs.kde.org/show_bug.cgi?id=453376 Bug ID: 453376 Summary: KMail crash Product: kmail2 Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sima...@gmail.com Target Milestone: --- Application: kmail (5.20.0 (22.04.0)) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.13.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Just checking mail and reading messages. When I have deleted a messahe, KMail closed. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted [New LWP 3975] [New LWP 3976] [New LWP 3977] [New LWP 3978] [New LWP 3979] [New LWP 3980] [New LWP 3981] [New LWP 4031] [New LWP 4033] [New LWP 4039] [New LWP 4040] [New LWP 4041] [New LWP 4042] [New LWP 4045] [New LWP 4046] [New LWP 4047] [New LWP 4053] [New LWP 4068] [New LWP 4083] [New LWP 4090] [New LWP 4176] [New LWP 4318] [New LWP 4319] [New LWP 4320] [New LWP 4321] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fcea570f9cf in __GI___poll (fds=0x7ffddbc0c778, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7fce965f9200 (LWP 3973))] Thread 26 (Thread 0x7fcdf39ff700 (LWP 4321)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fcdf39fe310, clockid=, expected=0, futex_word=0x5557cb7503f4) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fcdf39fe310, clockid=, mutex=0x5557cb7503a0, cond=0x5557cb7503c8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x5557cb7503c8, mutex=0x5557cb7503a0, abstime=0x7fcdf39fe310) at pthread_cond_wait.c:656 #3 0x7fcea5ac2618 in QWaitConditionPrivate::wait_relative (this=0x5557cb7503a0, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x5557cb7503a0) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x5557cb74b580, mutex=mutex@entry=0x5557cb7aec98, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7fcea5abfb21 in QThreadPoolThread::run (this=0x5557cb74b570) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7fcea5abc623 in QThreadPrivate::start (arg=0x5557cb74b570) at thread/qthread_unix.cpp:331 #8 0x7fcea2483609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fcea571c163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7fce12ffd700 (LWP 4320)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fce12ffc310, clockid=, expected=0, futex_word=0x5557cb7f8ea4) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fce12ffc310, clockid=, mutex=0x5557cb7f8e50, cond=0x5557cb7f8e78) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x5557cb7f8e78, mutex=0x5557cb7f8e50, abstime=0x7fce12ffc310) at pthread_cond_wait.c:656 #3 0x7fcea5ac2618 in QWaitConditionPrivate::wait_relative (this=0x5557cb7f8e50, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x5557cb7f8e50) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x5557cb8e2b20, mutex=mutex@entry=0x5557cb7aec98, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7fcea5abfb21 in QThreadPoolThread::run (this=0x5557cb8e2b10) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7fcea5abc623 in QThreadPrivate::start (arg=0x5557cb8e2b10) at thread/qthread_unix.cpp:331 #8 0x7fcea2483609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fcea571c163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fce11ffb700 (LWP 4319)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fce11ffa310, clockid=, expected=0, futex_word=0x5557cb7f9114) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fce11ffa310, clockid=, mutex=0x5557cb7f90c0, cond=0x5557cb7f90e8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x5557cb7f90e8, mutex=0x5557cb7f90c0, abstime=0x7fce11ffa310) at pthread_cond_wait.c:656 #3 0x7fcea5ac2618 in QWaitConditionPrivate::wait_relative (this=0x5557cb7f90c0, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x5557cb7f90c0) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x5557cb7a3cc0, mutex=mutex@entry=0x5557cb7aec98, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7fcea5abfb21 in
[kmail2] [Bug 412402] Kmail crashes when enabling/disabling favourites folders in kmail settings
https://bugs.kde.org/show_bug.cgi?id=412402
Rolf Eike Beer changed:
What|Removed |Added
CC||k...@opensource.sf-tec.de
--- Comment #1 from Rolf Eike Beer ---
I think I hit the same using openSUSE Tumbleweed 5.20.0 RPMs:
Application: Kontact (kontact), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 std::__atomic_base::load(std::memory_order) const
(__m=std::memory_order_relaxed, this=Python Exception : Cannot access memory at address 0x121
#7 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=Python
Exception : Cannot access memory at address 0x121
#8 QBasicAtomicInteger::loadRelaxed() const (this=Python Exception : Cannot access memory at address 0x121
#9 QtPrivate::RefCount::isShared() const (this=Python Exception : Cannot access memory at address 0x121
#10 QList::append(QWidget* const&) (this=0x121, t=@0x7ffc08be9ec0:
0x55c519bd6dc0) at ../../include/QtCore/../../src/corelib/tools/qlist.h:622
#11 0x7f1c30fab379 in QWidget::insertAction(QAction*, QAction*)
(this=this@entry=0x55c519bd6dc0, before=, before@entry=0x0,
action=0x55c519d37760) at kernel/qwidget.cpp:3129
#12 0x7f1c31731433 in KXMLGUI::ActionList::plug(QWidget*, int) const
(index=, container=0x55c519bd6dc0, this=0x55c51999abd0) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguifactory_p.cpp:33
#13 KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&,
QTypedArrayData::iterator const&)
(mergingIdxIt=..., state=..., this=0x55c51a1a73e0) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguifactory_p.cpp:230
#14 KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&)
(this=0x55c51a1a73e0, state=...) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguifactory_p.cpp:202
#15 0x7f1c317314f0 in
KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&)
(this=0x55c519ce1580, state=...) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguifactory_p.cpp:206
#16 0x7f1c317314f0 in
KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&)
(this=0x55c519cdca80, state=...) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguifactory_p.cpp:206
#17 0x7f1c31737c81 in KXMLGUIFactory::plugActionList(KXMLGUIClient*,
QString const&, QList const&) (this=0x55c519cb0c50,
client=0x55c519dec1d0, name=, actionList=...) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguifactory.cpp:564
#18 0x7f1bad606c58 in
PimCommon::PluginInterface::initializePluginActions(QString const&,
KXMLGUIClient*) (this=, prefix=..., guiClient=0x55c519dec1d0) at
/usr/src/debug/pimcommon-22.04.0-1.1.x86_64/src/pimcommonakonadi/genericplugins/plugininterface.cpp:152
#19 0x7f1bae396900 in KMMainWidget::initializePluginActions()
(this=0x55c519de8df0) at
/usr/src/debug/kmail-22.04.0-1.1.x86_64/src/kmmainwidget.cpp:4173
#20 0x7f1bae497a65 in
KMailPart::guiActivateEvent(KParts::GUIActivateEvent*) (this=0x55c519dec1a0,
e=) at
/usr/src/debug/kmail-22.04.0-1.1.x86_64/src/kmail_part.cpp:114
#21 0x7f1c303ee1af in QObject::event(QEvent*) (this=0x55c519dec1a0,
e=0x7ffc08bea440) at kernel/qobject.cpp:1336
#22 0x7f1c30f72b0f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55c519dec1a0, e=0x7ffc08bea440) at
kernel/qapplication.cpp:3632
#23 0x7f1c303c1b5a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55c519dec1a0, event=0x7ffc08bea440) at
kernel/qcoreapplication.cpp:1064
#24 0x7f1c2fafbc3f in KParts::MainWindow::createGUI(KParts::Part*) () at
/lib64/libKF5Parts.so.5
#25 0x7f1c317bc7ca in
Kontact::MainWindow::selectPlugin(KontactInterface::Plugin*)
(this=0x55c51995ffa0, plugin=) at
/usr/src/debug/kontact-22.04.0-1.1.x86_64/src/mainwindow.cpp:618
#26 0x7f1c303f8488 in doActivate(QObject*, int, void**)
(sender=0x55c519995820, signal_index=7, argv=0x7ffc08bea680) at
kernel/qobject.cpp:3898
#27 0x7f1c303f17af in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7f1c317de560
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc08bea680)
at kernel/qobject.cpp:3946
#28 0x7f1c317b73df in
Kontact::SidePaneBase::pluginSelected(KontactInterface::Plugin*)
(this=, _t1=) at
/usr/src/debug/kontact-22.04.0-1.1.x86_64/build/src/kontactprivate_autogen/EWIEGA46WW/moc_sidepanebase.cpp:141
#29 0x7f1c303f8453 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffc08bea7b0, r=0x55c519995820, this=0x55c519f0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#30 doActivate(QObject*, int, void**) (sender=0x55c51996dc40,
signal_index=15, argv=0x7ffc08bea7b0) at kernel/qobject.cpp:3886
#31 0x7f1c303f17af in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x55c51996dc40, m=,
local_signal_index=local_signal_index@entry=0,
[akregator] [Bug 449214] Akregator crashed when opening a news feed on a new tab
https://bugs.kde.org/show_bug.cgi?id=449214 Don Curtis changed: What|Removed |Added CC||bugrprt21...@online.de -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 449214] Akregator crashed when opening a news feed on a new tab
https://bugs.kde.org/show_bug.cgi?id=449214 --- Comment #1 from Don Curtis --- Created attachment 148549 --> https://bugs.kde.org/attachment.cgi?id=148549=edit New crash information added by DrKonqi kontact (5.14.2 (20.04.2)) using Qt 5.12.7 - What I was doing when the application crashed: >From a given News Feed, opening a URL to a linked News article. -- Backtrace (Reduced): #6 0x7fcfeba26906 in content::WebContentsImpl::CreateNewWindow () at ../../3rdparty/chromium/content/browser/web_contents/web_contents_impl.cc:3758 #7 0x7fcfeb8a8521 in content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr, base::OnceCallback)>) () at ../../3rdparty/chromium/content/browser/renderer_host/render_frame_host_impl.cc:5041 #8 0x7fcfe7b3dc11 in content::mojom::FrameHostStubDispatch::AcceptWithResponder () at gen/content/common/frame.mojom.cc:7074 #9 0x7fcfeb88089a in content::mojom::FrameHostStub >::AcceptWithResponder () at gen/content/common/frame.mojom.h:1026 #10 0x7fcfe97d4785 in mojo::InterfaceEndpointClient::HandleValidatedMessage () at ../../3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:528 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 453371] New: Akonadi crash when check new mail
https://bugs.kde.org/show_bug.cgi?id=453371
Bug ID: 453371
Summary: Akonadi crash when check new mail
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: alexey.shis...@gmail.com
Target Milestone: ---
Application: kontact (5.20.0 (22.04.0))
Qt Version: 5.15.2
Frameworks Version: 5.93.0
Operating System: Linux 5.17.4-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Start Kontact, check new (IMAP) mail = crash Akonadi server.
2022-05-04 T09:02:54 [WARN ] org.kde.pim.akonadiserver: Handler exception when
handling command FetchItems on connection Archive Mail Kernel ETM
(0x559d5df39b50) : Item query returned empty result set
2022-05-04 T09:03:35 [CRITICAL] org.kde.pim.akonadiserver: database server
stopped unexpectedly
The crash can be reproduced every time.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 memcpy@GLIBC_2.2.5 () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:222
#7 0x7fe7dd1f7222 in memcpy (__len=18446744062548373608, __src=, __dest=) at /usr/include/bits/string_fortified.h:29
#8 QListData::append (this=0x55fd52e48f90, n=n@entry=1) at tools/qlist.cpp:193
#9 0x7fe7dd1f726a in QListData::append (this=) at
tools/qlist.cpp:206
#10 0x7fe7ddf5c220 in QList::append (t=,
this=) at
../../include/QtCore/../../src/corelib/tools/qlist.h:643
#11 QList::append (this=, t=) at
../../include/QtCore/../../src/corelib/tools/qlist.h:620
#12 0x7fe7ddf89379 in QWidget::insertAction
(this=this@entry=0x55fd541ce100, before=, before@entry=0x0,
action=0x55fd5378bef0) at kernel/qwidget.cpp:3129
#13 0x7fe7de70f433 in KXMLGUI::ActionList::plug (index=,
container=0x55fd541ce100, this=0x55fd5368d890) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguifactory_p.cpp:33
#14 KXMLGUI::ContainerNode::plugActionList (mergingIdxIt=..., state=..., this=0x55fd53db3330) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguifactory_p.cpp:230
#15 KXMLGUI::ContainerNode::plugActionList (this=0x55fd53db3330, state=...) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguifactory_p.cpp:202
#16 0x7fe7de70f4f0 in KXMLGUI::ContainerNode::plugActionList
(this=0x55fd5341bf30, state=...) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguifactory_p.cpp:206
#17 0x7fe7de70f4f0 in KXMLGUI::ContainerNode::plugActionList
(this=0x55fd53282740, state=...) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguifactory_p.cpp:206
#18 0x7fe7de715c81 in KXMLGUIFactory::plugActionList (this=0x55fd538e4590,
client=0x55fd538d54e0, name=..., actionList=...) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguifactory.cpp:564
#19 0x7fe76b922c58 in
PimCommon::PluginInterface::initializePluginActions(QString const&,
KXMLGUIClient*) () from /lib64/libKF5PimCommonAkonadi.so.5
#20 0x7fe7786ba900 in KMMainWidget::initializePluginActions() () from
/lib64/libkmailprivate.so.5
#21 0x7fe778df2a65 in ?? () from /usr/lib64/qt5/plugins/kmailpart.so
#22 0x7fe7dd3cc1af in QObject::event (this=0x55fd538d54b0,
e=0x7fff45f7ec90) at kernel/qobject.cpp:1336
#23 0x7fe7ddf50b0f in QApplicationPrivate::notify_helper (this=, receiver=0x55fd538d54b0, e=0x7fff45f7ec90) at
kernel/qapplication.cpp:3632
#24 0x7fe7dd39fb5a in QCoreApplication::notifyInternal2
(receiver=0x55fd538d54b0, event=0x7fff45f7ec90) at
kernel/qcoreapplication.cpp:1064
#25 0x7fe7dcad9c3f in KParts::MainWindow::createGUI (this=0x55fd53ac9ca0,
part=0x55fd538d54b0) at
/usr/src/debug/kparts-5.93.0-1.1.x86_64/src/mainwindow.cpp:104
#26 0x7fe7de79a7ca in
Kontact::MainWindow::selectPlugin(KontactInterface::Plugin*) () from
/lib64/libkontactprivate.so.5
#27 0x7fe7dd3d6488 in doActivate (sender=0x55fd53661b80,
signal_index=7, argv=0x7fff45f7eed0) at kernel/qobject.cpp:3898
#28 0x7fe7de7953df in ?? () from /lib64/libkontactprivate.so.5
#29 0x7fe7dd3d6453 in QtPrivate::QSlotObjectBase::call (a=0x7fff45f7f000,
r=0x55fd53661b80, this=0x55fd53b2a390) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#30 doActivate (sender=0x55fd53295df0, signal_index=15,
argv=0x7fff45f7f000) at kernel/qobject.cpp:3886
#31 0x7fe7de7a2aa0 in ?? () from /lib64/libkontactprivate.so.5
#32 0x7fe7dd3d6453 in QtPrivate::QSlotObjectBase::call (a=0x7fff45f7f110,
r=0x55fd53295df0, this=0x55fd532dcc70) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#33 doActivate (sender=0x55fd53843540, signal_index=4,
argv=0x7fff45f7f110) at kernel/qobject.cpp:3886
#34 0x7fe7dd3cf7af in
