[korganizer] [Bug 485205] Most recent calendar entries deleted when reloading the file where they are supposed to be saved
https://bugs.kde.org/show_bug.cgi?id=485205 --- Comment #8 from Paul Stansell --- I'm ready provide any additional information that is required. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485207] Error while trying to create calendar item. Error was: Invalid parent collection
https://bugs.kde.org/show_bug.cgi?id=485207 --- Comment #5 from Paul Stansell --- Sorry, but I don't know what additional info you expect from me. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485205] Most recent calendar entries deleted when reloading the file where they are supposed to be saved
https://bugs.kde.org/show_bug.cgi?id=485205 --- Comment #6 from Paul Stansell --- I'm running on a Raspberry Pi 4B with 4GB of RAM. From my experience to date, it seems to work pretty well, apart from this problem that's stopped me from using korganizer. If you can think of any other tests I could run, I'd be happy to try them as it's easy for me to clone the SD card and experiment with different settings or run different tests. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485205] Most recent calendar entries deleted when reloading the file where they are supposed to be saved
https://bugs.kde.org/show_bug.cgi?id=485205 --- Comment #4 from Paul Stansell --- Hello Danial, Thanks for helping with this. Since I was already running korganizer from the command line, I noticed that when I choose "File > Quit" it didn't actually stop korganizer running, it just closed the window. And when I started it again, by clicking on the icon that I have on my panel, it opened the a korganizer window for the program that I originally started at the command in a console. This helps me understand why I could previously "quit" korganizer without it updating my .ics file with the new events, yet those new events were present when I restarted the korganizer. It implies that korganizer wasn't actually stopping, it was still running in the background, and caching the new events somewhere that wasn't in the .ics file. This explains why, when I reloaded the .ics the new events were lost (because the ics file was not up-to-date). Anyway, to start korganizer, I did the following: > killall korganizer > akonadictl stop > QT_LOGGING_RULES="*=true;qt.*=false" korganizer &> log.txt I've uploaded the log.txt file. These are the lines I got when I try, but fail, to paste an event: "Invalid parent collection" org.kde.pim.akonadiserver: Error while handling command CreateItem on connection korganizer-3257944331 (0x55bd6ce520) kf.notifications: Calling notify on "Sound" kf.notifications: Calling notify on "Taskbar" org.kde.pim.korganizer: Incidence not added, job reported error: "Invalid parent collection" -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485205] Most recent calendar entries deleted when reloading the file where they are supposed to be saved
https://bugs.kde.org/show_bug.cgi?id=485205 --- Comment #3 from Paul Stansell --- Created attachment 168396 --> https://bugs.kde.org/attachment.cgi?id=168396=edit Korganizer output log file. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485207] Error while trying to create calendar item. Error was: Invalid parent collection
https://bugs.kde.org/show_bug.cgi?id=485207 --- Comment #3 from Paul Stansell --- Hello Daniel, Thanks so much for replying. > 1) Could you please specify in which view (agenda/month view/etc.) does this >happen? The reported problem was for agenda day view, but I just tried with week and month view and when trying to paste an event I got the same error message as I reported before > 2) Do you have multiple calendars, or just a single one? I have two calendars (in addition to the Birthdays one). One is the default one and active, the other is "hidden" (or not displayed, so its entries are not displayed). 3) Do you have some calendar marked as default? Yes, the one I tried to paste to. 4) What kind of calendar is it (ical, DAV, Google, etc.?) ical (with file name .ics) > If you have more than one calendar, you should get a dialog that > lets you select the calendar to paste into. If you have only one calendar, > the event should automatically get pasted into it. I'm familiar with that dialog, but I'm not seeing it when I paste as I'm only viewing the default calendar. > Could you please run KOrganizer from terminal with the following command: > > QT_LOGGING_RULES="*=true;qt.*=false" korganizer > > then try to reproduce the bug and provide here the log that's printed to the >console? I exited and restarted korganizer again from the console. I tried to add a new event, but it wouldn't let me. (This is different from the problem I had before where I *could* add new events, but I couldn't copy and paste events.) When I try to add a new event the pop-up dialogue window appears, I can write "test event" in the summary field, but when I click either Ok or Apply, nothing happens except all the options Ok, Apply and Cancel become grey-out. To kill the pop-up I have to click the X on the top right of the window. It then asks me (in another pop-up window) if I want to Cancel Editing or not. I can cancel and both pop-up windows disappear and my event is not added to the calendar. Here is the output from the console: org.kde.pim.akonadicore: connectToServer "/run/user/1000/akonadi/akonadiserver-ntf.socket" Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed org.kde.pim.incidenceeditor: checkDirtyStatus called on an invalid incidence org.kde.pim.calendarsupport: creating CalendarSupport::FreeBusyCalendar(0x558693e660) org.kde.pim.incidenceeditor: org.kde.pim.incidenceeditor: Loading item -1 ; parent -17437 ; storage -1 org.kde.pim.akonadicore: Akonadi::Monitor(0x5586c33e60, name = "TagWidgetMonitor") Connected to notification bus org.kde.pim.akonadicore: Akonadi::Monitor(0x5586c33e60, name = "TagWidgetMonitor") Subscribing as " "TagWidgetMonitor - 367333162592" " org.kde.pim.incidenceeditor: free slot calculation: invalid range. range( 0 ) / mSlotResolutionSeconds( 900 ) = 0 org.kde.pim.calendarsupport: deleting CalendarSupport::FreeBusyCalendar(0x558693e660) -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485207] New: Error while trying to create calendar item. Error was: Invalid parent collection
https://bugs.kde.org/show_bug.cgi?id=485207 Bug ID: 485207 Summary: Error while trying to create calendar item. Error was: Invalid parent collection Classification: Applications Product: korganizer Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: paulstans...@gmail.com Target Milestone: --- Created attachment 168268 --> https://bugs.kde.org/attachment.cgi?id=168268=edit Screenshot of error message SUMMARY Copying an old event, or a newly created event, seems to work, but when I try to paste it in somewhere else in the calendar I get the error message "Error while trying to create calendar item. Error was: Invalid parent collection". STEPS TO REPRODUCE 1. Copy an event already in a calendar, or create a new "test" event and copy that (can use C-c or Right-click-Copy) 2. Try to paste the event somewhere else in the same calendar (using C-v or Right-click-paste) 3. A popup dialog box appears containing the following message: "Error while trying to create calendar item. Error was: Invalid parent collection" OBSERVED RESULT The error message attached. EXPECTED RESULT Successful paste of event. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Bookworm 6.6.20+rpt-rpi-v8 (64-bit) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION The message "Invalid parent collection" does not help me understand the problem or where the error might be. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485205] New: Most recent calendar entries deleted when reloading the file where they are supposed to be saved
https://bugs.kde.org/show_bug.cgi?id=485205 Bug ID: 485205 Summary: Most recent calendar entries deleted when reloading the file where they are supposed to be saved Classification: Applications Product: korganizer Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: paulstans...@gmail.com Target Milestone: --- SUMMARY Most recent calendar entries deleted (about 15 hours worth) when reloading the file where they are supposed to be saved. STEPS TO REPRODUCE 1. Right click on the name of the calendar in the bottom left pane. 2. Click "calendar properties". 3. Observer the file name where the calendar is supposed to be saved. 4. Click "okay" (or maybe it was "apply"). 5. Observe the calendar reloading with the all the recent entries absent. OBSERVED RESULT Most recent calendar entries are deleted. EXPECTED RESULT No loss of recent entries. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Bookworm 6.6.20+rpt-rpi-v8 (64-bit) (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I want to backup the .ics file where my calendar entries are saved. According the "calendar properties" they are saved in a .ics file in a subdirectory of my home directory which I backup. However, it seems that the changes are not being saved regularly to that file. I made numerous changes, but the time stamp of the file didn't change. I exited korganizer and still the time stamp of the .ics file didn't change. I restarted korganizer and all the most recent additions where there, but still the ics file was too old to be saving those recent additions. Then did what I described in "STEPS TO REPRODUCE" and it seems that the old ics file was reloaded and I lost all the recent changes that I'd made (which was about 15 hours worth). Where are the changes being saved, if not in the file in the "File Name" box in the "calendar properties"? I'd like to know so that I can back up my calendar files. I'd like to be able to force any changes I make to a calendar to be written to a named ics file that I can backup (without having to export that file as an ics file because I backup many times a day). -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485099] Clicking to add tags does nothing
https://bugs.kde.org/show_bug.cgi?id=485099 --- Comment #9 from Paul Stansell --- I'm running a brand new installation on a Raspberry Pi 4B (4GB), so maybe that has something to do with it, but in general I'm pleased to find that KDE runs remarkably well on such a low spec device. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485099] Clicking to add tags does nothing
https://bugs.kde.org/show_bug.cgi?id=485099 --- Comment #7 from Paul Stansell --- (In reply to Laurent Montel from comment #5) > Which theme do you use ? > It's ok with breeze. Yes, the check boxed show up with Breeze Classic -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485099] Clicking to add tags does nothing
https://bugs.kde.org/show_bug.cgi?id=485099 --- Comment #6 from Paul Stansell --- (In reply to Laurent Montel from comment #5) > Which theme do you use ? > It's ok with breeze. I chose it like this: - korganizer > Settings > Colour Scheme > Breeze Dark -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485099] Clicking to add tags does nothing
https://bugs.kde.org/show_bug.cgi?id=485099 --- Comment #3 from Paul Stansell --- Created attachment 168198 --> https://bugs.kde.org/attachment.cgi?id=168198=edit Screenshot showing "invisible" tick boxes to left of the tag names. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485099] Clicking to add tags does nothing
https://bugs.kde.org/show_bug.cgi?id=485099 --- Comment #2 from Paul Stansell --- I see the problem now. I had also tried clicking on the "..." which popped up a window with the tags, which I tried to click on to choose one, but nothing happened. Now I can see that there are boxes to the left of the tag names that I should have clicked on. However, in my colour scheme they boxes were black on black, so invisible. I'll add another attachment to illustrate this. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 485099] New: Clicking to add tags does nothing
https://bugs.kde.org/show_bug.cgi?id=485099 Bug ID: 485099 Summary: Clicking to add tags does nothing Classification: Applications Product: korganizer Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: paulstans...@gmail.com Target Milestone: --- Created attachment 168193 --> https://bugs.kde.org/attachment.cgi?id=168193=edit Screen shot showing the "click to add tags" box. SUMMARY Clicking to add a tags to an calendar entry (where it says "Tags: Click to add tags") does nothing. STEPS TO REPRODUCE 1. Double click on Day view to create an event 2. Click in the box that says "Click to add tags" 3. Observe that nothing happens so that no tags (or labels) can be added. OBSERVED RESULT Nothing happens EXPECTED RESULT A popup showing the choice of tags so that one can be selected SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Bookworm on aarch64 (available in About System) KDE Plasma Version: 5.27.5 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 485091] New: Time on Marcus Bains line always red and therefore does not show up against a red background
https://bugs.kde.org/show_bug.cgi?id=485091 Bug ID: 485091 Summary: Time on Marcus Bains line always red and therefore does not show up against a red background Classification: Applications Product: korganizer Version: 5.22.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: paulstans...@gmail.com Target Milestone: --- Created attachment 168183 --> https://bugs.kde.org/attachment.cgi?id=168183=edit Screenshot of invisible and visible Marcus Bain line *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Time on Marcus Bains line always red and therefore does not show up against a red background. A previous version of korganizer that I used put a small block of high contrast colour behind the Marcus Bains time so that it was always visible. The red line is also also invisible against a red background. When "show seconds" is chosen the display flicker every second. This did not happen with the previous version that I used. STEPS TO REPRODUCE 1. Open korganizer 2. Change settings to display the Marcus Bain's line 3. Configure a tag that has colour red. 4. Create an event with the red colour tag (label) at the current time 5. Observe that the Marcus Bain line and time is invisible as it's displayed as red against red. OBSERVED RESULT Invisible Marcus Bain line EXPECTED RESULT Marcus Bain line to be and text to us a colour that has high contrast against the background colour. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian (available in About System) KDE Plasma Version: 5.27.5 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 366511] Recurring events can't be changed properly in DAV calendar resource
https://bugs.kde.org/show_bug.cgi?id=366511 --- Comment #5 from Paul Gover --- Aaron, I wouldn't hold your breath - note the dates on this bug... The KDE developers have bigger, or more fun, fish to fry - AFAICT to do with Wayland and Qt6 Actually, I think it's been working OK for me over the past few years. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 479851] Allow for a single text/html part to be saved decoded (as html file)
https://bugs.kde.org/show_bug.cgi?id=479851 --- Comment #5 from Paul Schwabauer --- Here is the fix for the message structure viewer: https://invent.kde.org/pim/messagelib/-/merge_requests/188 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 479851] Allow for a single text/html part to be saved decoded (as html file)
https://bugs.kde.org/show_bug.cgi?id=479851 --- Comment #4 from Paul Schwabauer --- - Regarding the message view: In `messagelib` there is already code that can save the HTML and open it with a browser: https://invent.kde.org/pim/messagelib/-/blob/c52d92a121d6678e96dcb8e00dbd9d61101dc67e/messageviewer/src/viewer/viewer_p.h#L488-L490 However, this code is hidden in a private class, and I can find no usage of it. My proposal would be to expose `ViewerPrivate::slotOpenInBrowser` in `Viewer` and add a new method `ViewerPrivate::exportToHtml` and `Viewer::exportToHtml` similar to the `exportToPdf` methods, that can be used by kmail. This change would require the extending of the context menu in kmail with "Export to HTML..." and "Open in browser". - Regarding the email/message structure view: Currently, it is not possible to save an HTML part in the message structure display, if the HTML is sent as a main body. To reproduce, open an HTML mail with the HTML as main body part and press CTRL-ALT-D to open the message structure display. Then right-click on the HTML part. If the HTML part is not at the top level, for example, with a multipart/alternative mail, it is possible to save, open and view the HTML part. However, this is not possible if the mail only consists of the HTML part. The reason is here: https://invent.kde.org/pim/messagelib/-/blob/c52d92a121d6678e96dcb8e00dbd9d61101dc67e/messageviewer/src/viewer/viewer_p.cpp#L1733-L1746. To fix this, the `isTopLevel()` check has to be removed. This change should have a minimal impact. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 479851] Allow for a single text/html part to be saved decoded (as html file)
https://bugs.kde.org/show_bug.cgi?id=479851 Paul Schwabauer changed: What|Removed |Added CC||pschwaba...@intevation.de --- Comment #2 from Paul Schwabauer --- Currently, it is possible to save emails as mbox files by right-clicking on the message → "Save message". This opens a file dialog with the only possibility to filter for `.mbox` files. My proposal is to extend the filter to `.html` files and save the HTML part if the file extension is `.html`. This avoids the cluttering of the context menu and has similar behavior to Thunderbird, where I can select the wanted file type. This change would require refactoring in `messageviewer/utils/messageviewerutil`. `MessageViewer::Util::saveMessageInMboxAndGetUrl` would then check for the specified file extension of the user and extract and save the HTML part, if the extension is `.html`. -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 475485] New: Handbook: typo in OpenPGP link to Wikipedia
https://bugs.kde.org/show_bug.cgi?id=475485 Bug ID: 475485 Summary: Handbook: typo in OpenPGP link to Wikipedia Classification: Applications Product: kleopatra Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: p.r.worr...@gmail.com CC: kdepim-bugs@kde.org, m...@kde.org Target Milestone: --- In Chapter 1 of the Kleopatra handbook there's a link to Wikipedia for the description of OpenPGP. The link is invalid because it starts "httpis://" rather than "https://; -- You are receiving this mail because: You are on the CC list for the bug.
[kleopatra] [Bug 472486] Kleopatra: option to generate checksum file without paths
https://bugs.kde.org/show_bug.cgi?id=472486 Paul Worrall changed: What|Removed |Added Severity|normal |wishlist Ever confirmed|0 |1 CC||p.r.worr...@gmail.com Status|REPORTED|CONFIRMED Summary|Kleopatra needs a new hash |Kleopatra: option to |file generation mode|generate checksum file ||without paths -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 377399] kontact loses imap connections constantly
https://bugs.kde.org/show_bug.cgi?id=377399 Paul Brown changed: What|Removed |Added Status|RESOLVED|REOPENED CC||paul.br...@kde.org Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #7 from Paul Brown --- (In reply to Justin Zobel from comment #3) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! Happening now every few minutes in Arch with KMail version 5.23.2, Akonadi version 23.04.2. Akonadi message is: org.kde.pim.imapresource: Get metadata failed: "Connection to server lost." -- You are receiving this mail because: You are on the CC list for the bug.
[kdepim] [Bug 466422] New: org.kde.pim.pop3resource: Got unexpected job data:
https://bugs.kde.org/show_bug.cgi?id=466422
Bug ID: 466422
Summary: org.kde.pim.pop3resource: Got unexpected job data:
Classification: Applications
Product: kdepim
Version: 5.21.3
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: pmw.go...@yahoo.co.uk
Target Milestone: ---
Created attachment 156722
--> https://bugs.kde.org/attachment.cgi?id=156722=edit
Part of the wayland-session.log showing the problem. This NOT a complete
email.
SUMMARY
KDE console output ("wayland-session.log") contains lines like:
org.kde.pim.pop3resource: Got unexpected job data: t
along with complete dumps of email items (I think the ones just read from the
pop server).
Note this is Gentoo with OpenRC, so Systemd is not involved.
STEPS TO REPRODUCE
1. Start KDE under Wayland (in my case with /usr/bin/dbus-launch
--exit-with-session startplasma-wayland) and redirect console output to a file
in the usual way.
2. Use Kontact to view new messages - using a pop3 server
OBSERVED RESULT
1) The console output contains long copies of the email files. I don't think
this appears under X11, which to me is weird, but reading an Arch Linux blog
about their tweaks for Systemd, maybe isn't so weird.
Note: I consider this the main part of the problem
2) Every so often, a line starting "org.kde.pim.pop3resource: Got unexpected
job data:" appears. This line is particularly interesting: I've noticed for
ages that some emails I get are slightly corrupted. Typically they are from
the Daily Telegraph, and the symptom is various embedded URLs linking to their
feature pages omit a character, often the full stop in ".co.uk" or similar. I
reported the problem to the Telegraph, but they said it wasn't at their end.
Unfortunately, I only notice the corrupted emails occasionally, so this might
not be the same issue, but the coincidence is striking!
That said, the vast majority of emails arrive OK, whereas the "unexpected data"
message seems to appear for every email, so it may be some artifact to do with
buffer lengths or something.
This is not a particularly severe issue for me, but it may be indicating
something important and related, so I've included it.
I suspect this problem also occurs under X11, but I'm currently only seeing it
on Wayland as I'm trying to convert to using it all the time.
EXPECTED RESULT
No long dumps of emails in session logs, and no unexpected characters.
More important, if it does turn out to be related, no corrupted emails.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.26.5
(available in About System)
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
ADDITIONAL INFORMATION
Attached, part of one email dump. The unexpected data "Received: from
127.0.0.1" is common, but other examples can appear later, and seem to be
pretty random. This one isn't from the Telegraph, as theirs tend to be huge!
--
You are receiving this mail because:
You are the assignee for the bug.
[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator
https://bugs.kde.org/show_bug.cgi?id=438345 Paul Gover changed: What|Removed |Added CC|pmw.go...@yahoo.co.uk | -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 461356] New: How To Borrow Money From Cash App For Managing Your Needs?
https://bugs.kde.org/show_bug.cgi?id=461356 Bug ID: 461356 Summary: How To Borrow Money From Cash App For Managing Your Needs? Classification: Applications Product: akregator Version: 5.21.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: feed parser Assignee: kdepim-bugs@kde.org Reporter: paulilauli...@gmail.com Target Milestone: --- Are you suffering from some problems encountered during the course of taking a loan on Cash App? It may happen due to the lack of information about How To Borrow Money From Cash App. So, you have to first learn the required source of information and then implement the required steps and instructions get a loan on Cash App without any kind of trouble. In case of any hassle regarding the same, you should place a call at the helpline number that remains active all the time. https://www.emailsupport-contact.com/blog/how-to-borrow-money-from-cash-app/ -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 398577] closing a message subwindow crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=398577 Paul Nodine changed: What|Removed |Added CC|paul.nod...@outlook.com | -- You are receiving this mail because: You are the assignee for the bug.
[Spam] [Bug 457147] llee46467
https://bugs.kde.org/show_bug.cgi?id=457147 Paul Worrall changed: What|Removed |Added Status|REPORTED|RESOLVED Version|5.20.3 |unspecified Component|akonadiconsole |Spam Assignee|kdepim-bugs@kde.org |n...@kde.org Product|Akonadi |Spam Resolution|--- |NOT A BUG CC||p.r.worr...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator
https://bugs.kde.org/show_bug.cgi?id=438345 --- Comment #6 from Paul Gover --- (In reply to Paul Gover from comment #4) > I'm also getting this, on Gentoo, with: > Plasma 5.21.5 > kmail 20.12.3 > kwayland 5.82.0 > qtwayland 5.15.2 > kernel 5.13.7 > amdgpu Now working OK! Plasma 5.24.5 kmail 21.12.3 qtwayland 5.15.4 kernel 5.18.6 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 446025] Importing .ics file causing Korganizer to crash
https://bugs.kde.org/show_bug.cgi?id=446025 --- Comment #4 from Paul Ezvan --- The crash open with the following: - Open link https://www.aa-esiee.com/shortUrl/tM5-798129 in Firefox - Choose "open with Korganize" - Then Korganizer pops-up, select "Merge into existing calendar" - Korganizer then crashes -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 446025] Importing .ics file causing Korganizer to crash
https://bugs.kde.org/show_bug.cgi?id=446025 --- Comment #2 from Paul Ezvan --- Hello Allen, I've sent you the ics file by email. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 446025] New: Importing .ics file causing Korganizer to crash
https://bugs.kde.org/show_bug.cgi?id=446025
Bug ID: 446025
Summary: Importing .ics file causing Korganizer to crash
Product: korganizer
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: p...@ezvan.fr
Target Milestone: ---
Application: korganizer (5.17.3 (21.04.3))
Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.14.18-300.fc35.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 35 (KDE Plasma)
DrKonqi: 5.23.3 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
* Import ICS file from Firefox using Korganizer
* Select "merge into existing calendar"
* Korganizer crashes
The crash can be reproduced every time.
-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6 0x7f6b8aa05758 in cleanVObject (o=0x564633f031c0) at
/usr/src/debug/libical-3.0.11-1.fc35.x86_64/src/libicalvcal/vobject.c:591
#7 0x7f6b8aa08e94 in finiLex () at
/usr/src/debug/libical-3.0.11-1.fc35.x86_64/src/libicalvcal/vcc.c:855
#8 Parse_MIMEHelper () at
/usr/src/debug/libical-3.0.11-1.fc35.x86_64/src/libicalvcal/vcc.c:1171
#9 0x7f6b8aa09e96 in Parse_MIME_FromFile (file=file@entry=0x56463401aea0)
at /usr/src/debug/libical-3.0.11-1.fc35.x86_64/src/libicalvcal/vcc.c:1209
#10 0x7f6b8aa09f11 in Parse_MIME_FromFileName (fname=0x564633f062f8
"/tmp/mozilla_paul0/cal.ics") at
/usr/src/debug/libical-3.0.11-1.fc35.x86_64/src/libicalvcal/vcc.c:1220
#11 0x7f6b8dc101fb in KCalendarCore::VCalFormat::load (this=0x7ffd46eb2120,
calendar=..., fileName=...) at
/usr/src/debug/kf5-kcalendarcore-5.88.0-1.fc35.x86_64/src/vcalformat.cpp:92
#12 0x7f6b8dbd33ea in KCalendarCore::FileStorage::load
(this=this@entry=0x7ffd46eb2230) at
/usr/src/debug/kf5-kcalendarcore-5.88.0-1.fc35.x86_64/src/filestorage.cpp:117
#13 0x7f6b8b8dc8cd in Akonadi::ICalImporter::importIntoExistingResource
(this=this@entry=0x564633efbaf0, url=..., collection=...) at
/usr/src/debug/kf5-akonadi-calendar-21.04.3-1.fc35.x86_64/src/icalimporter.cpp:184
#14 0x7f6b8dedf434 in ActionManager::importURL (this=0x564633bbd9e0,
url=..., merge=) at
/usr/src/debug/korganizer-21.04.3-1.fc35.x86_64/src/actionmanager.cpp:859
#15 0x7f6b8dee3f6d in ActionManager::importCalendar (this=0x564633bbd9e0,
url=...) at
/usr/src/debug/korganizer-21.04.3-1.fc35.x86_64/src/actionmanager.cpp:1587
#16 0x5646329108be in KOrganizerApp::activate (this=0x7ffd46eb2670,
args=..., workingDir=...) at
/usr/src/debug/korganizer-21.04.3-1.fc35.x86_64/src/koapp.cpp:110
#17 0x7f6b8dfa10db in KontactInterface::PimUniqueApplication::start
(arguments=...) at
/usr/src/debug/kf5-kontactinterface-21.04.3-1.fc35.x86_64/src/pimuniqueapplication.cpp:144
#18 0x56463290ce1b in main (argc=, argv=) at
/usr/src/debug/korganizer-21.04.3-1.fc35.x86_64/src/main.cpp:49
[Inferior 1 (process 7082) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are the assignee for the bug.
[Spam] [Bug 440892] I am a Software developer .We provide best security services in usa.
https://bugs.kde.org/show_bug.cgi?id=440892 Jan Paul Batrina changed: What|Removed |Added Version|5.17.3 |unspecified Assignee|kdepim-bugs@kde.org |n...@kde.org Component|ICal dir resource |Spam Product|Akonadi |Spam -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator
https://bugs.kde.org/show_bug.cgi?id=438345 Paul Gover changed: What|Removed |Added CC||pmw.go...@yahoo.co.uk --- Comment #4 from Paul Gover --- I'm also getting this, on Gentoo, with: Plasma 5.21.5 kmail 20.12.3 kwayland 5.82.0 qtwayland 5.15.2 kernel 5.13.7 amdgpu -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 429894] New: Crash on copying an email address
https://bugs.kde.org/show_bug.cgi?id=429894 Bug ID: 429894 Summary: Crash on copying an email address Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: paul.monta...@live.co.uk Target Milestone: --- Application: kmail (5.15.3 (20.08.3)) Qt Version: 5.15.2 Frameworks Version: 5.76.0 Operating System: Linux 5.9.10-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Creating a new mail seive. - Unusual behavior I noticed: Copied email address for seive config. KMail crashes immediately The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [New LWP 3822] [New LWP 3823] [New LWP 3824] [New LWP 3825] [New LWP 3826] [New LWP 3827] [New LWP 3828] [New LWP 3829] [New LWP 3830] [New LWP 3831] [New LWP 3832] [New LWP 3833] [New LWP 3834] [New LWP 3835] [New LWP 3836] [New LWP 3837] [New LWP 3854] [New LWP 3858] [New LWP 3863] [New LWP 3864] [New LWP 4253] [New LWP 4323] [New LWP 4325] [New LWP 4331] [New LWP 4332] [New LWP 4333] [New LWP 4342] [New LWP 4367] [New LWP 4371] [New LWP 4372] [New LWP 4373] [New LWP 4374] [New LWP 4375] [New LWP 4406] [New LWP 4411] [New LWP 5314] [New LWP 5315] [New LWP 5320] [New LWP 5330] [New LWP 5496] [New LWP 5532] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7fcd698be83f in poll () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7fcd6848e080 (LWP 3414))] Thread 42 (Thread 0x7fcc5fad5640 (LWP 5532)): #0 0x7fcd698be83f in poll () from /lib64/libc.so.6 #1 0x7fcd63cd500e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcd63cd512f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcd69eae7fb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fcd69e55c4b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fcd69c74d0e in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fcd69c75e51 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7fcd66d613e9 in start_thread () from /lib64/libpthread.so.0 #8 0x7fcd698c9943 in clone () from /lib64/libc.so.6 Thread 41 (Thread 0x7fccb77fe640 (LWP 5496)): #0 0x7fcd66d679d8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcd6da283d2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x1297 in ?? () #3 0x1279a12a in ?? () #4 0x1276 in ?? () #5 0x1279a12a in ?? () #6 0x7fccb77fd328 in ?? () #7 0x7fccdc0037b0 in ?? () #8 0x in ?? () Thread 40 (Thread 0x7fccf2d98640 (LWP 5330)): #0 0x7fcd66d676b2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcd5a5ff30b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fcd5a5fe7c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fcd66d613e9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcd698c9943 in clone () from /lib64/libc.so.6 Thread 39 (Thread 0x7fccd2c0d640 (LWP 5320)): #0 0x7fcd66d676b2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcd5a5ff30b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fcd5a5fe7c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fcd66d613e9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcd698c9943 in clone () from /lib64/libc.so.6 Thread 38 (Thread 0x7fccb7fff640 (LWP 5315)): #0 0x7fcd66d676b2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcd5a5ff30b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fcd5a5fe7c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fcd66d613e9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcd698c9943 in clone () from /lib64/libc.so.6 Thread 37 (Thread 0x7fccd140a640 (LWP 5314)): #0 0x7fcd66d676b2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcd5a5ff30b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fcd5a5fe7c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fcd66d613e9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcd698c9943 in clone () from /lib64/libc.so.6 Thread 36 (Thread 0x7fcc762fe640 (LWP 4411)): #0 0x7fcd698c434d in syscall () from /lib64/libc.so.6 #1 0x7fcd69c78091 in QSemaphore::acquire(int) () from /usr/lib64/libQt5Core.so.5 #2 0x7fcd67b11934 in ?? () from /usr/lib64/libQt5Network.so.5 #3 0x7fcd69c75e51 in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x7fcd66d613e9 in start_thread () from /lib64/libpthread.so.0 #5 0x7fcd698c9943 in clone
[kmail2] [Bug 429101] New: Seg fault when clciking on new mail notification (KMail)
https://bugs.kde.org/show_bug.cgi?id=429101 Bug ID: 429101 Summary: Seg fault when clciking on new mail notification (KMail) Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: paul.monta...@live.co.uk Target Milestone: --- Application: kmail (5.15.3 (20.08.3)) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.3.18-lp152.50-preempt x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.2" -- Information about the crash: - What I was doing when the application crashed: Clicked on the new KMail notification, and immediately received a Seg fault. Relaunched KMail and get Seg Fault. I have to relaunch KMail a couple of times before it allows me to view emails without Seg fault. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [New LWP 20595] [New LWP 20596] [New LWP 20597] [New LWP 20598] [New LWP 20599] [New LWP 20600] [New LWP 20601] [New LWP 20602] [New LWP 20603] [New LWP 20604] [New LWP 20605] [New LWP 20606] [New LWP 20607] [New LWP 20608] [New LWP 20609] [New LWP 20610] [New LWP 20611] [New LWP 20612] [New LWP 20613] [New LWP 20614] [New LWP 20615] [New LWP 20624] [New LWP 20636] [New LWP 20637] [New LWP 20638] [New LWP 20639] [New LWP 20640] [New LWP 20643] [New LWP 20644] [New LWP 20645] [New LWP 20668] [New LWP 20669] [New LWP 20681] [New LWP 20683] [New LWP 20686] [New LWP 20687] [New LWP 20688] [New LWP 20689] [New LWP 20691] [New LWP 20704] [New LWP 20734] [New LWP 20735] [New LWP 20740] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f06530996db in poll () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7f065d9ccf40 (LWP 20594))] Thread 44 (Thread 0x7f05321cf700 (LWP 20740)): #0 0x7f064858e87d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f06215b5e9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f06215b5a87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f06485884f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f06530a3fbf in clone () from /lib64/libc.so.6 Thread 43 (Thread 0x7f05337fe700 (LWP 20735)): #0 0x7f064858e87d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f06215b5e9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f06215b5a87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f06485884f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f06530a3fbf in clone () from /lib64/libc.so.6 Thread 42 (Thread 0x7f0533fff700 (LWP 20734)): #0 0x7f064858e87d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f06215b5e9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f06215b5a87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f06485884f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f06530a3fbf in clone () from /lib64/libc.so.6 Thread 41 (Thread 0x7f053a7b7700 (LWP 20704)): #0 0x7f063f0aa013 in g_source_ref () from /usr/lib64/libglib-2.0.so.0 #1 0x7f063f0aa0f8 in g_source_iter_next () from /usr/lib64/libglib-2.0.so.0 #2 0x7f063f0ab5a3 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #3 0x7f063f0ac03b in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #4 0x7f063f0ac21c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f0653a7dddb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f0653a19eba in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f0653823f97 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f06538254ac in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f06485884f9 in start_thread () from /lib64/libpthread.so.0 #10 0x7f06530a3fbf in clone () from /lib64/libc.so.6 Thread 40 (Thread 0x7f054e9ef700 (LWP 20691)): #0 0x7f064858e87d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f06215b5e9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f06215b5a87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f06485884f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f06530a3fbf in clone () from /lib64/libc.so.6 Thread 39 (Thread 0x7f054f6f7700 (LWP 20689)): #0 0x7f064858e87d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f06215b5e9b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f06215b5a87 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f06485884f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f06530a3fbf in clone () from /lib64/libc.so.6 Thread 38 (Thread 0x7f054700 (LWP
[korganizer] [Bug 358249] Remote ICS file does not populate calendar
https://bugs.kde.org/show_bug.cgi?id=358249 Paul Brown changed: What|Removed |Added Platform|Ubuntu Packages |Manjaro Version|5.15.0 |5.15.1 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 358249] Remote ICS file does not populate calendar
https://bugs.kde.org/show_bug.cgi?id=358249 Paul Brown changed: What|Removed |Added CC||paul.br...@kde.org --- Comment #4 from Paul Brown --- This is still happening to me. I am trying to integrate KDE's Phab calendar into Korganizer, and I have the following export file: https://phabricator.kde.org/calendar/export/ics/vz6554ndpdhjeqpea3oy/kde_public_tasks.ics Which I can download and browse and it contains the calendar data. It also works when integrated into a Nextclous calendar, but it does not show events on Korganizer. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 417366] New: Kmail uses the wrong dictionary for spellchecking
https://bugs.kde.org/show_bug.cgi?id=417366 Bug ID: 417366 Summary: Kmail uses the wrong dictionary for spellchecking Product: kmail2 Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: k...@paulmcauley.com Target Milestone: --- I have the British English dictionary set as the default under my Identity->Advanced tab (only American English and British English are given as options, and my OpenSUSE Leap 15.1 base system is set to British English (United Kingdom)). If I click on "Spelling..." when composing a new email my language is also set to British English. However, the spellchecker will underline in red "colour" but not "color". I would expect the opposite. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 416542] New: Search folders not filtering properly
https://bugs.kde.org/show_bug.cgi?id=416542 Bug ID: 416542 Summary: Search folders not filtering properly Product: kmail2 Version: 5.11.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kdepim-bugs@kde.org Reporter: paul.lemm...@tmcaz.com Target Milestone: --- SUMMARY I have created a search folder using "Find messages" and have named the folder so that I can reuse the search. In the search, I wish to only have messages from selected folders that contain a particular word in the subject and have an age that is less than 5 days. The search for word in the subject appears to be the only filter that is being acted on. I get messages from all folders regardless of age. STEPS TO REPRODUCE 1. Connect kmail to Exchange via IMAP 2. Open "Find Messages" 3. Select specific folders 4. Select Match all of the following 5. Select "Subject" "Contains" "Word" 6. Select "Age in Days" "is less than or equal to" "3 Days" 7. Name the Search Folder to something meaningful 8. Perform "Search" OBSERVED RESULT I get all messages that contain "Word" in the subject regardless of location or age. EXPECTED RESULT The search would only return matches from selected folders and was less than or equal to 3 days old. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 KDE Plasma Version: 15.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION The indexer is running and all messages are cached locally. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 366511] Recurring events can't be changed properly in DAV calendar resource
https://bugs.kde.org/show_bug.cgi?id=366511 Paul Gover changed: What|Removed |Added CC||pmw.go...@yahoo.co.uk --- Comment #1 from Paul Gover --- I'm seeing the same problem, using Radicale as my CalDAV server. I can create a recurring event and it appears as a new .ics file in the server database. I can drag an item (the first item in my test) to a new date, and select "Only this item" in the resulting popup. It appears to work; the korganizer display shows that one item moved to the new date. Refreshing the containing folder has no new effect -the moved item is where I moved it to, the others remain where they were. However: 1) the ,ics file on the Radicale server is untouched 2) if I exit korganizer and restart it, the moved item reverts to its original date. There are no messages on the console from korganizer, and there are no messages in the Radicale server log. It looks like the change never got propogated to Radicale. I'm using Gentoo linux, KDE Frameworks 5.54.0 Qt 5.11.3 (built against 5.11.3) The xcb windowing system korganizer 5.10.3 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 407071] Akregator crashes on closing image in internal browser and moving to another article
https://bugs.kde.org/show_bug.cgi?id=407071 Paul Hands changed: What|Removed |Added Version|unspecified |5.11.0 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 407071] Akregator crashes on closing image in internal browser and moving to another article
https://bugs.kde.org/show_bug.cgi?id=407071 --- Comment #1 from Paul Hands --- Created attachment 119735 --> https://bugs.kde.org/attachment.cgi?id=119735=edit Screenshot 2 showing the image tab -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 407071] New: Akregator crashes on closing image in internal browser and moving to another article
https://bugs.kde.org/show_bug.cgi?id=407071 Bug ID: 407071 Summary: Akregator crashes on closing image in internal browser and moving to another article Product: akregator Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: internal browser Assignee: kdepim-bugs@kde.org Reporter: jpha...@gmail.com Target Milestone: --- Created attachment 119734 --> https://bugs.kde.org/attachment.cgi?id=119734=edit Screenshot 1, showing the feed and articles SUMMARY Akregator segfaults when closing an internal browser tab which is displaying an image from an article, and then selecting the following article in the feed. STEPS TO REPRODUCE 1. Open Akregator and open the "Pharyngula on FTB" feed. 2. Select the article " I need to send this to my kids". Circle 1 in the first attachment. 3. Click on the cartoon circled as 2 in the first attachment, which opens a new browser tab. 4. Close the new tab by clicking on the red "close" button top right, as shwon in circle 3 on th3 second attachment. 5. Now click on the following article "Relax, there aren't gojng to be any zombie pigs".akregator crashes with a segfault. OBSERVED RESULT Crash on selecting following article. EXPECTED RESULT Display next article. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.15 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION I installed the debug symbolstraceback is ... === Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff282070bc0 (LWP 1253))] Thread 24 (Thread 0x7ff149d6d700 (LWP 1355)): #0 0x7ff27151ded9 in futex_reltimed_wait_cancelable (private=, reltime=0x7ff149d6c710, expected=0, futex_word=0x7ff149d6c8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7ff27151ded9 in __pthread_cond_wait_common (abstime=0x7ff149d6c7b0, mutex=0x7ff149d6c8a8, cond=0x7ff149d6c8d0) at pthread_cond_wait.c:533 #2 0x7ff27151ded9 in __pthread_cond_timedwait (cond=0x7ff149d6c8d0, mutex=0x7ff149d6c8a8, abstime=0x7ff149d6c7b0) at pthread_cond_wait.c:667 #3 0x7ff27784d177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7ff27784dada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7ff27784dbc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7ff27780b851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7ff27780e387 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7ff27780e974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7ff27784fcd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7ff2715176db in start_thread (arg=0x7ff149d6d700) at pthread_create.c:463 #11 0x7ff27de2388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7ff14b76f700 (LWP 1309)): #0 0x7ff27151ded9 in futex_reltimed_wait_cancelable (private=, reltime=0x7ff14b76e710, expected=0, futex_word=0x7ff14b76e8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7ff27151ded9 in __pthread_cond_wait_common (abstime=0x7ff14b76e7b0, mutex=0x7ff14b76e8a8, cond=0x7ff14b76e8d0) at pthread_cond_wait.c:533 #2 0x7ff27151ded9 in __pthread_cond_timedwait (cond=0x7ff14b76e8d0, mutex=0x7ff14b76e8a8, abstime=0x7ff14b76e7b0) at pthread_cond_wait.c:667 #3 0x7ff27784d177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7ff27784dada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7ff27784dbc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7ff27780b851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7ff27780e387 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7ff27780e974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7ff27784fcd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7ff2715176db in start_thread (arg=0x7ff14b76f700) at pthread_create.c:463 #11 0x7ff27de2388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7ff1577fe700 (LWP 1290)): #0 0x7ff27de326ac in __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7ff27de34474 in ___fprintf_chk (fp=0x7ff27e0ef8b0 <_IO_stdfile_2_lock>, flag=1, format=0x7ff269b666a8 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7ff269b4e9ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7ff269b4eb44 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4
[korganizer] [Bug 385364] Timezone RRULE entry has bot UNTIL and COUNT property
https://bugs.kde.org/show_bug.cgi?id=385364 --- Comment #7 from Paul Gouin --- Comment on attachment 117519 --> https://bugs.kde.org/attachment.cgi?id=117519 PKGBUILD for patched kcalcore 18.12.1 on Arch Same issue here with kcalcore 18.12.1 on Arch Linux. Thanks to Ingo's helpful comments, I was able to patch it with the attached PKGBUILD. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 385364] Timezone RRULE entry has bot UNTIL and COUNT property
https://bugs.kde.org/show_bug.cgi?id=385364 Paul Gouin changed: What|Removed |Added CC||p...@pablomalo.fr --- Comment #6 from Paul Gouin --- Created attachment 117519 --> https://bugs.kde.org/attachment.cgi?id=117519=edit PKGBUILD for patched kcalcore 18.12.1 on Arch PKGBUILD for patched kcalcore 18.12.1 on Arch -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 401943] New: Kmail uses excessive CPU resources, heating up computer
https://bugs.kde.org/show_bug.cgi?id=401943 Bug ID: 401943 Summary: Kmail uses excessive CPU resources, heating up computer Product: kmail2 Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: paul.br...@kde.org Target Milestone: --- SUMMARY When I start Kmail, the fan starts spinning madly and seems to use up too many resources on the CPU. STEPS TO REPRODUCE 1. Start Kmail OBSERVED RESULT Fan starts spinning excessively and does not stop until Kmail is closed. top shows Kmail as the most resource-hungry process. EXPECTED RESULT None of the above. SOFTWARE/OS VERSIONS Kmail: 5.9.3 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Here is the output from top: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1389 paul 20 5718600 299452 186100 R 100.3 2.5 13:56.63 /usr/bin/kontact The computer I am using is a modern HP Envy and is powerful enough to run much more resource-hungry software without getting too hot. It is not Akonadi, since stopping, starting, fscking and vacuuming do not have any observable effects. It is not any of the other Kontact components: I have started them all separately and none has the same effect as Kmail. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 401936] "Sender Identity" changes back to default identity every time it runs
https://bugs.kde.org/show_bug.cgi?id=401936 --- Comment #2 from Paul Brown --- (In reply to Christophe Giboudeaux from comment #1) > I can't reproduce with these steps. After reopening KMail, the selected > identity is still there. Yes, it is tricky as it only happens on certain accounts. I have three IMAP accounts: one on Kolab Now, the second on GMX and the third on a private server of a company. The default identity is the Kolab Now and the one affected by the bug is the GMX. I was hoping someone could advise me on more diagnostic actions I could carry out to narrow it down. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 401936] New: "Sender Identity" changes back to default identity every time it runs
https://bugs.kde.org/show_bug.cgi?id=401936 Bug ID: 401936 Summary: "Sender Identity" changes back to default identity every time it runs Product: kmail2 Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: paul.br...@kde.org Target Milestone: --- SUMMARY In the "Folder Properties" > "General" tab, the "Sender identity" reverts to the default identity every time you restart the application. STEPS TO REPRODUCE 1. Select for a folder a different identity from the default in "Sender Identity" 2. Close Kmail/Kontact 3. Start Kmail/Kontact again and the "Sender identity" has changed back to the default one. EXPECTED RESULT That the "Sender Identity" not change from one run to the next. SOFTWARE/OS VERSIONS Kmail: 5.9.3 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION This doesn't happen consistently across all accounts. Only on folders linked to some IMAP accounts. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 398407] undeleted email with empty message body causes excessive cpu use
https://bugs.kde.org/show_bug.cgi?id=398407 --- Comment #2 from Paul Eggleton --- I forgot to mention in the preceding comment - my system is Fedora 28 and is up-to-date. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 398407] undeleted email with empty message body causes excessive cpu use
https://bugs.kde.org/show_bug.cgi?id=398407 Paul Eggleton changed: What|Removed |Added CC||bluelightning@bluelightning ||.org --- Comment #1 from Paul Eggleton --- Created attachment 116292 --> https://bugs.kde.org/attachment.cgi?id=116292=edit Script to find maildir messages with empty bodies I've had this same issue with a local maildir for about a week - high CPU usage persisting over reboots and akonadi restarts with mysqld and akonadi processes using up most of the available CPU time. I had some rules set up to move messages from an IMAP folder to the local maildir when they get to a certain age, but for some reason some of the moved messages ended up with an empty body when they arrived in the maildir, and these messages seemed to be tripping up akonadi (not at the time of moving - just by being present at the destination). This was visible via akonadiconsole - I could see the message IDs by enabling the debugger briefly, then I could use the DB Query tab to find the messages with those ids in the pimitemtable, and the "rev" field was constantly incrementing. Oddly I could not see those messages in the "Browser" tab, but at least some of them were visible in KMail. In order to work around the issue I wrote a script (attached) to find messages with an empty body in a specific directory (in my case, ~/.local/share/local-mail/inbox/new/ ) and then I moved the listed files out somewhere else. Shortly thereafter the machine calmed down, though I did have to finally run akonadictl restart to stop mysqld from using ~90% CPU so presumably there was still an expensive query running. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 399996] Kmail sometimes crashes when a message window is open
https://bugs.kde.org/show_bug.cgi?id=36 --- Comment #1 from Paul Nodine --- Created attachment 116006 --> https://bugs.kde.org/attachment.cgi?id=116006=edit New crash information added by DrKonqi kmail (5.9.2) using Qt 5.11.2 - What I was doing when the application crashed: KMail Crashed when closing an open message window. It happens quite a lot and the error is segmentation fault 11 -- Backtrace (Reduced): #7 0x7f51389bff65 in content::RenderProcessHostImpl::ShutdownRequest() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f51381d2a15 in content::mojom::RendererHostStubDispatch::Accept(content::mojom::RendererHost*, mojo::Message*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f5139fa4919 in IPC::(anonymous namespace)::ChannelAssociatedGroupController::AcceptOnProxyThread(mojo::Message) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7f5139fa3213 in void base::internal::Invoker, base::internal::PassedWrapper >, void ()>::RunImpl, base::internal::PassedWrapper > const&, 0ul, 1ul>(void (IPC::(anonymous namespace)::ChannelAssociatedGroupController::* const&)(mojo::Message), std::tuple, base::internal::PassedWrapper > const&, std::integer_sequence) [clone .isra.183] () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7f513959b6ff in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 399996] Kmail sometimes crashes when a message window is open
https://bugs.kde.org/show_bug.cgi?id=36 --- Comment #1 from Paul Nodine --- Created attachment 116006 --> https://bugs.kde.org/attachment.cgi?id=116006=edit New crash information added by DrKonqi kmail (5.9.2) using Qt 5.11.2 - What I was doing when the application crashed: KMail Crashed when closing an open message window. It happens quite a lot and the error is segmentation fault 11 -- Backtrace (Reduced): #7 0x7f51389bff65 in content::RenderProcessHostImpl::ShutdownRequest() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f51381d2a15 in content::mojom::RendererHostStubDispatch::Accept(content::mojom::RendererHost*, mojo::Message*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f5139fa4919 in IPC::(anonymous namespace)::ChannelAssociatedGroupController::AcceptOnProxyThread(mojo::Message) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7f5139fa3213 in void base::internal::Invoker, base::internal::PassedWrapper >, void ()>::RunImpl, base::internal::PassedWrapper > const&, 0ul, 1ul>(void (IPC::(anonymous namespace)::ChannelAssociatedGroupController::* const&)(mojo::Message), std::tuple, base::internal::PassedWrapper > const&, std::integer_sequence) [clone .isra.183] () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7f513959b6ff in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 --- Comment #2 from Paul Nodine --- Created attachment 116007 --> https://bugs.kde.org/attachment.cgi?id=116007=edit New crash information added by DrKonqi kmail (5.9.2) using Qt 5.11.2 - What I was doing when the application crashed: KMail Crashed when closing an open message window. It happens quite a lot and the error is segmentation fault 11 -- Backtrace (Reduced): #7 0x7f51389bff65 in content::RenderProcessHostImpl::ShutdownRequest() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f51381d2a15 in content::mojom::RendererHostStubDispatch::Accept(content::mojom::RendererHost*, mojo::Message*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f5139fa4919 in IPC::(anonymous namespace)::ChannelAssociatedGroupController::AcceptOnProxyThread(mojo::Message) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7f5139fa3213 in void base::internal::Invoker, base::internal::PassedWrapper >, void ()>::RunImpl, base::internal::PassedWrapper > const&, 0ul, 1ul>(void (IPC::(anonymous namespace)::ChannelAssociatedGroupController::* const&)(mojo::Message), std::tuple, base::internal::PassedWrapper > const&, std::integer_sequence) [clone .isra.183] () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7f513959b6ff in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 399996] Kmail sometimes crashes when a message window is open
https://bugs.kde.org/show_bug.cgi?id=36 Paul Nodine changed: What|Removed |Added CC||paul.nod...@outlook.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 391631] Identity not in list after creation
https://bugs.kde.org/show_bug.cgi?id=391631 Paul S changed: What|Removed |Added CC||ps...@comcast.net --- Comment #5 from Paul S --- I am having this issue as well, on kmail 5.9.2, running kde neon. -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 399551] Knotes Crash on start
https://bugs.kde.org/show_bug.cgi?id=399551 Paul Heeg changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #8 from Paul Heeg --- Update in Debian testing fixes the startup crashes? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 399996] New: Kmail sometimes crashes when a message window is open
https://bugs.kde.org/show_bug.cgi?id=36 Bug ID: 36 Summary: Kmail sometimes crashes when a message window is open Product: kmail2 Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: paul.nod...@outlook.com Target Milestone: --- Application: kmail (5.9.2) Qt Version: 5.11.1 Frameworks Version: 5.51.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: I had a email message window open and Kmail crashed after I closed it The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0f08d872c0 (LWP 25739))] Thread 33 (Thread 0x7f0de2407700 (LWP 31089)): #0 0x7f0efb58ded9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f0de2406a80, expected=0, futex_word=0x7f0de2406c68) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f0de2406b20, mutex=0x7f0de2406c18, cond=0x7f0de2406c40) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f0de2406c40, mutex=0x7f0de2406c18, abstime=0x7f0de2406b20) at pthread_cond_wait.c:667 #3 0x7f0ef01de837 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0ef01e0b17 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0ef01e0c02 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0ef01e5c81 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0ef01e701f in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f0ef01eff11 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f0efb5876db in start_thread (arg=0x7f0de2407700) at pthread_create.c:463 #10 0x7f0f05e0988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7f0de341f700 (LWP 31082)): #0 0x7f0efb58ded9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f0de341ea80, expected=0, futex_word=0x7f0de341ec68) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f0de341eb20, mutex=0x7f0de341ec18, cond=0x7f0de341ec40) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f0de341ec40, mutex=0x7f0de341ec18, abstime=0x7f0de341eb20) at pthread_cond_wait.c:667 #3 0x7f0ef01de837 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0ef01e0b17 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0ef01e0c02 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0ef01e5c81 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0ef01e7209 in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f0ef01eff11 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f0efb5876db in start_thread (arg=0x7f0de341f700) at pthread_create.c:463 #10 0x7f0f05e0988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7f0eab3cf700 (LWP 31040)): #0 0x7f0efb58ded9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f0eab3cea80, expected=0, futex_word=0x7f0eab3cec68) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f0eab3ceb20, mutex=0x7f0eab3cec18, cond=0x7f0eab3cec40) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f0eab3cec40, mutex=0x7f0eab3cec18, abstime=0x7f0eab3ceb20) at pthread_cond_wait.c:667 #3 0x7f0ef01de837 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0ef01e0b17 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0ef01e0c02 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6
[kmail2] [Bug 399631] New: kmail crash after update with segmentation fault, korganizer too
https://bugs.kde.org/show_bug.cgi?id=399631 Bug ID: 399631 Summary: kmail crash after update with segmentation fault, korganizer too Product: kmail2 Version: 5.7.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: paul.h...@ibaf.de Target Milestone: --- Created attachment 115549 --> https://bugs.kde.org/attachment.cgi?id=115549=edit "die gesmmelten Absturzinformationen sind nutzlos" SUMMARY STEPS TO REPRODUCE 1. update deb http://ftp.de.debian.org/debian/ testing main non-free contrib 2. start kmail from terminal 3. OBSERVED RESULT KCrash: crashing ... crashRecursionCounter = 2 KCrash: Application Name = kmail path = /usr/bin pid = 8379 KCrash: Arguments: /usr/bin/kmail KCrash: Attempting to start /usr/lib/i386-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 EXPECTED RESULT SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.49.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Happens after i updated debian today on my two separate computers. Maybe akonadi or QT problem? on laptop: QSocketNotifier: Invalid socket 9 and type 'Read', disabling ... on QSocketNotifier: Invalid socket 11 and type 'Read', disabling ... Thank you for any clue? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 398399] using + to move to next unread message keeps the current message also selected
https://bugs.kde.org/show_bug.cgi?id=398399 --- Comment #4 from paul vixie --- suse tumbleweed upgraded kmail to v5.9.1 today. i was able to reproduce the + behaviour i described earlier. but only when i was on the last previously-read message, and new unread messages had been received. + gave me a double selection: keeping the last previously-read message, but also selecting the first of the newly-received unread messages. v5.9.1 fixes a lot of other things related to mailbox and imap server asynchrony, so i am extremely grateful to all who participate as devs here. i don't know KDE or C++, so i'm strangely limited to being just-a-user of this software. please do not take any of my bug reports as critical of anyone's skills or motives -- i am trying to help with feedback of any kind. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 398399] using + to move to next unread message keeps the current message also selected
https://bugs.kde.org/show_bug.cgi?id=398399 --- Comment #2 from paul vixie --- Created attachment 114875 --> https://bugs.kde.org/attachment.cgi?id=114875=edit screen shot showing two selected messages after i read your message, i hit +, and both your message and the one following it in my inbox became selected. i took a screen shot. i attached that here. this is not a reliable problem. sometimes i can reproduce it, as now. my pane geometry may be unusual. i have sorting by date/time, aggregation by flat date, theme classic. headers are kmail 5.2, attachments are smart. i "use fixed font". -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 398399] New: using + to move to next unread message keeps the current message also selected
https://bugs.kde.org/show_bug.cgi?id=398399 Bug ID: 398399 Summary: using + to move to next unread message keeps the current message also selected Product: kmail2 Version: 5.9.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: p...@redbarn.org Target Milestone: --- if i'm focused on a message, and i hit + to move the focus to the next unread message, i end up with both the message i am coming from AND the message i am moving to, selected. this means when i then hit Delete to delete the second message, both the second and first messages are deleted. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 358265] Can't select AM while setting Start/Due time for a To-do
https://bugs.kde.org/show_bug.cgi?id=358265 Paul Beattie changed: What|Removed |Added CC||mine...@mammolaluce.com --- Comment #4 from Paul Beattie --- Still not working Plasma 5.12.6 Framework 5.44.0 All other calenders work only Korganiser with the bug -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 393815] Akregator dont show any feeds
https://bugs.kde.org/show_bug.cgi?id=393815 Paul Brown <paul.br...@kde.org> changed: What|Removed |Added CC||paul.br...@kde.org --- Comment #1 from Paul Brown <paul.br...@kde.org> --- This has also happened on Manjaro. It shows, say, 2 headlines, but it tells you there are a number of unread articles which is much higher, like 10 for example. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 393391] New: Speichern einer E-Mail Anlage (save an email attachment)
https://bugs.kde.org/show_bug.cgi?id=393391 Bug ID: 393391 Summary: Speichern einer E-Mail Anlage (save an email attachment) Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: u...@foni.net Target Milestone: --- Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.104-18.44-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I tried to save an email attachment an then the applicatan make a shutdown -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5c2ac007c0 (LWP 3375))] Thread 44 (Thread 0x7f5ac870b700 (LWP 24662)): #0 0x7f5c2358a0cf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5b0da3f6e3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f5b0dd61341 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f5c23585724 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5c27650c1d in clone () at /lib64/libc.so.6 Thread 43 (Thread 0x7f5ac8f0c700 (LWP 24661)): #0 0x7f5c2358a0cf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5b0da3f6e3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f5b0dd61341 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f5c23585724 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5c27650c1d in clone () at /lib64/libc.so.6 Thread 42 (Thread 0x7f5ac970d700 (LWP 24660)): #0 0x7f5c2358a0cf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5b0da3f6e3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f5b0dd61341 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f5c23585724 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5c27650c1d in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7f5bf97c2700 (LWP 24659)): #0 0x7f5c2358a0cf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5b0da3e70d in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f5b0dd61341 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f5c23585724 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5c27650c1d in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7f5acbc88700 (LWP 24658)): #0 0x7f5c2358a0cf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5b0dd32873 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f5b0dd32899 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f5c23585724 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5c27650c1d in clone () at /lib64/libc.so.6 Thread 39 (Thread 0x7f5bf8fc1700 (LWP 11932)): #0 0x7f5c2764837d in poll () at /lib64/libc.so.6 #1 0x7f5c22948314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5c2294842c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5c2816a33b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f5c28117feb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5c27f52f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f5c27f579e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f5c23585724 in start_thread () at /lib64/libpthread.so.0 #8 0x7f5c27650c1d in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7f5acd10c700 (LWP 7188)): #0 0x7f5c229897b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f5c22947c3e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5c229482a8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5c2294842c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f5c2816a33b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5c28117feb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f5c27f52f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f5c27f579e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f5c23585724 in start_thread () at /lib64/libpthread.so.0 #9 0x7f5c27650c1d in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7f5ace5e8700 (LWP 7186)): #0 0x7f5c2764837d in poll () at /lib64/libc.so.6 #1 0x7f5c22948314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5c2294842c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5c2816a33b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f5c28117feb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5c27f52f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f5c27f579e9 in () at
[kontact] [Bug 384113] New: Kmail chrash randomly
https://bugs.kde.org/show_bug.cgi?id=384113 Bug ID: 384113 Summary: Kmail chrash randomly Product: kontact Version: 5.4.3 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: paul.pyg...@gmail.com Target Milestone: --- Application: kontact (5.4.3) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.9.35-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: Just click on a mail. After two or three click en mail, kontact crash and close The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0a568b3840 (LWP 29245))] Thread 28 (Thread 0x7f091967b700 (LWP 1804)): #0 0x7f0a723d9c4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0967e68c23 in JSC::GCThread::gcThreadMain() () from /lib64/libQt5WebKit.so.5 #2 0x7f0968188141 in WTF::wtfThreadEntryPoint(void*) () from /lib64/libQt5WebKit.so.5 #3 0x7f0a723d466d in start_thread () from /lib64/libpthread.so.0 #4 0x7f0a759afe4d in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7f095d3ec700 (LWP 1803)): #0 0x7f0a723d9c4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0967e67bf4 in JSC::BlockAllocator::blockFreeingThreadMain() () from /lib64/libQt5WebKit.so.5 #2 0x7f0968188141 in WTF::wtfThreadEntryPoint(void*) () from /lib64/libQt5WebKit.so.5 #3 0x7f0a723d466d in start_thread () from /lib64/libpthread.so.0 #4 0x7f0a759afe4d in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f0a3e7fc700 (LWP 1797)): #0 0x7f0a723d9c4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f096815929b in WTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5WebKit.so.5 #2 0x7f09681592d9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5WebKit.so.5 #3 0x7f0a723d466d in start_thread () from /lib64/libpthread.so.0 #4 0x7f0a759afe4d in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7f0a3effd700 (LWP 1795)): #0 0x7f0a71788d9f in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #1 0x7f0a764c3e2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #2 0x7f0a7646f49a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7f0a762a93bc in QThread::exec() () from /lib64/libQt5Core.so.5 #4 0x7f0a762adff9 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f0a723d466d in start_thread () from /lib64/libpthread.so.0 #6 0x7f0a759afe4d in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f095e06d700 (LWP 29769)): #0 0x7f0a723d9c4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0a6a39b6ef in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f0a6a39be10 in base::SequencedWorkerPool::Worker::Run() () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f0a6a39bfe0 in base::SimpleThread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f0a6a398b6d in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f0a723d466d in start_thread () from /lib64/libpthread.so.0 #6 0x7f0a759afe4d in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f0963ad3700 (LWP 29293)): #0 0x7f0a717cd974 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7f0a71788220 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f0a71788bc3 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f0a71788d9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f0a764c3e2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f0a7646f49a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f0a762a93bc in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f0a762adff9 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f0a723d466d in start_thread () from /lib64/libpthread.so.0 #9 0x7f0a759afe4d in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f09642d4700 (LWP 29286)): #0 0x7ffdc6bf5b1b in clock_gettime () #1 0x7f0a759bda06 in clock_gettime () from /lib64/libc.so.6 #2 0x7f0a76355166 in qt_gettime() () from /lib64/libQt5Core.so.5 #3 0x7f0a764c1aa9 in QTimerInfoList::updateCurrentTime() () from /lib64/libQt5Core.so.5 #4 0x7f0a764c1ff5 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #5 0x7f0a764c335e in
[kontact] [Bug 380481] New: Create new mail for groupe
https://bugs.kde.org/show_bug.cgi?id=380481 Bug ID: 380481 Summary: Create new mail for groupe 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: u...@foni.net Target Milestone: --- Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.62-18.6-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: - Unusual behavior I noticed: the Mail Program runs for several days and i tried to create a new mail to a group. Then the program stops. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2aebce77c0 (LWP 3686))] Thread 36 (Thread 0x7f2ab9ffb700 (LWP 4884)): #0 0x7f2ae872449d in poll () at /lib64/libc.so.6 #1 0x7f2ae3a25314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2ae3a2542c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2ae924832b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2ae91f5fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2ae9030f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2ae90359e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f2ae4662744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2ae872cd3d in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7f299a6ac700 (LWP 4882)): #0 0x7f2ae872449d in poll () at /lib64/libc.so.6 #1 0x7f2ae3a25314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2ae3a2542c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2ae924832b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2ae91f5fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2ae9030f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2ae90359e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f2ae4662744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2ae872cd3d in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7f2aba7fc700 (LWP 4840)): #0 0x7f2ae3a24a09 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f2ae3a25230 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2ae3a2542c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2ae924832b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2ae91f5fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2ae9030f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2ae90359e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f2ae4662744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2ae872cd3d in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7f2993fff700 (LWP 4739)): #0 0x7f2ae3a66391 in g_private_get () at /usr/lib64/libglib-2.0.so.0 #1 0x7f2ae3a49e40 in g_thread_self () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2ae3a2541d in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2ae924832b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2ae91f5fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2ae9030f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2ae90359e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f2ae4662744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2ae872cd3d in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f299affd700 (LWP 4723)): #0 0x7f2ae872449d in poll () at /lib64/libc.so.6 #1 0x7f2ae3a25314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2ae3a2542c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2ae924832b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2ae91f5fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2ae9030f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2ae90359e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f2ae4662744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2ae872cd3d in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f299b7fe700 (LWP 4695)): #0 0x7f2ae872449d in poll () at /lib64/libc.so.6 #1 0x7f2ae3a25314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2ae3a2542c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2ae924832b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2ae91f5fdb in QEventLoop::exec(QFlags) () at
[kmail2] [Bug 378189] kmail often stuck in "Retrieving Folder Contents"
https://bugs.kde.org/show_bug.cgi?id=378189 --- Comment #3 from Paul Colquhoun <kdeb...@andor.dropbear.id.au> --- I have followed the directions at https://docs.kde.org/trunk5/en/pim/kmail2/clean-start-after-a-failed-migration.html to rebuild the akonadi databases from scratch, but the problem has persisted. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 378189] kmail often stuck in "Retrieving Folder Contents"
https://bugs.kde.org/show_bug.cgi?id=378189 --- Comment #2 from Paul Colquhoun <kdeb...@andor.dropbear.id.au> --- I forgot to include this: $ kmail --version kmail2 5.4.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 378189] kmail often stuck in "Retrieving Folder Contents"
https://bugs.kde.org/show_bug.cgi?id=378189 Paul Colquhoun <kdeb...@andor.dropbear.id.au> changed: What|Removed |Added CC||kdeb...@andor.dropbear.id.a ||u --- Comment #1 from Paul Colquhoun <kdeb...@andor.dropbear.id.au> --- I am also experiencing this problem. When I start kmail from a command line, and select a mailbox where the problem is happening, I get a run of errors shown, like: org.kde.pim.akonadicore: Got a stale notification for an item which was already removed. 36928 "" The number run up to 36968 with a few skipped. I have also noticed, in my attempts to fix things, that running "akonadictrl fsck" reports a list of errors, but does not fix any, as the same errors are reported on the next run. $ akonadictl fsck Looking for resources in the DB not matching a configured resource... Looking for collections not belonging to a valid resource... Checking collection tree consistency... Looking for items not belonging to a valid collection... Looking for item parts not belonging to a valid item... Looking for item flags not belonging to a valid item... Looking for overlapping external parts... Verifying external parts... Found 274 external files. Found 274 external parts. Found no unreferenced external files. Checking size treshold changes... Found 0 parts to be moved to external files Found 0 parts to be moved to database Looking for dirty objects... Collection "Search" (id: 1) has no RID. Found 1 collections without RID. Item "36378" has no RID. Item "36553" has no RID. Item "36554" has no RID. Item "36556" has no RID. Item "36575" has no RID. Item "36690" has no RID. Item "36709" has no RID. Item "36712" has no RID. Item "36723" has no RID. Item "36727" has no RID. Item "36733" has no RID. Item "36736" has no RID. Item "36739" has no RID. Item "36748" has no RID. Item "36759" has no RID. Item "36762" has no RID. Item "36764" has no RID. Item "36768" has no RID. Item "36770" has no RID. Item "36772" has no RID. Item "36779" has no RID. Item "36811" has no RID. Item "36924" has no RID. Found 23 items without RID. Found 0 dirty items. Looking for rid-duplicates not matching the content mime-type of the parent collection Checking Local Folders Checking Personal Contacts Checking Personal Contacts Found duplicates 022265b7-7fa6-4835-8b83-9afea8ccc538.vcf Checking Search Checking ASP Checking Accounts Checking Aust_Post Checking Bank Checking Companies Checking DandD Checking Friends_and_Family Checking From_Me Checking Getup Checking ITunes Checking Important Checking Internet_Sites Checking JUNK Found duplicates 1490556472.R580.bluering Checking Mailing_Lists Checking Misc Checking Orders Checking Software-Order Checking TAFE_related Checking Telegraph Checking Tickets Checking Web_Sites Checking drafts Checking inbox Checking muttout Checking outbox Checking sent-mail Checking templates Checking trash Checking Amazon.com Checking Apple Checking Athletes_foot Checking Australian_Unity Checking Bigpond Checking Bioware Checking Borders Checking Change.org Checking Computerworld Checking Epson Checking Food_Delivery Checking Foxtel Checking GoodOldGames_GOG.com Checking IceTV Found duplicates 1490549272.R827.bluering Checking Iolo Checking JB-Hi-Fi Checking Jacksons Checking Livecode Checking NRMA Checking Navman Checking New_Frog Checking New_Scientist Checking PacktPub Checking Pokemon Checking RTA Checking Realestate_Agent Checking Roses_Only Checking SMH.com.au Checking Techbuy Checking Telstra-Notices Checking Ticketmaster Checking Turbine Checking lazypatch Checking Boystown_Lottery Checking Facebook Checking Flatmates Checking Instagram Checking Internet Checking LinkedIn Checking Linux_Weekly_News Checking Littlemutt Checking No-IP Checking Pair.com Checking PayPal Checking Twitter Checking ebay Found duplicates 1490593373.R703.bluering Checking makeuseof Checking Gentoo Found duplicates 1490520173.R377.bluering Found duplicates 1490520474.R132.bluering Found duplicates 1490521075.R588.bluering Found duplicates 1490534871.R650.bluering Found duplicates 1490539671.R833.bluering Found duplicates 1490550472.R270.bluering Found duplicates 1490552872.R277.bluering Found duplicates 1490587073.R750.bluering Checking Gentoo-amd64 Checking Job_Hunting Found duplicates 1490561272.R98.bluering Checking Lotto-Results Checking NSWCC Checking Portage-elogs Checking RedHat_Announce Checking Red_Hat Checking SAGE-AU Checking Stats-Tracker Checking The_Troll Checking Yahoo_mail Checking gmail.com Checking rkhunter Checking News-Filters
[Akonadi] [Bug 335090] Akonadi Dav Resource: Broken State / Unexpected Error 401
https://bugs.kde.org/show_bug.cgi?id=335090 Paul Sommer n...@paul-sommer.de changed: What|Removed |Added CC||n...@paul-sommer.de --- Comment #42 from Paul Sommer n...@paul-sommer.de --- Unfortunately this critical bug exists for years now, and nobody seems to be interested (skilled?) to fix it. I like Kontact, but meanwhile I only use it to look up telephone numbers. What a waste. Still searching for a nice desktop companion for my OwnCloud server. -- 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 335090] Akonadi Dav Resource: Broken State / Unexpected Error 401
https://bugs.kde.org/show_bug.cgi?id=335090 --- Comment #44 from Paul Sommer n...@paul-sommer.de --- Oh! This sounds like good news to me. Sometimes it might be better to design things new when they come to age rather than putting a patch here and an extension there. Good luck for the relaunch. -- 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 346583] New: Kontact looses sync to owncloud
https://bugs.kde.org/show_bug.cgi?id=346583 Bug ID: 346583 Summary: Kontact looses sync to owncloud Product: kontact Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: n...@paul-sommer.de The contact and calendar looses sync on owncloud after a while. I use ownCloud 7.0.4 (stable) to sync my desktop and smartfones. When I add the server for the address book and calendar everything works fine. Changes are spread to all connected devices. After some while Kontact refuses to get updated contents and to push updates to the server. Pressing F5 doesn't help. There's no error message. It just does nothing. In former versions I got a message like For sync the ressource has to be set online. Should I do that? But this didn't help either. In the current version there's no such message anymore. a akonadictl restart helps in MOST of the cases. This is very annoying as I already missed appointments because of the broken sync. If I can provide any logs or output, please let me know. -- 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 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 --- Comment #18 from Paul Bennett paul_e.benn...@topmail.co.uk --- Some new information. I have noticed that when hitting the APPLY button during the creation of an event that it will appear in the upcoming events list in Summary. I have since gone back to some other events that were not shown and made a small edit in order to be able to hit the Apply buton and these then appear in the Summary List as well. Those that are merely saved on the OK button do not appear. -- 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 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 --- Comment #20 from Paul Bennett paul_e.benn...@topmail.co.uk --- On 14/04/2015 at 7:31 PM, Wolfgang Bauer wrote:https://bugs.kde.org/show_bug.cgi?id=327256 --- Comment #19 from Wolfgang Bauer --- (In reply to Paul Bennett from comment #18) Some new information. New information? This bug is fixed since over half a year (Kontact 4.14.1)... I have noticed that when hitting the APPLY button during the creation of an event that it will appear in the upcoming events list in Summary. I have since gone back to some other events that were not shown and made a small edit in order to be able to hit the Apply buton and these then appear in the Summary List as well. Those that are merely saved on the OK button do not appear. Hm? I cannot reproduce that here at all with the latest 4.14.6. They appear just fine if I only click on OK. Do they get saved in the calendar at all when you don't hit Apply? Are they shown in KOrganizer? If not, you're seeing a completely different bug, and should report it separately. On second thought, if the issue you mention is reproducible, you should open a new bug report in any case. I don't think that's in any way related to this one, and this one is marked as fixed (and it is fixed for me and also other people). You should probably also specify which Kontact version you are using (if it's not the latest one, you should try to update and see whether the problem persists), and probably some more information like what kind of calendars have that problem, explicit steps to reproduce,... -- 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 338658] GMail, Novell Groupwise, other IMAP: Multiple merge candidates, aborting
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #22 from Paul Eggleton bluelightn...@bluelightning.org --- I have at least figured out how to fix the database in order to get directories syncing again using the Akonadi Console. (Disclaimer: this worked for me, may not work for you, you might lose data if you aren't careful, etc.) First I searched to find the duplicate keys using the DB Console tab with the following query: SELECT pimitemtable.*, collectiontable.name FROM pimitemtable INNER JOIN pimitemtable dup ON pimitemtable.id != dup.id and pimitemtable.remoteId = dup.remoteId and pimitemtable.collectionId = dup.collectionId INNER JOIN collectiontable ON pimitemtable.collectionId = collectiontable.id ORDER by pimitemtable.remoteId Then I looked for the items specifically in the folders that I knew were failing to sync with the Multiple merge candidates, aborting error, then used the Id to track down one of the duplicate items in the Browser tab and then deleted it there from the context menu. (There are still others with duplicate ids, but I have not deleted those since they don't appear to be causing any problems.) I then restarted the akonadi server, and then reloaded the folder in KMail and voila, the folder now synchronises successfully. -- 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 338658] GMail: Multiple merge candidates, aborting
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #13 from Paul Gideon Dann pdgiddie+...@gmail.com --- Sadly, I've had to abandon KMail for the time being, as either this issue or something related to it is causing the Akonadi agents for my GMail IMAP to stop responding. I can retrieve e-mail if I kill and restart them, but they only last for a couple of minutes before freezing up again. I've had to resort to the GMail web interface for several months now :( -- 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 338658] GMail: Multiple merge candidates, aborting
https://bugs.kde.org/show_bug.cgi?id=338658 Paul Eggleton bluelightn...@bluelightning.org changed: What|Removed |Added CC||bluelightning@bluelightning ||.org -- 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 340015] Filter rules no longer matching after upgrade
https://bugs.kde.org/show_bug.cgi?id=340015 Paul Eggleton bluelightn...@bluelightning.org changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #13 from Paul Eggleton bluelightn...@bluelightning.org --- Just got the fix here too in F20, thanks!! -- 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 340794] New: KMail: error during new mail scanning interval
https://bugs.kde.org/show_bug.cgi?id=340794 Bug ID: 340794 Summary: KMail: error during new mail scanning interval Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: paulmontaq...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.14) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.13.0-39-generic x86_64 Distribution: Ubuntu 14.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I left KMail running in hte background while browsing using Firefox. I guess during KMail's mail scanning interval this error occurred -- Backtrace: Application: Microsoft Live Hotmail of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f8533f827c0 (LWP 18595))] Thread 2 (Thread 0x7f851f876700 (LWP 18302)): #0 0x7f852f8dc36d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f852e891c10 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f852e850b14 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f852e850f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f852e8510ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f85335b27be in QEventDispatcherGlib::processEvents (this=0x7f8510022f00, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x7f85335840af in QEventLoop::processEvents (this=this@entry=0x7f851f875e20, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f85335843a5 in QEventLoop::exec (this=this@entry=0x7f851f875e20, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f8533480c5f in QThread::exec (this=optimized out) at thread/qthread.cpp:537 #9 0x7f853348332f in QThreadPrivate::start (arg=0xd629d0) at thread/qthread_unix.cpp:349 #10 0x7f852ef40182 in start_thread (arg=0x7f851f876700) at pthread_create.c:312 #11 0x7f852f8eafbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f8533f827c0 (LWP 18595)): [KCrash Handler] #6 operator char const* (this=optimized out) at /usr/include/qt4/QtCore/qbytearray.h:425 #7 KIMAP::Session::selectedMailBox (this=0xabc2e0) at ../../kimap/session.cpp:449 #8 0x00446b1f in RetrieveItemsTask::startRetrievalTasks (this=this@entry=0xe1f8b0) at ../../../resources/imap/retrieveitemstask.cpp:150 #9 0x00446e0e in RetrieveItemsTask::doStart (this=0xe1f8b0, session=optimized out) at ../../../resources/imap/retrieveitemstask.cpp:98 #10 0x0043ab13 in ResourceTask::onSessionRequested (this=0xe1f8b0, requestId=optimized out, session=0xabc2e0, errorCode=0) at ../../../resources/imap/resourcetask.cpp:119 #11 0x004648b5 in ResourceTask::qt_static_metacall (_o=0x7fff36211920, _c=11256544, _id=-1, _a=0xbb9620) at moc_resourcetask.cpp:69 #12 0x7f853359987a in QMetaObject::activate (sender=sender@entry=0xba31a0, m=m@entry=0x482160 SessionPool::staticMetaObject, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fff36211ba0) at kernel/qobject.cpp:3539 #13 0x00464962 in SessionPool::sessionRequestDone (this=this@entry=0xba31a0, _t1=_t1@entry=739, _t2=_t2@entry=0xabc2e0, _t3=_t3@entry=0, _t4=...) at moc_sessionpool.cpp:153 #14 0x0045086a in SessionPool::processPendingRequests (this=0xba31a0) at ../../../resources/imap/sessionpool.cpp:257 #15 0x00464a2d in SessionPool::qt_static_metacall (_o=0x7fff36211920, _c=11256544, _id=-1, _a=0xbb9620) at moc_sessionpool.cpp:92 #16 0x7f853359dc1e in QObject::event (this=0xba31a0, e=optimized out) at kernel/qobject.cpp:1194 #17 0x7f8532919e2c in QApplicationPrivate::notify_helper (this=this@entry=0xa24f50, receiver=receiver@entry=0xba31a0, e=e@entry=0xc17d90) at kernel/qapplication.cpp:4567 #18 0x7f85329204a0 in QApplication::notify (this=this@entry=0x7fff36212330, receiver=receiver@entry=0xba31a0, e=e@entry=0xc17d90) at kernel/qapplication.cpp:4353 #19 0x7f8530a41cca in KApplication::notify (this=0x7fff36212330, receiver=0xba31a0, event=0xc17d90) at ../../kdeui/kernel/kapplication.cpp:311 #20 0x7f85335854dd in QCoreApplication::notifyInternal (this=0x7fff36212330, receiver=receiver@entry=0xba31a0, event=event@entry=0xc17d90) at kernel/qcoreapplication.cpp:953 #21 0x7f8533588b3d in sendEvent (event=0xc17d90, receiver=0xba31a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x9de220) at kernel/qcoreapplication.cpp:1577 #23
[kmail2] [Bug 340458] New: Dragging and dropping Inbox folder results in unexpected behaviour
https://bugs.kde.org/show_bug.cgi?id=340458 Bug ID: 340458 Summary: Dragging and dropping Inbox folder results in unexpected behaviour Product: kmail2 Version: 4.14.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: bluelightn...@bluelightning.org I was trying to drag some messages from one folder to another, but I think my mouse button momentarily disengaged and instead I ended up dragging the entire Inbox folder down into one of the subfolders. Once in this state it is impossible to drag the inbox back to where it should go (underneath the resource). When I closed KMail and reopened it, the inbox was back to where it should be, but it had to resync all items in the folder. If moving the inbox isn't sensible or cannot work then it seems to me it ought to be prevented from being done in the first place. Reproducible: Didn't try I'm using disconnected 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
[Akonadi] [Bug 340015] New: Filter rules no longer matching after upgrade
https://bugs.kde.org/show_bug.cgi?id=340015 Bug ID: 340015 Summary: Filter rules no longer matching after upgrade Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Mail Filter Agent Assignee: kdepim-bugs@kde.org Reporter: bluelightn...@bluelightning.org I just upgraded from KDE SC 4.14.1 to 4.14.2, and now my mail filters set up in KMail no longer work, either on incoming mail or when manually applying filtering on individual messages. Most of my filters are of the order of matching on a mailing list (as created by Create filter from message - From mailing list and move into a specific IMAP folder. New rules created using this method with the new version don't seem to work either, so it doesn't appear that it's some kind of corruption of the old filter rules. Enabling filter logging, manually applying filtering on a message that should match one of the rules and using the filter log viewer shows that it is at least running through all of the filters, but none of them are matching including the one that should match the message. Reproducible: Always Actual Results: No filtering occurs. Expected Results: Mail filter applies when filter conditions match. I'm using IMAP folders (disconnected IMAP) if it makes a difference. -- 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 338658] GMail: Multiple merge candidates, aborting
https://bugs.kde.org/show_bug.cgi?id=338658 Paul Gideon Dann pdgiddie+...@gmail.com changed: What|Removed |Added Severity|normal |grave --- Comment #9 from Paul Gideon Dann pdgiddie+...@gmail.com --- Yes, I'm getting the same thing: the imap resources get stuck, and I have to killall axonadi_imap_resource, and then restart them via the Akonadi Console in order to un-stick them. I've pretty much abandoned KMail for now as I can't use it for more than 10mins before it gets stuck. I've had to fall back to the GMail web app until this is resolved. -- 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
[akregator] [Bug 336417] Akregator crashes when being closed
https://bugs.kde.org/show_bug.cgi?id=336417 Paul White b...@pcwhite.com changed: What|Removed |Added CC||b...@pcwhite.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 328636] Calendar event isn't syncronized with google calendar after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=328636 Paul Gideon Dann pdgiddie+...@gmail.com changed: What|Removed |Added CC||pdgiddie+...@gmail.com --- Comment #6 from Paul Gideon Dann pdgiddie+...@gmail.com --- I have a very similar issue, although I find that my Google calendar resources develop this issue even if the machine has not slept: in particular, I get the same Requested resource does not exist. Google replied 'Not Found' error message whenever the resource attempts to refresh the calendar list, which I've set it to do at regular intervals. I've found that the resources behave correctly again if I restart them from the Akonadi console. -- 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 338658] GMail: Multiple merge candidates, aborting
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #4 from Paul Gideon Dann pdgiddie+...@gmail.com --- Agreed: I have also noticed that whereas previously when mail was marked as Read in one folder, it would eventually be marked as Read in another, this no longer happens. I'm sure that's no coincidence :p -- 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 338658] New: GMail: Multiple merge candidates, aborting
https://bugs.kde.org/show_bug.cgi?id=338658 Bug ID: 338658 Summary: GMail: Multiple merge candidates, aborting Product: Akonadi Version: 1.13.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: pdgiddie+...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org After upgrading to Akonadi 1.13.0 / Kontact 4.14.0 I've been getting quite a few notifications saying: Multiple merge candidates, aborting I'm getting this on both of the GMail accounts I've set up with. I've tried removing the akonadi database at ~/.local/share/akonadi. This greatly reduced the number of messages I was receiving, but once Akonadi had finished caching what it needed in the database, these messages started occurring regularly again (though only one at a time now), presumably when it polls for new mail. I've tried shutting down Akonadi and running akonadictl fsck, but that doesn't have any effect. What can I do to help diagnose the issue? -- 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 338658] GMail: Multiple merge candidates, aborting
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #1 from Paul Gideon Dann pdgiddie+...@gmail.com --- Sorry, I intended to specify ...on both of the GMail accounts I've set up with *IMAP* -- 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 297930] Kmail hangs on Retrieving folder contents ... please wait
https://bugs.kde.org/show_bug.cgi?id=297930 Paul Campbell p...@taniwha.com changed: What|Removed |Added CC||p...@taniwha.com --- Comment #12 from Paul Campbell p...@taniwha.com --- I ran into this problem when taking the new KDE upgrade in kubuntu- trusty this week All emails from meetup.com (containing .ics files) cause kmail to freeze, restarting akonadi unfreezes, but touching the email makes it freeze again. The fix I found was to go into the akonadi setup (Control Panel-Personal Information) and create an ics calendar entry (I actually made several types of calender entry so it might have been something else) - this means I can now read the emails, and even better delete them -- 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 336687] KMail Crashes with nepomukserver and Trying to Search
https://bugs.kde.org/show_bug.cgi?id=336687 --- Comment #2 from William Paul Liggett junkt...@junktext.org --- Okay, thanks for letting me know, Laurent. I'll look forward to trying out the newer version of KMail once it is part of my distro's repository. Take care! -- 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 336687] New: KMail Crashes with nepomukserver and Trying to Search
https://bugs.kde.org/show_bug.cgi?id=336687 Bug ID: 336687 Summary: KMail Crashes with nepomukserver and Trying to Search Classification: Unclassified Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: junkt...@junktext.org Application: kmail (4.12.5) KDE Platform Version: 4.12.5 Qt Version: 4.8.6 Operating System: Linux 3.14.8-200.fc20.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: See the bug report for #311184 as I did a write-up of my background of how I arrived at this situation. Essentially, I am on GNOME Shell v3.10.2 (Fedora 20, 64-bit) and I am using KMail v4.12.5, and I was unable to use the full e-mail search capability (the binoculars icon). So, I ran the nepomukserver command in terminal to make the full search dialog actually work. However, this is where this bug comes in, after I type something for the search dialog to look for and right when I click on Search, KMail crashes from a segmentation fault. --William (junktext) The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7feb1d1a4900 (LWP 1949))] Thread 4 (Thread 0x7fea9993b700 (LWP 2043)): #0 0x7feb165c179d in read () from /lib64/libc.so.6 #1 0x7feafe242eb1 in ?? () from /usr/lib64/nvidia/tls/libnvidia-tls.so.331.79 #2 0x7feb09c597b0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #3 0x7feb09c1909c in g_main_context_check () from /lib64/libglib-2.0.so.0 #4 0x7feb09c19533 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #5 0x7feb09c19a3a in g_main_loop_run () from /lib64/libglib-2.0.so.0 #6 0x7feb0551f376 in gdbus_shared_thread_func () from /lib64/libgio-2.0.so.0 #7 0x7feb09c3ea45 in g_thread_proxy () from /lib64/libglib-2.0.so.0 #8 0x7feb1876df33 in start_thread () from /lib64/libpthread.so.0 #9 0x7feb165cfded in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fea93dda700 (LWP 2045)): #0 0x7feb18771d20 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7feb0eb411bd in JSC::BlockAllocator::blockFreeingThreadMain() () from /lib64/libQtWebKit.so.4 #2 0x7feb0ee33a86 in WTF::wtfThreadEntryPoint(void*) () from /lib64/libQtWebKit.so.4 #3 0x7feb1876df33 in start_thread () from /lib64/libpthread.so.0 #4 0x7feb165cfded in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fea91e95700 (LWP 2047)): #0 0x7fff52d2875d in clock_gettime () #1 0x7feb165ddf3d in clock_gettime () from /lib64/libc.so.6 #2 0x7feb17192afb in qt_gettime() () from /lib64/libQtCore.so.4 #3 0x7feb17275f49 in QTimerInfoList::updateCurrentTime() () from /lib64/libQtCore.so.4 #4 0x7feb17274d27 in timerSourceCheckHelper(GTimerSource*) () from /lib64/libQtCore.so.4 #5 0x7feb09c18ff9 in g_main_context_check () from /lib64/libglib-2.0.so.0 #6 0x7feb09c19533 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #7 0x7feb09c196dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #8 0x7feb17274a7e in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #9 0x7feb1724495f in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #10 0x7feb17244cad in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #11 0x7feb17138e8f in QThread::exec() () from /lib64/libQtCore.so.4 #12 0x7feb1713b6bf in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #13 0x7feb1876df33 in start_thread () from /lib64/libpthread.so.0 #14 0x7feb165cfded in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7feb1d1a4900 (LWP 1949)): [KCrash Handler] #5 0x7feb19aa1be0 in Akonadi::PersistentSearchAttribute::setQueryLanguage(QString const) () from /lib64/libakonadi-kde.so.4 #6 0x7feb1bf23b66 in KMail::SearchWindow::slotSearch() () from /lib64/libkmailprivate.so.4 #7 0x7feb1bf283c5 in KMail::SearchWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libkmailprivate.so.4 #8 0x7feb1725a938 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib64/libQtCore.so.4 #9 0x7feb182d2ce2 in QAbstractButton::clicked(bool) () from /lib64/libQtGui.so.4 #10 0x7feb18015c23 in QAbstractButtonPrivate::emitClicked() () from /lib64/libQtGui.so.4 #11 0x7feb18016fd7 in QAbstractButtonPrivate::click() () from /lib64/libQtGui.so.4 #12 0x7feb180170dc in
[kmail2] [Bug 311184] Everlasting Please wait while the message is transferred
https://bugs.kde.org/show_bug.cgi?id=311184 --- Comment #5 from William Paul Liggett junkt...@junktext.org --- My apologies, I've just restarted my computer and KMail can now open up e-mails once again. However, before I restarted I did fully restart KMail a number of times (I had to use the kill -9 method as it wouldn't die. Well, visually the app would quit but I could still see it in ps aux). However, out of curiosity (after rebooting and getting KMail to work again), I re-ran nepomukserver in terminal and after I clicked on the binocular icon, KMail crashed via a segmentation fault. I opened a new bug report on this matter over at: https://bugs.kde.org/show_bug.cgi?id=336687 --William -- 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 311184] Everlasting Please wait while the message is transferred
https://bugs.kde.org/show_bug.cgi?id=311184 William Paul Liggett junkt...@junktext.org changed: What|Removed |Added CC||junkt...@junktext.org --- Comment #4 from William Paul Liggett junkt...@junktext.org --- Yeah, I am having the same issues that the original poster, Bernd Oliver Sünderhauf, mentioned two years ago, but I may have arrived at the same conditions via a different path. I am using KMail v4.12.5 on GNOME Shell v3.10.2 (Fedora 20, 64-bit) and this is a summary of my issue to be clear: 1. I cannot open any e-mails any longer. Double-clicking on a message does nothing. It doesn't even attempt to open the e-mail. When I right-clicking on a message and select Reply (or if I press the R key), all that happens is an endless loading dialog that says, Please wait while the message is transferred. Nothing ever happens. 2. I was using KMail successfully, with two different e-mail accounts. One was an IMAP (via SSL) connection to a regular e-mail server, and my other e-mail was a connection to a GMail account. Both were working fine until... 3a. Since I am on Fedora (on GNOME Shell, not KDE), I was trying to figure out how to get the full search feature (Nepomuk) working. As when I would click on the icon with the binoculars (that has the pop-up label Open Full Search), I would simply get a message saying: Search Not Available - KMail The Nepomuk semantic search service is not available. Searching is not possible without it. You can enable it in System Settings. 3b. Keep in mind that I am on GNOME Shell, not KDE, thus I don't think the reference to me opening up and enabling Nepomuk in System Settings means much to me (I cannot find such a menu on GNOME Shell). After searching around on the forums/bug reports, I ran across hints about needing to start the Nepomuk program and to monitor what it is doing via the Akonadi Console. In short on this regard, I ran the command nepomukserver in terminal then I was able to get Akonadi Console to make the Akonadi Nepomuk Feeder agent to fully index my e-mail. I was happy about this, since I wanted to search my e-mail more thoroughly and I was finally able to get the binocular icon to show me a search dialog (instead of the error message). Yet, this new search dialog ended up being worthless, since it couldn't pull up any e-mails I searched for. 4. This is when I noticed the problem of not being able to open up any of my e-mail messages as I stated at paragraph label 1. Thus, I think Nepomuk destroyed my KMail. In the meantime, I'll head back to using GNOME's Evolution. But, I'll leave my KMail in this state of disrepair in case somebody has a suggestion. --William -- 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
[knotes] [Bug 334345] New: KNotes fails to run if Kontact/KMail is already running
https://bugs.kde.org/show_bug.cgi?id=334345 Bug ID: 334345 Summary: KNotes fails to run if Kontact/KMail is already running Classification: Unclassified Product: knotes Version: 4.13 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: snow...@mtaonline.net CC: myr...@kde.org If Kontact/KMail is running, launching KNotes incorrectly takes you to Kontact/KMail application but does not present a KNote. If Kontact/KMail is not running, KNotes launches correctly and presents a KNote for editing. Reproducible: Always Steps to Reproduce: 1. Launch Kontact/Kmail 2. Launch KNotes 3. KNotes fails to load Actual Results: KNotes takes me to my running instance of Kontact/KMail and opens no notes. Expected Results: KNotes should launch and present a KNote on the desktop for editing. KNotes does work properly if Kontact/KMail isn't running. When Kontact/KMail is running, KNotes fails to launch. Interestingly, if I launch KNotes without Kontact/KMail running, in which case KNotes loads and operates properly, to include placement of the running KNotes icon in the System Tray, and I then launch Kontact/KMail, the Popup Notes in Kontact/KMail is unfunctional. If I then quit KNotes, Kontact/KMail Popup Notes performs normally. Kubuntu: 14.04 64-bit KDE: 4.13.0 KNotes: 4:4.13.0-0ubuntu1 Kontact: 4:4.13.0-0ubuntu1 KMail: 4:4.13.0-0ubuntu1 Kernel: 3.13.0-24-generic CPU: Intel i3 M380 -- 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
[knotes] [Bug 334345] KNotes fails to run if Kontact/KMail is already running
https://bugs.kde.org/show_bug.cgi?id=334345 --- Comment #1 from Paul Loughman snow...@mtaonline.net --- If I create a KNote with Kontact/KMail not running, save/close KNotes and then launch Kontact/KMail and click on Popup Notes, the note created with KNotes is shown and editable. -- 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
[knotes] [Bug 334345] KNotes fails to run if Kontact/KMail is already running
https://bugs.kde.org/show_bug.cgi?id=334345 --- Comment #2 from Paul Loughman snow...@mtaonline.net --- If KNotes is not running and I create a Popup Notes in Kontact/KMail and then quite Kontact/Kmail, launching KNotes sees/presents the Popup Note created in Kontact/KMail. -- 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 296036] Local Folders: Error: Unsupported type.
https://bugs.kde.org/show_bug.cgi?id=296036 Paul Gideon Dann pdgiddie+...@gmail.com changed: What|Removed |Added CC||pdgiddie+...@gmail.com --- Comment #9 from Paul Gideon Dann pdgiddie+...@gmail.com --- This has just started happening for me in KDE 4.12.4, immediately after upgrade. -- 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 332345] Kontact crashes on launch
https://bugs.kde.org/show_bug.cgi?id=332345 Paul Loughman snow...@mtaonline.net changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Paul Loughman snow...@mtaonline.net --- Resolved after package updates of 20-March-2014. -- 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 332345] New: Kontact/Kmail crashes on launch
https://bugs.kde.org/show_bug.cgi?id=332345 Bug ID: 332345 Summary: Kontact/Kmail crashes on launch Classification: Unclassified Product: kontact Version: 4.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: snow...@mtaonline.net Application: kontact (4.12.3) KDE Platform Version: 4.12.90 Qt Version: 4.8.6 Operating System: Linux 3.13.0-18-generic x86_64 Distribution: Ubuntu Trusty Tahr (development branch) -- Information about the crash: I updated the package cache and dist-upgraded. A reboot was indicated and I did reboot. After logging in I launched Kontact and it immediately crashed. The following packages were dist-upgraded: 2014-03-19 (dist-upgrade) The following packages will be upgraded: audiocd-kio bash bc cmake cmake-data cups cups-bsd cups-client cups-common cups-core-drivers cups-daemon cups-ppdc cups-server-common dc dragonplayer kaccessible kamera kcalc kde-base-artwork kde-l10n-engb kde-wallpapers-default kde-zeroconf kdegames-card-data kdegames-data kdegames-mahjongg-data kdegraphics-strigi-analyzer kdelibs-bin kdelibs5-data kdelibs5-dev kdelibs5-plugins kdemultimedia-kio-plugins kdenetwork-filesharing kdepimlibs-kio-plugins kdoctools kio-audiocd kmag kmahjongg kmix kpat kppp krdc krfb ksnapshot ksystemlog kwalletmanager language-selector-common libakonadi-calendar4 libakonadi-contact4 libakonadi-kabc4 libakonadi-kcal4 libakonadi-kde4 libakonadi-kmime4 libakonadi-notes4 libakonadi-socialutils4 libcups2 libcups2:i386 libcupscgi1 libcupsimage2 libcupsimage2:i386 libcupsmime1 libcupsppdc1 libdbusmenu-glib4 libdbusmenu-gtk3-4 libdbusmenu-gtk4 libglib2.0-0 libglib2.0-0:i386 libglib2.0-bin libglib2.0-data libgpgme++2 libkabc4 libkalarmcal2 libkblog4 libkcal4 libkcalcore4 libkcalutils4 libkcddb4 libkcmutils4 libkcompactdisc4 libkdcraw-data libkdcraw23 libkde3support4 libkdeclarative5 libkdecore5 libkdegames6 libkdesu5 libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4 libkexiv2-11 libkexiv2-data libkfile4 libkholidays4 libkhtml5 libkidletime4 libkimap4 libkimproxy4 libkio5 libkipi-data libkipi11 libkjsapi4 libkjsembed4 libkldap4 libkmahjongglib4 libkmbox4 libkmediaplayer4 libkmime4 libknewstuff2-4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkontactinterface4 libkparts4 libkpimidentities4 libkpimtextedit4 libkpimutils4 libkprintutils4 libkpty4 libkresources4 libkrosscore4 libkrossui4 libksane-data libksane0 libktexteditor4 libktnef4 libkunitconversion4 libkutils4 libkxmlrpcclient4 libmailtransport4 libmicroblog4 libnepomuk4 libnepomukquery4a libnepomukutils4 libplasma3 libqgpgme1 libqmobipocket1 librsvg2-2 librsvg2-2:i386 librsvg2-common librsvg2-common:i386 libsolid4 libsyndication4 libthreadweaver4 oracle-java8-installer print-manager python-apt python-apt-common python3-apt 148 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7fd18f846800 (LWP 4612))] Thread 3 (Thread 0x7fd17013f700 (LWP 4613)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd18a5eb3bd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fd18a5eb3f9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fd186d0c182 in start_thread (arg=0x7fd17013f700) at pthread_create.c:312 #4 0x7fd18cdbe12d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7fd12f83c700 (LWP 4614)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd18a32bd2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fd18a61ac76 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fd186d0c182 in start_thread (arg=0x7fd12f83c700) at pthread_create.c:312 #4 0x7fd18cdbe12d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7fd18f846800 (LWP 4612)): [KCrash Handler] #6 0x7fd18d51f992 in QObject::connect (sender=0x7fd12c8636f8 vtable for KMailPlugin+24, signal=signal@entry=0x7fd18f48544e 2destroyed(), receiver=receiver@entry=0x17e81e0, method=method@entry=0x7fd18f48543d 1partDestroyed(), type=type@entry=Qt::AutoConnection) at kernel/qobject.cpp:2546 #7 0x7fd18f482dc6 in connect (atype=Qt::AutoConnection, amember=0x7fd18f48543d 1partDestroyed(), asignal=0x7fd18f48544e 2destroyed(), asender=optimized out, this=0x17e81e0) at /usr/include/qt4/QtCore/qobject.h:339 #8 KontactInterface::Plugin::part (this=0x17e81e0) at ../../kontactinterface/plugin.cpp:195 #9 0x7fd18f04a3a1 in
[kontact] [Bug 332345] Kontact crashes on launch
https://bugs.kde.org/show_bug.cgi?id=332345 Paul Loughman snow...@mtaonline.net changed: What|Removed |Added Summary|Kontact/Kmail crashes on|Kontact crashes on launch |launch | -- 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 332345] Kontact crashes on launch
https://bugs.kde.org/show_bug.cgi?id=332345 --- Comment #1 from Paul Loughman snow...@mtaonline.net --- Kontact alone crashes. KMail, KOrganizer, KAdressBook, when launched separately work fine. -- 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 318934] KMail message list doesn't show an horizontal scroll bar when mails has many fwds
https://bugs.kde.org/show_bug.cgi?id=318934 Paul Gideon Dann pdgiddie+...@gmail.com changed: What|Removed |Added CC||pdgiddie+...@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
