Closed epitron closed 9 years ago
Yes. It seems like Weston didn't load nuclear. Do you have a different shell module specified in weston.ini?
Nope! I tried it with and without a weston.ini file - same problem.
Which version of weston are you developing against?
I'm running into this issue as well. An ideas how to fix it?
Can you paste your generated 'orbital' script?
#!/bin/sh
socket=0
tmppath="$XDG_CACHE_HOME"
if [ -z "$tmppath" ]; then
tmppath="$HOME/.cache"
fi
tmppath="$tmppath/orbital"
mkdir -p $tmppath >/dev/null
configpath="$XDG_CONFIG_HOME"
if [ -z "$configpath" ]; then
configpath="$HOME/.config"
fi
configpath="$configpath/orbital"
mkdir -p $configpath > /dev/null
while getopts S:v name
do
case $name in
S) if [ $OPTARG -eq $OPTARG 2> /dev/null ]; then
socket="$OPTARG"
else
echo "Invalid socket number. Must be an integer."
exit 1
fi;;
v) echo "Version: 0.1"
exit 0;;
?) printf "Usage: %s: [-Svalue]\n" $0
exit 2;;
esac
done
logfile="$tmppath/orbital-$socket.log"
out="$tmppath/orbital-$socket.out"
err="$tmppath/orbital-$socket.err"
function watch() {
IFS=''
while read a; do
echo "$a"
echo "$2$a" >>$logfile
done < "$1"
}
rm $logfile $out $err > /dev/null 2>&1
mkfifo $out $err
trap 'rm "$out" "$err"' EXIT
exec 4<>"$out"
exec 5<>"$err"
(watch "$out" "stdout: " >&1) &
pidout=$!
(watch "$err" "stderr: " >&2) &
piderr=$!
exec 1>&4
exec 2>&5
plugin="/usr/lib/nuclear-shell/nuclear-desktop-shell.so"
if [ "0.1" == "0.0.1" ]; then
plugin="/usr/lib/nuclear-shell/nuclear-shell.so"
fi
args="--shell=$plugin --nuclear-client=/usr/libexec/startorbital --session-file=$configpath/session -Swayland-$socket"
if [ -z "$DBUS_SESSION_BUS_ADDRESS" ] && type dbus-launch >/dev/null; then
eval `dbus-launch --sh-syntax`
fi
export QT_QPA_PLATFORM="wayland"
export XDG_CURRENT_DESKTOP="orbital"
if [ -z "$DISPLAY" ]; then
stdbuf -oL -eL weston-launch -- $args
else
stdbuf -oL -eL weston $args
fi
if [[ $DBUS_SESSION_BUS_PID ]]; then
kill $DBUS_SESSION_BUS_PID
fi
And is the plugin really there?
Yes:
$ ls /usr/lib/nuclear-shell/nuclear-desktop-shell.so
/usr/lib/nuclear-shell/nuclear-desktop-shell.so
What happens if weston encounters an error while loading a shell extension? Does it silently skip loading that module and continue its startup process? Judging by its console output, weston looks like it's not even trying to load the module.
It looks like I am having this issue too. It used to work, I think it might be some change in Weston that makes it read all arguments before loading any modules if I was to guess?
This problem is due to following commit in mailing list. http://lists.freedesktop.org/archives/wayland-devel/2012-July/004616.html
I remove the argument check and run orbital fine :). (with weston 1.6)
That commit is really odd, it surely isn't the issue. I still don't know what the problem was, anyway now orbital has a different architecture so this bug doesn't happen anymore.
Hi there!
I just built orbital and all of its dependencies from the AUR (weston-git, wayland-git, nuclear-git, orbital-git), and it's not able to start up when I run the
orbital
script:Those two unhandled options (
--nuclear-client
and--session-file
) don't seem to be part of weston. Are they supposed to be added bynuclear-desktop-shell.so
?