WebGL could not be intialized

[arielaco]

Describe the bug "Storyboarder is not supported on your device because WebGL could not be initialized"

To Reproduce Steps to reproduce the behavior:

1. Open Storyboarder
2. New blank project

Desktop (please complete the following information):

• OS: Ubuntu 20.04, fresh install with nvidia drivers
• AppImage 2.0.0

How can I fix this? Any package I need to install?

[arielaco]

Anyone?

[audionerd]

This is usually a graphics card issue. We’re hoping to upgrade the version of Electron used by Storyboarder soon which might help.

[arielaco]

Thank you!

[setpixel]

Actually, would you like to test? We can try to make a new build for you. Would be good to get a linux tester.

[arielaco]

Sure thing!

[fpstovall]

Sign me up as a linux tester too.. earlier versions ran on my machine, but I'm hitting the same issue on fedora 32 now. Using Nvidia driver on a KT5000 Quaddro card.

[Manuetlo]

Hi,

I have the same problem when I launch Storyboarder to open or create a project : Bug: "Storyboarder is not supported on your device because WebGL could not be initialized" My graphic card: Intel HD Graphics 4000 on Windows 7 professional 64 bits

Someone to solve the problem?

[andrenasturas]

Same, running with a Nvidia GTX 1080 Ti on ArchLinux with Nvidia proprietary drivers.

I found a workaround by running npm start --ignore-gpu-blacklist.

[OsniWinkelmann]

I was having the same problem.

I use Ububtu 20.04 and I have an NVidia 1060 graphics card and used 440 drives (owner, tested).

I solved the problem by changing the graphics driver to the Nouveau version of xserver-xorg-video-nouveau (open source).

[gRuGo]

I have the same problem. I use Pop!_OS 20.04 LTS and I have an GeForce GT 750M graphics card. if I use the integrated graphics card it runs without problems

[antimagic]

Same issue on Pop!_OS 20.04 LTS with a GTX 1070 Ti. Above workaround of setting up a local build & running npm start --ignore-gpu-blacklist seems to work nicely though, just used it for a while & didn't run into any issues.

[TheGhostHybrid]

Same issue! Manjaro 20.01 KDE with an Nvidia GeForce GTX Titan X card. I am utilizing the proprietary drivers.

[j2l]

+1, PopOS 20.04, GTX970 from another ticket about it: "Storyboarder-2.0.1-linux-x86_64.AppImage --no-sandbox &" works for now

[setpixel]

I recently switched from macos to pop os, so I'm going to fix this by next release!

[setpixel]

Additionally, which linux downloads should we offer? currently we publish an appImage. I am thinking about changing it to .deb .rpm and .snap. what do you guys think?

[arielaco]

I recently switched from macos to pop os, so I'm going to fix this by next release!

Great news!

Additionally, which linux downloads should we offer? currently we publish an appImage. I am thinking about changing it to .deb .rpm and .snap. what do you guys think?

I'd personally prefer .deb, though I'm not that knowledgeable about the differences. But in my experience as I suppose an average Ubuntu user, .deb seems to be at least the de facto standard and I can't say I've had any headaches with them, which is not the case with snap and the way it spams $ df -h, or the launcher I had to install and setup for AppImages.

Again, my experience as an average user without deep knowledge about the various distribution methods.

Whatever method you choose I'll adapt and I'll be eagerly waiting for the fix.

Thank you!

[TheGhostHybrid]

Perhaps flatpak as well? Not everyone can/wants to install the snap framework, and flatpaks seem to be more widely supported.

Plus, since not every distro is Debian/Ubuntu-based, that flexibility will help (although having the AppImage already helps in that regard!)

Either way, once you publish in .deb and .rpm, I'm sure someone will also make it available in the AUR as well, so that will be nice.

[jmtemmos]

Same issue Manjaro, Nvidia RTX 3080 witjh proprietary drivers npm start --ignore-gpu-blacklist works, but no shot generator is available