search

linuxmuster / linuxmuster-linbo

Linbo imaging system for linuxmuster.net
23 stars 22 forks source link

No GUI with v2.4.1 #160

Closed zefanja closed 3 years ago

zefanja commented 3 years ago

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:

Mem: 150572K used, 3879768K free, 115844K shrd, 0K buff, 115844K cached
CPU: 11.5% usr  1.4% sys  0.0% nic 86.6% idle  0.0% io  0.2% irq  0.0% sirq
Load average: 1.17 0.63 0.27 2/98 5772
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
 5772  5770 root     R    19384  0.4   5 12.4 tar xf linbo_gui64_7.tar.lz -C /
 5770  5729 root     R    13308  0.3   2  0.5 tar xf linbo_gui64_7.tar.lz -C /
  848     1 root     S    36680  0.9   5  0.0 udevd --daemon
 1675  1026 root     S    21048  0.5   7  0.0 /sbin/dropbear -s -g -E -p 2222
 1026     1 root     S    18796  0.4   6  0.0 /sbin/dropbear -s -g -E -p 2222
 1722  1676 root     R    13308  0.3   7  0.0 top
 1676  1675 root     S    13308  0.3   0  0.0 -sh
    1     0 root     S    11188  0.2   6  0.0 init

  ███               ███      WELCOME TO LINUXMUSTER.NET 7.0 - bond
 █████             █████     Monday, 21 December 2020, 04:15:58 AM
  ███               ███
      ███       ███          Uptime..........: 0 days, 00h34m00s
     █████     █████         Memory..........: 478/7945MB (6.02%)
      ███       ███          IP Internal.....: 10.0.0.1
           ███               IP External.....: 1.1.1.1
          █████
           ███              
      ███       ███          linuxmuster.net packages:
     █████     █████         -Base...........: 7.0.79-0ubuntu0
      ███       ███          -Linbo..........: 2.4.1-0
  ███               ███      -WebUI..........: 1.0.148-1
 █████             █████     -Sophomorix.....: 3.81.5-1
  ███               ███

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

dorianim commented 3 years ago

What happens when you run /usr/bin/linbo_gui -platform=linuxfb via ssh?

zefanja commented 3 years ago

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
dorianim commented 3 years ago

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?

zefanja commented 3 years ago

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?

zefanja commented 3 years ago

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

dorianim commented 3 years ago

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?

dorianim commented 3 years ago

Where is this file stored on a registered, partitioned client?

In /cache/

HappyBasher commented 3 years ago

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.

HappyBasher commented 3 years ago

I see the client is virtualized with xen server. AFAIK xen is not known to function properly with linbo.

HappyBasher commented 3 years ago

Please close the issue if it is not relevant anymore.

zefanja commented 3 years ago

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.

zefanja commented 3 years ago

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.

zefanja commented 3 years ago

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.

zefanja commented 3 years ago

After building the new UI by myself, everything is working fine. I don't know why it didn't worked in the first place.