[BUG] Orca Seg Faults when renderD128 is Passed In #13
Comments
|
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
|
For additional info, rolling back to v2.1.1-ls51 resolved the issue for me |
+1 Same issue here, though rolling back to v2.1.1-ls51 did not fix it for me. Details2024-10-28 01:46:46,196 [INFO] websocket 33: got client connection from 172.86.12.11 2024-10-28 01:46:46,205 [DEBUG] websocket 33: using SSL socket 2024-10-28 01:46:46,205 [DEBUG] websocket 33: X-Forwarded-For ip 'XXXX' 2024-10-28 01:46:46,210 [DEBUG] websocket 33: BasicAuth matched 2024-10-28 01:46:46,210 [DEBUG] websocket 33: using protocol Hixie 75 2024-10-28 01:46:46,210 [DEBUG] websocket 33: connecting to VNC target 2024-10-28 01:46:46,210 [DEBUG] XserverDesktop: new client, sock 35 2024-10-28 01:46:46,227 [INFO] EncodeManager: WEBP benchmark result: 10 ms 2024-10-28 01:46:46,227 [PRIO] Connections: accepted: XXXXX@XXXXX_1730098006.210469::websocket 2024-10-28 01:46:46,227 [DEBUG] XserverDesktop: Got request for framebuffer resize to 1680x844 2024-10-28 01:46:46,227 [DEBUG] XserverDesktop: 1 screen(s) 0 (0x00000000): 1680x844+0+0 (flags 0x00000000) 2024-10-28 01:46:46,227 [DEBUG] RandR: Resizing screen framebuffer to 1680x844 (orca-slicer:149): Gtk-CRITICAL **: 01:46:46.432: gtk_widget_set_size_request: assertion 'width >= -1' failed (orca-slicer:149): Gtk-CRITICAL **: 01:46:46.432: gtk_widget_set_size_request: assertion 'width >= -1' failed (orca-slicer:149): Gtk-CRITICAL **: 01:46:46.432: gtk_widget_set_size_request: assertion 'width >= -1' failed (orca-slicer:149): GLib-GObject-WARNING **: 01:46:48.686: invalid cast from 'wxPizza' to 'GtkCellLayout' (orca-slicer:149): Gtk-CRITICAL **: 01:46:48.686: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed (orca-slicer:149): GLib-GObject-WARNING **: 01:46:48.687: invalid cast from 'wxPizza' to 'GtkCellLayout' (orca-slicer:149): Gtk-CRITICAL **: 01:46:48.687: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed (orca-slicer:149): GLib-GObject-WARNING **: 01:46:48.697: invalid cast from 'wxPizza' to 'GtkCellLayout' (orca-slicer:149): Gtk-CRITICAL **: 01:46:48.697: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed (orca-slicer:149): GLib-GObject-WARNING **: 01:46:48.697: invalid cast from 'wxPizza' to 'GtkCellLayout' (orca-slicer:149): Gtk-CRITICAL **: 01:46:48.697: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed (orca-slicer:149): GLib-GObject-WARNING **: 01:46:48.704: invalid cast from 'wxPizza' to 'GtkCellLayout' (orca-slicer:149): Gtk-CRITICAL **: 01:46:48.704: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed (orca-slicer:149): GLib-GObject-WARNING **: 01:46:48.709: invalid cast from 'wxPizza' to 'GtkCellLayout' (orca-slicer:149): Gtk-CRITICAL **: 01:46:48.709: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed (orca-slicer:149): GLib-GObject-WARNING **: 01:46:48.710: invalid cast from 'wxPizza' to 'GtkCellLayout' (orca-slicer:149): Gtk-CRITICAL **: 01:46:48.710: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed ERROR: openbox-xdg-autostart requires PyXDG to be installed |
|
Easy fix. Clear within your "mounted" Folder everything except: /.config/OrcaSlicer Because there are stored your OrcaSlicer Configurations. |
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Having the same behavior, KASM is a black screen and the attempt to start the Slicer returns an error message similar to OPs. OS is Debian 11 |
Easy fix. Clear within your "mounted" Folder everything except: /.config/OrcaSlicer Because there are stored your OrcaSlicer Configurations. |
|
I deleted as you referred a couple of times and that didn't change a thing. |
Are you doing a fresh deployment? |
|
Yeah, I did a fresh deployment of everything |
|
ok, so your issue isn't the same as OP. Please open a fresh issue and provide all the requested information. |
|
As mentioned by OP, they are also without any existing config and thus a fresh deployment, so I would argue, this is the same issue. |
|
Ok, still, please provide information of your setup, our CI tests show it boots fine. https://ci-tests.linuxserver.io/linuxserver/orcaslicer/v2.2.0-ls61/index.html |
|
My setup is a Debian 11 setup with Docker (non-Swarm), using the provided docker-compose.yml example from the official documentation. |
|
What's the hardware? What's your docker compose? Are you able to deploy any of our other kasmvnc based containers without problem? Or does the same thing happen? |
|
My docker-compose.yml looks as follows: The hardware is a KVM-based virtual server with AMD-hardware. no GPU-acceleration. Temporarily deployed "docker-spotube" project and it fails to open up the spotube application as well. This time with: EDIT: There seems to be a problem with MESA , when QEMU writes the Processor-vendor as "AuthenticAMD" |
|
That LLVM error seems telling, what file system/how is your drive setup? Also provide the full path for your volume mount rather than just . |
|
The folder is on my main drive, running an ext4 filesystem. EDIT: for the LLVM problem, I found a few occurences around the web, that had to implement a fix for AMD setups, that are not correctly recognized by MESA as found in this issue |
|
Please try it from the home dir |
|
Added a fresh user "orcaslicer", created the compose-file in the /home/orcaslicer directory, started the project and got the same error as before. Adding the output of |
|
You didn't need to create a new user, just wanted you to try with the user that had id 1000. What CPU do you have? |
|
I am customer with a vServer hoster, that uses AMDs Epyc Server Processors. And it also doesn't work with the User on ID 1000 |
|
Ok, at this point, I'm lost for ideas why you're having this issue. I don't believe this to be a container issue but it's more either how your host is setup or (this is a long shot) some CPU feature that's missing. Will need to wait for someone else to join in. Though as I suspected the OP managed to boot the container and it just failed on upgrades. Your issue does not seem to be the same. |
|
I would be interested in a full-log from OP to see if they also see the But yeah, I guess with what we discussed and what my research on the MESA/LLVM side brought, it could very well be a CPU-identification mismatch produced by the LLVM/MESA subsystems that are present in the KMSAVNC base-image. |
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
As per my last suspicion, I could indeed confirm, that the problem I had was due to a faulty/not exactly correct KVM configuration on the side of hosters. |
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Still facing this issue, and nuking everything but .config did not fix it. Later image versions have not fixed the issue. |
|
Also worth noting.. as I mentioned originally the image version The working image has the following logs: So I'm thinking the big issue is the log that's only present in newer images: |
|
Like @Schuermi7 had issues running this on a vps/VM - are you perhaps doing the same? |
|
No this is on Ubuntu 24.04.1 LTS on bare metal, on an Intel i3-N300 with integrated graphics. |
|
The problem is the orasaslicer is seg faulting and crashing. |
|
I have built my own, I tried to switch over to linuxserver (one less thing for me maintain), but did work. you can try this if it works for you. https://github.com/vajonam/orcaslicer-novnc. Its specific to NVIDIA hardware. |
|
I notice when it docker exec a shell into the container and run /opt/orcaslicer/AppRun, it doesn't segfault or crash. I am running on beremetal, with other nvida runitme docker containers working fine. I have rolled my own which also works, the autostart in this container doesn't seem to work. |
|
|
|
Hmm I am using an Intel integrated GPU otherwise I'd give your image a try. When you say autorun file, do you mean https://github.com/linuxserver/docker-orcaslicer/blob/master/root/defaults/autostart? So this would need a container build to change, or is it on the filesystem somewhere? On a side note.. does that GTK_THEME give Orca a "dark mode" in this container? If so I wonder if an environment variable for it could solve #9 👀 |
|
@blackadar it ends up up inside the |
|
So anyhow, with NVIDIA proprietary drivers, one must launch the tool with virtualgl or “vglrun,” without which the slicer is not very usable. This works but, like I said, since I already maintain one image, there’s no point in adding to this one until it has this functionality, which it probably won’t, since DRI3 support is how KSVM is looking to add GPU acceleration to 3D rendering. |
|
Got the same thing unfortunately, black screen and |
|
Ah - the latest version works when I remove my mapping of This works on container version |
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Still seeing this issue with the latest image. It works fine until renderD128 is passed in. Anyone have an idea why? |
blackadar
changed the title
|
So after lots of debugging.. turns out the issue was having only Everything worked without a problem. If anyone else is experiencing this issue - give that a try! Closing this since the docs (at least now) say to use /dev/dri and not just renderD128 - so this was just a config issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
When launching even without any existing config, the container does not launch Orcaslicer although it does display a black screen with the Kasm overlay in browser. The logs show the following error:
Expected Behavior
No response
Steps To Reproduce
Launch container
Environment
CPU architecture
x86-64
Docker creation
services: orcaslicer: image: lscr.io/linuxserver/orcaslicer:latest container_name: orcaslicer security_opt: - seccomp:unconfined #optional environment: - PUID=1000 - PGID=1000 - TZ=Etc/UTC - DRINODE=/dev/dri/renderD128 - CUSTOM_USER=jordan - PASSWORD=$ORCA_PASSWORD volumes: - ./orca:/config devices: - /dev/dri/renderD128:/dev/dri/renderD128 ports: - 3002:3000 - 3001:3001 restart: unless-stoppedContainer logs
The text was updated successfully, but these errors were encountered: