Re: kdeinit and ksmserver won't start
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > After trashing my .kderc directory in a vain attempt to reset KDE, I have > lost all ability to use X. > > When I startx, the graphic Liquid splash screen pops up. Two dialogs > appear in order: Cannot start kdeinit and cannot start the ksmserver. Then > I am dumped back into the console. > > I've tried deleting as many KDE apps and libraries as I could and then > re-installing them. No luck. I think I need to delete the entire KDE > distribution and reinstall from the beginning. > > I hope someone has ideas about how to expedite this process. Anyone? > > Bob This looks like something is not installed... Are you sure you have kdebase,kdebase-bin,kdelibs and kdelibs-bin installed. try: apt-get install kdebase kdebase-bin kdelibs kdelibs-bin and see if something is missing Jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9o5pYhDaJ7BNOdRURAvNhAKDS4Uc4tmZxkSfZFKgKBUtaY6hkvwCdHZ66 8DTiPzr5y3RjSXIU7xkQ2b0= =cW9Q -END PGP SIGNATURE-
kdeinit and ksmserver won't start
After trashing my .kderc directory in a vain attempt to reset KDE, I have lost all ability to use X. When I startx, the graphic Liquid splash screen pops up. Two dialogs appear in order: Cannot start kdeinit and cannot start the ksmserver. Then I am dumped back into the console. I've tried deleting as many KDE apps and libraries as I could and then re-installing them. No luck. I think I need to delete the entire KDE distribution and reinstall from the beginning. I hope someone has ideas about how to expedite this process. Anyone? Bob
KDE3.1 beta2 package conflicts (log included)
Hi. I'm running an up to date sid system, and I have been using (with great pleasure) Karolina's KDE3.1-beta1 packages for some time now. I decided to upgrade to the KDE3.1-beta2 packages that I believe she created - I apt-got them ;) from http://shakti.ath.cx/debian/kde3.1-beta2. I have some conflicts with the new packages that I cannot resolve by any apt method I've tried. It looks as though libarts1, libarts1-dev, and kdelibs4-bin are using files that are part of the KDE3.1-beta1 packages. Any suggestions are appreciated. log follows: [EMAIL PROTECTED]:~$ sudo apt-get -f install Reading Package Lists... Done Building Dependency Tree... Done Correcting dependencies... Done The following extra packages will be installed: libartsflow-data libartsflow1 libkutils1 libmcop1 libsoundserver-bin libsoundserver-data libsoundserver1 The following NEW packages will be installed: libartsflow-data libartsflow1 libkutils1 libmcop1 libsoundserver-bin libsoundserver-data libsoundserver1 0 packages upgraded, 7 newly installed, 0 to remove and 109 not upgraded. 14 packages not fully installed or removed. Need to get 0B/1089kB of archives. After unpacking 4727kB will be used. Do you want to continue? [Y/n] y Reading changelogs... (Reading database ... 90738 files and directories currently installed.) Unpacking libkutils1 (from .../libkutils1_4%3a3.0.8.cvs20020930-1.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libkutils1_4%3a3.0.8.cvs20020930-1.2_i386.deb (--unpack): trying to overwrite `/usr/lib/libkutils.so.1.1.0', which is also in package kdelibs4-bin dpkg-deb: subprocess paste killed by signal (Broken pipe) Unpacking libmcop1 (from .../libmcop1_1.1.0.cvs20020926-1.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libmcop1_1.1.0.cvs20020926-1.2_i386.deb (--unpack): trying to overwrite `/usr/lib/libgmcop.so.1.0.0', which is also in package libarts1-dev dpkg-deb: subprocess paste killed by signal (Broken pipe) Unpacking libartsflow-data (from .../libartsflow-data_1.1.0.cvs20020926-1.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libartsflow-data_1.1.0.cvs20020926-1.2_i386.deb (--unpack): trying to overwrite `/usr/lib/mcop/Arts/DataHandlePlay.mcopclass', which is also in package libarts1 Unpacking libartsflow1 (from .../libartsflow1_1.1.0.cvs20020926-1.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libartsflow1_1.1.0.cvs20020926-1.2_i386.deb (--unpack): trying to overwrite `/usr/lib/libartsflow.so.1.0.0', which is also in package libarts1 dpkg-deb: subprocess paste killed by signal (Broken pipe) Unpacking libsoundserver-data (from .../libsoundserver-data_1.1.0.cvs20020926-1.2_all.deb) ... dpkg: error processing /var/cache/apt/archives/libsoundserver-data_1.1.0.cvs20020926-1.2_all.deb (--unpack): trying to overwrite `/usr/lib/mcop/Arts/FileInputStream.mcopclass', which is also in package libarts1 Unpacking libsoundserver-bin (from .../libsoundserver-bin_1.1.0.cvs20020926-1.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libsoundserver-bin_1.1.0.cvs20020926-1.2_i386.deb (--unpack): trying to overwrite `/usr/bin/artscat', which is also in package libarts1-bin dpkg-deb: subprocess paste killed by signal (Broken pipe) Unpacking libsoundserver1 (from .../libsoundserver1_1.1.0.cvs20020926-1.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libsoundserver1_1.1.0.cvs20020926-1.2_i386.deb (--unpack): trying to overwrite `/usr/lib/libartsgslplayobject.so.0.0.0', which is also in package libarts1 dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libkutils1_4%3a3.0.8.cvs20020930-1.2_i386.deb /var/cache/apt/archives/libmcop1_1.1.0.cvs20020926-1.2_i386.deb /var/cache/apt/archives/libartsflow-data_1.1.0.cvs20020926-1.2_i386.deb /var/cache/apt/archives/libartsflow1_1.1.0.cvs20020926-1.2_i386.deb /var/cache/apt/archives/libsoundserver-data_1.1.0.cvs20020926-1.2_all.deb /var/cache/apt/archives/libsoundserver-bin_1.1.0.cvs20020926-1.2_i386.deb /var/cache/apt/archives/libsoundserver1_1.1.0.cvs20020926-1.2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [EMAIL PROTECTED]:~$ Nathan Waddell
Re: KMail, pgp5 and gpg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 08 October 2002 12:20, Pablo de Vicente wrote: > El Martes 8 de Octubre de 2002 12:02, David Pashley escribió: > > On Tuesday 08 October 2002 10:49 am, Pablo de Vicente wrote: > > > Hello, > > > > > > I have run into some trouble with KMail, gpg and pgp5i. I will > > > expose the case: > > > > > > I usually use pgp5i and have exported my public key to a > > > keyserver. Before doing that I checked that using PGP5i in > > > different machines and with different identities KMail worked > > > fine, detecting the validity of signatures. > > > > > > The problem arises when people who only use GnuPG import my > > > public key from the keyserver. All emails from my address appear > > > in Red in their Mail folders and with a "Warning: The signature > > > is bad" message. These people use, under KMail -> Settings -> > > > Security -> OpenPGP option "Select encryption tool to use: > > > GnuPG". > > > > I can confirm that this does happen in KDE 3.1beta2. Unfortunately, it's not possible to fix this incompatibility between PGP5i and GnuPG. The problem is that PGP5 doesn't create proper clearsigned messages. We work around this problem by creating the clearsigned messages in KMail by combining the message text and the signature PGP5 returns. This works with all versions of PGP which I have tested (2.6, 5, 6.5.8). Unfortunately GnuPG barfs on these messages. But PGP5i is anyway very broken and you should really not use it anymore. You should consider using GnuPG instead. > > > If the previous option is set to: "Autodetect", then the email > > > will appear in yellow with a "The validity of the signature can't > > > be verified" message. > > > > > > However if one only uses KMail with PGP5 (for which one imports > > > my public key from the keyserver) the emails appear in green and > > > with a "The signature is valid and the key is fully trusted" > > > message. > > > > > > Is there some kind of incompatibilty between GnuPG and PGP5i?. Yes. See above. > > > Is this a KMail problem which, when using GnuPG does not > > > recognize the validity of messages signed with PGP5i?. See above. ;-) > "PGP 5.0i isn't able to clearsign a message if this message > contains 8-bit characters (like german umlauts). Therefore the > developers of KMail programmed a work around. The message is first > signed with a detached signature and then a clearsigned message is > composed as follows:" Hmm, that's more or less what I wrote above. ;-) > "... If a mail (or something else) you want to sign contains 8-bit > characters PGP 5.0i always generates a type 0x00 signature (a > signature of a binary document). Therefore GnuPG can't handle it > correctly (and it doesn't have to)" Hmm, that sounds familiar. I guess it does because I wrote it. :-) Regards, Ingo -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9o2EOGnR+RTDgudgRAr8RAKDWK/5zuJEOSn/ouep4wM95x4nDWACfcK6k E3U8jaIf75UtmdkVanZtIrY= =zbTT -END PGP SIGNATURE-
Re: KDE packages (3.0.4 and 3.1)
On Tuesday 08 October 2002 16:50, Mark Purcell wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Mon, 7 Oct 2002 03:05, Ralf Nolden wrote: > > 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 :-)) > > Hi Ralf, Thanks for your efforts with KDE 3.1beta2! No, it was Yenar who created them. I just uploaded them through my ftp account on ktown, that's where the Packages stuff went wrong because I didn't know they required all the subdirectories. I hope my versions of 3.0.4 went right, we'll see when the announcement is made and downloads can start :-)) Ralf > > You don't have to put the packages into subdirectories. You just need to > regenerate the Packages and Sources files in that directory: > > $ dpkg-scanpackages . override | gzip > Packages.gz > $ dpkg-scansources . | gzip > Sources.gz > > Mark > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.0 (GNU/Linux) > > iD8DBQE9ovDKoCzanz0IthIRAqgBAJ92WfoKxs6ujMnDLuF9qRBCcx3VwwCfUZRw > Tk1XNbGkKWm3NphePKeXwqg= > =ifzm > -END PGP SIGNATURE- -- We're not a company, we just produce better code at less costs. Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org
Re: Noatun
> Noatun segfaults on startup and the noatun-plugins wants to uninstall > most of kde. What does apt-get tell you when it tries to uninstall kde? Which versions of noatun-plugins and kdelibs4 are you trying to install? Ben. -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] Pretty is never beautiful. - Tori Amos, Bay Area Musician, 3/11/97
Re: Comparing Debian KDE 3.1 Beta 2 packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > If you and Ralf are building the first set then you should really change > the Maintainer: header in debian/control otherwise calc and Ivan will be > receiving queries against your package builds. Unless they know about this > of course. Yenar and Ralf's packages are using the debian/ dirs in KDE CVS, which the various maintainers are using for their own development. Thus I'd personally rather remain in the maintainer: field, since I'd like to get these bug reports so I can find out what I've screwed up. :) Ben. - -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] A man cannot be too careful in the choice of his enemies. - Oscar Wilde, The Picture of Dorian Gray -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9o11kMQNuxza4YcERAm/tAKChSEgUjWCcDn9SxiUbZTK/nzfxcwCfQglm mlMA/fwQkLIbuo6sMM9+kag= =+tqQ -END PGP SIGNATURE-
gwenview-0.15.0-1
Hi all, the 0.15.0 version of gwenview is released. I have uploaded the new version to http://www.stud.uni-karlsruhe.de/~udsv/debian/unstable/ Because I have messed up the last version number you are forced to install it manually by downloading the package and using dkpg -i Sorry for that, I'll be more careful next time. This package uses KDE3.0.3 so you need the unoffical packages. As this package is unoffical it may eat your cat and/or your harddisk so use it at your own risk and so on ... Any comments about the packages are appreciated. Cheers Michael
Re: Comparing Debian KDE 3.1 Beta 2 packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 08 October 2002 1:45 pm, Yenar Calentaure wrote: > Alan Chandler wrote: > > -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 > > I'm afraid there is no such thing. See mail by Ralf Nolden entitled "KDE > Packages (3.0.4 and 3.1)" from 6.10.2002. You can wget them and move > into right directory or regenerate Packages file. I see no other > solutions :(. Good idea - except seeing the message about 3.0.4 I am now nervous, since these were announced as 3.0.8 and I wouldn't want to get my version numbers all tangled up. - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9oyswuFHxcV2FFoIRAvhTAKCncF1E0jDRjJN/k3cpbYyNs1WA3wCeIzT+ umqIQrTNRX2wKkdauQAsPKE= =UtdD -END PGP SIGNATURE-
Re: KDE 3?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 08 October 2002 19:11, Gianfranco Berardi wrote:
> My roommate is using Mandrake on his system, so he has KDE 3.0. I am
> using Woody, but I tried to apt-get install kde, and I got version 2.*
> instead of 3.0.
> Is it not packaged yet? Do I have to download/compile it myself? Not
> that it would be a problem, but I am just wondering if I am going about
> it all wrong by expecting it to be apt-get-able.
KDE 3 is not part of Debian 3.0 'Woody' and never will be. Futher, KDE 3 is
not in Debian proper, as it is stalled waiting for the Debian development
branch ('sid') to convert to using gcc 3.2 as the default compiler.
However, unofficial KDE 3 packages are available, and there are a set of
packages available for Woody.
These packages, whilst they reportedly work well, are experimental and
unofficial.
You can get the KDE 3 packages for Woody by adding
deb http://people.debian.org/~schoepf/kde3/woody ./
To your /etc/apt/sources.list and following the instructions in the FAQ at
http://www.davidpashley.com/debian-kde/faq.html
You are also advised to read/search the list archives at
http://lists.debian.org/debian-kde for advice/information.
If you have read all the above information but are still having trouble
installing KDE 3, either join the #debian-kde IRC channel on irc.debian.org
(Freenode/OPN) or mail this list (debian-kde@lists.debian.org) will a full
and verbose explanation of your situation and the problem you are
encountering.
Regards,
Paul Cupis
- --
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9oyVzIzuKV+SHX/kRAp2qAJ4lHtRl2g2Ww2CVzfXpBvd8m6iqsACfdzA3
EPoPosDzJIF0jL6d7UsZqWY=
=UxNZ
-END PGP SIGNATURE-
Re: KDE 3?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 08 October 2002 20:11, Gianfranco Berardi wrote: # My roommate is using Mandrake on his system, so he has KDE 3.0. I am # using Woody, but I tried to apt-get install kde, and I got version 2.* # instead of 3.0. # Is it not packaged yet? Do I have to download/compile it myself? Not # that it would be a problem, but I am just wondering if I am going about # it all wrong by expecting it to be apt-get-able. # Thanks, # Gianfranco # # Hi, I had the same problem and also someone else did too, in the answer (which I will forward) are some links and I installed kde3 on woody without any problems:http://mypage.bluewin.ch/kde3-debian/ . This is the link I used, but there are some more. You could try to search the archives too. Regards Matej Here is the original message: Fwd: RE: How to upgrade from kde2 to kde3 - -- Forwarded Message -- Subject: RE: How to upgrade from kde2 to kde3 Date: Fri, 04 Oct 2002 10:32:11 +1000 From: "Joyce, Matthew" <[EMAIL PROTECTED]> To: Cc: "'debian-kde@lists.debian.org'" , "'debian-user@lists.debian.org'" These links maybe of interest too. http://lists.debian.org/debian-kde/2002/debian-kde-200209/msg00133.html http://mypage.bluewin.ch/kde3-debian/ Certainly I followed the instructions in the second link, in the General section, and it worked for me. Matthew Joyce - -Original Message- From: David Pastern [mailto:[EMAIL PROTECTED] Sent: Friday, 4 October 2002 9:37 AM To: 'suresh kumar sharma' Cc: 'debian-kde@lists.debian.org'; 'debian-user@lists.debian.org' Subject: RE: How to upgrade from kde2 to kde3 Suresh, That's a huge task I found. But worth it. I'm not really the best person technically to help you with this, but...i'd be disrepectful to the kind others on this list that helped me get kde3 working on my system. So i'll give it a bash - pun intended(bash = aussie slang for 'give it a try). 1. Firstly edit your /etc/apt/sources.list file to include the line: deb http://people.debian.org/~schoepf/kde3/woody ./ Make sure you do it exactly like that. Also, if you have multiple CD lines in there, i'd comment them out using your favourite editor. Just put a # in front of the lines starting with deb cdrom... 2. Then remove kde 2.2 from your system. Firstly, to check what packages are on your system try this: dpkg -l | grep 2.2.2 Note that *not* everything with the output of this command will be for kde - it looks for 2.2.2. 95% was for me though. Try this command to remove the current kde on your system: apt-get --remove purge libarts kde* It mostly worked for me, leaving a few left other kde files. I don't know if that will work for you or not. Each system is inherently different. At this point i'd run the dpkg -l | grep 2.2.2 command again at a term to see *what is left*. I had several files left to remove and Thomas Schoepf from the KDE user lists kindly made up a shell script to help me remove the rest of the files (I wasn't totally sure what could go and what should stay). I've attached the shell script to this email, i'd *strongly* suggest reading the shell script' contents and comparing that to what packages for kde you might have left on your system (and obviously editing the shell script to suit your needs). Please note that with the shell script attached you will need to: chmod u+x and then run it as ./purge202.sh (just in case you didn't know that - i'd rather give *too* much information than not enough) Hopefully after this, all kde 2.2.2 files will have been removed from your system. We can now try to update to kde 3.0.3. Please note that with Thomas' .debs you will not need to go down the testing/unstable route. You can keep the default setting of stable for woody, and there will be no need to create a /etc/apt/preferences file or pinning etc. Please also note that QT is included with Thomas' kde packages, so no need to have that (qt 3) on your system. I'm not sure what the outcome would be if you have already installed qt on your system. 3. We can now and try to upgrade to kde 3.0.3. Try this command at the command line please. apt-get update Once that is done we can try: apt-get -d dist-upgrade Now I found that this didn't work for me...so Thomas suggested using dselect to do the job. And I switched to dselect. This is the instructions Thomas gave to me on using dselect: "1. start dselect (obvious) 2. select [A]ccess and verify that "apt" is selected. (Pressing "X" exits that screen again, losing changes) 3. Run [U]pdate. If the .debs are still in /var/cache/apt/archives, apt will not download them again. If there are errors, please show them to me. 4. Choose [S]elect (pressing the Space key will get you out of the help screen, but that's described in the help itself, of course :) ) 5. Hit Enter. If there are any dependency problems, dselect will show a screen telling you that (hit Space again to get out). Now you should see the
KDE 3?
My roommate is using Mandrake on his system, so he has KDE 3.0. I am using Woody, but I tried to apt-get install kde, and I got version 2.* instead of 3.0. Is it not packaged yet? Do I have to download/compile it myself? Not that it would be a problem, but I am just wondering if I am going about it all wrong by expecting it to be apt-get-able. Thanks, Gianfranco
Re: kdevelop
On the last episode (Tuesday 08 October 2002 12:07), Arash Bijanzadeh wrote: > Hi! > I am using KDE3.0.3 on woody 3.0 and I want to have kdevelop on it but > I am getting a version conflict. Where can I find a new peraps testing > package of kdevelop ? >From a mantainer's message: I am not doing much work on the package at the moment. However I did recently upload a new version to http://people.debian.org/~njordan/kde3.0/ You can use the apt-get lines deb http://people.debian.org/~njordan kde3.0/ deb-src http://people.debian.org/~njordan kde3.0/ Ciao, Paolo -- If Linux is not Unix then Windows are not Gates Anonymous, XXI Century
Re: KDE packages (3.0.4 and 3.1)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 7 Oct 2002 03:05, Ralf Nolden wrote: > 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 :-)) Hi Ralf, Thanks for your efforts with KDE 3.1beta2! You don't have to put the packages into subdirectories. You just need to regenerate the Packages and Sources files in that directory: $ dpkg-scanpackages . override | gzip > Packages.gz $ dpkg-scansources . | gzip > Sources.gz Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9ovDKoCzanz0IthIRAqgBAJ92WfoKxs6ujMnDLuF9qRBCcx3VwwCfUZRw Tk1XNbGkKWm3NphePKeXwqg= =ifzm -END PGP SIGNATURE-
Re: Comparing Debian KDE 3.1 Beta 2 packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 7 Oct 2002 23:23, Yenar Calentaure wrote: > > Ralf's http://download.kde.org/unstable/kde-3.1-beta2/Debian/woody/ > 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. If you and Ralf are building the first set then you should really change the Maintainer: header in debian/control otherwise calc and Ivan will be receiving queries against your package builds. Unless they know about this of course. Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9ouAgoCzanz0IthIRAjbSAJ0VOTnGDeZwe75yyQaG2N4rJRM4LACgmVeB yvJjJm/OVNNvf22gCPycP9g= =/ZBK -END PGP SIGNATURE-
Re: Comparing Debian KDE 3.1 Beta 2 packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 8 Oct 2002 22:45, 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 > > I'm afraid there is no such thing. See mail by Ralf Nolden entitled "KDE > Packages (3.0.4 and 3.1)" from 6.10.2002. You can wget them and move > into right directory or regenerate Packages file. I see no other > solutions :(. It is a pretty straight forward process to regenerate the correct Packages file: dpkg-scanpackages . override | gzip > Packages.gz dpkg-scansources . | gzip > Sources.gz If you have access a local mirror of the packages you can generate those two files and email them to the kde.org guys to put on the kde.org server. However, I notice that all the Debian packages of 3.1beta2 seem to of left download.kde.org. Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9ot9doCzanz0IthIRAgOlAJ44YSpraga9HmsDYh6xSynOnZOQygCgmeUa 6MOZqwiz9EcM22ZpBq0394c= =btUP -END PGP SIGNATURE-
Re: kdevelop
A Dimarts 08 Octubre 2002 12:07, Arash Bijanzadeh va escriure: > Hi! > I am using KDE3.0.3 on woody 3.0 and I want to have kdevelop on it but I am > getting a version conflict. Where can I find a new peraps testing package > of kdevelop ? The only way that I have found to run Kdevelop on kde 3.0.3 on woody have been download it from CVS http://www.kdevelop.org/index.html?filename=branches_compiling.html use the KDE_2_2_BRANCH, follow the steps and that's ok. Leo
KDE Can't Start
I use KDE 3.1b2. I made a mistake last night while trying to fix a problem where KMail would continually crash after opening. Even after editing the kmailrc file (something about the path to openpgp was causing the problem...), I could not use KMail. My first thought was to delete the .kderc directory and let all of the preference files be regenerated. Wrong idea. Now KDE can't start at all and complains about missing scripts. I'm going to try doing an "update-alternatives --config x-window-manager" after work today, try using a different window manager, and hope that fixes my problem. In the meantime, can anyone suggest possible causes of this problem? Thanks, Bob
Re: Problem with konqueror 3.1beta2 and a website
David Pashley wrote: 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. IMHO it is worth filing a bug. It indicates a layouting bug (if mozilla renders it ok) or ie/moz incompatibility. Just send the url exposing the bug to bts, it should be fine. IMHO. Btw. only really small subset of www validates against validator.w3.org. If khtml was limited to this, it would be unusable. I'm afraid noone cares about standards (at least not enough to check their html code). - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -- --- 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
Alan Chandler wrote: -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 I'm afraid there is no such thing. See mail by Ralf Nolden entitled "KDE Packages (3.0.4 and 3.1)" from 6.10.2002. You can wget them and move into right directory or regenerate Packages file. I see no other solutions :(. - -- Alan Chandler [EMAIL PROTECTED] 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 ---
Re: KMail, pgp5 and gpg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Off-topic but for your interest to finish this thread: >... > Conclusion: > - This is off-topic, but how can I migrate my keys to GnuPG? > - Do I need to revoke my keys in the public keyserver and create new ones?. It is not necessary to revoke the keys because it is possible to migrate from PGP5i to GnuPG using the same keys from the PGP5i keyring. If somebody is interested I can send how I have done it. thanks, Pablo de Vicente -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9osPfSItUpHl6kJERApVzAKCxzkHXCKuI/GW7ea38gBzw4h7mGgCdHKkm rhqtdMQlPSXPYLXDVT5XYPE= =9lfI -END PGP SIGNATURE-
Noatun
Is this not for use in KDE3.0.3 (on sid/unstable)? Noatun segfaults on startup and the noatun-plugins wants to uninstall most of kde. Anders der..
kdevelop
Hi! I am using KDE3.0.3 on woody 3.0 and I want to have kdevelop on it but I am getting a version conflict. Where can I find a new peraps testing package of kdevelop ?
Re: KMail, pgp5 and gpg
-BEGIN PGP SIGNED MESSAGE- El Martes 8 de Octubre de 2002 12:02, David Pashley escribió: > On Tuesday 08 October 2002 10:49 am, Pablo de Vicente wrote: > > Hello, > > > > I have run into some trouble with KMail, gpg and pgp5i. I will expose > > the case: > > > > I usually use pgp5i and have exported my public key to a keyserver. > > Before doing that I checked that using PGP5i in different machines and > > with different identities KMail worked fine, detecting the validity of > > signatures. > > > > The problem arises when people who only use GnuPG import my public key > > from the keyserver. All emails from my address appear in Red in their > > Mail folders and with a "Warning: The signature is bad" message. These > > people use, under KMail -> Settings -> Security -> OpenPGP option > > "Select encryption tool to use: GnuPG". > > I can confirm that this does happen in KDE 3.1beta2. > > > If the previous option is set to: "Autodetect", then the email will > > appear in yellow with a "The validity of the signature can't be verified" > > message. > > > > However if one only uses KMail with PGP5 (for which one imports my public > > key from the keyserver) the emails appear in green and with a "The > > signature is valid and the key is fully trusted" message. > > > > Is there some kind of incompatibilty between GnuPG and PGP5i?. Is this a > > KMail problem which, when using GnuPG does not recognize the validity of > > messages signed with PGP5i?. > > > > On the other hand Kmail works fine the other way round, that is messages > > signed with GnuPG are correctly verified. > > > > Any ideas? > > Have you emailed [EMAIL PROTECTED] They are the KMail developers. they > should be able to help you more. No, I have not mailed them, but I am going to CC them this message. but I have found looking for it at Google that there IS a compatibility problem: "PGP 5.0i isn't able to clearsign a message if this message contains 8-bit characters (like german umlauts). Therefore the developers of KMail programmed a work around. The message is first signed with a detached signature and then a clearsigned message is composed as follows:" "... If a mail (or something else) you want to sign contains 8-bit characters PGP 5.0i always generates a type 0x00 signature (a signature of a binary document). Therefore GnuPG can't handle it correctly (and it doesn't have to)" Conclusion: - This is off-topic, but how can I migrate my keys to GnuPG? - Do I need to revoke my keys in the public keyserver and create new ones?. thanks in advance, Pablo de Vicente. -BEGIN PGP SIGNATURE- Version: PGPfreeware 5.0i for non-commercial use MessageID: O/nROO2dr1O4AtY5KFE9Uc5HLEeTk4PA iQA/AwUBPaKxW0iLVKR5epCREQIGdgCeM7azjj1oFLP4u+uKPF35GIdl4IwAoKyR WJ/wmInc0sqm+dNTf5igbHru =QqhG -END PGP SIGNATURE-
Re: KMail, pgp5 and gpg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 08 October 2002 10:49 am, Pablo de Vicente wrote: > Hello, > > I have run into some trouble with KMail, gpg and pgp5i. I will expose the > case: > > I usually use pgp5i and have exported my public key to a keyserver. Before > doing that I checked that using PGP5i in different machines and with > different identities KMail worked fine, detecting the validity of > signatures. > > The problem arises when people who only use GnuPG import my public key > from the keyserver. All emails from my address appear in Red in their Mail > folders and with a "Warning: The signature is bad" message. These people > use, under KMail -> Settings -> Security -> OpenPGP option "Select > encryption tool to use: GnuPG". > I can confirm that this does happen in KDE 3.1beta2. > If the previous option is set to: "Autodetect", then the email will appear > in yellow with a "The validity of the signature can't be verified" message. > > However if one only uses KMail with PGP5 (for which one imports my public > key from the keyserver) the emails appear in green and with a "The > signature is valid and the key is fully trusted" message. > > Is there some kind of incompatibilty between GnuPG and PGP5i?. Is this a > KMail problem which, when using GnuPG does not recognize the validity of > messages signed with PGP5i?. > > On the other hand Kmail works fine the other way round, that is messages > signed with GnuPG are correctly verified. > > Any ideas? Have you emailed [EMAIL PROTECTED] They are the KMail developers. they should be able to help you more. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9oq04YsCKa6wDNXYRArgBAKCdlMcgZ8PJ8z561azf9qnnTWWAzQCgmRE2 jQzZFDZxVBNjWMH1jg3Tb+8= =Lbsk -END PGP SIGNATURE-
KMail, pgp5 and gpg
-BEGIN PGP SIGNED MESSAGE- Hello, I have run into some trouble with KMail, gpg and pgp5i. I will expose the case: I usually use pgp5i and have exported my public key to a keyserver. Before doing that I checked that using PGP5i in different machines and with different identities KMail worked fine, detecting the validity of signatures. The problem arises when people who only use GnuPG import my public key from the keyserver. All emails from my address appear in Red in their Mail folders and with a "Warning: The signature is bad" message. These people use, under KMail -> Settings -> Security -> OpenPGP option "Select encryption tool to use: GnuPG". If the previous option is set to: "Autodetect", then the email will appear in yellow with a "The validity of the signature can't be verified" message. However if one only uses KMail with PGP5 (for which one imports my public key from the keyserver) the emails appear in green and with a "The signature is valid and the key is fully trusted" message. Is there some kind of incompatibilty between GnuPG and PGP5i?. Is this a KMail problem which, when using GnuPG does not recognize the validity of messages signed with PGP5i?. On the other hand Kmail works fine the other way round, that is messages signed with GnuPG are correctly verified. Any ideas? Pablo de Vicente. -BEGIN PGP SIGNATURE- Version: PGPfreeware 5.0i for non-commercial use MessageID: BS2TIf27uBlIHFXSqOHkx4HLS4m+jkER iQA/AwUBPaKqQkiLVKR5epCREQKbsgCeIze34+vRYoXdBZtHRTYtD1wVNS4AnRri Qw/P43ZbiiXYQ62ZcXhoAyLW =p6dB -END PGP SIGNATURE-
