why kde and gnome's menu situation sucks
Debian should follow the lead of every other major distro and offer the exact same menu layout throughout. -- http://debianplanet.net/node.php?id=831 I cannot help but shudder when I read that comment in this negative Debian review. We *led* the way: we wrote menu, we put everything in menu, we made every window manager (even twm, for crying out loud!) use menu. And then gnome and kde came along, and we threw all that out the window. No excuses: This stinks. We should be able to do much better. -- see shy jo pgpCxpO430p5B.pgp Description: PGP signature
Re: KMail Folder Disappeared!?!?!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 21 October 2002 1:47 am, Oracle Administrator wrote: One of my folders had about 4500 messages in it and suddenly disappeared this afternoon. I question that is truly vanished because when I try to recreate the folder the attempt fails. A dialog appears that tells me I do not have sufficient permissions to complete the operation. I suspect that it may simply not be shown in my folder list. Any ideas? So in ~/Mail what are the permissions on the files (if mbox) or directories (if maildir) [and what are the permisssions on ~/Mail itself - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9s5hGuFHxcV2FFoIRAqMxAJ40ljfF3LY+gqQFIYuHvb1A0HSgDwCdFvG6 4LK7aA/sNFZq+hocare3YEI= =bz02 -END PGP SIGNATURE-
Re: koffice-dev what should it contain
On Sunday 20 October 2002 23:35, Alan Chandler wrote: I have installed koffice-dev with the objective of trying to build kpresenter without the rest of koffice source. (So I can understand the code) However, I have found that kozoomhandler.h is not within the this library. It is stored in kde cvs under koffice/libs/kotext You will need the source-package for koffice to build the koffice apps themselves. The -dev package is for other programs linking to koffice libraries. Try 'apt-get source koffice' instead. Alex.
Re: dpkg installation of kde 3.0.4
tomas pospisek wrote: On Sat, 19 Oct 2002, John Schmidt wrote: I compiled the kde 3.0.4 for my powerpc box based on Ralph Nolden's source files on the kde.org site. I installed them using dpkg -i *.deb selecting the debs I wanted. Now when I go and use aptitude to update my testing box, I get messages indicating that the kde files I just installed are slated to be removed. Now did I mess up by doing installations via dpkg -i instead of apt-get? If so, is there any way to fix this or do I need to move all the debs to /var/cache/apt/archives and use a apt-get install? I don't know about aptitude but I'm pretty sure you can find out by looking at the explanation of apt/aptitude (maybe using some options that give you more info). I know that dselect will tell you why it wants to remove things. I find aptitude to be similar enough to deselect not to be alien but far better enough to easily make the switch. When you are on the list screen after pressing 'g' and you see the packages aptitude wants to delete you can figure out what the problem is by looking at the dependencies and reverse dependencies on those packages. This is something that dselect can't do, IIRC. 'd' will give you dependencies, 'r' will give you the reverse dependencies (packages that depend on this one). You can then see the unsatisified dependencies which if necessesary can be examined themselves to see their dependencies, dependencies can be viewed recursively. Unmet dependencies are listed in red. There will be something there to explain the problem, I've always been able to figure out the problem this way.
Re: KDE3 - Debian/experimental distribution proposal (was: yes i am alive ;)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 20 Oct 2002 23:01, Ben Burton wrote: And so I will nevertheless stick with the main point of my previous post which was, if we're going to use experimental, to argue for very clear documentation to be available on just what to do with APT configuration before any experimental KDE3 packages are announced. It is a good point, and does warrant some documentation prior to any 'release', that said it is not that disimilar to the current situation with 'woody' users wanting to use versions of applications which are only in unstable. The current recommendation is to use pinning so that the whole of the unstable tree isn't uploaded. Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9s9bpoCzanz0IthIRAuqKAKCPMFZMtmPnaj8hDawpn5w8DEGMOQCfS6kj 54ziYHrVA7johl0L7VqLH3k= =lKxz -END PGP SIGNATURE-
KDE3.1 compilatoin error
I have compiled qt-copy and KDEsupport on my box(Debian woody 3.0) but arts gives this error: Making all in qtmcop make[2]: Entering directory `/home/tester/KDE/arts/qtmcop' /bin/sh ../libtool --silent --mode=link --tag=CXX g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -pedantic -W -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -O2 -fno-exceptions -fno-check-new -ftemplate-depth-99-o libqtmcop.la.closure libqtmcop_la_closure.lo -no-undefined -version-info 1:0 -R /home/tester/KDE/lib -R /usr/lib -R /usr/X11R6/lib -L/usr/lib -L/usr/X11R6/lib qiomanager.lo ../mcop/libmcop.la -lqt-mt -lpng -lz -lm -lXext -lX11 -lSM -lICE -lpthread libtool: link: warning: `-version-info' is ignored for programs .libs/qiomanager.o: In function `Arts::QIOWatch::staticMetaObject(void)': .libs/qiomanager.o(.text+0xd12): undefined reference to `QMetaObject::new_metaobject(char const *, QMetaObject *, QMetaData const *, int, QMetaData const *, int, QMetaProperty const *, int, QMetaEnum const *, int, bool (*)(QObject *, int, int, QVariant *), QClassInfo const *, int)' .libs/qiomanager.o: In function `Arts::QIOWatch::qt_static_property(QObject *, int, int, QVariant *)': .libs/qiomanager.o(.text+0xe95): undefined reference to `QMetaObject::qt_static_property(QObject *, int, int, QVariant *)' .libs/qiomanager.o: In function `Arts::QTimeWatch::staticMetaObject(void)': .libs/qiomanager.o(.text+0xfc2): undefined reference to `QMetaObject::new_metaobject(char const *, QMetaObject *, QMetaData const *, int, QMetaData const *, int, QMetaProperty const *, int, QMetaEnum const *, int, bool (*)(QObject *, int, int, QVariant *), QClassInfo const *, int)' .libs/qiomanager.o: In function `Arts::QTimeWatch::qt_static_property(QObject *, int, int, QVariant *)': .libs/qiomanager.o(.text+0x1141): undefined reference to `QMetaObject::qt_static_property(QObject *, int, int, QVariant *)' .libs/qiomanager.o: In function `__static_initialization_and_destruction_0': .libs/qiomanager.o(.text+0x11a8): undefined reference to `QMetaObjectCleanUp::QMetaObjectCleanUp(char const *, QMetaObject *(*)(void))' .libs/qiomanager.o(.text+0x11c7): undefined reference to `QMetaObjectCleanUp::QMetaObjectCleanUp(char const *, QMetaObject *(*)(void))' collect2: ld returned 1 exit status make[2]: *** [libqtmcop.la.closure] Error 1 make[2]: Leaving directory `/home/tester/KDE/arts/qtmcop' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/tester/KDE/arts' make: *** [all] Error 2 any idea?
Re: koffice-dev what should it contain
Sorry about the format of this post, I am at work and only got the web archives and outlook to play with :-( I think this reply misunderstands what I am doing. I HAVE downloaded the source of koffice (not the debian source, but from the kde CVS), and I am now trying to cut it back so that I am left with the minimal amount of source, and maximum binary from previously downloaded .debs (from kde.org). The question I am asking is what is in koffice-dev - with respect to the koffice libraries that are distributed with the source. I deliberately cut away koffice/libs directory and then tried to build kpresenter. Within the source there is a line #include kozoomhandler.h which fails because there is no such file in /usr/include. However, since in the source its in koffice/lib/kotext (A general looking sort of library) - I sort of assumed that it was supposed to be in koffice-dev I did try looking in koffice/debian/rules to see if I could figure how koffice-dev was built - but I am not very knowledgable about how this works, and this attempt defeated me. Hence asking here. What your post doesn't quite explain is why would other programs NOT want to utillise to kozoomhandler. I know I am doing something completely unofficial - but I thought I would ask for two reasons 1) Just so I know 2) To question whether the package had actually been built correctly - ie the lack of this library was a deliberate decision rather than an accident. If I could get a clear statement, I'll just restore the missing directory(ies) and proceed (I am using a local CVS to store my changes so I should be able to revert them) = On Sunday 20 October 2002 23:35, Alan Chandler wrote: I have installed koffice-dev with the objective of trying to build kpresenter without the rest of koffice source. (So I can understand the code) However, I have found that kozoomhandler.h is not within the this library. It is stored in kde cvs under koffice/libs/kotext You will need the source-package for koffice to build the koffice apps themselves. The -dev package is for other programs linking to koffice libraries. Try 'apt-get source koffice' instead. -- Alan Chandler This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
Re: koffice-dev what should it contain
2) To question whether the package had actually been built correctly - ie the lack of this library was a deliberate decision rather than an accident. The debian koffice-dev package provides all of the headers that are installed in a default koffice installation. If you look in koffice/lib/kotext/Makefile.am, you'll see the line that would install these headers has been commented out (and has been since the initial CVS commit). I'm asking now on the koffice list to find out why. Ben. -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] If your thesis is utterly vacuous, / Use first-order predicate calculus. / With sufficient formality / The sheerist banality / Will be hailed by the critics: Miraculous! - Anon.
compiling kde-apps without --prefix=/usr
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi list, i will compile, install and use ;) a kde-application that not in the official woody. (kile). when i make the normal procedure ./configure make su make install then my computer installs the binarys under the /usr/local/kde file-hierarchie. that's ok and imho standard. but in my kde-menu i can't find an entry like kile to run the program. under the console i can run the program with /usr/local/kde/bin/kile but without many of the pictures and without menu i think, that my system (woody, kde3.0.4 from kde.org) don't search in the /usr/local/kde-tree. what can i do to add these directory-structur to my system? under /etc/profile i have try the KDEDIRS=/usr/:/usr/local/kde but this don't work :( the same problem i have with kdevelop... can anybody help me? thanks - -- Gruss/Greetings Andreas Richter OSZine - Das deutschsprachige Open Source Magazin (http://www.oszine.de) GnuPG-PubKey: http://www.oszine.de/gpg/ar.gpg -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9tDQrDPI8V3uhLdkRAqKaAKDCkLsHeYqlBLoPFCMndIj5Wg6hwACgi3DM PakpEyVgRQC8LqOY5zPGMQU= =gUNZ -END PGP SIGNATURE-
Re: compiling kde-apps without --prefix=/usr
Hi, if I understand it correctly, you want to separate packages from self-compiled binaries, but KDE likes to have all these things in one place ;) Just make a package. Go to the source dir of your app you want to compile and type deb-make. A directory named debian/ is being created. Call debian/rules binary and your package will be created. Any configure options you want to set, you can set in the shell script debian/rules. -- - Thomas Ritter
Re: koffice-dev what should it contain
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 21 October 2002 2:40 pm, Ben Burton wrote: 2) To question whether the package had actually been built correctly - ie the lack of this library was a deliberate decision rather than an accident. The debian koffice-dev package provides all of the headers that are installed in a default koffice installation. If you look in koffice/lib/kotext/Makefile.am, you'll see the line that would install Well, I've got to revert back to my version before I deleted this - but thanks for your help anyway. - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9tEIduFHxcV2FFoIRAgYOAJ9/FLikjYf+H7pv6CqYdslC5UrI2wCfWxrF 0USZOmLBgT+X+8PjgHMTXK0= =zh8l -END PGP SIGNATURE-
Re: compiling kde-apps without --prefix=/usr
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 21. Oktober 2002 19:23 schrieb Thomas Ritter: if I understand it correctly, you want to separate packages from self-compiled binaries, but KDE likes to have all these things in one place ;) Just make a package. Go to the source dir of your app you want to compile and type deb-make. A directory named debian/ is being created. Call debian/rules binary and your package will be created. Any configure options you want to set, you can set in the shell script debian/rules. I'd rather vote for using dh_make to create the debian subdir and debuild (or dpkg-buildpackage -rfakeroot) to acutally build the package. To get something useful, he should really edit those debian/* files, e.g. to have the right description :) HS - -- Mein GPG-Key ist auf meiner Homepage verfgbar: http://www.hendrik-sattler.de oder ber pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.schulnetz.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9tD5Tzvr6q9zCwcERAkWZAKCmBrCMWD4Q+hesOgxic4MLKYHT4wCfaZvg nSqFkbOZvDvimZ0taFTT2f8= =tI0m -END PGP SIGNATURE-
kdm in HEAD package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I just noticed that the way kdm handles the background greeter settings in debian has changed to a very non-standard way of writing it's own backgroundrc into /etc/kde3/kdm/, while the way that also the control center handles things is to do this inside /etc/kde3/kdm/kdmrc. Is there a reason or intention why this got broke ? Otherwise, I'll have a look into that over the coming days (guess thursday when most of my other work is done and I only need to prepare my talks for LWE next week). Ralf - -- 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9tEQAu0nKi+w1Ky8RAqOdAKCGOJJ/60tZpvHMvO5Gc/RfDWSwggCgs+hv e2eTnTIb4+UppcOs7JbTJxU= =dbBd -END PGP SIGNATURE-
Re: kdm in HEAD package
Ralf, I am not sure, kde just does it that way, if you look at what I am doing with the build it isn't anything special. I did modify kdm/kfrontend/genkdmconf.c slightly so that it would generate a default debian config. However as far as I can tell I did not modify anything wrt a backgroundrc, it just started getting generated a few months ago. Chris On Mon, Oct 21, 2002 at 08:14:19PM +0200, Ralf Nolden wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I just noticed that the way kdm handles the background greeter settings in debian has changed to a very non-standard way of writing it's own backgroundrc into /etc/kde3/kdm/, while the way that also the control center handles things is to do this inside /etc/kde3/kdm/kdmrc. Is there a reason or intention why this got broke ? Otherwise, I'll have a look into that over the coming days (guess thursday when most of my other work is done and I only need to prepare my talks for LWE next week). Ralf
cpu optimisation
Hello, Every now and then I compile kde packages which didn't make it in the kde3 distribution (yet). I usually make debian packages out of them, which involves nothing more then configuring the thing and running dh_make and dpkg-buildpackage in the source dir; then installing the .deb package . But debian has a habit of compiling everything so that it still runs on a 386. Since I am only installing those packages on my own machine, I would like to know what to manipulate to make these packages optimised for my cpu (athlon). Thx! -- Frank Van Damme homepage: www.student.kuleuven.ac.be/~m9917684 jabber (=IM): [EMAIL PROTECTED]
OpenPGP Plugin
KMail complains when I click on certain messages with the dialog that the openpgp plugin is not installed. I am running Debian unstable and apt-get update nightly. How can I install this plugin? -- Comments and information are appreciated. Robert
Re: KMail Folder Disappeared!?!?!
On Monday 21 October 2002 06:00 pm, Alan Chandler wrote: So in ~/Mail what are the permissions on the files (if mbox) or directories (if maildir) [and what are the permisssions on ~/Mail itself drwx--S---4 oracle oracle 4096 2002-10-21 17:34 Mail -rw---1 oracle oracle 3022742791 2002-10-20 20:12 Data I don't have an Oracle database installed. The user is called 'oracle' as I will install Oracle with the user oracle as the dba. KMail is set to use store mail in directories (maildir files). The maildir file the corresponds to the 'vanished' directory exists and can be cat'ed to view the contents. From this, I reason that the maildir file needs to be imported back into KMail to restore the directory. -- Comments and information are appreciated. Robert
Re: OpenPGP Plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 21 October 2002 23:34, Oracle Administrator wrote: KMail complains when I click on certain messages with the dialog that the openpgp plugin is not installed. I am running Debian unstable and apt-get update nightly. How can I install this plugin? That's quite complicated and is not yet available as a deb package. It is included in the Ägypten project that is connected to the S/MIME stuff. http://www.gnupg.org/aegypten/ -- Comments and information are appreciated. Robert - -- 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9tMwyu0nKi+w1Ky8RApRtAKCyFLgUzsQOLmX/yOUn5SQl/SD4bQCcDfqt skDWxAUvMx2UCwP2vbKUmr8= =a/4b -END PGP SIGNATURE-
