Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #227392 > unrolled thread
| Started by | local10 <local10@tutanota.com> |
|---|---|
| First post | 2020-09-26 14:10 +0200 |
| Last post | 2020-09-27 09:30 +0200 |
| Articles | 20 — 8 participants |
Back to article view | Back to linux.debian.user
Juk hangs after launch local10 <local10@tutanota.com> - 2020-09-26 14:10 +0200
Re: Juk hangs after launch Kenneth Parker <sea7kenp@gmail.com> - 2020-09-26 15:00 +0200
Re: Juk hangs after launch local10 <local10@tutanota.com> - 2020-09-26 16:00 +0200
Re: Juk hangs after launch Hans <hans.ullrich@loop.de> - 2020-09-26 16:40 +0200
Re: Juk hangs after launch <tomas@tuxteam.de> - 2020-09-26 17:50 +0200
Re: Juk hangs after launch local10 <local10@tutanota.com> - 2020-09-27 11:40 +0200
Re: Juk hangs after launch <tomas@tuxteam.de> - 2020-09-27 12:10 +0200
[SOLVED] Re: Juk hangs after launch local10 <local10@tutanota.com> - 2020-09-27 13:30 +0200
Re: [SOLVED] Re: Juk hangs after launch <tomas@tuxteam.de> - 2020-09-27 14:30 +0200
Re: [SOLVED] Re: Juk hangs after launch Brad Rogers <brad@fineby.me.uk> - 2020-09-27 15:00 +0200
Re: [SOLVED] Re: Juk hangs after launch <tomas@tuxteam.de> - 2020-09-27 15:20 +0200
Re: [SOLVED] Re: Juk hangs after launch Charles Curley <charlescurley@charlescurley.com> - 2020-09-27 19:30 +0200
Re: [SOLVED] Re: Juk hangs after launch local10 <local10@tutanota.com> - 2020-09-27 15:40 +0200
Re: [SOLVED] Re: Juk hangs after launch Brad Rogers <brad@fineby.me.uk> - 2020-09-27 16:40 +0200
Re: Juk hangs after launch <tomas@tuxteam.de> - 2020-09-26 17:30 +0200
Re: Juk hangs after launch local10 <local10@tutanota.com> - 2020-09-26 17:40 +0200
Re: Juk hangs after launch Marko Randjelovic <markoran@eunet.rs> - 2020-09-26 17:40 +0200
Re: Juk hangs after launch local10 <local10@tutanota.com> - 2020-09-26 17:50 +0200
Re: Juk hangs after launch Andrei POPESCU <andreimpopescu@gmail.com> - 2020-09-27 06:50 +0200
Re: Juk hangs after launch local10 <local10@tutanota.com> - 2020-09-27 09:30 +0200
| From | local10 <local10@tutanota.com> |
|---|---|
| Date | 2020-09-26 14:10 +0200 |
| Subject | Juk hangs after launch |
| Message-ID | <AThbA-4Pg-5@gated-at.bofh.it> |
Hi, Installed a kernel update and soft-rebooted the system to load the new kernel while juk was playing. After the system came back, juk cannot be launched, it just hangs and cannot even show its initial window properly. When I try to close the juk window, KDE says "Application "juk" is not responding" and offers to terminate juk. It looks like something got screwed up with juk configuration while the system was being shut down for reboot. I don't mind losing old juk config files and starting anew, just can't find them. Checked ~/.config, ~/.cache, ~/.kde/share but there appear to be no juk config files with the exception of ~/.config/jukrc . Any ideas? Thanks # echo "This is a Debin 10 Buster PC"; uname -a This is a Debin 10 Buster PC Linux tst 4.19.0-11-amd64 #1 SMP Debian 4.19.146-1 (2020-09-17) x86_64 GNU/Linux # aptitude show juk Package: juk Version: 4:18.08.1-1 State: installed
[toc] | [next] | [standalone]
| From | Kenneth Parker <sea7kenp@gmail.com> |
|---|---|
| Date | 2020-09-26 15:00 +0200 |
| Message-ID | <AThXY-55b-3@gated-at.bofh.it> |
| In reply to | #227392 |
[Multipart message — attachments visible in raw view] — view raw
>From Root: 1 "ps axu" (no quotes). 2 Determine Task Number of juk. 3 "kill -9 ____" where ____ is that task number. -9 means *really* Kill it! Kenneth Parker On Sat, Sep 26, 2020, 8:09 AM local10 <local10@tutanota.com> wrote: > Hi, > > Installed a kernel update and soft-rebooted the system to load the new > kernel while juk was playing. After the system came back, juk cannot be > launched, it just hangs and cannot even show its initial window properly. > When I try to close the juk window, KDE says "Application "juk" is not > responding" and offers to terminate juk. > > It looks like something got screwed up with juk configuration while the > system was being shut down for reboot. I don't mind losing old juk config > files and starting anew, just can't find them. Checked ~/.config, ~/.cache, > ~/.kde/share but there appear to be no juk config files with the exception > of ~/.config/jukrc . > > Any ideas? Thanks > > # echo "This is a Debin 10 Buster PC"; uname -a > This is a Debin 10 Buster PC > Linux tst 4.19.0-11-amd64 #1 SMP Debian 4.19.146-1 (2020-09-17) x86_64 > GNU/Linux > > # aptitude show juk > Package: juk > Version: 4:18.08.1-1 > State: installed > > > > >
[toc] | [prev] | [next] | [standalone]
| From | local10 <local10@tutanota.com> |
|---|---|
| Date | 2020-09-26 16:00 +0200 |
| Message-ID | <ATiU1-5DL-5@gated-at.bofh.it> |
| In reply to | #227394 |
Sep 26, 2020, 12:52 by sea7kenp@gmail.com: > From Root: 1 "ps axu" (no quotes). > > 2 Determine Task Number of juk. > > 3 "kill -9 ____" where ____ is that task number. > > -9 means *really* Kill it! > That did not help. After running "kill -9 $jukProcessNumberHere" and then restarting juk the issue is still there: juk hangs and cannot even show its window properly. Thanks
[toc] | [prev] | [next] | [standalone]
| From | Hans <hans.ullrich@loop.de> |
|---|---|
| Date | 2020-09-26 16:40 +0200 |
| Message-ID | <ATjwJ-664-1@gated-at.bofh.it> |
| In reply to | #227396 |
Am Samstag, 26. September 2020, 15:53:05 CEST schrieb local10: Try killing by name, sometimes this works: killall your_juk_process_name Good luck! Hans > Sep 26, 2020, 12:52 by sea7kenp@gmail.com: > > From Root: 1 "ps axu" (no quotes). > > > > 2 Determine Task Number of juk. > > > > 3 "kill -9 ____" where ____ is that task number. > > > > -9 means *really* Kill it! > > That did not help. After running "kill -9 $jukProcessNumberHere" and then > restarting juk the issue is still there: juk hangs and cannot even show its > window properly. > > Thanks
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2020-09-26 17:50 +0200 |
| Message-ID | <ATkCu-6HL-13@gated-at.bofh.it> |
| In reply to | #227396 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, Sep 26, 2020 at 03:53:05PM +0200, local10 wrote: > Sep 26, 2020, 12:52 by sea7kenp@gmail.com: > > > From Root: 1 "ps axu" (no quotes). > > > > 2 Determine Task Number of juk. > > > > 3 "kill -9 ____" where ____ is that task number. > > > > -9 means *really* Kill it! > > > > That did not help. After running "kill -9 $jukProcessNumberHere" and then restarting juk the issue is still there: juk hangs and cannot even show its window properly. Hrm. As I said, barring some magic, Juk should be gone after reboot anyway, so killing won't help. Did you actually /see/ a running juk process as per instruction (1) above? BTW: no need to be root for that. Actually better *not* be root. Other critique of those instructions: juk is an user application, so no need to be root for (2) .. (3) either; Don't kill -9 right away, first try plain kill (with no number), that is equivalen to kill -15 (SIGTERM). This gives the application the chance to clean up after itself (possibly removing a lock file). ONLY if the application doesn't go away (check with ps) you should resort to kill -9. Possibly the application has left behind a lock file. This might live somewhere in /run. You might try to start the application from the command line, perhaps there are error messages giving you some hints. Cheers - t
[toc] | [prev] | [next] | [standalone]
| From | local10 <local10@tutanota.com> |
|---|---|
| Date | 2020-09-27 11:40 +0200 |
| Message-ID | <ATBjX-8j9-1@gated-at.bofh.it> |
| In reply to | #227402 |
Sep 26, 2020, 15:45 by tomas@tuxteam.de: > Possibly the application has left behind a lock file. This might > live somewhere in /run. > Didn't find anything related to juk in /run, /var/run or /var/lock directories. > You might try to start the application from the command line, > perhaps there are error messages giving you some hints. > Starting (and then killing) juk from the command line produces the following output, regretfully it doesn't give much clues as to what I need to do to fix it: $ juk org.kde.juk: Unable to setup to load cache... perhaps it doesn't exist? Killed $ ls -la ~/.cache/j* ls: cannot access '/home/luser/.cache/j*': No such file or directory Regards,
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2020-09-27 12:10 +0200 |
| Message-ID | <ATBN0-gq-5@gated-at.bofh.it> |
| In reply to | #227409 |
[Multipart message — attachments visible in raw view] — view raw
On Sun, Sep 27, 2020 at 11:36:02AM +0200, local10 wrote: > Sep 26, 2020, 15:45 by tomas@tuxteam.de: > > > Possibly the application has left behind a lock file. This might > > live somewhere in /run. > > > > Didn't find anything related to juk in /run, /var/run or /var/lock directories. > > > > You might try to start the application from the command line, > > perhaps there are error messages giving you some hints. > > > > Starting (and then killing) juk from the command line produces the following output, regretfully it doesn't give much clues as to what I need to do to fix it: > > $ juk > org.kde.juk: Unable to setup to load cache... perhaps it doesn't exist? > Killed Ugh. It could tell us where it looks for its cache, couldn't it? OK. If you don't fear some text output, you could run it under strace (in Debian package strace), like so: strace -f -o /tmp/trace <your-program-here> You'll find a text file /tmp/trace (or whatever path you chose for the -o ooption) with all the system calls your program tries. Of interest are those failing (especially things like open or stat returning an ENOENT or similar) near the trace's bottom. Option -f is to "follow" your program when it forks -- trace file entries will be prepended by the process ID. You may share snippets of that trace here when in doubt (look out for possibly sensitive information -- in this case the risk seems pretty low, though). There should be a special hell for app developers issuing error messages like the above. Grrr. Cheers - t
[toc] | [prev] | [next] | [standalone]
| From | local10 <local10@tutanota.com> |
|---|---|
| Date | 2020-09-27 13:30 +0200 |
| Subject | [SOLVED] Re: Juk hangs after launch |
| Message-ID | <ATD2p-UX-1@gated-at.bofh.it> |
| In reply to | #227410 |
Sep 27, 2020, 10:06 by tomas@tuxteam.de: > Ugh. It could tell us where it looks for its cache, couldn't > it? > > OK. If you don't fear some text output, you could run it under > strace (in Debian package strace), like so: > > strace -f -o /tmp/trace <your-program-here> > OK, I ran strace and it helped me to understand what was happening: juk wasn't hanging but instead it was rebuilding the playlist it was playing when the system was shut down. Under a false assumption that juk was hanging (it really looked like that) I was killing juk too early, not allowing it to rebuild the playlist. So the solution in my case was easy: I just allowed juk to run for 5 minutes, that was enough time for it to rebuild the playlist and show its window properly. It surely looks like juk developers could've handled the situation in a better way but whatever... it works now. Thanks to everyone who responded.
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2020-09-27 14:30 +0200 |
| Subject | Re: [SOLVED] Re: Juk hangs after launch |
| Message-ID | <ATDYt-1tk-5@gated-at.bofh.it> |
| In reply to | #227412 |
[Multipart message — attachments visible in raw view] — view raw
On Sun, Sep 27, 2020 at 01:25:14PM +0200, local10 wrote: [...] > OK, I ran strace and it helped me to understand what was happening [...] Glad it helped :-) Strace can be a bit intimidating, but can be invaluable in such cases. The next-heavier armory would be GDB. But some error message culture wouldn't hurt. This one was killed by our current GUI culture, which tends to treat users as idiots (thus don't giving them a chance to learn!). Thinking about an alternative GUI culture is left as an exercise to the reader :-) Cheers - t
[toc] | [prev] | [next] | [standalone]
| From | Brad Rogers <brad@fineby.me.uk> |
|---|---|
| Date | 2020-09-27 15:00 +0200 |
| Subject | Re: [SOLVED] Re: Juk hangs after launch |
| Message-ID | <ATErv-1Dq-1@gated-at.bofh.it> |
| In reply to | #227412 |
[Multipart message — attachments visible in raw view] — view raw
On Sun, 27 Sep 2020 13:25:14 +0200 (CEST)
local10 <local10@tutanota.com> wrote:
Hello local10,
>like juk developers could've handled the situation in a better way
>but whatever... it
Depends how you went about your system reboot;
If you just hit the front panel reset button, there's not really a lot
any software can do to help. If, however, you used your DE's reboot
or other 'clean' (IOW, OS friendly) command then yes, something probably
needs a bug report.
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
Save me from myself
Prisoners - Judgement Centre
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2020-09-27 15:20 +0200 |
| Subject | Re: [SOLVED] Re: Juk hangs after launch |
| Message-ID | <ATEKR-1Zf-7@gated-at.bofh.it> |
| In reply to | #227415 |
[Multipart message — attachments visible in raw view] — view raw
On Sun, Sep 27, 2020 at 01:58:58PM +0100, Brad Rogers wrote: > On Sun, 27 Sep 2020 13:25:14 +0200 (CEST) > local10 <local10@tutanota.com> wrote: > > Hello local10, > > >like juk developers could've handled the situation in a better way > >but whatever... it > > Depends how you went about your system reboot; > > If you just hit the front panel reset button, there's not really a lot > any software can do to help. Oh, yes. A better error message (in this case, it turned out juk decided to rebuild its cache, which takes time -- so a message "rebuilding cache, please wait") instead of disappearing would be the right thing to do. Cheers - t
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2020-09-27 19:30 +0200 |
| Subject | Re: [SOLVED] Re: Juk hangs after launch |
| Message-ID | <ATIEN-4jk-1@gated-at.bofh.it> |
| In reply to | #227417 |
[Multipart message — attachments visible in raw view] — view raw
On Sun, 27 Sep 2020 15:18:00 +0200 <tomas@tuxteam.de> wrote: > > If you just hit the front panel reset button, there's not really a > > lot any software can do to help. > > Oh, yes. A better error message (in this case, it turned out juk > decided to rebuild its cache, which takes time -- so a message > "rebuilding cache, please wait") instead of disappearing would be the > right thing to do. If rebuilding the cache takes that long, I suggest that rebuilding should also be interruptible. That is, on being told to shut down, the program should save its state in such a way that the next time the user runs it, it can pick up where it left off. With an announcement! As Brad Rogers wrote, that would be useless in the event of hitting the physical reset button. That's why hitting the reset button is a last resort. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | local10 <local10@tutanota.com> |
|---|---|
| Date | 2020-09-27 15:40 +0200 |
| Subject | Re: [SOLVED] Re: Juk hangs after launch |
| Message-ID | <ATF4d-25i-5@gated-at.bofh.it> |
| In reply to | #227415 |
Sep 27, 2020, 12:58 by brad@fineby.me.uk: > Depends how you went about your system reboot; > > If you just hit the front panel reset button, there's not really a lot > any software can do to help. If, however, you used your DE's reboot > or other 'clean' (IOW, OS friendly) command then yes, something probably > needs a bug report. > It was a soft-reboot: KDE menu > Power/Session > Reboot Regards,
[toc] | [prev] | [next] | [standalone]
| From | Brad Rogers <brad@fineby.me.uk> |
|---|---|
| Date | 2020-09-27 16:40 +0200 |
| Subject | Re: [SOLVED] Re: Juk hangs after launch |
| Message-ID | <ATG0h-2DX-1@gated-at.bofh.it> |
| In reply to | #227419 |
[Multipart message — attachments visible in raw view] — view raw
On Sun, 27 Sep 2020 15:34:07 +0200 (CEST)
local10 <local10@tutanota.com> wrote:
Hello local10,
>It was a soft-reboot: KDE menu > Power/Session > Reboot
I couldn't remember what you said in original post, nor could I find
a copy locally, so thanks for reminding me.
I think a bug should be reported. In the first instance, against JuK.
If that's the wrong place, I'm sure they'll let you know, or forward to
the correct place themselves.
Good luck.
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
No rotten apple's gonna spoil my fun
Get The Funk Out - Extreme
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2020-09-26 17:30 +0200 |
| Message-ID | <ATkj7-6Bv-1@gated-at.bofh.it> |
| In reply to | #227394 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, Sep 26, 2020 at 08:52:54AM -0400, Kenneth Parker wrote: > >From Root: 1 "ps axu" (no quotes). > > 2 Determine Task Number of juk. It should be gone. The system was rebooted, after all. Cheers - t
[toc] | [prev] | [next] | [standalone]
| From | local10 <local10@tutanota.com> |
|---|---|
| Date | 2020-09-26 17:40 +0200 |
| Message-ID | <ATksN-6Ep-1@gated-at.bofh.it> |
| In reply to | #227399 |
Sep 26, 2020, 15:28 by tomas@tuxteam.de: > On Sat, Sep 26, 2020 at 08:52:54AM -0400, Kenneth Parker wrote: > >> >From Root: 1 "ps axu" (no quotes). >> >> 2 Determine Task Number of juk. >> > > It should be gone. The system was rebooted, after all. > Correct. There are no juk processes running yet the issue is still present: $ ps -A u | grep -i juk luser 5909 0.0 0.0 6048 892 pts/2 S+ 11:31 0:00 grep -i juk
[toc] | [prev] | [next] | [standalone]
| From | Marko Randjelovic <markoran@eunet.rs> |
|---|---|
| Date | 2020-09-26 17:40 +0200 |
| Message-ID | <ATksO-6Ep-3@gated-at.bofh.it> |
| In reply to | #227392 |
On Sat, 26 Sep 2020 14:09:28 +0200 (CEST) local10 <local10@tutanota.com> wrote: > Hi, > > Installed a kernel update and soft-rebooted the system to load the new kernel while juk was playing. After the system came back, juk cannot be launched, it just hangs and cannot even show its initial window properly. When I try to close the juk window, KDE says "Application "juk" is not responding" and offers to terminate juk. > > It looks like something got screwed up with juk configuration while the system was being shut down for reboot. I don't mind losing old juk config files and starting anew, just can't find them. Checked ~/.config, ~/.cache, ~/.kde/share but there appear to be no juk config files with the exception of ~/.config/jukrc . > > Any ideas? Thanks > > # echo "This is a Debin 10 Buster PC"; uname -a > This is a Debin 10 Buster PC > Linux tst 4.19.0-11-amd64 #1 SMP Debian 4.19.146-1 (2020-09-17) x86_64 GNU/Linux > > # aptitude show juk > Package: juk > Version: 4:18.08.1-1 > State: installed Hi local10, Launch juk from terminal to be able to see its debugging messages. Also you can reboot with the old kernel to see if juk works, maybe your new kernel introduced some bug. Regards, Marko
[toc] | [prev] | [next] | [standalone]
| From | local10 <local10@tutanota.com> |
|---|---|
| Date | 2020-09-26 17:50 +0200 |
| Message-ID | <ATkCu-6HL-15@gated-at.bofh.it> |
| In reply to | #227400 |
Sep 26, 2020, 15:36 by markoran@eunet.rs: > Launch juk from terminal to be able to see its debugging messages. Also > you can reboot with the old kernel to see if juk works, maybe your new > kernel introduced some bug. > $ juk org.kde.juk: Unable to setup to load cache... perhaps it doesn't exist? Killed The issue appears to be a juk issue not a system one. I'm currently using vlc to play mp3s, vlc is working fine. Regards,
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-09-27 06:50 +0200 |
| Message-ID | <ATwNk-5Bn-1@gated-at.bofh.it> |
| In reply to | #227392 |
[Multipart message — attachments visible in raw view] — view raw
On Sb, 26 sep 20, 14:09:28, local10 wrote: > Hi, > > Installed a kernel update and soft-rebooted the system to load the new > kernel while juk was playing. After the system came back, juk cannot > be launched, it just hangs and cannot even show its initial window > properly. When I try to close the juk window, KDE says "Application > "juk" is not responding" and offers to terminate juk. > > It looks like something got screwed up with juk configuration while > the system was being shut down for reboot. I don't mind losing old juk > config files and starting anew, just can't find them. Checked > ~/.config, ~/.cache, ~/.kde/share but there appear to be no juk config > files with the exception of ~/.config/jukrc . > > Any ideas? Thanks Does it work for another / new user on the same computer? Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | local10 <local10@tutanota.com> |
|---|---|
| Date | 2020-09-27 09:30 +0200 |
| Message-ID | <ATzi9-79Z-3@gated-at.bofh.it> |
| In reply to | #227406 |
Sep 27, 2020, 04:40 by andreimpopescu@gmail.com: > Does it work for another / new user on the same computer? > Yes, for a new user on the same PC it works fine. Thanks
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web