Re: Beware official Qt packages
Because KDE 3.0.5 isn't in the main archive, so it doesn't really matter that much. I suggest using KDE 3.1rc5; it kicks 3.0.x all over the park. Is the plan to start uploading it to Main in a few days still holding?-) - Jarno
Re: Beware official Qt packages
On Thu, Dec 12, 2002 at 11:21:25AM +0200, Jarno Elonen scrawled: Because KDE 3.0.5 isn't in the main archive, so it doesn't really matter that much. I suggest using KDE 3.1rc5; it kicks 3.0.x all over the park. Is the plan to start uploading it to Main in a few days still holding?-) Very much so. Ben Collins has fixed the gcc 3.2 SPARC bug, ergo the transition is supposed to start Real Soon Now. -- Daniel Stone [EMAIL PROTECTED] [EMAIL PROTECTED] Developer - http://kopete.kde.org, http://www.kde.org pgpMtQ6uIdl2E.pgp Description: PGP signature
Re: trouble with kdeprint: one more additional clue
måndagen den 9 december 2002 16.09 skrev James D. Freels: Perhaps this will help... Since it is a daemon, it should execute from the console also, no ? Attempting to manually execute what I think is the kdeprintd giving the error message gives the following (along with the output from ldd): fea# /usr/lib/kde3/kded_kdeprintd.so As far as I know, you can't execute .so files directly, even though they are executable. Everything directly executable for KDE is in /usr/bin (or /usr/games) -- Karolina
Re: a workaround: final posting since no help
fredagen den 6 december 2002 22.04 skrev James D. Freels: WEll, I am getting absolutely no help in this forum. However, I did figure out a work around that allows me to get prints from kde apps until such time as the system stabilizes and things work as they should. I can pick the printer print to PS file which then does not call the kdeprintd and simply creates a postscript file selectively on my harddrive. Then, using the debian package qtcups, I can print to a cups printer that was set up inside of kde. Go figure it ! I can't help you, since I could never get my postscript printer to work with KDE either, when I tried. Later I read that QT (and thus KDE) is emitting illegal postscript, so it won't work at all. I don't know if that is fixed now. I put my postscript printer in HP laser jet emulation, and is printing with the LPD printer system (lpr-ppd). That finally worked for me. I found that the easiest to get to work. With CUPS I could never get any output, and anyway, it does not have my printer model. -- Karolina
Re: trouble with kdeprint: one more additional clue
Am Donnerstag, 12. Dezember 2002 13:58 schrieb Karolina Lindqvist: As far as I know, you can't execute .so files directly, even though they are executable. Everything directly executable for KDE is in /usr/bin (or sometimes you can :) try to execute /lib/libc.so.6 ... -- MfG, Christian Welzel (Sektionsvorsitzender und Admin AG DSN Gerokstrasse) GPG-Key: http://www.wh9.tu-dresden.de/~gawain/key.asc Fingerprint: 4F50 19BF 3346 36A6 CFA9 DBDC C268 6D24 70A1 AD15
Re: Beware official Qt packages
On Wednesday 11 December 2002 04:23 am, Michael Schuerig wrote: On Wednesday 11 December 2002 12:01, Sergio Rodriguez de Guzman Martinez wrote: Too late for me... I have lost keramik theme style and more. I just have Qt styles. :[ [EMAIL PROTECTED] (2002-12-11 at 1144.26 +0100): The official Qt packages have just been updated to Qt 3.1 (KDE qt-copy). If you're using inofficial KDE 3.0.x packages, say from download.xx.kde.org, the new Qt packages will play a number of tricks on you... If you're using apt-get, it's likely that the 3.0.x packages are still in your package cache at /var/cache/apt/archives. You'll probably be able to go back to 3.0.x without too much pain. It worked for me. Michael My old Qt debs are not in there. Could somebody tell me where I can get the old Qt debs? The Qt 3.1 debs are hosing me right now - can only get Qt styles and konsole segfaults.
