[kdeconnect] [Bug 410149] Make & receive call from PC
https://bugs.kde.org/show_bug.cgi?id=410149 sid.swapnildev...@gmail.com changed: What|Removed |Added CC||sid.swapnildev...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466395] Random crashing
https://bugs.kde.org/show_bug.cgi?id=466395 --- Comment #7 from Sid --- Hi, yeah I think I'm fairly certain that its something to do with the taskbar, the taskbar is the most visible issue when plasmashell dies. now i dont know if its a cause or a symptom, but more often then not its the taskbar that freezes first (with everything else working just fine) before everything comes crashing down -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466395] Random crashing
https://bugs.kde.org/show_bug.cgi?id=466395 --- Comment #6 from Sid --- Oh yeah, I see. Could it be that multiple things are causing it to crash? should I maybe record multiple backtraces and add them all? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466395] Random crashing
https://bugs.kde.org/show_bug.cgi?id=466395 --- Comment #4 from Sid --- Hi there No problem! You guys are doing amazing work. I have attached the backtrace as well as a crash image now, please let me know if i can provide anything else that might help with the diagnosis Thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466395] Random crashing
https://bugs.kde.org/show_bug.cgi?id=466395 --- Comment #3 from Sid --- Created attachment 156912 --> https://bugs.kde.org/attachment.cgi?id=156912=edit Plasmashell error when run from console This is an error I got from running plasmashell via console (`plasmashell -n -d`). This was not the same run as the one with the backtrace (since i kinda forgot to run `thread apply all backtrace` (woops sorry), but this error has also happened a few times) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466395] Random crashing
https://bugs.kde.org/show_bug.cgi?id=466395 Sid changed: What|Removed |Added Assignee|plasma-b...@kde.org |m...@flaxeneel2.net Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- --- Comment #2 from Sid --- Created attachment 156911 --> https://bugs.kde.org/attachment.cgi?id=156911=edit Plasmashell backtrace this is the backtrace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466395] New: Random crashing
https://bugs.kde.org/show_bug.cgi?id=466395 Bug ID: 466395 Summary: Random crashing Classification: Plasma Product: plasmashell Version: 5.27.1 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m...@flaxeneel2.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.1) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.12-060112-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: Hi there! So ever since a few recent updates, plasmashell has been crashing a LOT on me randomly. It first pins 1-2 threads to 100% and then eventually dies. - System info: OS: KDE neon 5.27 x86_64 Host: Vivobook_ASUSLaptop M3401QA_M3401QA 1.0 Kernel: 6.1.12-060112-generic Uptime: 13 hours, 39 mins Packages: 2430 (dpkg), 7 (flatpak), 15 (snap) Shell: bash 5.1.16 Resolution: 2880x1800 DE: Plasma 5.27.1 WM: KWin Theme: [Plasma], Breeze [GTK2/3] Icons: [Plasma], breeze-dark [GTK2/3] Terminal: konsole CPU: AMD Ryzen 7 5800H with Radeon Graphics (16) @ 3.200GHz GPU: AMD ATI 03:00.0 Cezanne Memory: 13368MiB / 15398MiB - This has gotten so frequent that I have been running plasmashell on a konsole window (which i keep open so i can alt+tab to, cuz when the plasmashell crashes, the taskbar disappears too) I think it has something to do with the task bar? the taskbar is the most visible one when plasmashell freezes/crashes, because it auto hides itself (never to unhide itself till i alt tab to konsole n restart plasmashell). it also leaves a "ghost" of what i had over that portion of the screen before it crashed. it crashed again while i was typing this report, it is pretty common for some reason. The high memory usage in the system info is due to me working on something kinda heavy, but it also seems like plasma is taking 16.8% of the memory (according to htop at least) The memory usage seems to keep on growing with plasma, extreemely slowly, but it seems to? i mean im pretty certain it wasnt 16.8% when i booted up or was working on it for the first few hours I tried a bunch of stuff to reproduce it, but it seems pretty intermittent. I did get it to work a few times but i feel like it was some sort of fluke. I get messages like this right before it hangs/crashes. (more "Unable to assign [undefined] to QQuickItem*" lines below but i didnt include because they look similar) ``` file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/ConfigurationAppletPage.qml:38:5: QML Loader: Binding loop detected for property "height" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/DefaultListItemBackground.qml:57: ReferenceError: index is not defined file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/BreadcrumbControl.qml:16:5: Unable to assign [undefined] to QQuickItem* ``` also a spam of this sometimes ``` qrc:/ui/DuplicatesPage.qml:72:21: QML Action: Accessible must be attached to an Item qrc:/ui/DuplicatesPage.qml:92:21: QML Action: Accessible must be attached to an Item qrc:/ui/DuplicatesPage.qml:107:21: QML Action: Accessible must be attached to an Item ``` Thanks The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139940302157376) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139940302157376) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139940302157376, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f46c6842476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f46c68287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f46c6ca2bbe in () at /lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f46c6cae24c in () at /lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f46c6cae2b7 in () at /lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x7f46c7090f91 in qt_assert(char const*, char const*, int) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f46c7092e3c in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f46c6894b43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #15 0x7f46c6926a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 23 (Thread 0x7f4678ff9640 (LWP 49379) "plasmashel:sh2"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55cb87bfb7d8)
[Akonadi] [Bug 409341] Unable to start stable version of akonadi server or file bug report (Fedora 30)
https://bugs.kde.org/show_bug.cgi?id=409341 Sid Hymes changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #7 from Sid Hymes --- All attempts to obtain necessary files thru Fedora were unsuccessful. I therefore removed the entire kde-pim suite and reinstalled which corrected the problem. I noticed a few days later that some of the offending files had been updated (by Fedora) and it is unknown whether this would have resolved the problem. I have therefore marked the bug as resolved. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409341] Unable to start stable version of akonadi server or file bug report (Fedora 30)
https://bugs.kde.org/show_bug.cgi?id=409341 --- Comment #3 from Sid Hymes --- "Details" button is non-responsive so cannot generate self-test report and don't know of another way to generate the self-test results. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409341] Unable to start stable version of akonadi server or file bug report (Fedora 30)
https://bugs.kde.org/show_bug.cgi?id=409341 --- Comment #2 from Sid Hymes --- Response to starting Akonadi manually: akonadictl start (06/30/19 11:40:21) Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) [sid@hallie ~]$ org.kde.pim.akonadiserver: Starting up the Akonadi Server... org.kde.pim.akonadiserver: Failed to use database "akonadi" org.kde.pim.akonadiserver: Database error: "Can't connect to local MySQL server through socket '/tmp/akonadi-sid.T04dCL/mysql.socket' (2) QMYSQL: Unable to connect" org.kde.pim.akonadiserver: Failed to connect to database! org.kde.pim.akonadiserver: Database error: "Can't connect to local MySQL server through socket '/tmp/akonadi-sid.T04dCL/mysql.socket' (2) QMYSQL: Unable to connect" org.kde.pim.akonadiserver: Failed to remove runtime connection config file org.kde.pim.akonadiserver: Shutting down AkonadiServer... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally… -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409341] Unable to start stable version of akonadi server or file bug report (Fedora 30)
https://bugs.kde.org/show_bug.cgi?id=409341 Sid Hymes changed: What|Removed |Added CC||sidhy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409341] Unable to start stable version of akonadi server or file bug report (Fedora 30)
https://bugs.kde.org/show_bug.cgi?id=409341 --- Comment #1 from Sid Hymes --- Created attachment 121247 --> https://bugs.kde.org/attachment.cgi?id=121247=edit Missing, but not really, files -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409341] New: Unable to start stable version of akonadi server or file bug report (Fedora 30)
https://bugs.kde.org/show_bug.cgi?id=409341 Bug ID: 409341 Summary: Unable to start stable version of akonadi server or file bug report (Fedora 30) Product: Akonadi Version: 5.11.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: sidhy...@gmail.com Target Milestone: --- Created attachment 121246 --> https://bugs.kde.org/attachment.cgi?id=121246=edit Crash information from bug reporter SUMMARY Kontact, etc., report Akonadi as not being operational. Attempts to start result in large error messages. Attempts to file bug report result in error message that required files are not present; presence confirmed in specified location. Crash information (attached) deemed "not useful". All problems occurred after recent Fedora update. STEPS TO REPRODUCE 1. Start Kontact. 2. Kontact/KOrganizer opens with error message that akonadi not operational. 3. Manually starting akonadi results in repeated crash reports. 4. Use of system requires stopping akonadi. 5. See kdepim-users Digest, Vol 187, Issue 10 for additional details. OBSERVED RESULT Repeated crashes of akonadi and disabling of reliant apps. EXPECTED RESULT No crashes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 30, most recent versions (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
