KDE3.1beta2 packages and Liquid
Hi, I recently installed the 3.1beta2 packages and I'm quite happy with them so far, finally some KDE packages that installed smoothly on my Woody :-) There's just one minor problem, namely the Liquid theme. I had to recompile it to make it work with the packages and now it seems that some parts aren't redrawn correctly. The background of toolbar buttons and the parts of the menu bar that contain no text aren't filled with the same pattern as the rest of the background but with the color I chose for normal button background. I think it's a problem with the new Qt version because the theme worked fine with Beta2 compiled from CVS using Woody's own Qt. Is there anybody having the same problem and knowing a workaround? Or maybe a patch to get it working correctly? It seems that MOSFET has discontinued development (again). Bye, Michael -- "Beware of bugs in the above code. I have only proven it correct, not tested it." -- Donald Knuth
Building kde 3.0.3 on ppc box
Hi,
I downloaded the sources of kde 3.0.3 from:
deb http://people.debian.org/~schoepf/kde3/woody ./
My box is running testing, but for safeties sake, I built a chroot
partition running woody to build the kde 3.0.3 sources. Everything
went fine with the exception of the build/install of kdeadmin.
In kdeadmin, there is an application for lilo which is not needed for
ppc box. In the control file:
Package: kcmlilo
Section: admin
Architecture: i386
Depends: ${shlibs:Depends}
Suggests: lilo
Replaces: lilo-config
Conflicts: lilo-config
Description: KDE Frontend for lilo configuration
kcmlilo is a KDE based frontend to the lilo boot manager configuration.
It runs out of the KDE Control Center.
However, when I run dpkg-buildpackage in the kdeadmin directory
I get the following error:
/bin/sh ../libtool --mode=install /usr/bin/install -c -p secpolicy
/home/jas/kde/kdeadmin/kdeadmin-3.0.3/debian/tmp/usr/bin/secpolicy
/usr/bin/install -c -p secpolicy
/home/jas/kde/kdeadmin/kdeadmin-3.0.3/debian/tmp/usr/bin/secpolicy
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory
`/home/jas/kde/kdeadmin/kdeadmin-3.0.3/obj-powerpc-linux/secpolicy'
make[2]: Leaving directory
`/home/jas/kde/kdeadmin/kdeadmin-3.0.3/obj-powerpc-linux/secpolicy'
make[2]: Entering directory
`/home/jas/kde/kdeadmin/kdeadmin-3.0.3/obj-powerpc-linux'
make[3]: Entering directory
`/home/jas/kde/kdeadmin/kdeadmin-3.0.3/obj-powerpc-linux'
make[3]: Nothing to be done for `install-exec-am'.
*** Important *
add /usr/bin to your PATH
Please report bugs with our web form at
http://bugs.kde.org.
Stephan Kulow <[EMAIL PROTECTED]> and all the KDE
developers wish you fun with the KDE.
make[3]: Leaving directory
`/home/jas/kde/kdeadmin/kdeadmin-3.0.3/obj-powerpc-linux'
make[2]: Leaving directory
`/home/jas/kde/kdeadmin/kdeadmin-3.0.3/obj-powerpc-linux'
make[1]: Leaving directory
`/home/jas/kde/kdeadmin/kdeadmin-3.0.3/obj-powerpc-linux'
dh_install
cp: cannot stat `debian/tmp/usr/lib/kde3/kcm_lilo.la': No such file or
directorydh_install: command returned error code
make: *** [install] Error 1
There is no file kcm_lilo.la which shouldn't be because we are only
supposed to build kcmlilo on i386. Is there anyway to fix the above
error. This is the first time I have built packages from source, so
not that familiar with how to correct above errors.
Thanks,
John Schmidt
Re: Comparing Debian KDE 3.1 Beta 2 packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 07 October 2002 2:23 pm, Yenar Calentaure wrote: > http://download.kde.org/unstable/kde-3.1-beta2/Debian/woody/ Can someone fill me in on the correct sources.list line - this doesn't find the packages file - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9odjDuFHxcV2FFoIRApd2AJ4nD+bhk4F0mBOCKrPkIjg7e3AsdQCglpxo XarN3lhivGi0WQa1xaxvkHw= =gDu5 -END PGP SIGNATURE-
Re: disabling portmap with KDE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 07 October 2002 18:57, Alexei Kaminski wrote: > Hi all, > > I use KDE and would prefer not to have portmap running on my machine. > However > > kdelibs3 depends on libfam0 which recommends fam which depends on portmap > > so installing KDE leads to installation of portmap. I wonder what is the > proper way to disable portmap while still keeping KDE. I edited > /etc/init.d/portmap so that it never starts. Is it a proper way? Does it > cripple KDE anyhow? Are there better ways? I have libfam0 installed, but not fam or portmap, for just this reason. libfam0 only recommends fam, so I think you should be okay if you run: apt-get remove portmap This will probably remove portmap and fam. KDE should still work. You might also like to install the 'harden' package. (see apt-cache show harden). Regards, Paul Cupis - -- [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9odBiIzuKV+SHX/kRAp5wAJwMr1stjv7b4f8OqWKJFfbYhJrhqwCggCvI LzmC+0Lu9QKtMi11YdahiJA= =nX/t -END PGP SIGNATURE-
disabling portmap with KDE
Hi all, I use KDE and would prefer not to have portmap running on my machine. However kdelibs3 depends on libfam0 which recommends fam which depends on portmap so installing KDE leads to installation of portmap. I wonder what is the proper way to disable portmap while still keeping KDE. I edited /etc/init.d/portmap so that it never starts. Is it a proper way? Does it cripple KDE anyhow? Are there better ways? Thank you. Alexei Kaminski
Re: KDE packages (3.0.4 and 3.1)
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 :-)) I already rearranged my packages build to use apt-source root directory, so it can be uploaded without changes next time. I'll hopefully provide packages next week (a HEAD snapshot). 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 I have 4.1 (stock woody version), antialiasing and everything works fine. Err, qt 3.1 (beta 2 probably, i use qt-copy). Oh, do you have woody installation? Do you still need my builds or should i give up on them? 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 ? :-) The debian background is nice, isn't it? But i'd appreciate better debian logo for kdm logo area (the one provided is bit rough imho). 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. Cool, i will test them as well :). 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 :-) Your effort is much appreciated, thanks. Ralf -- --- inetname: Yenar Calentaure realname: Peter Rockai mail: yenar(at)host.sk homepage: http://yenar.host.sk --- The universe is entering maintenance mode in 2 minutes. Please logout. -- Your administrator ---
Re: Comparing Debian KDE 3.1 Beta 2 packages
Mark Purcell wrote: Seems like we have a choice now :-) Has anyone compared the two sets of Debian KDE 3.1 Beta 2 packages? Ralf's http://download.kde.org/unstable/kde-3.1-beta2/Debian/woody/ These are collective effort of debian-kde developers, but are built from post-beta2 snapshot. or Karolina's http://shakti.ath.cx/debian/kde3.1-beta2/ These are forked off the ones above. They use different kdelibs packaging, so they are upgrade-incompatible with former. Apart from the way they are packaged is there any difference between these sets? And that one is built for woody and one for sid. Are people getting good results on both? I used first set (i compiled them actually) with good enough results (there are some issues naturally, esp. with noatun/arts and korganizer, probably others). I cannot comment about Karolinas set, i only know they once had problems with .la files but i believe this was solved. There are chances that the Karolina's way of packaging kdelibs will be used in official debs, but i don't really know. Anyway, first set is what will go into sid when they are complete and when gcc-3.2 transition is over. Mark yenar -- --- inetname: Yenar Calentaure realname: Peter Rockai mail: yenar(at)host.sk homepage: http://yenar.host.sk --- The universe is entering maintenance mode in 2 minutes. Please logout. -- Your administrator ---
Comparing Debian KDE 3.1 Beta 2 packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Seems like we have a choice now :-) Has anyone compared the two sets of Debian KDE 3.1 Beta 2 packages? Ralf's http://download.kde.org/unstable/kde-3.1-beta2/Debian/woody/ or Karolina's http://shakti.ath.cx/debian/kde3.1-beta2/ Apart from the way they are packaged is there any difference between these sets? And that one is built for woody and one for sid. Are people getting good results on both? Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9oXK8oCzanz0IthIRAqt8AJ4r9WTwF5wUK/M8gI9DgwZG+riAywCePGyG UwBEjpgslb1vA9+R8QuZR2c= =Dle4 -END PGP SIGNATURE-
probs with 1 file in 2 packages
Hi, I have a problem with kdesktop and kcontrol In both packages is the file /usr/share/applnk/Settings/Desktop/filetrash.desktop So I get this error when I apt-get kdesktop (Lese Datenbank ... 116078 Dateien und Verzeichnisse sind derzeit installiert.) Entpacke kdesktop (aus .../kdesktop_4%3a3.0.8-1_i386.deb) ... dpkg: Fehler beim Bearbeiten von /var/cache/apt/archives/kdesktop_4%3a3.0.8-1_i386.deb (--unpack): versuche »/usr/share/applnk/Settings/Desktop/filetrash.desktop« zu überschreiben, welches auch in Paket kcontrol ist dpkg-deb: Unterprozess paste getötet mit Signal (Datenübergabe unterbrochen (broken pipe)) Fehler traten auf beim Bearbeiten von: /var/cache/apt/archives/kdesktop_4%3a3.0.8-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) How can I fix this? My sources.list deb http://ftp.de.debian.org/debian testing main contrib non-free deb-src http://ftp.de.debian.org/debian testing main contrib non-free deb http://ftp.de.debian.org/debian-non-US testing/non-US main deb-src http://ftp.de.debian.org/debian-non-US testing/non-US main deb http://kde3.geniussystems.net/debian-3.0.8 ./ deb http://people.debian.org/~bab/kde3 ./ deb http://ftp.freenet.de/pub/ftp.vpn-junkies.de/openoffice/ unstable main contrib deb http://www.opensides.be/debian/woody/kde3 ./ May be too many kde2 sources? Ciao! juh
Re: Problem with konqueror 3.1beta2 and a website
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 07 October 2002 10:48 am, Rob Lensen wrote: > Hello, > > I just installed the kde3.1beta2 packages and they are working fine. > But this http://forum.bsdfreaks.nl forum ain't working well. > It worked in kde3.0. I made a screenshot what it is look like > http://www.bsdfreaks.nl/files/forum.png > The problem is that the text is displayed outside the forum (as you see > on the screenshot) > Is this a bug in konqueror or is it a bug in the website? Galeon and > mozilla have no problems with this. > I would check the page with the validator at www.w3c.org first. If you have kdeaddons installed then konq should have a menu option in the tools menu. If it doesn't validate then there isn't much point in filing a bug with KDE. I would complain to the website though with a link to the validator test. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9oVvzYsCKa6wDNXYRAt8hAJ9MxXhwUdqwAhS4aXujY7Dj7KSBQgCfU5x0 I7W76Qx6YqcOzsNectbPP1o= =md7k -END PGP SIGNATURE-
Problem with konqueror 3.1beta2 and a website
Hello, I just installed the kde3.1beta2 packages and they are working fine. But this http://forum.bsdfreaks.nl forum ain't working well. It worked in kde3.0. I made a screenshot what it is look like http://www.bsdfreaks.nl/files/forum.png The problem is that the text is displayed outside the forum (as you see on the screenshot) Is this a bug in konqueror or is it a bug in the website? Galeon and mozilla have no problems with this. Greetings Rob Lensen -- **> Never let a computer see you hurry. <** __ /*-Rob Lensen[EMAIL PROTECTED]-*\ __ \ '/ Enschede, The Netherlands\' / \/http://www.bsdfreaks.nl \/
Re: Debian 3.0 Khelpcenter Glossary empty
> Dear users of Debian 3.0 with KDE, > > I've installed Debian 3.0r0 with KDE 2.2.x on my PC. When I call the > Khelpcenter, all the topics in the "Contents" tab are there but the > "Glossary" tab is empty except for the two sub-section headers > "Alphabetically" and "By topic". Has anybody else encountered this and > found a solution for it? > > Best regards, > > Dirk. I've found myself a solution for this by installing all KDE packages recommended in /usr/share/doc/kde/README.debian and the package htdig. Best regards, Dirk. -- *** Dirk Kostrewa Paul Scherrer Institut E-mail: [EMAIL PROTECTED] Life Sciences, OSRA/007 Phone: +41-56-310-4722 CH-5232 Villigen PSI Fax: +41-56-310-4556 Switzerland Internet: http://www.sb.psi.ch ***
[OT] Redirection with CGI (was: Re: KDE 3.2-beta2)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 29 September 2002 09:26 am, Paul Cupis wrote: > print 'HTTP/`1.0 302 Found' > print 'Location: ', newuri' [I realize the original problem has now been solved (hooray!), and anyway, apt doesn't like 30x status codes, however they are generated.] This is totally off-topic, but I feel compelled to share this, as I spent many years in painful ignorance of the following, until just recently when I actually sat down and read the CGI spec. You do not have to have your CGI program output a raw HTTP header just to change the status code. You may instead use the "Status" header to set the status code, and any CGI 1.1 compliant web server will translate this into the appropriate HTTP header, (i.e. "Location: 302 Found" will cause Apache to change the header to "HTTP/1.1 302 Found"). The relevent part of the CGI spec is: http://CGI-Spec.Golux.Com/draft-coar-cgi-v11-03-clean.html#7.2 This means you do not have to worry about figuring out how to get your web server to allow raw headers, like naming your CGI with some wierd prefix (which messes up your carefully crafted URI naming scheme)... Yay! Ok, so now that I have totally abused this list, I will crawl off and get some sleep... - -- Nathaniel W. Turner http://www.houseofnate.net/ Tel: +1 508 579 1948 (mobile) "Mamma Mia! Here I go again // My, my! How can I resist you?" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9oReX25cAeUrFyDIRAhfiAJ9AAeOgvLpqdTmkZUCYrSX+i8z70QCgzFYT D15JAOq/f1U+yUm8CDVYehQ= =ema4 -END PGP SIGNATURE-
