Quote:
Originally Posted by chipf0rk
Right. I let KUAL output its logs and found this:
Code:
/tmp/klauncher_background-17253.sh: line 2: ./bin/usbnet.sh: Permission denied
/tmp/klauncher_background-17254.sh: line 2: ./bin/usbnet.sh: Permission denied
/tmp/klauncher_background-17256.sh: line 2: /mnt/us/extensions/kindlenotes/bin/kindlenotes.sh: Permission denied
/tmp/klauncher_background-17258.sh: line 2: /mnt/us/extensions/kindlenotes/bin/kindlenotes.sh: Permission denied
/tmp/klauncher_background-17260.sh: line 2: /mnt/us/extensions/kindlemenu/bin/kindlemenu.sh: Permission denied
/tmp/klauncher_background-17262.sh: line 2: /mnt/us/extensions/kindlemenu/bin/shortcut.sh: Permission denied
/tmp/klauncher_background-17266.sh: line 2: bin/kindlegallery.sh: Permission denied
/tmp/klauncher_background-17267.sh: line 2: bin/kindlegallery.sh: Permission denied
/tmp/klauncher_background-17268.sh: line 2: bin/explorer.sh: Permission denied
/tmp/klauncher_background-17269.sh: line 2: ./gargoyle.sh: Permission denied
Welp, looks like it's not a problem on KUAL's nor your side, but I'm unsure whether there should be a thread opened for this. I suppose it's a permission problem with the executable flag missing, and that might happen because I'm copying the files on the device over USB- from Windows. If you've never heard of that problem, I'll gladly move this somewhere else, but is this known to happen and easily fixable? |
These all seem to be related to the user partition being mounted noexec. The easiest solution is to prefix the commands with /bin/sh. Not sure whether this should be handled in KUAL itself, or in each extension config...
PS: Moved to correct thread.