[BUG] acbr not opening

[traceitalian]

Description:

Recently performed a clean reinstall of Fedora, installed ACBR through the flathub repo on discover, application won't open. Registers as running in system monitor and icon appears on taskbar but cannot bring a screen up to view comics. Have tried uninstalling, clearing any leftover data and reinstalling but so far this hasn't helped.

System information:

• OS: Fedora Linux 44 (KDE Plasma Desktop Edition) x86_64
• ACBR Version: 3.24.2
• Build (e.g., .exe, Flatpak, ...): flatpak

Additional context / screenshots:

Session Log:

(See: https://github.com/binarynonsense/comic-book-reader/wiki/How-to-Enable-Log-Files-for-Bug-Reports)

[binarynonsense]

Hi,

sorry about that, could you run it from the command line with the --dev flag to see what error messages it shows?

flatpak run com.binarynonsense.acbr --dev

[binarynonsense]

Just in case: wouldn't you by any chance be using a software renderer like llvmpipe, not using hardware acceleration? What does "glxinfo | grep OpenGL" print in your machine? It's unlikely but I just ask because today someone I know had the same issue and that seemed like the culprit (previous ACBR version worked because it used a version of Electron more lenient in that regard), but maybe it's something more general (as I say I upgraded some of the libraries for v3.24.x, so maybe something else is failing depending on the specific OS config that I can't reproduce in my test machines).

[traceitalian]

Hi,

sorry about that, could you run it from the command line with the --dev flag to see what error messages it shows?

flatpak run com.binarynonsense.acbr --dev

Hi, full error text attached -

acbr error.txt

I'm not an especially experienced user but it looks like it can't find the directory? Unsure.

I've also got the results from the glxinfo search:

Thanks!

[binarynonsense]

Thanks for the logs!

I think I broke the app for wayland users with my latest updates despite you being the only report I've had so far. I changed the flatpak settings to more secure ones, wayland socket + x11-fallback, and updated the Electron version I was using, which don't seem to mix that well as I was forcing x11 due to some quirks in wayland in that version of Electron (and I thought that would work with the settings I made for the flatpak)... but it seems I'm wrong (my dev computer uses x11 so I can't really test it).
I'm going to have to accelerate my plans to upgrade to a newer version of electron that better supports wayland and make the program decide which to use. Some things are a bit annoying due to changes in how things work in this newer version, but I'll try to make it work as I think the tradeoff is needed.

I'll let you know when there's a new version to try.

[traceitalian]

great, thank you :)

[binarynonsense]

I've published a new version that hopefully will fix your issue. It's already available here but on Flathub I just submitted the update and passed the tests so it will take some time (an hour, maybe some more, it's out of my control now) until they make it public and you see it on Discover.

Let me know how it goes when you give it a try.

[traceitalian]

opens completely fine now! issue seems totally fixed far as i can tell, thanks :)

[binarynonsense]

No problem, thank you for taking the time to make the issue! No one else had reported this bug since I published 3.24.0 last week, but I imagine more people were experiencing it if my theory of what was happening is correct (my systems don't use Wayland so I couldn't test it) so, if you hadn't, it could have been like that for a while :S