[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

[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

[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|---

[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

[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

[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

[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

[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.