Re: problems with dist-upgrade (libarts)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 05 October 2002 6:54 pm, Fred K Ollinger wrote: > > /home/mschz/ROOT> apt-get dist-upgrade > > [SNIP] > > > (Reading database ... 55855 files and directories currently installed.) > > Unpacking libartsflow-data (from .../libartsflow-data_1.1.0-1_all.deb) > > ... dpkg: error processing > > /var/cache/apt/archives/libartsflow-data_1.1.0-1_all.deb (--unpack): > > trying to overwrite `/usr/lib/mcop/Arts/Synth_ADD.mcopclass', which is > > also in package libarts1 > > Looks like you have two versions of libarts, one of which is being > replaced. > > To me, I think you should have purged kde before you did the dist-upgrade: > > apt-get remove --purge `dpkg -l | grep kde` > This sadly will not work. you need to do: apt-get --purge remove kdelibs4 libarts1 you can then just install kde again. > After you dist-upgrade do: > > apt-get -f install > > if you need to clear things up. > > Good luck, > > Fred Ollinger - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9oBQRYsCKa6wDNXYRAoUtAJ4t7qK4xwRnsXiasExiBBodSR9iXgCeN3Ee jN9S9fZti036WmBTrcqR+mA= =k7bx -END PGP SIGNATURE-
Re: kde3, xinerama, and xfs (x font server)
On Fri, Oct 04, 2002 at 10:06:39AM +0100, David Pashley wrote: > don't use xfs. seriously. There is no reason these days to run a font server > if you just have a single machine. AIUI, you can't use XRENDER with font > servers, so you will be able to get anti-aliased text if you use one of the > local font renderers. > > /me awaits the "you should always use font servers" replies Not having to fiddle around with font servers (at least with TT fonts) was one of the coolest things about X4. The downside (as far as I have been able to figure) is that you have restart X to take advantage of any new fonts you might install. Aside from that, yeah, avoid font servers unless you know why you want it (sharing fonts over a network). -rob pgpxQK50K4Ig3.pgp Description: PGP signature
Re: kde3, xinerama, and xfs (x font server)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 06 October 2002 5:53 am, Rob Weir wrote: > On Fri, Oct 04, 2002 at 10:06:39AM +0100, David Pashley wrote: > > don't use xfs. seriously. There is no reason these days to run a font > > server if you just have a single machine. AIUI, you can't use XRENDER > > with font servers, so you will be able to get anti-aliased text if you > > use one of the local font renderers. > > > > /me awaits the "you should always use font servers" replies > > Not having to fiddle around with font servers (at least with TT fonts) > was one of the coolest things about X4. The downside (as far as I have > been able to figure) is that you have restart X to take advantage of any > new fonts you might install. > "xset fp rehash" should work. AIUI, it reloads the font path info. I would be surprised if it didn't take new fonts into account. > Aside from that, yeah, avoid font servers unless you know why you want > it (sharing fonts over a network). > > -rob - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9oBrQYsCKa6wDNXYRAitVAJ9pG3+o64P01MSKGEGzggmitrMtewCfZeqY KraKz1dGMm9OFEtqL9iqktg= =yEvz -END PGP SIGNATURE-
Re: kde3, xinerama, and xfs (x font server)
On Sun, Oct 06, 2002 at 12:13:17PM +0100, David Pashley wrote: > > Not having to fiddle around with font servers (at least with TT fonts) > > was one of the coolest things about X4. The downside (as far as I have > > been able to figure) is that you have restart X to take advantage of any > > new fonts you might install. > > "xset fp rehash" should work. AIUI, it reloads the font path info. I would be > surprised if it didn't take new fonts into account. Oh wow. I thought that only worked if you had a font server. -rob pgpkNUWVWebMK.pgp Description: PGP signature
some problems for kde3.1beta2 debian packages
I have experienced, until now, problems with the following applications noatun korganizer the problems are solved by the following actions: noatun: the following links are missing in /usr/lib directory libvorbisenc.so.0 -> libvorbisenc.so.2.0.0 libvorbisfile.so.0 -> libvorbisfile.so.3.0.0 korganizer: the following files are missing in /usr/lib directory libkcalsystem.la libkcalsystem.so.0.0.1 the following link is missing in /usr/lib directory libkcalsystem.so.0 -> libkcalsystem.so.0.0.1 bye and thank you for Debian packaging of kde3.1 beta :) V P.S. Debian rulez
3.1 b2 won't start up
hi, i'm trying to run kde 3.1 beta2 (it seemed to install without a problem) on woody but as soon as X (4.2.1-0pre1v2) starts i get the two notorious messages "Couldn't start kdeinit. Check your installation." and "Couldn't start ksmserver. Check your installation." when i ok both, the xserver shuts down. i checked .kde3-errors and there it says this: ... xsetroot: unable to open display '' xset: unable to open display "" dcopserver: relocation error: /usr/lib/libDCOP.so.4: undefined symbol: static_QUType_varptr kwin: relocation error: /usr/lib/libDCOP.so.4: undefined symbol: static_QUType_varptr ... and so on for anything that was attempted to run. i get the same error when trying to run a kde app from other window managers. anybody's got an idea what the reason of this might be? i'm new both to debian and linux in general (running freebsd) so this may be just a silly mistake which i didn't think of. thanks. robert
KDE packages (3.0.4 and 3.1)
Hi, three things :-) a) Sorry ...for the inconvenience about the Packages.gz file on the ftp server. I didn't know why I should create 8 subdirectories in a row just for a beta build and that I should have regenerated the Packages.gz file. As said, the KDE 3.1 beta2 was not correct anyway so I think this is a minor issue for now. more important is that it works for b) and c) correctly :-)) b) KDE-3.0.4 Release I'm packaging up KDE 3.0.4 for both, sid and woody. Woody gives me a bit of a problem in kdelibs-data not installing the files in /etc/kde3 there, so if you have any idea why that is, please tell me :-). The woody release will include a backport of qt-3.0.5 from unstable and a fix in kdelibs that avoids the stretching of the ktipdialog with qt-3.0.5. At any rate, qt has been compiled with -no-xft to avoid application crashes under XFree 4.1, so if you're missing antialiasing and you're running XFree 4.2, take the version from unstable. Another minor change in kdebase will be that this ugly debian background logo will be away by default and be replaced with the usual debian logo in the logo field of the greeter in KDM. The default background wallpaper will be the default_blue.jpg as is stock with KDE. It's much more pleasant to the eyes and you don't want to scare away your users at the login screen already, do you ? :-) c) KDE 3.1 Release (and RC's) When I'm done with the 3.0.4 packages, I'll switch to HEAD again and help solve the remaining issues with the packages there so we can be able to provide RC packages when they are due and final packages, too, as soon as the KDE release date is coming up and the packagers get the packages provided by Dirk Mueller as usual. I hope you can live with that I'm struggling a bit, but being a Debian user since 3 weeks only I hope you can live with that I try to catch up for a week :-) Ralf -- We're not a company, we just produce better code at less cost. Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org
Re: KDE packages (3.0.4 and 3.1)
On Sunday 06 October 2002 19:05, Ralf Nolden wrote: > Hi, > > three things :-) > > a) Sorry > ...for the inconvenience about the Packages.gz file on the ftp server. I > didn't know why I should create 8 subdirectories in a row just for a beta > build and that I should have regenerated the Packages.gz file. As said, the > KDE 3.1 beta2 was not correct anyway so I think this is a minor issue for > now. more important is that it works for b) and c) correctly :-)) > > b) KDE-3.0.4 Release > I'm packaging up KDE 3.0.4 for both, sid and woody. Woody gives me a bit of > a problem in kdelibs-data not installing the files in /etc/kde3 there, so > if you have any idea why that is, please tell me :-). The woody release > will include a backport of qt-3.0.5 from unstable and a fix in kdelibs that > avoids the stretching of the ktipdialog with qt-3.0.5. At any rate, qt has > been compiled with -no-xft to avoid application crashes under XFree 4.1, so > if you're missing antialiasing and you're running XFree 4.2, take the > version from unstable. Another minor change in kdebase will be that this > ugly debian background logo will be away by default and be replaced with > the usual debian logo in the logo field of the greeter in KDM. The default > background wallpaper will be the default_blue.jpg as is stock with KDE. > It's much more pleasant to the eyes and you don't want to scare away your > users at the login screen already, do you ? :-) > > c) KDE 3.1 Release (and RC's) > When I'm done with the 3.0.4 packages, I'll switch to HEAD again and help > solve the remaining issues with the packages there so we can be able to > provide RC packages when they are due and final packages, too, as soon as > the KDE release date is coming up and the packagers get the packages > provided by Dirk Mueller as usual. > > I hope you can live with that I'm struggling a bit, but being a Debian user > since 3 weeks only I hope you can live with that I try to catch up for a > week Can live with that? I appreciate everything you do and have to be _thankful_! Thankfull to all debian-kde developers, we can't stress that too often, if you wouldn't do it your way we might not have packages at all! BTW, I'm using current 3.1b2 packages and they are quite nice... looking forward to the RC1 packages! MfG Franz Keferböck > > :-) > > Ralf > -- > We're not a company, we just produce better code at less cost. > > Ralf Nolden > [EMAIL PROTECTED] > > The K Desktop Environment The KDevelop Project > http://www.kde.orghttp://www.kdevelop.org
