[akregator] [Bug 412771] New: Akregator crashes when clicking a link in a web page
https://bugs.kde.org/show_bug.cgi?id=412771 Bug ID: 412771 Summary: Akregator crashes when clicking a link in a web page Product: akregator Version: 5.12.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: t...@nobu-games.com Target Milestone: --- Application: akregator (5.12.1) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-31-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Links in web pages cause Akregator to crash. In this case I tried to open a link on a Reddit page. 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 0x7f4c6fb82bc0 (LWP 12051))] Thread 22 (Thread 0x7f4b2e7be700 (LWP 12179)): #0 0x7f4c5de6bed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f4b2e7bd6f0, expected=0, futex_word=0x7f4b2e7bd8c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f4c5de6bed9 in __pthread_cond_wait_common (abstime=0x7f4b2e7bd790, mutex=0x7f4b2e7bd878, cond=0x7f4b2e7bd8a0) at pthread_cond_wait.c:533 #2 0x7f4c5de6bed9 in __pthread_cond_timedwait (cond=0x7f4b2e7bd8a0, mutex=0x7f4b2e7bd878, abstime=0x7f4b2e7bd790) at pthread_cond_wait.c:667 #3 0x7f4c64c480c6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4c64c48a5d in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4c64c48bf2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4c64c01ca1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4c64c04bad in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4c64c052d4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4c64c4aa65 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4c5de656db in start_thread (arg=0x7f4b2e7be700) at pthread_create.c:463 #11 0x7f4c6b91388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f4b2f93f700 (LWP 12177)): #0 0x7f4c5de6b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f4b2f93e8d8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f4c5de6b9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f4b2f93e888, cond=0x7f4b2f93e8b0) at pthread_cond_wait.c:502 #2 0x7f4c5de6b9f3 in __pthread_cond_wait (cond=0x7f4b2f93e8b0, mutex=0x7f4b2f93e888) at pthread_cond_wait.c:655 #3 0x7f4c64c47fca in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4c64c48a6c in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4c64c48baf in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4c64c01c75 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4c64c04bad in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4c64c05314 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4c64c4aa65 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4c5de656db in start_thread (arg=0x7f4b2f93f700) at pthread_create.c:463 #11 0x7f4c6b91388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f4b3ebeb700 (LWP 12097)): #0 0x7f4c5de6bed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f4b3ebea6f0, expected=0, futex_word=0x7f4b3ebea8c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f4c5de6bed9 in __pthread_cond_wait_common (abstime=0x7f4b3ebea790, mutex=0x7f4b3ebea878, cond=0x7f4b3ebea8a0) at pthread_cond_wait.c:533 #2 0x7f4c5de6bed9 in __pthread_cond_timedwait (cond=0x7f4b3ebea8a0, mutex=0x7f4b3ebea878, abstime=0x7f4b3ebea790) at pthread_cond_wait.c:667 #3 0x7f4c64c480c6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4c64c48a5d in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4c64c48bf2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4c64c01ca1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4c64c04f0b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4c64c052d4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4c64c4aa65 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4c5de656db in start_thread (arg=0x7f4b3ebeb700) at pthread_create.c:463 #11 0x7f4c6b91388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f4b3f56c700 (LWP 12096)): #0 0x7f4c5de6b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x
[korganizer] [Bug 357819] Korganizer doesn't send calendar events to Google account
https://bugs.kde.org/show_bug.cgi?id=357819 Thomas Iguchi changed: What|Removed |Added CC||t...@nobu-games.com --- Comment #6 from Thomas Iguchi --- I have sync problems in both directions. Log output in .xsession-errors seems very sparse and not really helpful. There are repeated log lines like these: org.kde.pim.akonadiserver: Error while handling command ModifyCollection on connection akonadi_googlecalendar_resource_0 org.kde.kgapi: Requested resource does not exist The only way to get Google calendar sync temporarily working (for maybe 10 minutes) is by restarting each calendar account in the settings. Not sure if that's related, but the Google access token expires beforehand: KGAPI2::CalendarFetchJob(0x55a957f330f0) "Invalid authentication." org.kde.kgapi: Unauthorized. Access token has expired or is invalid. Maybe the token is not properly refreshed in that case of failure. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 406411] Korganizer daemon closes when plasma starts
https://bugs.kde.org/show_bug.cgi?id=406411 Thomas Iguchi changed: What|Removed |Added CC||t...@nobu-games.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 316341] New: Kmail forgets SMTP passwords
https://bugs.kde.org/show_bug.cgi?id=316341 Bug ID: 316341 Summary: Kmail forgets SMTP passwords Classification: Unclassified Product: kmail2 Version: 4.9.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: t...@nobu-games.com KMail randomly (but regularly) forgets SMTP passwords of all my email accounts even though the remember checkbox is checked. Unlike a similar bug I never cancelled the password dialog. KMail could remember passwords for the past few months but now it randomly forgets all different kinds of settings. Reproducible: Sometimes Steps to Reproduce: 1. Restart KDE / KMail 2. Try to send mail 3. SMTP Password dialog shows up 4. Enter password for the umptieth time 5. Check "remember password" box 6. Press ok 7. Hope for the best -- 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 314772] Kontact loses settings and layout changes when KDE shuts down
https://bugs.kde.org/show_bug.cgi?id=314772 --- Comment #1 from Thomas Iguchi --- This bug is especially a nuisance since one of my most important calendars is hosted online on an ownCloud server. The calendar gets randomly deactivated from time to time (checkmark is automatically removed from the checkbox and I really have not the slightest clue why). When I happen to notice that problem it does not suffice to just check that box again. I need to check it, close Kontact start it again and hope for the best. But unfortunately another unrelated bug makes calendar notifications in Kontact also pretty much useless. Your computer needs to be switched on at the point in time the appointment notification kicks in. It does not notify you about alarms that started slightly in the past. Kontact used to work years ago. I could rely on not missing a single calendar event notification. Also simple stuff like email recipient auto-completion used to work. Kontact felt solid, reliable and well-made. Since the migration to Akonadi that changed dramatically. -- 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 314772] New: Kontact loses settings and layout changes when KDE shuts down
https://bugs.kde.org/show_bug.cgi?id=314772 Bug ID: 314772 Summary: Kontact loses settings and layout changes when KDE shuts down Classification: Unclassified Product: kontact Version: 4.9.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: t...@nobu-games.com Kontact loses settings like activated / checked calendar or address book resources as well as layout changes like shifted panes when KDE shuts down. I have Kontact permanently running and do not close it prior shutting down so it gets automatically restored on restart. However, these mentioned settings only get properly persisted when I manually close Kontact. Reproducible: Always Steps to Reproduce: 1. Change any layout property of any of the plugins or activate / deactivate a calendar or addressbook 2. Shutdown PC / KDE 3. Restart Actual Results: The applied changes are lost. Expected Results: Kontact should persist these changes right away so a forceful shutdown does not discard them. Maybe KDE should also just wait for applications to stop properly instead of just killing them. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
