Created attachment 140928 [details] When you right-click on a text file, the system crashes SUMMARY: When you right-click on a text file, the system crashes STEPS TO REPRODUCE 1. Create a text file with any name on the desktop. 2. Right-click on this text file. 3. Scroll through the menu items with the mouse down. OBSERVED RESULT: The system crashes into a black screen, blocking further use of KDE Neon. Expected result: A menu for selecting actions for the text file will appear. Environment: 1.KDE Plasma Version: 5.22.3 2.KDE Frameworks Version:5.85.0 3.Qt Version: 5.15.3 ADDITIONAL INFORMATION
Bother... I cannot reproduce this now but I also met this for a while (on Neon Unstable or Testing). I remember I could right click to get the context menu, I wanted to scroll down to the bottom to get to Properties but crashed out. I was able to move the mouse round outside the menu and get to Properties. Memory suggests that the issue was when you "scrolled through" Activities Describing this in "uncertain terms" because I didn't make notes.
Checked a Neon Testing KDE Plasma Version: 5.22.3 KDE Frameworks Version:5.85.0 Qt Version: 5.15.3 snapshot, no joy. There definitely was an issue but I've "lost" it.
Hello , Could you please make a test in these 2 conditions : 1- When creating a new file instead of putting a Russian/crillic name, give a name like abc.txt and try if it crashes again or not 2- Disable the baloo ( on commandline use balooctrl disable ) and wait a few seconds then create your file and try it again * I know that there is a bug about baloo which causes it crash but it doesnt have to crash whole system ( and btw i will fix it within 1 week ) And also after crash could you share with us the coredumpctl logs ? ( in commandline/konsole coredumpctl list then find the crash then coredumpctl dump applicationName ( example : coredumpctl dump /usr/bin/kmix ) Thank you
.
When creating a new file in English new.txt, the error is repeated. Added a video of a bug with an English name
Created attachment 141034 [details] The system crashes into a black screen when creating a text file in English
Please attach a backtrace of the crash. :)
If you are still getting the crash... ... and "it went away" for me :-( set up a new user on the machine and see if it affects a clean setup. Also, if you can, do a snapshot before you do any updates (I'll admit that's easier if you experience the problem in a VM guest)
@Bogdan could you please disable baloo and test again if it crashes or not 1- open terminal / konsole 2- enter this command : balooctl disable 3- enter this command : balooctl purge 4- restart your system 5- Test if it crashes or not
PLAYBACK ACTIONS 1. Create a text file named abc on the desktop 2. Right-click this text file. 3. Scroll down the menu items with the mouse. After disabling the baloo, the same bug occurs. THE OBSERVED RESULT: the system crashes to a black screen, blocking further use of KDE Neon. Expected result: a menu for selecting actions for a text file will appear. Environment: KDE Plasma Version: 5.22.3 2. KDE Frameworks Version: 5.85.0 3. Qt Version: 5.15.3
After turning off the ballo, the same thing happens.
What would the baloo bug be that affects the context menu? I cannot properly see whether the crash happens when in the "Activities" menu item or the "Assign Tags". If the index is purged/empty then there'll be no tags indexed. As it's a new file, there won't be any extended attribute tags set... I suspect when I had the issue, I had baloo running but I don't remember whether I had any tags set up. I've tried on my 5.22.3 snapshot with and without tags and not seen anything.
We still need a backtrace of the crash, or else this is not actionable. :)
(In reply to Nate Graham from comment #13) > We still need a backtrace of the crash, or else this is not actionable. :) Try... https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!