Bug 362820 - Juk crashes on startup
Summary: Juk crashes on startup
Status: RESOLVED WORKSFORME
Alias: None
Product: juk
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Scott Wheeler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-08 16:40 UTC by Guido Winkelmann
Modified: 2018-12-02 03:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guido Winkelmann 2016-05-08 16:40:11 UTC
When starting juk, the splash screen will appear for a split second, then disappear again. Nothing else happens.

When starting juk from the command line, I get this error message:

$ juk
juk(13305): Communication problem with  "juk" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message recipient disconnected from message bus without replying" "

Reproducible: Always

Steps to Reproduce:
1. Start juk

Actual Results:  
The splash screen appears, then immediately disappears again.

Expected Results:  
Juk should start up correctly, displaying either its main window or it system tray icon.

Version according to portage is 15.08.3
Comment 1 Guido Winkelmann 2016-05-09 19:55:04 UTC
Addedum:

juk -v says:

Qt: 4.8.6
KDE Development Platform: 4.14.19
JuK: 3.12
Comment 2 Andrew Crouthamel 2018-11-01 13:57:39 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-16 11:41:37 UTC
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!
Comment 4 Bug Janitor Service 2018-12-02 03:47:49 UTC
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!