non-themed kdm greeter text needs to be bigger

Duncan 1i5t5.duncan at cox.net
Mon Jul 21 03:14:13 BST 2014


Felix Miata posted on Sun, 20 Jul 2014 10:18:34 -0400 as excerpted:

>> Be that as it may, while I don't know the kde-specific technology, and
>> don't have a greeter installed here at all as I login at the CLI, one
>> general solution I've used to change font size in the past is to set
>> X's DPI...
> 
> On your giant display it may not have been obvious, but that screenshot
> was taken in what should be a 144 DPI context. It's a different degree
> problem according to what the DPI actually is, but not solvable via DPI
> when DPI has already been set where it needs to be set or DPI forcing is
> being ignored. It would be a lesser problem were not KDM ignoring the
> xrandr commands necessary to work around
> https://bugs.freedesktop.org/show_bug.cgi?id=77321 and do DPI
> configuration via xorg.conf* DisplaySize instead of messing with xrandr.

Hmm...  Regarding that bug, I see in your xorg.conf you have a screen 
section, but no display subsection.  Does adding a display subsection 
with the following, in the screen section, work?

Subsection "Display"
	Virtual 1920 1200
EndSubSection

It has been a few xorg versions ago that I tried something like that 
here, and I can't remember whether it worked or whether I had to do an 
xrandr call to get it to work, but I remember trying it.  I had been 
using kwin's zooming effect and of course panning with that, and the idea 
came to me that I could setup a really giant virtual desktop basically 
twice the size horizontally of my triple-monitor-stacked actual display 
area, so the virtual would be 2x3 the size of a single monitor, but with 
the three monitors stacked displaying the full height, I'd essentially 
have two desktops side-by-side on the same virtual desktop and could pan 
between them, while still having the normal set of virtual desktops I 
could switch between.  Either that or possibly double it both directions 
so I'd have a 6x2 grid, with three physical monitors stacked so it was 
2x2 times the actual display area and I could pan to any of the four.

As I said I don't remember whether it was the xorg.conf configuration or 
only xrandr that worked, but whichever it was, that did work as far as X 
and most apps were concerned.

The biggest problem was plasma.  Normally, each monitor gets its own 
"activity" -- it's the same activity-name, but each monitor's screen-
space is configured separately, with its own plasmoids and its own 
wallpaper and etc.  That didn't work out so well with the over-sized 
virtual desktop, and plasma went crazy, distorting the desktop, with no 
obvious way to configure the size of each sub-activity or to make it a 
2x3=6 sub-activity display instead of 1x3.

The other problem was that I decided I didn't like the full-resolution 
panning as much as I thought I would, tho if I had been able to get 
plasma working correctly on the oversized desktop, I'd have lived with 
that.

One of these days I might try that again, just to see if it works better 
now.

> KDM3 doesn't misbehave like KDM4 does:
> https://bugzilla.novell.com/show_bug.cgi?id=888055
> 
> Maybe I filed in the wrong place, but knowing what I know about v4
> locking vs. v5 development, and LightDM replacing KDM, I suspect
> attempting a solution upstream of a distro would be an exercise in
> futility. Plus the complexity of getting a shot set up remotely made me
> avoid attempting to ensure that the problem and absence of apparent
> solution is the same on other than openSUSE.

FWIW, as I said I don't use a DM or greeter, so I don't know about that 
side of things, but I DO know that kde-frameworks-5 and plasma-5 (what 
was being called plasma2) are supposed to support high-density displays, 
basically doubling (tripling?) the size of most things, while still 
allowing the extra pixels to smooth fonts and the like, much like Apple's 
technology does these days.

(FWIW2, I did actually setup and build qt5/kde-frameworks-5/kde-
workspaces-5-rc a few days ago, based on the gentoo/qt overlay qt5 and 
the gentoo/kde overlay kde-frameworks-5 and kde-workspaces-5-rc, and did 
get all the gentoo USE flags and etc setup for it and got it to build and 
install, but when I tried to run it, kwin5 kept crashing.  Unfortuantely, 
while kde-frameworks-5 is designed to install beside kde4, kde-
workspaces-5 is not, so to get it to install I had to uninstall kwin4/
plasma4, etc, enough of kde4 so it wouldn't run either.  If I could have 
left them both installed, the working kde4 and a broken kde5 to keep 
trying every so often, I would have, but since I couldn't, I uninstalled 
all the kde5 stuff and reinstalled the bits of kde4 I had to uninstall to 
get kde5 installed.

So I'm back to kde4 now, without getting much of a chance at kde5, tho I 
tried.  I suspect that as the readme said is the case with some graphics 
hardware, kwin5 can't yet deal with the radeon turks (hd6670 IIRC) 
graphics I'm running, thus the crashes.  I was disappointed that I 
couldn't really get a running kde5 yet, but not entirely surprised.

I'll probably wait now until gentoo gets a main-tree qt5 at least, as 
there's no qt5 in the main gentoo tree at all yet, thus my having to 
install it from the gentoo/qt overlay, then try kde5 again.  But I have 
tried it now, just no dice for me at this early stage. =:^(  )

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.




More information about the kde mailing list