Weird layout after fresh install

16 posts / 0 new
Last post
PA8E
PA8E's picture
Weird layout after fresh install

After installing CQRlog on a fresh Ubuntu 18.04 from PPA I got a very weird layout (see picture). Probably a simple preference thingy. Can some one point me in the right direction?
73 Jim

PA8E
PA8E's picture
The screenshot

The screenshot

File: 

73 de PA8E, Jim

https://pa8e.nl

oh1kh
The screenshot

Hi!
What window manager is in use? Can you switch to another window manager for test?

You can also try Petr's new beta 2.3.0-002. Look at https://www.cqrlog.com/node/2170
Or my test version 2.3.0-203 http://www.saunalahti.fi/~sakny/bin/cqrlog2/

to see if those make any difference.

--
Saku
OH1KH

DL7OAP
i did have a similar problem

i did have a similar problem some month ago.
at that time it was a mismatch between using QT , GTK and GTK2.
i found a email where i solved the problem by changing an enviroment variable UNSET QT_STYLE_OVERRIDE".

you should search in this direction and have a look in the environment variables GTK*, GTK2* and QT*.

55&73 de DL7OAP, Andreas

PA8E
PA8E's picture
Hi Andreas,

Hi Andreas,

thank you for the tip. No luck setting the variable. Still the same... :-(

73 de PA8E, Jim

https://pa8e.nl

PA8E
PA8E's picture
Hi Saku,

Hi Saku,

Ehm, the default window manager in Ubuntu Desktop 18.04?

It's a little better, but not yet what it should be.

File: 

73 de PA8E, Jim

https://pa8e.nl

oh1kh
What version of GTK do you

What version of GTK do you have?

Lazarus programs may need (I'm not sure but by fast googling) GTK2. GTK# is not supported fully yet.
My computer (Fedora28) has both gtk2 and gtk3

--
Saku
OH1KH

PA8E
PA8E's picture
dpkg -l libgtk* | grep -e '^i

dpkg -l libgtk* | grep -e '^i' | grep -e 'libgtk-*[0-9]'
ii libgtk-3-0:amd64 3.22.30-1ubuntu1 amd64 GTK+ graphical user interface library
ii libgtk-3-bin 3.22.30-1ubuntu1 amd64 programs for the GTK+ graphical user interface library
ii libgtk-3-common 3.22.30-1ubuntu1 all common files for the GTK+ graphical user interface library
ii libgtk2.0-0:amd64 2.24.32-1ubuntu1 amd64 GTK+ graphical user interface library
ii libgtk2.0-bin 2.24.32-1ubuntu1 amd64 programs for the GTK+ graphical user interface library
ii libgtk2.0-common 2.24.32-1ubuntu1 all common files for the GTK+ graphical user interface library
ii libgtk3-perl 0.032-1 all Perl bindings for the GTK+ graphical user interface library
ii libgtk3-simplelist-perl 0.17-1 all Perl simple interface to GTK+ 3's complex MVC list widget

I guess I have both?

73 de PA8E, Jim

https://pa8e.nl

PA8E
PA8E's picture
[Solved]

Okay, after tried almost everything I could think of (even downgrading to Ubuntu 16.04, which didn't solve my layout problem) it turns out to be a simple preference. When Ubuntu detects a high resolution (which it choose itself upon installation) it will set display scaling to a higher value then 1.
When scaling is higher then 1 the layout of CQRlog will be weird. Not only CQRlog by the way, more applications suffer from this.

Put scaling back to 1 and everything is back to normal.

73 de PA8E, Jim

https://pa8e.nl

ok2cqr
ok2cqr's picture
Re: [Solved]

Jim,

I can prepare QT5 version of CQRLOG. Could you try it on your system, please? I don't have any device with so high resolution or where I ahve to change scaling. QT5 version could work better.

73 Petr

kd9nzz
Petr,

Petr,
I may not be Jim but I would be happy to help out with testing a QT5 version since i ran into this issue as well. Just let me know what you need me to do.
--
Marc

PA8E
PA8E's picture
Petr,

Petr,

Sure I can do that! Let me know where I can download the QT5 version of CQRLOG and I'll report back.

73 Jim

73 de PA8E, Jim

https://pa8e.nl

kd9nzz
What if we can't (practically) change the scaling?

I'm running Ubuntu 18.04 LTS on an nVidia Jetson Nano with a small display attached (a 10" 2K display). Setting scaling to 1 makes everything except for CQRlog too small to read comfortably at all. I'm wondering if there's some switch that can be set during build time to tell the application to support high DPI displays and scaling.
Now, unlike some I'm not deep into CQRlog, having only had my call sign for a week or so and having not made any contacts that I need to log, but I'd like to be able to find a way around this scaling issue so that I can use the application. While I know that my specific setup is unusual, but I would imagine that there are a lot of people out there using small high DPI displays for mobile logging (for field days and such).

Thanks for reading!
Marc
kd9nzz

kd9nzz
And just like that I found a workaround!

It's not a perfect solution but https://askubuntu.com/a/960041 shows a way to *not* scale an individual app. In my case I had to leave winswitch out of the apt-get install list because it's not available. I also had to install curl because it wasn't on my system (sudo apt-get install curl). I had to create the directory .local/bin before running the curl command. After installing everything, I needed to add my user to the xpra group (sudo adduser xpra). After testing from a terminal, I created a desktop shortcut to launch it. Interestingly, it won't run if Terminal=false is set, so I had to change that line to Terminal=true. The only weirdness I've seen at a glance is that the mouse pointer goes from normal size to GIANT when it moves over the cqrlog window but that's no biggie.
73!
Marc (kd9nzz)

sm0nor
DPI Scaling on high res display

Marc,
This solution seem to work fine on my Surface Pro 3 on Ubuntu 20.04. Thanks! Cqrlog scales nicely with an extra big pointer as you say :-).
I do get a few lines of error messages when starting up. Do you get that as well? I'm a Linux-newbie, so I don't really know the implications..
Also, I did not understand the terminal=true/terminal false part. I just type it at the terminal prompt but it seem to make no difference.

To others who are Linux-newbies as me, in order to write to /usr/local/bin you need to be a root user with with sudo -s
73's
Ulf - SM0NOR

mi0hoz
mi0hoz's picture
CQRLog Scaling Problem Solved

I think I've found the solution. I'm using Ubuntu 20.10 and made a short video showing the solution. https://youtu.be/_yTOvTmA-Ng

73's

MI0HOZ