[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#326542: kdm: kdm ignores/overrides -dpi 100 setting



retitle 326542 kdm should explain how to proceed on upgrade from 3.3.x
stop

On September 3, 2005 21:22, Brian Nelson wrote:
> Christopher Martin <christopher.martin@utoronto.ca> writes:
> > On September 3, 2005 19:31, Brian Nelson wrote:
> >> Package: kdm
> >> Version: 4:3.4.2-2
> >> Severity: normal
> >>
> >> I have the following line in my /etc/kde3/kdm/Xservers:
> >> :0 local@tty1 /usr/X11R6/bin/X -dpi 100 -nolisten tcp vt7
> >>
> >> However, since my recent upgrade to the 3.4.2 packages, X no longer
> >> starts with a dpi of 100--it either calculates the real monitor dpi
> >> and uses that (e.g. 112x112) or falls back to 75 dpi.  For whatever
> >> reason, it seems that my setting of -dpi 100 is now being ignored or
> >> overridden.
> >>
> >> The only way I can figure out how to actually get X to start with 100
> >> dpi is to exit kdm and run "startx -- -dpi 100" from the console.
> >
> > kdm doesn't use /etc/kde3/kdm/Xservers as of 3.4.x. The kdm upgrade
> > scripts will not remove Xservers if it detects local changes, however,
> > to give admins a chance to merge their customizations into kdmrc (have
> > a look at ServerArgsLocal - you'll probably need an updated kdmrc to
> > see this and have it work).
>
> Sounds like a good case for a debconf note to warn that the previous
> customizations need to be merged manually.

Indeed, I was just thinking of this as well, when I responded to your 
report. If you don't mind, I'll retitle this report, and close it when we 
upload a kdebase with the appropriate NEWS entry explaining how to upgrade 
kdm.

Cheers,
Christopher Martin

Attachment: pgp5J2fERMyQE.pgp
Description: PGP signature


Reply to: