[akregator] [Bug 445351] Akregator always wants to recover the session on boot
https://bugs.kde.org/show_bug.cgi?id=445351 Jan Wesselink changed: What|Removed |Added Platform|Arch Linux |Debian stable Version|5.18.3 |5.22.3 CC||wessel...@gmail.com --- Comment #6 from Jan Wesselink --- Same thing here while using wayland on desktop HP prodesk 400 g5. Akregator opens screen to restore last session, is wasnt shutdown properly it says. When starting with x11 it doenst give any problems. akregator 5.22.3 (22.12.3) debian 12 stable KDE -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 412722] KOrganizer does not show some events from EWS resource
https://bugs.kde.org/show_bug.cgi?id=412722 Jan Bundesmann changed: What|Removed |Added CC||k...@knofafo.de --- Comment #16 from Jan Bundesmann --- This might be the same bug that's bothering me: https://bugs.kde.org/show_bug.cgi?id=421916 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 471414] Application: Kontact (kontact), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=471414 Jan Iversen changed: What|Removed |Added CC||jan.iver...@mailbox.org -- 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.
[akregator] [Bug 311311] Select last seen feed/article when starting and the introduction page is disabled
https://bugs.kde.org/show_bug.cgi?id=311311 Jan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 423684] New: Akonadi crashing due to MySQL Socket is gone
https://bugs.kde.org/show_bug.cgi?id=423684 Bug ID: 423684 Summary: Akonadi crashing due to MySQL Socket is gone Product: Akonadi Version: 5.13.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: malte.ge...@googlemail.com Target Milestone: --- After a while akonadi is crashing, because of a communication error. The MySQL sockets seems to disappear, even if the MySQL server is still running. # MySQL Server still running after Akonadi crash /usr/sbin/mysqld-akonadi --defaults-file=/home/maltegerth/.local/share/akonadi/mysql.conf --datadir=/home/maltegerth/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid # Socket file is missing $ ll /run/user/1000/akonadi/mysql.socket ls: cannot access '/run/user/1000/akonadi/mysql.socket': No such file or directory # Akonadi error log 2020-06-29T21:17:29 [INFO ] org.kde.pim.akonadiserver: Starting up the Akonadi Server... 2020-06-29T21:18:34 [CRITICAL] org.kde.pim.akonadiserver: Failed to connect to database! 2020-06-29T21:18:34 [CRITICAL] org.kde.pim.akonadiserver: Database error: "Can't connect to local MySQL server through socket '/run/user/1000/akonadi/mysql.socket' (2) QMYSQL: Unable to connect" 2020-06-29T21:18:40 [INFO ] org.kde.pim.akonadiserver: Shutting down AkonadiServer.. # MySQL error log 2020-06-29 21:17:29 0 [ERROR] mysqld-akonadi: Can't lock aria control file '/home/maltegerth/.local/share/akonadi/db_data/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds 2020-06-29 21:18:00 0 [ERROR] mysqld-akonadi: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/home/maltegerth/.local/share/akonadi/db_data/aria_log_control' 2020-06-29 21:18:00 0 [ERROR] Plugin 'Aria' init function returned error. 2020-06-29 21:18:00 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. 2020-06-29 21:18:00 0 [Note] InnoDB: Using Linux native AIO 2020-06-29 21:18:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-06-29 21:18:00 0 [Note] InnoDB: Uses event mutexes 2020-06-29 21:18:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-06-29 21:18:00 0 [Note] InnoDB: Number of pools: 1 2020-06-29 21:18:00 0 [Note] InnoDB: Using SSE2 crc32 instructions 2020-06-29 21:18:00 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2020-06-29 21:18:00 0 [Note] InnoDB: Completed initialization of buffer pool 2020-06-29 21:18:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2020-06-29 21:18:00 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 2020-06-29 21:18:00 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2020-06-29 21:18:00 0 [Note] InnoDB: Retrying to lock the first data file 2020-06-29 21:18:01 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 2020-06-29 21:18:01 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2020-06-29 21:18:02 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 421916] New: Events not shown when PARTSTAT=NEEDS-ACTION for current identity
https://bugs.kde.org/show_bug.cgi?id=421916 Bug ID: 421916 Summary: Events not shown when PARTSTAT=NEEDS-ACTION for current identity Product: korganizer Version: 5.13.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@knofafo.de Target Milestone: --- Created attachment 128693 --> https://bugs.kde.org/attachment.cgi?id=128693=edit Example ICS file SUMMARY Bug is related to https://bugs.kde.org/show_bug.cgi?id=352214. For me it is still relevant since this also affects events that I did not create. They have been synced from Office365 in this case through DavMail but the scenario can be reproduced with simple files. STEPS TO REPRODUCE 1. Import the .ics-file from the attachement - go to may 20, 2020: there should be an event labelled "test". 2. Manually change the file and in the section "ATTENDEE"; replace y...@email.org with the email you entered in your kmail profile. OBSERVED RESULT The event disappears. EXPECTED RESULT The event should stay visible SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-31-generic OS Type: 64-bit ADDITIONAL INFORMATION Problem appears with Office365. Event after accepting an invitation this tags stays and an additional entry PARTSTAT=ACCEPTED is added as well. For some calendar apps the latter one probably overwrites the first one. korganizer apparently behaves differently. Since this is quite specific, I would not give it super high priority, but unfortunately the EWS agent is currently also broken (does not store credentials anymore). -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 352214] Event is not displayed in the UI if the invitation list contains the creator's email address with PARTSTAT=NEEDS-ACTION (or maybe anything else than PARTSTAT=ACCEPTED?)
https://bugs.kde.org/show_bug.cgi?id=352214 Jan Bundesmann changed: What|Removed |Added CC||k...@knofafo.de -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414794] kmail crashing in kitinerary when opening a mail
https://bugs.kde.org/show_bug.cgi?id=414794 Jan-Matthias Braun changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REPORTED --- Comment #2 from Jan-Matthias Braun --- It probably was a stupid idea to just set the status to resolved, as kde applications 19.08 are going to be around a bit longer. I am setting this back to reported and leave the decision on the status to people who actually know how and when to do this. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414794] kmail crashing in kitinerary when opening a mail
https://bugs.kde.org/show_bug.cgi?id=414794 Jan-Matthias Braun changed: What|Removed |Added Component|general |mail -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414794] kmail crashing in kitinerary when opening a mail
https://bugs.kde.org/show_bug.cgi?id=414794 Jan-Matthias Braun changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Jan-Matthias Braun --- This seems to be fixed in kde-applications 19.11.90. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414794] New: kmail crashing in kitinerary when opening a mail
https://bugs.kde.org/show_bug.cgi?id=414794 Bug ID: 414794 Summary: kmail crashing in kitinerary when opening a mail Product: kontact Version: 5.12.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jan_br...@gmx.net Target Milestone: --- Application: kontact (5.12.3) Qt Version: 5.14.0 Frameworks Version: 5.64.0 Operating System: Linux 5.4.1 x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: I was opening a mail from the my inbox. I could repeat this several times on the same mail, i.e., there are mails I cannot read. Compiler flags are (this is gentoo after all) "-O2 -fomit-frame-pointer -march=native", so quite standard. The e-mail contains two parts, one is text/html, and the other is a pdf attachment. 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 0x7f5f8b57da40 (LWP 35527))] Thread 71 (Thread 0x7f5eae7fc700 (LWP 50226)): #0 0x7f5f9b05ed2d in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f94e18f66 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x2e3b0450 in () #3 0x000553ec in () #4 0x2e3b1008 in () #5 0x in () Thread 70 (Thread 0x7f5db4b68700 (LWP 36127)): #0 0x7f5f9bfc7a6b in poll () at /lib64/libc.so.6 #1 0x7f5f9a65017e in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5f9a65029f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5f9c60d2eb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f5f9c5b5c1b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5f9c400fde in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f5f9c40202f in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #7 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #8 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 69 (Thread 0x7f5db6ffd700 (LWP 35693)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 68 (Thread 0x7f5db77fe700 (LWP 35692)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 67 (Thread 0x7f5db7fff700 (LWP 35691)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 66 (Thread 0x7f5dccba1700 (LWP 35690)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 65 (Thread 0x7f5dcd3a2700 (LWP 35689)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 64 (Thread 0x7f5dcdba3700 (LWP 35688)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 63 (Thread 0x7f5dce8d6700
[kmail2] [Bug 410099] New: Crash on Logging out
https://bugs.kde.org/show_bug.cgi?id=410099 Bug ID: 410099 Summary: Crash on Logging out Product: kmail2 Version: 5.11.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: hasenh...@gmx.net Target Milestone: --- STEPS TO REPRODUCE 1. Have Kmail2 running in tray 2. Log off Plasma or shut down the pc OBSERVED RESULT A splash screen appears indicating that Kmail2 has crashed EXPECTED RESULT Kmail2 should shut terminate regularly SOFTWARE/OS VERSIONS Kernel Version: 5.2.1-arch1-1-ARCH KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION This might be a duplicate of 378315, but since that one is reported to be resolved by upgrading Qt to a version >= 5.10 I've decided to post this again, since I don't know if this is the same bug Stacktrace: https://pastebin.com/dM0ywSEP -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409767] New: Check mail on startup does not work if akonadi wasn't already running when KMail is started
https://bugs.kde.org/show_bug.cgi?id=409767 Bug ID: 409767 Summary: Check mail on startup does not work if akonadi wasn't already running when KMail is started Product: kmail2 Version: 5.11.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: medhe...@web.de Target Milestone: --- Check for new mail on startup does not work if akonadi wasn't running prior to starting KMail. STEPS TO REPRODUCE 1. Ensure "Check mail on startup" under "Retrieval Options" is checked for account 2. Make sure a different folder from inbox is selected 3. Quit KMail and stop akonadi with "akonadictl stop" 4. Put a new mail in inbox through some other mail client / webmail. 5. Start KMail and observe that no new mail is found in inbox (unless the folder is selected or if KMail starts with it selected) 6. Quit KMail but leave akonadi around 7. Add another new mail 8. Start KMail and observe that the new mail was found -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409224] kmail with >=mariadb-10.4.6: not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 Jan changed: What|Removed |Added CC||medhe...@web.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 Jan changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=386507 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 386507] Caldav and Carddav sync does not work
https://bugs.kde.org/show_bug.cgi?id=386507 Jan changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=380012 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 --- Comment #5 from Jan --- I can reproduce this with mailbox.org with KOrganizer 5.11.2. Neither CardDAV or CalDAV read any items from the server. If I create an item locally it is synced to the server. What information can I provide to resolve this issue? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 Jan changed: What|Removed |Added Version|5.5.1 |5.11.2 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 Jan changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=386985 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Jan changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=380012 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 Jan changed: What|Removed |Added CC||soc...@jan-iversen.de -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 407935] New: Empty UI field when creating new Folder and adding feed to it
https://bugs.kde.org/show_bug.cgi?id=407935 Bug ID: 407935 Summary: Empty UI field when creating new Folder and adding feed to it Product: akregator Version: 5.11.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jan.thomas.118+...@gmail.com Target Milestone: --- Created attachment 120301 --> https://bugs.kde.org/attachment.cgi?id=120301=edit Shows the unvisible UI element SUMMARY Empty UI field when creating new Folder and adding one feed to it STEPS TO REPRODUCE 1. Create new Folder 2. Add a feed to it 3. Open the folder OBSERVED RESULT An empty feed element is shown under the added feed EXPECTED RESULT everything looks as normal Operating System: Manjaro Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 Kernel Version: 5.0.15-1-MANJARO OS Type: 64-bit Processors: 4 × Intel® Core™ i3-4150 CPU @ 3.50GHz Memory: 7,2 GiB of RAM ADDITIONAL INFORMATION Restarting Akregator makes this issue dissapear I have tested this bug on another machine, it was reproducible there aswell. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405010] Don't show a notification badge with a zero when there aren't any notifications
https://bugs.kde.org/show_bug.cgi?id=405010 --- Comment #4 from Jan Przybylak --- Yes -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405010] Don't show a notification badge with a zero when there aren't any notifications
https://bugs.kde.org/show_bug.cgi?id=405010 Jan Przybylak changed: What|Removed |Added Version|unspecified |5.11.1 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405010] Don't show a notification badge with a zero when there aren't any notifications
https://bugs.kde.org/show_bug.cgi?id=405010 --- Comment #2 from Jan Przybylak --- I use 5.11.1. This doesn't always happen, just sometimes. I have not been able to figure out what is causing it exactly, but I'm only using Kmail and Akregator, so it has to be one of them. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 407876] Akregator crashes when closing tab in internal browser
https://bugs.kde.org/show_bug.cgi?id=407876 Jan Thomas changed: What|Removed |Added CC||jan.thomas.118+...@gmail.co ||m -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 407876] Akregator crashes when closing tab in internal browser
https://bugs.kde.org/show_bug.cgi?id=407876 --- Comment #1 from Jan Thomas --- I forgot the Akregator version, and the Bug report doesnt let me specify this version. Pacman reports "19.04.1-1" -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 407876] New: Akregator crashes when closing tab in internal browser
https://bugs.kde.org/show_bug.cgi?id=407876 Bug ID: 407876 Summary: Akregator crashes when closing tab in internal browser Product: akregator Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jan.thomas.118+...@gmail.com Target Milestone: --- SUMMARY Akregator crashes when closing tab in internal browser STEPS TO REPRODUCE 1. Open article in internal browser "open in tab" Examples i used: https://www.kdab.com/little-trouble-in-big-data-part-1/ https://www.sueddeutsche.de/leben/gemeinwohlatlas-2019-1.4456660 https://www.sueddeutsche.de/bayern/regensburg-wolbergs-anwalt-fordert-freispruch-1.4459459 2. click "close tab", "close other tabs" or "close all tabs" OBSERVED RESULT Akregator crashes EXPECTED RESULT Akregator does not crash SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 Kernel Version: 5.0.15-1-MANJARO OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4690K CPU @ 3.50GHz Memory: 11,5 GiB of RAM ADDITIONAL INFORMATION Opening Akregator in the temrinal doesnt lead to any more information other than "core dumped" -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 407688] Clicking link on XKCD page crashes Akregator
https://bugs.kde.org/show_bug.cgi?id=407688 Jan Hasebos changed: What|Removed |Added URL||https://xkcd.com/2067/ Version|unspecified |5.9.2 Platform|Debian stable |Debian unstable Component|general |internal browser -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 407688] New: Clicking link on XKCD page crashes Akregator
https://bugs.kde.org/show_bug.cgi?id=407688 Bug ID: 407688 Summary: Clicking link on XKCD page crashes Akregator Product: akregator Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: j...@hasebos.net Target Milestone: --- Application: akregator (5.9.3) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-5-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: On the page https://xkcd.com/2067/, clicking any link in the infographic crashes Akregator. The crash can be reproduced every time. -- Backtrace: 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 0x7faac7f20f00 (LWP 7528))] Thread 28 (Thread 0x7faa15a70700 (LWP 23306)): #0 futex_reltimed_wait_cancelable (private=0, reltime=0x7faa15a6f400, expected=0, futex_word=0x7faa15a6f5e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7faa15a6f4a0, mutex=0x7faa15a6f598, cond=0x7faa15a6f5c0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7faa15a6f5c0, mutex=0x7faa15a6f598, abstime=0x7faa15a6f4a0) at pthread_cond_wait.c:667 #3 0x7faad8fb4a37 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7faad8fb730a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7faad8fb73f2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7faad8fbb981 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7faad8fbce61 in base::internal::SchedulerWorker::Thread::ThreadMain() () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7faad8fc5c81 in base::(anonymous namespace)::ThreadFunc(void*) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7faad6691fa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7faaddc614cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7fa9faffc700 (LWP 8614)): #0 __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:63 #1 0x7faaddc704e4 in ___fprintf_chk (fp=0x7faaddd258b0 <_IO_stdfile_2_lock>, flag=1, format=0x7faad40fa848 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7faad40e2a5a in event_logv_ () from /lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7faad40e2c34 in event_warn () from /lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7faad40e4588 in ?? () from /lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7faad40da329 in event_base_loop () from /lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7faad8f897cd in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7faad8fa8c8b in base::RunLoop::Run() () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7faad8fca204 in base::Thread::ThreadMain() () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7faad8fc5c81 in base::(anonymous namespace)::ThreadFunc(void*) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7faad6691fa3 in start_thread (arg=) at pthread_create.c:486 #11 0x7faaddc614cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7faa1526f700 (LWP 8189)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x7faa1526e5f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7faa1526e5a8, cond=0x7faa1526e5d0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7faa1526e5d0, mutex=0x7faa1526e5a8) at pthread_cond_wait.c:655 #3 0x7faad8fb4969 in base::ConditionVariable::Wait() () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7faad8fb7318 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7faad8fb73af in base::WaitableEvent::Wait() () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7faad8fbb998 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7faad8fbcc7f in base::internal::SchedulerWorker::Thread::ThreadMain() () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7faad8fc5c81 in base::(anonymous namespace)::ThreadFunc(void*) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7faad6691fa3 in start_thread
[kmail2] [Bug 406072] New: Archiving does not work from unified mailbox
https://bugs.kde.org/show_bug.cgi?id=406072 Bug ID: 406072 Summary: Archiving does not work from unified mailbox Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: jplx...@gmail.com Target Milestone: --- SUMMARY Clicking the archive button when viewing an email inside a unified mailbox (e.g. one that show the inboxes of mulitple accounts) fails without an error message. Archiving an email from a single accounts inbox works perfectly. STEPS TO REPRODUCE 1. Select email in unified mailbox 2. Try to archive it 3. Nothing happens OBSERVED RESULT Nothing EXPECTED RESULT The email is moved to the account's "archive" folder -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405010] New: Don't show a notification badge with a zero when there aren't any notifications
https://bugs.kde.org/show_bug.cgi?id=405010 Bug ID: 405010 Summary: Don't show a notification badge with a zero when there aren't any notifications Product: kontact Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jplx...@gmail.com Target Milestone: --- Created attachment 118493 --> https://bugs.kde.org/attachment.cgi?id=118493=edit Notification badge for zero notifications I think the notification badge on the app icon showing a zero when there aren't any notifications is pretty pointless, it shouldn't be there at all. When seeing this badge, one automatically assumes there are notifications, until realizing there's a zero inside of it, which creates unnecessary stress. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376519] Check Mail on Startup does not work
https://bugs.kde.org/show_bug.cgi?id=376519 Jan changed: What|Removed |Added CC||medhe...@web.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet
https://bugs.kde.org/show_bug.cgi?id=393002 Jan Kriho changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||erbur...@seznam.cz --- Comment #6 from Jan Kriho --- After upgrading to KDE PIM 18.12 I recreated the EWS account, however storing password into KWallet no longer works. -- You are receiving this mail because: You are on the CC list for the bug.
[akregator] [Bug 402132] New: Make it more obvious that the search didn't find anything
https://bugs.kde.org/show_bug.cgi?id=402132 Bug ID: 402132 Summary: Make it more obvious that the search didn't find anything Product: akregator Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: feed parser Assignee: kdepim-bugs@kde.org Reporter: jplx...@gmail.com Target Milestone: --- Created attachment 116923 --> https://bugs.kde.org/attachment.cgi?id=116923=edit When you don't remember using the search box, it's not immediately obvious why no articles are showing SUMMARY Making the search box red (like other apps) or showing a message when nothing was found would be helpful. I just ran into this: I was confused because Akregator wasn't showing any articles and only later realised that this was because I had searched when using it earlier and the query was still there. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 399290] Adding Googlemail accounts: A window with google's login form opens, but is too small
https://bugs.kde.org/show_bug.cgi?id=399290 Jan Przybylak changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 399290] Adding Googlemail accounts: A window with google's login form opens, but is too small
https://bugs.kde.org/show_bug.cgi?id=399290 Jan Przybylak changed: What|Removed |Added Version|unspecified |5.8.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 399290] New: Adding Googlemail accounts: A window with google's login form opens, but is too small
https://bugs.kde.org/show_bug.cgi?id=399290 Bug ID: 399290 Summary: Adding Googlemail accounts: A window with google's login form opens, but is too small Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jplx...@gmail.com Target Milestone: --- Created attachment 115347 --> https://bugs.kde.org/attachment.cgi?id=115347=edit Screenshots of the issue SUMMARY When connecting KMail to a Googlemail account, a window opens that contains Google's own login form. The problem is that this window is not big enough (see attached screenshots). It is not obvious that it has to be resized to be able to access the interface, leading to the assumption that KMail is not compatible with Googlemail. STEPS TO REPRODUCE 1. Add a Googlemail inbox just like you would add any other email account 2. Wait for the first window seen in the screenshots I attached to pop up OBSERVED RESULT Window too small EXPECTED RESULT Bigger window so the reason for its existence is visible SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.4 KDE Frameworks Version: 5.48.0 Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 398036] Password for sending mails not used when specified via password prompt
https://bugs.kde.org/show_bug.cgi?id=398036 --- Comment #7 from Jan Hambrecht --- Many thanks and great work! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 398036] Password for sending mails not used when specified via password prompt
https://bugs.kde.org/show_bug.cgi?id=398036 --- Comment #4 from Jan Hambrecht --- Looking at src/kmailtransport/plugins/smtp/smtpjob.cpp it seems the password from the password dialog is only set to the transport but not to the login job (see line 290). Probably because of the XOAUTH2 handling in line 286. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 398036] Password for sending mails not used when specified via password prompt
https://bugs.kde.org/show_bug.cgi?id=398036 --- Comment #2 from Jan Hambrecht --- Yes it is probably sensible to disable the lineedit in the settings dialog if the store password option is unchecked. In any case if kmail asks the user for a password via the password prompt popping up before sending, it should be used for authentication on the mail server. Otherwise there is no point asking the user for a password, isn't it? This used to work in older versions and just stopped working in the last kmail version. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 398036] New: Password for sending mails not used when specified via password prompt
https://bugs.kde.org/show_bug.cgi?id=398036 Bug ID: 398036 Summary: Password for sending mails not used when specified via password prompt Product: kmail2 Version: 5.9.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ja...@gmx.net Target Milestone: --- When the smtp password is not saved in the smtp settings dialog kmail prompts for a password just before sending a mail. When debugging the ksmtp component I discovered that an empty password is sent to the server. When I set the smtp password to be stored in the settings dialog, the password is sent correctly to the server and sending mails works again. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 279115] Standard Mailing list doesn't thread properly
https://bugs.kde.org/show_bug.cgi?id=279115 --- Comment #11 from Jan --- I figured out why this is happening: KMail only considers prefixed E-Mails for subject based threading. If it doesn't start with a "Re:" for example, it's not a thread. Bugzilla doesn't do that. So in the absence of that, it only uses In-Reply-To/Reference headers. And that doesn't work if the thread starter is missing, which imho is the wrong way to handle that. And even if it is prefixed, it will not consider messages with a time difference of 120 seconds. So if you managed to have a github conversation that is faster than that, it's not a thread either. This one in particular I really don't understand. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 279115] Standard Mailing list doesn't thread properly
https://bugs.kde.org/show_bug.cgi?id=279115 Jan changed: What|Removed |Added CC||medhe...@web.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 389369] Can't Authenticate to Office 365
https://bugs.kde.org/show_bug.cgi?id=389369 Jan Kriho <erbur...@seznam.cz> changed: What|Removed |Added CC||erbur...@seznam.cz -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 Jan <soc...@jan-iversen.de> changed: What|Removed |Added CC||soc...@jan-iversen.de --- Comment #76 from Jan <soc...@jan-iversen.de> --- Can confirm this with Manjaro and openSuSe Tumbleweed. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386469] Akonadi resp. Korganizer and Kaddressbook only sync one way
https://bugs.kde.org/show_bug.cgi?id=386469 Jan <soc...@jan-iversen.de> changed: What|Removed |Added CC||soc...@jan-iversen.de --- Comment #2 from Jan <soc...@jan-iversen.de> --- I can confirm this bug on the latest openSuSe Tumbleweed and Manjaro-version. On both distributions the sync works only from kontact to mailbox.org. Entries are not read from the server. Please fix this. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Jan Wiele <j...@wiele.org> changed: What|Removed |Added CC||j...@wiele.org -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #2 from Jan-Matthias Braun <jan_br...@gmx.net> --- For another account using SMTP, I am seeing another error in the notification widget. Instead of getting a "1", as for the original report, I am seeing "Serverfehler", the German translation of Server error, in the notification window, but unluckily no debug output in the terminal. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #1 from Jan-Matthias Braun <jan_br...@gmx.net> --- Further tests with another account revealed, that sending via the EWS resource works. So does sending via a local mail dispatcher, like ssmtp or nullmailer. Although akonadi/kmail2 seems to run into problems with sendmail compatibility issues of those. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added Severity|normal |grave -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] New: Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Bug ID: 387926 Summary: Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1 Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Mail Dispatcher Agent Assignee: kdepim-bugs@kde.org Reporter: jan_br...@gmx.net Target Milestone: --- When trying to send an e-Mail since trying out the 17.12 pre-releases, I am unable to send e-Mails. In the official release, I have now recreated the SMTP but the problem persists, no mail gets out. The only debug message I am seeing after enabling diverse output in kdebugdialog5 is org.kde.pim.ksmtp: Socket error: 1 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 379131] Gmail authentication expires after some time
https://bugs.kde.org/show_bug.cgi?id=379131 Jan Grulich <jgrul...@redhat.com> changed: What|Removed |Added Ever confirmed|0 |1 CC||jgrul...@redhat.com Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 386423] New: color on link defined by inline style is not applied
https://bugs.kde.org/show_bug.cgi?id=386423 Bug ID: 386423 Summary: color on link defined by inline style is not applied Product: kmail2 Version: 5.2.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@piskvor.org Target Milestone: --- Created attachment 108663 --> https://bugs.kde.org/attachment.cgi?id=108663=edit button "Přejít na Aktuálně" unreadable An A element with an explicitly styled color, inside a TABLE with and explicitly styled background-color, still gets the default link-color, thus becoming unreadable. What should happen: 1. open e-mail in HTML view 2. see table with blue background and white text What happens instead: 2. see table with blue background and blue text (see attachment) Below is one of the tables in question: https://aktualne.us8.list-manage.com/track/click?u=5ec4c91d59d1b26aefb919e61id=0bf30eab98e=5c55646d3f; target="_blank" style="font-weight: 500;letter-spacing: .5px;line-height: 100%;text-align: center;text-decoration: none;color: #fff;mso-line-height-rule: exactly;-ms-text-size-adjust: 100%;-webkit-text-size-adjust: 100%;display: block;"> link text which blends into the background color -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 364670] kmail crash on search
https://bugs.kde.org/show_bug.cgi?id=364670
--- Comment #8 from Jan-Matthias Braun <jan_br...@gmx.net> ---
Created attachment 106677
--> https://bugs.kde.org/attachment.cgi?id=106677=edit
New crash information added by DrKonqi
kontact (5.5.3) using Qt 5.7.1
I was entering a search term in a mail folder. I am unsure if I have pressed
the enter button, but in general the procedure seems like the one layed out
above.
Distribution: Gentoo with standard buld flags ("-O2 -march=native").
-- Backtrace (Reduced):
#8 0x7f7fdef72cad in __gnu_cxx::__verbose_terminate_handler () at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/vterminate.cc:95
#9 0x7f7fdef70a16 in __cxxabiv1::__terminate (handler=) at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/eh_terminate.cc:47
#10 0x7f7fdef70a61 in std::terminate () at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/eh_terminate.cc:57
#11 0x7f7fdef70c79 in __cxxabiv1::__cxa_throw (obj=obj@entry=0x54eae90,
tinfo=0x7f7fdf0b2890 , dest=0x7f7fdef86cb0
<std::logic_error::~logic_error()>) at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/eh_throw.cc:87
#12 0x7f7fdef9b73f in std::__throw_logic_error (__s=0x7f7ed88afd28
"basic_string::_M_construct null not valid") at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/src/c++11/functexcept.cc:74
--
You are receiving this mail because:
You are the assignee for the bug.
[kontact] [Bug 364670] kmail crash on search
https://bugs.kde.org/show_bug.cgi?id=364670 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 366487] Add Support for Media RSS/Atom Feeds (mrss)
https://bugs.kde.org/show_bug.cgi?id=366487 Jan Molnar <jan.mol...@gmail.com> changed: What|Removed |Added CC||jan.mol...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367998] quick-search field does not receive some keys
https://bugs.kde.org/show_bug.cgi?id=367998 --- Comment #4 from Jan-Matthias Braun <jan_br...@gmx.net> --- (In reply to Jan-Matthias Braun from comment #3) > 2. Whenever I enter text into the search field, right after updating the > message list, the focus seems to go to the mail view, too. Of course, any > keystrokes won't go to the search field anymore. This is similar to the > original problem here and can be reproduced reliably without any folder > change. When there is no mail displayed in the message view, e.g., one of akonadi's i-m-not-serving-any-requests-periods, then the focus won't leave the search field. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case
https://bugs.kde.org/show_bug.cgi?id=222878 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #37 from Jan-Matthias Braun <jan_br...@gmx.net> --- And another (rather short) one for kontact 16.12.0 (gdb) bt #0 0x7f15af07199d in poll () from /lib64/libc.so.6 #1 0x7f15a8041266 in g_main_context_iterate.isra.42.lto_priv () from /usr/lib64/libglib-2.0.so.0 #2 0x7f15a7fc8a3c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f15acd8e7af in QEventDispatcherGlib::processEvents (this=0x1236fd0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f15acd3a7ba in QEventLoop::exec (this=this@entry=0x7fffa171af30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f15acd42bfd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261 #6 0x00404203 in main (argc=, argv=) at /var/tmp/portage/kde-apps/kontact-16.12.0/work/kontact-16.12.0/src/main.cpp:227 Cheers, Jan -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367998] quick-search field does not receive some keys
https://bugs.kde.org/show_bug.cgi?id=367998 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi! I am not sure, if this really is the same problem, but as I see it, I do see a general problem with the focus strategy. :-) 1. Whenever I select an e-Mail, the mail view is focused. This means, that actions like delete don't work anymore. Only when I select an e-Mail a second time, things are back to normal and the focus stays in the message list. 2. Whenever I enter text into the search field, right after updating the message list, the focus seems to go to the mail view, too. Of course, any keystrokes won't go to the search field anymore. This is similar to the original problem here and can be reproduced reliably without any folder change. The description of where the focus goes has been derived from ticking shift-tab until I was back at the search field. Assuming "Search Field" - "Message List" - "Message View" tab order. I.e., I went back and forth to see where the focus has ended up. My kde installation is up to date. I.e., kmail 16.12.0, plasma 5.8.5, and frameworks 5.29. The patch noted in Comment 1 is already applied, as far as I can see. I am not sure, when this started. Probably with the qtwebengine version? Does the mail view now focus itself? I really like kmail, so thanks for looking into this! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #6 from Jan-Matthias Braun <jan_br...@gmx.net> --- (In reply to Jan-Matthias Braun from comment #5) > Update: I recompiled with "-fno-delete-null-pointer-checks -fno-lifetime-dse > -fno-schedule-insns2", but the crash still happens. Yeah, looks like I did not rccompile with these CFLAGS. Now I did and it looks quite a lot better. qtwebengine is still using wrong CFLAGS for gcc 6. :-( -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #5 from Jan-Matthias Braun <jan_br...@gmx.net> --- Update: I recompiled with "-fno-delete-null-pointer-checks -fno-lifetime-dse -fno-schedule-insns2", but the crash still happens. Then I took a look at kdepim git and found at, that there is a KF5WebEngineViewerConfig in the works. So it looks like everything will change in git, right? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #4 from Jan-Matthias Braun <jan_br...@gmx.net> --- In a side-note, the secondary crash happens when grabbing selected text: #0 0x7fffeedae224 in QtWebEngineCore::WebContentsAdapter::selectedText() const () from /usr/lib64/libQt5WebEngineCore.so.5 #1 0x760eb321 in QWebEnginePage::selectedText() const () from /usr/lib64/libQt5WebEngineWidgets.so.5 #2 0x760f8547 in QWebEngineView::selectedText() const () from /usr/lib64/libQt5WebEngineWidgets.so.5 #3 0x7fff027e5991 in MessageViewer::Viewer::selectedText() const (this=) at /var/tmp/portage/kde-apps/messagelib-16.08.2/work/messagelib-16.08.2/messageviewer/src/viewer/viewer.cpp:248 #4 0x7fff02e78600 in KMReaderWin::copyText() const (this=) at /var/tmp/portage/kde-apps/kmail-16.08.2/work/kdepim-16.08.2/kmail/src/kmreaderwin.cpp:399 #5 0x7fff02ed0508 in KMail::MessageActions::replyCommand (this=0x3bd4fc0, strategy=MessageComposer::ReplySmart) at /var/tmp/portage/kde-apps/kmail-16.08.2/work/kdepim-16.08.2/kmail/src/messageactions.cpp:477 #6 0x76ef3d1c in QtPrivate::QSlotObjectBase::call (a=0x7fffc930, r=0x3bd4fc0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:130 #7 QMetaObject::activate (sender=0x3bd0160, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3723 #8 0x77a4dea2 in QAction::triggered(bool) () from /usr/lib64/libQt5Widgets.so.5 #9 0x77a539ff in QAction::activate(QAction::ActionEvent) () from /usr/lib64/libQt5Widgets.so.5 #10 0x77a53aec in QAction::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #11 0x77a5c32c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #12 0x77a61739 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x76ec8f18 in QCoreApplication::notifyInternal2 (receiver=0x3bd0160, event=event@entry=0x7fffcc00) at kernel/qcoreapplication.cpp:988 #14 0x7723ef96 in QCoreApplication::sendEvent (event=0x7fffcc00, receiver=) at /usr/include/qt5/QtCore/qcoreapplication.h:231 #15 QShortcutMap::dispatchEvent (this=this@entry=0x449968, e=e@entry=0x7fffccb0) at kernel/qshortcutmap.cpp:674 #16 0x7723f069 in QShortcutMap::tryShortcut (this=this@entry=0x449968, e=e@entry=0x7fffccb0) at kernel/qshortcutmap.cpp:351 #17 0x771fad5f in QWindowSystemInterface::handleShortcutEvent (window=, window@entry=0xca8120, timestamp=, keyCode=82, modifiers=..., nativeScanCode=27, nativeVirtualKey=114, nativeModifiers=0, text=..., autorepeat=false, count=1) at kernel/qwindowsysteminterface.cpp:235 #18 0x77210fcc in QGuiApplicationPrivate::processKeyEvent (e=0x419f800) at kernel/qguiapplication.cpp:2008 #19 0x77216285 in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x419f800) at kernel/qguiapplication.cpp:1699 #20 0x771f596b in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:654 #21 0x7fffe7a26900 in userEventSourceDispatch (source=) at eventdispatchers/qeventdispatcher_glib.cpp:76 #22 0x74a6bd17 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #23 0x74a6c788 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #24 0x74a6c91c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #25 0x76f1aeef in QEventDispatcherGlib::processEvents (this=0x4bb6d0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #26 0x76ec704a in QEventLoop::exec (this=this@entry=0x7fffd010, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #27 0x76ecf48d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261 #28 0x004042c3 iat /var/tmp/portage/kde-apps/kontact-16.08.2/work/kdepim-16.08.2/kontact/src/main.cpp:223 n main (argc=, argv=) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- Looking at the stack trace again, I just remembered that v8 has problems with gcc 6 due to programming practices. I am recompiling qtwebengine with appropriate compiler flags to check if this is the underlying problem here... -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #2 from Jan-Matthias Braun <jan_br...@gmx.net> --- Sorry for being incoherent: I am using qt 5.7.0, plasma 5.8.3, kde apps 16.08.2, and frameworks 5.27. The compiler is gcc 6.2.0. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #1 from Jan-Matthias Braun <jan_br...@gmx.net> --- Side note: For all messages I see this error message in the logs: js: Uncaught ReferenceError: qt is not defined js: Uncaught ReferenceError: qt is not defined js: Uncaught ReferenceError: qt is not defined but it does not seem to interrupt kmail. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] New: kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 Bug ID: 372022 Summary: kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2. Product: kmail2 Version: 5.3.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: jan_br...@gmx.net Target Milestone: --- When selecting a mail in message view, the message is displayed and then disappears after a variable delay. Changing to another mail and then back does not triggering this behaviour. The disappearing message happens in the embedded message view as well as in an extra window (after double clicking the message). If the mail display is blank and I trigger any message related, e.g., reply, forward, delete, kmail crashes. But if I redisplay the message and do the same action while the display is intact, everything will work fine. Nonetheless, this mail focuses on the disappearing of the displayed mail. I see the following backtrace, which seems to lead into the depths of QtWebEngine. Received signal 11 SEGV_MAPERR 0008 #0 0x74cb3b3e base::debug::StackTrace::StackTrace() #1 0x74cb3c2b base::debug::(anonymous namespace)::StackDumpSignalHandler() #2 0x722cc2b0 #3 0x733785b0 v8::internal::IncrementalMarking::ActivateIncrementalWriteBarrier() #4 0x733787e7 v8::internal::IncrementalMarking::StartMarking() #5 0x73378943 v8::internal::IncrementalMarking::Start() #6 0x7368ac9f v8::internal::MemoryReducer::TimerTask::RunInternal() #7 0x74d46869 base::debug::TaskAnnotator::RunTask() #8 0x7541b323 scheduler::TaskQueueManager::ProcessTaskFromWorkQueue() #9 0x7541bda0 scheduler::TaskQueueManager::DoWork() #10 0x74d46869 base::debug::TaskAnnotator::RunTask() #11 0x74cd79d5 base::MessageLoop::RunTask() #12 0x74cd99ab base::MessageLoop::DoDelayedWork() #13 0x74cdaaaf base::MessagePumpDefault::Run() #14 0x74cefffd base::RunLoop::Run() #15 0x74cd6f65 base::MessageLoop::Run() #16 0x74a07baf content::RendererMain() #17 0x73dc4cdb content::RunZygote() #18 0x73dc5034 content::ContentMainRunnerImpl::Run() #19 0x73dc34e1 content::ContentMain() #20 0x7311d514 QtWebEngine::processMain() #21 0x00400703 main #22 0x722b9681 __libc_start_main #23 0x00400749 _start What additional information can I provide? Jan -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 371859] Segfault of kmail when removing a mail
https://bugs.kde.org/show_bug.cgi?id=371859 --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- (In reply to Michael.Calmer from comment #2) > (In reply to Jan-Matthias Braun from comment #1) > > I do have a question. I am experiencing problems with current QtWebEngine > > based kmail too: Sometimes, the mail display will become empty after a short > > delay. Changing to another mail and then back has a slight chance of not > > triggering this behaviour. If the mail display is blank and I trigger any > > message related, e.g., reply, forward, delete, kmail crashes. > > My crash happens not only while removing a mail. action, I wanted to write: any nessage releted action. ^^ > > But if I redisplay the message and do the same action while the display is > > intact, everything will work fine. > > Well, I cannot make the message visible. "redisplay" is not really working > for me. So you never see the message? I can at least see it shortly before it vanishes... > > Do you observe similar behaviour? Or should I file a new bug. > > Sounds a bit similar to what I see. > > > My backtrace hints to QtWebEngine. But unfortunately, I am using > > self-compiled qt 5.7 and the debug build for QtWebEngine is exhausting my > > disk space, i.e., my backtrace is worthless. > > I also saw other bugreports which point to this component together with the > use of the "nouveau" driver. I am using an up-to-date proprietary nvidia driver. I will try to get some useful debug information. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 371859] Segfault of kmail when removing a mail
https://bugs.kde.org/show_bug.cgi?id=371859 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #1 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi Michael, I do have a question. I am experiencing problems with current QtWebEngine based kmail too: Sometimes, the mail display will become empty after a short delay. Changing to another mail and then back has a slight chance of not triggering this behaviour. If the mail display is blank and I trigger any message related, e.g., reply, forward, delete, kmail crashes. But if I redisplay the message and do the same action while the display is intact, everything will work fine. Do you observe similar behaviour? Or should I file a new bug. My backtrace hints to QtWebEngine. But unfortunately, I am using self-compiled qt 5.7 and the debug build for QtWebEngine is exhausting my disk space, i.e., my backtrace is worthless. Cheers, Jan -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 371533] Kmail crash on close (kvantum)
https://bugs.kde.org/show_bug.cgi?id=371533 jan neumann <neum...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from jan neumann <neum...@gmail.com> --- deactivating translucence for kmail in kvantum manager solved the crash. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 371533] New: Kmail crash on close (kvantum)
https://bugs.kde.org/show_bug.cgi?id=371533 Bug ID: 371533 Summary: Kmail crash on close (kvantum) Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: neum...@gmail.com Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.4-1-ck x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: closed KMail - Custom settings of the application: Use plasma with arc-dark and kvantum theme engine. This error only occours if i use kvantum The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd3dcdce580 (LWP 28964))] Thread 3 (Thread 0x7fd379fbe700 (LWP 29006)): #0 0x7fd3cf84c10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd3c564ec35 in () at /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fd3c564ed05 in () at /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fd3c562fd03 in () at /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fd3c5641f54 in () at /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fd3c562bee5 in () at /usr/lib/libQt5WebEngineCore.so.5 #6 0x7fd3c565ad6a in () at /usr/lib/libQt5WebEngineCore.so.5 #7 0x7fd3c56570dc in () at /usr/lib/libQt5WebEngineCore.so.5 #8 0x7fd3cf846454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fd3d9c6f7df in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fd39ddee700 (LWP 28989)): #0 0x7fd3d9c6648d in poll () at /usr/lib/libc.so.6 #1 0x7fd3cdca1786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd3cdca189c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fd3da7a272b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd3da74c23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fd3da56f0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fd3d8b84e55 in () at /usr/lib/libQt5DBus.so.5 #7 0x7fd3da573d78 in () at /usr/lib/libQt5Core.so.5 #8 0x7fd3cf846454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fd3d9c6f7df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fd3dcdce580 (LWP 28964)): [KCrash Handler] #6 0x7fd3daca79c2 in QWindow::destroy() () at /usr/lib/libQt5Gui.so.5 #7 0x7fd3db46a0f7 in QWidgetPrivate::deleteTLSysExtra() () at /usr/lib/libQt5Widgets.so.5 #8 0x7fd3db46efb0 in QWidget::destroy(bool, bool) () at /usr/lib/libQt5Widgets.so.5 #9 0x7fd3db4758b7 in QWidget::~QWidget() () at /usr/lib/libQt5Widgets.so.5 #10 0x7fd3db565379 in QLabel::~QLabel() () at /usr/lib/libQt5Widgets.so.5 #11 0x7fd3d08fa545 in () at /usr/lib/libQt5WebEngineWidgets.so.5 #12 0x7fd3d08fa579 in () at /usr/lib/libQt5WebEngineWidgets.so.5 #13 0x7fd3d9bbc990 in __run_exit_handlers () at /usr/lib/libc.so.6 #14 0x7fd3d9bbc9ea in () at /usr/lib/libc.so.6 #15 0x7fd3d9ba7298 in __libc_start_main () at /usr/lib/libc.so.6 #16 0x0040403a in _start () Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 369500] Links in Feed are not opened in external browser anymore
https://bugs.kde.org/show_bug.cgi?id=369500 Jan Sommer <summers...@web.de> changed: What|Removed |Added CC||summers...@web.de -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 369500] New: Links in Feed are not opened in external browser anymore
https://bugs.kde.org/show_bug.cgi?id=369500 Bug ID: 369500 Summary: Links in Feed are not opened in external browser anymore Product: akregator Version: 5.3.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-bugs@kde.org Reporter: summers...@web.de In the Settings->Browser I have configured to open links in an external browser. However, if I follow a link in an article instead it opens a new Akregator window where the link is opened. This only happens with the links in the article itself. If I click on the "Complete Story"-Link at the end of the article, it is correctly opened in my browser. The same happens if I set the option to "Open in Tab". "Complete Story" opens a new tab inside Akregator. A normal link in the article opens an extra window of the internal browser. Reproducible: Always Steps to Reproduce: 1. Set the browser settings to external browser 2. Click a link in an article 3. Actual Results: The link is opened in a new Akregator-Window (the internal browser, I guess) Expected Results: The link should be opened in the external browser -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368748] New: KMail crashes when changing destination folder in antispam wizard
https://bugs.kde.org/show_bug.cgi?id=368748 Bug ID: 368748 Summary: KMail crashes when changing destination folder in antispam wizard 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: czd...@gmail.com Application: kontact (5.2.3) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: * Started antispam wizard * Selected: SpamAssasin 3.x (Daemon) -- but it's same result for Perl SpamAssasin * On next page I checked both checkboxes and opened dialog for change spam destination folder * Selected new folder and KMail crashed 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 0x7f12b64cd7c0 (LWP 7813))] Thread 26 (Thread 0x7f11d73ed700 (LWP 15010)): #0 0x7f12b3185bfd in poll () at /lib64/libc.so.6 #1 0x7f12aa7d3e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f12aa7d3f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f12b3ca1f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f12b3c518cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f12b3a9806a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f12b3a9c899 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f12ac4ea0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f12b318e02d in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f11f4ff9700 (LWP 8217)): #0 0x7f12b3181ccd in read () at /lib64/libc.so.6 #1 0x7f12aa814b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f12aa7d3999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f12aa7d3df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f12aa7d3f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f12b3ca1f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f12b3c518cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f12b3a9806a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f12b3a9c899 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f12ac4ea0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f12b318e02d in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f11f57fa700 (LWP 8213)): #0 0x7f12aa7d3443 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f12aa7d3d80 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f12aa7d3f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f12b3ca1f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f12b3c518cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f12b3a9806a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f12b3a9c899 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f12ac4ea0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f12b318e02d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f11f5ffb700 (LWP 8177)): #0 0x7f12aa815cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f12aa7d34b9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f12aa7d3d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f12aa7d3f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f12b3ca1f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f12b3c518cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f12b3a9806a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f12b3a9c899 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f12ac4ea0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f12b318e02d in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f11f67fc700 (LWP 8175)): #0 0x7f12aa815d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f12aa7d3538 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f12aa7d3d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f12aa7d3f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f12b3ca1f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f12b3c518cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f12b3a9806a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f12b3a9c899 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f12ac4ea0a4 in start_thread () at
[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #13 from Jan-Matthias Braun <jan_br...@gmx.net> --- it looks like my problem is somehow related to akonadi/kmail producing and not coping with invalid xapian searches. Right now, I have not seen another akonadi crash. The search that was crashing akonadi had a debug output representation (using the qdebug overload of operator << on term()) over half a screen, i.e., many lines with many many columns. I have no Idea where it came from -- and now it is gone. -- 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 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #12 from Jan-Matthias Braun <jan_br...@gmx.net> --- Okay, I was able to remove a very reproducible crash (with the above mentioned segfault) during startup of akonadi (without any client running) by removing a search from the search folder in kmail. Since then, it is running for at least eight minutes (!) now and I haven't seen a SEGV up to now. By the way, is it normal, that different searches have the same name? In the logs I am seeing the Executing search "foo-1186278907-bar" lines. And the crashing search had the same name, as the search running before, which was much, much simpler. And checking now I see, that different searches often have the same search name in the logs, although from time to time the name seems to change. Revisiting older logs, the crash always happend with a reused search-name. But I cannot tell if it was the same search, always, because only now I went to instrument the code around the backtrace end in the akonadi-search code (xapian/xapiansearchstore.cpp:177) with lots of output. -- 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 363741] akonadi server 16.04.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #11 from Jan-Matthias Braun <jan_br...@gmx.net> --- I do see the same backtrace for xapian 1.3.7. -- 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 363741] akonadi server 16.04.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #10 from Jan-Matthias Braun <jan_br...@gmx.net> --- Ok, I have seen this one three times in a row, now, -- 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 363741] akonadi server 16.04.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #9 from Jan-Matthias Braun <jan_br...@gmx.net> --- Connecting into the running process indeed provides a better backtrace, although -- why? :-) Here it is: #0 0x in ?? () #1 0x7f6ef42d333b in ExternalPostList::ExternalPostList (this=0x7f6f0835a170, db=..., source_=, factor_=, matcher=0x7f6f137fcd30) at matcher/externalpostlist.cc:40 #2 0x7f6ef41e6d6b in Xapian::Internal::QueryPostingSource::postlist (this=, qopt=0x7f6f137fc650, factor=1) at api/queryinternal.cc:739 #3 0x7f6ef41e50a1 in Xapian::Query::Internal::postlist_sub_xor (this=, ctx=..., qopt=, factor=) at api/queryinternal.cc:634 #4 0x7f6ef41e6553 in Xapian::Internal::QueryBranch::do_or_like (this=this@entry=0x7f6f0807b490, ctx=..., qopt=qopt@entry=0x7f6f137fc650, factor=factor@entry=1, elite_set_size=elite_set_size@entry=0, first=first@entry=1) at api/queryinternal.cc:1186 #5 0x7f6ef41e6b1a in Xapian::Internal::QueryAndMaybe::postlist (this=0x7f6f0807b490, qopt=0x7f6f137fc650, factor=1) at api/queryinternal.cc:1550 #6 0x7f6ef42d35fa in LocalSubMatch::get_postlist (this=0x7f6f0807af50, matcher=0x7f6f137fcd30, total_subqs_ptr=0x7f6f137fc7bc) at matcher/localsubmatch.cc:204 #7 0x7f6ef42d9a51 in MultiMatch::get_mset (this=this@entry=0x7f6f137fcd30, first=first@entry=0, maxitems=10, check_at_least=check_at_least@entry=10, mset=..., stats=..., mdecider=0x0, sorter=0x0) at matcher/multimatch.cc:419 #8 0x7f6ef41d55e1 in Xapian::Enquire::Internal::get_mset (this=0x7f6f0807ad10, first=, maxitems=, check_at_least=, check_at_least@entry=0, rset=rset@entry=0x0, mdecider=0x0) at api/omenquire.cc:548 #9 0x7f6ef41d5924 in Xapian::Enquire::get_mset (this=this@entry=0x7f6f137fd050, first=, maxitems=, check_at_least=check_at_least@entry=0, rset=rset@entry=0x0, mdecider=0x0) at api/omenquire.cc:906 #10 0x7f6ee05e968d in Akonadi::Search::XapianSearchStore::exec (this=0x7f6ef009bf50, query=...) at /var/tmp/portage/kde-apps/akonadi-search-16.04.49./work/akonadi-search-16.04.49./xapian/xapiansearchstore.cpp:177 #11 0x7f6f12df8065 in Akonadi::Search::Query::exec (this=this@entry=0x7f6f137fd2c0) at /var/tmp/portage/kde-apps/akonadi-search-16.04.49./work/akonadi-search-16.04.49./core/query.cpp:252 #12 0x7f6f180fff7d in SearchPlugin::search (this=, akonadiQuery=..., collections=..., mimeTypes=...) at /var/tmp/portage/kde-apps/akonadi-search-16.04.49./work/akonadi-search-16.04.49./akonadiplugin/searchplugin.cpp:348 #13 0x0055b4eb in Akonadi::Server::SearchRequest::searchPlugins (this=this@entry=0x7f6f137fd900) at /var/tmp/portage/kde-apps/akonadi-16.04.49./work/akonadi-16.04.49./src/server/search/searchrequest.cpp:112 #14 0x0055b893 in Akonadi::Server::SearchRequest::exec (this=this@entry=0x7f6f137fd900) at /var/tmp/portage/kde-apps/akonadi-16.04.49./work/akonadi-16.04.49./src/server/search/searchrequest.cpp:123 #15 0x00444788 in Akonadi::Server::SearchManager::updateSearchImpl (this=0x27003f0, collection=..., cond=) at /var/tmp/portage/kde-apps/akonadi-16.04.49./work/akonadi-16.04.49./src/server/search/searchmanager.cpp:350 #16 0x7f6f1f8deaa9 in QObject::event (this=0x27003f0, e=) at kernel/qobject.cpp:1263 #17 0x7f6f1f8b2b5b in doNotify (event=0x7f6f08031ea0, receiver=0x27003f0) at kernel/qcoreapplication.cpp:1063 #18 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1049 #19 QCoreApplication::notifyInternal2 (receiver=0x27003f0, event=event@entry=0x7f6f08031ea0) at kernel/qcoreapplication.cpp:988 #20 0x7f6f1f8b526b in QCoreApplication::sendEvent (event=0x7f6f08031ea0, receiver=) at kernel/qcoreapplication.h:231 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x2700600) at kernel/qcoreapplication.cpp:1649 #22 0x7f6f1f8b56d8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1503 #23 0x7f6f1f9063f3 in postEventSourceDispatch (s=0x7f6f080012d0) at kernel/qeventdispatcher_glib.cpp:276 #24 0x7f6f1dd2eb17 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #25 0x7f6f1dd2f4f8 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #26 0x7f6f1dd2f68c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #27 0x7f6f1f9067ff in QEventDispatcherGlib::processEvents (this=0x7f6f080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f6f1f8b0b1a in QEventLoop::exec (this=this@entry=0x7f6f137fde80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #29 0x7f6f1f6d2214 in QThread::exec (this=) at thread/qthread.cpp:507 #30 0x7f6f1f6d6e78 in QThreadPrivate::start (arg=0x27004c0) at thread/qthread_unix.cpp:344 #31 0x7f6f1e
[Akonadi] [Bug 363741] akonadi server 16.04.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #8 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi! I am seeing similar behaviour since 16.04.x, and checked up to 16.04.2 and 16.04-git. I am using qt 5.7, xapian 1.4, frameworks 5.23, and mariadb 10.1.14 on gentoo, too. One of my backtraces looks like this and is only partially usable: 0: akonadiserver() [0x4ac960] 1: akonadiserver() [0x4acc5f] 2: /lib64/libc.so.6(+0x33250) [0x7f025e5b3250] 3: /usr/lib64/libxapian.so.30(+0x1b2508) [0x7f0248531508] 4: /usr/lib64/libxapian.so.30(+0x7554b) [0x7f02483f454b] 5: /usr/lib64/libxapian.so.30(_ZNK6Xapian5Query8Internal20postlist_sub_or_likeERNS_8Internal9OrContextEP14QueryOptimiserd+0x21) [0x7f02483f1e21] 6: /usr/lib64/libxapian.so.30(+0x745a3) [0x7f02483f35a3] 7: /usr/lib64/libxapian.so.30(+0x74e1a) [0x7f02483f3e1a] 8: /usr/lib64/libxapian.so.30(+0x1b266a) [0x7f024853166a] 9: /usr/lib64/libxapian.so.30(+0x1c2991) [0x7f0248541991] 10: /usr/lib64/libxapian.so.30(_ZNK6Xapian7Enquire8Internal8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE+0x1c1) [0x7f02483dd8f1] 11: /usr/lib64/libxapian.so.30(_ZNK6Xapian7Enquire8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE+0x24) [0x7f02483ddc34] 12: /usr/lib64/libKF5AkonadiSearchXapian.so.5(_ZN7Akonadi6Search17XapianSearchStore4execERKNS0_5QueryE+0x8b6) [0x7f02481725d6] 13: /usr/lib64/libKF5AkonadiSearchCore.so.5(_ZN7Akonadi6Search5Query4execEv+0x245) [0x7f0258235a55] 14: /usr/lib64/qt5/plugins/akonadi/akonadi_search_plugin.so(+0x400c) [0x7f025844000c] 15: akonadiserver() [0x4cba6f] 16: akonadiserver() [0x44aaa8] 17: akonadiserver() [0x4835d0] 18: /usr/lib64/libQt5Core.so.5(_ZN7QObject5eventEP6QEvent+0xe9) [0x7f025e085aa9] 19: /usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0xfb) [0x7f025e059b5b] 20: /usr/lib64/libQt5Core.so.5(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x2db) [0x7f025e05c26b] 21: /usr/lib64/libQt5Core.so.5(+0x2de3f3) [0x7f025e0ad3f3] 22: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x297) [0x7f025c86eb17] 23: /usr/lib64/libglib-2.0.so.0(+0x294f8) [0x7f025c86f4f8] 24: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f025c86f68c] 25: /usr/lib64/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5f) [0x7f025e0ad7ff] 26: /usr/lib64/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xfa) [0x7f025e057b1a] 27: /usr/lib64/libQt5Core.so.5(_ZN7QThread4execEv+0xb4) [0x7f025de79214] 28: /usr/lib64/libQt5Core.so.5(+0xaee78) [0x7f025de7de78] 29: /lib64/libpthread.so.0(+0x7434) [0x7f025d99c434] 30: /lib64/libc.so.6(clone+0x6d) [0x7f025e667ded] Now I have installed all debug symbols, but now I can only see mini-backtraces with even less information: 0: akonadiserver() [0x572666] 1: akonadiserver() [0x572982] 2: /lib64/libc.so.6(+0x33250) [0x7fa0e1fe9250] which leaves me at a loss for useful info. (I am not even getting dr konqi, I have to grab the debug info from the akonadi logs.) I am using a bunch of imap-servers including one akonadi-ews account. I have contacts and calendars in owncloud. These seem to get disabled all the while. What can I do to improve debugging information? Cheers, Jan -- 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 131710] Kmail does not remember sender identity in folders for IMAP accounts
https://bugs.kde.org/show_bug.cgi?id=131710 --- Comment #22 from Jan Binder <wh...@herr-der-mails.de> --- Still here in KMail 5.1.1. -- 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 361485] New: crash on initial start with mysql 5.7 on ubuntu 16.04
https://bugs.kde.org/show_bug.cgi?id=361485
Bug ID: 361485
Summary: crash on initial start with mysql 5.7 on ubuntu 16.04
Product: Akonadi
Version: unspecified
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: grave
Priority: NOR
Component: server
Assignee: kdepim-bugs@kde.org
Reporter: malte.ge...@googlemail.com
On a clean installation of kubuntu 16.04 akonadi won't start.
The initial creation of the mysql database fails.
Reproducible: Always
Steps to Reproduce:
1. Clean install of kubuntu 16.04 beta release
2. Start akonadi from the cli using 'akonadictl start'
Actual Results:
initial start fails
akonadi is not usable at all
Expected Results:
initial start of akonadi and be able to set up ressources
janmalte@ubuntu:~$ akonadictl start
Starting Akonadi Server...
done.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths: ("/home/janmalte/.composer/vendor/bin", "/home/janmalte/.bin",
"/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin", "/sbin", "/bin",
"/usr/games", "/usr/local/games", "/opt/bin", "/usr/sbin", "/usr/local/sbin",
"/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec",
"/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Found mysql_install_db: "/usr/bin/mysql_install_db"
Found mysqlcheck: "/usr/bin/mysqlcheck"
mysql_install_db: [ERROR] unknown option '--force'
2016-04-07 08:51:57 [ERROR] Unrecognized options
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld-akonadi"
arguments: ("--defaults-file=/home/janmalte/.local/share/akonadi/mysql.conf",
"--datadir=/home/janmalte/.local/share/akonadi/db_data/",
"--socket=/tmp/akonadi-janmalte.ddv6eY/mysql.socket")
stdout: ""
stderr: ""
exit code: 1
process error: "Unknown error"
terminating service threads
terminating connection threads
stopping db process
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket
'/tmp/akonadi-janmalte.ddv6eY/mysql.socket' (2)'
Check that mysqld is running and that the socket:
'/tmp/akonadi-janmalte.ddv6eY/mysql.socket' exists!
Failed to remove Unix socket
Failed to remove runtime connection config file
Application 'akonadiserver' exited normally...
--
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 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #28 from Jan-Matthias Braun <jan_br...@gmx.net> --- Okay, I think I have answered my own question: It is there and therefore I should better open a new but. Please excuse the noise... :-/ -- 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 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #27 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi! I do have the impression that this issue came back with 15.12.: My outlook imap is not syncing anymore. Does somebody else see the same behaviour? Can the fix somehow have evaded going into 15.12 or should I open a new bug report? All the best, Jan -- 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
[kleopatra] [Bug 357933] Kleopatra 15.12.1 (2.2): load certifications (pgp) - segfault after infinite recursion
https://bugs.kde.org/show_bug.cgi?id=357933 Jan Kundrát <j...@kde.org> changed: What|Removed |Added CC||j...@kde.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
[kontact] [Bug 358364] New: Crashes on startup ever since trying to answer email
https://bugs.kde.org/show_bug.cgi?id=358364 Bug ID: 358364 Summary: Crashes on startup ever since trying to answer email Product: kontact Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: b...@ucw.cz Application: kontact (4.14.10) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.3.0-1-amd64 x86_64 Distribution: Debian GNU/Linux testing (stretch) -- Information about the crash: - What I was doing when the application crashed: Kontact crashed. I am not sure whether it was trying to answer or just display email. Ever since it crashes immediately on startup. Starting kmail alone crashes as well. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f508d07d940 (LWP 3726))] Thread 3 (Thread 0x7f5066317700 (LWP 3727)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f50897baa4d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f50897baaa9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f50842bf284 in start_thread (arg=0x7f5066317700) at pthread_create.c:333 #4 0x7f508a56974d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f5025a14700 (LWP 3742)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f50894de191 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f50897eafe6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f50842bf284 in start_thread (arg=0x7f5025a14700) at pthread_create.c:333 #4 0x7f508a56974d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f508d07d940 (LWP 3726)): [KCrash Handler] #6 0x7f508a4b4657 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #7 0x7f508a4b5a2a in __GI_abort () at abort.c:89 #8 0x7f508a4f2bb3 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f508a5eb5f8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7f508a4f800e in malloc_printerr (action=1, str=0x7f508a5eb708 "free(): invalid next size (fast)", ptr=) at malloc.c:4965 #10 0x7f508a4f87eb in _int_free (av=, p=, have_lock=0) at malloc.c:3834 #11 0x7f508b9bd89d in QTextEngine::clearLineData() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #12 0x7f508ba09b8f in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13 0x7f508bbdb564 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #14 0x7f508bbdbde0 in QTextEdit::resizeEvent(QResizeEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #15 0x7f508b7a71b0 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #16 0x7f508bb6d80e in QFrame::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #17 0x7f508ad2abd6 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #18 0x7f508b7508bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #19 0x7f508b757816 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #20 0x7f508c4d271a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #21 0x7f508ad2aa6d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #22 0x7f508b7a3321 in QWidgetPrivate::sendPendingMoveAndResizeEvents(bool, bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #23 0x7f508b7a44b3 in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #24 0x7f508b7a6502 in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #25 0x7f508b7a4407 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #26 0x7f508b7a44cf in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #27 0x7f508b7a6502 in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #28 0x7f508b7a4407 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #29 0x7f508b7a44cf in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #30 0x7f508b7a6502 in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #31 0x7f508b7a4407 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #32 0x7f508b7a44cf in QWidgetPrivate::show_helper() () from
[kontact] [Bug 358364] Crashes on startup ever since trying to answer email
https://bugs.kde.org/show_bug.cgi?id=358364 --- Comment #2 from Jan Hudec <b...@ucw.cz> --- Created attachment 96785 --> https://bugs.kde.org/attachment.cgi?id=96785=edit Valgrind memcheck trace I killed kontact after it started (successfully under valgrind). When I then started it, it crashed again, so I am quite sure the log corresponds to the faulty case. -- 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 358364] Crashes on startup ever since trying to answer email
https://bugs.kde.org/show_bug.cgi?id=358364 Jan Hudec <b...@ucw.cz> changed: What|Removed |Added Component|general |mail -- 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 358364] Crashes on startup ever since trying to answer email
https://bugs.kde.org/show_bug.cgi?id=358364 --- Comment #1 from Jan Hudec <b...@ucw.cz> --- I am now certain it started after trying to answer email, because when I started it under valgrind it filtered the invalid write and two composers opened. I am attaching the valgrind memcheck output. There are two invalid writes, presumably one in each composer that starts. The backtraces clearly show they are MessageComposer-related. Unfortunately Debian does not seem to have debug information for the /usr/lib/libkmailprivate.so.4.14.10, which appears on the last line of the stack trace. All of the MessageComposer and everything called from it is decoded correctly though. Hope it helps. Kind regards, Jan -- 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 358364] Crashes on startup ever since trying to answer email
https://bugs.kde.org/show_bug.cgi?id=358364 --- Comment #3 from Jan Hudec <b...@ucw.cz> --- Created attachment 96786 --> https://bugs.kde.org/attachment.cgi?id=96786=edit One more valgrind trace When I started it next time, one more message editor came up. However the number of invalid writes remained two. I also noticed some invalid reads there. The standard error also showed these errors: kontact(9096) MessageList::Core::ModelPrivate::findMessageParent: Circular reference loop detected in the message tree kontact(9096) MessageList::Core::ModelPrivate::viewItemJobStepInternalForJobPass1Fill: Circular In-Reply-To reference loop detected in the message tree kontact(9096) MessageList::Core::ModelPrivate::findMessageParent: Circular In-Reply-To reference loop detected in the message tree Not sure whether they are related; they appeared long after the point where it would have crashed without valgrind. -- 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 358364] Crashes on startup ever since trying to answer email
https://bugs.kde.org/show_bug.cgi?id=358364 --- Comment #4 from Jan Hudec <b...@ucw.cz> --- I closed the message editors when running under valgrind. Since then, kontact starts up correctly again. This workaround isn't for mere mortals, but presumably there might be some way to remove the draft message via akonadi. I don't know how though; I restarted since it started crashing and something remembered there should be message editor open across it. -- 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 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 --- Comment #17 from Jan <malte.ge...@googlemail.com> --- This is still present: Akonadi 5.0.51 kmail2 5.0.3 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 Jan <malte.ge...@googlemail.com> changed: What|Removed |Added Keywords||regression, reproducible -- 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 349800] Akonadi IMAP resource crashes when refreshing folders in KMail while search folder is open
https://bugs.kde.org/show_bug.cgi?id=349800 Jan Binder <wh...@herr-der-mails.de> changed: What|Removed |Added CC||wh...@herr-der-mails.de --- Comment #2 from Jan Binder <wh...@herr-der-mails.de> --- Still present in libkf5imap from kde applications 15.08.2: Application: Akonadi Resource (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 0x7f840895c940 (LWP 3840))] Thread 4 (Thread 0x7f8407429700 (LWP 3851)): #0 0x7f841830286d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f8413a5d382 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f8413a5eff7 in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f840871f569 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f8418bfd87e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8413c7c284 in start_thread (arg=0x7f8407429700) at pthread_create.c:333 #6 0x7f841830b74d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f83f700 (LWP 3979)): #0 0x7f8412f3ea14 in g_mutex_unlock (mutex=0x7f83f8000990) at /build/glib2.0-F6SQOr/glib2.0-2.47.3/./glib/gthread-posix.c:1350 #1 0x7f8412ef9880 in g_main_context_prepare (context=context@entry=0x7f83f8000990, priority=priority@entry=0x7f83eb50) at /build/glib2.0-F6SQOr/glib2.0-2.47.3/./glib/gmain.c:3440 #2 0x7f8412efa22b in g_main_context_iterate (context=context@entry=0x7f83f8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-F6SQOr/glib2.0-2.47.3/./glib/gmain.c:3820 #3 0x7f8412efa40c in g_main_context_iteration (context=0x7f83f8000990, may_block=1) at /build/glib2.0-F6SQOr/glib2.0-2.47.3/./glib/gmain.c:3901 #4 0x7f8418e3539b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8418ddc35a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8418bf88d4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8418bfd87e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8413c7c284 in start_thread (arg=0x7f83f700) at pthread_create.c:333 #9 0x7f841830b74d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f83f5325700 (LWP 4079)): #0 0x7f841830286d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f8412efa2fc in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f83ec003020, timeout=, context=0x7f83ec000990) at /build/glib2.0-F6SQOr/glib2.0-2.47.3/./glib/gmain.c:4135 #2 0x7f8412efa2fc in g_main_context_iterate (context=context@entry=0x7f83ec000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-F6SQOr/glib2.0-2.47.3/./glib/gmain.c:3835 #3 0x7f8412efa40c in g_main_context_iteration (context=0x7f83ec000990, may_block=1) at /build/glib2.0-F6SQOr/glib2.0-2.47.3/./glib/gmain.c:3901 #4 0x7f8418e3539b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8418ddc35a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8418bf88d4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8418bfd87e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8413c7c284 in start_thread (arg=0x7f83f5325700) at pthread_create.c:333 #9 0x7f841830b74d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f840895c940 (LWP 3840)): [KCrash Handler] #6 0x7f841c2f347d in KIMAP::SearchJob::handleResponse(KIMAP::Message const&) () at /usr/lib/x86_64-linux-gnu/libKF5IMAP.so.5 #7 0x7f841c2fae5b in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () at /usr/lib/x86_64-linux-gnu/libKF5IMAP.so.5 #8 0x7f8418e0e601 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f8419750ffc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f84197564c6 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f8418ddebcb in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f8418de0fc6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f8418e34f73 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f8412efa107 in g_main_context_dispatch (context=0x7f8416f0) at /build/glib2.0-F6SQOr/glib2.0-2.47.3/./glib/gmain.c:3154 #15 0x7f8412efa107 in g_main_context_dispatch (context=context@entry=0x7f8416f0) at
[kmail2] [Bug 355093] Crash if I click on new mail
https://bugs.kde.org/show_bug.cgi?id=355093 Jan <malte.ge...@googlemail.com> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- 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 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 Jan <malte.ge...@googlemail.com> changed: What|Removed |Added Priority|NOR |HI -- 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 255104] KMail fails to start with: Could not create collection
https://bugs.kde.org/show_bug.cgi?id=255104 Jan Wiele <j...@wiele.org> changed: What|Removed |Added CC||j...@wiele.org --- Comment #17 from Jan Wiele <j...@wiele.org> --- I also encounter this bug on Kubuntu 15.10 with Kmail 5.0.2 after moving my Trash from local folders to my IMAP trash folder. -- 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 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 Jan <malte.ge...@googlemail.com> changed: What|Removed |Added CC||jus...@affinix.com --- Comment #14 from Jan <malte.ge...@googlemail.com> --- *** Bug 316153 has been marked as a duplicate of this bug. *** -- 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 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 Jan <malte.ge...@googlemail.com> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #36 from Jan <malte.ge...@googlemail.com> --- *** This bug has been marked as a duplicate of bug 354056 *** -- 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
