Re: imlib and libpng
"Steve M. Robbins" <[EMAIL PROTECTED]> writes: > About the new SONAME for imlib. It would be nice if we had > cooperation across distributions about this. I've emailed upstream a > few times over the the last month or two about picking a standard > soname, but have heard nothing back. For their "rawhide", RedHat went > ahead and linked in libpng3 *without* changing the SONAME. So I think > we can kiss cross-distribution compatibility goodbye. Note that we went to some care to maintain the ABI of gdk_imlib, by forcing it to load libpng with private symbols. For plain imlib, my basic sentiment is that it's barely maintained, deprecated, not used by many things, and not a very good library... its non-maintenance is why this problem exists, since the real solution here is for upstream to release a parallel-installable new version that uses libpng3. Still the soname probably should be incremented. I can do that still, rawhide is just a beta, it's not released. Havoc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sick and tired of the little font boxes
On Saturday 13 July 2002 14:04, Andy Saxena wrote: > On Tue, Jul 09, 2002 at 08:26:26PM -0500, Peter Clark wrote: > > I don't understand this at all: I cannot get the fonts to display > > properly in KDE. Most of the TrueType and all of the Type1 fonts come out > > as boxes. I'm running KDE 3.0.2 and xfs-xtt 1.3.0 (i.e., the latest). > > Anti-aliasing is enabled. (Although disabling doesn't help anything.) > > There are only an odd handful of fonts that work, all of which are the MS > > fonts. The odd thing is that everything looks fine under GNOME. I've > > tried nuking my ~/.kde directory, but to no avail. What gives? > > > > :Peter > > Are you using version 4 or later of X? Yes; I'm using the very latest from sid. (Not the 4.2 experimental ones, however.) > What does Section "Module" say in your /etc/X11/XF86Config-4 file? Section "Module" Load"ddc" Load"dbe" Load"extmod" Load"glx" Load"pex5" Load"record" Load"xie" Load"bitmap" Load"freetype" Load"speedo" Load"type1" Load"vbe" Load"int10" EndSection > If you are using version 4 or later of X, you could try disabling > xfs-xtt to see if the font display changes. To disable xfs-xtt just remove > the 7110 FontPath entry. Instead of using xfs X will use the FontPath > entries directly. I just tried this (again). First I just commented out the 7110 FontPath part, exited KDE, hit Alt-E in kdm to restart X, logged back into KDE, opened up the Control Panel, looked at the fonts: little boxes. So then I entered '/etc/init.d/xfs-xtt stop', verified that it was stopped, exited, restarted X, logged back in--and still got little boxes. I've similarily played with turning anti-aliasing on and off, but nothing works. What's driving me mad is that all the fonts work just fine in GNOME, so it _should_ work in KDE. For the record, here also is the "Files" section of my XFConfig-4 file: Section "Files" # FontPath "unix/:7110" FontPath "/usr/share/fonts/truetype" FontPath "/usr/share/fonts/truetype/openoffice" FontPath "/usr/share/fonts/truetype/thryomanes" FontPath "/usr/share/fonts/type1/gsfonts" FontPath "/usr/lib/X11/fonts/misc" FontPath "/usr/lib/X11/fonts/cyrillic" FontPath "/usr/lib/X11/fonts/100dpi:unscaled" FontPath "/usr/lib/X11/fonts/75dpi:unscaled" # FontPath "/usr/lib/X11/fonts/TrueType" # FontPath "/usr/lib/X11/fonts/Type1" FontPath "/usr/lib/X11/fonts/Speedo" EndSection (Note that the I just commented out the last two entries for TrueType and Type1 fonts; I've tried those paths as well, and all that happens is that I get duplicate fonts that are displayed as boxes.) :Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Recompile Quanta for KDE3
I think you need cvs version to make it compile with kde3. I'm not 100% sure, but this is what I have done and it works great. Instructions at: http://sourceforge.net/forum/forum.php?thread_id=686946&forum_id=12422 // Erik -- Don't worry, tomorrow won't be a better day ! Erik Johansson <[EMAIL PROTECTED]> http://come.to/erre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Recompile Quanta for KDE3
On Saturday 13 July 2002 22:34, Andreas Schuldei wrote: > what keeps you from installing kdelibs-dev? kdelibs-dev is not installable on my system because it depends on kde2.2-packages. I already installed kdelibs4-dev, but this did not solve my problem. Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: imlib and libpng
lördagen den 13 juli 2002 22.39 skrev Steve M. Robbins: > The only consensus that emerged is: if imlib changed from PNG2 to > PNG3, then the imlib SONAME should change. In the interests of the > woody freeze, nothing has happened yet: imlib, and anything that links > to it, is using libpng2. > > However, the KDE folks are increasingly impatient to use imlib with > png3. It's time to update imlib, so I'm looking for ideas. When i needed imlib, I simply rebuilt it with libpng3. If you change the soname, you have to rebuild 129 packages. If you keep the soname, you have to rebuild 18 packages. It looks like a continuing debian nightmare like we experienced this spring with KDE. If it was so hard to find someone to rebuild just KDE. How will it then be to find maintainers to rebuild all those 129 packages? Anyway, the solution is to have unofficial packages that are rebuilt for libpng3 for those who does not like such nightmares. :-) Not that I worry, I rebuild those I need myself. It is often a quite fast business. It is also often needed, since so many packages want to deinstall KDE3 or libpng3. Some debian maintainers continually rebuild packages, to keep late active versions in unstable. I have to send my big appreciation to those people. -- Karolina -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
imlib and libpng
Hi, Back in January, libpng version 3 was released. This PNG library happens to be linked into several libraries (e.g. imlib and qt2). It is also linked into many applications which also link to imlib or qt2. Such an application will fail if the PNG library version it links with is different than the PNG library that imlib or qt2 links with. A fair bit of discussion was generated at the time, e.g. http://lists.debian.org/debian-devel/2002/debian-devel-200201/msg2.html The only consensus that emerged is: if imlib changed from PNG2 to PNG3, then the imlib SONAME should change. In the interests of the woody freeze, nothing has happened yet: imlib, and anything that links to it, is using libpng2. However, the KDE folks are increasingly impatient to use imlib with png3. It's time to update imlib, so I'm looking for ideas. Given that the SONAME for imlib will change, the two versions of imlib will be able to be installed in parallel, and so no existing packages will break. I'm not sure what to do about the -dev package, though. If I just switch it to png3, then almost surely some packages will fail to build or, once built, fail to run. I guess I could prevent them from building by declaring the new imlib-dev to conflict with libpng2-dev. If that happens, the packages in question will not build until their maintainer fixes up the build-deps. In unstable/main, of the 129+2 source packages (main+contrib) that build-depend on imlib (there are no such packages in non-free nor non-us), I find just 18 that also build-depend on libpng2. At first blush, it seems that the number of affected packages is rather small. On the other hand, among the packages that link with imlib are some libraries. It is conceivable that one of THOSE may be used along with libpng2 in some other binary. While that 18 is only a lower bound of the number of affected packages, it seems small enough that my plan (tentatively) is: 1. Notify the maintainers of these 18, then 2. upload the changed imlib packages (the -dev packages conflicting with libpng2-dev). If porting a package to libpng3 proves infeasible, I'm willing to upload an "imlib+png2-dev" package. About the new SONAME for imlib. It would be nice if we had cooperation across distributions about this. I've emailed upstream a few times over the the last month or two about picking a standard soname, but have heard nothing back. For their "rawhide", RedHat went ahead and linked in libpng3 *without* changing the SONAME. So I think we can kiss cross-distribution compatibility goodbye. My feeling at the moment is to just change the current "libImlib.so.1" to "libImlib.so.1.1" (or "libImlib.so.1.png3" maybe). If there is a policy or precedent for this, I'd be happy to hear about it. I welcome any feedback, -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Recompile Quanta for KDE3
* Stefan Rotsch ([EMAIL PROTECTED]) [020713 19:52]: > Hi all, > > I am running unstable and the current unofficial KDE 3.0.2 packages. I would > like to compile quanta 2.0.1, but building fails: > > dpkg-checkbuilddeps: Unmet build dependencies: kdelibs-dev (>> 4:2.2.0) > dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting. > dpkg-buildpackage: (Use -d flag to override.) > > Any hints? what keeps you from installing kdelibs-dev? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: audio io slave, ogg, and incorrect bitrates.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=141092&repeatmerged=yes Exactly 100 days old :) Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sick and tired of the little font boxes
On Tue, Jul 09, 2002 at 08:26:26PM -0500, Peter Clark wrote: > I don't understand this at all: I cannot get the fonts to display > properly in > KDE. Most of the TrueType and all of the Type1 fonts come out as boxes. I'm > running KDE 3.0.2 and xfs-xtt 1.3.0 (i.e., the latest). Anti-aliasing is > enabled. (Although disabling doesn't help anything.) There are only an odd > handful of fonts that work, all of which are the MS fonts. The odd thing is > that everything looks fine under GNOME. I've tried nuking my ~/.kde > directory, but to no avail. What gives? > :Peter > > Are you using version 4 or later of X? What does Section "Module" say in your /etc/X11/XF86Config-4 file? If you are using version 4 or later of X, you could try disabling xfs-xtt to see if the font display changes. To disable xfs-xtt just remove the 7110 FontPath entry. Instead of using xfs X will use the FontPath entries directly. -Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Recompile Quanta for KDE3
Hi all, I am running unstable and the current unofficial KDE 3.0.2 packages. I would like to compile quanta 2.0.1, but building fails: dpkg-checkbuilddeps: Unmet build dependencies: kdelibs-dev (>> 4:2.2.0) dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting. dpkg-buildpackage: (Use -d flag to override.) Ignoring the build dependencies will cause make to exit: make[3]: *** [grepdialog.o] Error 1 make[3]: Leaving directory `/home/rotsch/quanta-2.0.1/quanta/dialogs' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/rotsch/quanta-2.0.1/quanta' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/rotsch/quanta-2.0.1' make: *** [all-recursive-am] Error 2 Any hints? Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
audio io slave, ogg, and incorrect bitrates.
I'm really confused. I tried ripping and encoding a CD with the audio io slave in kde, and it worked. BUT, the bitrate was consistently above 400 kbits per second, when the average should have been 192. This is really strange. Any ideas? At that bitrate I might as well use FLAC. I know this post might be more appropriate on kde dev, but I thought that I'm probably just doing something stupid. Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Gideon snapshot packages available for Debian, homepage comment, CVS
On Sat, 13 Jul 2002, Tamas Nagy wrote: > The first round of Gideon snapshots packages (CVS 2002-07-12) for Debian > are available at http://mypage.bluewin.ch/kde3-debian/ . How stable is Gideon? Is Gideon "selfhosting" (i.e. Gideon developers developing in Gideon). *t Tomas Pospisek SourcePole - Linux & Open Source Solutions http://sourcepole.ch Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: VMware interaction with screensaver
The question for people here is running kde 3.0 debs going to give you a lock _without_ vmware. Having had a lock in the past (kde 2.2, IIRC), I think this could be likely. Where is the lock, on the big-screen or virtual? Fred Ollinger ([EMAIL PROTECTED]) CCN sysadmin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Gideon snapshot packages available for Debian, homepage comment, CVS
Hello, The first round of Gideon snapshots packages (CVS 2002-07-12) for Debian are available at http://mypage.bluewin.ch/kde3-debian/ . If there is any interest for these, then I consider to update the packages regularly... If you like, you could indicate these packages at www.kdevelop.org Download sites as "Debian 3 (Woody) unstable packages (link)" I do not have write access to CVS, so therefore I haven't updated the Debian directory there. If sy contacts me with CVS write access, I glad to share the updated Debian files... Best regards and keep walking;) Tamas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: VMware interaction with screensaver
Hi, just to answer a few of the questions. I am using the XFree86 4.2 pre1v1 packages, the KDE 3.0.2 packages and debian unstable. As far as I know there are no VMware debs, I was referring to the KDE version. I am using VMware 3.1.1 build-1790. I have also just found the /usr/bin/kdesktop_lock process running and after killing this the screensaver/lock button will work again. I have just run VMware windowed and full screen and the button still works... Maybe something happens after the screensaver timeout if VMware is running at the time. I'll have to wait and see. Regards, Simeon -- Simeon Walker, email: [EMAIL PROTECTED] School of Biological Sciences, phone: +44 (0)1248 383702 University of Wales, Bangor,fax: +44 (0)1248 382569 Gwynedd, LL57 2UW, UK. www: http://biology.bangor.ac.uk/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Fw:problem starting kde
Thanks to your answer, I have half resolved the problem : I forgot to install x-window-system and its dependances. Now twm works fine as before, but not yet kde. I hope to solve the problem soon. Eric __ first message : Hello, I'm a beginner with Debian which I like already a lot. I did a basic installation of woody with only kde and its dependances. When the system boots, I get the message "starting K desktop manager : done", then the login in text mode and no kde. With a precedent installation with xfree86, xdm and twm, the graphical environment worked fine. I feel it's perhaps a problem of X configuration because I was not asked during this latter intallation to tell my kind of graphics hardware despite the fact that xfree86 has been installed. Thanks for answer, Eric Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 /mn) ; tél : 08 92 68 13 50 (0,34/mn)" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
