When I try to start Juk, it dies. The crash report self-diagnoses as having insufficient information to be worth reporting. I suspect therefore that this issue is under-reported. I am running Linux Mint 18.2 and haven't done anything special with Juk. I have 200GB of sound files, 15034 items. I have used Juk successfully for some months, but now it crashes on start. Application: juk (3.12) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.13.0-31-generic x86_64 Distribution: Linux Mint 18.2 Sonya
Hi Alan, If you have debug packages available for juk I'd like to request that you install those (or otherwise enable those) and see if you can reproduce the crash. If you can please comment with the backtrace or attach as a comment, those make it significantly easier to troubleshoot the issue, especially for those like me who no longer maintain KDE4 development environments. Also, have you recently upgraded or otherwise changed juk itself? Or did this start happening out of the blue?
Juk is currently working apparently just fine today. Can you give me a path to the 3.12 debug package- they are not part of mint and I can find everything else except the package I want. I have only done routine apt-get update & upgrade, nothing special with Juk except I changed the directory path (yesterday I think) from //diskstation/mp3/moved to /home/ahowlett/Music The latter path is still in place and working just fine. Ah... I also had an issue with SMB. I use a synology diskstation as my server, which was set to only use SMB1 and I became unable to access it at some point when I upgraded my machine (mint) and my box decided it did not want to use SMB1 any more. Thank you for your interest so far. I wish to help you get to the bottom of this if I can- and it might indeed be an issue coming from SMB stopping working.
According to https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Linux_Mint, Linux Mint mostly uses Ubuntu packages. So the question is really what the Ubuntu package name is for juk's debug symbols. So for that, according to https://launchpad.net/ubuntu/+source/juk, the package name is "juk-dbgsym", so that seems to be what you'd want to install (with apt-get or otherwise) in order to get better backtraces. A temporary error condition with SMB makes sense as a cause of the crash, though that doesn't help too much on narrowing it down. If you're willing to get a proper backtrace even though JuK is now working for you, then I'll see if I can fix it.
Thank you. I appreciate your involvement. I can't figure out how to install the debug package, and my system is now working properly. I give up for now. But again, I thank you for your help.
OK, will mark as needing info for now but thanks for the report regardless, useful to have for awareness as we continue to evolve the code.
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 set the bug status 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!
Dear Bug Submitter, 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!