Re: Font problem with 2.2
On Tue, Sep 25, 2001 at 11:56:35PM -0700, Kamil Kisiel wrote: > If you have KDE 2.2.1, you can run "konsole --noxft", which will turn off > anti-aliased fonts in the konsole and allow you to use all the standard fonts > that you could before. Thanks. In fact I just updated to 2.2.1 and also installed some additional font packages and it appears my problem went away. The default font in konsole is able to display ยค (Euro) and also looks quite nice with anti-aliasing enabled. Thanks a lot for the info anyway. I will probably need it in the future. Michael -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
Font question yet again
Well sort of. I have a setup where my system looks okay and displays everything I need. All I need to know now is how to set the font for the terminal window. I think I need a fixed width font there to be able to clear screen etc. Michael -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
Deadkeys
For some reason I have deadkeys again since I switched to KDE 2.2. My X server is correctly configured to use the German layout with option "nodeadkeys" and indeed it works nicely in Gnome or Xsession setup. But with KDE I get my dead keys back. Any idea? Michael P.S.: Please CC me on replies. P.P.S: Sorry for bringing this up again, but the last time it was hidden in a mail with a different topic. -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
Font problem with 2.2
Could anypone please tell me which font to use? :-) Okay, here's the situation. I configured my system to display the Euro symbol. To do so I of course need a 8859-15 font. And that's where the problem starts. As a matter of fact I need the Euro symbol in just a handful of applications one being konsole. There are just 2 8859-15 fonts available unless you use anti-aliasing. I do like to way KDE looks with anti-aliasing but konsole is rendered almost useless with it. I get vertical lines every two or three letters, I get a display that is not correctly erased etc. For instance I run an ls -R and some lines still contain pixels from before the scrolling. Then I run clear and still have quite some stuff lying around. Causing a redraw by iconizing and de-iconizing the windows clears it correctly. Do I miss a configuration option? Or do I need some other fonts? One suggestion I got was to install M$ fonts, but I'm not yet willing to do that. Michael P.S.:Please CC me on replies. -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
Re: KDM and ip aliasing
On Thu, Sep 20, 2001 at 12:15:32PM +0200, Oswald Buddenhagen wrote: > which version of kde/kdm are you using? if it's >= 2.2alpha2, the Sorry, forgot that. It's 2.1.1. > otherwise i can only ask, if it works with plain xdm - if not, then > i obviously have something more to code ... I have to try that. More later. Michael -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
KDM and ip aliasing
Hi, does anyone know how to configure KDM to run on an aliased IP? I do have a machine running 2 IPs on one network card. For some network reasons I need KDM to run on the aliased one and not the original one. The clients try to connect via chooser broadcast and only see the original IP address. Is there a way to correct this? I tried setting DisplayManager.sourceAddress but this does not seem to change anything. Thanks in advance for any hint Michael P.S.: Please CC me on replies as I'm not subscribed here. -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
Re: Bug#78129: kups: Cannot configure my printer anymore
On Mon, Nov 27, 2000 at 06:53:15PM +0100, Mariusz Przygodzki wrote: > I can not reproduce this bug. > Versions of the packages (on my machine) kups depends on: > cupsys1.1.4-2 > kdelibs3 2.0-final-11 > libc6 2.2-4 > libjpeg62 6b-1.2 > libkupsdconf1 0.8.0.20001119cvs-1.1 > libpng2 1.0.8-1 > libqtcups11.1-3.1 > xlib6 3.3.6-15 > xlibs 4.0.1-8 > zlib1g1.1.3-11 I just updated my system to the most up-to-date packages available but kups still crashes. Here's the stack trace: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1024 (LWP 10860)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x40ce8a99 in wait4 () from /lib/libc.so.6 #0 0x40ce8a99 in wait4 () from /lib/libc.so.6 #1 0x40d4c48c in __check_rhosts_file () from /lib/libc.so.6 #2 0x404e6d60 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.3 #3 0x40f14a6b in pthread_sighandler () from /lib/libpthread.so.0 #4 0x40c72da8 in sigaction () from /lib/libc.so.6 #5 0x8062bc5 in QCollection::newItem () #6 0x805e574 in QCollection::newItem () #7 0x40906307 in QListView::rightButtonClicked () from /usr/lib/libqt.so.2 #8 0x40882b90 in QListView::contentsMouseReleaseEvent () from /usr/lib/libqt.so.2 #9 0x408c1a35 in QScrollView::viewportMouseReleaseEvent () from /usr/lib/libqt.so.2 #10 0x408c1576 in QScrollView::eventFilter () from /usr/lib/libqt.so.2 #11 0x40881a71 in QListView::eventFilter () from /usr/lib/libqt.so.2 #12 0x407f6c48 in QObject::activate_filters () from /usr/lib/libqt.so.2 #13 0x4083a2af in QWidget::event () from /usr/lib/libqt.so.2 #14 0x407a9edb in QApplication::notify () from /usr/lib/libqt.so.2 #15 0x4049c5d4 in KApplication::notify () from /usr/lib/libkdecore.so.3 #16 0x40779470 in QETWidget::translateMouseEvent () from /usr/lib/libqt.so.2 #17 0x40776bca in QApplication::x11ProcessEvent () from /usr/lib/libqt.so.2 #18 0x40775c4a in QApplication::processNextEvent () from /usr/lib/libqt.so.2 #19 0x407abb90 in QApplication::enter_loop () from /usr/lib/libqt.so.2 #20 0x40775bc7 in QApplication::exec () from /usr/lib/libqt.so.2 #21 0x8082cdb in QCollection::newItem () #22 0x40c63c1c in __libc_start_main () from /lib/libc.so.6 > Is anybody can help me and reproduce this bug? There is no difference between running kups as root or as a normal user. The text printed out on the calling konsole is: menu value: 7 KCrash: crashing crashRecursionCounter = 2 KCrash: Application Name = kups path = Michael -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
