[juk] [Bug 392377] QFSFileEngine::open: No file name specified on startup

2022-12-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=392377

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #10 from Bug Janitor Service  ---
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!

-- 
You are receiving this mail because:
You are watching all bug changes.

[juk] [Bug 392377] QFSFileEngine::open: No file name specified on startup

2022-12-02 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=392377

--- Comment #9 from Bug Janitor Service  ---
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!

-- 
You are receiving this mail because:
You are watching all bug changes.

[juk] [Bug 392377] QFSFileEngine::open: No file name specified on startup

2022-11-17 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=392377

Justin Zobel  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #8 from Justin Zobel  ---
Thank you for reporting this issue in KDE software. As it has been a while
since this issue was reported, can we please ask you to see if you can
reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when
replying. Thank you!

-- 
You are receiving this mail because:
You are watching all bug changes.

[juk] [Bug 392377] QFSFileEngine::open: No file name specified on startup

2018-03-28 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=392377

--- Comment #7 from Jarosław Staniek  ---
[Settings]
StartDocked=false

in jukrc fixed it for me! I think the commit will improve things. Thanks.

However if XDG_CURRENT_DESKTOP=KDE is for some reason set under e.g. XFCE (like
in my case, to get KFileDialogs) having StartDocked=true and
DockInSystemTray=true won't put JuK to the tray and thus it's inaccessible. In
this case the patch won't help but this is really different issue. 
If we knew JuK is not getting properly into tray maybe we would show it.

I admit it looks more like a challenge related to hacking the desktop with
XDG_CURRENT_DESKTOP settings than something app developers would care about.

Thanks Michael!

-- 
You are receiving this mail because:
You are watching all bug changes.

[juk] [Bug 392377] QFSFileEngine::open: No file name specified on startup

2018-03-28 Thread Michael Pyne
https://bugs.kde.org/show_bug.cgi?id=392377

Michael Pyne  changed:

   What|Removed |Added

  Latest Commit||1eed47304c46ccba081a8306a3c
   ||95151ff8ffd66

--- Comment #6 from Michael Pyne  ---
Normally I would backport to stable, but in this case the next release is 18.04
so I only applied the fix to master.

If distributions are going to continue to make their own releases based on
Applications/17.12 branch then I have no objection to backporting but it didn't
seem relevant.

The relevant git commit would be
1eed47304c46ccba081a8306a3c95151ff8ffd66

-- 
You are receiving this mail because:
You are watching all bug changes.

[juk] [Bug 392377] QFSFileEngine::open: No file name specified on startup

2018-03-28 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=392377

--- Comment #5 from Jarosław Staniek  ---
Would be nice, Michael. I am using opensuse packages though. I am not sure
software vendors execute autotests for packages prior to release. But I do not
know if some test would catch the problem. 

I'll build JuK later and let you know. Thanks!

If there's a fix I understand you would backport to stable?

-- 
You are receiving this mail because:
You are watching all bug changes.

[juk] [Bug 392377] QFSFileEngine::open: No file name specified on startup

2018-03-27 Thread Michael Pyne
https://bugs.kde.org/show_bug.cgi?id=392377

--- Comment #4 from Michael Pyne  ---
Do you still have this bug with the git-master form of JuK?  Would be nice if I
had fixed it by accident. :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[juk] [Bug 392377] QFSFileEngine::open: No file name specified on startup

2018-03-26 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=392377

--- Comment #3 from Jarosław Staniek  ---
Thanks. "qdbus org.mpris.MediaPlayer2.juk /Player play" plays a song.
Juk is still invisible... :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[juk] [Bug 392377] QFSFileEngine::open: No file name specified on startup

2018-03-26 Thread Michael Pyne
https://bugs.kde.org/show_bug.cgi?id=392377

--- Comment #2 from Michael Pyne  ---
I'm aware of the code getting confused into trying to add a file with an empty
name, that's why JuK warns about this.  Obviously I still haven't figured out
the cause though :(

Hanging on startup is more interesting though.  Does JuK attach to the DBus? 
e.g. does "qdbus org.mpris.MediaPlayer2.juk /Player play" do something
(assuming you already have music loaded)?

If so it may be a bug I just fixed last night, where JuK could be
simultaneously configured to start in docked mode but also configured to not
actually dock in the system tray.  This would make it look like JuK is hung
because it wouldn't show any U/I.

-- 
You are receiving this mail because:
You are watching all bug changes.

[juk] [Bug 392377] QFSFileEngine::open: No file name specified on startup

2018-03-26 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=392377

--- Comment #1 from Jarosław Staniek  ---
(hangs, no reaction)

-- 
You are receiving this mail because:
You are watching all bug changes.