"swc-launch -- velox" locks up computer

a6ec2a79 · 2015-01-15 16:28:43

I installed velox-wl-git from AUR and when I try to launch it my computer locks up. I can still shutdown without holding the power button from 5 seconds, but I can't switch to another TTY or kill the process. Has anyone encountered this?

nomorewindows · 2015-01-15 17:36:12

The power button shuts down during any lockup if held for 4 seconds. Do you have sshd running, and can you hit it from there?

Trilby · 2015-01-15 17:39:04

I haven't done much with wayland yet - so unfortunately I haven't tried this at all, but the wiki says to run "swc-launch velox", but your title says you used "swc-launch -- velox". Is there documentation for the latter? Have you tried the former?

a6ec2a79 · 2015-01-15 21:19:54

nomorewindows: Sorry, I was typing on a mobile device. I meant to say that I hold it long enough so systemd takes over and shuts it down instead of going to sleep if I had just pressed it quickly. I don't have hold the power button down that long. (That being said, I've had one or two lockups where holding the power button wouldn't even power it off and had to yank the battery)

The suggestion to SSH into the machine worked, but I can't get much info on it. journalctl just says that I log in and it opens a new session on TTY for me but doesn't print any errors. When I ran:

swc-launch velox 2> ~/velox.log

it only prints this:

Running on /dev/tty2
[swc:libswc/drm.c:160] DEBUG: /dev/dri/card0 is the primary GPU
# find_driver: Trying DRM driver `intel'
Using config at '/etc/velox.conf'
glamor: EGL version 1.4 (DRI2):
Server exited with status 0
(EE)Restoring VT to original state
 
Fatal server error:
(EE) failed to dispatch Wayland events: Broken pipe
(EE)

Right around "Server exited..." is where I ran

killall swc-launch

from the ssh session.

Trilby: See above. I tried without the double dash, but the author of swc uses it in a comment for an issue on github. Link:

https://github.com/michaelforney/swc/issues/8

Steef435 · 2015-01-15 23:02:41

I remember I also had trouble with velox when I wanted to try it out some time before.

Have you tried running the small example included with swc?

nomorewindows · 2015-01-15 23:18:36

You have to remember that what happens over an ssh connection may be trying to use the remote machines hardware in some cases. You want to use the redirection before everything goes crash and then retrieve the log from ssh just to be sure.

a6ec2a79 · 2015-01-16 03:07:54

I can't find the wm executable, and after running

make && make install

