[kmail2] [Bug 465418] New: "Remove invitation from my calendar" does not work
https://bugs.kde.org/show_bug.cgi?id=465418 Bug ID: 465418 Summary: "Remove invitation from my calendar" does not work Classification: Applications Product: kmail2 Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- I have a recurring calendar event. The invitation was originally also sent via email. Now the organizer sent me a cancellation mail for todays event, which kmail shows with the "Remove invitation from my calendar" button in the mail. However clicking on this button leads to nothing. The event for today is still shown in korganizer. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 465217] New: again and again kmail loses received emails
https://bugs.kde.org/show_bug.cgi?id=465217 Bug ID: 465217 Summary: again and again kmail loses received emails Classification: Frameworks and Libraries Product: Akonadi Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Since years there is the problem that mails get lost and represent themselves as (No Subject), Unknown Sender, 0-timestamp in kmails message list. Even showing them in "Message as plain text" shows a completely empty dialog. Here this happens a lot where I get mails via davmail running locally which itself connects to the company EWS. I have the feeling that this happens more frequently when a bunch of new mails arrive "simultaneously", e.g. more on auto-generated mails coming from our bugtracker. I know this is not reliabely reproducible, but is really a serious issue, since I constantly lose mails! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 462540] New: list of current jobs no longer shown
https://bugs.kde.org/show_bug.cgi?id=462540 Bug ID: 462540 Summary: list of current jobs no longer shown Classification: Applications Product: kmail2 Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- When I send mails or check for new mails, I see the small arrow button in the statusbar. In previous version, I could click on this and get a popup list seeing all currently running jobs and their progress including the possibility to cancel a job. The button is still there and changes up/down direction when clicking on it but the popup no longer appears. -- You are receiving this mail because: You are the assignee for the bug.
[kmailtransport] [Bug 387389] abort when sending mail
https://bugs.kde.org/show_bug.cgi?id=387389 Martin Koller changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Martin Koller --- since I'm not using a self-compiled kmail at this point, I can't check. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 386344] abort when typing in folder filter
https://bugs.kde.org/show_bug.cgi?id=386344 Martin Koller changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 393451] drag a mail into folder tree shows possibility to drop between folders
https://bugs.kde.org/show_bug.cgi?id=393451 Martin Koller changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Martin Koller --- Still possible with Version 5.21.3 (22.08.3) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388714] selecting a favorite when folder tree is filtered shows no messages
https://bugs.kde.org/show_bug.cgi?id=388714 Martin Koller changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Martin Koller --- still the same Version 5.21.3 (22.08.3) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 378930] can not change mbox settings
https://bugs.kde.org/show_bug.cgi?id=378930 Martin Koller changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Martin Koller --- seems to work now -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 378807] dav resource crash after PC resume
https://bugs.kde.org/show_bug.cgi?id=378807 Martin Koller changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Martin Koller --- did not see it recently -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 379029] regression: all the placeholder texts make the user interface unreadable
https://bugs.kde.org/show_bug.cgi?id=379029 Martin Koller changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Martin Koller --- Still the case Version 5.21.2 (22.08.2) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412839] kmail crash when trying to decrypt a mail
https://bugs.kde.org/show_bug.cgi?id=412839 Martin Koller changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Martin Koller --- haven't seen this recently. closing -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409515] sometimes crashes when fetching mail
https://bugs.kde.org/show_bug.cgi?id=409515 Martin Koller changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #13 from Martin Koller --- haven't seen it crash under normal usage since a long time. closing -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458543] New: kmail no longer displayes HTML when defined in a contact
https://bugs.kde.org/show_bug.cgi?id=458543 Bug ID: 458543 Summary: kmail no longer displayes HTML when defined in a contact Product: kmail2 Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Since the latest major update, kmail lost the functionality to display a mail body in HTML when allowed in the contact. This worked before (22.04) but now does no longer (22.08) -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 458271] selected line does not use selection colors
https://bugs.kde.org/show_bug.cgi?id=458271 --- Comment #1 from Martin Koller --- Mistake: the scrrenshot has the wrong akregator on the left and correct konqueror on the right. Operating System: openSUSE Tumbleweed 20220822 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.2-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: HP Product Name: HP ProBook 650 G2 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 458271] New: selected line does not use selection colors
https://bugs.kde.org/show_bug.cgi?id=458271 Bug ID: 458271 Summary: selected line does not use selection colors Product: akregator Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Created attachment 151563 --> https://bugs.kde.org/attachment.cgi?id=151563&action=edit Screenshot Since 22.08, akregator does not honor the selection colors in the tree or in the article list view. Selecting an item does not use the selected background color nor the selected text foreground color. attached is a screenshot showing on the left how it should look like (konqueror) and right (akregator) -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 454495] reminder fires notification for old events
https://bugs.kde.org/show_bug.cgi?id=454495 Martin Koller changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Martin Koller --- The "can not dismiss" issue was the same as in bug #453567 which is fixed now. Somehow in ~/.config/kalendaracrc I had some old Suspended events - these are retriggered on start of the reminder daemon. Since the "Dismiss" action was not working, I could not get rid of them. Let's close for now and see if it happens again. -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453567] endless reminder notifications
https://bugs.kde.org/show_bug.cgi?id=453567 Martin Koller changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||akonadi-calendar/commit/e1b ||7964a91c7fe47a1d909e4fd079c ||b6c37d21b3 Status|REPORTED|RESOLVED --- Comment #4 from Martin Koller --- Git commit e1b7964a91c7fe47a1d909e4fd079cb6c37d21b3 by Martin Koller. Committed on 04/06/2022 at 20:55. Pushed by mkoller into branch 'release/22.04'. add missing connect for the "Dismiss" action M +8-4reminder-daemon/alarmnotification.cpp M +3-1reminder-daemon/kalendaralarmclient.cpp https://invent.kde.org/pim/akonadi-calendar/commit/e1b7964a91c7fe47a1d909e4fd079cb6c37d21b3 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 454495] New: reminder fires notification for old events
https://bugs.kde.org/show_bug.cgi?id=454495 Bug ID: 454495 Summary: reminder fires notification for old events Product: Reminder Daemon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Had this before, now also with the new "Reminder Daemon". After a reboot and fresh login, I get reminder notifications for an event 2 days ago. The event is a recurring event, every week on tuesdays, but the last instance was moved from tuesday to wednesday. Now (friday) I get the reminder of the wednesday event and I can not dismiss it (the notification comes again and again). -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453567] endless reminder notifications
https://bugs.kde.org/show_bug.cgi?id=453567 --- Comment #3 from Martin Koller --- generally the reminder daemon seems to not pick up changes for an event. I have a recurring event (every week at 15:00) and today I moved the instance from today to the next day, so that today I should have NO event, but tomorrow there is now one. Still, the reminder daemon triggers the reminder notification for TODAY, which I can not dismiss (the notifcation is not removed when clicking the "dismiss" option) and the notification is triggered endlessly every minute, even though the start time is 15:00 and now it's already 15:35 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453567] endless reminder notifications
https://bugs.kde.org/show_bug.cgi?id=453567 --- Comment #2 from Martin Koller --- Another detail: the event at 6:00 is a recurring (endless every monday) event. The other event at 9:00 is a single event but even removing the reminder setting completely in that event does not stop kalendarac to keep sending the reminder notification message. -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453567] endless reminder notifications
https://bugs.kde.org/show_bug.cgi?id=453567 --- Comment #1 from Martin Koller --- I should add that this is happening for 2 events which occured on the 9th of May at 6:00 and 9:00 (today is already the 15th). I always get these 2 events in tandem and can't dismiss either of them. Maybe the main issue here is that I get reminders for events which are long over, nearly a week ago. -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453843] New: view event does not actually show the event
https://bugs.kde.org/show_bug.cgi?id=453843 Bug ID: 453843 Summary: view event does not actually show the event Product: Reminder Daemon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- I have an event at 6:00 but the agenda view shows the time from 7:00 - 21:00. When a reminder for the 6:00 event shows up, clicking on view shows the date for the event but it does not actually show the 6:00 event since it's above the viewed time span. korgac ASAIR did open the event details dialog, which is a much better option, since I see exactly the one event I clicked "view" on, and not the whole day which potentially has a lot of other events. So my whish would be to do it as korgac did: show the details dialog for the one event I clicked. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 453567] New: endless reminder notifications
https://bugs.kde.org/show_bug.cgi?id=453567 Bug ID: 453567 Summary: endless reminder notifications Product: korganizer Version: 5.20.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- since the upgrade to this new reminder daemon, I continuously get notifications for the same incidence again and again. After clicking "Dismiss", the notification reappears in a minute or so -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 450824] New: crash when closing kleopatra
https://bugs.kde.org/show_bug.cgi?id=450824 Bug ID: 450824 Summary: crash when closing kleopatra Product: kleopatra Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: kol...@aon.at CC: kdepim-bugs@kde.org, m...@kde.org Target Milestone: --- Application: kleopatra (3.1.19.211202 (21.12.2)) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.16.10-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.24.1 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Started kleopatra (have a smartcard inserted), Quit kleopatra -> crash The crash can be reproduced every time. -- Backtrace: Application: Kleopatra (kleopatra), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #5 0x7fa66c4601e3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #6 0x7fa66c410306 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #7 0x7fa66c3f9813 in __GI_abort () at abort.c:79 #8 0x7fa66c3f972b in __assert_fail_base (fmt=, assertion=, file=, line=, function=) at assert.c:92 #9 0x7fa66c4088f6 in __GI___assert_fail (assertion=0x7fa66e2b909f "li", file=0x7fa66e2b907d "wait-global.c", line=125, function=0x7fa66e2ba480 "ctx_done") at assert.c:101 #10 0x7fa66e286106 in ?? () from /lib64/libgpgme.so.11 #11 0x7fa66e2b67a3 in ?? () from /lib64/libgpgme.so.11 #12 0x7fa66e2b6960 in gpgme_cancel () from /lib64/libgpgme.so.11 #13 0x7fa66e2f2821 in GpgME::Context::cancelPendingOperationImmediately() () from /lib64/libgpgmepp.so.6 #14 0x563eb061ad39 in ?? () #15 0x563eb061ada9 in ?? () #16 0x7fa66cb2324f in QObject::event (this=0x563eb18c5000, e=0x7fa64c0051f0) at kernel/qobject.cpp:1301 #17 0x7fa66d6a7a7f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7fa66caf6e3a in QCoreApplication::notifyInternal2 (receiver=0x563eb18c5000, event=0x7fa64c0051f0) at kernel/qcoreapplication.cpp:1064 #19 0x7fa66caf9e77 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=52, data=0x563eb1893d80) at kernel/qcoreapplication.cpp:1821 #20 0x7fa66c9115d5 in QThreadPrivate::finish (arg=0x563eb18840a8) at thread/qthread_unix.cpp:371 #21 0x7fa66c911ef7 in __pthread_cleanup_class::~__pthread_cleanup_class (this=, __in_chrg=) at /usr/include/pthread.h:578 #22 QThreadPrivate::start (arg=0x563eb18840a8) at thread/qthread_unix.cpp:350 #23 0x7fa66c45e2ba in start_thread (arg=) at pthread_create.c:442 #24 0x7fa66c4e8440 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 3 (Thread 0x7fa6669a8640 (LWP 27282) "QDBusConnection"): #1 0x7fa66b01714e in ?? () from /lib64/libglib-2.0.so.0 #2 0x7fa66b01726f in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fa66cb4e3f6 in QEventDispatcherGlib::processEvents (this=0x7fa658000b70, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa66caf583b in QEventLoop::exec (this=this@entry=0x7fa6669a7b50, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #5 0x7fa66c910d7e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7fa66df32287 in ?? () from /lib64/libQt5DBus.so.5 #7 0x7fa66c911eef in QThreadPrivate::start (arg=0x7fa66dfab440) at thread/qthread_unix.cpp:331 #8 0x7fa66c45e2ba in start_thread (arg=) at pthread_create.c:442 #9 0x7fa66c4e8440 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 2 (Thread 0x7fa6681c1640 (LWP 27281) "QXcbEventQueue"): #1 0x7fa66be3a892 in ?? () from /lib64/libxcb.so.1 #2 0x7fa66be3c2ac in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7fa668300dc0 in ?? () from /lib64/libQt5XcbQpa.so.5 #4 0x7fa66c911eef in QThreadPrivate::start (arg=0x563eb1744e60) at thread/qthread_unix.cpp:331 #5 0x7fa66c45e2ba in start_thread (arg=) at pthread_create.c:442 #6 0x7fa66c4e8440 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 1 (Thread 0x7fa66a07e980 (LWP 27280) "kleopatra"): #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x563eb18975f0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7fa66c45a97f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x563eb18975f0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x7fa66c45
[kmail2] [Bug 378689] fancy headers uses wrong indent
https://bugs.kde.org/show_bug.cgi?id=378689 Martin Koller changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||kdepim-addons/commit/a287d4 ||90e64f45853ac999c5642082176 ||589ed74 --- Comment #1 from Martin Koller --- Git commit a287d490e64f45853ac999c5642082176589ed74 by Martin Koller. Committed on 09/01/2022 at 15:18. Pushed by mkoller into branch 'release/21.12'. Fix header width M +1-0 plugins/messageviewerheaderplugins/fancyheaderstyleplugin/fancyheaderstyleplugin.cpp https://invent.kde.org/pim/kdepim-addons/commit/a287d490e64f45853ac999c5642082176589ed74 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 414977] broken layout does no longer resize attendee list
https://bugs.kde.org/show_bug.cgi?id=414977 Martin Koller changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||incidenceeditor/commit/5cca ||64c559b3651f40985ce9104d3bb ||a79af3749 --- Comment #3 from Martin Koller --- Git commit 5cca64c559b3651f40985ce9104d3bba79af3749 by Martin Koller. Committed on 26/12/2021 at 17:08. Pushed by mkoller into branch 'release/21.12'. make organizer lable wider M +1-1src/ui/dialogdesktop.ui https://invent.kde.org/pim/incidenceeditor/commit/5cca64c559b3651f40985ce9104d3bba79af3749 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 439803] New: reminder shows wrong time when item in series changed
https://bugs.kde.org/show_bug.cgi?id=439803 Bug ID: 439803 Summary: reminder shows wrong time when item in series changed Product: korganizer Version: 5.17.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- I have a recurring event every week at 15:00, but I changed the event today (as an exception) to start at 16:15. However when the reminder triggered 15 minutes before at 16:00 (which is OK), the dialog popping up still shows Time: 15:00 - 15:45 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 439391] New: korgac not started/stopped when not shown in System Tray
https://bugs.kde.org/show_bug.cgi?id=439391 Bug ID: 439391 Summary: korgac not started/stopped when not shown in System Tray Product: korganizer Version: 5.17.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- When I uncheck "Show Reminder Daemon in System Tray", korgac is stopped, therefore I don't get the reminders. This contradicts the explicitely stated Note, that the daemon keeps running, even when unchecked. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 439017] New: can not remove custom field
https://bugs.kde.org/show_bug.cgi?id=439017 Bug ID: 439017 Summary: can not remove custom field Product: kaddressbook Version: 5.17.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at CC: to...@kde.org Target Milestone: --- I double click on an entry, select the "Custom fields" tab and have 2 lines: X-CUSTOM-KPILOT-MODIFIED and KPILOT-RECORDID On the right of the value each line has a red minus icon, which I assume is to remove the line. However clicking on it does not do anything and I see no other way to get rid of a line. It does not matter where the contact is stored. Even when I try to remove a line while creating(!) a new contact, before having clicked on the OK button (the contact is not created yet), it does not work. The version is in fact 5.17.2 on Operating System: openSUSE Tumbleweed 20210618 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.10-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 520 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 438728] after login reminders are shown for dates long passed
https://bugs.kde.org/show_bug.cgi?id=438728 Martin Koller changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Martin Koller --- Sadly, I can not reproduce it. I tried to logout several times, ensuring no processes were running for my user, then login again - no reminders. Event after a reboot (although I'm pretty sure that does not make any difference) and login, no reminders. I had the issue already a few times in the past, but since I very seldomly logout or even reboot (every few weeks only), the chance is therefore already rather low. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 438728] New: after login reminders are shown for dates long passed
https://bugs.kde.org/show_bug.cgi?id=438728 Bug ID: 438728 Summary: after login reminders are shown for dates long passed Product: korganizer Version: 5.17.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Created attachment 139382 --> https://bugs.kde.org/attachment.cgi?id=139382&action=edit screenshot of reminders I did just a system upgrade on openSuse Tumbleweed and after reboot and a new login, the reminder daemon pops up the dialog showing me dates from 3 weeks ago. See screenshot. I expect to not see reminders for dates which have already long passed. Operating System: openSUSE Tumbleweed 20210614 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.9-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 520 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 382335] often links clicked lead to empty pages or doing nothing
https://bugs.kde.org/show_bug.cgi?id=382335 Martin Koller changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Martin Koller --- I'm using here Version 5.15.2 (20.08.2) and the issue of a link-click doing nothing is still there. E.g. I read https://www.teslarati.com/spacex-starlink-approved-canada-beta-invites/ and click on the link in the text "Beta users have already begun putting Starlink user terminals through their paces..." https://www.reddit.com/r/Starlink/comments/jqedvw/snow_in_sw_montana_today/ and nothing happens. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409383] akonadi_davgroupware_resource always crashes on startup
https://bugs.kde.org/show_bug.cgi?id=409383 Martin Koller changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Martin Koller --- just tested, does no longer occur: Operating System: openSUSE Tumbleweed 20200910 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.7-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 520 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 424957] New: korganizer crashed when moving one event of a series
https://bugs.kde.org/show_bug.cgi?id=424957 Bug ID: 424957 Summary: korganizer crashed when moving one event of a series Product: korganizer Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Application: korganizer (5.14.3 (20.04.3)) Qt Version: 5.15.0 Frameworks Version: 5.72.0 Operating System: Linux 5.7.9-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I have an event which recurs every week. I moved the event from today one hour down and korganizer crashed -- Backtrace: Application: KOrganizer (korganizer), signal: Aborted [KCrash Handler] #4 0x7feb71fcb4b1 in raise () from /lib64/libc.so.6 #5 0x7feb71fb4539 in abort () from /lib64/libc.so.6 #6 0x7feb7252bc27 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffc2c1fc6f8, msg=msg@entry=0x7feb72825ea0 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:893 #8 0x7feb7252b074 in qt_assert (assertion=, file=, line=) at ../../include/QtCore/../../src/corelib/global/qlogging.h:90 #9 0x7feb74dcf168 in Akonadi::IncidenceChanger::Private::handleTransactionJobResult (this=0x4d0960, job=0xba4d60) at /home/KDE5/source/kde/pim/akonadi-calendar/src/incidencechanger.cpp:229 #10 0x7feb74de1dbf in QtPrivate::FunctorCall, QtPrivate::List, void, void (Akonadi::IncidenceChanger::Private::*)(KJob*)>::call (f=(void (Akonadi::IncidenceChanger::Private::*)(Akonadi::IncidenceChanger::Private * const, KJob *)) 0x7feb74dceec0 , o=0x4d0960, arg=0x7ffc2c1fc9e0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:152 #11 0x7feb74de1d28 in QtPrivate::FunctionPointer::call, void> (f=(void (Akonadi::IncidenceChanger::Private::*)(Akonadi::IncidenceChanger::Private * const, KJob *)) 0x7feb74dceec0 , o=0x4d0960, arg=0x7ffc2c1fc9e0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:185 #12 0x7feb74de1c55 in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x7feb60035920, r=0x4d0960, a=0x7ffc2c1fc9e0, ret=0x0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:418 #13 0x7feb7277b0f6 in QtPrivate::QSlotObjectBase::call (a=0x7ffc2c1fc9e0, r=0x4d0960, this=0x7feb60035920) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate (sender=0xba4d60, signal_index=6, argv=argv@entry=0x7ffc2c1fc9e0) at kernel/qobject.cpp:3886 #15 0x7feb72774450 in QMetaObject::activate (sender=sender@entry=0xba4d60, m=m@entry=0x7feb7392f660 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc2c1fc9e0) at kernel/qobject.cpp:3946 #16 0x7feb738dde0c in KJob::result (this=this@entry=0xba4d60, _t1=, _t1@entry=0xba4d60, _t2=...) at /usr/src/debug/kcoreaddons-5.72.0-1.1.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:576 #17 0x7feb738e20a3 in KJob::finishJob (this=0xba4d60, emitResult=) at /usr/src/debug/kcoreaddons-5.72.0-1.1.x86_64/src/lib/jobs/kjob.cpp:96 #18 0x7feb745ace1b in Akonadi::TransactionSequencePrivate::commitResult (this=0x1362740, job=0xec6290) at /home/KDE5/source/kde/pim/akonadi/src/core/jobs/transactionsequence.cpp:60 #19 0x7feb745ac4a0 in Akonadi::TransactionSequence::slotResult(KJob*)::$_1::operator()(KJob*) const (this=0x118e6b0, job=0xec6290) at /home/KDE5/source/kde/pim/akonadi/src/core/jobs/transactionsequence.cpp:135 #20 0x7feb745ac464 in QtPrivate::FunctorCall, QtPrivate::List, void, Akonadi::TransactionSequence::slotResult(KJob*)::$_1>::call(Akonadi::TransactionSequence::slotResult(KJob*)::$_1&, void**) (f=..., arg=0x7ffc2c1fcc50) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #21 0x7feb745ac431 in QtPrivate::Functor::call, void>(Akonadi::TransactionSequence::slotResult(KJob*)::$_1&, void*, void**) (f=..., arg=0x7ffc2c1fcc50) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #22 0x7feb745ac3dc in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x118e6a0, r=0xec6290, a=0x7ffc2c1fcc50, ret=0x0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #23 0x7feb7277b0f6 in QtPrivate::QSlotObjectBase::call (a=0x7ffc2c1fcc50, r=0xec6290, this=0x118e6a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #24 doActivate (sender=0xec6290, signal_index=6, argv=argv@entry=0x7ffc2c1fcc50) at kernel/qobject.cpp:3886 #25 0x7feb72774450 in QMetaObject::activate (sender=sender@entry=0xec6290, m=m@entry=0x7feb7392f660 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc2c1fcc50) at kernel/qobject.cpp:3946 #26 0x7feb738dde0c in KJob::result (this=this@entry=0xec6290, _t1=, _t1@ent
[Akonadi] [Bug 423132] New: mail dispatcher crash on sending email
https://bugs.kde.org/show_bug.cgi?id=423132 Bug ID: 423132 Summary: mail dispatcher crash on sending email Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Mail Dispatcher Agent Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Application: akonadi_maildispatcher_agent (5.14.3 (20.04.3)) Qt Version: 5.15.0 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: I sent an email and the mail dispatcher crashed. The mail was sent via a locally running davmail -- Backtrace: Application: akonadi_maildispatcher_agent (akonadi_maildispatcher_agent), signal: Aborted [KCrash Handler] #4 0x7f73a26ad4b1 in raise () from /lib64/libc.so.6 #5 0x7f73a2696539 in abort () from /lib64/libc.so.6 #6 0x7f73a2c0dc27 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffed2472c88, msg=msg@entry=0x7f73a2f07ea0 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:893 #8 0x7f73a2c0d074 in qt_assert (assertion=, file=, line=) at ../../include/QtCore/../../src/corelib/global/qlogging.h:90 #9 0x00424473 in SendJob::transportResult (this=0x7f738804fbc0, job=0x1889e30) at /home/KDE5/source/kde/pim/kdepim-runtime/agents/maildispatcher/sendjob.cpp:202 #10 0x004291cf in QtPrivate::FunctorCall, QtPrivate::List, void, void (SendJob::*)(KJob*)>::call (f=(void (SendJob::*)(SendJob * const, KJob *)) 0x424430 , o=0x7f738804fbc0, arg=0x7ffed2472f30) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:152 #11 0x00429138 in QtPrivate::FunctionPointer::call, void> (f=(void (SendJob::*)(SendJob * const, KJob *)) 0x424430 , o=0x7f738804fbc0, arg=0x7ffed2472f30) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:185 #12 0x00429065 in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x183c3c0, r=0x7f738804fbc0, a=0x7ffed2472f30, ret=0x0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:418 #13 0x7f73a2e5cfe6 in QtPrivate::QSlotObjectBase::call (a=0x7ffed2472f30, r=0x7f738804fbc0, this=0x183c3c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate (sender=0x1889e30, signal_index=6, argv=argv@entry=0x7ffed2472f30) at kernel/qobject.cpp:3886 #15 0x7f73a2e56340 in QMetaObject::activate (sender=sender@entry=0x1889e30, m=m@entry=0x7f73a4010660 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffed2472f30) at kernel/qobject.cpp:3946 #16 0x7f73a3fbee0c in KJob::result (this=this@entry=0x1889e30, _t1=, _t1@entry=0x1889e30, _t2=...) at /usr/src/debug/kcoreaddons-5.70.0-1.2.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:574 #17 0x7f73a3fc30b3 in KJob::finishJob (this=0x1889e30, emitResult=) at /usr/src/debug/kcoreaddons-5.70.0-1.2.x86_64/src/lib/jobs/kjob.cpp:96 #18 0x7f739c0ae6d7 in MailTransport::SmtpJob::startSmtpJob()::$_0::operator()(QString const&) const (this=0x18876e0, err=...) at /home/KDE5/source/kde/pim/kmailtransport/src/kmailtransport/plugins/smtp/smtpjob.cpp:169 #19 0x7f739c0ae654 in QtPrivate::FunctorCall, QtPrivate::List, void, MailTransport::SmtpJob::startSmtpJob()::$_0>::call(MailTransport::SmtpJob::startSmtpJob()::$_0&, void**) (f=..., arg=0x1856e38) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #20 0x7f739c0ae621 in QtPrivate::Functor::call, void>(MailTransport::SmtpJob::startSmtpJob()::$_0&, void*, void**) (f=..., arg=0x1856e38) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #21 0x7f739c0ae5cc in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x18876d0, r=0x1889e30, a=0x1856e38, ret=0x0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #22 0x7f73a2e52a31 in QObject::event (this=0x1889e30, e=0x1856df0) at kernel/qobject.cpp:1314 #23 0x7f73a397d0cf in QApplicationPrivate::notify_helper (this=, receiver=0x1889e30, e=0x1856df0) at kernel/qapplication.cpp:3671 #24 0x7f73a2e26b0a in QCoreApplication::notifyInternal2 (receiver=0x1889e30, event=0x1856df0) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #25 0x7f73a2e29531 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x15f91b0) at kernel/qcoreapplication.cpp:1815 #26 0x7f73a2e7e8c3 in postEventSourceDispatch (s=0x16cdb70) at kernel/qeventdispatcher_glib.cpp:277 #27 0x7f73a12e12c7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x7f73a12e1648 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x7f73a12e16ff in g_main_context_iteration () from /usr/lib64/libgl
[korganizer] [Bug 421771] reminder daemon not started when not also shown in systray
https://bugs.kde.org/show_bug.cgi?id=421771 Martin Koller changed: What|Removed |Added Version|5.12.3 |5.14.1 --- Comment #2 from Martin Koller --- No, I'm using self-compiled Version 5.14.1 (20.04.0) -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 421771] New: reminder daemon not started when not also shown in systray
https://bugs.kde.org/show_bug.cgi?id=421771 Bug ID: 421771 Summary: reminder daemon not started when not also shown in systray Product: korganizer Version: 5.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- I want the reminder daemon running of course but I do not need it in the systray, so I unchecked the option "Show reminder daemon in the systray", which also tells me that "the daemon will continue running even if it's not shown in the systray" but that seems to no longer work, since when I uncheck this option, also the korgac daemon is stopped and I get no reminders. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 420765] New: imap resource crashed after Laptop resume
https://bugs.kde.org/show_bug.cgi?id=420765 Bug ID: 420765 Summary: imap resource crashed after Laptop resume Product: Akonadi Version: 5.14.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Application: akonadi_imap_resource (5.14.0 (20.04.0)) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.6.4-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: After I resumed the Laptop from suspend, the imap resource crashed immediately -- Backtrace: Application: IMAP_davmail (akonadi_imap_resource), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f95ac8b5cc0 (LWP 25079))] Thread 9 (Thread 0x7f958adee700 (LWP 25293)): #0 0x7f95b2954629 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f95b29088d7 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f95b290926b in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f95b290945f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f95bc77ec0b in QEventDispatcherGlib::processEvents (this=0x7f957c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f95bc726b9b in QEventLoop::exec (this=this@entry=0x7f958aded8e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f95bc5515ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f95bc552698 in QThreadPrivate::start (arg=0x10c3bf0) at thread/qthread_unix.cpp:342 #8 0x7f95b37ffefa in start_thread () from /lib64/libpthread.so.0 #9 0x7f95bc07e3bf in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f958bfff700 (LWP 25258)): #0 0x7f95b29088bd in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7f95b290926b in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f95b290945f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f95bc77ec0b in QEventDispatcherGlib::processEvents (this=0x7f9584000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f95bc726b9b in QEventLoop::exec (this=this@entry=0x7f958bffe8e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f95bc5515ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f95bc552698 in QThreadPrivate::start (arg=0x1083730) at thread/qthread_unix.cpp:342 #7 0x7f95b37ffefa in start_thread () from /lib64/libpthread.so.0 #8 0x7f95bc07e3bf in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f95a0df7700 (LWP 25251)): #0 0x7f95bc073acf in poll () from /lib64/libc.so.6 #1 0x7f95b290933e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f95b290945f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f95bc77ec0b in QEventDispatcherGlib::processEvents (this=0x7f959b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f95bc726b9b in QEventLoop::exec (this=this@entry=0x7f95a0df68b0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f95bc5515ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f95bd98a507 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f95bc552698 in QThreadPrivate::start (arg=0x7f95bda0cda0) at thread/qthread_unix.cpp:342 #8 0x7f95b37ffefa in start_thread () from /lib64/libpthread.so.0 #9 0x7f95bc07e3bf in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f95a2ffd700 (LWP 25219)): #0 0x7f95b3806795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f95a93fd98b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f95a93fd807 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f95b37ffefa in start_thread () from /lib64/libpthread.so.0 #4 0x7f95bc07e3bf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f95a37fe700 (LWP 25218)): #0 0x7f95b3806795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f95a93fd98b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f95a93fd807 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f95b37ffefa in start_thread () from /lib64/libpthread.so.0 #4 0x7f95bc07e3bf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f95a3fff700 (LWP 25217)): #0 0x7f95b3806795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f95a93fd98b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f95a93fd807 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f95b37ffefa in start_thread () from /lib64/libpthread.so.
[korganizer] [Bug 411777] import of vcs fails, still says success
https://bugs.kde.org/show_bug.cgi?id=411777 --- Comment #4 from Martin Koller --- I tested now again with a self-compiled KDE-PIM (20.04) on Operating System: openSUSE Tumbleweed 20200415 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 Kernel Version: 5.6.2-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 15,5 GiB of RAM Now korganizer and korgac crash when I import it and merge it into an existing calendar (stored on a nextcloud server). backtrace of korganizer below. When I import it as a new calendar, then it is still not shown in korganizer but at least no crash. Checking with akonadiconsole and looking on the new calendar shows 0 items. Thread 1 (Thread 0x7fd1985ed880 (LWP 15319)): [KCrash Handler] #6 0x7fd19b572ea1 in raise () from /lib64/libc.so.6 #7 0x7fd19b55c53d in abort () from /lib64/libc.so.6 #8 0x7fd19bad1aef in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1894 #9 QMessageLogger::fatal (this=this@entry=0x7fff2e279750, msg=msg@entry=0x7fd19bdbeea0 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:893 #10 0x7fd19bad0f2f in qt_assert (assertion=, file=, line=) at ../../include/QtCore/../../src/corelib/global/qlogging.h:90 #11 0x7fd19e33ed39 in Akonadi::ETMCalendarPrivate::updateItem (this=0x2430480, item=...) at /home/KDE5/source/kde/pim/akonadi-calendar/src/etmcalendar.cpp:408 #12 0x7fd19e33d534 in Akonadi::ETMCalendarPrivate::onDataChangedInFilteredModel (this=0x2430480, topLeft=..., bottomRight=...) at /home/KDE5/source/kde/pim/akonadi-calendar/src/etmcalendar.cpp:394 #13 0x7fd19e34b947 in QtPrivate::FunctorCall, QtPrivate::List, void, void (Akonadi::ETMCalendarPrivate::*)(QModelIndex const&, QModelIndex const&)>::call (f=(void (Akonadi::ETMCalendarPrivate::*)(Akonadi::ETMCalendarPrivate * const, const QModelIndex &, const QModelIndex &)) 0x7fd19e33d420 , o=0x2430480, arg=0x7fff2e279bf0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:152 #14 0x7fd19e34b8a8 in QtPrivate::FunctionPointer::call, void> (f=(void (Akonadi::ETMCalendarPrivate::*)(Akonadi::ETMCalendarPrivate * const, const QModelIndex &, const QModelIndex &)) 0x7fd19e33d420 , o=0x2430480, arg=0x7fff2e279bf0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:185 #15 0x7fd19e34b7d5 in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x246d9b0, r=0x2430480, a=0x7fff2e279bf0, ret=0x0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:414 #16 0x7fd19bd149fe in QtPrivate::QSlotObjectBase::call (a=0x7fff2e279bf0, r=0x2430480, this=0x246d9b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #17 doActivate (sender=0x247a4b0, signal_index=3, argv=0x7fff2e279bf0) at kernel/qobject.cpp:3870 #18 0x7fd19bd0f1bf in QMetaObject::activate (sender=sender@entry=0x247a4b0, m=m@entry=0x7fd19bfa1060 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff2e279bf0) at kernel/qobject.cpp:3930 #19 0x7fd19bc83d35 in QAbstractItemModel::dataChanged (this=this@entry=0x247a4b0, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #20 0x7fd19bcb7b2d in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x247f6c0, source_top_left=..., source_bottom_right=..., roles=...) at itemmodels/qsortfilterproxymodel.cpp:1500 #21 0x7fd19bcb8c2a in QSortFilterProxyModel::qt_static_metacall (_o=, _c=, _id=, _a=) at itemmodels/qsortfilterproxymodel.h:199 #22 0x7fd19bd14a30 in doActivate (sender=0x24430e0, signal_index=3, argv=0x7fff2e279ee0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:391 #23 0x7fd19bd0f1bf in QMetaObject::activate (sender=sender@entry=0x24430e0, m=m@entry=0x7fd19bfa1060 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff2e279ee0) at kernel/qobject.cpp:3930 #24 0x7fd19bc83d35 in QAbstractItemModel::dataChanged (this=this@entry=0x24430e0, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #25 0x7fd19bcb7b2d in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x247e6d0, source_top_left=..., source_bottom_right=..., roles=...) at itemmodels/qsortfilterproxymodel.cpp:1500 #26 0x7fd19bcb8c2a in QSortFilterProxyModel::qt_static_metacall (_o=, _c=, _id=, _a=) at itemmodels/qsortfilterproxymodel.h:199 #27 0x7fd19bd14a30 in doActivate (sender=0x23fef30, signal_index=3, argv=0x7fff2e27a1d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:391 #28 0x7fd19bd0f1bf in QMetaObject::activate (sender=sender@entry=0x23fef30, m=m@entry=0x7fd19bfa1060 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff2e27a1d0) at kernel/qobject.cpp:3930 #29 0x7fd19bc83d35 in QAbstractItemModel::dataChanged (this=this@entry=0x23fef30, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #30 0x7fd19bcb7b2d in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x247d3b0, source
[kmail2] [Bug 377554] "Show HTML for this contact" no longer works
https://bugs.kde.org/show_bug.cgi?id=377554 --- Comment #5 from Martin Koller --- Using current Version 5.14.0 (20.04.0) self compiled, it still does not work. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 419726] New: trying to change POP3 resource crashes
https://bugs.kde.org/show_bug.cgi?id=419726 Bug ID: 419726 Summary: trying to change POP3 resource crashes Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: POP3 Resource Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at CC: aa...@kde.org Target Milestone: --- Application: akonadi_pop3_resource (5.14.0 (20.04.0)) Qt Version: 5.14.1 Frameworks Version: 5.68.0 Operating System: Linux 5.6.0-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: In kmail configuration dialog -> Accounts I select a POP3 resource and click Modify -> crash The crash can be reproduced every time. -- Backtrace: Application: gmail (akonadi_pop3_resource), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6c0f7c6040 (LWP 12164))] Thread 10 (Thread 0x7f6bf664a700 (LWP 15177)): #0 0x7f6c127e8f59 in syscall () at /lib64/libc.so.6 #1 0x7f6c12cc4841 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:133 #2 0x7f6c12cc4841 in QtLinuxFutex::futexWait >(QBasicAtomicInteger&, QBasicAtomicInteger::Type) (expectedValue=, futex=...) at thread/qfutex_p.h:135 #3 0x7f6c12cc4841 in futexSemaphoreTryAcquire_loop(QBasicAtomicInteger&, unsigned long long, unsigned long long, int) (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:219 #4 0x7f6c12cc4841 in futexSemaphoreTryAcquire(QBasicAtomicInteger&, int, int) (timeout=-1, n=, u=...) at thread/qsemaphore.cpp:262 #5 0x7f6c12cc4841 in QSemaphore::acquire(int) (this=0x7f6c144c95a0, n=) at thread/qsemaphore.cpp:326 #6 0x7f6c143f69b4 in () at /usr/lib64/libQt5Network.so.5 #7 0x7f6c12cc2698 in QThreadPrivate::start(void*) (arg=0x7f6c144c9580) at thread/qthread_unix.cpp:342 #8 0x7f6c11c94efa in start_thread () at /lib64/libpthread.so.0 #9 0x7f6c127ee3bf in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f6bf6ffd700 (LWP 15011)): #0 0x7f6c11c9b795 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6c050d7c5b in () at /usr/lib64/dri/i965_dri.so #2 0x7f6c050d7ad7 in () at /usr/lib64/dri/i965_dri.so #3 0x7f6c11c94efa in start_thread () at /lib64/libpthread.so.0 #4 0x7f6c127ee3bf in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f6bf77fe700 (LWP 15010)): #0 0x7f6c11c9b795 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6c050d7c5b in () at /usr/lib64/dri/i965_dri.so #2 0x7f6c050d7ad7 in () at /usr/lib64/dri/i965_dri.so #3 0x7f6c11c94efa in start_thread () at /lib64/libpthread.so.0 #4 0x7f6c127ee3bf in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f6bf7fff700 (LWP 15009)): #0 0x7f6c11c9b795 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6c050d7c5b in () at /usr/lib64/dri/i965_dri.so #2 0x7f6c050d7ad7 in () at /usr/lib64/dri/i965_dri.so #3 0x7f6c11c94efa in start_thread () at /lib64/libpthread.so.0 #4 0x7f6c127ee3bf in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f6c04a0b700 (LWP 15008)): #0 0x7f6c11c9b795 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6c050d7c5b in () at /usr/lib64/dri/i965_dri.so #2 0x7f6c050d7ad7 in () at /usr/lib64/dri/i965_dri.so #3 0x7f6c11c94efa in start_thread () at /lib64/libpthread.so.0 #4 0x7f6c127ee3bf in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f6c06fd0700 (LWP 12169)): #0 0x7f6c10f49644 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f6c10efd8bd in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f6c10efe26b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6c10efe45f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f6c12eeec0b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f6bfc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f6c12e96b9b in QEventLoop::exec(QFlags) (this=this@entry=0x7f6c06fcfda0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f6c12cc15ce in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f6c12cc2698 in QThreadPrivate::start(void*) (arg=0xf27850) at thread/qthread_unix.cpp:342 #8 0x7f6c11c94efa in start_thread () at /lib64/libpthread.so.0 #9 0x7f6c127ee3bf in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f6c077d1700 (LWP 12167)): #0 0x7ffd913f1af4 in clock_gettime () #1 0x7f6c127b5cf1 in clock_gettime@GLIBC_2.2.5 () at /lib64/libc.so.6 #2 0x7f6c12eee511 in qt_clock_gettime (ts=0x7f6c077d0b0
[kmail2] [Bug 413022] decrypting mail (via filter) removes From/To mail headers
https://bugs.kde.org/show_bug.cgi?id=413022 Martin Koller changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/mai ||lcommon/0628360b2240fda1be5 ||4e38abd46865707666c2c Status|REPORTED|RESOLVED --- Comment #1 from Martin Koller --- Git commit 0628360b2240fda1be54e38abd46865707666c2c by Martin Koller. Committed on 04/04/2020 at 18:40. Pushed by mkoller into branch 'release/20.04'. do not lose address headers when decrypting mail Differential Revision: https://phabricator.kde.org/D28399 M +1-1src/filter/autotests/gpgdata/text-plain.msg M +1-1src/filter/autotests/gpgdata/text-plain.msg.pgp M +1-1src/filter/autotests/gpgdata/text-plain.msg.smime M +1-1src/util/cryptoutils.cpp https://commits.kde.org/mailcommon/0628360b2240fda1be54e38abd46865707666c2c -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 419482] New: icon in "important" column wrong
https://bugs.kde.org/show_bug.cgi?id=419482 Bug ID: 419482 Summary: icon in "important" column wrong Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Created attachment 127155 --> https://bugs.kde.org/attachment.cgi?id=127155&action=edit screenshot SUMMARY The icon shown in the "Important" column is now wrong (worked e.g. with KDE 19.12). The icon in the column header is still correct, but in the row per mail the icon is now wrong and different from the column header. See attached screenshot. Please bring back the icon which is shown in the column header. It is much better visible than the one currently visible. SOFTWARE/OS VERSIONS openSuse Tumbleweed PIM compiled from source, git master -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 419473] New: kmail crashed on sending mail
https://bugs.kde.org/show_bug.cgi?id=419473 Bug ID: 419473 Summary: kmail crashed on sending mail Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Application: kmail (5.13.90 rc (20.03.90)) Qt Version: 5.14.1 Frameworks Version: 5.68.0 Operating System: Linux 5.5.11-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I just replied to an email, hit the send button and kmail crashed. The mail was plain text (no HTML) -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0a936a0ac0 (LWP 17210))] Thread 22 (Thread 0x7f0a55ffb700 (LWP 15921)): #0 0x7f0aa3023aaa in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0a9d91bbe6 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x000246ca in ?? () #3 0x281b5daf in ?? () #4 0x000246a9 in ?? () #5 0x281b6967 in ?? () #6 0x in ?? () Thread 21 (Thread 0x7f0a54ff9700 (LWP 9742)): #0 0x7f0aa4421acf in poll () from /lib64/libc.so.6 #1 0x7f0a98fea2fe in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f0a98fea41f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f0aa4b2ac0b in QEventDispatcherGlib::processEvents (this=0x7f0a3c008560, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0aa4ad2b9b in QEventLoop::exec (this=this@entry=0x7f0a54ff8ae0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f0aa48fd5ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f0aa48fe698 in QThreadPrivate::start (arg=0xb489100) at thread/qthread_unix.cpp:342 #7 0x7f0aa301cefa in start_thread () from /lib64/libpthread.so.0 #8 0x7f0aa442c3bf in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7f0a4700 (LWP 28474)): #0 0x7f0aa43b29c7 in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7f0aa439ab2e in buffered_vfprintf () from /lib64/libc.so.6 #2 0x7f0aa4397a44 in __vfprintf_internal () from /lib64/libc.so.6 #3 0x7f0aa443a5cf in __fprintf_chk () from /lib64/libc.so.6 #4 0x7f0a984daf2e in event_logv_ () from /usr/lib64/libevent-2.1.so.7 #5 0x7f0a984ddb15 in event_warn () from /usr/lib64/libevent-2.1.so.7 #6 0x7f0a984df678 in ?? () from /usr/lib64/libevent-2.1.so.7 #7 0x7f0a984f0086 in event_base_loop () from /usr/lib64/libevent-2.1.so.7 #8 0x7f0a9d9236bd in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x00010077007c in ?? () #10 0x7f0a4fffe950 in ?? () #11 0x7f0a4fffe948 in ?? () #12 0x in ?? () Thread 19 (Thread 0x7f0a5cbba700 (LWP 28467)): #0 0x7f0aa441d4fc in read () from /lib64/libc.so.6 #1 0x7f0a961c20f1 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #2 0x7f0a980cda0e in pa_mainloop_prepare () from /usr/lib64/libpulse.so.0 #3 0x7f0a980ce4b0 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7f0a980ce570 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7f0a980dc439 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7f0a961efd78 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f0aa301cefa in start_thread () from /lib64/libpthread.so.0 #8 0x7f0aa442c3bf in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7f0a07428700 (LWP 17899)): #0 0x7f0a98fe849f in g_source_ref () from /usr/lib64/libglib-2.0.so.0 #1 0x7f0a98fe8548 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f0a98fe9c6f in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f0a98fea2a2 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f0a98fea41f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f0aa4b2ac0b in QEventDispatcherGlib::processEvents (this=0x7f0a0b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f0aa4ad2b9b in QEventLoop::exec (this=this@entry=0x7f0a07427ae0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #7 0x7f0aa48fd5ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #8 0x7f0aa48fe698 in QThreadPrivate::start (arg=0x79472a0) at thread/qthread_unix.cpp:342 #9 0x7f0aa301cefa in start_thread () from /lib64/libpthread.so.0 #10 0x7f0aa442c3bf in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f0a4cff9700 (LWP 17800)): #0 0x7f0aa3023795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0a9d91
[Akonadi] [Bug 418293] "filter account is missing" dialog does not show account names
https://bugs.kde.org/show_bug.cgi?id=418293 --- Comment #2 from Martin Koller --- Created attachment 126600 --> https://bugs.kde.org/attachment.cgi?id=126600&action=edit screenshot the forgotten one ;-) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418293] New: "filter account is missing" dialog does not show account names
https://bugs.kde.org/show_bug.cgi?id=418293 Bug ID: 418293 Summary: "filter account is missing" dialog does not show account names Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- SUMMARY After removing some accounts on starting akonadi I am presented with a dialog with the title "Select Account - Mail Filter Agent" and the text in it says "Filter account is missing. Please Select account..." (see attached screenshot) The problem here is that the dialog does not tell me the names of the accounts but instead only shows the type (e.g. I have 2 POP3 accounts, but all I see is two times the same text "POP3 E-Mail Server" in the "Account Name" column, so I can not chose the right one. SOFTWARE/OS VERSIONS Linux openSuse tumbleweed 20200226 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 416378] New: adding POP account does not use defined name
https://bugs.kde.org/show_bug.cgi?id=416378 Bug ID: 416378 Summary: adding POP account does not use defined name Product: kmail2 Version: 5.13.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- SUMMARY I'm adding a new POP3-account and give it a name. After pressing OK, the list of configured accounts still shows the generic "POP3 Account" string and not the name I gave it. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200115 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.1 Kernel Version: 5.4.10-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 15,5 GiB -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 414977] broken layout does no longer resize attendee list
https://bugs.kde.org/show_bug.cgi?id=414977 --- Comment #2 from Martin Koller --- Created attachment 124411 --> https://bugs.kde.org/attachment.cgi?id=124411&action=edit screenshot here you go. mentioned areas circled in red -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 414977] New: broken layout does no longer resize attendee list
https://bugs.kde.org/show_bug.cgi?id=414977 Bug ID: 414977 Summary: broken layout does no longer resize attendee list Product: korganizer Version: 5.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: incidence editors Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- SUMMARY Open any event in korganizer, select the attendee tab and resize the whole dialog. You'll see that the attendee list no longer resizes. Instead seeing more entries in the attendee table, just an empty area below the table will enlarge. Also, the name of the meeting organizer is cut (just part of the name is visible). SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20191203 KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 Kernel Version: 5.3.12-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 15,5 GiB of RAM -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 413921] New: crash on mail check
https://bugs.kde.org/show_bug.cgi?id=413921 Bug ID: 413921 Summary: crash on mail check Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Application: akonadiserver (5.12.2) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: new mail check was running, then the server crashed The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb48135d800 (LWP 9568))] Thread 39 (Thread 0x7fb3ecff9700 (LWP 14817)): #0 0x7fb48356e60c in read () from /lib64/libc.so.6 Thread 7 (Thread 0x7fb47d020700 (LWP 9576)): [KCrash Handler] #6 0x7fb483961619 in qHash (key=..., seed=888454470) at ../../include/QtCore/../../src/corelib/tools/qstring.h:239 #7 0x563b7224f79b in QHash::findNode (this=this@entry=0x563b73f7e968, akey=..., ahp=ahp@entry=0x0) at /usr/include/qt5/QtCore/qhash.h:928 #8 0x563b7224f80a in QHash::remove (this=this@entry=0x563b73f7e968, akey=...) at /usr/include/qt5/QtCore/qrefcount.h:102 #9 0x563b7224df12 in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x563b73f7e930, request=0x7fb430122390, errorMsg=...) at /usr/src/debug/akonadi-server-19.08.2-1.1.x86_64/src/server/storage/itemretrievalmanager.cpp:227 #10 0x7fb483b01638 in QtPrivate::QSlotObjectBase::call (a=0x7fb47d01f800, r=0x563b73f7e930, this=0x7fb46801f9d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #11 QMetaObject::activate (sender=0x7fb468015af0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3789 #12 0x563b72298b04 in Akonadi::Server::AbstractItemRetrievalJob::requestCompleted (this=this@entry=0x7fb468015af0, _t1=, _t2=...) at /usr/src/debug/akonadi-server-19.08.2-1.1.x86_64/build/src/server/libakonadiserver_autogen/5XLNPBDXWK/moc_itemretrievaljob.cpp:136 #13 0x563b7224feb3 in Akonadi::Server::ItemRetrievalJob::callFinished (this=0x7fb468015af0, watcher=) at /usr/include/qt5/QtCore/qchar.h:88 #14 0x7fb483b01638 in QtPrivate::QSlotObjectBase::call (a=0x7fb47d01f9c0, r=0x7fb468015af0, this=0x7fb4780254e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #15 QMetaObject::activate (sender=0x7fb468008280, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3789 #16 0x7fb483e5c93f in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /usr/lib64/libQt5DBus.so.5 #17 0x7fb483e5ca40 in ?? () from /usr/lib64/libQt5DBus.so.5 #18 0x7fb483b01eea in QObject::event (this=0x7fb468008280, e=) at kernel/qobject.cpp:1260 #19 0x7fb483ad654f in doNotify (event=0x7fb43017e550, receiver=0x7fb468008280) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:143 #20 QCoreApplication::notify (event=0x7fb43017e550, receiver=0x7fb468008280, this=) at kernel/qcoreapplication.cpp:1171 #21 QCoreApplication::notifyInternal2 (receiver=0x7fb468008280, event=0x7fb43017e550) at kernel/qcoreapplication.cpp:1095 #22 0x7fb483ad9208 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x563b73fc85d0) at kernel/qcoreapplication.cpp:1840 #23 0x7fb483b2d343 in postEventSourceDispatch (s=0x7fb4680047c0) at kernel/qeventdispatcher_glib.cpp:277 #24 0x7fb48209ad3d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #25 0x7fb48209caf0 in ?? () from /usr/lib64/libglib-2.0.so.0 #26 0x7fb48209cb2f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #27 0x7fb483b2c981 in QEventDispatcherGlib::processEvents (this=0x7fb468000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7fb483ad50db in QEventLoop::exec (this=this@entry=0x7fb47d01fda0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #29 0x7fb48390d021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #30 0x7fb48390e1a2 in QThreadPrivate::start (arg=0x563b73fc8500) at thread/qthread_unix.cpp:360 #31 0x7fb482cd8f2a in start_thread () from /lib64/libpthread.so.0 #32 0x7fb48357d4af in clone () from /lib64/libc.so.6 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 413631] auth failure goes offline but success not online again
https://bugs.kde.org/show_bug.cgi?id=413631 --- Comment #2 from Martin Koller --- I assume you could call ResourceBase::doSetOnline(true); when the re-auth succeeds. Another thing I seem to encounter: after the re-auth and the resource being offline, it does no longer react to a manual "check for email" - even if the resource is no longer offline. All I can do in that case is to kill and restart it. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 413631] New: auth failure goes offline but success not online again
https://bugs.kde.org/show_bug.cgi?id=413631 Bug ID: 413631 Summary: auth failure goes offline but success not online again Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: EWS Resource Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at CC: kri...@op.pl Target Milestone: --- SUMMARY sometimes the ews resource fails with the authentication and I see the following debug output: org.kde.pim.ews.client.request: Starting SyncFolderHierarchy request (folder: EwsId(Distinguished: msgfolderroot), state: 1sgz95w org.kde.pim.ews.client.proto: data KIO::TransferJob(0x150d230) "" org.kde.pim.ews.client.proto: response dumped to "/tmp/akonadi-ews-qzRmyGa/ews_xmldump_DyEEOSp.xml" org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 org.kde.pim.ews: requestAuthFailed - going offline org.kde.pim.ews.client: Starting OAuth2 authentication org.kde.pim.ews.client: Authentication succeeded The result is still the resource being offline, despite the success in authentication. It should go online again (or not offline in the first place). SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20191025 KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.7-1-default OS Type: 64-bit -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 413260] New: click on a mail on local maildir folder crashed akonadi server
https://bugs.kde.org/show_bug.cgi?id=413260 Bug ID: 413260 Summary: click on a mail on local maildir folder crashed akonadi server Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- SUMMARY I was just reading a mail in a local maildir folder when akonadi server crashed when I selected a new mail. EXPECTED RESULT no crash SOFTWARE/OS VERSIONS openSuse Tumbleweed 20191016 ADDITIONAL INFORMATION Application: Akonadi Server (akonadiserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2da5922900 (LWP 4319))] Thread 7 (Thread 0x7f2da15e4700 (LWP 4327)): [KCrash Handler] #6 0x7f2da7f8dabe in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x34003a) at /usr/include/c++/9/bits/atomic_base.h:413 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x34003a) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 #9 QtPrivate::RefCount::deref (this=0x34003a) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:66 #10 QString::operator= (this=this@entry=0x7f2d3c04bb48, other=...) at tools/qstring.cpp:2434 #11 0x55a366e28f01 in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x55a367c6dd80, request=0x7f2d3c04bb30, errorMsg=...) at /usr/src/debug/akonadi-server-19.08.2-1.1.x86_64/src/server/storage/itemretrievalmanager.cpp:224 #12 0x7f2da8102638 in QtPrivate::QSlotObjectBase::call (a=0x7f2da15e3700, r=0x55a367c6dd80, this=0x7f2d90019f20) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #13 QMetaObject::activate (sender=0x7f2d9000c180, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3789 #14 0x55a366e73b04 in Akonadi::Server::AbstractItemRetrievalJob::requestCompleted (this=this@entry=0x7f2d9000c180, _t1=, _t2=...) at /usr/src/debug/akonadi-server-19.08.2-1.1.x86_64/build/src/server/libakonadiserver_autogen/5XLNPBDXWK/moc_itemretrievaljob.cpp:136 #15 0x55a366e2aeb3 in Akonadi::Server::ItemRetrievalJob::callFinished (this=0x7f2d9000c180, watcher=) at /usr/include/qt5/QtCore/qchar.h:88 #16 0x7f2da8102638 in QtPrivate::QSlotObjectBase::call (a=0x7f2da15e38c0, r=0x7f2d9000c180, this=0x7f2d90005290) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #17 QMetaObject::activate (sender=0x7f2d90021ee0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3789 #18 0x7f2da845d93f in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /usr/lib64/libQt5DBus.so.5 #19 0x7f2da845da40 in ?? () from /usr/lib64/libQt5DBus.so.5 #20 0x7f2da8102eea in QObject::event (this=0x7f2d90021ee0, e=) at kernel/qobject.cpp:1260 #21 0x7f2da80d754f in doNotify (event=0x7f2d3c048610, receiver=0x7f2d90021ee0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:143 #22 QCoreApplication::notify (event=0x7f2d3c048610, receiver=0x7f2d90021ee0, this=) at kernel/qcoreapplication.cpp:1171 #23 QCoreApplication::notifyInternal2 (receiver=0x7f2d90021ee0, event=0x7f2d3c048610) at kernel/qcoreapplication.cpp:1095 #24 0x7f2da80da208 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55a367c59260) at kernel/qcoreapplication.cpp:1840 #25 0x7f2da812e343 in postEventSourceDispatch (s=0x7f2d90004bc0) at kernel/qeventdispatcher_glib.cpp:277 #26 0x7f2da668b6b3 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #27 0x7f2da668d460 in ?? () from /usr/lib64/libglib-2.0.so.0 #28 0x7f2da668d49f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #29 0x7f2da812d981 in QEventDispatcherGlib::processEvents (this=0x7f2d9b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #30 0x7f2da80d60db in QEventLoop::exec (this=this@entry=0x7f2da15e3ca0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #31 0x7f2da7f0e021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #32 0x7f2da7f0f1a2 in QThreadPrivate::start (arg=0x55a367c59190) at thread/qthread_unix.cpp:360 #33 0x7f2da72d9f2a in start_thread () from /lib64/libpthread.so.0 #34 0x7f2da7b7e4af in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f2da1de5700 (LWP 4326)): #0 0x7f2da7b73bdf in poll () from /lib64/libc.so.6 #1 0x7f2da668d3ce in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2da668d49f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2da812d99b in QEventDispatcherGlib::processEvents (this=0x7f2d74000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
[kmail2] [Bug 413022] New: decrypting mail (via filter) removes From/To mail headers
https://bugs.kde.org/show_bug.cgi?id=413022 Bug ID: 413022 Summary: decrypting mail (via filter) removes From/To mail headers Product: kmail2 Version: 5.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- SUMMARY I received a crypted mail. In then message list I right-click on that mail and select "copy decrypted mail to ..." some folder. The resulting decrypted copied mail no longer has a "From:" nor a "To:" Header. All other headers seem to be still there and with correct content SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSuse Tumbleweed 20191012 KDE Frameworks 5.62.0 Qt 5.13.1 (built against 5.13.1) The xcb windowing system -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412839] New: kmail crash when trying to decrypt a mail
https://bugs.kde.org/show_bug.cgi?id=412839 Bug ID: 412839 Summary: kmail crash when trying to decrypt a mail Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Application: kmail (5.12.1) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 4.12.14-lp150.12.73-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I clicked on the "decrypt" link inside the mail body and kmail crashed The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6db3bd4a80 (LWP 2589))] Thread 25 (Thread 0x7f6ca0d55700 (LWP 4845)): #0 0x7f6dc2f309ca in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f6dbc5d5486 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f6dbc5d5e53 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f6dbc5d5fd1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f6dbc58e141 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f6dbc590fdd in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f6dbc5916d4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f6dbc5d82c5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f6dc2f29f2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f6dc68fb4af in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f6d6e7fc700 (LWP 4075)): #0 0x7f6dc2f309ca in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f6dbc5d5486 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f6dbc5d5e53 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f6dbc5d5fd1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f6dbc58e141 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f6dbc59132b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f6dbc5916d4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f6dbc5d82c5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f6dc2f29f2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f6dc68fb4af in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f6c86ffd700 (LWP 31788)): #0 0x7f6dc24b31b9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f6dc2500cca in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f6dc25012fb in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f6dc250149f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f6dc54ab99b in QEventDispatcherGlib::processEvents (this=0x7f6c7c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f6dc54540db in QEventLoop::exec (this=this@entry=0x7f6c86ffcb20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f6dc528c021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f6dc528d1a2 in QThreadPrivate::start (arg=0x561ecaf50a20) at thread/qthread_unix.cpp:360 #8 0x7f6dc2f29f2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f6dc68fb4af in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f6c87fff700 (LWP 31772)): #0 0x7f6dc6881ca7 in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7f6dc6869b0e in buffered_vfprintf () from /lib64/libc.so.6 #2 0x7f6dc6866a24 in __vfprintf_internal () from /lib64/libc.so.6 #3 0x7f6dc690989f in __fprintf_chk () from /lib64/libc.so.6 #4 0x7f6db8576d3e in event_logv_ () from /usr/lib64/libevent-2.1.so.7 #5 0x7f6db8579925 in event_warn () from /usr/lib64/libevent-2.1.so.7 #6 0x7f6db857b488 in ?? () from /usr/lib64/libevent-2.1.so.7 #7 0x7f6db858bdf5 in event_base_loop () from /usr/lib64/libevent-2.1.so.7 #8 0x7f6dbc5dc17a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f6dbc5682a7 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f6dbc59f44f in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7f6dbc5d82c5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7f6dc2f29f2a in start_thread () from /lib64/libpthread.so.0 #13 0x7f6dc68fb4af in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7f6d6d7fa700 (LWP 14830)): #0 0x7f6dc68f0bdf in poll () from /lib64/libc.so.6 #1 0x7f6db8b344f2 in ?? () from /usr/lib64/libpulse.so.0 #2 0x7f6db8b25e39 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #3 0x7f6db8b264bf in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7f6db8b26570 in pa_mainloop_run () f
[akregator] [Bug 412209] New: fails to parse date - date field display is empty
https://bugs.kde.org/show_bug.cgi?id=412209 Bug ID: 412209 Summary: fails to parse date - date field display is empty Product: akregator Version: GIT (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: feed parser Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- SUMMARY I'm now running akregator built from master (19e86d1b4fdcfff81e8b38615b5981c7384b1e95) and new feeds no longer display any date. The date field is simply empty. When I quit akregator and start it again, the former empty date field now shows the unix-0-time (1.1.1970 00:00) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 411907] New: server crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411907 Bug ID: 411907 Summary: server crashes on startup Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- SUMMARY whenever I login, akonadiserver crashes. So I tried it manually. Stopped everything akonadi realted (akonadictl stop; killed mysqld), then did a "akonadictl start". This is the result (crashes; can be reproduced every time): org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: DB initializer done Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadicontrol: Akonadi server is now operational. org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f93ac005180) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f93ac00f4d0) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f93ac013120) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f93ac014860) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f93ac015f00) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f93ac005180) identified as "ItemMonitorMonitor - 93886007149376" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f93ac00f4d0) identified as "ItemMonitorMonitor - 93886007334320" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f93ac013120) identified as "kaddressbook-182605794 - 93886007135424" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f93ac014860) identified as "KAddressBook::GlobalContactSession - 93886007689872" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f93ac015f00) identified as "ETMCalendarMonitor - 94393032152576" org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f93ac0702e0) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f93ac0702e0) identified as "AgentBaseChangeRecorder - 94831215899632" org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f93ac071910) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f93ac03dc50) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f93ac03e250) ) org.kde.pim.akonadiserver: Cannot connect to agent instance with identifier 'akonadi_ews_resource_2', error message: '' org.kde.pim.akonadiserver: ItemRetrievalJob for request 0x7f938807db20 finished with error: "Unable to contact resource" org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f93ac072ab0) ) org.kde.pim.akonadiserver: Cannot connect to agent instance with identifier 'akonadi_ews_resource_2', error message: '' org.kde.pim.akonadiserver: ItemRetrievalJob for request 0x7f9388037be0 finished with error: "Unable to contact resource" org.kde.pim.akonadiserver: Cannot connect to agent instance with identifier 'akonadi_ews_resource_2', error message: '' org.kde.pim.akonadiserver: ItemRetrievalJob for request 0x7f9388072070 finished with error: "Unable to contact resource" KCrash: Application 'akonadiserver' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 15 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 12 and type 'Read', disabling... org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/run/user/1000/akonadi/akonadiserver-cmd.socket" org.kde.pim.akonadiserver: Database error: Cannot open database. org.kde.pim.akonadiserver: Last driver error: "QMYSQL: Unable to open database 'akonadi'" org.kde.pim.akonadiserver: Last database error: "Lost connection to MySQL server during query" QSqlQuery::exec: database not open Unable to start Dr. Konqi I'm on openSuse leap 15.0, KDE 19.08 KDE Frameworks 5.61.0 Qt 5.13.0 (built against 5.13.0) The xcb windowing system -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 411777] New: import of vcs fails, still says success
https://bugs.kde.org/show_bug.cgi?id=411777 Bug ID: 411777 Summary: import of vcs fails, still says success Product: korganizer Version: 5.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: import/export Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Created attachment 122574 --> https://bugs.kde.org/attachment.cgi?id=122574&action=edit test vcs SUMMARY A webpage produced the attached vcs file. When importing it, korganizer shows a blue bar saying "1 incidence was successfully imported" but in konsole I see the log output: Incidence has empty UID. id= 336260 ; summary= "Test" Please fix it. Ignoring this incidence. org.kde.pim.kcalcore: The incidence didn't have any UID! Report a bug to the application that generated this file. OBSERVED RESULT The incidence is not shown in korganizer EXPECTED RESULT Show imported incidence. When an import finds a missing UID, it should simply generate one and import the file, instead of just ignoring this file. A user can not control what content a web server produces and there is zero chance that a user can convince any company to fix the producer. Please be more forgiving on broken input. SOFTWARE/OS VERSIONS KDE Frameworks 5.61.0 Qt 5.13.0 (built against 5.13.0) The xcb windowing system openSuse Leap 15.0 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 411378] New: dav (nextcloud) resource crashed on restart
https://bugs.kde.org/show_bug.cgi?id=411378 Bug ID: 411378 Summary: dav (nextcloud) resource crashed on restart Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Application: akonadi_davgroupware_resource (5.12.0) Qt Version: 5.13.0 Frameworks Version: 5.61.0 Operating System: Linux 4.12.14-lp150.12.70-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: The dav groupware resource (for a nextcloud server) showed "could not connect to host" ... status, so I decided to do a restart (from akonadiconsole), which led to the crash -- Backtrace: Application: Nextcloud (akonadi_davgroupware_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5a918eef40 (LWP 17821))] Thread 4 (Thread 0x7f5a677fe700 (LWP 17848)): #0 0x7f5a8c46c1db in poll () from /lib64/libc.so.6 #1 0x7f5a85895229 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5a8589533c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f5a8cfd251b in QEventDispatcherGlib::processEvents (this=0x7f5a58000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5a8cf72baa in QEventLoop::exec (this=this@entry=0x7f5a677fdcb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f5a8cd8edba in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f5a8cd90562 in QThreadPrivate::start (arg=0x559cb2ba3c20) at thread/qthread_unix.cpp:360 #7 0x7f5a88029569 in start_thread () from /lib64/libpthread.so.0 #8 0x7f5a8c476a2f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f5a67fff700 (LWP 17843)): #0 0x7f5a858db059 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f5a85895328 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5a8cfd251b in QEventDispatcherGlib::processEvents (this=0x7f5a6b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7f5a8cf72baa in QEventLoop::exec (this=this@entry=0x7f5a67ffecb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #4 0x7f5a8cd8edba in QThread::exec (this=) at thread/qthread.cpp:531 #5 0x7f5a8cd90562 in QThreadPrivate::start (arg=0x559cb2b0f7a0) at thread/qthread_unix.cpp:360 #6 0x7f5a88029569 in start_thread () from /lib64/libpthread.so.0 #7 0x7f5a8c476a2f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f5a6cf22700 (LWP 17839)): #0 0x7f5a8c46c1db in poll () from /lib64/libc.so.6 #1 0x7f5a85895229 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5a8589533c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f5a8cfd251b in QEventDispatcherGlib::processEvents (this=0x7f5a68000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5a8cf72baa in QEventLoop::exec (this=this@entry=0x7f5a6cf21c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f5a8cd8edba in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f5a8e373e35 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f5a8cd90562 in QThreadPrivate::start (arg=0x7f5a8e5ebd80) at thread/qthread_unix.cpp:360 #8 0x7f5a88029569 in start_thread () from /lib64/libpthread.so.0 #9 0x7f5a8c476a2f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5a918eef40 (LWP 17821)): [KCrash Handler] #6 QScopedPointer >::operator-> (this=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 #7 qGetPtrHelper > > (ptr=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1055 #8 QSettings::d_func (this=) at io/qsettings.h:72 #9 QSettings::setValue (this=this@entry=0x0, key=..., value=...) at io/qsettings.cpp:3276 #10 0x7f5a9122837d in Akonadi::AgentBase::setOnline (this=0x7ffd0f40, state=false) at /usr/src/debug/akonadi-server-19.08.0-lp150.198.1.x86_64/src/agentbase/agentbase.cpp:1031 #11 0x7f5a9125115c in Akonadi__StatusAdaptor::setOnline (state=, this=0x559cb2b3bac0) at /usr/src/debug/akonadi-server-19.08.0-lp150.198.1.x86_64/build/src/agentbase/statusadaptor.cpp:51 #12 Akonadi__StatusAdaptor::qt_static_metacall (_o=_o@entry=0x559cb2b3bac0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=8, _a=_a@entry=0x7ffd06c0) at /usr/src/debug/akonadi-server-19.08.0-lp150.198.1.x86_64/build/src/agentbase/statusadaptor.moc:154 #13 0x7f5a912513f5 in Akonadi__StatusAdaptor::qt_metacall (this=0x559cb2b3bac0, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7ffd06c0) at /usr/src/debug/akonadi-server-19.08.0-lp150.198.1.x86_64/build/src/agentbase/statusadaptor.moc:238 #14 0x7f5a8e37ee88 in ?? () from /usr/lib64/l
[Akonadi] [Bug 411054] New: starting kaddressbook crashes akonadiserver
https://bugs.kde.org/show_bug.cgi?id=411054 Bug ID: 411054 Summary: starting kaddressbook crashes akonadiserver Product: Akonadi Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Application: akonadiserver (5.12.0) Qt Version: 5.13.0 Frameworks Version: 5.61.0 Operating System: Linux 4.12.14-lp150.12.70-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: Sometimes when I start kaddressbook, akonadiserver crashes. I use a local addressbook, a nextcloud resource and an MS-EWS resource The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f50ff0a6d80 (LWP 2710))] Thread 42 - 8 snipped Thread 7 (Thread 0x7f50f148f700 (LWP 3090)): [KCrash Handler] #6 0x7f50fcc59160 in raise () from /lib64/libc.so.6 #7 0x7f50fcc5a741 in abort () from /lib64/libc.so.6 #8 0x7f50fcc9c4a7 in __libc_message () from /lib64/libc.so.6 #9 0x7f50fcca2cc3 in malloc_printerr () from /lib64/libc.so.6 #10 0x7f50fcca45c9 in _int_free () from /lib64/libc.so.6 #11 0x5654af97f9ff in QTypedArrayData::deallocate (data=) at /usr/include/qt5/QtCore/qarraydata.h:239 #12 QString::~QString (this=0x7f50ec0246b0, __in_chrg=) at /usr/include/qt5/QtCore/qstring.h:1133 #13 QHashNode >::~QHashNode (this=, __in_chrg=) at /usr/include/qt5/QtCore/qhash.h:149 #14 QHash >::deleteNode2 (node=0x7f50ec0246a0) at /usr/include/qt5/QtCore/qhash.h:547 #15 QHash >::deleteNode (node=0x7f50ec0246a0, this=0x5654b0a8a970) at /usr/include/qt5/QtCore/qhash.h:537 #16 QHash >::erase (this=this@entry=0x5654b0a8a970, it=..., it@entry=...) at /usr/include/qt5/QtCore/qhash.h:874 #17 0x5654af97da8f in QHash >::erase (it=..., this=0x5654b0a8a970) at /usr/include/qt5/QtCore/qhash.h:477 #18 Akonadi::Server::ItemRetrievalManager::processRequest (this=0x5654b0a8a940) at /usr/src/debug/akonadi-server-19.08.0-lp150.198.1.x86_64/src/server/storage/itemretrievalmanager.cpp:184 #19 0x7f50fd84ae42 in QObject::event (this=0x5654b0a8a940, e=) at kernel/qobject.cpp:1260 #20 0x7f50fd819971 in doNotify (event=0x7f50e0012c00, receiver=0x5654b0a8a940) at kernel/qcoreapplication.cpp:1155 #21 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1141 #22 QCoreApplication::notifyInternal2 (receiver=0x5654b0a8a940, event=0x7f50e0012c00) at kernel/qcoreapplication.cpp:1065 #23 0x7f50fd819b5e in QCoreApplication::sendEvent (receiver=, event=event@entry=0x7f50e0012c00) at kernel/qcoreapplication.cpp:1460 #24 0x7f50fd81c2a7 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x5654b0a8ab00) at kernel/qcoreapplication.cpp:1810 #25 0x7f50fd81c838 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1664 #26 0x7f50fd877ee3 in postEventSourceDispatch (s=0x7f50d8004b90) at kernel/qeventdispatcher_glib.cpp:277 #27 0x7f50f955af07 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x7f50f955b2b0 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x7f50f955b33c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x7f50fd8774ff in QEventDispatcherGlib::processEvents (this=0x7f50d8000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #31 0x7f50fd817baa in QEventLoop::exec (this=this@entry=0x7f50f148ecb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #32 0x7f50fd633dba in QThread::exec (this=) at thread/qthread.cpp:531 #33 0x7f50fd635562 in QThreadPrivate::start (arg=0x5654b0ab4510) at thread/qthread_unix.cpp:360 #34 0x7f50fba79569 in start_thread () from /lib64/libpthread.so.0 #35 0x7f50fcd1ba2f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f50f1c90700 (LWP 3089)): #0 0x7f50fcd0ccd8 in read () from /lib64/libc.so.6 #1 0x7f50f959fd20 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f50f955ad38 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f50f955b1d0 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f50f955b33c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f50fd87751b in QEventDispatcherGlib::processEvents (this=0x7f50d4000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f50fd817baa in QEventLoop::exec (this=this@entry=0x7f50f1c8fcb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f50fd633dba in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f50fd635562 in QThreadPrivate::start (arg=0x5654b0ab9d50) at
[kmail2] [Bug 410694] New: can no longer decline invitation
https://bugs.kde.org/show_bug.cgi?id=410694 Bug ID: 410694 Summary: can no longer decline invitation Product: kmail2 Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- SUMMARY I receive an invitation email and kmail shows the different buttons like "accept", "tentative", "decline", ... When I click "decline" I get a dialog to enter some text, but after clicking OK, I get an error dialog: "Error: Could not find incidence to delete." SOFTWARE/OS VERSIONS openSuse 15.0 KMail Version 5.11.80 beta KDE Frameworks 5.60.0 Qt 5.13.0 (built against 5.13.0) The xcb windowing system -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 410586] New: crash of akonadiserver when kaddressbook starts
https://bugs.kde.org/show_bug.cgi?id=410586 Bug ID: 410586 Summary: crash of akonadiserver when kaddressbook starts Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Application: akonadiserver (5.11.80) Qt Version: 5.13.0 Frameworks Version: 5.60.0 Operating System: Linux 4.12.14-lp150.12.67-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: started kaddressbook -> akonadiserver crashes. akonadictl stop then again started kaddressbook which tried to start akonadiserver which immediately crashed again. However after the next restart of akonadiserver it now runs and also kaddressbook can be used. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd8a4b9ad80 (LWP 18924))] Thread 12 (Thread 0x7fd8577fe700 (LWP 19001)): #0 0x7fd8a1573c3b in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd8a3130436 in QWaitConditionPrivate::wait_relative (this=0x7fd88c055f70, deadline=...) at thread/qwaitcondition_unix.cpp:136 #2 QWaitConditionPrivate::wait (deadline=..., this=0x7fd88c055f70) at thread/qwaitcondition_unix.cpp:144 #3 QWaitCondition::wait (this=, mutex=0x7fd88c0034b0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #4 0x7fd8a3130796 in QWaitCondition::wait (this=this@entry=0x7fd88c055db0, mutex=mutex@entry=0x7fd88c0034b0, time=) at thread/qwaitcondition_unix.cpp:209 #5 0x7fd8a312d1dd in QThreadPoolThread::run (this=0x7fd88c055da0) at thread/qthreadpool.cpp:139 #6 0x7fd8a3129562 in QThreadPrivate::start (arg=0x7fd88c055da0) at thread/qthread_unix.cpp:360 #7 0x7fd8a156d569 in start_thread () from /lib64/libpthread.so.0 #8 0x7fd8a280fa2f in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7fd857fff700 (LWP 19000)): #0 0x7fd8a1573c3b in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd8a3130436 in QWaitConditionPrivate::wait_relative (this=0x7fd88c055b00, deadline=...) at thread/qwaitcondition_unix.cpp:136 #2 QWaitConditionPrivate::wait (deadline=..., this=0x7fd88c055b00) at thread/qwaitcondition_unix.cpp:144 #3 QWaitCondition::wait (this=, mutex=0x7fd88c0034b0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #4 0x7fd8a3130796 in QWaitCondition::wait (this=this@entry=0x7fd88c0559b0, mutex=mutex@entry=0x7fd88c0034b0, time=) at thread/qwaitcondition_unix.cpp:209 #5 0x7fd8a312d1dd in QThreadPoolThread::run (this=0x7fd88c0559a0) at thread/qthreadpool.cpp:139 #6 0x7fd8a3129562 in QThreadPrivate::start (arg=0x7fd88c0559a0) at thread/qthread_unix.cpp:360 #7 0x7fd8a156d569 in start_thread () from /lib64/libpthread.so.0 #8 0x7fd8a280fa2f in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7fd86cb57700 (LWP 18999)): #0 0x7fd8a1573c3b in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd8a3130436 in QWaitConditionPrivate::wait_relative (this=0x7fd88c0126a0, deadline=...) at thread/qwaitcondition_unix.cpp:136 #2 QWaitConditionPrivate::wait (deadline=..., this=0x7fd88c0126a0) at thread/qwaitcondition_unix.cpp:144 #3 QWaitCondition::wait (this=, mutex=0x7fd88c0034b0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #4 0x7fd8a3130796 in QWaitCondition::wait (this=this@entry=0x7fd88c035540, mutex=mutex@entry=0x7fd88c0034b0, time=) at thread/qwaitcondition_unix.cpp:209 #5 0x7fd8a312d1dd in QThreadPoolThread::run (this=0x7fd88c035530) at thread/qthreadpool.cpp:139 #6 0x7fd8a3129562 in QThreadPrivate::start (arg=0x7fd88c035530) at thread/qthread_unix.cpp:360 #7 0x7fd8a156d569 in start_thread () from /lib64/libpthread.so.0 #8 0x7fd8a280fa2f in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fd86d358700 (LWP 18998)): #0 0x7fd8a1573c3b in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd8a3130436 in QWaitConditionPrivate::wait_relative (this=0x7fd88c014670, deadline=...) at thread/qwaitcondition_unix.cpp:136 #2 QWaitConditionPrivate::wait (deadline=..., this=0x7fd88c014670) at thread/qwaitcondition_unix.cpp:144 #3 QWaitCondition::wait (this=, mutex=0x7fd88c0034b0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #4 0x7fd8a3130796 in QWaitCondition::wait (this=this@entry=0x7fd88c0352e0, mutex=mutex@entry=0x7fd88c0034b0, time=) at thread/qwaitcondition_unix.cpp:209 #5 0x7fd8a312d1dd in QThreadPoolThread::run (this=0x7fd88c0352d0) at thread/qthreadpool.cpp:139 #6 0x7fd8a3129562 in QThreadPrivate::start (arg=0x7f
[Akonadi] [Bug 409515] sometimes crashes when fetching mail
https://bugs.kde.org/show_bug.cgi?id=409515 --- Comment #3 from Martin Koller --- Just SSL/TLS, nothing else -- You are receiving this mail because: You are the assignee for the bug.
[korgac] [Bug 379026] reminder shows dialog for past events
https://bugs.kde.org/show_bug.cgi?id=379026 --- Comment #5 from Martin Koller --- On Mittwoch, 17. Juli 2019 17:24:02 CEST you wrote: > https://bugs.kde.org/show_bug.cgi?id=379026 > > --- Comment #3 from Filipus Klutiero --- > Martin, did the problem happen after? Does is still happen now? I will monitor it. A quick and simple test did not show the problem. -- You are receiving this mail because: You are the assignee for the bug.
[korgac] [Bug 379026] reminder shows dialog for past events
https://bugs.kde.org/show_bug.cgi?id=379026 --- Comment #2 from Martin Koller --- since this is over 2 years ago, I can't remember -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409789] New: crash on manually applying on many mails
https://bugs.kde.org/show_bug.cgi?id=409789 Bug ID: 409789 Summary: crash on manually applying on many mails Product: Akonadi Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Mail Filter Agent Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- SUMMARY Selected about 200 mails, hit CTRL+J -> crash Application: akonadi_mailfilter_agent (akonadi_mailfilter_agent), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f55290c0fc0 (LWP 3872))] Thread 6 (Thread 0x7f54e615b700 (LWP 4168)): #0 0x7f5523cbb0bb in poll () from /lib64/libc.so.6 #1 0x7f5518dff229 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5518dff33c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f552482151b in QEventDispatcherGlib::processEvents (this=0x7f54d8000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f55247c1baa in QEventLoop::exec (this=this@entry=0x7f54e615abf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f55245dddba in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f55245df562 in QThreadPrivate::start (arg=0x557e3b6b0fe0) at thread/qthread_unix.cpp:360 #7 0x7f5527f40569 in start_thread () from /lib64/libpthread.so.0 #8 0x7f5523cc585f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f54e757c700 (LWP 4017)): #0 0x7f5527f49ea8 in read () from /lib64/libpthread.so.0 #1 0x7f5518e43d20 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5518dfed38 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f5518dff1d0 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f5518dff33c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f552482151b in QEventDispatcherGlib::processEvents (this=0x7f54d4000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f55247c1baa in QEventLoop::exec (this=this@entry=0x7f54e757bbf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f55245dddba in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f55245df562 in QThreadPrivate::start (arg=0x557e3a9367c0) at thread/qthread_unix.cpp:360 #9 0x7f5527f40569 in start_thread () from /lib64/libpthread.so.0 #10 0x7f5523cc585f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f54e7d7d700 (LWP 3970)): #0 0x7f5527f47c10 in pthread_getspecific () from /lib64/libpthread.so.0 #1 0x7f5518e27050 in g_thread_self () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5518dff32d in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f552482151b in QEventDispatcherGlib::processEvents (this=0x7f54dc000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f55247c1baa in QEventLoop::exec (this=this@entry=0x7f54e7d7cbf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f55245dddba in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f55245df562 in QThreadPrivate::start (arg=0x557e3a4fcf40) at thread/qthread_unix.cpp:360 #7 0x7f5527f40569 in start_thread () from /lib64/libpthread.so.0 #8 0x7f5523cc585f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f54e8800700 (LWP 3967)): #0 0x7f5518dff0c4 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f5518dff33c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #2 0x7f552482151b in QEventDispatcherGlib::processEvents (this=0x7f54eb10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7f55247c1baa in QEventLoop::exec (this=this@entry=0x7f54e87ffbc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #4 0x7f55245dddba in QThread::exec (this=) at thread/qthread.cpp:531 #5 0x7f5524c98e35 in ?? () from /usr/lib64/libQt5DBus.so.5 #6 0x7f55245df562 in QThreadPrivate::start (arg=0x7f5524f10d80) at thread/qthread_unix.cpp:360 #7 0x7f5527f40569 in start_thread () from /lib64/libpthread.so.0 #8 0x7f5523cc585f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f54f65ee700 (LWP 3942)): #0 0x7f5523cbb0bb in poll () from /lib64/libc.so.6 #1 0x7f551b38a387 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f551b38bfba in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f54f8956898 in QXcbEventQueue::run (this=0x557e3a4eda40) at qxcbeventqueue.cpp:228 #4 0x7f55245df562 in QThreadPrivate::start (arg=0x557e3a4eda40) at thread/qthread_unix.cpp:360 #5 0x7f5527f40569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f5523cc585f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f55290c0fc0 (LWP 3872)): [KCrash Handler] #6 0x7f5523c03120 in raise () from /lib64/libc.so.6 #7 0x7f5523c04701 in abort () from /lib64/libc.so.6 #8 0x7f5524232e83 in ?? () from /usr/lib64/libstdc++.so.6 #9
[Akonadi] [Bug 409621] New: new calendar folder not shown on server
https://bugs.kde.org/show_bug.cgi?id=409621 Bug ID: 409621 Summary: new calendar folder not shown on server Product: Akonadi Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- SUMMARY I have a DAV resource for a nextcloud server, which already has 3 calendar folders. In korganizer I now add a new one, which I can use and add events to, but when I view the same data with the web interface of nextcloud, I do not see this new calendar folder. Also I can not see the new folder on my Android phones calendar application - only the existing 3 older ones are there. I already did "akonadictl restart" - same result. Checking the entries with akonadiconsole shows me that none of the new events has a remote id. The sync of the new folder is not done at all it seems. SOFTWARE/OS VERSIONS openSuse 15.0 KOrganizer Version 5.11.2 KDE Frameworks 5.59.0 Qt 5.13.0 (built against 5.13.0) The xcb windowing system -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 409618] time scale not visible in side-by-side view
https://bugs.kde.org/show_bug.cgi?id=409618 Martin Koller changed: What|Removed |Added Summary|time scal not visible in|time scale not visible in |side-by-side view |side-by-side view -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 409618] New: time scal not visible in side-by-side view
https://bugs.kde.org/show_bug.cgi?id=409618 Bug ID: 409618 Summary: time scal not visible in side-by-side view Product: korganizer Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: agendaview (weekview) Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- SUMMARY When viewing calendars with the side-by-side setting, the vertical time scale on the left side is not shown, which makes planning a new event rather tricky. EXPECTED RESULT always show the time scale SOFTWARE/OS VERSIONS KOrganizer Version 5.11.2 KDE Frameworks 5.59.0 Qt 5.13.0 (built against 5.13.0) The xcb windowing system -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409519] New: ews resource does not react on restart request
https://bugs.kde.org/show_bug.cgi?id=409519 Bug ID: 409519 Summary: ews resource does not react on restart request Product: Akonadi Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: EWS Resource Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at CC: kri...@op.pl Target Milestone: --- SUMMARY Using the kmail settings dialog, I click on a already configured and running ews resource, then I click on "restart" but the ews process keeps running and will not be restarted. Comparing this to a POP resource I see that restarting the POP resource works. SOFTWARE/OS VERSIONS openSuse Leap 15.0 KMail Version 5.11.2 KDE Frameworks 5.59.0 Qt 5.13.0 (built against 5.13.0) The xcb windowing system -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409515] New: sometimes crashes when fetching mail
https://bugs.kde.org/show_bug.cgi?id=409515 Bug ID: 409515 Summary: sometimes crashes when fetching mail Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: POP3 Resource Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at CC: aa...@kde.org Target Milestone: --- SUMMARY Not much to say more than the title. It usually works, but sometimes crashes. Application: akonadi_pop3_resource (akonadi_pop3_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f877983ed80 (LWP 22271))] Thread 5 (Thread 0x7f87574a5700 (LWP 22404)): #0 0x7f87759540bb in poll () from /lib64/libc.so.6 #1 0x7f8770550229 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f877055033c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f87764ba51b in QEventDispatcherGlib::processEvents (this=0x7f874c000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f877645abaa in QEventLoop::exec (this=this@entry=0x7f87574a4cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f8776276dba in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f8776278562 in QThreadPrivate::start (arg=0x55a014a129e0) at thread/qthread_unix.cpp:360 #7 0x7f8772156569 in start_thread () from /lib64/libpthread.so.0 #8 0x7f877595e85f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f8757ca6700 (LWP 22347)): #0 0x7f87759540bb in poll () from /lib64/libc.so.6 #1 0x7f8770550229 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f877055033c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f87764ba51b in QEventDispatcherGlib::processEvents (this=0x7f8748000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f877645abaa in QEventLoop::exec (this=this@entry=0x7f8757ca5cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f8776276dba in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f8776278562 in QThreadPrivate::start (arg=0x55a014ab99e0) at thread/qthread_unix.cpp:360 #7 0x7f8772156569 in start_thread () from /lib64/libpthread.so.0 #8 0x7f877595e85f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f87586f2700 (LWP 22340)): #0 0x7f87764b8c8a in QTimerInfoList::timerWait (this=0x7f8750004ce0, tm=...) at kernel/qtimerinfo_unix.cpp:413 #1 0x7f87764ba27e in timerSourcePrepareHelper (timeout=0x7f87586f1ab4, src=) at kernel/qeventdispatcher_glib.cpp:133 #2 timerSourcePrepare (source=, timeout=0x7f87586f1ab4) at kernel/qeventdispatcher_glib.cpp:166 #3 0x7f877054f789 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #4 0x7f877055015b in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f877055033c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x7f87764ba51b in QEventDispatcherGlib::processEvents (this=0x7f875b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f877645abaa in QEventLoop::exec (this=this@entry=0x7f87586f1c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #8 0x7f8776276dba in QThread::exec (this=) at thread/qthread.cpp:531 #9 0x7f8a2e35 in ?? () from /usr/lib64/libQt5DBus.so.5 #10 0x7f8776278562 in QThreadPrivate::start (arg=0x7f8777a1ad80) at thread/qthread_unix.cpp:360 #11 0x7f8772156569 in start_thread () from /lib64/libpthread.so.0 #12 0x7f877595e85f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f8765487700 (LWP 22301)): #0 0x7f87759540bb in poll () from /lib64/libc.so.6 #1 0x7f876def6387 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f876def7fba in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f876827b898 in QXcbEventQueue::run (this=0x55a01486ecc0) at qxcbeventqueue.cpp:228 #4 0x7f8776278562 in QThreadPrivate::start (arg=0x55a01486ecc0) at thread/qthread_unix.cpp:360 #5 0x7f8772156569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f877595e85f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f877983ed80 (LWP 22271)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x20003) at /usr/include/c++/7/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x20003) at /usr/include/qt5/QtCore/qbasicatomic.h:103 #9 QWeakPointer::data (this=0x55a0149e3860) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:569 #10 QPointer::data (this=0x55a0149e3860) at /usr/include/qt5/QtCore/qpointer.h:86 #11 QPointer::operator KIO::Slave* (this=0x55a0149e3860) at /usr/include/qt5/QtCore/qpointer.h:92 #12 POPSession::getSlave (this=0x55a0149e3850) at /usr/src/debug/kdepim-runtime-19.04.2-lp150.174.3.x86_64/resource
[kmail2] [Bug 409487] New: diff view does not decode UTF8 characters
https://bugs.kde.org/show_bug.cgi?id=409487 Bug ID: 409487 Summary: diff view does not decode UTF8 characters Product: kmail2 Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- SUMMARY I got an email with a diff attachment, which is nicely shown in the message view area below the message list. However UTF-8 encoded characters are not decoded and shown correctly, instead e.g. german Umlauts are displayed as 2 charcters SOFTWARE/OS VERSIONS openSuse Leap 15.0 KDE Frameworks 5.59.0 Qt 5.13.0 (built against 5.13.0) The xcb windowing system -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409383] New: akonadi_davgroupware_resource always crashes on startup
https://bugs.kde.org/show_bug.cgi?id=409383 Bug ID: 409383 Summary: akonadi_davgroupware_resource always crashes on startup Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- On openSuse Leap 15.0 with KDE Frameworks 5.59.0 Qt 5.13.0 (built against 5.13.0) immediately when starting akonadi (e.g. on login or manually "aconadictl start") the /usr/bin/akonadi_davgroupware_resource crashes with the following backtrace. The server for the dav_groupware is a nextcloud server, syncing calendar and contacts. It worked until recently with KDE 17.04 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 0x7f53fbb7e900 (LWP 28235))] Thread 5 (Thread 0x7f53d5d26700 (LWP 28241)): #0 0x7f53f670b7da in recv () from /lib64/libc.so.6 #1 0x7f53f3f9ddec in ?? () from /usr/lib64/libQt5Network.so.5 #2 0x7f53f3f8e4a5 in ?? () from /usr/lib64/libQt5Network.so.5 #3 0x7f53f3f8ecf4 in QNetworkInterface::allInterfaces() () from /usr/lib64/libQt5Network.so.5 #4 0x7f53d50d1b96 in ?? () from /usr/lib64/qt5/plugins/bearer/libqgenericbearer.so #5 0x7f53f7219bc5 in QMetaMethod::invoke (this=this@entry=0x7f53d5d25320, object=object@entry=0x56499297b810, connectionType=Qt::DirectConnection, connectionType@entry=Qt::AutoConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:2301 #6 0x7f53f721bb18 in QMetaObject::invokeMethod (obj=0x56499297b810, member=0x7f53f4013dc4 "requestUpdate", type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1515 #7 0x7f53f3f7bd0b in QNetworkConfigurationManagerPrivate::pollEngines() () from /usr/lib64/libQt5Network.so.5 #8 0x7f53f40082c5 in ?? () from /usr/lib64/libQt5Network.so.5 #9 0x7f53f72392e5 in QMetaObject::activate (sender=sender@entry=0x7f53cc050420, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=, argv@entry=0x7f53d5d258f0) at kernel/qobject.cpp:3807 #10 0x7f53f72399a7 in QMetaObject::activate (sender=sender@entry=0x7f53cc050420, m=m@entry=0x7f53f76beb60 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f53d5d258f0) at kernel/qobject.cpp:3658 #11 0x7f53f7245fa7 in QTimer::timeout (this=this@entry=0x7f53cc050420, _t1=...) at .moc/moc_qtimer.cpp:205 #12 0x7f53f7246308 in QTimer::timerEvent (this=0x7f53cc050420, e=) at kernel/qtimer.cpp:255 #13 0x7f53f7239dfb in QObject::event (this=0x7f53cc050420, e=) at kernel/qobject.cpp:1282 #14 0x7f53f7208971 in doNotify (event=0x7f53d5d25a60, receiver=0x7f53cc050420) at kernel/qcoreapplication.cpp:1155 #15 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1141 #16 QCoreApplication::notifyInternal2 (receiver=0x7f53cc050420, event=0x7f53d5d25a60) at kernel/qcoreapplication.cpp:1065 #17 0x7f53f7265989 in QTimerInfoList::activateTimers (this=0x7f53cc004ce0) at kernel/qtimerinfo_unix.cpp:643 #18 0x7f53f7266151 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #19 0x7f53efb1ef07 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #20 0x7f53efb1f2b0 in ?? () from /usr/lib64/libglib-2.0.so.0 #21 0x7f53efb1f33c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #22 0x7f53f726651b in QEventDispatcherGlib::processEvents (this=0x7f53cc000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #23 0x7f53f7206baa in QEventLoop::exec (this=this@entry=0x7f53d5d25cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #24 0x7f53f7022dba in QThread::exec (this=) at thread/qthread.cpp:531 #25 0x7f53f7024562 in QThreadPrivate::start (arg=0x564992a07870) at thread/qthread_unix.cpp:360 #26 0x7f53f2813569 in start_thread () from /lib64/libpthread.so.0 #27 0x7f53f670a85f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f53d6527700 (LWP 28238)): #0 0x7f53f66fbba8 in read () from /lib64/libc.so.6 #1 0x7f53efb63d20 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f53efb1ed38 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f53efb1f1d0 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f53efb1f33c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f53f726651b in QEventDispatcherGlib::processEvents (this=0x7f53c8000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f53f7206baa in QEventLoop::exec (this=this@entry=0x7f53d6526cb0,
[kmail2] [Bug 377554] "Show HTML for this contact" no longer works
https://bugs.kde.org/show_bug.cgi?id=377554 --- Comment #2 from Martin Koller --- I checked again with my current setup. I'm now using kmail 5.8.3 on openSuse Leap 15.0. I have the address only once in the addressbook (the address is in an addressbook stored on an ownCloud server in my local network). I set the address to "show HTML" and checked "allow remote content" - still when I select a mail received from this address it does not show me the HTML version but instead shows the usual text in the red rectangle: "Note: This is an HTML message. For security reasons, only the raw HTML code is shown. If you trust the sender of this message then you can activate formatted HTML display for this message by clicking here." Interesting to see is that when I right-click on the sender address in kmail and open the submenu "Show HTML Format" in the context menu, NONE of the 2 checkboxes are checked! I did set the "show HTML" from within kaddressbook. So it seems kmail does not read the same information as kaddressbook in this case. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 382185] resources color is only used for border
https://bugs.kde.org/show_bug.cgi?id=382185 --- Comment #8 from Martin Koller --- Agenda View and Month View settings both show * Category inside, calendar outside It seems that the month view has a different behavior than the agenda view when there is no category specified for an event. It seems agenda view uses the calendar color inside when no category is defined, but month view uses a default color in this case. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 Martin Koller changed: What|Removed |Added CC||kol...@aon.at --- Comment #33 from Martin Koller --- I see lots of them from http://planet.qt-project.org/rss20.xml and I have the feeling it is the same problem coming from kio-http which stores the same date/time when doing kioclient5 copy 'https://www.kde.org/aether/media/patrons/google.svg' file:///tmp/google.svg stat google.svg shows Modify: 2106-02-07 07:28:15.0 +0100 Also described here https://bugs.kde.org/show_bug.cgi?id=374420 but there it says it's not related to Akregator Also possible dup: https://bugs.kde.org/show_bug.cgi?id=262271#c10 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397239] New: crash when searching with kmail
https://bugs.kde.org/show_bug.cgi?id=397239 Bug ID: 397239 Summary: crash when searching with kmail Product: Akonadi Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Application: akonadiserver (5.8.90) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.4.138-59-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: I opened the "find messages" dialog from kmail, selected "Search in all folders", "Match all of the following" (default), "Complete Message" and entered my search string and hit "Search", then I got the crash report assistant tellig me akonadi crashed and kmail opens a dialog showing "Cannot get search result. Cannot connect to the Akonadi service." -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f048a6c8900 (LWP 25381))] Thread 33 (Thread 0x7f0451ffb700 (LWP 2164)): #0 0x7f0486e694a8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 Thread 9 (Thread 0x7f04767fc700 (LWP 25461)): [KCrash Handler] #6 0x7f0487fe4f67 in raise () from /lib64/libc.so.6 #7 0x7f0487fe633a in abort () from /lib64/libc.so.6 #8 0x00643f8e in akMessageHandler (type=QtFatalMsg, context=..., msg=...) at /home/KDE5/source/kde/pim/akonadi/src/shared/akdebug.cpp:177 #9 0x00646094 in (anonymous namespace)::RemoteLogger::dbusLogger (type=QtFatalMsg, ctx=..., msg=...) at /home/KDE5/source/kde/pim/akonadi/src/shared/akremotelog.cpp:178 #10 0x7f04759f4a24 in (anonymous namespace)::RemoteLogger::dbusLogger (type=QtFatalMsg, ctx=..., msg=...) at /home/KDE5/source/kde/pim/akonadi/src/shared/akremotelog.cpp:178 #11 0x7f0488c969bf in qt_message_print (message=..., context=..., msgType=QtFatalMsg) at global/qlogging.cpp:1793 #12 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=msg@entry=0x7f0488f10788 "ASSERT: \"%s\" in file %s, line %d", ap=ap@entry=0x7f04767fa318) at global/qlogging.cpp:365 #13 0x7f0488c7ff04 in QMessageLogger::fatal (this=this@entry=0x7f04767fa3f0, msg=msg@entry=0x7f0488f10788 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:877 #14 0x7f0488c7f576 in qt_assert (assertion=, file=, line=) at global/qglobal.cpp:3188 #15 0x0042da12 in Akonadi::Server::Connection::self () at /home/KDE5/source/kde/pim/akonadi/src/server/connection.cpp:82 #16 0x005b086b in Akonadi::Server::NotificationCollector::completeNotification (this=0x7f04608d2af0, changeMsg=...) at /home/KDE5/source/kde/pim/akonadi/src/server/storage/notificationcollector.cpp:545 #17 0x005b026f in Akonadi::Server::NotificationCollector::dispatchNotification (this=0x7f04608d2af0, msg=...) at /home/KDE5/source/kde/pim/akonadi/src/server/storage/notificationcollector.cpp:580 #18 0x005acb1b in Akonadi::Server::NotificationCollector::itemNotification (this=0x7f04608d2af0, op=Akonadi::Protocol::ItemChangeNotification::Unlink, items=..., collection=..., collectionDest=..., resource=..., parts=..., addedFlags=..., removedFlags=..., addedTags=..., removedTags=..., addedRelations=..., removedRelations=...) at /home/KDE5/source/kde/pim/akonadi/src/server/storage/notificationcollector.cpp:373 #19 0x005ad719 in Akonadi::Server::NotificationCollector::itemsUnlinked (this=0x7f04608d2af0, items=..., collection=...) at /home/KDE5/source/kde/pim/akonadi/src/server/storage/notificationcollector.cpp:132 #20 0x004bda51 in Akonadi::Server::SearchManager::updateSearchImpl (this=0x1fb8b80, collection=...) at /home/KDE5/source/kde/pim/akonadi/src/server/search/searchmanager.cpp:374 #21 0x004bfb07 in Akonadi::Server::SearchManager::updateSearch(Akonadi::Server::Collection const&)::$_9::operator()() const (this=0x7f03f81740a0) at /home/KDE5/source/kde/pim/akonadi/src/server/search/searchmanager.cpp:269 #22 0x004bfac9 in QtPrivate::FunctorCall, QtPrivate::List<>, void, Akonadi::Server::SearchManager::updateSearch(Akonadi::Server::Collection const&)::$_9>::call(Akonadi::Server::SearchManager::updateSearch(Akonadi::Server::Collection const&)::$_9&, void**) (f=..., arg=0x7f040f7fc530) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:128 #23 0x004bfaa1 in QtPrivate::Functor::call, void>(Akonadi::Server::SearchManager::updateSearch(Akonadi::Server::Collection const&)::$_9&, void*, void**) (f=..., arg=0x7f040f7fc530) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:238 #24 0x004bf9dd in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObje
[Akonadi] [Bug 397131] New: kmail crash due to MonitorPrivate::emitItemsNotification accessing empty items
https://bugs.kde.org/show_bug.cgi?id=397131
Bug ID: 397131
Summary: kmail crash due to
MonitorPrivate::emitItemsNotification accessing empty
items
Product: Akonadi
Version: GIT (master)
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: kol...@aon.at
Target Milestone: ---
I see kmail crashing after todays update (akonadi @
f7ce8ab4af83b8a64e97e2a8f11c21674cde826c)
The problem is in akonadis MonitorPrivate::emitItemsNotification
implementation, which gets called in line 555 via
if (!items.isEmpty() || itemNtf.operation() ==
Protocol::ItemChangeNotification::Remove || !fetchItems()) {
someoneWasListening = emitItemsNotification(itemNtf, items, parent,
destParent);
}
so obviously items CAN be empty (which it is in the crash case), but
emitItemsNotification()
in line 1064 (and others) uses
case Protocol::ItemChangeNotification::Add:
return emitToListeners(&Monitor::itemAdded, its.first(), col);
and Qt asserts due to the first() call on the empty list.
The stack I have here is:
1 raise
0x7fa2fad6df67
2 abort
0x7fa2fad6f33a
3 qt_message_fatal qlogging.cpp
1842 0x7fa2fba08f1c
4 QMessageLogger::fatal qlogging.cpp
880 0x7fa2fba08f1c
5 qt_assert qglobal.cpp
3188 0x7fa2fba08576
6 QVector::first qvector.h
237 0x7fa2f48bb98e
7 Akonadi::MonitorPrivate::emitItemsNotification monitor_p.cpp
1064 0x7fa2f48b0f90
8 Akonadi::MonitorPrivate::emitNotification monitor_p.cpp
555 0x7fa2f48ae94c
9 Akonadi::MonitorPrivate::dispatchNotifications monitor_p.cpp
1000 0x7fa2f48b58c5
10 Akonadi::MonitorPrivate::slotNotifymonitor_p.cpp
969 0x7fa2f48b532a
11 Akonadi::MonitorPrivate::handleCommandsmonitor_p.cpp
864 0x7fa2f48b4963
12 Akonadi::Monitor::qt_static_metacall moc_monitor.cpp
338 0x7fa2f48a18b3
13 QObject::event qobject.cpp
1251 0x7fa2fbc07f76
14 QApplicationPrivate::notify_helper qapplication.cpp
3728 0x7fa2fc9821ac
15 QApplication::notify qapplication.cpp
3487 0x7fa2fc988b52
16 QCoreApplication::notifyInternal2 qcoreapplication.cpp
1048 0x7fa2fbbdc8f5
17 QCoreApplication::sendEventqcoreapplication.h
234 0x7fa2fbbdf2be
18 QCoreApplicationPrivate::sendPostedEvents qcoreapplication.cpp
1745 0x7fa2fbbdf2be
19 QEventDispatcherUNIX::processEventsqeventdispatcher_unix.cpp
466 0x7fa2fbc2c5c4
20 QUnixEventDispatcherQPA::processEvents qunixeventdispatcher.cpp 68
0x7fa2d1fbc34d
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 397053] New: drag/drop mail from message list into folder tree no longer works
https://bugs.kde.org/show_bug.cgi?id=397053 Bug ID: 397053 Summary: drag/drop mail from message list into folder tree no longer works Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- since my latest git update (kmail at ec861db1120dae7d5b49fabc247bee4be9fc7816) I can no longer drag/drop a mail from the message list into any other folder. The operation is simply not done. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 396781] kmail no longer shows new mails
https://bugs.kde.org/show_bug.cgi?id=396781 --- Comment #3 from Martin Koller --- Did now a clean build, but does not resolve the problem. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 396781] kmail no longer shows new mails
https://bugs.kde.org/show_bug.cgi?id=396781 Martin Koller changed: What|Removed |Added Priority|NOR |VHI -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 396781] New: kmail no longer shows new mails
https://bugs.kde.org/show_bug.cgi?id=396781 Bug ID: 396781 Summary: kmail no longer shows new mails Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- since a recent update (yesterday or so) kmail no longer shows the new mails in the message list. I see the number of new mails e.g. in the systray notifier, I see the same number in the folder tree beside the "inbox" name and also in the favorites but clicking on my "inbox" folder does not show these new mails. Selecting any other folder and going back to "inbox" does not help. (In recent versions I sometimes had the same problem but often clicking on a different folder and back to "inbox" solved the issue. No more it seems). "Expand all threads" or "got to next/prev unread mail" does not help either. Only solution is to quit kmail and restart it. After the new start, the new mails correctly show up -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 386612] can't edit manual adblock filter rule
https://bugs.kde.org/show_bug.cgi?id=386612 --- Comment #2 from Martin Koller --- Yes, edit button now works. The multi-selection is still wrong. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 394169] New: zoom in value stored when viewing different article
https://bugs.kde.org/show_bug.cgi?id=394169 Bug ID: 394169 Summary: zoom in value stored when viewing different article Product: akregator Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- I select an article, press CTRL-+ to zoom in. Now I click on a different article, which is opened in 100%, but when I now press CTRL-+ then the actual zoom factor is added to the previous zoomed-in view of the other article. When I now select yet another article, which is again shown at 100% and I now press CTRL-+ again, then the view jumps already to the tripled zoomed in factor. akregator should either reset the zoom factor back to 100% internally when viewing a new article so that a one time press of CTRL-+ always leads to the same result, or it should keep the previously defined zoom factor when switching between articles. Just be consistent, please. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 393566] crashes when closing tab
https://bugs.kde.org/show_bug.cgi?id=393566 Martin Koller changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 393566] New: crashes when closing tab
https://bugs.kde.org/show_bug.cgi?id=393566 Bug ID: 393566 Summary: crashes when closing tab Product: akregator Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Just with some recent changes (either in KDE-PIM sources or Qt 5.10) akregator very often crashes e.g. on closing a tab. That was not the case just a week or 2 ago, but now it's happening so often that akregator is barely usable. I assume it has to do with webengine, since I also encounter often crashes in kmail since. BT: #0 0x7f3684cfbded in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*, base::Callback const&, GURL*) () from /usr/lib64/libQt5WebEngineCore.so.5 #1 0x7f36864bb772 in net::NetworkDelegate::NotifyBeforeURLRequest(net::URLRequest*, base::Callback const&, GURL*) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f36865c8f5b in net::URLRequest::Start () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f36853e1f11 in content::ResourceLoader::StartRequestInternal () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f36853e29f5 in content::ResourceLoader::Resume () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f36853c1b4a in content::AsyncResourceHandler::OnWillStart () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f36853c4ea2 in content::LayeredResourceHandler::OnWillStart () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f36853eb501 in content::ThrottlingResourceHandler::OnWillStart () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f36853eb1b1 in content::ThrottlingResourceHandler::ResumeStart () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f36853c98fa in base::internal::Invoker, content::NavigationThrottle::ThrottleCheckResult>, void ()>::Run(base::internal::BindStateBase*) () from /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f3685f67fd1 in base::debug::TaskAnnotator::RunTask () from /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7f3685f02cb0 in base::MessageLoop::RunTask () from /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7f3685f044ce in base::MessageLoop::DeferOrRunPendingTask () from /usr/lib64/libQt5WebEngineCore.so.5 #13 0x7f3685f054a9 in DoWork () from /usr/lib64/libQt5WebEngineCore.so.5 #14 0x7f3685f05a50 in base::MessagePumpLibevent::Run () from /usr/lib64/libQt5WebEngineCore.so.5 #15 0x7f3685f22068 in base::RunLoop::Run () from /usr/lib64/libQt5WebEngineCore.so.5 #16 0x7f368521c465 in content::BrowserThreadImpl::IOThreadRun () from /usr/lib64/libQt5WebEngineCore.so.5 #17 0x7f368521c89b in content::BrowserThreadImpl::Run () from /usr/lib64/libQt5WebEngineCore.so.5 #18 0x7f3685f3cf16 in base::Thread::ThreadMain () from /usr/lib64/libQt5WebEngineCore.so.5 #19 0x7f3685f3827d in ThreadFunc () from /usr/lib64/libQt5WebEngineCore.so.5 #20 0x7f3680e4c724 in start_thread () from /lib64/libpthread.so.0 ---Type to continue, or q to quit--- #21 0x7f368c758e8d in clone () from /lib64/libc.so.6 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 393451] New: drag a mail into folder tree shows possibility to drop between folders
https://bugs.kde.org/show_bug.cgi?id=393451 Bug ID: 393451 Summary: drag a mail into folder tree shows possibility to drop between folders Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- When I drag a mail from the message list to the folder tree, the drag operation shows me also a drop possibility (via a black line) *between* folders. That does not make sense. A mail will always be dropped only *into* a folder. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 352214] Event is not displayed in the UI if the invitation list contains the creator's email address with PARTSTAT=NEEDS-ACTION (or maybe anything else than PARTSTAT=ACCEPTED?)
https://bugs.kde.org/show_bug.cgi?id=352214 Martin Koller changed: What|Removed |Added Latest Commit|https://commits.kde.org/ako |https://commits.kde.org/ako |nadi-calendar/268284b419a51 |nadi-calendar/86625a0ebcd5d |9e08367c19de3fb1f9ed841acea |0bf2e13edb05cea7acfd5121a82 --- Comment #8 from Martin Koller --- Git commit 86625a0ebcd5d0bf2e13edb05cea7acfd5121a82 by Martin Koller. Committed on 14/04/2018 at 11:56. Pushed by mkoller into branch 'Applications/18.04'. always show an incidence if we are the organizer (cherry picked from commit 268284b419a519e08367c19de3fb1f9ed841acea) M +5-0src/calfilterpartstatusproxymodel_p.cpp https://commits.kde.org/akonadi-calendar/86625a0ebcd5d0bf2e13edb05cea7acfd5121a82 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 352214] Event is not displayed in the UI if the invitation list contains the creator's email address with PARTSTAT=NEEDS-ACTION (or maybe anything else than PARTSTAT=ACCEPTED?)
https://bugs.kde.org/show_bug.cgi?id=352214 Martin Koller changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/ako ||nadi-calendar/268284b419a51 ||9e08367c19de3fb1f9ed841acea Resolution|--- |FIXED --- Comment #7 from Martin Koller --- Git commit 268284b419a519e08367c19de3fb1f9ed841acea by Martin Koller. Committed on 09/04/2018 at 17:28. Pushed by mkoller into branch 'master'. always show an incidence if we are the organizer M +5-0src/calfilterpartstatusproxymodel_p.cpp https://commits.kde.org/akonadi-calendar/268284b419a519e08367c19de3fb1f9ed841acea -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 366055] kOrganizer 5.1.3: Incidents inviting "myself" are invisible
https://bugs.kde.org/show_bug.cgi?id=366055 Bug 366055 depends on bug 352214, which changed state. Bug 352214 Summary: Event is not displayed in the UI if the invitation list contains the creator's email address with PARTSTAT=NEEDS-ACTION (or maybe anything else than PARTSTAT=ACCEPTED?) https://bugs.kde.org/show_bug.cgi?id=352214 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388714] New: selecting a favorite when folder tree is filtered shows no messages
https://bugs.kde.org/show_bug.cgi?id=388714 Bug ID: 388714 Summary: selecting a favorite when folder tree is filtered shows no messages Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- I filter the folder tree where e.g. my inbox (which I have defined as favorite) is no longer shown. I select one folder shown in the folder tree and see the messages inside it -> OK I click on the inbox favorite -> no mails are shown -> Not OK Only when I clear the folder filter and select the favorite again I can see the messages inside the selected favorite folder -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388424] New: abort when clicking on favorites folder
https://bugs.kde.org/show_bug.cgi?id=388424 Bug ID: 388424 Summary: abort when clicking on favorites folder Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- kmail built from source as of today. After starting kmail, enter some text in the filter line edit above the folder tree (tree gets reduced to some folders), then click on a favorite folder -> abort. Problem is in akonadi/src/widgets/standardactionmanager.cpp favoriteSelectionChanged() line 587 where the selection.indexes() calls first() but the list is actually empty. #0 0x716948d7 in raise () from /lib64/libc.so.6 #1 0x71695caa in abort () from /lib64/libc.so.6 #2 0x72340dae in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5 #3 0x7233c0c6 in qt_assert(char const*, char const*, int) () from /usr/lib64/libQt5Core.so.5 #4 0x7fffeb7ea47a in QList::first (this=0x7fffbdb0) at /usr/include/qt5/QtCore/qlist.h:345 #5 0x7fffeb804477 in Akonadi::StandardActionManager::Private::favoriteSelectionChanged (this=0xe56f20) at /home/KDE5/source/kde/pim/akonadi/src/widgets/standardactionmanager.cpp:587 #6 0x7fffeb8000cc in Akonadi::StandardActionManager::qt_static_metacall (_o=0xe49e70, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7fffbf80) at /home/KDE5/source/build/kde/pim/akonadi/src/widgets/moc_standardactionmanager.cpp:258 #7 0x7253f3df in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #8 0x724cdc67 in QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) () from /usr/lib64/libQt5Core.so.5 #9 0x724d098a in QItemSelectionModel::emitSelectionChanged(QItemSelection const&, QItemSelection const&) () from /usr/lib64/libQt5Core.so.5 #10 0x724d187a in QItemSelectionModel::select(QItemSelection const&, QFlags) () from /usr/lib64/libQt5Core.so.5 #11 0x73491af7 in QListView::setSelection(QRect const&, QFlags) () from /usr/lib64/libQt5Widgets.so.5 #12 0x7345a550 in QAbstractItemView::mousePressEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x70b0a842 in MailCommon::FavoriteCollectionWidget::mousePressEvent (this=0xe5b690, e=0x7fffc920) at /home/KDE5/source/kde/pim/mailcommon/src/widgets/favoritecollectionwidget.cpp:79 #14 0x7325e590 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #15 0x7330112e in QFrame::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7345f04b in QAbstractItemView::viewportEvent(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x72514fe1 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #18 0x732226f5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 ---Type to continue, or q to quit--- #19 0x73229b9c in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #20 0x72515115 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #21 0x73228a19 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib64/libQt5Widgets.so.5 #22 0x73276a6f in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #23 0x73278f83 in QWidgetWindow::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #24 0x7322271c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #25 0x73229500 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #26 0x72515115 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #27 0x72a8308d in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib64/libQt5Gui.so.5 #28 0x72a84c45 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5 #29 0x72a636bb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib64/libQt5Gui.so.5 #30 0x7fffc8435b6b in QPAEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5XcbQpa.so.5 #31 0x7251383b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #32 0x7251bef4 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #33 0x004047fa in main (argc=1, argv=0x7fffd2e8) at /home/KDE5/source/kde/pim/kmail/src/main.cpp:156 -- You are receiv
[kmail2] [Bug 367998] quick-search field does not receive some keys
https://bugs.kde.org/show_bug.cgi?id=367998 Martin Koller changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Martin Koller --- using git master now I can not reproduce it. closing -- You are receiving this mail because: You are the assignee for the bug.
[kmailtransport] [Bug 387389] abort when sending mail
https://bugs.kde.org/show_bug.cgi?id=387389 --- Comment #3 from Martin Koller --- No, this is in a different class and really a Q_ASSERT() -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 377485] regression: system tray icon no longer shows number of unread articles
https://bugs.kde.org/show_bug.cgi?id=377485 --- Comment #7 from Martin Koller --- In my own desktop shell, liquidshell, I have integrated a workaround to see the unread count for KMail and Akregator if the count is < 100. You might want to give it a try: https://cgit.kde.org/liquidshell.git/ -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 378944] crash when typing a "C" in the folder quick-filter line edit
https://bugs.kde.org/show_bug.cgi?id=378944 --- Comment #2 from Martin Koller --- *** Bug 381126 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 381126] assert in storagemodelbase.cpp
https://bugs.kde.org/show_bug.cgi?id=381126 Martin Koller changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Koller --- *** This bug has been marked as a duplicate of bug 378944 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387873] New: can no longer drag/drop a message from message list to favorites
https://bugs.kde.org/show_bug.cgi?id=387873 Bug ID: 387873 Summary: can no longer drag/drop a message from message list to favorites Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- With current git version I can no longer drag/drop a mail from the message list onto a folder shown in the favorites. This worked some time ago. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387613] sending mail with 2MB attachment delivers but still shows error
https://bugs.kde.org/show_bug.cgi?id=387613 Martin Koller changed: What|Removed |Added Latest Commit||https://commits.kde.org/ksm ||tp/400942fde2e90c79dca9d60c ||e94293cffaccde38 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Martin Koller --- Git commit 400942fde2e90c79dca9d60ce94293cffaccde38 by Martin Koller. Committed on 09/12/2017 at 11:33. Pushed by mkoller into branch 'Applications/17.12'. do not cancel send job after 10s timeout Differential Revision: https://phabricator.kde.org/D9256 M +10 -1src/session.cpp https://commits.kde.org/ksmtp/400942fde2e90c79dca9d60ce94293cffaccde38 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387613] sending mail with 2MB attachment delivers but still shows error
https://bugs.kde.org/show_bug.cgi?id=387613 Martin Koller changed: What|Removed |Added Latest Commit|https://commits.kde.org/ksm |https://commits.kde.org/ksm |tp/400942fde2e90c79dca9d60c |tp/28b99a142ea66b123cc1d271 |e94293cffaccde38|25beff80b3c58188 --- Comment #2 from Martin Koller --- Git commit 28b99a142ea66b123cc1d27125beff80b3c58188 by Martin Koller. Committed on 09/12/2017 at 11:31. Pushed by mkoller into branch 'master'. do not cancel send job after 10s timeout Differential Revision: https://phabricator.kde.org/D9256 M +10 -1src/session.cpp https://commits.kde.org/ksmtp/28b99a142ea66b123cc1d27125beff80b3c58188 -- You are receiving this mail because: You are the assignee for the bug.
