[korganizer] [Bug 466973] Events can overlap such as one hides the other
https://bugs.kde.org/show_bug.cgi?id=466973 --- Comment #1 from Alex Dănilă --- Comment on attachment 157065 --> https://bugs.kde.org/attachment.cgi?id=157065 Screenshot event3 is under event1 even though it is selected. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 466973] New: Events can overlap such as one hides the other
https://bugs.kde.org/show_bug.cgi?id=466973 Bug ID: 466973 Summary: Events can overlap such as one hides the other Classification: Applications Product: korganizer Version: 5.22.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: monthview Assignee: kdepim-bugs@kde.org Reporter: alex.danila@protonmail.com Target Milestone: --- Created attachment 157065 --> https://bugs.kde.org/attachment.cgi?id=157065=edit Screenshot SUMMARY When working with a few events that extend over more than one day, it is easy to get into a situation when one event hides the other STEPS TO REPRODUCE 1. Create a couple of multi-day events. E.g. in the screenshot: - event1: 06-03 - 06-04 - event2: 06-04 - 06-05 - event4: 06-26 - 07-03 - event5: 07-06 - 0709 2. Notice the event 3 may or may no be visible, depending on the order of creation and interaction. OBSERVED RESULT EXPECTED RESULT Easier to distinguish and interact with the different events. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian GNU/Linux 12, 6.1.0-5-amd64 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 466971] Korganizer crashes when dragging the edge of an event in the month view
https://bugs.kde.org/show_bug.cgi?id=466971 Alex Dănilă changed: What|Removed |Added Attachment #157064|Crash dump, other can be|Crash stack, other can be description|produced on request |produced on request -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 466971] New: Korganizer crashes when dragging the edge of an event in the month view
https://bugs.kde.org/show_bug.cgi?id=466971 Bug ID: 466971 Summary: Korganizer crashes when dragging the edge of an event in the month view Classification: Applications Product: korganizer Version: 5.22.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: monthview Assignee: kdepim-bugs@kde.org Reporter: alex.danila@protonmail.com Target Milestone: --- Created attachment 157064 --> https://bugs.kde.org/attachment.cgi?id=157064=edit Crash dump, other can be produced on request SUMMARY Crashes when dragging an edge of an event, such as to extend or shorten it. STEPS TO REPRODUCE 1. Open month view 2. Add a few events 3. Click on the edge of one event and start dragging to extend and shorten it 4. After a succession of such ”resizes” the crash will likely happen. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian GNU/Linux 12, 6.1.0-5-amd64 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 465735] Kontact doesn't work with iCal URLs
https://bugs.kde.org/show_bug.cgi?id=465735 --- Comment #5 from Alex Ander --- (In reply to Laurent Montel from comment #3) > Indeed I can't see "display name" for sure. > no event too. Can we mark the bug as "confirmed" then? -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 465735] Kontact doesn't work with iCal URLs
https://bugs.kde.org/show_bug.cgi?id=465735 --- Comment #4 from Alex Ander --- (In reply to Laurent Montel from comment #3) > What is the url that you put in resource ? local ? url ? This is the URL to .ics file, located in the web. Actually, dynamically created on each call. I followed instructions from this old forum, where they said, it worked: https://bbs.archlinux.org/viewtopic.php?id=166238 I want to see events from remote calendar. I don't need it for Nextcloud, as it does support CalDAV, but for another application, which supports only iCal exports. And looks like the thing with "akonadi_ical_resource_1" is not new, as it can be found here: https://www.reddit.com/r/kde/comments/qalqf0/readding_an_ical_file_to/ and was reported here: https://bugs.kde.org/show_bug.cgi?id=452456 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 465735] Kontact doesn't work with iCal URLs
https://bugs.kde.org/show_bug.cgi?id=465735 --- Comment #2 from Alex Ander --- (In reply to Laurent Montel from comment #1) > Hi, > Do you have a test case file about it ?. > Regards Hi! I made a test iCal link with nextcloud: https://nextcloud.webo.hosting/remote.php/dav/public-calendars/fgGHm4CpLw7A9eda/?export All the best -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 465735] New: Kontact doesn't work with iCal URLs
https://bugs.kde.org/show_bug.cgi?id=465735 Bug ID: 465735 Summary: Kontact doesn't work with iCal URLs Classification: Applications Product: kontact Version: 5.20.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-bugs@kde.org Reporter: aalexand...@gmail.com Target Milestone: --- SUMMARY Kontact doesn't work with iCal data from URL. It does work with downloaded file, but doesn't with URL. If I add it, Kontact add a "akonadi_ical_resource_1" line under calendars and don't show any events. Right click and "Update Calendar" and "Update Folder" changes nothing. Sometimes after a while - after many system restarts - the calendar with given display name appears as one more calendar and shows right events. But this is quite unpredictable, I couldn't find any correlation, and removing the "akonadi_ical_resource_1" calendar removes also the correct calendar from Kontact list. STEPS TO REPRODUCE 1. go to calendars in Kontact. 2. Right Click on calendars frame -> "add calendar" 3. Choose "iCal Calendar File" 4. Set your exported calendar's URL as filename and something as display name, press ok 5. look onto calendars list. OBSERVED RESULT Added calendar named "akonadi_ical_resource_1", without any events. EXPECTED RESULT Added calendar with name from "display name" and with all events from URL. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-60-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I tested iCal URLs from Leantime and from Nextcloud. The problem exists even on fresh installed Kubuntu. I used Backports PPA to get the latest Kontact. -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 324840] sync notes with owncloud/nextcloud notes app
https://bugs.kde.org/show_bug.cgi?id=324840 Alex Ander changed: What|Removed |Added Summary|sync notes with owncloud|sync notes with |notes app |owncloud/nextcloud notes ||app CC||aalexand...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 444288] Akonadi "losing connection" to Google Calendars after some uptime / waking from sleep until either akonadictrl restart is used or Google Groupware is restarted in Korganizer.
https://bugs.kde.org/show_bug.cgi?id=444288 Alex Dewar changed: What|Removed |Added CC||alex.de...@gmx.co.uk --- Comment #6 from Alex Dewar --- I was experiencing this bug and now things seem to have got worse -- restarting Google Groupware (or the whole of the akonadi service) doesn't fix it, so I can't view my Google Calendar at all :-( -- You are receiving this mail because: You are on the CC list for the bug.
[akregator] [Bug 445351] Akregator always wants to recover the session on boot
https://bugs.kde.org/show_bug.cgi?id=445351 --- Comment #2 from Alex Barrero --- (In reply to Alex Barrero from comment #1) > I have a desktop PC for home and a laptop for work. Both use the latest > version of KDE Neon User Edition > > Operating System: KDE neon 5.23 > KDE Plasma Version: 5.23.4 > KDE Frameworks Version: 5.89.0 > Qt Version: 5.15.3 > Kernel Version: 5.11.0-43-generic (64-bit) > Graphics Platform: Wayland > > Only difference is that PC desktop uses X11 session and the laptop uses > Wayland session. > > In PC desktop, Akregator auto starts fine with latest session used after > reboot the system, but in Wayland, although I haven't configured the app to > autostart on system boot, when I launch the app I can always reproduce this > issue that shows the recover session. > > Will try to configure Akregator to autostart on system launch and update > this comment. Forgot to add the Akregator version: 5.19.0 (21.12.0) -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 445351] Akregator always wants to recover the session on boot
https://bugs.kde.org/show_bug.cgi?id=445351 Alex Barrero changed: What|Removed |Added CC||alex.brrsc...@gmail.com --- Comment #1 from Alex Barrero --- I have a desktop PC for home and a laptop for work. Both use the latest version of KDE Neon User Edition Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-43-generic (64-bit) Graphics Platform: Wayland Only difference is that PC desktop uses X11 session and the laptop uses Wayland session. In PC desktop, Akregator auto starts fine with latest session used after reboot the system, but in Wayland, although I haven't configured the app to autostart on system boot, when I launch the app I can always reproduce this issue that shows the recover session. Will try to configure Akregator to autostart on system launch and update this comment. -- You are receiving this mail because: You are the assignee for the bug.
[kmime] [Bug 419628] kmime fails {header,message}test with Qt 5.15.0-beta2
https://bugs.kde.org/show_bug.cgi?id=419628
Alex Fan changed:
What|Removed |Added
CC||alex.fa...@gmail.com
--- Comment #1 from Alex Fan ---
I am having only two similar failures of header,message tests on Gentoo,
didn't get other failures. But I am testing it on riscv though, not sure if it
would affect.
FAIL! : HeaderTest::testAddressListHeader() Compared values are not the same
Actual (h->as7BitString(false)) :
"Ingo Kl\xF6""cker "
Expected (QByteArray("Ingo =?ISO-8859-1?Q?Kl=F6cker?= ")):
"Ingo =?ISO-8859-1?Q?Kl=F6cker?= "
Loc:
[/var/tmp/portage/kde-apps/kmime-21.08.3/work/kmime-21.08.3/autotests/headertest.cpp(147)]
FAIL! : MessageTest::testOutlookAttachmentNaming() Compared values are not the
same
Actual (attachment->contentDisposition()->as7BitString(false))
: "attachment; filename=\"\xE5.diff\""
Expected (QByteArray("attachment;
filename=\"=?ISO-8859-1?Q?=E5=2Ediff?=\"")): "attachment;
filename=\"=?ISO-8859-1?Q?=E5=2Ediff?=\""
Loc:
[/var/tmp/portage/kde-apps/kmime-21.08.3/work/kmime-21.08.3/autotests/messagetest.cpp(580)]
SOFTWARE/OS VERSIONS
kmime Version: 21.08.3
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
--
You are receiving this mail because:
You are the assignee for the bug.
[Akonadi] [Bug 437535] PayRoll
https://bugs.kde.org/show_bug.cgi?id=437535 Alex changed: What|Removed |Added CC||alex...@protonmail.com -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 84472] Sundays are colored the same as holidays.
https://bugs.kde.org/show_bug.cgi?id=84472 Alex changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- Ever confirmed|1 |0 --- Comment #6 from Alex --- Actually my mistake, I just happened to have some stuff that happened to be on the same day as nearby public holidays, so I thought that bold = public holiday, when it really means that you just have something on that day. And it looks like in the settings, pink is still a holiday colour, which is the same as weekend colours. But by default, public holidays aren't shown at all, and I can't work out how to show them... I'll re-mark this as reported until I understand the issue better. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 84472] Sundays are colored the same as holidays.
https://bugs.kde.org/show_bug.cgi?id=84472 Alex changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||alex...@protonmail.com --- Comment #5 from Alex --- I don't think this bug exists anymore. At the moment, in the calendar, Saturdays and Sundays are both coloured red, while public holidays are boldened. I'll mark this as fixed, but feel free to reopen it if you disagree. -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 430161] New: Decrytion failed: 'Unable to decrypt, no secret key'
https://bugs.kde.org/show_bug.cgi?id=430161 Bug ID: 430161 Summary: Decrytion failed: 'Unable to decrypt, no secret key' Product: kleopatra Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: alexander@unilever.com CC: kdepim-bugs@kde.org, m...@kde.org Target Milestone: --- Created attachment 133934 --> https://bugs.kde.org/attachment.cgi?id=133934=edit Error message SUMMARY Whenever I try to decrypt any file I get the error message 'Unable to decrypt, no secret key'. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 388151] Moving messages to other folder corrupts threading
https://bugs.kde.org/show_bug.cgi?id=388151 Alex Hermann changed: What|Removed |Added Version|5.6.0 |5.12.2 --- Comment #1 from Alex Hermann --- It is not just threading that breaks. Kmail messes up the whole relation between headers and bodies of emails. In other words, message 1 gets the headers from message 2 and so on. This leads to wrong threading, but also to replying to the wrong message or even deleting them, making this a data-loss bug. Reproduce: 1. Select multiple messages in a folder (preferably with different subject, thus from different threads, as it will show the bug more easily). 2. Move those messages to another folder 3. Notice that in the target folder, headers and bodies of the moved emails don't match with each other. This can be fixed (until the next move) by clearing the cache for the target folder in akonadiconsole. Is there anything I can do/provide to get some movement on this bug? -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 389059] Deleting articles in Akregator causes graphics reset
https://bugs.kde.org/show_bug.cgi?id=389059 Alex changed: What|Removed |Added CC||alex...@protonmail.com --- Comment #3 from Alex --- I could not reproduce this with Akregator 5.15.0 on AMD graphics (mesa). Syam, do you still get this bug? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 422173] Handling missing 'date' in email headers
https://bugs.kde.org/show_bug.cgi?id=422173 Alex Hermann changed: What|Removed |Added CC||g...@gmx.net --- Comment #4 from Alex Hermann --- Wouldn't the first received date be more appropriate? It is probably closer to the real originating date than the latest received dat after all intermediate hops with all their delays. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 403065] Akregator crashes when adding link
https://bugs.kde.org/show_bug.cgi?id=403065 --- Comment #2 from Alex Dănilă --- Created attachment 123867 --> https://bugs.kde.org/attachment.cgi?id=123867=edit New crash information added by DrKonqi akregator (5.9.3) using Qt 5.12.5 - What I was doing when the application crashed: Like the original reporter, tried to add a link to a website feed, but with right click add. -- Backtrace (Reduced): #6 0x7f1145978dbf in Akregator::Feed::slotAddToFetchQueue(Akregator::FetchQueue*, bool) () from /usr/lib/x86_64-linux-gnu/libakregatorprivate.so.5 #7 0x7f114598dff1 in Akregator::Folder::slotAddToFetchQueue(Akregator::FetchQueue*, bool) () from /usr/lib/x86_64-linux-gnu/libakregatorprivate.so.5 #8 0x7f114437f528 in QtPrivate::QSlotObjectBase::call (a=0x7ffcc3e814b0, r=0x563f19e1e170, this=0x563f19c9f0d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 [...] #10 0x7f114438c147 in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:204 #11 0x7f114437fd85 in QObject::event (this=0x563f19d6c7b0, e=) at kernel/qobject.cpp:1282 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 403065] Akregator crashes when adding link
https://bugs.kde.org/show_bug.cgi?id=403065 Alex Dănilă changed: What|Removed |Added CC||nuor...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Alex changed: What|Removed |Added CC||drace...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 410077] Signing in with Google is temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=410077 --- Comment #7 from Alex --- Hi! I have the same problem with fresh OpenSuse Tumbleweed installation. I add screenshots about the error (in spanish). Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 410077] Signing in with Google is temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=410077 --- Comment #6 from Alex --- Created attachment 121795 --> https://bugs.kde.org/attachment.cgi?id=121795=edit akonadi google error -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 410077] Signing in with Google is temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=410077 Alex changed: What|Removed |Added CC||drace...@gmail.com --- Comment #5 from Alex --- Created attachment 121794 --> https://bugs.kde.org/attachment.cgi?id=121794=edit akonadi google login -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Alex Sidorenko changed: What|Removed |Added CC||alexandre.sidorenko@gmail.c ||om -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 396714] New: Calendar doesn't show Facebook events
https://bugs.kde.org/show_bug.cgi?id=396714 Bug ID: 396714 Summary: Calendar doesn't show Facebook events Product: korganizer Version: 5.8.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: aalexand...@gmail.com Target Milestone: --- I connected a Facebook account as calendar source in KOrganizer. It shows 5 folders like "Events I'm attending" etc, but shows no actual event in the calendar. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 395800] Tasklist Panel in "Agenda" view doesn't show my tasks.
https://bugs.kde.org/show_bug.cgi?id=395800 --- Comment #1 from Alex Ander --- I'm sorry, what I considered a "tasklist panel" was actually a "item view" panel. I found a setting, showing the tasklist - and they are all there :) Please delete this "bug". -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 395800] New: Tasklist Panel in "Agenda" view doesn't show my tasks.
https://bugs.kde.org/show_bug.cgi?id=395800 Bug ID: 395800 Summary: Tasklist Panel in "Agenda" view doesn't show my tasks. Product: korganizer Version: 5.8.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: agendaview (weekview) Assignee: kdepim-bugs@kde.org Reporter: aalexand...@gmail.com Target Milestone: --- Tasklist Panel in "Agenda" view doesn't show my tasks. It can show one to-do, after turning off and on related source, but after switching view, for example to "To-do List" and back, it also disappears. All my to-dos are simple, without due date, and priorities. I have to-dos as from gmail, as from Next Cloud Server (CalDAV). They are all visible in "To-do List" view. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 374761] Event/To-do/Journal editor fails to populate calendar combo box
https://bugs.kde.org/show_bug.cgi?id=374761 --- Comment #6 from Alex Dănilă --- Note: go to Settings->General->Calendar, select "Personal Calendar" click modify, press OK in the calendar modification window without actually modifying anything. The new calendar may be available for use. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 374761] Event/To-do/Journal editor fails to populate calendar combo box
https://bugs.kde.org/show_bug.cgi?id=374761 Alex Dănilă changed: What|Removed |Added CC||nuor...@gmail.com --- Comment #5 from Alex Dănilă --- Can confirm with 5.7.3. What is a good workaround? -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 394946] New: Delete key no longer works in articles list after using search - keyboard focus stays in search field
https://bugs.kde.org/show_bug.cgi?id=394946 Bug ID: 394946 Summary: Delete key no longer works in articles list after using search - keyboard focus stays in search field Product: akregator Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: nuor...@gmail.com Target Milestone: --- After typing into the „Search articles” field, the keyboard focus seems to remain there, so the delete key won't delete articles anymore. Steps: 1. select an article in the articles list and press delete, notice it is deleted 2. click and type a text in the search field, then clear the text 3. click an article in the articles list 4. press delete and notice nothing happens; right click will still work 5. click in the article contents area and press the delete key, notice that now delete works. Akregator 5.7.3 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 376045] Non-functional "Details" button when Akonadi fails to start
https://bugs.kde.org/show_bug.cgi?id=376045 Alex Dănilă <nuor...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Alex Dănilă <nuor...@gmail.com> --- Can still reproduce with 17.12.3 of Debian Testing. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 376045] Non-functional "Details" button when Akonadi fails to start
https://bugs.kde.org/show_bug.cgi?id=376045 Alex Dănilă <nuor...@gmail.com> changed: What|Removed |Added CC||nuor...@gmail.com --- Comment #1 from Alex Dănilă <nuor...@gmail.com> --- *** Bug 394768 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 394768] „Details” button of „The akonadi [...] service is not operational" does nothing”
https://bugs.kde.org/show_bug.cgi?id=394768 Alex Dănilă <nuor...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Alex Dănilă <nuor...@gmail.com> --- Should have noticed already reported bug. *** This bug has been marked as a duplicate of bug 376045 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 394768] New: „Details” button of „The akonadi [...] service is not operational" does nothing”
https://bugs.kde.org/show_bug.cgi?id=394768 Bug ID: 394768 Summary: „Details” button of „The akonadi [...] service is not operational" does nothing” Product: Akonadi Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: nuor...@gmail.com Target Milestone: --- When KAddressBook/Korganizer fail to start they show a grey window with a „Details” button. Pressing that doesn't show any more information (I assume corruption) or do anything at all. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 392888] New: Allow setting a "default status filter" in settings, for when Quick Filter is hidden
https://bugs.kde.org/show_bug.cgi?id=392888 Bug ID: 392888 Summary: Allow setting a "default status filter" in settings, for when Quick Filter is hidden Product: akregator Version: 5.7.2 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: eternal...@gmail.com Target Milestone: --- Note: I'm on 5.7.3, but Bugzilla doesn't have that yet, so filing against 5.7.2. In Akregator, article status filtering and title filtering are both tied to the "Quick Filter" bar. However, this forces a number of problematic trade-offs: - If the filter is visible, various cases cause keyboard focus to move to the filter input, resulting in shortcuts (such as "d" for "mark read") instead causing the filter to kick in - If the filter is not visible, the article status filter is reset (this behavior was introduced somewhere within the past year, and while it makes sense from a "invisible settings are liable to confuse the user", it also makes my use case impossible) The vast majority of the time, I want: - To only see unread articles - To not have the filter bar visible or a valid target for keyboard focus Occasionally, I want: - To see all articles, or - To filter articles, or - Both If there was an item in settings, that set the "default status filter" (all/unread/new) for when the Quick Filter bar was hidden (and thus would also set that dropdown appropriately on reset), this would make Akregator much easier for me to use with my workflow (which the reset-on-hide behavior regressed). (For a while, I worked around the reset-on-hide behavior by manually setting the appropriate fields in akregatorrc, but it's just recently stopped accepting status filters being set while the Quick Filter bar is hidden.) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Alex Hermann <g...@gmx.net> changed: What|Removed |Added CC||g...@gmx.net -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[kmail2] [Bug 388151] New: Moving messages to other folder corrupts threading
https://bugs.kde.org/show_bug.cgi?id=388151 Bug ID: 388151 Summary: Moving messages to other folder corrupts threading Product: kmail2 Version: 5.6.0 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: g...@gmx.net Target Milestone: --- When using threading strategy "Perfect and by references", moved messages are threaded randomly in the tree under the thread starter. In the same folder, the direct parent (from In-Reply-To) is also present, but the message not threaded under it. The resulting folder structure is a complete mess. Restarting kmail and/or akonadi doesn't help. Changing to threading startegy "Perfect only" shows the correct tree, but obviously creates separate trees when a message is missing. Switching back to "Perfect and by references" seems to fix the threading. I have not noticed any problems with threading of new incoming emails, only when moving messages between folders. The messages are moved within the same account, which uses online imap as its backend. The message list aggregation is set to "Threaded" with the following config: Grouping: none Group expand policy: - Threading: perfect and by references Thread leader: Topmost message Thread expand policy: Expand threads with unread or important messages Fill view strategy: Favor interactivity -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #17 from Alex Sidorenko <alexandre.sidore...@gmail.com> --- (In reply to Alex Sidorenko from comment #16) > Same here - Gmail sending stopped work after upgrade to 17.12 (Ubuntu/Neon) My settings were based on 'Autodetect', SSL on port 465. After I changed this manually to TLS/587, sending email works -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Alex Sidorenko <alexandre.sidore...@gmail.com> changed: What|Removed |Added CC||alexandre.sidorenko@gmail.c ||om --- Comment #16 from Alex Sidorenko <alexandre.sidore...@gmail.com> --- Same here - Gmail sending stopped work after upgrade to 17.12 (Ubuntu/Neon) -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 387400] New: Renaming note on desktop changes colours to original default.
https://bugs.kde.org/show_bug.cgi?id=387400 Bug ID: 387400 Summary: Renaming note on desktop changes colours to original default. Product: knotes Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: buggersholea...@gmail.com CC: myr...@kde.org Target Milestone: --- Version 4:17.04.3-0ubuntu1 on Kubuntu 17.10 To reproduce, start knotes outside of kontact. 1: Change default colour scheme 2: Create new note on desktop via the system tray. 3: Right click the title to rename it -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 378315] KMail crash on logout
https://bugs.kde.org/show_bug.cgi?id=378315 Alex Sidorenko <alexandre.sidore...@gmail.com> changed: What|Removed |Added CC||alexandre.sidorenko@gmail.c ||om --- Comment #14 from Alex Sidorenko <alexandre.sidore...@gmail.com> --- I can see the same problem on Ubuntu-16.04 + Neon libqt5webengine5 5.9.1+dfsg-2+16.04+xenial+build36 The problem is still there after upgrade to KDE-applications 17.08.0 (KMail 5.6.0) -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 380101] New: Question: CalDavSync
https://bugs.kde.org/show_bug.cgi?id=380101 Bug ID: 380101 Summary: Question: CalDavSync Product: korganizer Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: html export Assignee: kdepim-bugs@kde.org Reporter: alex...@web.de Target Milestone: --- My question: Is it possible to syncronize the calendar by CALDAVSYNC with my ANDROID-Smartphone (Huawei P10 PLUS) and/or other accounts ? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 379911] No mail accounts (IMAP) can be created or configured anymore
https://bugs.kde.org/show_bug.cgi?id=379911 --- Comment #4 from Alex Sidorenko <alexandre.sidore...@gmail.com> --- Hi Michael, the upstream BZ says: "Pushed by arojas into branch 'Applications/17.04'" This essentially means that if Neon maintainers do not care about backporthing this bugfix to 17.04.1 (should be trivial), we will get the fixed package when 17.04.2 is released. According to https://community.kde.org/Schedules/Applications/17.04_Release_Schedule this is expected on Thursday, June 8, 2017 Alex -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 379911] No mail accounts (IMAP) can be created or configured anymore
https://bugs.kde.org/show_bug.cgi?id=379911 Alex Sidorenko <alexandre.sidore...@gmail.com> changed: What|Removed |Added CC||alexandre.sidorenko@gmail.c ||om --- Comment #2 from Alex Sidorenko <alexandre.sidore...@gmail.com> --- This is upstream bug https://bugs.kde.org/show_bug.cgi?id=379155 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 377233] New: Deleting a message should select next message below
https://bugs.kde.org/show_bug.cgi?id=377233 Bug ID: 377233 Summary: Deleting a message should select next message below Product: akregator Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: nuor...@gmail.com Target Milestone: --- When deleting a message Akregator selects the message above the deleted one. This is the opposite of the usual moving down to the next object, e.g. deleting a message in Thunderbird moves down (more extreme: pressing delete in text editor will keep deleting letters from the right of the cursor). -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 377061] New: Crash after adding new project in zanshin
https://bugs.kde.org/show_bug.cgi?id=377061 Bug ID: 377061 Summary: Crash after adding new project in zanshin Product: kontact Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: coolm...@gmx.de Target Milestone: --- Application: kontact (5.4.2) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.11-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Added a new project in zanshin (0.4.1-1) additional Infos: zanshin uses KOrganizer-source as its backend KOrganizer (korganizer 16.12.2-1) has a file source (ical) -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4f3ef99900 (LWP 1360))] Thread 28 (Thread 0x7f4e16f44700 (LWP 1467)): #0 0x7f4f3ba274ed in read () at /usr/lib/libc.so.6 #1 0x7f4f2fc5eaa0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f4f2fc1a26e in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f4f2fc1a744 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f4f2fc1a8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f4f3c56606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f4f3c50f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f4f3c331a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f4f3c3366d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f4f31e04454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f4f3ba347df in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7f4e191e8700 (LWP 1440)): #0 0x7f4f3ba2b48d in poll () at /usr/lib/libc.so.6 #1 0x7f4f2fc1a7a6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f4f2fc1a8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f4f3c56606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f4f3c50f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f4f3c331a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f4f3c3366d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f4f31e04454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f4f3ba347df in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7f4e1a006700 (LWP 1437)): #0 0x7f4f3ba2b48d in poll () at /usr/lib/libc.so.6 #1 0x7f4f2fc1a7a6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f4f2fc1a8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f4f3c56606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f4f3c50f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f4f3c331a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f4f3c3366d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f4f31e04454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f4f3ba347df in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7f4e1b60e700 (LWP 1436)): #0 0x7f4f31e0a10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4f367f0dd9 in () at /usr/lib/libQt5WebEngineCore.so.5 #2 0x7f4f367f1409 in () at /usr/lib/libQt5WebEngineCore.so.5 #3 0x7f4f367f15c0 in () at /usr/lib/libQt5WebEngineCore.so.5 #4 0x7f4f367ee142 in () at /usr/lib/libQt5WebEngineCore.so.5 #5 0x7f4f31e04454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f4f3ba347df in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f4e1d7fb700 (LWP 1396)): #0 0x7f4f2fc19f14 in g_main_context_query () at /usr/lib/libglib-2.0.so.0 #1 0x7f4f2fc1a718 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f4f2fc1a8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f4f3c56606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f4f3c50f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f4f3c331a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f4f3c3366d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f4f31e04454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f4f3ba347df in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f4e24200700 (LWP 1390)): #0 0x7f4f3ba2b48d in poll () at /usr/lib/libc.so.6 #1 0x7f4f2fc1a7a6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f4f2fc1a8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f4f3c56606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f4f3c50f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f4f3c331a73 in
[kaddressbook] [Bug 376610] New: Name changes are not applied in either the names list or the person view
https://bugs.kde.org/show_bug.cgi?id=376610 Bug ID: 376610 Summary: Name changes are not applied in either the names list or the person view Product: kaddressbook Version: 5.2.3 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: nuor...@gmail.com CC: to...@kde.org Target Milestone: --- Created attachment 104091 --> https://bugs.kde.org/attachment.cgi?id=104091=edit Screenshot of KAddressBook showing the correct name only in "Edit Contact" window When updating names of people in KAddressBook the changes are saved and appear correctly in the edit window, but they stay the same in both the people list (the scroll list with the header "Name") and the contact view. In the screenshot you can see the person is displayed with "Ceausu", but in the "Edit Contact" window it is displayed with the corrected family name "Ceaușu". Seems similar to #371195, but not sure it's the same, as the other bug seems to request an editor feature. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 365608] Akregator crashes when shutting down
https://bugs.kde.org/show_bug.cgi?id=365608 --- Comment #5 from Alex <a...@polverini.org> --- After a reboot of the system the problem is gone. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 376130] Akregator crashes on quit
https://bugs.kde.org/show_bug.cgi?id=376130 --- Comment #4 from Alex <a...@polverini.org> --- It'd only for zeisty and to update it I would need to probably upgrade hundreds of other packages :-( -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 376130] Akregator crashes on quit
https://bugs.kde.org/show_bug.cgi?id=376130 --- Comment #2 from Alex <a...@polverini.org> --- Is it packaged yet? apt-cache policy akregator akregator: Installed: 4:16.04.3-0ubuntu2 Candidate: 4:16.04.3-0ubuntu2 Version table: *** 4:16.04.3-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages 90 http://it.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages 100 /var/lib/dpkg/status -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 376130] New: Akregator crashes on quit
https://bugs.kde.org/show_bug.cgi?id=376130 Bug ID: 376130 Summary: Akregator crashes on quit Product: akregator Version: 5.2.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: a...@polverini.org Target Milestone: --- I'm using akregator 5.2.3, with a full up to date kubuntu with KDE backports. Akregator crashes everytime I quit it, and so it loses all my read/unread feeds. Very annoying. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 364783] When url is clicked, messageviewer gets screwed
https://bugs.kde.org/show_bug.cgi?id=364783 --- Comment #2 from Alex Fiestas <afies...@kde.org> --- This only happens with hidpi apparently. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 347355] Starting akonadi
https://bugs.kde.org/show_bug.cgi?id=347355 Alex Fiestas <afies...@kde.org> changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #1 from Alex Fiestas <afies...@kde.org> --- Reported this long ago, no longer crashes. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 375410] New: Can't fetch email from oauth configured GMail account
https://bugs.kde.org/show_bug.cgi?id=375410
Bug ID: 375410
Summary: Can't fetch email from oauth configured GMail account
Product: Akonadi
Version: GIT (master)
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: IMAP resource
Assignee: chrig...@fastmail.fm
Reporter: afies...@kde.org
CC: kdepim-bugs@kde.org, vkra...@kde.org
Target Milestone: ---
After configuring the account via oauth, the resource does not seem to be able
to connect.
akonadi output:
Pass a valid window to KWallet::Wallet::openWallet().
org.kde.pim.kimap: sasl_client_start failed with: -4 "SASL(-4): no mechanism
available: No worthy mechs found"
org.kde.kgapi.raw: Requesting token refresh:
"client_id=554266.apps.googleusercontent.com_secret=mdT1T0gO_token=1/f1A_type=refresh_token"
org.kde.kgapi: Queued QUrl("https://accounts.google.com/o/oauth2/token;)
org.kde.kgapi: KGAPI2::AuthJob(0x236f7d0) Dispatching request to
QUrl("https://accounts.google.com/o/oauth2/token;)
org.kde.kgapi.raw:
"client_id=55404.apps.googleusercontent.com_secret=mdT1DjzohxN_token=1/f1AHBA_type=refresh_token"
org.kde.kgapi: Received reply from
QUrl("https://accounts.google.com/o/oauth2/token;)
org.kde.kgapi: Status code: 200
org.kde.kgapi.raw: "{\n \"access_token\" : \"["another deleted token"]",\n
\"expires_in\" : 3600,\n \"id_token\" : \"["DELETED TOKENHERE"]\",\n
\"token_type\" : \"Bearer\"\n}"
org.kde.kgapi:
Pass a valid window to KWallet::Wallet::openWallet().
qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on
non-plain connection
org.kde.pim.akonadicore: "QLocalSocket: Socket operation timed out"
"/tmp/akonadi-afiestas.Z3ui6I/akonadiserver-cmd.socket"
org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket: Socket operation
timed out"
org.kde.pim.akonadi_indexer_agent: Failed to fetch items: "Cannot connect to
the Akonadi service."
org.kde.pim.akonadi_indexer_agent: Indexing failed: ""
org.kde.pim.akonadicore: Invalid command, the world is going to end!
QIODevice::read (QLocalSocket): device not open
org.kde.pim.kimap: Connection to server lost 0
org.kde.pim.imapresource: Session login cancelled
org.kde.pim.kimap: Connection to server lost 0
org.kde.pim.imapresource: Session login cancelled
Pass a valid window to KWallet::Wallet::openWallet().
Pass a valid window to KWallet::Wallet::openWallet().
org.kde.pim.kimap: sasl_client_start failed with: -4 "SASL(-4): no mechanism
available: No worthy mechs found"
--
You are receiving this mail because:
You are on the CC list for the bug.
[Akonadi] [Bug 375102] New: New OAuth configuration is spooky.
https://bugs.kde.org/show_bug.cgi?id=375102 Bug ID: 375102 Summary: New OAuth configuration is spooky. Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: afies...@kde.org CC: kdepim-bugs@kde.org, vkra...@kde.org Target Milestone: --- Hi After upgrading to latest git I encountered two dialogs loading a website that said Google and asked me for my credentials. It is awesome that support for oauth is finally there but the dialog is really spooky because the url is not shown, I can't see if it is using SSL or not, etc. -- You are receiving this mail because: You are on the CC list for the bug.
[neon] [Bug 370498] KMail crashes when pressing SPACE while displaying a message
https://bugs.kde.org/show_bug.cgi?id=370498 --- Comment #3 from Alex Sidorenko <alexandre.sidore...@gmail.com> --- This was not really a bug in KDE but rather mismatched shared libraries... So Neon/User update of 15 Oct 2016 has fixed the problem as it provides KDE applications 16.08.2 and the new build obviously fixes the issue. Anyway, it is FIXED now -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 361676] Problem syncing my mailbox using Imap
https://bugs.kde.org/show_bug.cgi?id=361676 alex <a...@netecgc.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from alex <a...@netecgc.com> --- This can be closed now as is no longer an issue. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 364786] New: KMail crashes after selecting a contact in comopse Message
https://bugs.kde.org/show_bug.cgi?id=364786 Bug ID: 364786 Summary: KMail crashes after selecting a contact in comopse Message Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: afies...@kde.org KMail is hitting an assert when I select a contact in the "new email" composer. This happens everytime. Bt: #0 0x7128f295 in raise () from /usr/lib/libc.so.6 #1 0x712906da in abort () from /usr/lib/libc.so.6 #2 0x71f323ce in qt_message_fatal (context=..., message=) at /home/afiestas/kde5/qt5/qtbase/src/corelib/global/qlogging.cpp:1680 #3 QMessageLogger::fatal (this=this@entry=0x7fffd4d0, msg=msg@entry=0x721ce3e0 "ASSERT: \"%s\" in file %s, line %d") at /home/afiestas/kde5/qt5/qtbase/src/corelib/global/qlogging.cpp:793 #4 0x71f2dcae in qt_assert (assertion=, file=, line=) at /home/afiestas/kde5/qt5/qtbase/src/corelib/global/qglobal.cpp:3091 #5 0x7605649a in Akonadi::JobPrivate::handleResponse (this=0x3ccaa50, tag=5, response=...) at /home/afiestas/kde5/source/akonadi/src/core/jobs/job.cpp:69 #6 0x76017f0a in Akonadi::SessionPrivate::handleCommand (this=0x20f5e70, tag=5, cmd=...) at /home/afiestas/kde5/source/akonadi/src/core/session.cpp:143 #7 0x76019bcf in Akonadi::Session::qt_static_metacall (_o=0x3ce71a0, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7fff40b1aca0) at /home/afiestas/kde5/build/akonadi/src/core/moc_session.cpp:117 #8 0x7213ef41 in QObject::event (this=0x3ce71a0, e=) at /home/afiestas/kde5/qt5/qtbase/src/corelib/kernel/qobject.cpp:1263 #9 0x729e33ec in QApplicationPrivate::notify_helper (this=, receiver=0x3ce71a0, e=0x7fff40b1a9f0) at /home/afiestas/kde5/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3799 #10 0x729ea571 in QApplication::notify (this=0x7fffdec0, receiver=0x3ce71a0, e=0x7fff40b1a9f0) at /home/afiestas/kde5/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3556 #11 0x72114368 in QCoreApplication::notifyInternal2 (receiver=0x3ce71a0, event=event@entry=0x7fff40b1a9f0) at /home/afiestas/kde5/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:988 #12 0x721169bd in QCoreApplication::sendEvent (event=0x7fff40b1a9f0, receiver=) at /home/afiestas/kde5/qt5/qtbase/src/corelib/kernel/qcoreapplication.h:231 #13 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x626780) at /home/afiestas/kde5/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:1649 #14 0x72116e28 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at /home/afiestas/kde5/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:1503 #15 0x721655d3 in postEventSourceDispatch (s=0x670900) at /home/afiestas/kde5/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:276 #16 0x7fffdd87bdd7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #17 0x7fffdd87c040 in ?? () from /usr/lib/libglib-2.0.so.0 #18 0x7fffdd87c0ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #19 0x721659df in QEventDispatcherGlib::processEvents (this=0x670210, flags=...) at /home/afiestas/kde5/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:423 #20 0x721128ea in QEventLoop::exec (this=this@entry=0x7fffdd20, flags=..., flags@entry=...) at /home/afiestas/kde5/qt5/qtbase/src/corelib/kernel/qeventloop.cpp:210 #21 0x7211a9ed in QCoreApplication::exec () at /home/afiestas/kde5/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:1261 #22 0x0040486f in main (argc=1, argv=0x7fffe048) at /home/afiestas/kde5/source/kdepim/kmail/src/main.cpp:155 Reproducible: Always Steps to Reproduce: 1.Open KMAil 2.Click new email 3.Search for a contact 4.Select one of the contacts included in the result -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 364783] When url is clicked, messageviewer gets screwed
https://bugs.kde.org/show_bug.cgi?id=364783 --- Comment #1 from Alex Fiestas <afies...@kde.org> --- Created attachment 99703 --> https://bugs.kde.org/attachment.cgi?id=99703=edit Video with the behaviour -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 364783] New: When url is clicked, messageviewer gets screwed
https://bugs.kde.org/show_bug.cgi?id=364783 Bug ID: 364783 Summary: When url is clicked, messageviewer gets screwed Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: afies...@kde.org Whenever I click or open on an url, the messageviewer gets screwed, checkout the video. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 361676] Problem syncing my mailbox using Imap
https://bugs.kde.org/show_bug.cgi?id=361676 --- Comment #1 from alex <a...@netecgc.com> --- I am using Davmail to connect to my work exchange which was working with Thunderbird just fine. Thanks, Al -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 361676] New: Problem syncing my mailbox using Imap
https://bugs.kde.org/show_bug.cgi?id=361676 Bug ID: 361676 Summary: Problem syncing my mailbox using Imap Product: kmail2 Version: 4.14.10 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: a...@netecgc.com Error when syncing my inbox at about 30% says "There is currently no connection to the IMAP server" even though my internet has not dropped. Thanks, Al Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 353168] Akregator is unable to fetch favicons
https://bugs.kde.org/show_bug.cgi?id=353168 Alex Elsayed <eternal...@gmail.com> changed: What|Removed |Added CC||eternal...@gmail.com --- Comment #13 from Alex Elsayed <eternal...@gmail.com> --- Still broken here - tracked this down; the culprit seems to be src/feediconmanager.cpp as of 15.12.3 - line 60 adds a QDBusInterface member m_favIconsModule, line 76 initializes it as querying kded5 for the favicons module (which was never released, and was killed off due to moving into KIO), and lines 91 and 102 call methods on it. Tracked it down thanks to the error message on line 104. All line numbers are from the 15.12.3 release tarball. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990 Alex Potter <a...@alepot.org> changed: What|Removed |Added CC||a...@alepot.org --- Comment #12 from Alex Potter <a...@alepot.org> --- Created attachment 97927 --> https://bugs.kde.org/attachment.cgi?id=97927=edit Screenshot of kmail sieve manager dialog This bug exists on KMail 5.0.2 on Kubuntu 15.10 AMD 64. The login to sieve succeeds, data is returned, but is inaccessible to kmail, as can be seen in the attached screenshot -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990 --- Comment #13 from Alex Potter <a...@alepot.org> --- Version here is 15.08.2-0ubuntu1 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 352512] 5.0.xx after a crash, the restore session pops up twice then akregator crashes
https://bugs.kde.org/show_bug.cgi?id=352512 --- Comment #20 from Alex <a...@polverini.org> --- Unfortunately (k)ubuntu uses the old 15.08 version and has not prepared official updates so I can't test the new one, but I'm very happy to know it's getting better -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 352512] 5.0.xx after a crash, the restore session pops up twice then akregator crashes
https://bugs.kde.org/show_bug.cgi?id=352512 --- Comment #17 from Alex <a...@polverini.org> --- The only workaround solution I found is to: - save the file ~/.local/share/akregator/data/feeds.opml BEFORE running again akregator after a crash - run akregator and follow the broken recovery that instead of recoverying deletes the feed list - close akregator - reput in place the feeds.opml file - run akregator again -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 352512] 5.0.xx after a crash, the restore session pops up twice then akregator crashes
https://bugs.kde.org/show_bug.cgi?id=352512 Alex <a...@polverini.org> changed: What|Removed |Added CC||a...@polverini.org --- Comment #12 from Alex <a...@polverini.org> --- I'm experiencing the same issue -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 354472] New: Kolab resource crashed in Akonadi::ResourceBasePrivate::slotAttributeRetrievalCollectionFetchDone
https://bugs.kde.org/show_bug.cgi?id=354472
Bug ID: 354472
Summary: Kolab resource crashed in
Akonadi::ResourceBasePrivate::slotAttributeRetrievalCo
llectionFetchDone
Product: Akonadi
Version: GIT (master)
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: Kolab Resource
Assignee: kdepim-bugs@kde.org
Reporter: alex.me...@kde.org
CC: kdepim-bugs@kde.org
The kolab resource crashed in the background while I wasn't doing anything (I
wasn't even near the computer). It looks like a Akonadi::CollectionFetchJob ran
and didn't manage to get any collections (for whatever reason).
Reproducible: Didn't try
FWIW, GDB dump of the job's private class (lots of empty QVectors):
(gdb) print *(Akonadi::CollectionFetchJobPrivate*)(fetchJob->d_ptr)
$6 = { = {_vptr.JobPrivate = 0x7f02598fcae8 , q_ptr = 0x1a5e8f0, mParentJob = 0x0,
mCurrentSubJob = 0x0, mTag = 6361,
mSession = 0x18da8c0, mWriteFinished = false, mStarted = true}, mType =
Akonadi::CollectionFetchJob::Base, mBase = {d_ptr = {d = 0x18914d0}}, mBaseList
= {
d = 0x7f0250b4e160 }, mCollections = {d =
0x7f0250b4e160 }, mScope = {d = {d = 0x19e8f00}},
mPendingCollections = {
d = 0x7f0250b4e160 }, mEmitTimer = 0x1a4ae80,
mBasePrefetch = false, mPrefetchList = {d = 0x7f0250b4e160
}}
Application: akonadi_kolab_resource (akonadi_kolab_resource), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0240a23840 (LWP 16259))]
Thread 8 (Thread 0x7f023de31700 (LWP 16299)):
#0 0x7f024fc2e18d in poll () from /usr/lib/libc.so.6
#1 0x7f024a6efae2 in ?? () from /usr/lib/libxcb.so.1
#2 0x7f024a6f1757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3 0x7f02407501e1 in QXcbEventReader::run (this=0x1884840) at
qxcbconnection.cpp:1229
#4 0x7f0250842065 in QThreadPrivate::start (arg=0x1884840) at
thread/qthread_unix.cpp:331
#5 0x7f024ef4c4a4 in start_thread () from /usr/lib/libpthread.so.0
#6 0x7f024fc3713d in clone () from /usr/lib/libc.so.6
Thread 7 (Thread 0x7f023cb34700 (LWP 16347)):
#0 0x7f0249d785f9 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0
#1 0x7f0249d339fc in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#2 0x7f0249d33f60 in ?? () from /usr/lib/libglib-2.0.so.0
#3 0x7f0249d340cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4 0x7f0250ae14be in QEventDispatcherGlib::processEvents
(this=0x7f0238c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5 0x7f0250a67e42 in QEventLoop::processEvents (this=0x7f023cb33d20,
flags=...) at kernel/qeventloop.cpp:128
#6 0x7f0250a6813e in QEventLoop::exec (this=0x7f023cb33d20, flags=...) at
kernel/qeventloop.cpp:204
#7 0x7f025083a814 in QThread::exec (this=0x191af90) at
thread/qthread.cpp:503
#8 0x7f025083a9b6 in QThread::run (this=0x191af90) at
thread/qthread.cpp:570
#9 0x7f0250842065 in QThreadPrivate::start (arg=0x191af90) at
thread/qthread_unix.cpp:331
#10 0x7f024ef4c4a4 in start_thread () from /usr/lib/libpthread.so.0
#11 0x7f024fc3713d in clone () from /usr/lib/libc.so.6
Thread 6 (Thread 0x7f0237fff700 (LWP 16350)):
#0 0x7f0250ae0c13 in postEventSourcePrepare (s=0x7f022c0012d0,
timeout=0x7f0237ffeae4) at kernel/qeventdispatcher_glib.cpp:254
#1 0x7f0249d3354d in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#2 0x7f0249d33eeb in ?? () from /usr/lib/libglib-2.0.so.0
#3 0x7f0249d340cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4 0x7f0250ae14be in QEventDispatcherGlib::processEvents
(this=0x7f022c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5 0x7f0250a67e42 in QEventLoop::processEvents (this=0x7f0237ffed20,
flags=...) at kernel/qeventloop.cpp:128
#6 0x7f0250a6813e in QEventLoop::exec (this=0x7f0237ffed20, flags=...) at
kernel/qeventloop.cpp:204
#7 0x7f025083a814 in QThread::exec (this=0x190e250) at
thread/qthread.cpp:503
#8 0x7f025083a9b6 in QThread::run (this=0x190e250) at
thread/qthread.cpp:570
#9 0x7f0250842065 in QThreadPrivate::start (arg=0x190e250) at
thread/qthread_unix.cpp:331
#10 0x7f024ef4c4a4 in start_thread () from /usr/lib/libpthread.so.0
#11 0x7f024fc3713d in clone () from /usr/lib/libc.so.6
Thread 5 (Thread 0x7f0236dee700 (LWP 16404)):
#0 0x7ffc4d9dd929 in ?? ()
#1 0x7ffc4d9ddc55 in clock_gettime ()
#2 0x7f024fc43d36 in clock_gettime () from /usr/lib/libc.so.6
#3 0x7f025093cae2 in qt_clock_gettime (clock=1, ts=0x7f0236ded960) at
tools/qelapsedtimer_unix.cpp:105
#4 0x7f025093cb90 in do_gettime (sec=0x7f0236ded998, frac=0x7f0236ded990)
at tools/qelapsedtimer_unix.cpp:156
#5 0x7f025093cbc4 in qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#6 0x7f0250ade63a
[kontact] [Bug 354401] New: Kontact crashed when closing and reopening
https://bugs.kde.org/show_bug.cgi?id=354401 Bug ID: 354401 Summary: Kontact crashed when closing and reopening Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: alex.me...@kde.org Application: kontact (5.0.46 pre) (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.2.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I closed Kontact, then immediately opened it again. It seems as if the previous instance hadn't finished exiting, and crashed in the background. The new instance then started just fine. Looking at the backtrace, I think there was a bit of a race condition going on. I guess KMail's mainwindow had been destroyed, then the Activate signal came in over D-Bus from the new instance because of the "unique application" code. The first thing KMail's MainWindow class does in its constructor is create a ServiceStarter, which is a subclass of the singleton KdbusServiceStarter. Since there was a previous MainWindow, and hence a previous ServiceStarter, this singleton already exists. So the new one hits an assert in the KdbusServiceStarter constructor. Not sure what a sensible solution for this might be. I'm not sure the "subclassing" method of extending KDBusServiceStarter is sane, for all that it is suggested by the documentation of that class. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f26bb464840 (LWP 3466))] Thread 17 (Thread 0x7f26b8662700 (LWP 3467)): #0 0x7f26ceba018d in poll () from /usr/lib/libc.so.6 #1 0x7f26c5794ae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f26c5796757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f26bb1911e1 in QXcbEventReader::run (this=0x1267a60) at qxcbconnection.cpp:1229 #4 0x7f26cf7b4065 in QThreadPrivate::start (arg=0x1267a60) at thread/qthread_unix.cpp:331 #5 0x7f26cd8aa4a4 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f26ceba913d in clone () from /usr/lib/libc.so.6 Thread 16 (Thread 0x7f266ef8c700 (LWP 3468)): #0 0x7f26cf9da59b in QFlags::QFlags (this=0x7f266ef8ba10, f=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:113 #1 0x7f26cfa4fccf in QFlags::operator& (this=0x7f2668002f10, f=QEventLoop::X11ExcludeTimers) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #2 0x7f26cfa52860 in timerSourcePrepareHelper (src=0x7f2668002e70, timeout=0x7f266ef8bae4) at kernel/qeventdispatcher_glib.cpp:127 #3 0x7f26cfa52a37 in timerSourcePrepare (source=0x7f2668002e70, timeout=0x7f266ef8bae4) at kernel/qeventdispatcher_glib.cpp:160 #4 0x7f26cb26d54d in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #5 0x7f26cb26deeb in ?? () from /usr/lib/libglib-2.0.so.0 #6 0x7f26cb26e0cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #7 0x7f26cfa534be in QEventDispatcherGlib::processEvents (this=0x7f26680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #8 0x7f26cf9d9e42 in QEventLoop::processEvents (this=0x7f266ef8bd20, flags=...) at kernel/qeventloop.cpp:128 #9 0x7f26cf9da13e in QEventLoop::exec (this=0x7f266ef8bd20, flags=...) at kernel/qeventloop.cpp:204 #10 0x7f26cf7ac814 in QThread::exec (this=0x13f22d0) at thread/qthread.cpp:503 #11 0x7f26cf7ac9b6 in QThread::run (this=0x13f22d0) at thread/qthread.cpp:570 #12 0x7f26cf7b4065 in QThreadPrivate::start (arg=0x13f22d0) at thread/qthread_unix.cpp:331 #13 0x7f26cd8aa4a4 in start_thread () from /usr/lib/libpthread.so.0 #14 0x7f26ceba913d in clone () from /usr/lib/libc.so.6 Thread 15 (Thread 0x7f266c99d700 (LWP 3469)): #0 0x7f26cd8b007f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f26d69869be in WTF::ThreadCondition::wait (this=0x1613e78, mutex=...) at wtf/ThreadingPthreads.cpp:378 #2 0x7f26d667974a in JSC::BlockAllocator::blockFreeingThreadMain (this=0x1613c68) at heap/BlockAllocator.cpp:139 #3 0x7f26d667965c in JSC::BlockAllocator::blockFreeingThreadStartFunc (blockAllocator=0x1613c68) at heap/BlockAllocator.cpp:115 #4 0x7f26d696c986 in WTF::threadEntryPoint (contextData=0x1552060) at wtf/Threading.cpp:69 #5 0x7f26d69861df in WTF::wtfThreadEntryPoint (param=0x13b1a80) at wtf/ThreadingPthreads.cpp:195 #6 0x7f26cd8aa4a4 in start_thread () from /usr/lib/libpthread.so.0 #7 0x7f26ceba913d in clone () from /usr/lib/libc.so.6 Thread 14 (Thread 0x7f2667fff700 (LWP 3470)): #0 0x7f26cd8b007f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f26d69869be in
[kmail2] [Bug 259720] KMail crashed when attempting to delete the same message multiple times
https://bugs.kde.org/show_bug.cgi?id=259720 --- Comment #4 from Alex Merry <alex.me...@kde.org> --- I haven't seen this in the last few years. Feel free to close it as unreproducible. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 259798] Assert in IMAP resource ("!set.toImapSequenceSet().trimmed().isEmpty()") [KIMAP::FetchJob::setSequenceSet, RetrieveItemTask::triggerFetchJob, RetrieveItemTask::onSelectDone]
https://bugs.kde.org/show_bug.cgi?id=259798 --- Comment #8 from Alex Merry <alex.me...@kde.org> --- I haven't seen this issue for a few years now. I'm happy for this bug to be closed as unreproducible. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 354056] New: Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 Bug ID: 354056 Summary: Deleted emails stay, but greyed out Product: Akonadi Version: GIT (master) Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: alex.me...@kde.org CC: kdepim-bugs@kde.org, vkra...@kde.org With one of my IMAP accounts (but not the other), when I delete emails, they disappear from the message list, and reappear in the trash folder (on the same server) as expected. However, when I switch back to the original folder, the messages have reappeared there, but greyed out, and unselectable. Roundcube webmail (0.9.5) also displays these messages as grey and with a circle-with-a-line-through-it symbol in the status column (but there I can select them and delete them properly). This also happens when I try to empty the trash folder. Reproducible: Always Steps to Reproduce: 1. Delete an email from the inbox 2. Switch to a different folder 3. Switch back to the inbox Actual Results: Email has reappeared, but greyed out. Expected Results: Email stays gone. It happens whether or not I have offline emails enabled for the account. Note that I don't have a particularly large number of emails in my inbox (where I've observed this behaviour). Possibly relevant is this from akonadiserver.error: DATABASE ERROR: Error code: 1452 DB error: "Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`parttable`, CONSTRAINT `parttable_ibfk_1` FOREIGN KEY (`pimItemId`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE)" Error text: "Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`parttable`, CONSTRAINT `parttable_ibfk_1` FOREIGN KEY (`pimItemId`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL3: Unable to execute statement" Query: "INSERT INTO PartTable (pimItemId, partTypeId, data, datasize, version, external) VALUES (:0, :1, :2, :3, :4, :5)" Akonadi is also using a ridiculous amount of bandwidth when communicating with the IMAP server (in August, when I also observed this bug, it used nearly 30Gb over the month, and I have at most a couple hundred Mb of emails on the server). This may or may not be related. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 --- Comment #1 from Alex Merry <alex.me...@kde.org> --- Possibly related: Bug 299422 (although this is about the SEEN flag, rather than deleting) Bug 321357 (although my issue doesn't resolve itself by using roundcube to view my email, or by restarting anything) Bug 324135 (likewise). -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 --- Comment #2 from Alex Merry <alex.me...@kde.org> --- The server greeting is * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2011 Double Precision, Inc. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 292418] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=292418 Alex Brandt alund...@alunduil.com changed: What|Removed |Added CC||alund...@alunduil.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail] [Bug 244443] When renaming a folder, filters are not updated accordingly
https://bugs.kde.org/show_bug.cgi?id=23 Alex Richardson arichardson@gmail.com changed: What|Removed |Added Resolution|UNMAINTAINED|FIXED --- Comment #3 from Alex Richardson arichardson@gmail.com --- Pretty sure this is no longer valid. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail] [Bug 240350] KMail imap connection freezes in response to broken response
https://bugs.kde.org/show_bug.cgi?id=240350 Alex SchiFFer alex.schif...@gmail.com changed: What|Removed |Added CC||alex.schif...@gmail.com --- Comment #13 from Alex SchiFFer alex.schif...@gmail.com --- kubuntu 14.04 kmail 4.14.3 error is present for sent dir (while interacting with exchange server via imap) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kleopatra] [Bug 340146] IMPROVEMENT1: Manage subkeys
https://bugs.kde.org/show_bug.cgi?id=340146 Alex Brandt alund...@alunduil.com changed: What|Removed |Added CC||alund...@alunduil.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990 alex jus...@gmx.de changed: What|Removed |Added CC||jus...@gmx.de --- Comment #11 from alex jus...@gmx.de --- Confirmed the bug still exists: Qt: 4.8.6 KDE: 4.14.3 KMail: 4.14.3 So switching from LOGIN to PLAIN worked for me. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 341906] New: imap crash accepting bad certificate dialog after a some period of time
https://bugs.kde.org/show_bug.cgi?id=341906 Bug ID: 341906 Summary: imap crash accepting bad certificate dialog after a some period of time Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: frol...@froller.net CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.14) KDE Platform Version: 4.14.3 Qt Version: 4.8.6 Operating System: Linux 3.17.4-200.fc20.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: 1. Connecе to IMAP server with bad cert 2. Do not acccept certificate just leave dialog open for a minute or two 3. Choose 'Accept' / 'This session only' 4. ... 5. CRASH - Custom settings of the application: STARTTLS + bad server certificate The crash can be reproduced every time. -- Backtrace: Application: froller.net типа Почтовый сервер IMAP (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7fdb95abe8c0 (LWP 22682))] Thread 2 (Thread 0x7fdb83fff700 (LWP 22795)): #0 0x003a7c6ea71d in poll () from /lib64/libc.so.6 #1 0x003a7ea495b4 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x003a7ea496dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fdb975e841e in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #4 0x7fdb975b836f in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #5 0x7fdb975b86bd in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #6 0x7fdb974ace5f in QThread::exec() () from /lib64/libQtCore.so.4 #7 0x7fdb974af69f in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #8 0x003a7c207ee5 in start_thread () from /lib64/libpthread.so.0 #9 0x003a7c6f4b8d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fdb95abe8c0 (LWP 22682)): [KCrash Handler] #5 0x7fdb975c4172 in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from /lib64/libQtCore.so.4 #6 0x003aab044a38 in KIMAP::SessionThread::sslErrorHandlerResponse(bool) () from /lib64/libkimap.so.4 #7 0x7fdb975d28ee in QObject::event(QEvent*) () from /lib64/libQtCore.so.4 #8 0x7fdb9691ce6c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQtGui.so.4 #9 0x7fdb969237c5 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQtGui.so.4 #10 0x003a8be4a4fa in KApplication::notify(QObject*, QEvent*) () from /lib64/libkdeui.so.5 #11 0x7fdb975b98dd in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQtCore.so.4 #12 0x7fdb975bcac5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQtCore.so.4 #13 0x7fdb975e8c7e in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQtCore.so.4 #14 0x003a7ea492a6 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #15 0x003a7ea49628 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #16 0x003a7ea496dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #17 0x7fdb975e83fe in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #18 0x7fdb969bec46 in QGuiEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtGui.so.4 #19 0x7fdb975b836f in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #20 0x7fdb975b86bd in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #21 0x7fdb975bdd89 in QCoreApplication::exec() () from /lib64/libQtCore.so.4 #22 0x003a99f8a09c in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /lib64/libakonadi-kde.so.4 #23 0x00418c23 in int Akonadi::ResourceBase::initImapResource(int, char**) () #24 0x003a7c621d65 in __libc_start_main () from /lib64/libc.so.6 #25 0x00418ad5 in _start () The reporter indicates this bug may be a duplicate of or related to bug 332830. Possible duplicates by query: bug 332830. Reported using DrKonqi -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org
[kmail2] [Bug 315726] KMail 2 doesn't accept subkeys for signing and encrypting
https://bugs.kde.org/show_bug.cgi?id=315726 Alex Brandt alund...@alunduil.com changed: What|Removed |Added CC||alund...@alunduil.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 Alex Wright bugzi...@wright-family.me.uk changed: What|Removed |Added CC||bugzi...@wright-family.me.u ||k -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 335642] New: KMail freezes when loading folders
https://bugs.kde.org/show_bug.cgi?id=335642 Bug ID: 335642 Summary: KMail freezes when loading folders Classification: Unclassified Product: kmail2 Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: afies...@kde.org I guess this is an error in akonadi libs but it might be KMail doing an async use of them as well... These are some backtraces of a gdb attached to a KMail with a complete frozen GUI. #0 0x7fce74cc9f5e in Akonadi::NotificationMessageHelpers::appendAndCompressImplQListAkonadi::NotificationMessageV3, Akonadi::NotificationMessageV3 ( list=..., msg=...) at /home/afiestas/kde4/source/akonadi/libs/notificationmessagev2_p_p.h:53 #1 0x7fce74cc76eb in Akonadi::NotificationMessageV3::appendAndCompress (list=..., msg=...) at /home/afiestas/kde4/source/akonadi/libs/notificationmessagev3.cpp:65 #2 0x7fce81b022c9 in Akonadi::MonitorPrivate::translateAndCompress (this=optimized out, notificationQueue=..., msg=...) at /home/afiestas/kde4/source/kdepimlibs/akonadi/monitor_p.cpp:578 #3 0x7fce81b02713 in Akonadi::MonitorPrivate::slotNotify (this=0xf48150, msgs=...) at /home/afiestas/kde4/source/kdepimlibs/akonadi/monitor_p.cpp:668 #4 0x7fce81a61471 in Akonadi::ChangeRecorderPrivate::slotNotify (this=0xf48150, msgs=...) at /home/afiestas/kde4/source/kdepimlibs/akonadi/changerecorder_p.cpp:53 #5 0x7fce81af97d4 in Akonadi::Monitor::qt_static_metacall (_o=0xf9e5f0, _c=optimized out, _id=optimized out, _a=0x7fff37d29970) at /home/afiestas/kde4/build/kdepimlibs/akonadi/moc_monitor.cpp:177 #6 0x7fce7ef99637 in QMetaObject::activate (sender=0xfc4b30, m=0x7fce81ca4400 Akonadi::NotificationSource::staticMetaObject, local_signal_index=0, argv=0x7fff37d29970) at /home/afiestas/kde4/source/qt/src/corelib/kernel/qobject.cpp:3567 #7 0x7fce81ba7e4a in notifyV3 (this=optimized out, _t1=...) at /home/afiestas/kde4/build/kdepimlibs/akonadi/moc_notificationsource_p.cpp:98 #8 Akonadi::NotificationSource::qt_static_metacall (_o=0xfc4b30, _c=optimized out, _id=optimized out, _a=0x7fff37d29d10) at /home/afiestas/kde4/build/kdepimlibs/akonadi/moc_notificationsource_p.cpp:49 #9 0x7fce7ef99637 in QMetaObject::activate (sender=0x1018420, m=0x7fce81ca39a0 OrgFreedesktopAkonadiNotificationSourceInterface::staticMetaObject, local_signal_index=10, argv=0x7fff37d29d10) at /home/afiestas/kde4/source/qt/src/corelib/kernel/qobject.cpp:3567 #10 0x7fce81b9eba7 in ignoredSessionsChanged (this=optimized out) at /home/afiestas/kde4/build/kdepimlibs/akonadi/notificationsourceinterface.moc:201 #11 OrgFreedesktopAkonadiNotificationSourceInterface::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at /home/afiestas/kde4/build/kdepimlibs/akonadi/notificationsourceinterface.moc:109 #12 0x7fce81b9f742 in OrgFreedesktopAkonadiNotificationSourceInterface::qt_metacall (this=0x1018420, _c=optimized out, _id=10, _a=0x7fff37d2a068) at /home/afiestas/kde4/build/kdepimlibs/akonadi/notificationsourceinterface.moc:192 #13 0x7fce7f399747 in QDBusConnectionPrivate::deliverCall (this=0xd55fc0, object=0x1018420, msg=..., metaTypes=..., slotIdx=15) at /home/afiestas/kde4/source/qt/src/dbus/qdbusintegrator.cpp:950 #14 0x7fce7f3b7a2e in QDBusCallDeliveryEvent::placeMetaCall (this=0x1bd14970, object=0x1018420) at /home/afiestas/kde4/source/qt/src/dbus/qdbusintegrator_p.h:103 #15 0x7fce7ef92a80 in QObject::event (this=0x1018420, e=0x1bd14970) at /home/afiestas/kde4/source/qt/src/corelib/kernel/qobject.cpp:1222 #16 0x7fce7fb0461f in QApplicationPrivate::notify_helper (this=0xd79860, receiver=0x1018420, e=0x1bd14970) at /home/afiestas/kde4/source/qt/src/gui/kernel/qapplication.cpp:4565 #17 0x7fce7fb06bde in QApplication::notify (this=0x7fff37d2b6e0, receiver=0x1018420, e=0x1bd14970) at /home/afiestas/kde4/source/qt/src/gui/kernel/qapplication.cpp:3947 #18 0x7fce83629541 in KApplication::notify (this=0x7fff37d2b6e0, receiver=0x1018420, event=0x1bd14970) at /home/afiestas/kde4/source/kdelibs/kdeui/kernel/kapplication.cpp:311 #19 0x7fce7ef72556 in QCoreApplication::notifyInternal (this=0x7fff37d2b6e0, receiver=0x1018420, event=0x1bd14970) at /home/afiestas/kde4/source/qt/src/corelib/kernel/qcoreapplication.cpp:953 #20 0x7fce7ef7684a in QCoreApplication::sendEvent (receiver=0x1018420, event=0x1bd14970) at /home/afiestas/kde4/build/qt/src/corelib/../../include/QtCore/../../../../source/qt/src/corelib/kernel/qcoreapplication.h:231 #21 0x7fce7ef73977 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xccb220) at /home/afiestas/kde4/source/qt/src/corelib/kernel/qcoreapplication.cpp:1577 ---Type return to
[kmail2] [Bug 335642] KMail freezes when loading folders
https://bugs.kde.org/show_bug.cgi?id=335642 --- Comment #1 from Alex Fiestas afies...@kde.org --- After 6h running trying to load a folder I have killed KMail, the backtrace was still similar. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 246146] Mail list columns width shrink when sorted or view changed
https://bugs.kde.org/show_bug.cgi?id=246146 Alex Merry alex.me...@kde.org changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED CC||alex.me...@kde.org Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #5 from Alex Merry alex.me...@kde.org --- I can reproduce this with standalone KMail 4.13.1, using kdelibs 4.13.1, on ArchLinux (Qt 4.8.6). As with the others, I have the message list on the left (under the folder list), and the message pane on the right. I also have a very small screen real estate (1024x600). The columns shrink whenever I change the sorting (by clicking a column header) or change mail directory. I don't recall having this issue even a few months ago (I don't use email much on this machine, so I'm not sure quite what the timing was). I'm going to try playing around with configuration settings, and possibly building a local copy of KMail and/or kdepimlibs and putting debug statements in. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 246146] Mail list columns width shrink when sorted or view changed
https://bugs.kde.org/show_bug.cgi?id=246146 --- Comment #6 from Alex Merry alex.me...@kde.org --- The precise bit of my kmailrc that seems to be causing issues is: [MessageListView::Themes] Count=3 Set0=cafe100200180031003300310039003500360030003200380035002d0039000e0043006c0061007300730069006300600041002000730069006d0070006c0065002c0020006200610063006b0077006100720064007300200063006f006d00700061007400690062006c0065002c002000730069006e0067006c006500200072006f00770020007400680065006d0065001019000100000700100011000e005300750062006a0065006300740106000100020152000f001400530061006e007300200053006500720069006640220001003210006401000015000a0008001400530061006e007300200053006500720069006640220001004b10006401000001000700480015001400530061006e00730020005300650072006900664022000100321000640100004a00080001001400530061006e00730020005300650072006900664022fff f000100321000640100014a00170001001400530061006e00730020005300650072006900664022000100321000640100004800180001001400530061006e00730020005300650072006900664022000100321000640100004a00110001001400530061006e00730020005300650072006900664022000100321000640100004a0011001400530061006e00730020005300650072006900664022000100321000640100002d0001001400530061006e0073002000530065007200690066402200010032100064010000010013001e00530065006e006400650072002f005200650063006500690076006500720101000300010001000d0003001400530061006e00730020005300650072006900664022 0001003210006401000001000e000c00530065006e006400650072000400010001000d0004001400530061006e00730020005300650072006900664022000100321000640100001000520065006300650069007600650072000500010001000d0005001400530061006e0073002000530065007200690066402200010032100064010000080044006100740065010100010001001d0002001400530061006e00730020005300650072006900664022000100321000640100000100070020004d006f0073007400200052006500630065006e007400200044006100740065000200010001001d0014001400530061006e007300200053006500720069006640220 00000010032100064010000010001001d0014001400530061006e00730020005300650072006900664022000100321000640100000800530069007a0065000700010001000d0006001400530061006e007300200053006500720069006640220001003210006401000014004100740074006100630068006d0065006e0074001e006d00610069006c002d006100740074006100630068006d0065006e007400010001004a00080002001400530061006e0073002000530065007200690066402200010032100064010000010367000c0055006e0072006500610064001e006d00610069006c002d0075006e0072006500610064002d006e00650077000900010001004800070002001400530061006e007300 20005300650072006900664022000100321000640100000e005200650070006c0069006500640018006d00610069006c002d007200650070006c00690065006400010001004a00090002001400530061006e0073002000530065007200690066402200010032100064010000120049006d0070006f007200740061006e007400200065006d0062006c0065006d002d0069006d0070006f007200740061006e007400010001014a000c0002001400530061006e0073002000530065007200690066402200010032100064010000160041006300740069006f0
[kmail2] [Bug 223034] cannot send mail to distribution list
https://bugs.kde.org/show_bug.cgi?id=223034 Alex Ball a.b...@ukoln.ac.uk changed: What|Removed |Added CC||a.b...@ukoln.ac.uk -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 333850] Kontact has crashed on opening Kmail part 4.13
https://bugs.kde.org/show_bug.cgi?id=333850 --- Comment #1 from Alex Minton alex...@gmail.com --- Created attachment 86327 -- https://bugs.kde.org/attachment.cgi?id=86327action=edit New crash information added by DrKonqi kontact (4.13) on KDE Platform 4.13.0 using Qt 4.8.5 - What I was doing when the application crashed: Now I have tried to open KNotes right after the migration. Very similar result -- Backtrace (Reduced): #7 0x7f2265c1dea9 in MailCommon::Kernel::folderIsTemplates (this=optimized out, col=...) at /usr/src/debug/kdepim-4.13.0/mailcommon/kernel/mailkernel.cpp:277 #8 0x7f226602f9b0 in KMail::MessageActions::updateActions (this=0x2a2c4e0) at /usr/src/debug/kdepim-4.13.0/kmail/messageactions.cpp:271 #9 0x7f2266031a79 in KMail::MessageActions::setCurrentMessage (this=optimized out, msg=..., items=...) at /usr/src/debug/kdepim-4.13.0/kmail/messageactions.cpp:236 #10 0x7f22660024c5 in KMMainWidget::updateMessageActions (this=this@entry=0x283a970, fast=fast@entry=false) at /usr/src/debug/kdepim-4.13.0/kmail/kmmainwidget.cpp:3803 #11 0x7f22660031ba in KMMainWidget::initializeFilterActions (this=0x283a970) at /usr/src/debug/kdepim-4.13.0/kmail/kmmainwidget.cpp:4317 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 333850] Kontact has crashed on opening Kmail part 4.13
https://bugs.kde.org/show_bug.cgi?id=333850 Alex Minton alex...@gmail.com changed: What|Removed |Added CC||alex...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 333850] New: Kontact has crashed on opening Kmail part 4.13
https://bugs.kde.org/show_bug.cgi?id=333850 Bug ID: 333850 Summary: Kontact has crashed on opening Kmail part 4.13 Classification: Unclassified Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: alex...@gmail.com Application: kontact (4.13) KDE Platform Version: 4.13.0 Qt Version: 4.8.5 Operating System: Linux 3.14.1-1.geafcebd-desktop x86_64 Distribution: openSUSE 13.1 (Bottle) (x86_64) -- Information about the crash: - What I was doing when the application crashed: This may be connected with my recent update to 4.13 (this is the 1st session after reboot) Kmail systray icon kept telling me I had 1 unread message in my box, while there was none. After re-checking for new mails twice I have opened Kontact window once again and clicked on Kmail icon, but the whole app has just crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7fc13fbf08c0 (LWP 1537))] Thread 5 (Thread 0x7fc138c1a700 (LWP 1570)): #0 0x003bb640c0af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x003bd3480f76 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x003bd3480fa9 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x003bb64080db in start_thread () from /lib64/libpthread.so.0 #4 0x003bb58e790d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fc0f82ff700 (LWP 1612)): #0 0x003bb640c0af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x003bd31f32cd in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x003bd34a8ad6 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x003bb64080db in start_thread () from /lib64/libpthread.so.0 #4 0x003bb58e790d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fc0f5957700 (LWP 1705)): #0 0x003bb58deb3d in poll () from /lib64/libc.so.6 #1 0x003bb804b604 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x003bb804b70c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x003bbd1add76 in QEventDispatcherGlib::processEvents (this=0x7fc0e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #4 0x003bbd17fd0f in QEventLoop::processEvents (this=this@entry=0x7fc0f5956d20, flags=...) at kernel/qeventloop.cpp:149 #5 0x003bbd180005 in QEventLoop::exec (this=this@entry=0x7fc0f5956d20, flags=...) at kernel/qeventloop.cpp:204 #6 0x003bbd07efef in QThread::exec (this=optimized out) at thread/qthread.cpp:536 #7 0x003bbd08168f in QThreadPrivate::start (arg=0x2349cf0) at thread/qthread_unix.cpp:338 #8 0x003bb64080db in start_thread () from /lib64/libpthread.so.0 #9 0x003bb58e790d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fc0e08aa700 (LWP 2094)): #0 0x003bb640b595 in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0 #1 0x003bb808b2c1 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #2 0x003bb804b4bd in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x003bb804b70c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x003bbd1add76 in QEventDispatcherGlib::processEvents (this=0x7fc0d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #5 0x003bbd17fd0f in QEventLoop::processEvents (this=this@entry=0x7fc0e08a9ce0, flags=...) at kernel/qeventloop.cpp:149 #6 0x003bbd180005 in QEventLoop::exec (this=this@entry=0x7fc0e08a9ce0, flags=...) at kernel/qeventloop.cpp:204 #7 0x003bbd07efef in QThread::exec (this=this@entry=0x30073a0) at thread/qthread.cpp:536 #8 0x003bbd161513 in QInotifyFileSystemWatcherEngine::run (this=0x30073a0) at io/qfilesystemwatcher_inotify.cpp:256 #9 0x003bbd08168f in QThreadPrivate::start (arg=0x30073a0) at thread/qthread_unix.cpp:338 #10 0x003bb64080db in start_thread () from /lib64/libpthread.so.0 #11 0x003bb58e790d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fc13fbf08c0 (LWP 1537)): [KCrash Handler] #6 0x003bdf066ea6 in MailCommon::Kernel::folderIsTemplates (this=optimized out, col=...) at /usr/src/debug/kdepim-4.13.0/mailcommon/kernel/mailkernel.cpp:277 #7 0x003be090d9b0 in KMail::MessageActions::updateActions (this=0x2b76af0) at /usr/src/debug/kdepim-4.13.0/kmail/messageactions.cpp:271 #8 0x003be090fa79 in KMail::MessageActions::setCurrentMessage (this=optimized out, msg=..., items=...) at /usr/src/debug/kdepim-4.13.0/kmail/messageactions.cpp:236 #9 0x003be08e04c5 in KMMainWidget::updateMessageActions (this=this@entry=0x298c5e0, fast=fast@entry=false) at /usr/src/debug/kdepim-4.13.0/kmail/kmmainwidget.cpp:3803 #10 0x003be08e11ba in KMMainWidget::initializeFilterActions (this=0x298c5e0) at /usr/src/debug/kdepim
[kmail2] [Bug 330849] mail account in kontact recieves mail, but doesn't send. network unreachable
https://bugs.kde.org/show_bug.cgi?id=330849 --- Comment #2 from Alex Muehle mue...@gmx.org --- sad: I deleted the kde pim completely -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 331091] New: Crashes when marking as read folders too fast
https://bugs.kde.org/show_bug.cgi?id=331091 Bug ID: 331091 Summary: Crashes when marking as read folders too fast Classification: Unclassified Product: kontact Version: 4.13 pre Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: afies...@kde.org Application: kontact (4.13 pre) KDE Platform Version: 4.12.60 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 3.13.2-2-ARCH x86_64 Distribution: Arch Linux -- Information about the crash: There are a few mailing list I mark as read after reading all the subjects of the unread emails (since that's the only part I'm interested about). If I mark as read too many folders fast enough kontact will crash. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library /usr/lib/libthread_db.so.1. To enable execution of this file add add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.19-gdb.py line to your configuration file /home/afiestas/.gdbinit. To completely disable this security protection add set auto-load safe-path / line to your configuration file /home/afiestas/.gdbinit. For more information about this security protection see the Auto-loading safe path section in the GDB manual. E.g., run from the shell: info (gdb)Auto-loading safe path [Current thread is 1 (Thread 0x7eff4850c7c0 (LWP 24214))] Thread 3 (Thread 0x7eff2422e700 (LWP 24215)): #0 0x7eff424b204f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7eff46f895bb in WTF::TCMalloc_PageHeap::scavengerThread() () from /opt/qt4/lib/libQtWebKit.so.4 #2 0x7eff46f88ba6 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /opt/qt4/lib/libQtWebKit.so.4 #3 0x7eff424ae0a2 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7eff41180d1d in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7eff23a2d700 (LWP 24216)): #0 0x7eff4117835d in poll () from /usr/lib/libc.so.6 #1 0x7eff3f266584 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7eff3f26668c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7eff41e74862 in QEventDispatcherGlib::processEvents (this=0x7eff1c0008c0, flags=...) at /home/afiestas/kde4/source/qt/src/corelib/kernel/qeventdispatcher_glib.cpp:427 #4 0x7eff41e353c7 in QEventLoop::processEvents (this=0x7eff23a2cda0, flags=...) at /home/afiestas/kde4/source/qt/src/corelib/kernel/qeventloop.cpp:149 #5 0x7eff41e3555a in QEventLoop::exec (this=0x7eff23a2cda0, flags=...) at /home/afiestas/kde4/source/qt/src/corelib/kernel/qeventloop.cpp:204 #6 0x7eff41cfae65 in QThread::exec (this=0x244b1b0) at /home/afiestas/kde4/source/qt/src/corelib/thread/qthread.cpp:537 #7 0x7eff41cfb012 in QThread::run (this=0x244b1b0) at /home/afiestas/kde4/source/qt/src/corelib/thread/qthread.cpp:604 #8 0x7eff41cfd931 in QThreadPrivate::start (arg=0x244b1b0) at /home/afiestas/kde4/source/qt/src/corelib/thread/qthread_unix.cpp:349 #9 0x7eff424ae0a2 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7eff41180d1d in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7eff4850c7c0 (LWP 24214)): [KCrash Handler] #6 0x7eff410d0389 in raise () from /usr/lib/libc.so.6 #7 0x7eff410d1788 in abort () from /usr/lib/libc.so.6 #8 0x7eff41cf02ae in qt_message_output (msgType=QtFatalMsg, buf=0x21aed118 ASSERT: \flags.size() == 1\ in file /home/afiestas/kde4/source/kdepimlibs/akonadi/kmime/markascommand.cpp, line 102) at /home/afiestas/kde4/source/qt/src/corelib/global/qglobal.cpp:2359 #9 0x7eff41cf042d in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7eff41ebcaa8 ASSERT: \%s\ in file %s, line %d, ap=0x7fff09c3ef78) at /home/afiestas/kde4/source/qt/src/corelib/global/qglobal.cpp:2405 #10 0x7eff41cf0bff in qFatal (msg=0x7eff41ebcaa8 ASSERT: \%s\ in file %s, line %d) at /home/afiestas/kde4/source/qt/src/corelib/global/qglobal.cpp:2588 #11 0x7eff41cefe6e in qt_assert (assertion=0x7eff21396d56 flags.size() == 1, file=0x7eff21396c90 /home/afiestas/kde4/source/kdepimlibs/akonadi/kmime/markascommand.cpp, line=102) at /home/afiestas/kde4/source/qt/src/corelib/global/qglobal.cpp:2054 #12 0x7eff213886c8 in MarkAsCommand::markMessages (this=this@entry=0x5dbc040) at /home/afiestas/kde4/source/kdepimlibs/akonadi/kmime/markascommand.cpp:102 #13 0x7eff21388a63 in MarkAsCommand::slotFetchDone (this=0x5dbc040, job=optimized out) at /home/afiestas/kde4/source/kdepimlibs/akonadi/kmime/markascommand.cpp:73 #14 0x7eff41e56754 in QMetaObject::activate (sender=0x23ff4620, m=0x7eff42b87ac0 KJob::staticMetaObject, local_signal_index=3, argv=0x7fff09c3f2e0) at
[knode] [Bug 204697] Blank From: field in article view when accented characters are used
https://bugs.kde.org/show_bug.cgi?id=204697 --- Comment #8 from alex dekker b...@ale.cx --- This is still present in 4.11.3 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 330727] New: Kmail/Kontact crashes when attaching document via external program
https://bugs.kde.org/show_bug.cgi?id=330727 Bug ID: 330727 Summary: Kmail/Kontact crashes when attaching document via external program Classification: Unclassified Product: kontact Version: 4.12.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: a...@alexmakin.com.au Application: kontact (4.12.1) KDE Platform Version: 4.12.1 Qt Version: 4.8.5 Operating System: Linux 3.11.6-4-desktop x86_64 Distribution: openSUSE 13.1 (Bottle) (x86_64) -- Information about the crash: Adding an attachment via LibreOffice - Send Document as Email- What I was doing when the application crashed: The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f289c1e6880 (LWP 5668))] Thread 6 (Thread 0x7f28805b2700 (LWP 5675)): #0 0x7f28939180af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f28970b3f76 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f28970b3fa9 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f28939140db in start_thread () from /lib64/libpthread.so.0 #4 0x7f289985490d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f283fc97700 (LWP 5682)): #0 0x7f28939180af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2896e262cd in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f28970dbad6 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f28939140db in start_thread () from /lib64/libpthread.so.0 #4 0x7f289985490d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f2827a5b700 (LWP 6420)): #0 0x7f2899861284 in pthread_mutex_unlock () from /lib64/libc.so.6 #1 0x7f28933912c1 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2893351079 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f289335159b in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f289335170c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f2899fd1d76 in QEventDispatcherGlib::processEvents (this=0x7f2828c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #6 0x7f2899fa3d0f in QEventLoop::processEvents (this=this@entry=0x7f2827a5ad60, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f2899fa4005 in QEventLoop::exec (this=this@entry=0x7f2827a5ad60, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f2899ea2fef in QThread::exec (this=optimized out) at thread/qthread.cpp:536 #9 0x7f2899ea568f in QThreadPrivate::start (arg=0x16437c0) at thread/qthread_unix.cpp:338 #10 0x7f28939140db in start_thread () from /lib64/libpthread.so.0 #11 0x7f289985490d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f281e979700 (LWP 9283)): #0 0x7f28939175b4 in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0 #1 0x7f28933912c1 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2893351048 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f289335159b in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f289335170c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f2899fd1d76 in QEventDispatcherGlib::processEvents (this=0x7f2818c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #6 0x7f2899fa3d0f in QEventLoop::processEvents (this=this@entry=0x7f281e978d20, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f2899fa4005 in QEventLoop::exec (this=this@entry=0x7f281e978d20, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f2899ea2fef in QThread::exec (this=this@entry=0x2220160) at thread/qthread.cpp:536 #9 0x7f2899f85513 in QInotifyFileSystemWatcherEngine::run (this=0x2220160) at io/qfilesystemwatcher_inotify.cpp:256 #10 0x7f2899ea568f in QThreadPrivate::start (arg=0x2220160) at thread/qthread_unix.cpp:338 #11 0x7f28939140db in start_thread () from /lib64/libpthread.so.0 #12 0x7f289985490d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f281d3f8700 (LWP 16205)): #0 0x7f289984bb3d in poll () from /lib64/libc.so.6 #1 0x7f2893351604 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f289335170c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2899fd1d76 in QEventDispatcherGlib::processEvents (this=0x7f2814020330, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #4 0x7f2899fa3d0f in QEventLoop::processEvents (this=this@entry=0x7f281d3f7d20, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f2899fa4005 in QEventLoop::exec (this=this@entry=0x7f281d3f7d20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f2899ea2fef in QThread::exec (this=this@entry=0x121bcd30) at thread/qthread.cpp:536 #7 0x7f2899f85513
[Akonadi] [Bug 326480] Akonadi fails to start with nvidia binary drivers installed
https://bugs.kde.org/show_bug.cgi?id=326480 Alex G gfo...@gmail.com changed: What|Removed |Added CC||gfo...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 324219] IMAP Folder Rename fails
https://bugs.kde.org/show_bug.cgi?id=324219 Alex Wright bugzi...@wright-family.me.uk changed: What|Removed |Added CC||bugzi...@wright-family.me.u ||k -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
