Re: artsd-1.3.0 and thus libqt3-3.3.3 in testing
Am Samstag, 25. September 2004 16:18 schrieb Tomas Pospisek's Mailing Lists: > On Sat, 25 Sep 2004, Hendrik Sattler wrote: > > Am Samstag, 25. September 2004 12:30 schrieb Tomas Pospisek's Mailing Lists: > >> Have you tried removing ~/.kde before upgrading? > > > > Are you joking? I shall wipe my whole working-since-KDE2-config because > > of a QT-Upgrade? NO. > > $ mv ~/.kde ~/.kde.orig > $ startkde >-> test >-> exit > $ rm -r ~/.kde > $ mv ~/.kde.orig ~/.kde Even better, a new user "test". Same problem. There is no visible difference between AA and no AA. I think I can see that AA is enabled (the grey pixels between the black ones). How can I disable it again? HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org pgpIUONGnfqEm.pgp Description: signature
Re: artsd-1.3.0 and thus libqt3-3.3.3 in testing
On Sat, 25 Sep 2004, Hendrik Sattler wrote: Am Samstag, 25. September 2004 12:30 schrieb Tomas Pospisek's Mailing Lists: Have you tried removing ~/.kde before upgrading? Are you joking? I shall wipe my whole working-since-KDE2-config because of a QT-Upgrade? NO. $ mv ~/.kde ~/.kde.orig $ startkde -> test -> exit $ rm -r ~/.kde $ mv ~/.kde.orig ~/.kde -- --- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ---
Re: artsd-1.3.0 and thus libqt3-3.3.3 in testing
Am Samstag, 25. September 2004 12:30 schrieb Tomas Pospisek's Mailing Lists: > Have you tried removing ~/.kde before upgrading? Are you joking? I shall wipe my whole working-since-KDE2-config because of a QT-Upgrade? NO. HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org pgphwqNoYO5jt.pgp Description: signature
Re: artsd-1.3.0 and thus libqt3-3.3.3 in testing
On Fri, 24 Sep 2004, Hendrik Sattler wrote: Am Freitag, 24. September 2004 19:13 schrieb Adeodato Simó: * Hendrik Sattler [Fri, 24 Sep 2004 18:30:01 +0200]: does the new version actually works reliable with the old KDE-3.2.3? see Bug#269132. the migration to testing has only been allowed by the RMs after some developer (Riku Voipio) actually checked it worked. Or is this all well tested and I should upgrade with a smile? you should be safe. if you encounter any problems, please report. First problem: all the sudden, every newly started app has AA enabled. Too bad that I really do not like it. And yes, this is surely caused by the upgrade. AA is disabled in the KDE control center and autohint and antialias are disabled in /etc/fonts/local.conf. And yes, I alread restarted the whole system... Have you tried removing ~/.kde before upgrading? *t -- --- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ---
Re: artsd-1.3.0 and thus libqt3-3.3.3 in testing
Am Freitag, 24. September 2004 22:49 schrieb Josh Metzler: > I'm running sid, but I have held off updating KDE to 3.3 until all packages > are available (which it sounds like will be in a couple of days). I have > upgraded qt to 3.3.3, though. So, I have been running KDE 3.2.3, qt 3.3.3, > and arts 1.2.3 for about a month now with no problems. > > So, I can answer your question for qt, but not for arts. Do you have antialiasing enabled? HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org pgpwrmIZjOC6z.pgp Description: signature
Re: artsd-1.3.0 and thus libqt3-3.3.3 in testing
Am Freitag, 24. September 2004 19:13 schrieb Adeodato Simó: > * Hendrik Sattler [Fri, 24 Sep 2004 18:30:01 +0200]: > > does the new version actually works reliable with the old KDE-3.2.3? > > see Bug#269132. the migration to testing has only been allowed by the > RMs after some developer (Riku Voipio) actually checked it worked. > > > Or is this all well tested and I should upgrade with a smile? > > you should be safe. if you encounter any problems, please report. First problem: all the sudden, every newly started app has AA enabled. Too bad that I really do not like it. And yes, this is surely caused by the upgrade. AA is disabled in the KDE control center and autohint and antialias are disabled in /etc/fonts/local.conf. And yes, I alread restarted the whole system... HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org pgpnuMwE9iHJQ.pgp Description: signature
Re: artsd-1.3.0 and thus libqt3-3.3.3 in testing
On Friday 24 September 2004 12:30 pm, Hendrik Sattler wrote: > Hi, > > does the new version actually works reliable with the old KDE-3.2.3? > > This also pulls in new libqt3-3.3.3. Was this actually tested against > KDE-3.2.2? I actually remember changes of libqt where some thing started > to behave strange. > How comes that such changes are in Sarge although it _might_ mess up KDE, > there? > > Or is this all well tested and I should upgrade with a smile? > > HS I'm running sid, but I have held off updating KDE to 3.3 until all packages are available (which it sounds like will be in a couple of days). I have upgraded qt to 3.3.3, though. So, I have been running KDE 3.2.3, qt 3.3.3, and arts 1.2.3 for about a month now with no problems. So, I can answer your question for qt, but not for arts. Josh
Re: artsd-1.3.0 and thus libqt3-3.3.3 in testing
* Hendrik Sattler [Fri, 24 Sep 2004 18:30:01 +0200]: > does the new version actually works reliable with the old KDE-3.2.3? see Bug#269132. the migration to testing has only been allowed by the RMs after some developer (Riku Voipio) actually checked it worked. > Or is this all well tested and I should upgrade with a smile? you should be safe. if you encounter any problems, please report. thanks, -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 The difference between literature and journalism is that journalism is unreadable and literature is not read. -- Oscar Wilde
artsd-1.3.0 and thus libqt3-3.3.3 in testing
Hi, does the new version actually works reliable with the old KDE-3.2.3? This also pulls in new libqt3-3.3.3. Was this actually tested against KDE-3.2.2? I actually remember changes of libqt where some thing started to behave strange. How comes that such changes are in Sarge although it _might_ mess up KDE, there? Or is this all well tested and I should upgrade with a smile? HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org pgp9wRKng4bKW.pgp Description: signature
