html documentation for kde
Is there any use for the kde documentation in html format, that some packages generate? kdeaddons-doc-html - KDE add-ons documentation in HTML format kdeedu-doc-html - KDE edutainment documentation in HTML format kdesdk-doc-html - docs in html format for the KDE Software Development Kit kdetoys-doc-html - KDE toys documentation in HTML format koffice-doc-html - KDE Office Suite documentation in HTML format It is not something that KDE is using, and all the documentation is available from within the programs and from the khelpcenter. It is just that you can also get the documentation through a web browser, over the web server or locally. It might be useful for some, but is it useful enough to warrant separate packages for it? Right now only some of the kde modules have documentation in this way, and some have not. I think that either they should all have it, or these packages should all go. If they are valuable, then it is the question if there should be localized versions of the documentation in html too? I think these html files just clutter up the installations, and that someone might install them not knowing if they are needed or not, just in case, so better get rid of them. Those few who want them can very easily generate them. Or is it someone who think they should stay? -- Karolina
Re: html documentation for kde
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there any use for the kde documentation in html format, that some packages generate? These are all from the modules that I maintain. It is not something that KDE is using, and all the documentation is available from within the programs and from the khelpcenter. It is just that you can also get the documentation through a web browser, over the web server or locally. I created these packages because there are people who use other desktop environments with just the odd KDE app here or there (just as I use the odd GNOME app here or there but don't want the whole GNOME installation filling up my hard disk). In this sense, there's no guarantee that (say) a kword user would have khelpcenter or even konqueror. If they don't have some native KDE app that can read in the docbook files directly, then they have no way to view the documentation. Hence the -doc-html packages. This way they can read them in usual HTML format (and even get at them through the usual doc-base interface). Note that they're not dependencies of koffice/kdeedu/etc, so the hard-core KDE user who installs all the metapackages (and presumably has khelpcenter) won't get them by default. It might be useful for some, but is it useful enough to warrant separate packages for it? The alternative is to bundle them in with kword, kspread, etc., and have the usual KDE users complain about all this extra HTML documentation that they don't want. This is why they're separate packages. Right now only some of the kde modules have documentation in this way, and some have not. I think that either they should all have it, or these packages should all go. Well I'm not taking them out simply because hard-core KDE users don't want them. They can just opt not to install them. :) If they are valuable, then it is the question if there should be localized versions of the documentation in html too? Well, I initially provided english docs because I didn't want to create lots and lots of small packages and I didn't want to make these packages excessively large since they're primarily for users who don't *want* lots of KDE stuff on their system. This at least offers the courtesy of having some docs that you can view; of course this does not address the issue of whether you can understand them. Not sure what the best plan is there. I think these html files just clutter up the installations, and that someone might install them not knowing if they are needed or not, just in case, so better get rid of them. Well, you could say this about half the packages in debian. This is why we have metapackages (koffice, kdeedu, etc), and this is why they're not dependencies of the metapackages. Those few who want them can very easily generate them. Well, no. Those few who want them are presumably the ones who don't use KDE much and have no idea what meinproc is. Or is it someone who think they should stay? /me raises his hand. Oh, and when I first started providing them I got a personal thank-you from a user, so make that two. :) Ben. :) - -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] Your gay mathematics! You're probably hard at work on some homosexual theorem that will overthrow Christianity! Some toroidal (the most suspect of all geometries) topology that will in all its sinister proof, destroy precious family values!! - Flipper to me on the theology boards -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9k/lSMQNuxza4YcERAsi1AKCBZtPwAoDumbH52OGGpuF8IeM/pwCgkPxd cIR5OTVFXXHVs9a+loUmfbQ= =OYy1 -END PGP SIGNATURE-
Re: html documentation for kde
fredagen den 27 september 2002 08.23 skrev Ben Burton: /me raises his hand. Oh, and when I first started providing them I got a personal thank-you from a user, so make that two. :) Thank you for your nice answer. You have convinced me that they are useful and a good thing to have. -- Karolina
Notes utility for KDE3?
Hi there, is there any tool for KDE3 to place little stickers with notes on the desktop? I have seen this on a friend's MacOS laptop and it seems pretty useful. Is there any tool to remind you of certain dates like birthdays? Thanks in advance, Michael
Re: Notes utility for KDE3?
fredagen den 27 september 2002 13.25 skrev Michael Thaler: Hi there, is there any tool for KDE3 to place little stickers with notes on the desktop? I have seen this on a friend's MacOS laptop and it seems pretty useful. knotes make sticky yellow notes stickers for the screen. Is there any tool to remind you of certain dates like birthdays? korganizer is a personal information manager, that can do that Both applications are in the kdepim kde module -- Karolina
Re: Notes utility for KDE3?
On Fri, 2002-09-27 at 12:25, Michael Thaler wrote: is there any tool for KDE3 to place little stickers with notes on the desktop? I have seen this on a friend's MacOS laptop and it seems pretty useful. knotes. Is there any tool to remind you of certain dates like birthdays? korganizer with kalarmd (iirc you can set an alarm to start a certain time before the event). Thanks in advance, Michael np :-) -- Chris Boyle - Debian Developer (cmb) - aewm++, sapphire, xmmsarts GPG: B7D86E0F, MSN: [EMAIL PROTECTED], ICQ: 24151961, AIM: kerneloops, Yahoo: kerneloops, IRC: cmb on openprojects.net
Re: html documentation for kde
It might be useful for some, but is it useful enough to warrant separate packages for it? You can also find the documentation (but only in English) at docs.kde.org. Maybe, we should ask Lauri Watts to add the option to download a documentation in HTML format for local browsing. Cheers, Charles -- [EMAIL PROTECTED] http://www.kde-france.org
Re: html documentation for kde
From: Ben Burton [EMAIL PROTECTED] /me raises his hand. Oh, and when I first started providing them I got a personal thank-you from a user, so make that two. :) Consider this a personal thank-you from someone who sees the value of providing the html-docs for those who want them, but doesn't want them cluttering up my system. Thanks :-) derek
178 days and counting
Since KDE 3.0 was released, and still nothing in sid. -- Brad Felmey
Run kde3 from kdm
Hi all, I have installed kde3 after completely remove kde2 (/etc/kde* and $HOME/.kde* included). Now when I choose kde3 on kdm I only get a xterm, like failsafe option. I can run kde3 with startx and similar. -- Adéu. Jordi Catalán Morros
Re: html documentation for kde
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 i also appriciate the documentation packages. it would be nice if there were more of them. it is good to be able to set up docs locally so i can save the bandwidth. i know i should take the time to actually find the appropriate bug or submit one...but while we're on the topic... the html documentation doesn't contain the images that the html references. this means ugly pages. removing the links would be an editing chore. the images would increase the size of the download (but i would prefer this option). whatever is done, i'll still have the documentation, so thank you. sincerely, tim - -- Tim Wheeler [EMAIL PROTECTED] http://www.greengibberish.com/ - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9lHS8RNiK9b6/KqoRAnRkAJ4nPG4yKVe01GR6nMKtuFB+EzcPqQCdF9Bu CELfhIwYv32PS9ByrEurn+Y= =/Oze -END PGP SIGNATURE-
Re: html documentation for kde
fredagen den 27 september 2002 17.09 skrev Tim Wheeler: i know i should take the time to actually find the appropriate bug or submit one...but while we're on the topic... the html documentation doesn't contain the images that the html references. this means ugly pages. removing the links would be an editing chore. the images would increase the size of the download (but i would prefer this option). The problem is that if you pack the images with the html pages, you won't have the images in the normal kde documentation (right?). Some solutions to this would be to 1) to require installation of the html documentation 2) to have an either- or situation, either docbook or html documentation 3) to have a separate package for the images. None of the solutions are really hard to implement. But I thought the whole idea of the html documentation was to be able to use the application and get documentation without installing the kde help browser. Maybe another solution would be to simply, somehow, generate the required html documentation during package installation if required. Maybe not with one of those bluescreen questions, but with a comment if you want the html documentation, run the script generatehtmldocumentation or something like that. No extra package, no extra space, but you can still get the docs if you want to. As an alternative, there could be a kind of global switch to set if html documentation is wanted, or a special package kdehtmldocs that if present will generate the documentation during installation. That could then also take care of generating non-english language documentation in html. -- Karolina
Re: 178 days and counting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 27 September 2002 2:48 pm, Brad Felmey wrote: Since KDE 3.0 was released, and still nothing in sid. -- Brad Felmey Well you could join #debian-kde on irc.freenode.org, check out KDE from CVS and fix problems. Whie you're at it you could sort out a correct transition to GCC 3.2 in sid without breaking updates including from woody, or you could just bitch about it. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9lIPWYsCKa6wDNXYRAoFtAJ4mZb5noFhCkUFRCTqe1h/ablQrnACgiYz3 k7Ig8eY97dWx7gRUN1T6zr0= =OcOa -END PGP SIGNATURE-
Re: 178 days and counting
On Fri, 2002-09-27 at 11:14, David Pashley wrote: Well you could join #debian-kde on irc.freenode.org, check out KDE from CVS and fix problems. Whie you're at it you could sort out a correct transition to GCC 3.2 in sid without breaking updates including from woody, or you could just bitch about it. I'd rather just bitch about it, thanks. -- Brad Felmey
Re: html documentation for kde
i know i should take the time to actually find the appropriate bug or submit one...but while we're on the topic... the html documentation doesn't contain the images that the html references. this means ugly pages. Just curious: have you also installed the applications whose docs don't have images? - eg., if you don't have images for the kword docs, do you actually have kword installed? Or only koffice-doc-html? As Karolina points out, the images are part of the kword (or whatever) package itself which is why they're not also provided with the -doc-html packages. If you do have both the -doc-html and the original package (eg., kword) installed, can you let me know precise details of which application has broken docs so I can chase this down? Karolina has some interesting ideas in her last email on how to best resolve this problem, though it's 2.40am and so I feel I should sleep on them. :) Ben. -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] If this is the way Queen Victoria treats her prisoners, she doesn't deserve to have any. (Complaining at having to wait in the rain for transport to take him to prison) - Oscar Wilde
Re: Run kde3 from kdm
Jordi, Make sure you have a symlink in /usr/bin ln -s /etc/kde3/debian/startkde kde3 and then kde3 should work in kdm (3.0-3.03) the startkde in /usr/bin should also be symlinked to etc/kde3/debian/startkde. For KDE 3.1 (3.07), There is a subtle warning not to use kcontrol to modify kmrc, but that's where you can specify SessionTypes in /etc/kde3/kdm/kdmrc For KDE 3.1 (3.07) I am using startkde (symlinked as above) as I didn't get kde3 to work initially. Michael
Re: 178 days and counting
David Pashley [EMAIL PROTECTED] writes: On Friday 27 September 2002 2:48 pm, Brad Felmey wrote: Since KDE 3.0 was released, and still nothing in sid. Well you could join #debian-kde on irc.freenode.org, check out KDE from CVS and fix problems. Whie you're at it you could sort out a correct transition to GCC 3.2 in sid without breaking updates including from woody That's likely the problem that I encountered. I did a fresh woody installation. I then wanted kde3.0 and added a feed that contained it. It required libraries found only in woody/unstable (not even in available from woody/testing) so I added unstable to my sources.list, selected kde3.0 with dselect, and about four hours later, 350 new packages were installed or upgraded. kde3.0 worked great but lots of other things broke. Many apps that previously worked (e.g. sshd and dig) gave Illegal instruction after the upgrade. I've now reinstalled woody/stable and have only stable in sources.list. I'd love to install kde3.x if someone can point me to a .deb that will install it on standard woody/stable. Anyone? Thanks, Derrell
Re: 178 days and counting
I haven't tired it but there was some discussion on the list a few weeks ago and someone made kde3 for woody deb http://people.debian.org/~schoepf/kde3/woody ./ I am running kde3 on testing though with no real troubles to speak of. [EMAIL PROTECTED] wrote: David Pashley [EMAIL PROTECTED] writes: On Friday 27 September 2002 2:48 pm, Brad Felmey wrote: Since KDE 3.0 was released, and still nothing in sid. Well you could join #debian-kde on irc.freenode.org, check out KDE from CVS and fix problems. Whie you're at it you could sort out a correct transition to GCC 3.2 in sid without breaking updates including from woody That's likely the problem that I encountered. I did a fresh woody installation. I then wanted kde3.0 and added a feed that contained it. It required libraries found only in woody/unstable (not even in available from woody/testing) so I added unstable to my sources.list, selected kde3.0 with dselect, and about four hours later, 350 new packages were installed or upgraded. kde3.0 worked great but lots of other things broke. Many apps that previously worked (e.g. sshd and dig) gave Illegal instruction after the upgrade. I've now reinstalled woody/stable and have only stable in sources.list. I'd love to install kde3.x if someone can point me to a .deb that will install it on standard woody/stable. Anyone? Thanks, Derrell
Re: 178 days and counting
I've now reinstalled woody/stable and have only stable in sources.list. I'd love to install kde3.x if someone can point me to a .deb that will install it on standard woody/stable. Anyone? deb http://people.debian.org/~schoepf/kde3/woody ./ apt-get update apt-get install kdebase apt-get install arts apt-get install kdelibs and kdenetwork / kdegraphics / kde-i18n etc . Guess this is what you want ;-) Bye Michael
Re: 178 days and counting
On Friday 27 September 2002 18:25, Brad Felmey wrote: On Fri, 2002-09-27 at 11:14, David Pashley wrote: Well you could join #debian-kde on irc.freenode.org, check out KDE from CVS and fix problems. Whie you're at it you could sort out a correct transition to GCC 3.2 in sid without breaking updates including from woody, or you could just bitch about it. I'd rather just bitch about it, thanks. -- Brad Felmey Or you could try some other distro. A lot a debian people have left because debian isn't that cool anymore because all the new software is missing. Try gentoo it is source based but has most of the latest available source code. Or mandrake, I have found that the new version 9.0 is very usable. Bastiaan
RE: 178 days and counting
I don't think the reason why one would choose Debian was ever to have always the latest packages without any hassle You choose Debian because it is 1337 :)) -Original Message- From: Bastiaan Naber [mailto:[EMAIL PROTECTED] Sent: Friday, September 27, 2002 7:33 PM To: debian-kde@lists.debian.org Subject: Re: 178 days and counting On Friday 27 September 2002 18:25, Brad Felmey wrote: On Fri, 2002-09-27 at 11:14, David Pashley wrote: Well you could join #debian-kde on irc.freenode.org, check out KDE from CVS and fix problems. Whie you're at it you could sort out a correct transition to GCC 3.2 in sid without breaking updates including from woody, or you could just bitch about it. I'd rather just bitch about it, thanks. -- Brad Felmey Or you could try some other distro. A lot a debian people have left because debian isn't that cool anymore because all the new software is missing. Try gentoo it is source based but has most of the latest available source code. Or mandrake, I have found that the new version 9.0 is very usable. Bastiaan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] __ Gesendet von Yahoo! Mail - http://mail.yahoo.de Yahoo! präsentiert als offizieller Sponsor das Fußball-Highlight des Jahres: - http://www.FIFAworldcup.com
Re: 178 days and counting
what happens on a Debian system when you compile from source? I have run in succession 3.0 alpha, 3.0beta, 3.1 alpha and now 3.1beta (or for you purests 3.0.7) All built from tarballs on the dread RH. I have never had the slightest difficulty with KDE on RH unless it was something of my own doing but for reasons I will not go into on this list, I am switching to Debian. Since I am a gnome blows kinda guy and require, no insist that I have KDE and in the 3.0 family running on debian woody. I have no experience with .deb or any other debian tools. never liked RPMs for that matter and have always built my packages from source. What say you fellows? source? will there be issues? On Fri, 27 Sep 2002 19:33:09 +0200 Bastiaan Naber [EMAIL PROTECTED] wrote: On Friday 27 September 2002 18:25, Brad Felmey wrote: On Fri, 2002-09-27 at 11:14, David Pashley wrote: Well you could join #debian-kde on irc.freenode.org, check out KDE from CVS and fix problems. Whie you're at it you could sort out a correct transition to GCC 3.2 in sid without breaking updates including from woody, or you could just bitch about it. I'd rather just bitch about it, thanks. -- Brad Felmey Or you could try some other distro. A lot a debian people have left because debian isn't that cool anymore because all the new software is missing. Try gentoo it is source based but has most of the latest available source code. Or mandrake, I have found that the new version 9.0 is very usable. Bastiaan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 178 days and counting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Freitag, 27. September 2002 19:36 schrieb [EMAIL PROTECTED]: woody/unstable (libc3.x maybe? I don't remember.) that were dependencies. Because you wrote that often enought now: woody is not unstable or testing but the current stable, maybe you should take a look at http://www.debian.org to get this right: woody == current stable sarge == current testing sid == always unstable It is annoying and hard to track what you mean when you mix this up completely. BTW: I don't understand why most unstable packages are not in unstable anymore. KDE3.x ist left out because of gcc3.2, although it does not make much sense: if it breaks on transistion to gcc3.2- well, it's unstable. Same with XFree4.2. What's the difference to make the gcc change with or without KDE3 in unstable? It compiles with gcc2.95 and troubles with gcc3.2 are expected anyway. Sorry, but it does not make much sense to me at all. This is no matter to me though because I track testing and not unstable. But current behaviour makes unstable rather pointless. HS - -- Mein GPG-Key ist auf meiner Homepage verfügbar: 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.0.7 (GNU/Linux) iD8DBQE9lJzpzvr6q9zCwcERAhSDAJ9CCSVndeCaWflQRp0Y/FLwC1FJxACgjVxv nbp0lnoIHEe4fbM5cNWLONg= =9Zz/ -END PGP SIGNATURE-
Re: 178 days and counting
Strange, I chose Debian because it's Free, stable, feature-rich and fairly easy to use. The stable distribution is perfect for people who want a general-purpose operating system and have real work to get done, rather than just playing with a technological toy. Can't say I'm iching to upgrade to KDE3. KDE2 has more bells and whistles than I really need already. Am I missing some compelling must-have feature that will make me wonder how I ever lived without it? Oh, and I always thought Slakware was l337 ;-o) perhaps I'm giving away my age. - Dan On Friday 27 Sep 2002 6:36 pm, Albert Heijn wrote: I don't think the reason why one would choose Debian was ever to have always the latest packages without any hassle You choose Debian because it is 1337 :)) -Original Message- From: Bastiaan Naber [mailto:[EMAIL PROTECTED] Sent: Friday, September 27, 2002 7:33 PM To: debian-kde@lists.debian.org Subject: Re: 178 days and counting On Friday 27 September 2002 18:25, Brad Felmey wrote: On Fri, 2002-09-27 at 11:14, David Pashley wrote: Well you could join #debian-kde on irc.freenode.org, check out KDE from CVS and fix problems. Whie you're at it you could sort out a correct transition to GCC 3.2 in sid without breaking updates including from woody, or you could just bitch about it. I'd rather just bitch about it, thanks. -- Brad Felmey Or you could try some other distro. A lot a debian people have left because debian isn't that cool anymore because all the new software is missing. Try gentoo it is source based but has most of the latest available source code. Or mandrake, I have found that the new version 9.0 is very usable. Bastiaan
Re: 178 days and counting
Hendrik Sattler [EMAIL PROTECTED] writes: Am Freitag, 27. September 2002 19:36 schrieb [EMAIL PROTECTED]: woody/unstable (libc3.x maybe? I don't remember.) that were dependencies. Because you wrote that often enought now: woody is not unstable or testing but the current stable, maybe you should take a look at http://www.debian.org to get this right: woody == current stable sarge == current testing sid == always unstable It is annoying and hard to track what you mean when you mix this up completely. Sorry. I've been a long-time Redhat user, just recently transitioning to Debian so I'm still learning the lingo. I'll try to be more careful with my terminology in the future. Thanks for the lesson. Derrell
Re: 178 days and counting
On Fri, 27 Sep 2002 11:25:40 -0500 Brad Felmey [EMAIL PROTECTED] wrote: On Fri, 2002-09-27 at 11:14, David Pashley wrote: Well you could join #debian-kde on irc.freenode.org, check out KDE from CVS and fix problems. Whie you're at it you could sort out a correct transition to GCC 3.2 in sid without breaking updates including from woody, or you could just bitch about it. I'd rather just bitch about it, thanks. I decided to check out CVS 3.1 beta 2 (and privately fixing some problems). I don't have GCC 3.2 installed.
Re: 178 days and counting
On Fri, 2002-09-27 at 13:14, Simon Hepburn wrote: Brad Felmey wrote: I'd rather just bitch about it, thanks. That's odd I'm running sid and kde3.0.3. How did that happen ? Guess I must have pasted one of those pesky apt-lines for ftp.kde.org that people keep littering this list with, into my sources.list. Mind you that's an awful lot of work compared to working out how many days kde3 has been missing from sid and bitching about it on a mailing list. You have my sympathies...honest. Simon, don't even pretend you understand what I was getting at. It's painfully obvious you don't. If I wanted to maintain dozens of workstations using RPMFIND methods, I wouldn't be on Debian. It's people like you and the all-but-AWOL maintainer who are responsible for issues like this: http://debianplanet.org/node.php?id=813 And between bouts of insinuating that I'm too st00p1d to figure out how to install unofficial debs (breaking everything compiled against libarts), see if you can figure out how to set your line-wrap appropriately in KMail. -- Brad Felmey
Re: Compiling KBabel 1.0.2 for KDE 3.0.3
install libdb2-dev Thanks it worked. If somebody wants a crude .deb package of KBabel 1.0beta2 for Sid / KDE 3.0.3, please contact me Cheers, Charles -- [EMAIL PROTECTED] http://www.kde-france.org
Re: ugle background when starting kdm
Does anyone know how to do this ? This is part of X - nothing to do with kdm. You could try looking at the ceiling just before X starts. I don't think it looks so ugly. It looks like the mac classic default desktop. Anyone remember this? Also, if you ever configure X, this is what you see first off. The reason it shows the dots for so long is b/c your computer is slow. The faster the computer, the less time to see ugliness. If you get a fast enough computer, you won't see it anymore. So spring the $300 for a new computer. Also, if you spend $200 more and get a smokin' graphics card, I can guarantee that this will go away. Finally linux is compeditive w/ windows. We can solve all yer problems if you spend enough money. :) Fred Ollinger
Re: 178 days and counting
On Fri, Sep 27, 2002 at 01:36:16PM -0400, [EMAIL PROTECTED] wrote: deb http://people.debian.org/~schoepf/kde3/woody ./ It appears to be what I want. That looks like what I did, though, and there were still libraries that were required and only available from woody/unstable Use the deb source written above. The packages there will work with woody (=stable) without requiring any libs from testing or unstable. Bye Thomas --
Re: ugle background when starting kdm
The reason it shows the dots for so long is b/c your computer is slow. The faster the computer, the less time to see ugliness. If you get a fast enough computer, you won't see it anymore. So spring the $300 for a new computer. Also, if you spend $200 more and get a smokin' graphics card, I can guarantee that this will go away. Finally linux is compeditive w/ windows. We can solve all yer problems if you spend enough money. :) Sorry but I have a amd athlon XP 2000+ and a geforce graphics card and still the dots appear long enough to make my head hurt. I don't think spending more money will make the dotted background go away Bastiaan
Re: ugle background when starting kdm
Sorry but I have a amd athlon XP 2000+ and a geforce graphics card and still the dots appear long enough to make my head hurt. I don't think spending more money will make the dotted background go away Well, I stand corrected. This coming from someone who uses a 200 MHZ pentium II and the dots don't bother me at all b/c it reminds me of my old mac days. How long do these 'ugly' dots last? I'm curious now. How long in seconds. Also, I am very sorry that you have a headache due to this. I would help more if I could as I like to alleviate as much suffering in the world as possible. Have a good day. Fred Ollinger
Re: ugly x background when starting kdm
I've heard the proper explaination before on the Xpert list. I'm no programmer either but the basic idea is that this is an extremely low-level test of the X-Server. The reason for the horrible pattern it that it can be wrapped evenly on any bit boundary. The usefullness is when you are programming X, and you are changing things in the server, the presence or absence of this pattern will give you a very definite idea of how far X got before it crashed. Of course this is of no interest to non-X-programmers who are using stable X servers that are allready configured and working. I do know that there are patches available to remove this, but this would mean getting the proper version of source code to apply the patch to, patch it and re-compile and install. Not a difficult task, even for a non-programmer, but a lot to down-load and you would then be running a celf-compiled X rather than the Debian packaged version. Several people have tried to submit this patch for inclussion in X, but the existing pattern is too useful to the developers so it will never be applied. Think of it as similar to the BIOS report screen that appears when you first turn on your computer. It's of no interest, UNTIL you have a problem, then it's indespensable! Hope this explains it purpose for you. Cheers, John Gay
Re: ugly x background when starting kdm
Quoting John Gay [EMAIL PROTECTED]: I do know that there are patches available to remove this, but this would mean getting the proper version of source code to apply the patch to, patch it and re-compile and install. Not a difficult task, even for a non-programmer, but a lot to down-load and you would then be running a celf-compiled X rather than the Debian packaged version. Several people have tried to submit this patch for inclussion in X, but the existing pattern is too useful to the developers so it will never be applied. I have trouble believing that they would refuse a patch that made it an option somewhere. A simple IFDEF and a line in a config file would satisfy everyone. :Peter
ugle background when starting kdm
I would say look at the Xserver logs. I would bet you have something in there that X is searching for and not finding. If you have both a 'Configured Mouse' and 'Generic Mouse' section, disable the one that is NOT set as root pointer. This caused a few seconds of hangup on my box. Look for any warnings, like unused font paths and such, and correct the errors. If some fonts are not used by X anyway, comment them out of XF86Config-4. Nathan
Re: 178 days and counting
Brad Felmey wrote: Simon, don't even pretend you understand what I was getting at. It's painfully obvious you don't. Given that your posts consisted of: Since KDE 3.0 was released, and still nothing in sid. and I'd rather just bitch about it, thanks. ... what is it that we are supposed to understand ? If I wanted to maintain dozens of workstations using RPMFIND methods, I wouldn't be on Debian. It's people like you and the all-but-AWOL maintainer who are responsible for issues like this: http://debianplanet.org/node.php?id=813 I fail to see how I'm responsible for any of the issues raised in this article. I wont even attempt to speak on Chris's behalf but I will say that I am more than happy with the job Chris has done, since he took over as kde maintainer. Perhaps that's because I'm judging him by the quality of his packages and not by how vocal he is on this list. What makes you think he is all-but-AWOL ? And between bouts of insinuating that I'm too st00p1d to figure out how to install unofficial debs (breaking everything compiled against libarts), see if you can figure out how to set your line-wrap appropriately in KMail. The only thing I insinuated was that it's not a big effort to add a couple of lines to your sources.list. You seem to be suggesting that you intend to employ debian/unstable on dozens of workstations, presumably a production environment: I'd say that editing a simple config file will be the least of your problems and I would have thought you would be grateful that so much hard work was going into minimising the effects of the transition to gcc3.2. Or would you prefer it if your dozens of workstations were a bit more unstable ? As for the line wrap it's set to 78, always has been. Looks like a bug in kmail when moving mails to or from the drafts folder. I'll try and reproduce it. Anyone else seen anything similar ? Nothing on the kde bug page. -- Simon Hepburn.
Re: 178 days and counting
Simon Hepburn wrote: As for the line wrap it's set to 78, always has been. Looks like a bug in kmail when moving mails to or from the drafts folder. I'll try and reproduce it. Anyone else seen anything similar ? Nothing on the kde bug page. Reproduced and reported as #48392 -- Simon Hepburn.
The United States Healthcare Directory
We are publishers of specialized reports and directories dealing with public affairs. Our new directory, The United States Healthcare Directory covers hospitals, nursing homes, HMOs, medical manufacturers, etc. For more information, kindly visit our website at www.national-directories.com or contact us by phone at 905-751-0919. Thank you.
Re: html documentation for kde
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 grace and peace to you. thank everyone (who's typed on this topic) for your help. i set up a server for my local network with the linux documentation html package. i thought, while i was at it, that i'd install any other documentation on the web server that i thought i might need just for conveniance and to save bandwidth. the kde documentation looked like i'd read it if i made it available, so i installed it and set it up with apache. the system that it's installed on doesn't have kde or even X. it's strictly a server (and as a firewall, i didn't want to install X, that'd be to much work for *me* to lock down). so this is the scenario i wanted to use the documentation in. so regarding the suggestions: [ On Friday 27 September 2002 10:50 am, Karolina Lindqvist wrote: ] The problem is that if you pack the images with the html pages, you won't have the images in the normal kde documentation (right?). Some solutions to this would be to 1) to require installation of the html documentation 2) to have an either- or situation, either docbook or html documentation 3) to have a separate package for the images. Maybe another solution would be to simply, somehow, generate the required html documentation during package installation if required. Maybe not with one of those bluescreen questions, but with a comment if you want the html documentation, run the script generatehtmldocumentation or something like that. No extra package, no extra space, but you can still get the docs if you want to. As an alternative, there could be a kind of global switch to set if html documentation is wanted, or a special package kdehtmldocs that if present will generate the documentation during installation. That could then also take care of generating non-english language documentation in html. in my scenario, neither 1 nor 4 would be ideal. i don't necessarily want the extra docs on my work machine or the actual programs on the server. i like 3 best. then both the program and the docs could just link to the images. thanks. tim - -- Tim Wheeler [EMAIL PROTECTED] http://www.greengibberish.com/ - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9lSKyRNiK9b6/KqoRAu7+AJ9CKkFymEF8r5qLYSHkOoCJJc/xxQCfcRVP cW70JprS7yRCW10XizpCFzk= =TEtp -END PGP SIGNATURE-
Re: What's going on with KDE 3 and XFree86's libxkbfile?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 27 September 2002 2:17 am, Branden Robinson wrote: [Please reply to both debian-kde and debian -x.] I recently got a mail that said something like this: Why isn't there a -fPIC compiled version of /usr/X11R6/lib/libxkbfile.a available? (e.g. /usr/X11R6/lib/libxkbfile_pic.a) Background: I'm regulary compiling KDE3 CVS head on hppa and I'm getting a failure in the link stage: /usr/local/bin/ld: /usr/X11R6/lib/libxkbfile.a(maprules.o): relocation R_PARISC_DPREL21L can not be used when making a shared object; recompile with -fPIC /usr/X11R6/lib/libxkbfile.a: could not read symbols: Bad value This error is caused because the libxbbfile isn't compiled with -fPIC and so it's not usable to build a shared lib. But both libXxf86dga_pic.a libXxf86vm_pic.a are available as pic versions. I already answered this person privately, and I trust I don't need to remind this list of why it's a stupid idea to treat an unversioned static object like a shared library[1]. Can someone tell me what part of KDE is trying to sneak things in the back door? Can someone get in touch with upstream quickly and warn them of the hazards of doing so? The right thing to do is to statically link libxkbfile into the object being created. [1] http://lists.debian.org/debian-devel/2001/debian-devel-200111/msg00028.html http://lists.debian.org/debian-devel/2001/debian-devel-200111/msg00063.html http://lists.debian.org/debian-devel/2001/debian-devel-200111/msg00087.html http://lists.debian.org/debian-devel/2001/debian-devel-200111/msg00085.html Branden, can you get deepthroat to send a build log so we can see there this error is occuring in the build. Can you ask them how recently this has happened? Has anyone else had this problem on HPPA? - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9lCsqYsCKa6wDNXYRAuCsAJ0eT9Gj4HoXq83zQfc1yP5WfHNaLgCeLP3J 1kAF7Jnh/DxSlupG6lzrJb8= =zyI3 -END PGP SIGNATURE-
Re: What's going on with KDE 3 and XFree86's libxkbfile?
[Please remember to follow-up to both debian-kde and debian-x.] On Fri, Sep 27, 2002 at 10:55:51AM +0100, David Pashley wrote: Branden, can you get deepthroat to send a build log so we can see there this error is occuring in the build. Can you ask them how recently this has happened? I'll ask him. -- G. Branden Robinson| I came, I saw, she conquered. Debian GNU/Linux | The original Latin seems to have [EMAIL PROTECTED] | been garbled. http://people.debian.org/~branden/ | -- Robert Heinlein pgpdzie4JNZSs.pgp Description: PGP signature
Re: Regarding KDE 3, hppa, and libxkbfile
From: David Pashley [EMAIL PROTECTED] To: debian-kde@lists.debian.org, debian-x@lists.debian.org Subject: Re: What's going on with KDE 3 and XFree86's libxkbfile? Date: Fri, 27 Sep 2002 10:55:51 +0100 [snip] Branden, can you get deepthroat to send a build log so we can see there this error is occuring in the build. Can you ask them how recently this has happened? Has anyone else had this problem on HPPA? Hi, I haven't followed the discussions here and thus I maybe say things which already have been said, but yes, I have the same problem. The problem is, that we are trying to build a shared object in KDE (kxkb.so - most applications are just shared libraries to speed up loading iirc) and there we would need a -fPIC compiled version of libxkbfile.a (e.g. libxkbfile_pic.a). Please also see the attached make log. N.B. Please CC me, I'm not on those lists... Regards, Helge make[3]: Entering directory `/opt/xc/c3000-debian/kdebase/kxkb' source='/home/cvs/kde20/kdebase/kxkb/rules.cpp' object='rules.lo' libtool=yes \ depfile='.deps/rules.Plo' tmpdepfile='.deps/rules.TPlo' \ depmode=gcc3 /bin/sh /home/cvs/kde20/kdebase/admin/depcomp \ /bin/sh ../libtool --silent --mode=compile --tag=CXX g++ -DHAVE_CONFIG_H -I. -I/home/cvs/kde20/kdebase/kxkb -I.. -I/opt/kde/include -I/opt/kde/qt/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -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 -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -Os -ffunction-sections -fPIC -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST -D_GNU_SOURCE -c -o rules.lo `test -f /home/cvs/kde20/kdebase/kxkb/rules.cpp || echo '/home/cvs/kde20/kdebase/kxkb/'`/home/cvs/kde20/kdebase/kxkb/rules.cpp source='/home/cvs/kde20/kdebase/kxkb/kcmlayout.cpp' object='kcmlayout.lo' libtool=yes \ depfile='.deps/kcmlayout.Plo' tmpdepfile='.deps/kcmlayout.TPlo' \ depmode=gcc3 /bin/sh /home/cvs/kde20/kdebase/admin/depcomp \ /bin/sh ../libtool --silent --mode=compile --tag=CXX g++ -DHAVE_CONFIG_H -I. -I/home/cvs/kde20/kdebase/kxkb -I.. -I/opt/kde/include -I/opt/kde/qt/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -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 -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -Os -ffunction-sections -fPIC -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST -D_GNU_SOURCE -c -o kcmlayout.lo `test -f /home/cvs/kde20/kdebase/kxkb/kcmlayout.cpp || echo '/home/cvs/kde20/kdebase/kxkb/'`/home/cvs/kde20/kdebase/kxkb/kcmlayout.cpp source='/home/cvs/kde20/kdebase/kxkb/pixmap.cpp' object='pixmap.lo' libtool=yes \ depfile='.deps/pixmap.Plo' tmpdepfile='.deps/pixmap.TPlo' \ depmode=gcc3 /bin/sh /home/cvs/kde20/kdebase/admin/depcomp \ /bin/sh ../libtool --silent --mode=compile --tag=CXX g++ -DHAVE_CONFIG_H -I. -I/home/cvs/kde20/kdebase/kxkb -I.. -I/opt/kde/include -I/opt/kde/qt/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -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 -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -Os -ffunction-sections -fPIC -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST -D_GNU_SOURCE -c -o pixmap.lo `test -f /home/cvs/kde20/kdebase/kxkb/pixmap.cpp || echo '/home/cvs/kde20/kdebase/kxkb/'`/home/cvs/kde20/kdebase/kxkb/pixmap.cpp source='/home/cvs/kde20/kdebase/kxkb/kcmmisc.cpp' object='kcmmisc.lo' libtool=yes \ depfile='.deps/kcmmisc.Plo' tmpdepfile='.deps/kcmmisc.TPlo' \ depmode=gcc3 /bin/sh /home/cvs/kde20/kdebase/admin/depcomp \ /bin/sh ../libtool --silent --mode=compile --tag=CXX g++ -DHAVE_CONFIG_H -I. -I/home/cvs/kde20/kdebase/kxkb -I.. -I/opt/kde/include -I/opt/kde/qt/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -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 -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -Os -ffunction-sections -fPIC -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST -D_GNU_SOURCE -c -o kcmmisc.lo `test -f /home/cvs/kde20/kdebase/kxkb/kcmmisc.cpp || echo '/home/cvs/kde20/kdebase/kxkb/'`/home/cvs/kde20/kdebase/kxkb/kcmmisc.cpp source='/home/cvs/kde20/kdebase/kxkb/kxkb.cpp' object='kxkb.lo' libtool=yes \ depfile='.deps/kxkb.Plo' tmpdepfile='.deps/kxkb.TPlo' \ depmode=gcc3 /bin/sh /home/cvs/kde20/kdebase/admin/depcomp \ /bin/sh ../libtool --silent --mode=compile --tag=CXX g++ -DHAVE_CONFIG_H -I. -I/home/cvs/kde20/kdebase/kxkb -I.. -I/opt/kde/include
