When you install LuckyBackup, it puts two options in the menu.
Normal LuckyBackup and LuckyBackup as superuser.
With LuckyBackup, the command is /usr/bin/luckybackup.
With LuckyBackup as superuser, the command is /usr/bin/luckybackup-pkexec.
I save to an external hard drive and with the regular LuckyBackup, it always failed because
of not having the correct permission, so I always used the superuser LuckyBackup.
(This was with LL48)
Well, the superuser LuckyBackup always worked just fine in LL48, but in LL50, it gives the following error
when you use the terminal to start it:
/usr/bin/luckybackup-pkexec
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Aborted
Anyone know what the problem could be ?
[member=9005]arky217[/member] I would say it maybe something with LuckyBackup and Ubuntu 20.04 (LL5.0 Base)...
I did a quick google search and there does appear to be a bug -
https://bugs.launchpad.net/ubuntu/+sourc...ug/1887279
You would want to follow up with those devs...
(08-10-2020, 06:36 PM)arky217 link Wrote: [ -> ][...] Anyone know what the problem could be ?
Hello!
I use LuckyBackup for years!
I used it on Linux Lite 4.2, 4.4, 4.6, 4.8 and now, i use it on 5.0. Never had any trouble.
I use it as Root, only in exceptional situations.
You probably messed up with the rights.
Now, the settings are all saved in /home so reinstalling, is unlikely to solve the problem.
The only way to solve it is uninstall everything and then
delete manually any remainders from /home and wherever you find any traces of LuckyBackup. You'll have to enable viewing the hiddeen files. There are many LuckyBackup profiles spread here and there.
After cleaning everything,
use Synaptic Package Manager to install.
It should work.
I never had any problem, except for the first run. Take care at the paths. It supoports only one directory depth (the root directory) as target.
Good luck!

Quote:Well, the superuser LuckyBackup always worked just fine
I'm also facing this and the only work aorund I found is run it with sudo
so as [member=5414]firenice03[/member] posted it is a bug, its not supossed to behave like that.
Quote:I use it as Root, only in exceptional situations.
Like your regular user for backing up your /home folder it woks fine but if you want to backup the whole system you need to run it as root/superuser as it's not working. It's a bug.
(08-10-2020, 08:20 PM)Moltke link Wrote: [ -> ][...] Like your regular user for backing up your /home folder it woks fine but if you want to backup the whole system you need to run it as root/superuser as it's not working. It's a bug.
I never use it to backup /home or / (Root). It's a waste of time and space. I use CloneZilla. I only backup with LuckyBackup my personal data, nothing else.
So, I never use the "As Root" version. I only used it once, to backup Home (it's a partition) and I was sorry. It took ages (some 15 minutes or more) and sucked me 7 GB of HDD space. Bad business! :o
A common CloneZilla backup, takes below 3 GB. Some 2,5 GB / 7GB data.
LuckyBackup is very handy for 1:1 backup tasks, since you can access files directly. And is fast enough for this kind of job.

(Actually, the Oscar goes to
rsync, but...)
PS:
A bug? What bug?
rsync works in real time so NEVER backup the whole system, since it leads to many errors, due to system locked files. I thought you knew this. That's the second reason I never tried to backup the system with LuckyBackup. Too many files are changing too fast and this prevents rsync to do its job, whatever superuser you might be.
These are basic backup rules: never backup a running OS. Do it from a bootable backup tool. If you ever used TimeShift, I bet you noticed it works after shutting down the system and re-loading from RAM.
There is a difference between being a root user and trying to copy a common file and copying a system locked file. You need to issue a special command to unlock the file, which will then conflict with systemd, for one.
You may do as you please, it's your choice, but this is how it works. It has nothing to do with me, or you or anyone else. It is just the way the OS operates.
Best regards!

(08-10-2020, 08:23 PM)Şerban S. link Wrote: [ -> ]I tested it for the sake of convenience:
Below, there is a screenshot:
![[Image: IRGsEEB]](https://imgur.com/a/IRGsEEB)
https://imgur.com/a/IRGsEEB
As your regular user it works fine, the problem it's not working as expected when superuser mode; if you click on menu and look for luckybackup you'll find 2 versions/modes to choose from; a regular one and the superuser one, if you choose the
luckybackup (superuser) it won't launch/start, did you try that? did it work for you? It doesn't for me, OP and a bunch of other people apparently.
(08-10-2020, 08:45 PM)Moltke link Wrote: [ -> ][...] the problem it's not working as expected when superuser mode;
See all previous posts. I explained there what happens.
As a matter of fact, if you
read all the docs of rsync, you'll understand.
LuckyBackup is only a GUI for rsync.
Good luck!

(08-10-2020, 08:03 PM)firenice03 link Wrote: [ -> ][member=9005]arky217[/member] I would say it maybe something with LuckyBackup and Ubuntu 20.04 (LL5.0 Base)...
I did a quick google search and there does appear to be a bug - https://bugs.launchpad.net/ubuntu/+sourc...ug/1887279
You would want to follow up with those devs...
Thank you firenice03 for that link.
I edited the command in Luckybackup (superuser) and put in sudo -H luckybackup
Then I checked the box 'Run in terminal'.
Now when I click on the Luckybackup (superuser) icon, the terminal opens,
I enter my sudo password and LuckyBackup starts.
I created a task and backed up my Documents folder to the external drive, works fine.
Of course, I have to mount the external drive first or Luckybackup won't see it.
I think I've found a solution or at least a "better" workaround; open a terminal and type
Code:
pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY luckybackup
a window should pop up for you to type in your password and LBSU should launch/start and if it does, open a terminal and type
Code:
sudo nano /usr/bin/luckybackup-pkexec
comment the lines in the file, copy/paste the
pkexec command above, hit
Ctrl + o to save changes and then
Ctrl + x to close nano.
Now, click on menu, search for luckybackup and click on LBSU, a window should pop up for you to type in your password, hit enter and LBSU should start without a problem, at least It did here.