[Akonadi] [Bug 485132] New: DAV resource: invalid response from backend
https://bugs.kde.org/show_bug.cgi?id=485132 Bug ID: 485132 Summary: DAV resource: invalid response from backend Classification: Frameworks and Libraries Product: Akonadi Version: 6.0.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: DAV Resource Assignee: kdepim-b...@kde.org Reporter: t...@tsbarnes.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY When I add a DAV resource, fetching from it always fails with the error "Invalid response from backend" STEPS TO REPRODUCE 1. Add a DAV resource in KOrganizer 2. Attempt to fetch the list of calendars 3. An error pops up says "Invalid response from backend" OBSERVED RESULT An error dialog stating "Invalid response from backend" EXPECTED RESULT Fetching the list of calendars SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 440811] Calendar events don't show up at all for some calendars
https://bugs.kde.org/show_bug.cgi?id=440811 Thea Barnes changed: What|Removed |Added Version|unspecified |5.17.3 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 440811] Calendar events don't show up at all for some calendars
https://bugs.kde.org/show_bug.cgi?id=440811 Thea Barnes changed: What|Removed |Added Summary|Calendar events don't sho |Calendar events don't show |up at all for some |up at all for some |calendars |calendars -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 440811] New: Calendar events don't sho up at all for some calendars
https://bugs.kde.org/show_bug.cgi?id=440811 Bug ID: 440811 Summary: Calendar events don't sho up at all for some calendars Product: kontact Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-b...@kde.org Reporter: t...@tsbarnes.com Target Milestone: --- SUMMARY Calendar events don't show up at all for some calendars STEPS TO REPRODUCE 1. Add a calendar that uses DavMail 2. Notice that the events are never displayed 3. Check the DavMail logs, they show it successfully retrieving them OBSERVED RESULT No events are shown from the bugged calendar EXPECTED RESULT Events should be shown from all the calendars SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I've had this issue with EWS calendars as well, and occasionally with a Google account, though with Google accounts removing it and re-adding it will sometimes fix it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 429789] New: Item is in an invalid or unknown state
https://bugs.kde.org/show_bug.cgi?id=429789 Bug ID: 429789 Summary: Item is in an invalid or unknown state Product: frameworks-knewstuff Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: t...@tsbarnes.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Attempting to update a theme produced an unknown state STEPS TO REPRODUCE 1. Go to a KNewStuff dialog 2. Find one with an update available and go to it 3. Click "Update" OBSERVED RESULT "This item is currently in an invalid or unknown state." EXPECTED RESULT Updating the theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.10 (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Theme was "Ant-Dracula" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428617] GTK+ settings crashes when applying
https://bugs.kde.org/show_bug.cgi?id=428617 Thea Barnes changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #7 from Thea Barnes --- (In reply to Christoph Feck from comment #6) > Please see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB So I did that, and it turns out the crash was in appmenu-gtk2 (a leftover package from before I switched to KDE); after removing that, the crash no longer occurs. Thanks for your help! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428617] GTK+ settings crashes when applying
https://bugs.kde.org/show_bug.cgi?id=428617 --- Comment #5 from Thea Barnes --- (In reply to Mikhail Zolotukhin from comment #4) > There should be a program called Dr Konqui or something like that on > Kubuntu. It should show the notification after the crash happened and > suggest you to show the backtrace if you click on it. Dr. Konqi doesn't show up when it crashes anymore, it did the first few times it happened, but now it just crashes silently. Is there another way to generate the backtrace? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428617] GTK+ settings crashes when applying
https://bugs.kde.org/show_bug.cgi?id=428617 --- Comment #3 from Thea Barnes --- (In reply to Mikhail Zolotukhin from comment #1) > I cannot reproduce. Could you please provide a crash backtrace? What's the easiest way for me to get a stack trace of the crash? (In reply to Mikhail Zolotukhin from comment #2) > And what GTK theme do you mean GTK2 or GTK3? Either one, just clicking Apply after a change is what crashes it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428617] New: GTK+ settings crashes when applying
https://bugs.kde.org/show_bug.cgi?id=428617 Bug ID: 428617 Summary: GTK+ settings crashes when applying Product: systemsettings Version: 5.19.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_style Assignee: plasma-b...@kde.org Reporter: t...@tsbarnes.com CC: zom...@protonmail.com Target Milestone: --- SUMMARY When I change my GTK+ theme, clicking "Apply" applies the changes properly, but then immediately crashes System Settings. STEPS TO REPRODUCE 1. Open System Settings 2. Change GTK+ theme 3. Click "Apply" OBSERVED RESULT GTK+ theme is changed, followed by a crash EXPECTED RESULT No crash afterwards SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.10 (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 407147] Kopete crashes when trying to associate an address book entry to a new contact
https://bugs.kde.org/show_bug.cgi?id=407147 Thea Barnes changed: What|Removed |Added CC||t...@tsbarnes.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 423759] New: Opening folder properties crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=423759 Bug ID: 423759 Summary: Opening folder properties crashes Kontact Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: t...@tsbarnes.com Target Milestone: --- Application: kontact (5.13.3 (19.12.3)) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-40-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04 LTS -- Information about the crash: - What I was doing when the application crashed: I was attempting to open the folder properties on a Gmail account folder. It doesn't crash every time I do it, but about half the time. The same Gmail account also performs much worse than my other accounts. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8b0e6ecf00 (LWP 748984))] Thread 32 (Thread 0x7f8a5c985700 (LWP 785689)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f8a5c9844a0, clockid=, expected=0, futex_word=0x7f8a5c9845e8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f8a5c9844a0, clockid=, mutex=0x7f8a5c984598, cond=0x7f8a5c9845c0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f8a5c9845c0, mutex=0x7f8a5c984598, abstime=0x7f8a5c9844a0) at pthread_cond_wait.c:656 #3 0x7f8b1b11bb2e in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f8b1b11c51f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f8b1b11c615 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f8b1b0ddda6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8b1b0e0939 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8b1b0e0ef8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8b1b11eb63 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8b20b78609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f8b21b8d103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7f8addffb700 (LWP 785688)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f8addffa4a0, clockid=, expected=0, futex_word=0x7f8addffa5e8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f8addffa4a0, clockid=, mutex=0x7f8addffa598, cond=0x7f8addffa5c0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f8addffa5c0, mutex=0x7f8addffa598, abstime=0x7f8addffa4a0) at pthread_cond_wait.c:656 #3 0x7f8b1b11bb2e in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f8b1b11c51f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f8b1b11c615 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f8b1b0ddda6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8b1b0e0c48 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8b1b0e0ef8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8b1b11eb63 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8b20b78609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f8b21b8d103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7f8a5d186700 (LWP 785687)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f8a5d1854a0, clockid=, expected=0, futex_word=0x7f8a5d1855e8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f8a5d1854a0, clockid=, mutex=0x7f8a5d185598, cond=0x7f8a5d1855c0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f8a5d1855c0, mutex=0x7f8a5d185598, abstime=0x7f8a5d1854a0) at pthread_cond_wait.c:656 #3 0x7f8b1b11bb2e in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f8b1b11c51f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f8b1b11c615 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f8b1b0ddda6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8b1b0e0c48 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8b1b0e0ef8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8b1b11eb63 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8b20b78609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f8b21b8d103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7f8add7fa700 (LWP 785686)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f8add7f94a0, clockid=, expected=0,
