Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

backintime-qt issues with very large screens #1124

Closed
nsoft opened this issue Dec 13, 2020 · 5 comments
Closed

backintime-qt issues with very large screens #1124

nsoft opened this issue Dec 13, 2020 · 5 comments
Labels
Bug Qt Qt bugs, code or features

Comments

@nsoft
Copy link

nsoft commented Dec 13, 2020

Description: When attempting to open backintime-qt on my Ubuntu 18.04 desktop with a Samsung Oddessy G9 49" monitor running at 5120x1440 pixels there is a long delay and then the intial "question" and "settings" screens are created at a window size much LARGER than my screen. No text or controls are visible, and the windows created cannot be resized via side or top corners. Bottom corners are inaccessible because they hang off the bottom of the screen. The following error messages are seen in the terminal window:

gus@ns-l1:~$ backintime-qt

Back In Time
Version: 1.2.1

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.

ERROR:dbus.proxies:Introspect error on :1.19:/org/gnome/SessionManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
ERROR:dbus.proxies:Introspect error on :1.69:/modules/kwalletd5: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
ERROR:dbus.proxies:Introspect error on :1.69:/modules/kwalletd: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::deviceTransform: Painter not active
QPainter::worldTransform: Painter not active
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setRenderHint: Painter must be active to set rendering hints
QPainter::translate: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::setBrush: Painter not active
QPainter::setPen: Painter not active
QPainter::setPen: Painter not active
QPainter::end: Painter not active, aborted
QPainter::end: Painter not active, aborted

Steps to reproduce:

  1. Download version 1.2.1 and unpack on a machine with a 32:9 DQHD monitor
  2. From a terminal run backintime-qt

Workaround:
I can get the program to start normally if I activate Picture By Picture which divides the screen to show two inputs (since I only have one, half the screen is blank) and halves the horizontal resolution to 2560x1440. Once I do that I an see that the first "Question" dialog is asking "Back in Time is not configured. Would you like to restore a previous configuration?" And settings has 6 tabs all of which seem normal, and once the program is opened I seem to be able to safely restore the original resolution.

@ploplo
Copy link

ploplo commented Dec 25, 2020

I have exactly the same issue on a Samsung 49" running Kubuntu 20.04.
I do not get any error output in the terminal.
This happens when I run as root. If I start as regular user it states that it has no saved configuration and opens the gui to navigate to previous backup.
Changing to a smaller screen and starting as root it starts (but with a small window) and configurations are there .

@carobinario
Copy link

Hi, any chance to get bug fixed? Developement of backintime seems stopped since 2019. Thanks.

@aryoda
Copy link
Contributor

aryoda commented Oct 7, 2022

Does the issue still occur?

It is difficult to reproduce without the same hardware (perhaps on a VM it it is possible to set the screen size beyond the size of the host).

According to this link it may be fixed with a Qt update (so not directly connected to BiT):

bitcoin-core/gui#175 (comment)

@emtiu
Copy link
Member

emtiu commented Oct 7, 2022

Well, I nearly broke my wrist, but I managed to crank up an OpenSUSE Tumbleweed VM to >5400x1500, and backintime-qt ran just fine, without any failures. So I'm closing this Issue.
Screenshot_20221007_231217

@emtiu emtiu closed this as completed Oct 7, 2022
@aryoda
Copy link
Contributor

aryoda commented Oct 22, 2022

Whichever may have caused the huge window size - the first aid in such cases is:

Open your BiT config file with a text editor (normally stored in this file and location: ~/.config/backintime/config)
and search for these lines at the end of the config:

qt.main_window.height=1142
qt.main_window.width=1482

You can now edit the numbers to change the windows size (in pixels).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Qt Qt bugs, code or features
Projects
None yet
Development

No branches or pull requests

5 participants