[BUG] AppImage binary creates a blank window in ubuntu 18.04 about vipster HOT 14 CLOSED

Update: I tried running VIPSTER on a different computer (also running ubuntu 18.04), and the problem was not reproducible. It launched successfully on the second computer. This new computer is running the standard Gnome window manager. The computer where I encountered the problem was running the (outdated) Unity window manager. I don't know if that could have caused the problem.

Perhaps this issue is specific to my computer and would not effect many users. This was my first time using an AppImage file.
If you want to close the issue, feel free.
-a

from vipster.

Thanks for the report.
What gpu is in your second machine?
I have no AMD gpus available, might be the issue here.

from vipster.

Hi Sebastian.
The second machine has an Nvidia Quadro 6000.

Incidentally, to confirm: this problem does not appear to be window-manager related. (I changed from unity to gnome, and tried again on my other computer, -the one with the AMD/ATI card-, and VIPSTER launched with an empty window again.) It's too soon to know how many other people would be effected by this. I have a weird video card. It's frustrating go get bug reports that are sort of beyond your control like this, I know. I have not tried running VIPSTER on a computer with an integrated video card yet. I'll let you know if I do. Hope this helps in some way.

from vipster.

Thanks for double-checking!
I wouldn't go so far as calling AMD-cards weird.
A bit strange that the machine tries to load the r600 driver which is mesa-based, afaik, instead of the fglrx that you claim is installed. Or maybe this is one of these hybrid drivers?
We saw (and ignored) the same problem on a colleague's machine that was using nouveau, but figured that it's not that big of a deal for nvidia.
Will leave this open, even if I've got no clue how to resolve this.

from vipster.

r600
Good catch. It looks like I never bothered to install proprietary drivers this time. I must be using the open source drivers that came with ubuntu 18.04. (My apologies for the confusion. I remember installing "fglrx" a few years ago back when I was using ubuntu 16.04. It's an old machine. I don't think it's a hybrid machine.)

from vipster.

I wouldn't have a clue how to fix this bug either. (Hopefully it will fix itself with an update to "AppImageKit".)

from vipster.

May be that it just needs a shipped and optionally loaded mesa-stack or something like that.
This is regularly done for the standard libs in appimages.
Will definitely have to check if this happens on intel, where users will rightfully expect the mesa-stack to work.

from vipster.

This is reproducible for machines running nouveau, but not intel.
When the bundled libstdc++ is loaded on our Tumbleweed machines, the driver cannot be loaded.

Why this happens on 18.04 is still unknown to me...

from vipster.

Could you test this again with a current continuous release?
I have weakened the substitution criteria, it's probably not necessary to use the bundled libstdc++,
if the system libstdc++ can be used the drivers should work.

from vipster.

Sure! Unfortunately, no success, but at least something different:

Using system python
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Fatal Python error: initfsencoding: Unable to get the locale encoding
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00007fea6f34f780 (most recent call first):
Aborted (core dumped)

from vipster.

For what it's worth, I also tested this on the computer which previously worked fine with vipster, and it has the same problem.

from vipster.

Ok, now the python integration is broken. Strange, it's compiled on ubuntu and I've personally tested it on Arch and suse. Of course this means that it won't work on another ubuntu version...
Thanks for testing, anyways, will come back to this issue when i've made some adjustments.

from vipster.

Sorry, this issue completely escaped my mind.
Is this still a problem with newer releases?

from vipster.

AppImage release mechanism will be overhauled soon.
Closing this issue as stale.

from vipster.