[gentoo-user] big fonts after Xorg update
Hi, I just updated from xorg-server 1.3.0.0-r6 to 1.6. After the upgrade I see a lot of applications have now much bigger fonts then they used to have (the fonts and font sizes of course are the same - they just appear bigger). Examples are KDM, Konsole, most KDE apps (GNOME applications seem not to be affected). The increased fonts looks a bit as when I connect via VNC to the diplay manager session (with the Xorg VNC module). I had the same effect already when I tried to upgrade to Xorg 1.5 (which was why I had to revert back to 1.3). This is a VMware virtual machine with the VMware tools installed and running. What can I do to avoid the "font increase"? Thorsten
[gentoo-user] Re: big fonts after Xorg update
* Nikos Chantziaras (Fri, 16 Oct 2009 02:32:21 +0300) > > On 10/16/2009 02:22 AM, Thorsten Kampe wrote: > > > > I just updated from xorg-server 1.3.0.0-r6 to 1.6. After the upgrade I > > see a lot of applications have now much bigger fonts then they used to > > have (the fonts and font sizes of course are the same - they just appear > > bigger). Examples are KDM, Konsole, most KDE apps (GNOME applications > > seem not to be affected). > > > > The increased fonts looks a bit as when I connect via VNC to the diplay > > manager session (with the Xorg VNC module). I had the same effect > > already when I tried to upgrade to Xorg 1.5 (which was why I had to > > revert back to 1.3). > > > > This is a VMware virtual machine with the VMware tools installed and > > running. > > > > What can I do to avoid the "font increase"? > > The best thing you can do with VMWare (from my own experiences) is to > force 96 DPI in /usr/share/config/kdm/kdmrc. Find this line: > >ServerArgsLocal=-nolisten tcp > > And add "-dpi 96" to it: > >ServerArgsLocal=-nolisten tcp -dpi 96 That was the solution. I checked the resolution before the upgrade with "xdpyinfo | grep resolution" (Tip from the German list): 75 dpi. Afterwards: 96 dpi. Setting it to 75 solved the issue. I'd still like to know what exactly changed and if 75 or 96 is the "correct" value. Nevertheless, I have Xorg server 1.6 running and it looks fine. Thanks, Thorsten
[gentoo-user] Re: Re: big fonts after Xorg update
* Paul Hartman (Mon, 19 Oct 2009 15:38:12 -0500) > > On Mon, Oct 19, 2009 at 3:18 PM, Thorsten Kampe > wrote: > > That was the solution. I checked the resolution before the upgrade with > > "xdpyinfo | grep resolution" (Tip from the German list): 75 dpi. > > Afterwards: 96 dpi. Setting it to 75 solved the issue. > > > > I'd still like to know what exactly changed and if 75 or 96 is the > > "correct" value. Nevertheless, I have Xorg server 1.6 running and it > > looks fine. > > Divide your screen resolution (pixels) by its visible area (inches) to > get DPI. For example my monitor screen is 16 inches wide and 12 inches > tall and I use 1600x1200 resolution. That is 100dpi. In my system this > is autodetected when xorg starts (maybe the nvidia drivers do it?). This is a VMware virtual machine using a virtual monitor on a physical machine with two physical monitors. I'm not sure whether calculating DPI that way would lead to meaningfull results for the virtual machine. This whole "hard" setting of DPI for a monitor seems anachronistic to me. Thorsten
[gentoo-user] Two taskbar panels after upgrade to KDE 4
Hi, I just upgraded from KDE 3.5.10 to KDE 4. The upgrade went fine and KDE 4 KDM shows still my old KDE 3.5, XFCE and GNOME sessions as well as the new KDE 4 session. The only problem is that when I login to the old KDE 3.5 desktop (which I want to keep until I configured KDE 4 fully) shows *two* taskbar panels: at the bottom of the screen the KDE 4 taskbar panel and directly above the old KDE 3.5 taskbar panel. How can I stop the old KDE 3.5 session from loading any KDE 4 component and in particular: how can I stop the KDE 3.5 desktop loadling the KDE 4 taskbar panel?! Thorsten
[gentoo-user] Re: Copying settings from Konqueror-3.5 to 4.3
* Etaoin Shrdlu (Fri, 23 Oct 2009 10:35:48 +0100) > > On Thursday 22 October 2009, Alex Schuster wrote: > > > > I did > > > > > > cp -a .kde3.5 .kde4 > > > > > > and all the settings (not just only konqueror's) were picked up. > > > > That did not work for me, all windows had no window title then. But it > > worked fine for partial applications when I copied just their data over. > > For konqueror, that would probably be share/config/konquerrorrc and > > share/apps/konqueror/. > > Yeah, I've seen mixed outcomes when doing that. I was probably lucky. > > What I really did was: > > 1) save the "vanilla" .kde directory that was created when kde4 first started > up, to have a safe rollback in case something goes wrong > > 2) cp -a the .kde3.5 dir to .kde4, as said > > 3) check that things were mostly correct, and if not rollback to the saved > .kde dir I created in step 1 ~/.kde is a symlink to ~/.kde3.5. So there is nothing to backup or restore. Thorsten
[gentoo-user] Re: Downgrade glibc-2.11 to 2.10
* Alan McKinnon (Tue, 17 Nov 2009 18:06:45 +0200) > > A multitude of apps that used to run just fine now give "free(): > invalid pointer" errors since I upgraded to glibc-2.11 Which ones are these? I installed glibs 2.11 on Monday and had exactly zero problems afterwards... Thorsten
[gentoo-user] Re: Python 2.7 support
* Xavier Parizet (Mon, 07 Dec 2009 10:28:07 +0100) > > I eard some (long) time ago that portage is not compatible with python 2.7, > so i > masked it (python) in /etc/portage/package.mask. What i would like to know now > is is portage now compatible with this version of python ? Or if not, where > can > i follow the status of this compatibility ? I looked on b.g.o but didn't find > anything related to this. Don't waste your or our time by trying to install alpha packages. Thorsten
[gentoo-user] Cascading autofs mounts
Hi, does anyone know (or have an idea about) how to achieve cascading mounts with autofs 5?! Basically what I would like to do is to (auto)-mount an iso image which lies on an (auto)-mounted smb share. /etc/auto.master contains: # mount_directory map_file options /mnt/smb /etc/auto/smb --timeout=5 --ghost /mnt/iso /etc/auto/iso --timeout=5 --ghost /etc/auto/smb: tkampe -fstype=cifs,cred=/root/cred ://tkampe/C\$ /etc/auto/iso: image -fstype=iso9660,ro,loop :/mnt/smb/tkampe/image.iso The auto-mount of the smb share works fine. But the mount of the iso works only if the smb share is already mounted (via "cd /mnt/smb/tkampe" for instance). What I would like to achieve is that trying to access /mnt/iso/image (which should be auto-mounted to /mnt/smb/tkampe/image.iso) triggers the auto-mount of /mnt/smb/tkampe to //tkampe/C$. But it doesn't. Ideas? Thorsten
