openSUSE KDE June 2005

kde@lists.opensuse.org

56 participants
45 discussions

by cms

Hello all, Just received my copy of SuSE 9.2 Pro and completed a clean install on my Toshiba Satellite 2435 laptop. For whatever reason, the laptop's touchpad was not detected/installed correctly. Using the laptop has become extremely difficult. The mouse opens *almost* every window and app that it trails over and hardware clicking/tapping doesn't work. I don't recall what driver I've used in the past with SuSE and this laptop--truth is, I never looked. Currently I'm using the generic PS/2 Mouse (Aux-Port) driver as indicated in the Hardware section of YaST's Control Center and the touchpad is somewhat functional, albeit with irritating side effects. With previous versions of SuSE the touchpad was detected/configured correctly and without my intervention. Anyone using SuSE 9.2 with a similar machine? Searches on SuSE's Support Portal turned up zero articles related to ALPS Touchpad devices. This is a snippet of dmesg, related to the mouse/touchpad: ------- SNIP ------- mice: PS/2 mouse device common for all mice input: AT Translated Set 2 keyboard on isa0060/serio0 alps.c: E6 report: 00 00 64 alps.c: E7 report: 73 02 0a alps.c: E6 report: 00 00 64 alps.c: E7 report: 73 02 0a alps.c: Status: 15 01 0a ALPS Touchpad (Glidepoint) detected Disabling hardware tapping alps.c: Status: 11 01 0a input: AlpsPS/2 ALPS TouchPad on isa0060/serio4 input: PC Speaker md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 ------- SNIP ------- Any help or suggestions would be greatly appreciated. TIA Chris Shanahan

15 years, 10 months

Xvnc does not start KDE anymore after update to KDE 3.4

by Thomas Börkel

HI! Since updating my Suse 9.2 to KDE 3.4, Xvnc (started via xinetd) does not start KDE anymore. When I connect to the specified port, I get a grey screen and an X mouse pointer, but no KDE login. I get nothing in .xsession-errors (I guess because Xvnc is being started by user nobody) and nothing in /var/log/messages. vncserver works OK. Any hints? Thanks! Thomas

15 years, 11 months

Monitor-Einstellungen ignoriert

by Gerhard Schmidt

Hallo. Ich habe folgendes Problem mit einem 19-Zoll-Monitor vom Typ JEN: Sowohl unter 9.2 als auch unter 9.3 stellt die KDE die Frequenz zu hoch ein, oben entsteht ein ca. 3cm breiter Rand, das Bild ist gestaucht und weit nach rechts verschoben. Alle Versuche, im Controlcenter, mit YAST oder mit sax2 die Einstellungen zu verändern, scheitern hartnäckig. Die Einstellungen lassen sich zwar ändern (bei etwas niedrigeren Bildwiederholungsfrequenzen gibt sich das) und speichern, beim nächsten KDE-Start kriegt man aber immer wieder nur den gleichen alten Salat. Was kann ich da bloss noch tun, um ihm seine Automatik abzugewöhnen und dass er gefälligst das macht, was ich ihm nun so viele Male schon gesagt habe? mfg gerd -- / ***************************************************** / * Gerhard Schmidt, Wilhelmstr.6, D-64646 Heppenheim * / * Tel. +49-(0)6252-6322, Mobile +49-(0)175-183-4118 * / * http://www.dg4fac.de, http://www.g-schmidt-hp.de * / *****************************************************

16 years, 1 month

kde

by harald.piasecki＠hanse.net

Hallo Liste, folgender Fehler: 1. der Persönlicher Ordner läßt sich unter Konqueror nicht öffnen. Fehleranzeige: KDEInit konnte "kooka" nicht starten! 2. der gleiche Fehler tritt auf wenn man am KDesktop die Ordner -Arbeitsplatz -Mülleimer aufruft. bei den Ordner -SUSE erscheint dir Fehleranzeige: KDEInit konnte "SUSEgreeter nicht starten Anmerkung: Ich habe das Betriebsssytem SUSE 9.3. Das Programm "kooka" habe ich ( deinstalliert) unter YAST wieder gelöscht. Wo liegt der Fehler? Gruß Harald Piasecki

16 years, 1 month

Clean font rendering with freetype2, ttf, the bytecode interpreter and antialiasing

by Robert Graf-Waczenski

