Closed zefanja closed 3 years ago
What happens when you run /usr/bin/linbo_gui -platform=linuxfb
via ssh?
What happens when you run /usr/bin/linbo_gui -platform=linuxfb via ssh?
On a fresh, not registered client:
~ # /usr/bin/linbo_gui -platform=linuxfb
Bus error
On a client, that worked before with the old GUI, after upgrading to latest testing packages:
~ # /usr/bin/linbo_gui -platform=linuxfb
-sh: /usr/bin/linbo_gui: not found
Hi @zefanja
In your first post I have noticed there are two tar processes which are trying to unpack the GUI ... Do they disappear after some time?
What happens when you run /linbo.sh
?
What happens when you run tar -vxf /linbo_gui64_7.tar.lz -C /
?
How much ram do you have?
Hi @CodeCrafter912,
What happens when you run /linbo.sh ?
unregistered client:
~ # ./linbo.sh
Trying to download linbo_gui from server to cache.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
Bus error
Bus error
Bus error
Bus error
Bus error
Bus error
Bus error
Bus error
Bus error
Bus error
Successfully installed linbo_gui from cache.
Bus error
registered client, used before with older linbo versions:
~ # ./linbo.sh
Trying to download linbo_gui from server to cache.
Successfully mounted cache partition.
Downloading linbo_gui64_7.tar.lz from 10.0.0.1.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
Successfully installed linbo_gui from cache.
Unable to figure out framebuffer device. Specify it manually.
linuxfb: Failed to initialize screen
no screens available, assuming 24-bit color
Fontconfig error: Cannot load default config file
Segmentation fault
~ # /usr/bin/linbo_gui -platform=linuxfb
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: linuxfb.
Aborted
There seems to be a loop in on of the scripts, because it tries to download linbo_gui over and over again (on unregistered client):
~ # cat /cache/linbo.log
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz from 10.0.0.1.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Continuing without cache partition.
Downloading linbo_gui64_7.tar.lz.md5 from 10.0.0.1.
linbo_gui64_7.tar.lz is up-to-date. No need to download.
Is there anything else I could do?
What happens when you run tar -vxf /linbo_gui64_7.tar.lz -C / ?
On the unregistered client, this command runs fine, but on the registered client there is no linbo_gui64_7.tar.lz:
~ # tar -vxf /linbo_gui64_7.tar.lz -C /
tar: can't open '/linbo_gui64_7.tar.lz': No such file or directory
But ./linbo.sh
says, it's up to date. Where is this file stored on a registered, partitioned client?
How much ram do you have?
4GB
In my opinion, all of your logs look like there is some problem with your hardware... Do you use a VM or actual hardware for this test? To be honest though, this got to a point where I don't know if can help, I am the GUI guy an I don't know too much about the underlying Linux... @HappyBasher what do you think?
Where is this file stored on a registered, partitioned client?
In /cache/
I suggest to test the new gui only on registered clients for the moment to have a defined and limited environment. I'm sorry I do know nothing about the above qt & linuxfb error.
I see the client is virtualized with xen server. AFAIK xen is not known to function properly with linbo.
Please close the issue if it is not relevant anymore.
It is still relevant, I just didn't have the time right now to do more testing. Regarding xcp-ng: the old linbo + gui worked without any problems.
I did some further test:
Do you have a 2.4.0 package somewhere? I like to test it, before I have to build packages for myself.
Another update:
I've build the package by myself commit after commit to test, when the booting fails. When building the package by myself linbo (without the new GUI) is working without problems (up to the latest changes).
I'm not sure, why the version from the repo didn't worked.
I'll do some more tests to get the new GUI working in xcp-ng.
After building the new UI by myself, everything is working fine. I don't know why it didn't worked in the first place.
I've installed linuxmuster-linbo7 v2.4.1 on my test server to test the new linbo GUI, but after installing the package no GUI is shown (no old gui, no new gui).
I can linbo-ssh into a client and on a new client
top
looks like this:This is how it looks like on a new (not registered) virtual client (xcp-ng 8.0):
https://user-images.githubusercontent.com/708888/102739901-ed3ced00-4380-11eb-9d8b-e52609605ed0.mp4
What can I do to debug the problem?
I've