@Germar,
What you wrote gave me an idea to change QT theme for root. So I run "sudo qtconfig-qt4". But... I run into exactly the same problem.
Search Criteria
Package Details: backintime 1.5.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/backintime.git (read-only, click to copy) |
---|---|
Package Base: | backintime |
Description: | Simple backup system inspired from the Flyback Project and TimeVault. Qt5 GUI version. |
Upstream URL: | https://github.com/bit-team/backintime |
Licenses: | GPL |
Submitter: | None |
Maintainer: | graysky |
Last Packager: | graysky |
Votes: | 296 |
Popularity: | 0.48 |
First Submitted: | 2009-01-09 20:46 (UTC) |
Last Updated: | 2024-08-07 19:55 (UTC) |
Dependencies (11)
- backintime-cliAUR (backintime-cli-gitAUR)
- libnotify (libnotify-gitAUR)
- polkit (polkit-gitAUR, polkit-consolekitAUR)
- python-dbus
- python-pyqt6
- sshfs
- xorg-xdpyinfo
- python (python37AUR, python311AUR, python310AUR) (make)
- kompare (kompare-gitAUR) (optional) – diff/patch frontend
- meld (meld-gitAUR) (optional) – diff/patch frontend
- qt6-translations (optional) – translate BIT dialogs into native language
Required by (1)
- backintime-cli (optional)
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 .. 73 Next › Last »
lockheed commented on 2015-01-31 19:47 (UTC)
Germar commented on 2015-01-31 19:39 (UTC)
I can't explain nor reproduce it neither, sorry.
Last update came with huge changes especially for GUI (it's now pure Qt4).
I only have two thinks you could check:
1. on my Arch-VM BackInTime started as root shows up with this ugly, Win95-style default theme. Not the theme you selected. Maybe there is no such default theme on your machine, or your selected theme does make some troubles with this?
2. next version 1.1.2 (coming soon) will call 'pkexec backintime-qt4' for root. You could try out if this helps by coping http://bazaar.launchpad.net/~bit-team/backintime/trunk/view/head:/qt4/net.launchpad.backintime.policy to /usr/share/polkit-1/action/ and run 'pkexec backintime-qt4'
lockheed commented on 2015-01-30 20:38 (UTC)
Here are screenshots:
Asking whether I want to import old config: http://i.imgur.com/Ffpuuf7.png
Asking for location of the old config: http://i.imgur.com/ul5WDW0.png
graysky commented on 2015-01-30 20:35 (UTC)
I can't explain it nor can I reproduce it :/ Perhaps Germar [one of the BIT devs] has some ideas.
lockheed commented on 2015-01-30 20:32 (UTC)
@graysky, I created a new empty /root folder and run sudo backintime, but the problem persists. Up until the recent upgrade, I did not have such issues.
graysky commented on 2015-01-30 20:03 (UTC)
@lockheed - I found this if I didn't have a ttf installed which is why I added the meta packages ttf-font to the qt4 package. For me, I can call backintime as my user or root via sudo and it displays just fine. Not sure what's wrong with your system. Does your /root dir have anything in it that would override or ignore system fonts? Just for the hell of it, can you create a fresh /root dir with no profiles or the like and see if you get that same behavior?
Germar commented on 2015-01-30 12:15 (UTC)
@lockheed Could you please post a screenshot?
lockheed commented on 2015-01-30 12:08 (UTC)
@Germar, why would a missing font affect root, but not user? I installed this package but the problem persists.
Germar commented on 2015-01-30 11:57 (UTC)
@lockheed sounds like missing fonts. Did you install 'ttf-font' from dependencies?
lockheed commented on 2015-01-30 10:57 (UTC)
I can run backintime as user fine, but if I run it as root, all the qt4 dialog boxes are empty gray slabs of space in the shape and size of windows of user-run backintime.
Pinned Comments
graysky commented on 2023-10-07 12:15 (UTC)
Using an AUR helper such as yay to build packages including backintime is HIGHLY discouraged. The recommended build method is to use a clean chroot. See: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot
I wrote a script that automates much of that called clean-chroot-manager offered here in the AUR.
Please stop posting build failures because you insist on building with yay or other AUR helpers.