Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#1133 - Juk doesn't start
Attached to Project:
Arch Linux
Opened by Christoph Neuroth (delmonico) - Friday, 16 July 2004, 11:18 GMT
Last edited by Dale Blount (dale) - Friday, 16 July 2004, 12:38 GMT
Opened by Christoph Neuroth (delmonico) - Friday, 16 July 2004, 11:18 GMT
Last edited by Dale Blount (dale) - Friday, 16 July 2004, 12:38 GMT
|
DetailsWhen trying to start juk, it gives this error message:
"juk: ERROR: Communication problem with juk, it probably crashed." I use OSS instead of ALSA because I had some problems with this. This has also been posted some days ago in the italian Archlinux forum, but i can't translate the answer: http://www.archlinux.it/post-718.html |
This task depends upon
Running juk through strace shows that it segfaults in a very odd place:
-- strace output --
mkdir("/tmp/mcop-brandan", 0700) = -1 EEXIST (File exists)
lstat64("/tmp/mcop-brandan", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
getuid32() = 1000
open("/tmp/mcop-brandan/secret-cookie", O_RDONLY) = 14
read(14, "fd311589c7535cc2e83f70b4c1db413e", 8192) = 32
close(14) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
rt_sigaction(SIGALRM, {SIG_DFL}, {SIG_DFL}, 8) = 0
alarm(3) = 0
-- end strace output --
I'm basically at my wits end once strace doesn't solve my problems. I can't figure out why closing a filehandle would segfault in the first place, unless there's something else going on that I'm not seeing. I tried rebuilding juk as well.
The Italian forum suggested turning on the arts daemon, or tweaking it to work with OSS emulation. I'm using ALSA, and arts or no arts doesn't seem to make a difference at this point. I think I corrupted something while I was screwing around with the arts configuration.
Hopefully this offers some useful information. I'm going to check the KDE forums now.
Brandan L.
[1] - I actually have gotten it to start with the --norestore option to prevent it from trying to rescan any directories, which I thought could've been the problem. Now it's stopped working with that option as well. I wish I knew how to debug KDE apps...