In Live session, Systemback will not start

[John Hupp]

I created a Live DVD from a Lubuntu 14.04.1 32-bit desktop installation on a machine with a Pentium 4 @ 3.2 GHz and 1 GB RAM.

It booted on another machine with an AMD Athlon 64 3400+ and 1 GB RAM, but Systemback would not start. From the Systemback desktop shortcut, I copied the startup command into an X terminal and ran that. The only output before it simply stops responding:

QXcbConnection: XCB error: 148 (Unknown), sequence: 158, resource id: 0, major code: 140 (Unknown), minor code: 20

But the Live DVD seems to be OK. I booted it on a machine with a Pentium 4 @ 2.4 GHz and 1 GB, ran Systemback, and successfully restored.

[Kendek (nemh)]

So the Systemback GUI starts with a similar machine, but would not starts with another?
Are you using closed-source graphics driver?
Please test Systemback on an installed system (with AMD-machine). The problem is persists or Systemback starts normally?

[John Hupp (john.hupp)]

The graphics drivers are the standard included open-source drivers.

I installed Lubuntu 14.04.1 on the same machine from which I made the initial report, let it update, then installed Systemback.

Trying to run Systemback failed as in the initial report.

But here is an interesting additional observation: If from an xterm I run the Systemback command string (and it hangs) and I then Ctrl-C and run the command again, it starts!

For the initial report I was using an old Matrox Mystique PCI video card. I tried again with an ATI AGP card, and it too hung on the first run but started on the second attempt.

Error output:

Matrox run #1 (hangs):

QXcbConnection: XCB error: 148 (Unknown), sequence: 158, resource id: 0, major code: 140 (Unknown), minor code: 20

Matrox run #2 (starts):

(no error output)

======================

ATI run #1 (hangs):

libGL error: dlopen /usr/lib/i386-linux-gnu/dri/r128_dri.so failed (/usr/lib/i386-linux-gnu/dri/r128_dri.so: cannot open shared object file: No such file or directory)
libGL error: dlopen ${ORIGIN}/dri/r128_dri.so failed (${ORIGIN}/dri/r128_dri.so: cannot open shared object file: No such file or directory)
libGL error: dlopen /usr/lib/dri/r128_dri.so failed (/usr/lib/dri/r128_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: r128_dri.so
libGL error: failed to load driver: r128
QXcbConnection: XCB error: 148 (Unknown), sequence: 158, resource id: 0, major code: 140 (Unknown), minor code: 20

ATI run #2 (starts):

libGL error: dlopen /usr/lib/i386-linux-gnu/dri/r128_dri.so failed (/usr/lib/i386-linux-gnu/dri/r128_dri.so: cannot open shared object file: No such file or directory)
libGL error: dlopen ${ORIGIN}/dri/r128_dri.so failed (${ORIGIN}/dri/r128_dri.so: cannot open shared object file: No such file or directory)
libGL error: dlopen /usr/lib/dri/r128_dri.so failed (/usr/lib/dri/r128_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: r128_dri.so
libGL error: failed to load driver: r128

[Kendek (nemh)]

So this is a graphics driver problem. Systemback GUI is written in Qt5, and it is quite modern, but the hardware is quite old.
I cannot access the Qt's lower level things, so I cannot fix this problem.
But try to boot the Live system in safe graphics mode, Qt5 is works with LLVMpipe (this is slow solution, using CPU).
And check an other Qt5 GUI application, this problem is probably persisted.
But anyway then you can run the command twice. :-)

[John Hupp (john.hupp)]

Booting in safe graphics mode makes no difference.

But running Systemback twice works in the Live system just as it does in the installed system. And the resulting installation seems to have full integrity.

Thanks for having a look at this promptly.

And thanks for contributing such a fine piece of software!

[Luis Gustavo S. Barreto (gustavosbarreto)]

Hi,

I found a similar problem with Ubuntu 14.04 running in VirtualBox.

Hi. I’m getting “QXcbConnection: XCB error 148” when I run a Qt based application on a empty DISPLAY. Other applications (GTK based) works fine.

Steps to reproduce:

* Install Ubuntu 14.04
* Drop to a shell
* Stop lightdm (/etc/init.d/lightdm stop)
* Start X (X -ac :0)
* Start any Qt based application (remember to export DISPLAY env)

[Kendek (nemh)]

I tried to reproduce this problem, but unfortunately I have not been successful. The 'X', 'startx' and "X -ac :0" commands does not work, I get black screen (on tty7 after "stop lightdm") and error messages (on tty1). I tried with many different systems (Lubuntu 14.04, 14.10, Ubuntu 14.04, Debian 8) in VirtualBox, and tried with a real machine (Ubuntu 14.10). I tried with root permissions and without. But the "start lightdm" command works well, so I do not know.
But seems to be this is a Qt problem, not only Systemback specific.