Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when running Ulubis from image in shell: "Inappropriate ioctl for device" #62

Open
earl-ducaine opened this issue Nov 25, 2020 · 1 comment

Comments

@earl-ducaine
Copy link

earl-ducaine commented Nov 25, 2020

Ubuntu: 20.04 -- Focal Fossa
SBCL: sbcl-2.0.1.debian-linux-x64 (from distribution)

The image created by cat build-ulubis.lisp | sbcl is failing to launch when run from the bash shell. If the project is loaded via ASDF and launched interactively in lisp, e.g.

;; As a local quicklisp project
(ql:quickload :ulubis-sdl)
(ulubis::run-compositor)

It works fine. Below is the backtrace, attached is the .ulubu.lisp init file (the default suggested in the readme)
ulubis.txt

:~/dev/common-lisp/egl/ulubis$ ./ulubis

Oops! Something went wrong with ulubis...we throw ourselves at your mercy! Exiting wih error:
Date/time: 2020-11-24-16:47!
An unhandled error condition has been signalled:
   #<ENOTTY OSICAT-POSIX::%IOCTL-WITH-ARG 25 :ENOTTY "Inappropriate ioctl for device">


Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {10005F8083}>
0: (TRIVIAL-BACKTRACE:PRINT-BACKTRACE-TO-STREAM #<SYNONYM-STREAM :SYMBOL *TERMINAL-IO* {1000023AD3}>)
1: (TRIVIAL-BACKTRACE:PRINT-BACKTRACE #<OSICAT-POSIX:ENOTTY OSICAT-POSIX::%IOCTL-WITH-ARG 25 :ENOTTY "Inappropriate ioctl for device"> :OUTPUT NIL :IF-EXISTS :APPEND :VERBOSE NIL)
2: ((FLET "H0" :IN ULUBIS::INITIALISE) #<OSICAT-POSIX:ENOTTY OSICAT-POSIX::%IOCTL-WITH-ARG 25 :ENOTTY "Inappropriate ioctl for device">)
3: (SB-KERNEL::%SIGNAL #<OSICAT-POSIX:ENOTTY OSICAT-POSIX::%IOCTL-WITH-ARG 25 :ENOTTY "Inappropriate ioctl for device">)
4: (ERROR #<OSICAT-POSIX:ENOTTY OSICAT-POSIX::%IOCTL-WITH-ARG 25 :ENOTTY "Inappropriate ioctl for device">)
5: (OSICAT-POSIX:POSIX-ERROR 25 NIL OSICAT-POSIX::%IOCTL-WITH-ARG)
6: (OSICAT-POSIX::SYSCALL-SIGNAL-POSIX-ERROR #<unused argument> NIL OSICAT-POSIX::%IOCTL-WITH-ARG)
7: (OSICAT-POSIX::%IOCTL-WITH-ARG 4 19268 #.(SB-SYS:INT-SAP #X7F30298C7FF0))
8: ((:METHOD ULUBIS-BACKEND:INITIALISE-BACKEND (ULUBIS-BACKEND:BACKEND T T T)) #<ULUBIS-BACKEND:BACKEND {10047A3363}> 1920 1080 NIL) [fast-method]
9: (ULUBIS::INITIALISE)
10: ((FLET SB-UNIX::BODY :IN SAVE-LISP-AND-DIE))
11: ((FLET "WITHOUT-INTERRUPTS-BODY-14" :IN SAVE-LISP-AND-DIE))
12: ((LABELS SB-IMPL::RESTART-LISP :IN SAVE-LISP-AND-DIE))


debugger invoked on a SB-KERNEL:CASE-FAILURE in thread
#<THREAD "main thread" RUNNING {10005F8083}>:
  :SHUTTING-DOWN fell through ECASE expression.
  Wanted one of (:SUSPENDED :ACTIVE).

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT] Exit from the current thread.

(CEPL.LIFECYCLE::FROM-UNITIALIZED :SHUTTING-DOWN)
   source: (ECASE TARGET-STATE
             (:SUSPENDED (TO-SUSPENDED TARGET-STATE))
             (:ACTIVE (TO-SUSPENDED TARGET-STATE)))
0] 

@malcolmstill
Copy link
Owner

I don't suppose you're using an nvidia card?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants