| Summary: | Plasma crashes after trying to create a new file on the desktop | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Agustin Ayala <rosendoagustinayala> |
| Component: | Containment | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | kde, nate, notmart, qydwhotmail |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.25.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 5.27 | |
| Sentry Crash Report: | |||
|
Description
Agustin Ayala
2022-09-29 18:15:47 UTC
#4 0x00007f78e84b8b3c in ?? () from /lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5 The backtrace is not complete. You need to install debuginfo for kio Hi. Thanks for the quick response. 1. First of all, I want to update my... I don't know how you call it... my first comment. Apparently, the behavior is very erratic. Now, when I try to create the file, the wallpaper don't change and the file is not created (it didn't before either), but when I try for a second time it does, and it does it every time, I don't know when it start to fail. 2. I forgot to mention that I update every Sunday at the very least, and some days during the week when I can. This is because I don't want my computer to break on an update during the week. That's another thing I want to mention. I'm not able to customize the update schedule. I tried with software-properties-qt but it doesn't work. I would like the updates to be installed when I turn off the computer, but I wasn't able to get it work. I read a very long thread regarding offline updates (https://forum.kde.org/viewtopic.php?f=309&t=170775), and I mention my problem, but I didn't have a good response. 3. I was about to update when I had the problem, but I decided not to. On the next point I will give you some command outputs on the current status and I will wait for you to tell me when you have all the info you need before I do so. 4. Regarding your response, I follow the assistant to file the bug. Here's the sources list it created: cat /etc/apt/sources.list.d/org.kde.neon.com.ubuntu.ddebs.list deb http://ddebs.ubuntu.com focal main restricted universe multiverse deb http://ddebs.ubuntu.com focal-updates main restricted universe multiverse deb http://ddebs.ubuntu.com focal-proposed main restricted universe multiverse The debug symbols it installed pkcon search dbgsym | sed -n '/^Installed/p' Installed kio-dbgsym-5.98.0-0xneon+20.04+focal+release+build95.amd64 (installed:user_focal-focal-main) Installed libqt5core5a-dbgsym-5.15.5+p20.04+tunstable+git20220920.0042-0.amd64 (installed:user_focal-focal-main) Installed libqt5gui5-dbgsym-5.15.5+p20.04+tunstable+git20220920.0042-0.amd64 (installed:user_focal-focal-main) Installed libqt5widgets5-dbgsym-5.15.5+p20.04+tunstable+git20220920.0042-0.amd64 (installed:user_focal-focal-main) Installed ubuntu-dbgsym-keyring-2020.02.11.4.all (installed:ubuntu-focal-updates-main) Now, considering your answer, I follow a thread on askubuntu (https://askubuntu.com/questions/487222/how-to-install-debug-symbols-for-installed-packages) and add this line on the sources list: deb http://ddebs.ubuntu.com focal-security main restricted universe multiverse But when I try to update I get this error: sudo apt update [sudo] password for admin: Des:1 file:/var/lib/preinstalled-pool focal InRelease Ign:1 file:/var/lib/preinstalled-pool focal InRelease Des:2 file:/var/lib/preinstalled-pool focal Release [3.949 B] Des:2 file:/var/lib/preinstalled-pool focal Release [3.949 B] Des:4 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB] Ign:5 http://ddebs.ubuntu.com focal InRelease Obj:6 http://archive.ubuntu.com/ubuntu focal InRelease Des:7 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Obj:8 https://deb.librewolf.net focal InRelease Ign:9 http://ddebs.ubuntu.com focal-updates InRelease Ign:10 http://ddebs.ubuntu.com focal-proposed InRelease Ign:11 http://ddebs.ubuntu.com focal-security InRelease Des:12 http://ddebs.ubuntu.com focal Release [40,4 kB] Des:13 http://archive.neon.kde.org/user focal InRelease [162 kB] Des:15 http://ddebs.ubuntu.com focal-updates Release [40,5 kB] Obj:17 http://ddebs.ubuntu.com focal-proposed Release Err:18 http://ddebs.ubuntu.com focal-security Release 404 Not Found [IP: 2620:2d:4000:1::2b 80] Leyendo lista de paquetes... Hecho E: El repositorio «http://ddebs.ubuntu.com focal-security Release» no tiene un fichero de Publicación. N: No se puede actualizar de un repositorio como este de forma segura y por tanto está deshabilitado por omisión. N: Vea la página de manual apt-secure(8) para los detalles sobre la creación de repositorios y la configuración de usuarios. But I guess it's because I have to install the GPG key for the repositories. 5. This is the only uninstalled debug symbol that the assistant got behind. pkcon search kio-dbg Installed kio-dbgsym-5.98.0-0xneon+20.04+focal+release+build95.amd64 (installed:user_focal-focal-main) debug symbols for kio Available qml-module-org-kde-kio-dbgsym-5.98.0-0xneon+20.04+focal+release+build78.amd64 (user_focal-focal-main) debug symbols for qml-module-org-kde-kio Tell me if I have to install qml-module and give you all the backtrace again or install qml-module AND update the system and then give you the backtrace. 6. So, to summarize, I have to: 1. Install the GPG key for the repositories 2. Add deb http://ddebs.ubuntu.com focal-security main restricted universe multiverse to the sources list. 3. Install qml-module 4. Update the system Did I get right? Which steps do I have to follow and which ones don't? In what order? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! If you need help getting debug symbols, please ask in a venue specific to your distro. Are you able to reproduce this issue in Plasma 5.27.4? Ok, I will ask on the KDE Neon venue, as fast as I can. Regarding your question, yes, I'm currently on Plasma 5.27.4 and updating everyday. I don't know if I mention it but it only happens on folders placed on the Desktop. To be short; if I create a folder on the Desktop, access its content by clicking on the 'up' arrow and try to create an item (file, folder), this is what happens: 1. All items disappears, like when you log out you account or shutdown. 2. The screen turns black , all you can see is the mouse cursor. 3. The items reappears and the wallpaper that was set was replaced by another. The solution I found was to place the folder somewhere else and use a Folder View Widget. To tell you that I just test it several times, and something new happens. After trying several times, you try one more and: 1. Same as before 2. Same as before 3. The items doesn't reappear, the screen stays black. 4. I tried several shortcuts, including Win+L to block the screen. Can log in again, but I was able to come back to the browser window where I'm writing these response, and the Plasma's Taskbar has disappear. Interesting, I just tried those exact steps and I still don't get a crash. Any chance you could attach a screen recording or a phone video so I can be sure I'm doing exactly the same thing you are? You fix it! After today's update I'm no longer able to reproduce the issue, although I tried many times. You're a genius. I'm marking it as solved. Thank you very much. Heh I wish I could take credit, but I didn't do anything. :) Maybe someone else did though. Glad it's fixed now! |