in the swc file with a PREFIX in my home dir, I still can't find a wm binary. If someone would tell me how to compile it I'll give it a shot (I don't usually do much more than edit Makefiles to change the PREFIX when I wade into hand-compiling territory).

edit and I tried running gcc on the wm.c file, but I'm getting a bunch of errors about undefined references, I'm assuming I'm doing something wrong here.

Last edited by a6ec2a79 (2015-01-16 03:12:22)

thiagowfx · 2015-01-16 03:25:02

I just downloaded the PKGBUILD of velox-wl-git from the AUR and compiled it (after doing the same for its dependencies). The name of the final executable is simply "velox". Look at this output:

thiago@archpad ~/aur/velox-wl-git % tar tvf velox-wl-git-r400.4e549c6-1-x86_64.pkg.tar.xz                                                                           :(
-rw-r--r-- root/root       720 2015-01-16 01:21 .PKGINFO
-rw-r--r-- root/root       671 2015-01-16 01:21 .MTREE
drwxr-xr-x root/root         0 2015-01-16 01:21 etc/
-rw-r--r-- root/root      3110 2015-01-16 01:21 etc/velox.conf
drwxr-xr-x root/root         0 2015-01-16 01:21 usr/
drwxr-xr-x root/root         0 2015-01-16 01:21 usr/share/
drwxr-xr-x root/root         0 2015-01-16 01:21 usr/libexec/
drwxr-xr-x root/root         0 2015-01-16 01:21 usr/bin/
drwxr-xr-x root/root         0 2015-01-16 01:21 usr/lib/
drwxr-xr-x root/root         0 2015-01-16 01:21 usr/lib/pkgconfig/
-rw-r--r-- root/root        95 2015-01-16 01:21 usr/lib/pkgconfig/velox.pc
-rwxr-xr-x root/root     37152 2015-01-16 01:21 usr/bin/velox
drwxr-xr-x root/root         0 2015-01-16 01:21 usr/libexec/velox/
-rwxr-xr-x root/root     19104 2015-01-16 01:21 usr/libexec/velox/status_bar
drwxr-xr-x root/root         0 2015-01-16 01:21 usr/share/velox/
-rw-r--r-- root/root       976 2015-01-16 01:21 usr/share/velox/velox.xml

Last edited by thiagowfx (2015-01-16 03:25:19)

a6ec2a79 · 2015-01-16 03:28:08

I have velox compiled, I was talking about example/wm.c in swc's git repo. If I can get wm running with swc, then we know the issue has something to do with velox.

Last edited by a6ec2a79 (2015-01-16 03:28:23)

thiagowfx · 2015-01-16 04:04:35

Okay, try

gcc -lm -lswc -lwld -lwayland-client -lwayland-server -lpthread wm.c -o wm

then. Source: trial and error.

a6ec2a79 · 2015-01-16 04:28:47

I compiled wm.c from commit ef95f2fe with zero errors using the gcc options from above. After running

swc-launch ./wm 2> wm.log

, I lost keyboard input (no switching TTY, no ctrl-C). I ssh'd into the machine, killall'd swc-launch and here I am posting the contents of wm.log:

Running on /dev/tty2
[swc:libswc/drm.c:160] DEBUG: /dev/dri/card0 is the primary GPU
# find_driver: Trying DRM driver `intel'
glamor: EGL version 1.4 (DRI2):
Server exited with status 0
(EE)Restoring VT to original state
 
Fatal server error:
(EE) failed to dispatch Wayland events: Broken pipe
(EE)

not sure if I should file a bug report or not. Could I be missing anything? I got swc and velox-wl from AUR, so everything should be there...

thiagowfx · 2015-01-17 14:18:44

I tried some tests yesterday, and they all failed. At least I discovered something: you can use

swc-launch -t /dev/tty3 -- /usr/bin/velox

for example, to launch velox in another tty. Then, just switch to it (Ctrl+Alt+F3, as you probably know). Why? Because this way your computer won't lock up. When I tried to launch velox (--and the compiled wm example) in the same tty I was, my computer also locked up -- the only available solution to this was to power it off directly too. By using this method you can do Ctrl-C and test swc or velox several times.

FYI, launching velox this way produced a black screen with a pointer. I could move the pointer with my touchpad, but it hadn't much to do (no bars, nothing to click on). I tried pressing Mod+Shift+Enter to spawn a terminal but nothing happened -- maybe the keyboard wasn't detected, but I don't know how to troubleshoot that.

bstaletic · 2015-01-17 14:42:00

For me

swc-launch -- velox

worked. I got a black screen and a pointer ( which I could move), but none of the keybindings worked. I don't think keyboard is the problem as Ctrl-Alt-F[1-6] works. Even it's dmenu wouldn't open.

blackout23 · 2015-01-17 15:27:56

Might be related to this? https://github.com/michaelforney/swc/issues/16

That's the issue I have on my laptop with nouveau graphics.

Endres · 2015-03-01 11:13:09

Same issue here using intel graphics.
When launching using

swc-launch velox

no further keys are recognized and when launching using

swc-launch -t /dev/tty3 velox

only a black screen (w/ mouse cursor) is produced.
swc generally works using weston or loliwm.

Last edited by Endres (2015-03-01 11:13:32)

W.F.Cody · 2015-03-09 09:48:59

Thanks for the swc-launch -t /dev/tty3 -- velox idea. This works great.

Are you guys able to start dmenu_run-wl using mod+r? For me it does not start, but if I run it via st-wl (which starts with mod+shift+enter) I can get the dmenu.

Also, do you know a way to auto-start /usr/lib/velox/status_bar in velox.conf?
(even better: if there is a way to assign a quick key to start/stop the status bar)

I like the dwm-like look when the status bar is there (it also helps me remember on whic tag I am and I can quickly see the time while at my computer).

I would love to get some more documentation or examples of velox.conf

EDIT:
got the status_bar on/off switch working
....

action spawn_status     spawn   /usr/lib/velox/status_bar
action spawn_unstatus   spawn   killall status_bar

....

key s           mod                 spawn_status
key s           mod,shift           spawn_unstatus

....

Last edited by W.F.Cody (2015-03-09 10:10:55)

Arch Linux

#1 2015-01-15 16:28:43

"swc-launch -- velox" locks up computer

#2 2015-01-15 17:36:12

Re: "swc-launch -- velox" locks up computer

#3 2015-01-15 17:39:04

Re: "swc-launch -- velox" locks up computer

#4 2015-01-15 21:19:54

Re: "swc-launch -- velox" locks up computer

#5 2015-01-15 23:02:41

Re: "swc-launch -- velox" locks up computer

#6 2015-01-15 23:18:36

Re: "swc-launch -- velox" locks up computer

#7 2015-01-16 03:07:54

Re: "swc-launch -- velox" locks up computer

#8 2015-01-16 03:25:02

Re: "swc-launch -- velox" locks up computer

#9 2015-01-16 03:28:08

Re: "swc-launch -- velox" locks up computer

#10 2015-01-16 04:04:35

Re: "swc-launch -- velox" locks up computer

#11 2015-01-16 04:28:47

Re: "swc-launch -- velox" locks up computer

#12 2015-01-17 14:18:44

Re: "swc-launch -- velox" locks up computer

#13 2015-01-17 14:42:00

Re: "swc-launch -- velox" locks up computer

#14 2015-01-17 15:27:56

Re: "swc-launch -- velox" locks up computer

#15 2015-03-01 11:13:09

Re: "swc-launch -- velox" locks up computer

#16 2015-03-09 09:48:59

Re: "swc-launch -- velox" locks up computer

Board footer