Hi List! I'm reporting a (finally) successfull attempt to get crisp and clean looking fonts on my SuSE 9.2 / KDE 3.4.1 box. It took me quite a while to get the result that i have now, but the final procedure is (as is the case frequently) as easy as one-two-three, so i'm reporting it here for the archives and because i have unclear issues which i will be asking further below. One of the most frequently reported annoying problems on linux boxes is (IMHO) font display. There are myriads of HOWTOs and descriptions about getting truetype fonts and antialiasing working on a linux box, so i will not repeat what others have described in detail. On my own box at home, i always follow these descriptions so i have AA enabled and also have lots of free and less free truetype fonts installed. To enable & configure font antialiasing, i use the KDE control center, switch on antialiasing and set it to leave out font sizes of less than 15 points, apply the changes and restart my KDE session to let all KDE apps benefit from the changes. Result: Yuck! Or, more precisely: If I look close enough at the fonts on my LCD panel, i see some problems. Take for example the big letter A: In many fonts, the line from the bottom left point to the top middle is fuzzy and has additional "wrong" pixels in it. So, not knowing it better, i reconfigure antialiasing to not leave out smaller fonts. The result now is "better", i.e. the wrong pixels are smoothed by the antialiasing algorithm. But still! Small fonts now look sort of fuzzy and not really crisp. However, lacking time and energy, i usually leave the settings as they are and live with the font display as it is. Some time later, i stumbled upon references to the bytecode interpreter in the freetype2 library and that it would help to get better font display. I then read what the freetype2 folks write on www.freetype.org and did not enable the bytecode interpreter because it would require to re-compile the library which i would have liked to avoid. Also, the problem with the bytecode interpreter is that it needs patented algorithms, which is why it is disabled by default in almost all linux distros today. The freetype web page also mentions that their pixel-hinting algorithms are actually better than the bytecode interpreter, so they recommend to not enable it but to instead use their pixel-hinting algorithms. The page also explains why the bytecode interpreter and/or the pixel hinting is needed: The font glyph definitions contain bytes which are ignored by default and due to this, the wrong pixels i describe above are caused. I finally decided to give the bytecode interpreter a try, went to download the freetype2 sources (version 2.1.9, to be exact) and enabled the bytecode interpreter by removing the comments in one of the header files in the source code. What follows then is the usual combo of: ./configure make make install For freetype2, i also had to copy the resulting library files from /usr/local/lib to /usr/lib, but this was also done in a few seconds. I then restarted my KDE session and.... Wow! I must have been blind previously! All fonts are displayed clean and crisp, my LCD panel allowed me to distinguish each and every pixel and there were no "wrong" pixels anymore. I then re-configured anti-aliasing to start at the font size of 15, as it is supposed to be because antialiasing does not increase readability for small fonts, quite on the contrary: It makes them fuzzy! Of course, if the lack of the bytecode interpreter causes off-glyph pixels in most of the letters, antialiasing is the only way to smooth the glyph again, but this only blurs something which has been rendered badly in the first case. Did anybody encounter similar difficulties? Can anybody describe a method to get a similarly crisp and clean font display *without* the patented bytecode interpreter? I feel that this will simply not be possible because in KDE, you can only enable pixel hinting with antialiasing *enabled*, which tells me that small fonts will not benefit from pixel hinting because, as said above, antialiasing is supposed to be disabled for smaller fonts. I did play with the hinting settings that are offered by the AA config dialog but did not actually understand what i was doing, maybe i left out a variant that would have helped? Any other ideas and suggestions? Robert

16 years, 1 month

QT update from supplementary/KDE fails for SuSE 9.1

by Ingo Strauch

Hi all, I have a problem updating from the supplementary/KDE repository. I use ftp.gwdg.de /pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1 What fails are the QT3 packages: Installing the following 5 package(s): qt3-3.3.4-20.i586.rpm qt3-devel-3.3.4-20.i586.rpm qt3-devel-doc-3.3.4-20.i586.rpm qt3-devel-tools-3.3.4-20.i586.rpm qt3-static-3.3.4-19.i586.rpm ************************ * ERROR: Update failed * ************************ error: Failed dependencies: xorg-x11-Mesa-devel is needed by qt3-devel-3.3.4-20 I don't know how to resolve this. It seems to me like a bug as SuSE 9.1 came with XFree, not X.org. XFree86-Mesa-devel is installed on my system. I don't feel too happy to install with --nodeps but would prefer if the dependency could be fixed (or is the policy to upgrade XFree to X.org also for older SuSE versions?). Cheers, Ingo -- Ingo Strauch ---- Registered Linux User #227900 (http://counter.li.org/) GPG Key Fingerprint = DEC8 1B12 9573 6BE7 7A99 C33F 809C 8C2C 772E 66A1 http://www.the-one-brack.org/

16 years, 1 month

Kontact and To Do List printing

by Alvin Beach

Hello all, I am trying to print my To Do list from within Kontact. However, I only want to print the entries what have a specific start date. However, no matter what options I select in the To Do Print dialog, it always wants to print all the entries, in alphabetically order. Is there any way to fix this? Thanks, Alvin -- Please reply to the mailing list.

16 years, 1 month

panel hiding button color

by Gabor Istvan

Hello all: Is there a way to change back the hiding button's color in the panel to black? I am using Suse KDE 3.4 and the button's color currently is blue, which I don't like. Thanks, IG

16 years, 1 month

Konqueror

by Alvin Beach

Hello all, The icon placement for "Icon View" in Konqueror seems erratic. Sometimes there are huge gaps between the icons. This is for files that do have previews enabled and those with a standard icon. Is there anyway to control this? I tried changing "Height for icon text" and "Width for icon text" but they don't make that much of a difference. I'm using SuSE 9.3. Thanks, Alvin -- Please reply to the mailing list.

16 years, 1 month

KDE: cannot log in as root

by Klaus-F. Kaal

As I am having problems, logging in at KDE as root. After having checked - together with helpful people in this mailing list - whatever could be the reason for that, I only see the way to re-install Suse. I have tried to repair the system, tried the update, but it does not change the points, I want to have changed. My question: Is there a proper way of installing Suse on my computer without formating the harddisk? I have lots of data on it and it would be a huge work to save that all. The only way, Suse offers a new installtion is to re-format the harddisk. Can I avoid this? Thanks for your hints. Klaus

16 years, 1 month

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE KDE June 2005