On Sun, 27 Sep 2020 15:18:00 +0200
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
> "rebuild
On Sun, 27 Sep 2020 15:34:07 +0200 (CEST)
local10 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 inst
Sep 27, 2020, 12:58 by b...@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, somet
On Sun, Sep 27, 2020 at 01:58:58PM +0100, Brad Rogers wrote:
> On Sun, 27 Sep 2020 13:25:14 +0200 (CEST)
> local10 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;
>
> I
On Sun, 27 Sep 2020 13:25:14 +0200 (CEST)
local10 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
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 cultu
Sep 27, 2020, 10:06 by to...@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
>
OK, I ran strace and it helped me to under
On Sun, Sep 27, 2020 at 11:36:02AM +0200, local10 wrote:
> Sep 26, 2020, 15:45 by to...@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.
>
>
>
Sep 26, 2020, 15:45 by to...@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
Sep 27, 2020, 04:40 by andreimpope...@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
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
On Sat, Sep 26, 2020 at 03:53:05PM +0200, local10 wrote:
> Sep 26, 2020, 12:52 by sea7k...@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
Sep 26, 2020, 15:36 by marko...@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 exis
On Sat, 26 Sep 2020 14:09:28 +0200 (CEST)
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
Sep 26, 2020, 15:28 by to...@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 ye
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
signature.asc
Description: Digital signature
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 sea7k...@gmail.com:
> > From Root: 1 "ps axu" (no quotes).
> >
> > 2 Determine Task Number of juk.
> >
> > 3 "kill
Sep 26, 2020, 12:52 by sea7k...@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
>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 wrote:
> Hi,
>
> Installed a kernel update and soft-rebooted the system to load the new
> kern
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 res
20 matches
Mail list logo
