Konq with authenticating proxies
Up until yesterday, I was using konqueror here at work, and it was wonderful. Then, after apt-get'ing yesterday's updates, everytime I try and surf the web through the authenticating proxy here at work, it returns this error (when it would normally be popping up the username/pass box): Unsupported action Unknown authorization method. And won't go anywhere. Nothing else changed, I didn't mess around with the proxy settings, though I have gone back and made sure that they are correct. I was hoping that would be fixed in todays update, but it wasn't :-( Anyone have any idea what's going on? I had a few short days of bliss, but am now back to mozilla and hating almost every minute of it. Vital stats: latest sid, everything to do with kde installed (within reason, no games), i386. TIA and HAND, D.A.Bishop
Konq with authenticating Proxies
(resend) Up until yesterday, I was using konqueror here at work, and it was wonderful. Then, after apt-get'ing last Thursday's updates, everytime I try and surf the web through the authenticating proxy here at work, it returns this error (when it would normally be popping up the username/pass box): Unsupported action Unknown authorization method. And won't go anywhere. Nothing else changed, I didn't mess around with the proxy settings, though I have gone back and made sure that they are correct. I was hoping that would be fixed in subsequent updates, but it wasn't :-( Anyone have any idea what's going on? Any place that I can start debugging the issue? Even when starting konq from within a terminal, no debugging output was sent to the shell, so that was a dead-end. I had a few short days of bliss, but am now back to mozilla and hating almost every minute of it. Vital stats: latest sid, everything to do with kde installed (within reason, no games), i386. TIA and HAND, D.A.Bishop
Re: Konq with authenticating Proxies
Whew. Just looking for some validation in my life :-) As long as I'm not the only one having the problem, I know it's not something I jacked up. Well, I'm off to file a bug report. I already did on the KDE side, but afaict, nobody's even looked at it yet :-( Oh, well. I can stand galeon for a few more days D.A.Bishop On Tue, 06 Mar 2001 19:34:50 +1100, John Reid said: > Hi, > > "Ivan E. Moore II" wrote: > > > > (resend) > > > > got you the first time...still sitting in my debian-kde mailbox. :) > > > > a) since your a sid user, file a bug report. > > b) can anyone else validate this, it's been on my todo since the first > message > >to setup a auth proxy to test with but work keeps getting in my way. > > FYI - I have exactly the same problem here. Same set-up (sid), same > symptoms - was > working fine until the weekend, then updated and :-(. > > > c) I also need to go look through the cvs commits to see if it's been fixed > > No mention of problem on kde-user list that a quick search on "proxy" could > find > :-( > -- > john reid e-mail [EMAIL PROTECTED] > technical officerroom G02, building 41 > school of geosciences phone +61 02 4221 3963 > university of wollongong fax +61 02 4221 4250 > > uproot your questions from their ground and the dangling roots will be > seen. more questions! > -mentat zensufi > > apply standard disclaimers as desired... > -- > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > >
authenticating proxy
I saw a message last week for all of us authenticating proxy users to upgrade. Well, I did, and I have the same problem. Was the fix repealed? Or is something else wrong? To repeat, the exact error is: Unsuported action Unknown authorization method! Thanks, D.A.Bishop
Re: kmail question
A non-kmail related answer is to run your own smtp server. Using exim, restricted to only localhost, allows you to send mail no matter who you are dialed up to, or connected to via ethernet, or whatever. The only configuration for your mailer then is to set the reply-to based on which account you recieved a piece of mail from, or have a drop-down list of accounts that you can set the "reply to:" to if sending a fresh mail. mail-it for beos does this wonderfully, however I don't know if kmail has this functionality or not. In linux, pronto is my baby (and also has this functionality). HTH, D.A.Bishop On Mon, 12 Mar 2001 20:16:18 +, Neil Youngman said: > OK. I wasn't clear enough. I can see how to read POP3 mail, but they > have different SMTP servers for outgoing mail. I want to be able to send > mail to the appropriate SMTP server for the account I'm dialled into and > I can't see a sensible way of doing it, unless you count hacking ip-up > scripts as sensible solution. > > Neil > > "G. L. `Griz' Inabnit" wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > > > On Sunday 11 March 2001 02:51, Neil Youngman wrote something to this > effect: > > > I have accounts with 2 different ISPs. I have tried to set up 2 kmail > > > identities, one for each account, but it appears to only allow one > > > network setup. Obviously I'd like to associate one set of mail servers > > > with each identity. Is this possible? > > > > > > Neil > > > > Yes! > > > > SETTING, > > CONFIGURATION, > > NETWORK, > > ADD (it's a button), > > POP3, > > fill in the blanks. > > > > I'm checking five accounts with mine. :--) That's why it's used! > > > > Ivan, I'm coming to ask you a question on KMail though. :--)) > > > > - -- > > > __ > >OutCast Computer Consultants of Central Oregon > > http://outcast-consultants.redmond.or.us > > [EMAIL PROTECTED] > > (541) 504-1388 > > Via IRC at; 205.227.115.251:6667:#OutCasts > >Via ICQ: UIN 138930 > > > > "Failure is not an option...it's bundled with Microsoft" > > -anonymous- > > > > -BEGIN PGP SIGNATURE- > > Version: PGPfreeware 5.0i for non-commercial use > > MessageID: MmT9ynRM8NYx2BznLRJ64O6GakIaaodv > > > > iQA/AwUBOq0hwAhnWicv+0tKEQJ0PwCfeXgiHlXxn+WQtiX3DV7kTdl7hekAoM1R > > 2qPKBNm1lSnHBwSVDV0VU8Qk > > =91iV > > -END PGP SIGNATURE- > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > >
invalid domain (with kmail)
So, I'm trying to send email to a domain that uses exim with kmail, and it consistenly rejects my email saying that [EMAIL PROTECTED] is an invalid domain. Since this is the only email address that I have this problem with, I assume they turned on some sort of spam protection that looks at an X-header of the email to determine that (suprise, suprise!) my domain isn't "real". Well, I'm not going to change my whole hostname setup for a single email app (sorry), so I'm wondering if I can change something else. I'm using exim myself as my smtp server (localhost) so I was wondering what I have to do to make this work. Edit my exim config to "spoof" a valid domain? Edit my kmail config to do the same? Something else? I'm kinda lost here Oh, and the reason that I'm sending this to debian-kde is that I didn't ever get this problem with my previous mailer (pronto), and I'm running debian. So, that leads me to suspect it is either a kde issue, or a debian-packaging of a kde issue (like the whole authenticating proxy thing, or the internet keywork search saying invalid url). Just to clarify :-) TIA, D.A.Bishop
Re: invalid domain (with kmail)
On Tuesday 13 March 2001 13:39, Bart Oldeman wrote: > On Tue, 13 Mar 2001, David Bishop wrote: > > So, I'm trying to send email to a domain that uses exim with kmail, and > > it consistenly rejects my email saying that [EMAIL PROTECTED] is an invalid > > domain. Since this is the only email address that I have this problem > > with, I assume they turned on some sort of spam protection that looks at > > an X-header of the email to determine that (suprise, suprise!) my domain > > isn't "real". Well, I'm not going to change my whole hostname setup for > > a single email app (sorry), so I'm wondering if I can change something > > else. I'm using exim myself as my smtp server (localhost) so I was > > wondering what I have to do to make this work. Edit my exim config to > > "spoof" a valid domain? Edit my kmail config to do the same? Something > > else? I'm kinda lost here > > > > Oh, and the reason that I'm sending this to debian-kde is that I didn't > > ever get this problem with my previous mailer (pronto), and I'm running > > debian. So, that leads me to suspect it is either a kde issue, or a > > debian-packaging of a kde issue (like the whole authenticating proxy > > thing, or the internet keywork search saying invalid url). Just to > > clarify :-) > > There exists a file /etc/email-adresses which does what you want (I > think). Also check out whether /etc/exim.conf is really using it. > > Bart Wonderfull! Did exactly what I wanted, with the minimum of fuss. Thank you! D.A.Bishop
Re: Little advice for AA
On Tuesday 13 March 2001 16:54, Rogerio Brito wrote: > On Mar 09 2001, Malte Cornils wrote: > > The Debian sid (unstable) Xfree4.0.2 version does not offer the > > Render extension (which is necessary for AA) when you use a > > non-Radeon non-Rage128 card (like all Mach64-based cards). > > Uh, oh! I'm using a Matrox here and I *can* get AA output. :-) > > > []s, Roger... He was refering soley to ATi cards. As in, if you have an ATi card, it has to be rage128 or Radeon. At least, that's how I took it, cuz I have both an ATi card *and* a Matrox, and I can attest to the fact that it doesn't work with the mach64, but does with the g450. YMMV, D.A.Bishop
disabling the render extension
Digging around on bugs.kde.org, I found out that the problems I'm having with my xinerama setup are due to a bug in my xserver, specifically the render extension. The (terse) reply is "disable the render extention". So. How in the heck do I do that without uninstalling the entire xfree package and compiling from source, downgrading to 3.3.6 (ick), or some other weirdness. Am I asking too much? You'd think, with the fact that only a couple drivers can do it anyways, that it would be an option that you get seperate to the base X install. So, what are my options? Besides using Enlightenment as my window manager, which, believe me, isn't working too well with kde 2.1.0 :-( TIA D.A.Bishop P.S. I *really* like the AA fonts and everything that RENDER gives me, I would just like to be able to actually use kwm more :-P
pilot/visor integration with kde
Having just recieved a Handspring Visor for graduation, I was of course eager to try it out with linux :-) However, there seems to be a slight derth of information on how to integrate a palm-like device with KDE. Most sections of the manual that have to do with syncing a visor with [korganizer|abbrowser|kab] have the ever popular "This Section Isn't Here Yet." So, what is your collective experience with the different apps out there? KPilot seems to be buggy, in that it always trys to start up two copies, and will only "sync" once before I have to close it and start it up again. That also limits it usefullness in transfering programs/ebooks over to the visor. Oh, and if I leave kpilot-daemon running in the background, it continually respawns (will never shut down the window). However, it has "conduits" to korganizer for the to-do list and the appointments. j-pilot seems to be much more stable and featureful, however, it's a gtk app (looks ugly), doesn't have conduits to korganizer or anyother kde app for that matter, and has it's own set of issues. I'd really hate to have to use pilot-xfer for stuff that should be easy click->install. Whew. Didn't mean for that to turn into a rant, and I'm impressed with how far along this stuff has come already. However (you saw that coming, didn't you?) does anyone have experience with all of these issues, and if so, can you point me to a place where I can get an app that (hopefully, doesn't need to do all of this): 1. Runs in the background and monitors for me pushing the hotsync button 2. Has conduits to korganizer and abbrowser or kab (which is better supported?) 3. Isn't crash happy 4. Is a kde app 5. Makes it really easy to install new stuff And while this isn't the appropriate forum, has anyone heard tale of adding functionality in konqueror to recognize .prb and .prc files, and load them automatically after being clicked (with confirmation, of course)? It would take a kpart's thingamajig from kpilot, but should be doable. If there has already been noise about that, I will wait patiently, otherwise I'll file a wishlist bug. Thanks for any ideas/insight you have. If this is too off-topic for debian-kde, please reply to me off-list. Thank you! D.A.Bishop P.S. I'm running sid, if that affects my options for programs. Thanks again.
Re: stupid, but I have to ask it - how to start it up once installed
If you install kdm, but haven't rebooted, you need to run /etc/init.d/kdm start as root. You will then see the login window he was referring to. Otherwise, just reboot the machine. On Tuesday 20 March 2001 11:44, Whit wrote: > On Tue, Mar 20, 2001 at 07:23:09AM +0100, Achim Bohnet wrote: > > Method two: > > > > apt-get install kdm > > select 'kde2' instead of 'default' in the login window > > The first step is redundant - but did it anyhow - no change. > > The second - well, where is that 'login window'? > > Thanks, > Whit > [EMAIL PROTECTED]
Re: stupid, but I have to ask it - how to start it up once installed
To stop it, you can either uninstall kdm (apt-get remove kdm) or manually delete the link in /etc/rc2.d/. Since it seems like you won't ever want it to boot to X (the only function of *dm on a workstation machine) you should probably just remove the package. However, I'm curious as to whether or not that worked (i.e., did it actually start kde when you logged on?) If it did, that points to a problem with you startx routine (type, whatnot). If it didn't, something is seriously wrong with your install and we get to dig deeper :-) HTH, D.A.Bishop On Tuesday 20 March 2001 16:15, Whit wrote: > On Tue, Mar 20, 2001 at 11:59:47AM -0700, David Bishop wrote: > > If you install kdm, but haven't rebooted, you need to run /etc/init.d/kdm > > start as root. You will then see the login window he was referring to. > > Otherwise, just reboot the machine. > > Yeah, I just discovered that on the next boot. Please tell me how to undo > it! I don't want the system to come up in a GUI - guess I should have been > clear that what I'm trying to do is get startx or the equivalent to work > from a bash tty. I often don't work in a GUI, and don't want to waste time > going in to one just to go back out. > > I'm also curious why the reinstall of kdm set it this way, when the initial > one didn't - guess that script modified the install enough to keep this > often-undesirable result from happening? > > Thanks again, > Whit > [EMAIL PROTECTED]
Re: Proxy authentification
On Thursday 22 March 2001 02:42, Thierry FLORAC wrote: > Hi, > > I was currently using Debian potato, updated with KDE-2.1 packages for > Potato from kde.debian.net. > I have upgraded to KDE-2.1.1 this morning, and now I have a problem with > Konqueror, which don't want to handle my proxy authentification anymore. > The error message is : > > Unsupported action > Unknown authorization method! > > This problem disappear if I downgrade my "kdelibs3" package to old version > (kdelibs3_2.1-final-0.potato1). > > Any idea ?? > > Thierry You found a fix?? Sweet! Now, before I completely bowlderize away my box (sid/i386) does anyone know whether or not I can downgrade to that version of kdelibs without screwing anything else up? I assume there were other changed in kdelibs between 2.1 and 2.1.1 besides jacking proxyauth up :-) Oh, and yeah, I've been seeing that same problem (if you couldn't tell). I've had to use ssh tunneling to get out of my corporate firewall, and it sucks to surf at DSL speeds when I could be riding a T3 :-( D.A.Bishop
authenticating proxy
Sorry to bother you guys about this again, but I just did a full apt-get update and konq is still broken wrt authenticating proxies. This is regarding #21832 that I filed a while ago. I've noticed other bug reports regarding authenticatin proxies have been closed, but not mine. Also, as was under the impression that Ivan was running pretty much the bleeding edge stuff for sid, so any updates that affect this should be included already. If there is anything that I could do on my end (recompile with debugging? strace?) please tell me and I'll do it. It is killing me to not be able to really use the best browser for linux (by far. I mean, it's almost not fair to the other browsers). Please help! Thanks, D.A.Bishop P.S. I am cc:ing debian-kde and the konq list as I'm not certain whether this is a packaging issue or not (i.e. the whole attachments in alternative wm's thing).
browser identifier
Can anyone tell me if this is accurate? There's some stuff on there that I think konq supports, but it's coming back as Property Not Supported. Is it a bug in the jvavscript, a bug in konq, or is it correct? http://www.webpak.net/~tschmidt/browser_info.html Thanks, D.A.Bishop
Re: browser identifier
I was looking more at the stuff like cookie enabled, browserLanguage, and the like. AFAIK, that stuff is used all over the web to set default languages, redirect to specific pages, what version of javascript you are running to give you different scripts, stuff like that. I wasn't pointing to that page in particular as perfect example of why you would want that, just a good example of whether or not konq would work with a page that *required* those. I'm sorry for not really making that point clear in my first email. D.A.Bishop On Wednesday 04 April 2001 14:32, Hendrik Sattler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am Donnerstag, 5. April 2001 00:12 schrieb David Bishop: > > Can anyone tell me if this is accurate? There's some stuff on there that > > I think konq supports, but it's coming back as Property Not Supported. > > Is it a bug in the jvavscript, a bug in konq, or is it correct? > > > > http://www.webpak.net/~tschmidt/browser_info.html > > Would you prefer to give away all this information? > I think the site has some errors anyway. There is no Konqueror 5.0, you > cannot just cut the "userAgent" field this way. Anyway, who cares for all > those red marked fields. What does, e.g. my frameRate matter to anything? > > HS > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.0.4 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE6y5Lwzvr6q9zCwcERAig2AJ0f9QjXInPbbXYI51Jl/3qLAJkwkQCcCd1m > cilxpvN0uf6Sv9FSHxvaars= > =KXVx > -END PGP SIGNATURE-
proxy auth
So, now that 2.1.1 is out, which supposedly has the fix for the annoying "proxy auth" bug, and the kde I get in debian/sid is supposedly 2.1.1, why do I still have the same annoying problem? I'm running the latest version of everything (i.e., done the apt-get update/upgrade thang), and it is still not working with a proxy that was fine before it broke. Do I have to reboot or restart kde or something? Does closing konq and restarting it not do enough? Help! (the reason I ask rather than try is I have several long running processes going, so I can't even try logging out until tomorrow at the earliest). TIA, D.A.Bishop
Re: proxy auth
On Wednesday 04 April 2001 14:52, Ivan E. Moore II wrote: > On Wed, Apr 04, 2001 at 03:49:05PM -0700, David Bishop wrote: > > So, now that 2.1.1 is out, which supposedly has the fix for the annoying > > "proxy auth" bug, and the kde I get in debian/sid is supposedly 2.1.1, > > why do I still have the same annoying problem? I'm running the latest > > version of everything (i.e., done the apt-get update/upgrade thang), and > > it is still not working with a proxy that was fine before it broke. Do I > > have to reboot or restart kde or something? Does closing konq and > > restarting it not do enough? Help! (the reason I ask rather than try > > is I have several long running processes going, so I can't even try > > logging out until tomorrow at the earliest). > > what version are you running. 2.1.1 did not fix the problem..it wasn't > *supposidly* fixed until the other day. > > kdelibs (4:2.1.1-3) > kdebase (4:2.1.1-3) > > Ivan Ack, sorry about that. I had no right to snap at you that way. My apologies. However, since my program just crashed, I took the opportunity to log out and back on again with the same result. Here's a quick grep of what's on my system. [EMAIL PROTECTED]:~$ dpkg --list | grep kdelib ii kdelibs-dev2.1.1-3KDE core libraries (development files) ii kdelibs3 2.1.1-3KDE core libraries (runtime files) ii kdelibs3-crypt 2.1.1.0-1 KDE core libraries (Crypto Modules) ii kdelibs3-doc 2.1.1-3KDE core library documentation [EMAIL PROTECTED]:~$ dpkg --list | grep kdebase ii kdebase2.1.1-3KDE core applications ii kdebase-crypto 2.1.1-1.0.1KDE core applications (Crypto modules) ii kdebase-dev2.1.1-3KDE core applications (development files) ii kdebase-doc2.1.1-3Documentation for Applications in kdebase ii kdebase-libs 2.1.1-3KDE libraries amd modules for kdebase [EMAIL PROTECTED]:~$ cat /etc/apt/sources.list deb ftp://ftp.us.debian.org/debian unstable main contrib non-free deb ftp://non-us.debian.org/debian-non-US unstable/non-US main contrib non-free Thanks, D.A.Bishop
Re: proxy auth
On Wednesday 04 April 2001 15:03, Ivan E. Moore II wrote: > > > what version are you running. 2.1.1 did not fix the problem..it wasn't > > > *supposidly* fixed until the other day. > > > > > > kdelibs (4:2.1.1-3) > > > kdebase (4:2.1.1-3) > > > > > > Ivan > > > > Ack, sorry about that. I had no right to snap at you that way. My > > apologies. However, since my program just crashed, I took the opportunity > > to log out and back on again with the same result. Here's a quick grep > > of what's on my system. > > > > ii kdelibs3 2.1.1-3KDE core libraries (runtime files) > > ii kdebase2.1.1-3KDE core applications > > ii kdebase-libs 2.1.1-3KDE libraries amd modules for kdebase > > hmmm...well unless someone else can vouch for it working I guess they > didn't fix it. I don't have a proxy with authentication setup to test > this. > > Ivan Damn. I dunno if you follow kfm-devel (it's not like you have a ton of free time), but a guy just posted a short patch that commented out the offending line(s). I don't suppose you want to fork the entire konq codebase and keep a seperate source-tree, dealing with keeping your tree up-to-date via patches and diffs, all to make my life a little easier, do you? You do?? Great! You're the best ;-) Or, I could break down and either compile it myself or figure out why it's still b0rken. Naw, that's too much work B) D.A.Bishop
Re: proxy auth
On Wednesday 04 April 2001 15:22, Ivan E. Moore II wrote: > > Damn. I dunno if you follow kfm-devel (it's not like you have a ton of > > free time), but a guy just posted a short patch that commented out the > > offending line(s). I don't suppose you want to fork the entire konq > > codebase and keep a seperate source-tree, dealing with keeping your tree > > up-to-date via patches and diffs, all to make my life a little easier, do > > you? You do?? Great! You're the best ;-) > > > > Or, I could break down and either compile it myself or figure out why > > it's still b0rken. Naw, that's too much work B) > > you don't think I"m keeping my own patch db? :) Do you know how much I would appreciate you commenting that section out? I'd almost go so far as to say thanks. Effusively. ;-) If you want a link to the patch, I can dig it up. D.A.Bishop
Re: proxy auth
On Thursday 05 April 2001 04:00, Thierry Florac wrote: > "Ivan E. Moore II" a écrit : > > > > what version are you running. 2.1.1 did not fix the problem..it > > > > wasn't *supposidly* fixed until the other day. > > > > > > > > kdelibs (4:2.1.1-3) > > > > kdebase (4:2.1.1-3) > > > > > > > > Ivan > > > > > > Ack, sorry about that. I had no right to snap at you that way. My > > > apologies. However, since my program just crashed, I took the > > > opportunity to log out and back on again with the same result. Here's > > > a quick grep of what's on my system. > > > > > > ii kdelibs3 2.1.1-3KDE core libraries (runtime files) > > > ii kdebase2.1.1-3KDE core applications > > > ii kdebase-libs 2.1.1-3KDE libraries amd modules for kdebase > > > > hmmm...well unless someone else can vouch for it working I guess they > > didn't fix it. I don't have a proxy with authentication setup to test > > this. > > Hi, > > I currently use KDE-2.1.1 and a proxy with authentication, and : > - if I just enable proxy auth and specify and HTTP/FTP server/port, > authentication fails !! > But : > - if I put "user:[EMAIL PROTECTED]" in the server name entry, > authentication is OK and transparent ;-)) > But : > - if I come back to this option configure dialog, "user:password@" has > disappeared in front of the server name and if I say OK in the dialog box, > authentication don't work anymore :-(( > > Hope this will help while waiting for a complete proxy authentication > support in Konqueror... > > Thierry > -- Wahooo! *hugs and kisses for Thierry* Thanks :-) (btw, it works ;) D.A.Bishop
auth proxy
FYI, the latest kdelibs package has fixed the whole auth proxy problem. Thanks to all who came up with ideas (esp. working ones ;-) and Ivan for packaging up the fix so quickly. I can finally use our OC3 to surf the web! Woohoo! =-) D.A.Bishop
Re: version of QT - was OpenSSL 0.9.6a breaks X?
http://slashdot.org/articles/01/04/09/1728246.shtml On Tuesday 10 April 2001 20:24, Ivan E. Moore II wrote: > On Tue, Apr 10, 2001 at 07:12:39PM -0700, Doug Byfield wrote: > > On Tuesday 10 April 2001 18:29, Ivan E. Moore II wrote: > > > As it stands now I > > > have alot on my plate with new X4.0.3 packages that require an update > > > to how QT is built > > > > Which QT will you be targeting first off for this? Qt 2.3 or 3.0? Just > > curious as I know 3.0 was just announced yesterday, not trying to be > > pushy. TIA. > > ok...I didn't think I saw the announcement...where did you see this? There > is no QT 3 packages (except the snapshots) on their ftp site nor a > announcement or any reference of it on their website. > > Ivan
Re: call for help with man pages
On Thursday 12 April 2001 20:02, Ivan E. Moore II wrote: > > Do you have a "template" or something we can work off of? If you had a > > standard > > here is one for konqueror I just threw together..probably still needs some > tweaks...but it's short sweet and to the point. > > Ivan So, call to arms. Gather round, my countrymen, and I'll tell you a tale of Brer. Nevermind, I think I just mixed four different speeches in two sentences :-) Is there a list of the programs that we should be doing this for? A central repository to send these to (or just the mailing list) so as to keep the duplication of effort to a minimum? Free milkshakes for everyone that helps? Just making sure you were still paying attention. If there is a way to query dpkg about what binaries there are in the kde packages, that would at least give us a list to work off of. If no one else is interested, I hereby volunteer to help coordinate this, via keeping some sort of list of what's been done, what's left, and (if necessary) who's working on what. I don't have enough to do at work anyways So, to sum up this ramble (it's late for me), here's what I need to get off the ground: 1) A list of the packages that we need to do this for 2) Hopefully have that list annotated and grouped with "common", "seperate", and "special" (i.e., Ivan feels he would do a better job) packages marked 3) A (probably) short list of people willing to help out 4) I can't think of anything else. Response? The Eternally Tired One, D.A.Bishop
Re: call for help with man pages
Just run 'man ./filename.1'. It will read the man page just like it was system-wide. I'm working on organizing that list Ivan sent out, and will repost it minus the dupes and grouped in a little bit. On Fri, Apr 13, 2001 at 10:26:31PM +1000, David Kempe wrote: > On Friday 13 April 2001 13:12, David Bishop wrote: > >3) A (probably) short list of people willing to help out > > Add me to that list, however How do we test the man page from Ivan's template > once we have written it? I think the syntax is easy enough, I just want to > know what its going to look like i guess. > > Dave
quanta while using 2.2
I've now upgraded to kde 2.2 alpha, and it shows :-) I've already submitted a bug report against kmail, but before I did the same against quanta, I wanted to make sure I wasn't doing something wrong. First off, it doesn't look like quanta has been updated to use the newest qt libraries. Is that a problem? I.e., when you updated to qt2.2, do all qt apps need to be recompiled? And if not (i.e., it's backwards compatabile binary-wise) then do you have any idea of why it is crashing? Here's the bt and output to terminal, if it helps at all: (no debugging symbols found)...(no debugging symbols found)... 0x40f49789 in wait4 () from /lib/libc.so.6 #0 0x40f49789 in wait4 () from /lib/libc.so.6 #1 0x40fb378c in __check_rhosts_file () from /lib/libc.so.6 #2 0x4075bf20 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.3 #3 0x40ed2738 in sigaction () from /lib/libc.so.6 #4 0x80c4c7c in QCollection::newItem () #5 0x809bfff in QCollection::newItem () #6 0x80ab930 in QCollection::newItem () #7 0x807ca7a in QCollection::newItem () #8 0x806b98e in QCollection::newItem () #9 0x409e80dd in QObject::activate_signal_string () from /usr/lib/libqt.so.2 #10 0x80e8b4f in QCollection::newItem () #11 0x80d7692 in QCollection::newItem () #12 0x807ab5c in QCollection::newItem () #13 0x80685f3 in QCollection::newItem () #14 0x40ec316b in __libc_start_main () from /lib/libc.so.6 and here's the term output: Xlib: extension "RENDER" missing on display ":0.0". 2667 quanta: KHTMLSettings::resetFontSizes adjustment is 4 2667 quanta: KHTMLSettings::resetFontSizes adjustment is 4 2667 khtml (part): KHTMLPart::init this=0x81df348 d=0x82b6b78 2667 quanta: KHTMLSettings::resetFontSizes adjustment is 5 2667 quanta: KHTMLSettings::resetFontSizes adjustment is 5 2667 khtml (part): KHTMLPart::init this=0x82bc350 d=0x8345c78 2667 quanta: KHTMLSettings::resetFontSizes adjustment is 5 2667 quanta: KHTMLSettings::resetFontSizes adjustment is 5 2667 khtml (part): KHTMLPart::init this=0x8342ad0 d=0x8351b40 2667 quanta: KHTMLSettings::resetFontSizes adjustment is 5 2667 quanta: KHTMLSettings::resetFontSizes adjustment is 5 2667 khtml (part): KHTMLPart::init this=0x834f980 d=0x835dcc0 2667 quanta: KHTMLSettings::resetFontSizes adjustment is 5 2667 quanta: KHTMLSettings::resetFontSizes adjustment is 5 parseBlock(0x83ceb00) KWBufBlock: buildStringList this = 0x83ceb00 dirtyBlock(0x83ceb00) KWBufBlock: disposeRawData this = 0x83ceb00 fatal parsing error: unexpected end of file in line 1 fatal parsing error: error while parsing prolog in line 1 Parsing error parseBlock(0x8445ab0) KWBufBlock: buildStringList this = 0x8445ab0 dirtyBlock(0x8445ab0) KWBufBlock: disposeRawData this = 0x8445ab0 fatal parsing error: unexpected end of file in line 1 fatal parsing error: error while parsing prolog in line 1 Parsing error KCrash: crashing crashRecursionCounter = 2 KCrash: Application Name = quanta path = Xlib: extension "RENDER" missing on display ":0.0". QToolBar::QToolBar main window cannot be 0. 2668 kio (KDirLister): KDirLister::openURL file:/home/david/ keep=false 2668 kio (Slave): createSlave for file:/home/david/ 2668 kdecore (KSocket): Performing lookup on //tmp/ksocket-david/drkonqiccVq6a.slave-socket 2668 kdecore (KSocket): Trying to listen on Unix /tmp/ksocket-david/drkonqiccVq6a.slave-socket 2668 kdecore (KSocket): Socket bound: 19 2668 kio (Slave): PID of slave = 2670 2668 kdecore (KSocket): Socket 19 accepted socket 18 2668 kio (Slave): slave has connected to application 2668 kio (Slave): got answer 10 2668 kio (KIOJob): stat file:/home/david/quanta.bt 2668 kio (KIOJob): error 11 /home/david/quanta.bt 2668 kdecore (KLibLoader): Deleting KLibLoader 0x80de1f8 unnamed Note that I have anti-aliasing off in the control panel, and I'm exporting no variables in my .xinitrc or anything. Okay, while typing this up I kept playing around with it, and moved my quantarc to quantarc.BACKUP and tried it again. It started!! Woohoo. However, as soon as I tried to open up a saved project, it crashed :-( Again, here's the bt and output: (no debugging symbols found)...0x40f49789 in wait4 () from /lib/libc.so.6 #0 0x40f49789 in wait4 () from /lib/libc.so.6 #1 0x40fb378c in __check_rhosts_file () from /lib/libc.so.6 #2 0x4075bf20 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.3 #3 0x40ed2738 in sigaction () from /lib/libc.so.6 #4 0x80c4c7c in QCollection::newItem () #5 0x809bfff in QCollection::newItem () #6 0x80ab930 in QCollection::newItem () #7 0x807ca7a in QCollection::newItem () #8 0x806b98e in QCollection::newItem () #9 0x409e80dd in QObject::activate_signal_string () from /usr/lib/libqt.so.2 #10 0x80e8b4f in QCollection::newItem () #11 0x80d7692 in QCollection::newItem () #12 0x80d6553 in QCollection::newItem () #13 0x806b26e in QCollection::newItem () #14 0x409e7b4f in QObject::activate_signal () from /usr/lib/libqt.so.2 #15 0x40b1af40 in QPopupMenu::activated () from /usr/lib/libqt.so.2 #
manless bins
Sorry, I got caught up playing around with my new kde and forgot to send this out. :-) Below is the list of bins that still need man pages. I'll claim the libarts stuff, as it's related and should be easy, please email me with what you claim, so as to avoid duping work. Completed man pages can be sent to either Ivan or me, or both. This shouldn't take too long, but I know it will be a load off of poor Ivan's back :-). Thanks for any help! D.A.Bishop P.S. Though I know it is almost antithetical to life itself, I noticed that there is a gmanedit package that helps when editing man pages. I won't mention that it is a gtk app so as not to offend anyone :-P libarts: artsc-config #Mine from here to libarts: artscat libarts: artsd libarts: artsdsp libarts: artsplay libarts: artsshell libarts: artswrapper libarts: mcopidl#here libkmid: knotify kdelibs3-cups: cupsdconf kdelibs3-cups: make_driver_db_cups kdelibs3: artsmessage kdelibs3: dcop kdelibs3: dcopidl kdelibs3: dcopidl2cpp kdelibs3: dcopserver kdelibs3: kbuildsycoca kdelibs3: kcookiejar kdelibs3: kdb2html kdelibs3: kde-config kdelibs3: kded kdelibs3: kdeinit kdelibs3: kdeinit_shell kdelibs3: kdeinit_shutdown kdelibs3: kdeinit_wrapper kdelibs3: kdesu_stub kdelibs3: kio_http_cache_cleaner kdelibs3: kio_uiserver kdelibs3: klauncher kdelibs3: kmailservice kdelibs3: ksendbugmail kdelibs3: lnusertemp kdelibs3: make_driver_db_lpd kdelibs3: settheme1
Re: quanta while using 2.2
On Saturday 14 April 2001 00:28, Ben Burton wrote: > If you can hang out a couple of days, Quanta has just made a new release > which I will be packaging shortly. > > > quanta, I wanted to make sure I wasn't doing something wrong. First off, > > it doesn't look like quanta has been updated to use the newest qt > > libraries. Is that a problem? I.e., when you updated to qt2.2, do all > > qt apps need to be recompiled? > > Hmmm.. > > Version: 1:2.0-pr1-4 > Depends: kdelibs3 (>= 4:2.1.0-0), kdelibs3 (>= 4:2.1.0-0) | kdelibs3-crypto > (>= 4:2.1.0-0), libc6 (>= 2.2.1-2), libjpeg62, libpng2, libqt2 (>= > 2:2.3.0-final-0) | libqt2-gl (>= 2:2.3.0-final-0), libstdc++2.10-glibc2.2, > xlibs (>= 4.0.1-11), zlib1g (>= 1:1.1.3), kdebase-libs, weblint > > In particular this list contains libqt 2.3. What makes you say it wants > old libraries? > > Ben. Sorry, I mistyped :-) That sentence should have read "I.e., when you updated to the latest qt2.3, do all qt apps need to be recompiled?". My fault. But it still stands, it still crashes as soon as I try to open anything, either a project or just an html file. Weird. D.A.Bishop
Re: new 2.2 packages avail
On Saturday 14 April 2001 12:55, Doug Byfield wrote: > On Saturday 14 April 2001 01:36, Ivan E. Moore II wrote: > > Ok...just got done uploading the latest -pretty-much-alpha1-packages- > > to > > > > deb http://people.debian.org/%7Erkrusty/ kde2.2/$(ARCH)/ > > deb http://pandora.debian.org/%7Erkrusty/ kde2.2/$(ARCH)/ > > I'm a bit concerned about the fact that 55 packages are not upgraded > and nothing seems to have been done. I checked in var/cache/apt, and > it's clean(no .deb files sitting in there. Pls see below. Am I missing > something? Do I just need more coffee input? :-) > Take any one of those and do a apt-get install packagename. That will bring up apt and it will go out and either install whatever it is you are missing that all those packages depend upon, or tell you what it is that is broken. Though I might be mistaken, and apt-get dist-upgrade will do that same thing. HTH, D.A.Bishop
Re: quanta while using 2.2
Works here at home. I'll try it at work tomorrow, but it's looking good :-) Thanks. D.A.Bishop On Saturday 14 April 2001 18:59, Ben Burton wrote: > Okay, the new quanta release is in incoming.. please let me know if the > problem persists (ak, I sound like I'm flogging paracetamol..). > > Ben.
Re: task-anti-aliasing
I figured that "task" package would consist soley of the documention that it installs into /usr/share/doc. So someone installing task-anti-aliasing would get a nice large "LOOK IN /USR/SHARE/DOC" and the really nice, step-by-step howtos and whatnot that you included. Then, if they said that they installed the package and it didn't make things automatically look nicer, you could flame them to hell and gone for being dumb :-) At least, that was *my* take. Having it install something else (xfs-xtt in this case) just makes it look like it *is* an, apt-get install and walk-away sorta routine. Just my insignificant pocket change, D.A.Bishop On Sunday 15 April 2001 20:49, Ivan E. Moore II wrote: > On Sun, Apr 15, 2001 at 03:21:54PM +0200, Stefan Schwandter wrote: > > Why does the package have to depend on a font server, although XF 4.x > > supports TT fonts natively ? > > cuz I just did it that way...I guess I could make everything a suggest > since nothing is truely needed except xlibs...then when someone does a > apt-get install task-anti-aliasing it won't install anything. :) > > no for real...yes X does support TTF...however it does not provide certain > support that, for example, xfs-xtt does. > > "XFree86 4.0's font server can handle TrueType too, but it > can not handle TTCap. By using TTCap description, support for font > transformations, such as slanting, adjusting glyph width, pseudo-bolding, > etc." > > Based on this I made a decision to depend on it. you can alwasy choose not > to install it. > > Ivan
kde man pages
Okay, so I've got artsc-config, artsd, artscat, and artsdsp done. However, I'm stuck on artsplay. What does it do, exactly? There is no documentation on it (duh) and afaict, it doesn't support any sort of commandline help switch (--help, -h, -?, and --h don't work). Using a google search, I figured out that it can play wav files, however, is that all it does? I.e., is it just a drop-in replacement for the "play" command? If so, I can whip up a man page saying so, but if it supports multlpe input formats, I'd like to know :-) Probably the best thing would be a link to any existing documentation, or a definitive answer. Any help appreciated! Thanks! D.A.Bishop
quanta and kde alpha
It's still crashing, with the debug output below. Should I send a bug report to kde, the quanta developers, here, or what? I'm afraid my ignorance is showing :-) Note this crash happens when trying to open any html file, not just one in particular. Also note, that I was *not* trying to open a file called Untitled.html, despite what the output to the terminal was. (no debugging symbols found)...(no debugging symbols found)... 0x40f4a789 in wait4 () from /lib/libc.so.6 #0 0x40f4a789 in wait4 () from /lib/libc.so.6 #1 0x40fb478c in __check_rhosts_file () from /lib/libc.so.6 #2 0x4075cf20 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.3 #3 0x40ed3738 in sigaction () from /lib/libc.so.6 #4 0x80b97ec in QCollection::newItem () #5 0x809062f in QCollection::newItem () #6 0x80a0300 in QCollection::newItem () #7 0x8076414 in QCollection::newItem () #8 0x806b84e in QCollection::newItem () #9 0x8111f80 in QCollection::newItem () #10 0x8109053 in QCollection::newItem () #11 0x40b1414f in QListView::doubleClicked () from /usr/lib/libqt.so.2 #12 0x40a840b7 in QListView::contentsMouseDoubleClickEvent () from /usr/lib/libqt.so.2 #13 0x40aca18d in QScrollView::viewportMouseDoubleClickEvent () from /usr/lib/libqt.so.2 #14 0x40ac818d in QScrollView::eventFilter () from /usr/lib/libqt.so.2 #15 0x40a83098 in QListView::eventFilter () from /usr/lib/libqt.so.2 #16 0x409e6df0 in QObject::activate_filters () from /usr/lib/libqt.so.2 #17 0x40a3013f in QWidget::event () from /usr/lib/libqt.so.2 #18 0x40994c2e in QApplication::notify () from /usr/lib/libqt.so.2 #19 0x406cefe4 in KApplication::notify () from /usr/lib/libkdecore.so.3 #20 0x40963a70 in QETWidget::translateMouseEvent () from /usr/lib/libqt.so.2 #21 0x4096133a in QApplication::x11ProcessEvent () from /usr/lib/libqt.so.2 #22 0x409602cc in QApplication::processNextEvent () from /usr/lib/libqt.so.2 #23 0x4099709f in QApplication::enter_loop () from /usr/lib/libqt.so.2 #24 0x409678e7 in QApplication::exec () from /usr/lib/libqt.so.2 #25 0x8068db8 in QCollection::newItem () #26 0x40ec416b in __libc_start_main () from /lib/libc.so.6 1539 quanta: KHTMLSettings::resetFontSizes adjustment is 4 1539 quanta: KHTMLSettings::resetFontSizes adjustment is 4 1539 khtml (part): KHTMLPart::init this=0x81bcf08 d=0x82845c8 1539 quanta: KHTMLSettings::resetFontSizes adjustment is 5 1539 quanta: KHTMLSettings::resetFontSizes adjustment is 5 1539 khtml (part): KHTMLPart::init this=0x82a0430 d=0x829ebc0 1539 quanta: KHTMLSettings::resetFontSizes adjustment is 5 1539 quanta: KHTMLSettings::resetFontSizes adjustment is 5 QToolBar::QToolBar main window cannot be 0. QToolBar::QToolBar main window cannot be 0. QToolBar::QToolBar main window cannot be 0. QToolBar::QToolBar main window cannot be 0. QToolBar::QToolBar main window cannot be 0. QToolBar::QToolBar main window cannot be 0. QGDict::hashStringKey: Invalid null key parseBlock(0x8407588) KWBufBlock: buildStringList this = 0x8407588 dirtyBlock(0x8407588) KWBufBlock: disposeRawData this = 0x8407588 1539 kdecore (KURL): KURL couldn't parse URL "Untitled1.html" 1539 kdecore (KURL): KURL couldn't parse URL "Untitled1.html" 1539 kdecore (KURL): KURL couldn't parse URL "Untitled1.html" 1539 kdecore (KURL): KURL couldn't parse URL "Untitled1.html" KCrash: crashing crashRecursionCounter = 2 KCrash: Application Name = quanta path = QToolBar::QToolBar main window cannot be 0. 1540 kio (KDirLister): KDirLister::openURL file:/home/david/ keep=false 1540 kio (Slave): createSlave for file:/home/david/ 1540 kdecore (KSocket): Performing lookup on //tmp/ksocket-david/drkonqicIE1sa.slave-socket 1540 kdecore (KSocket): Trying to listen on Unix /tmp/ksocket-david/drkonqicIE1sa.slave-socket 1540 kdecore (KSocket): Socket bound: 18 1540 kio (Slave): PID of slave = 1542 1540 kdecore (KSocket): Socket 18 accepted socket 17 1540 kio (Slave): slave has connected to application 1540 kio (Slave): got answer 10 1540 kdecore (KIconEffect): Image depth src != overlay! 1540 kio (KIOJob): stat file:/home/david/quanta.bt 1540 kio (KIOJob): error 11 /home/david/quanta.bt 1540 kdecore (KLibLoader): Deleting KLibLoader 0x80e2cf0 unnamed
kde2.2 alpha
I was wondering if, as a boon to the kde developers, all "pre-unstable" snapshots (of kde 2.2alpha specifically) could be built with debugging support. I've been trying to be a good end user and file bug reports on crashes and whatnot, but with the binaries stripped, oftentime I know it's somewhat useless. Of course, once they are rolled into sid/woody/whatever, they should be stripped again, but at least at this stage, I'd prefer to give the dev's all the help they can get. And if someone complains that the alpha-quality pre-unstable packages are too big, well, tough beans :-) Use the regular stuff, then. Just a thought, I might be missing something that is obvious to everyone else. It's happened before :-) TIA, D.A.Bishop
Re: Help! kdm loops
On Friday 20 April 2001 10:12, Steffen Evers wrote: > > I copied a perfectly working potato & kde2 installation from my portable > > to a partiotn of my desktop through NFS. > > Now it all works but kdm (and xdm). > > When I start the service (./kdm start ) it propose me to enter the login > > & password then the screen blackens and ,here it is again, the request > > for a login & password. In a nutshell kdm seems unable to start kde. The > > same behavior applies to xdm. > > I've surely messed up something. Take into account that startx makes kde > > start regularly! > > What sh ould I check now? > > I had a similar problem. Can't remember the details. The config files of > xdm and kdm are not set correctly. Fixed it with an executeable > ~/.xsession calling kde2. > > There is another problem that xdm/kdm does not process profile and > logout files (bash and etc). Fixed it by calling it from .xsession as > well. > > Seems to be a general xdm problem not kde specific. > > Bye, Steffen Actually, the problem I've had with this lately, is with ssh. That whole compiled with different ssl thingy. My solution has been to simply remove ssh from the afflicted machines, as kdm trys to start ssh-agent, and as there is no mechanism to prompt you for anything (i..e., when something screws up) it simply dumps you back to the beginning. This might or might not have anything to do with your error, but it's happened to me on two different machines. Oh, I guess you could figure out where it's calling ssh-agent and comment that out, but it was too much trouble for me. I don't use ssh all that often (bad david, no biscuit!) HTH, D.A.Bishop
Re: Help! kdm loops
On Friday 20 April 2001 17:31, Ivan E. Moore II wrote: > > Actually, the problem I've had with this lately, is with ssh. That whole > > compiled with different ssl thingy. My solution has been to simply > > remove ssh from the afflicted machines, as kdm trys to start ssh-agent, > > and as there is no mechanism to prompt you for anything (i..e., when > > something screws up) it simply dumps you back to the beginning. This > > might or might not have anything to do with your error, but it's happened > > to me on two different machines. Oh, I guess you could figure out where > > it's calling ssh-agent and comment that out, but it was too much trouble > > for me. I don't use ssh all that often (bad david, no biscuit!) > > /etc/X11/Xsession.options > > (which looks like this) > > # /etc/X11/Xsession.options > # > # configuration options for /etc/X11/Xsession > # See Xsession.options(5) for an explanation of the available options. > allow-failsafe > allow-user-modmap > allow-user-resources > allow-user-xsession > use-ssh-agent > > > just change use-ssh-agent to no-use-ssh-agent or just remove that > line..whatever > That's good to know. However, on machines where that's a problem (the libssl mismatch) I can't use ssh at all, so uninstalling the package was the cleanest way to get rid of that issue anyways. D.A.Bishop
Re: KDE 2.1.1 + XFree86 4.0.3 + Matrox G450
Your problem is that you installed libssl096. I would be willing to bet dollars to donutholes that you have ssh installed, and that startx is dying while trying to start the ssh-agent. If you run ssh from the command line it will come back with an error about mismatching libssl's. The quick work around is to uninstall ssh. The correct workaround is finding the ssh packages that work with that libssl. I don't recall where you get those from :-) Either way, that's your problem. D.A.Bishop On Saturday 28 April 2001 13:46, Frankie Fong wrote: > Hello everyone, > > I have a situation where I wonder if anybody experienced: > > I have a Debian 2.2r2 distribution installed. > I have XFree86 4.0.3 installed from source (built together with > the latest Matrox G450 driver) > > X works fine with twm as window manager. > > then I installed the KDE2.2.1 binary deb packages: > KDElibs3 > KDEbase > > successfully after I resolved the dependencies which > include the following packages: > XFree86 3.3.6, qt 2.3.0, > libssl096 -> libc6 2.2.2.4 -> libdb2.7.7-7 > > they all installed successfully. > > in order to rebuild my XFree86 4.0.3 after the libc6 update, > i installed libc6-dev 2.2.2.4. > > X worked fine after the upgrade (with twm). > > then I modified my .xinitrc script to run 'startkde' > instead of the 'twm' stuff. > > startx > > after some blinking and flashing of the screen, x dies. > > strangely enough, when i compared the /var/log/XFree86.0.log > of my successful twm start and my failed kde start, they > are both the same. > > I am hoping for someone who could point me to somewhere else > inside the system where i could find some KDE/X error messages. > > thanks in advance. > frankie > > > _ > Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: Man Pages
I've been volunteered to be the debian man pages writer/coordinator, though as far as I know, I'm the only one doing it :-) I'll send you a quick followup email with the man pages I've written so far attached (I don't want to clutter the list), but you should be warned that I have made them *somewhat* debian specific. This is also really my first attempt at writing documentation, so I know I've probably got a few things wrong. I'd be more than happy to help out with your project, though. D.A.Bishop On Friday 04 May 2001 01:00, Lauri Watts wrote: > Hi, > > We recently gained some volunteers to write man pages for the > console/daemon KDE apps, and so we've been doing some experimentation with > DocBook to set this up. > > We are specifically not wanting to use *roff as a source format, because > we've gone to some lengths to automate and simplify the translation > process, and DocBook is an excellent source format for this type of > documentation - the manual pages will of course be converted to *roff, > probably during compile time. > > I've just been informed however, that the Debian KDE packages have already > been creating manual pages. A cursory search through our CVS finds me a > handful of these, three in the kdebase module to be precise. > > It's entirely possible I'm being blind and not seeing them - or it's > possible they aren't in our CVS tree. In any case, I have some questions: > > 1: Where do I find them, and how can I get them (bearing in mind I don't > actually use Debian, or even Linux in fact). FTP or anonCVS access is > fine, or even webcvs, I just don't really know where to start looking. > > 2: To avoid duplication of effort, is there any objection to us (KDE) > taking the already written man pages and converting them to DocBook, and > then moving them into the doc directory of each module? All existing > credits and copyrights will of course be left intact. > Having them in the main CVS /doc/ hierarchies will mean they are > translated into most major languages and quite some minor ones as soon as > they are committed, which you must agree is a good thing. > > 3: If this is the case, that there are Debian written manual pages outside > of KDE CVS, and if in fact you would like to carry on writing them, perhaps > we can discuss a priority list, or some division (or at least, which end of > the long list we should each start at,) to save our new volunteers and your > writers covering the same applications. As I mentioned, we were planning > to concentrate efforts on the console apps and daemons first, as they > currently have no documentation at all. > > I'm not subscribed to your list - I did bookmark the archive page at > http://lists.kde.org, but it will probably be quicker to CC me with any > replies. > > Regards,
directory size limit?
Is there a limit to how large a single directory can be?? I was copying a large number of iso's into a directory to be shared via samba on my local network (one of those virtual cd programs for the kid's games), converting an NT box to linux+smb, when I ran into a problem. About a dozen iso's into it, the copy process stopped, claiming the drive was full. Except df says 35% of the 35gig drive is being used. And I can copy the iso's into other directories just fine. But any attempt to write more into that one fails with the disk full error. All me attempts at searching the net for "file directory size limit" just brought back the old 2.1 gig limit for a single file, which I have not reached at all. It's also not an inode problem, as there are about 50 files in there total, well under the ext2fs limit. And just to make sure, I deleted everything in there, recopied the files, and it bombed out in the same directory. Anyways, if anyone has run into this limit, please tell me, and if it's something else stupid, please tell me that too :-) Thanks, D.A.Bishop P.S. While this isn't *directly* kde-related, I was using konq to copy the files... :-P
Re: directory size limit?
On Monday 07 May 2001 07:23, you wrote: > > P.S. While this isn't *directly* kde-related, I was using konq to copy > > the files... :-P > > hmmm - does it work without konq? > if not, i would strongly suggest a file system check. many programs > report "disk full" (i guess, that's what the kernel says) when the > file system was found to be corrupted (look at your syslog). > Well, upon further examination, it appears to be a samba thing, not a linux or kde thing. But thanks for the quick reply anyways :-) D.A.Bishop
Re: scroll wheel
On this subject, has anyone found something for Linux that replicates the functionality of UniversalScroller (http://www.bebits.com/app/1359) which duplicates Logitech's Mouseware. Basically, clicking and holding the middle mouse button allows you to scroll up and down using normal mouse movements. It's nice enough that I prefer to use it even when I have a (true) scroll mouse (which I don't at the moment). I've done some 'net searches and haven't found anything. TIA, D.A.Bishop On Monday 07 May 2001 10:58, Guillermo Castro wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I've been using my mouse wheel in KDE 2.x, and I don't have imwheel > installed. The only thing I needed was to configure XF86Config-4 to handle > the mouse wheel: > > Section "InputDevice" > Identifier "Generic Mouse" > Driver "mouse" > Option "CorePointer" > Option "Device""/dev/psaux" > Option "Protocol" "ImPS/2" > Option "ZAxisMapping" "4 5" > EndSection > > The two relevant options are the protocol, which most be compatible with > the wheel, and the ZAxisMapping, which tells X to map the wheel. > > I have an intellimouse from MS, and I use the wheel as the middle button > (so I don't have to emulate the third buuton) > > Most KDE applications respond to the wheel (konqueror, kmail, konsole, > etc.) > > Hope this helps. > > On Sunday 06 May 2001 17:29, James Smith wrote: > > Does anyone know of a way to get a scroll wheel on a mouse working in KDE > > without using an external program like imwheel? > > > > JW, > > James Smith > > - -- > Guillermo Castro [EMAIL PROTECTED] > eMonterreyMonterrey NL, Mexico > Public key: > http://wwwkeys.eu.pgp.net:11371/pks/lookup?op=get&search=0x3E28D3B9 > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.0.4 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE69uIuuvZ3Qj4o07kRAuvjAJ9pbBdMZMbMo/VGTmx2ao1G/gtjCACZAWtQ > f7bK5Ak3NWeXPgFhm4lrAG8= > =5bdi > -END PGP SIGNATURE-
Re: help with kde install
Try this: apt-get install kdelibs3 and see what happens. After that works, go back and do the apt-get install task-kde again. HTH, D.A.Bishop On Tuesday 08 May 2001 10:41, Yuri Leikind wrote: > Hi all, > > I decided to install kde on my potato, added > deb http://kde.tdyc.com/debian potato main crypto optional > to sources.list, 'apt-get update'd it, found the task-kde > package and tried to install it - > > apt-get install task-kde > > It said: > > = > Some packages could not be installed. This may mean that you > have > requested an impossible situation or if you are using the > unstable > distribution that some required packages have not yet been > created > or been moved out of Incoming. > > Since you only requested a single operation it is extremely > likely that > the package is simply not installable and a bug report > against > that package should be filed. > The following information may help to resolve the situation: > > Sorry, but the following packages have unmet dependencies: > task-kde: Depends: kdelibs3 but it is not going to be > installed > Depends: kdebase but it is not going to be > installed > Depends: kdebase-libs but it is not going to be > installed > Depends: libkonq3 but it is not going to be > installed > Depends: konqueror but it is not going to be > installed > Depends: konsole but it is not going to be > installed > Depends: kuser but it is not going to be > installed > Depends: ksysv but it is not going to be > installed > Depends: kcron but it is not going to be > installed > Depends: kpackage but it is not going to be > installed > Depends: ksysctrl but it is not going to be > installed > Depends: secpolicy but it is not going to be > installed > Depends: kghostview but it is not going to be > installed > Depends: kview but it is not going to be > installed > Depends: kmail but it is not going to be > installed > Depends: korn but it is not going to be > installed > Depends: korganizer but it is not going to be > installed > Depends: abbrowser but it is not going to be > installed > Depends: ark but it is not going to be installed > Depends: kab but it is not going to be installed > Depends: karm but it is not going to be > installed > Depends: kcalc but it is not going to be > installed > Depends: kcharselect but it is not going to be > installed > Depends: kdepasswd but it is not going to be > installed > Depends: kdf but it is not going to be installed > Depends: kedit but it is not going to be > installed > Depends: kfind but it is not going to be > installed > Depends: khexedit but it is not going to be > installed > Depends: kjots but it is not going to be > installed > Depends: knotes but it is not going to be > installed > Depends: kpm but it is not going to be installed > Depends: ktimemon but it is not going to be > installed > Depends: koffice-libs but it is not going to be > installed > Depends: kchart but it is not going to be > installed > Depends: kword but it is not going to be > installed > Depends: kspread but it is not going to be > installed > Depends: killustrator but it is not going to be > installed > Depends: kpresenter but it is not going to be > installed > Depends: koshell but it is not going to be > installed > Depends: kivio but it is not going to be > installed > Depends: pixie but it is not going to be > installed > Depends: kpaint but it is not going to be > installed > Depends: kiconedit but it is not going to be > installed > E: Sorry, broken packages > = > > Am I doing something wrong? Or the package is out-of-date ? > > Please help me. > > Yuri Leikind > -- > ôÅÐÅÒØ É ÐÏÞÔÏ×ÙÅ ÒÁÓÓÙÌËÉ ÎÁ TUT.BY. ðÏÄÐÉÛÉÓØ ÉÌÉ ÚÁ×ÅÄÉ Ó×ÏÀ! > http://rasmas.tut.by
Re: thread reading in kmail - howto?
On Thursday 24 May 2001 10:28, Jaye Inabnit ke6sls wrote: >Hello, > > I really like being able to thread messages on lists, but reading through > them is next to impossible. I just finished re-reading the help files but I > don't see any way to read the mail without jumping wildly through out read > and unread messages. > > What I would like to do is have my mail sorted by date, then by threads. > Now, the first thread that I come to is ok, the next will jump somewhere > deep into un-read territory. Finally the next may or may not take me to the > next thread. So my next unread message is lost in the depths of unread > mails, instead of back to the top to continue reading in a linear date > sorted fashion. Other mailers do this? > > Any help on reading mails with threading enabled would be much appreciated. > I'm obviously missing the finer points of this code. > > tia I think your major problem is that (it sounds like) you are deleteing each email as you read it. When you do that, Kmail resorts all of the other messages in the thread, and splits stuff off/whatnot because the missing email can't be referenced anymore. The work around is to read throughout the thread, and then delete in batches. For instance, I read your email and then the reply by Hendrik before deleting either, because otherwise Hendrik's would have dropped four messages down to the bottom of my inbox. Not optimal, but as long as kmail immediately moves deleted mail to the trash, instead of just "marking" them as deleted (like mutt), this will be an issue. HTH, D.A.Bishop P.S. I'm not advocating a "mark for delete" paradigm. I much prefer the current system. But I do recognize the tradeoff :-)
Re: konqueror and flash
On Thursday 21 June 2001 08:57, Regnat Nikolaus wrote: > What's the proper way to get flash running with konqueror? I tried the > following: jre1.3 (from blackdown), the flash files copied to the > /usr/lib/netscape/plugin dir. Konqueror setup found the plugins (after > scanning), but flash still doesn't work. What's the problem with it? Flash > with Netscape works fine, but I don't like to install Netscape just for > that > > Nik Not only that, but for me flash has been crashing very regularly (almost every time) for the last few weeks, whereas before it worked fine. This happens both with 2.1.2 and 2.2alpha. Anyone else experiencing this? Workarounds? Thanks, David -- To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it. -- [EMAIL PROTECTED]
Re: nspluginviewer crashs with debian version of libqt 2.3.1
On Tuesday 26 June 2001 07:12, Jens Hoffmann wrote: > Ivan E. Moore II wrote: > > > I compiled it like this: > > > # ./configure -gif -system-zlib -system-libpng -system-libmng > > > -system-jpeg # make symlinks src-moc src-mt sub-src > > > and copied the newly compiled l > > > >so your not building with "-opengl -sm -xft -no-g++-exceptions" ? > > Doh! > well i tried the "-sm -xft -no-g++-exceptions" options before but i didn't > checked the gl support, since i thought that its enabled by default in the > upstream sources. but ldd told me, that i was wrong. > > changing -opengl to -no-opengl in the rules file resulted in a working lib > (i.e. no crashes with the nspluginviewer.) > so, it looks like the cause for the trouble is the damn binary only nvidia > driver. (again) > just then you think the nvidia driver behaves nicely, it strikes back with > a new problem :( but its kinda funny how it relates to the pluginviewer.. > > Ivan, any chance that you revive the extra package for a gl linked qt > and one without gl? :-/ > > > Jens > > > nvidia drivers version is 1.0-1251 > konqueror version: 4:2.2-cvs20010602-1 > libqt2 version: 2:2.3.1-1 > (debian sid) Well, I wouldn't start pointing fingers quite yet. I have the same problem (crashing nsplugin viewer) but no nVidia, just an old ATI Rage128 Pro. It could still be the gl-related stuff, I'm not ruling that out, but it happens with more than just your card. If you want to send me the qt package you made without gl support, I'll try it out and see if it gains me anything. -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: nspluginviewer crashs with debian version of libqt 2.3.1
Yep, my pluginviewer works great now (using Jen's recompiled qt package). Now I'm curious, what debian/kde apps *use* qt-gl? Is it more common than I know? 'Cuz I'm not thinking of anything off the top of my head. Daggon it, my needs come first! *grin* -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: qt + gl + problems + etc...
Sounds great. Though I'm sure you've thought of it, maybe have one of those "notes" that dpkg uses when a user install libqt-gl, saying VERY LOUDLY that they'll have to change the linking option for any qt-gl apps, and emails it to them if they have their priority level too high. Other than that (and the fact that my home desktop can't install 2.2 yet, missing kdelibs3 >=4:2.2-cvsfoo-1 in unstable) and I'm *really* liking this new kde :-) I've been running the alpha at work for the last week (from people.debian.org), and aside from konq's tendency to wonk out at seeminly random places once a day, it's very nice. Please keep up the good work! Many Thanks, D.A.Bishop On Wednesday 27 June 2001 17:57, Ivan E. Moore II wrote: > Ok...so with kde 2.2 mostly uploaded (some bits already installed) to sid I > turned focus to QT again especially since I've personally had many crashes > of konsole due to the whole GL bit. > > so this lead me to a immediate solution. I still do not like this solution > however this is one that I am comfortable in sticking with if a proper > one does not arise before woody's release. > > so your asking...what's the solution??? > > well...a libqt2-gl package...but not like before. I have created a > completely seperate source package (qt-x11-gl) which builds 2 packages: > libqt2-gl and libqt-gl-dev. The actual qt library it creates also has been > changed. Instead of it providing /usr/lib/libqt.so.* I've renamed the > library to libqt-gl so that it can co-exist with a normal (non-gl'd) qt > library. > > So..what does this do for everyone you might ask? > >allows packages that do not need the GL bits of QT to not have to deal > with a library with them compiled in nor the issues surrounding QT + GL + > threads. (short answer on this...flash plugin works, no more konsole > crashes, etc...) This also allows for applications that do need GL support > to still exist within the distribution. (oh yea..and the pure_virtual > problems *should* go away) > > > So..what's the drawbacks you might ask? > > 1: (obvious) yet another package (well 2)...not really that big of a > deal 2: anyone who wants their package to link to the GL'd version of QT > *must* modify their build process to link to libqt-gl instead of libqt. ( > "-lqt-gl" instead of "-lqt") > > Overall I think this will be a good solution until someone comes up with > another better solution. I'm sure I'll get several bug reports from people > saying their GL based apps broke and then I'll hear them gripe when I tell > them they need to install libqt-gl-dev and modify their source. > > any major issues before I upload the new packages? > > Ivan
Re: qt + gl + problems + etc...
Good point! Maybe, use the debconf warning, but attach it to a "libqt-gl-dev" package, that those who are going to be compiling their own software will need to install, but a normal user wouldn't. I'm just trying to make your job easier :-) It's not like you don't have a ton of emails to wade through anyways.. As for beta1, I'm looking forwards to it B-) David On Wednesday 27 June 2001 20:46, Ivan E. Moore II wrote: > well..doing a debconf warning won't do any good for the maintainers of > the packages. It'll only annoy any users who install the library. I'm > expecting that people will file bug reports rather quickly that apps fail > and the maintainers will come yell at me and all will eventually be good. > > new maintainers will find out by reading documentation or asking me. > > as for 2.2...beta1 is really nice. kdelibs is in incoming and kdebase is > on it's way up right now. > > Ivan > > On Wed, Jun 27, 2001 at 09:10:45PM -0600, David Bishop wrote: > > Sounds great. Though I'm sure you've thought of it, maybe have one of > > those "notes" that dpkg uses when a user install libqt-gl, saying VERY > > LOUDLY that they'll have to change the linking option for any qt-gl apps, > > and emails it to them if they have their priority level too high. Other > > than that (and the fact that my home desktop can't install 2.2 yet, > > missing kdelibs3 > > > > >=4:2.2-cvsfoo-1 in unstable) and I'm *really* liking this new kde :-) > > > I've > > > > been running the alpha at work for the last week (from > > people.debian.org), and aside from konq's tendency to wonk out at > > seeminly random places once a day, it's very nice. Please keep up the > > good work! > > > > Many Thanks, > > > > D.A.Bishop > > > > On Wednesday 27 June 2001 17:57, Ivan E. Moore II wrote: > > > Ok...so with kde 2.2 mostly uploaded (some bits already installed) to > > > sid I turned focus to QT again especially since I've personally had > > > many crashes of konsole due to the whole GL bit. > > > > > > so this lead me to a immediate solution. I still do not like this > > > solution however this is one that I am comfortable in sticking with if > > > a proper one does not arise before woody's release. > > > > > > so your asking...what's the solution??? > > > > > > well...a libqt2-gl package...but not like before. I have created a > > > completely seperate source package (qt-x11-gl) which builds 2 packages: > > > libqt2-gl and libqt-gl-dev. The actual qt library it creates also has > > > been changed. Instead of it providing /usr/lib/libqt.so.* I've renamed > > > the library to libqt-gl so that it can co-exist with a normal > > > (non-gl'd) qt library. > > > > > > So..what does this do for everyone you might ask? > > > > > >allows packages that do not need the GL bits of QT to not have to > > > deal with a library with them compiled in nor the issues surrounding QT > > > + GL + threads. (short answer on this...flash plugin works, no more > > > konsole crashes, etc...) This also allows for applications that do need > > > GL support to still exist within the distribution. (oh yea..and the > > > pure_virtual problems *should* go away) > > > > > > > > > So..what's the drawbacks you might ask? > > > > > > 1: (obvious) yet another package (well 2)...not really that big of > > > a deal 2: anyone who wants their package to link to the GL'd version of > > > QT *must* modify their build process to link to libqt-gl instead of > > > libqt. ( "-lqt-gl" instead of "-lqt") > > > > > > Overall I think this will be a good solution until someone comes up > > > with another better solution. I'm sure I'll get several bug reports > > > from people saying their GL based apps broke and then I'll hear them > > > gripe when I tell them they need to install libqt-gl-dev and modify > > > their source. > > > > > > any major issues before I upload the new packages? > > > > > > Ivan > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > > [EMAIL PROTECTED] > > ---end quoted text---
kde2.2-beta1
So, I'm now running beta-1 on my box, and enjoying the hell out of all the nifty new options (and speedups, thanks!). All of the crash bugs I was having with alpha2 in the kcontrol panel are gone, they all work (pretty much, I have a reproducible bug I'll be filing in a minute) flawlessly. However, konq crashes tons more than it did, and frequently the kio_http hangs and I have to manually kill it and restart konq before I can continue surfing. The error I get is the exact same one I got before when going through an authenticating proxy (http protocol died unexpectedly, pre 2.1.2 days), but in this case it works great for a few minutes, then dies. Is anyone else seeing this, or is this a case of me being screwed by our auth_proxy? Or (gulp) can this be solved by blowing away my .kde dir? I'm crossposting this with debian-kde and kfm-devel, as I'm not yet sure if this is a packaging issue, or a "hard core" kde issue. If there's something else I can do, please tell me and I'll do it. If it's of interest, if I run konqueror from the command line, it outputs this when it errors: kio (KRun): ERROR: 0x83ad520 ERROR 43 The process for the http://slashdot.org protocol died unexpectedly. and it won't work again until I kill the kio_http slave (after closing konq). Here's a listing of the beta1 packages I still have installed, followed by the alpha2 (just in case that's screwing it up somehow: [EMAIL PROTECTED]:/home/david# dpkg --list | grep -i 2.2-cvs2001062 ii aktion 2.2-cvs2001062 KDE frontend to xanim ii kcron 2.2-cvs2001062 Crontab editor for KDE ii kdebase2.2-cvs2001062 KDE core applications ii kdebase-audiol 2.2-cvs2001062 KDE audio libraries amd modules for kdebase ii kdebase-crypto 2.2-cvs2001062 KDE core applications (Crypto modules) ii kdebase-libs 2.2-cvs2001062 KDE libraries amd modules for kdebase ii kdelibs3 2.2-cvs2001062 KDE core libraries (runtime files) ii kdelibs3-crypt 2.2-cvs2001062 KDE core libraries (Crypto Modules) ii kdelibs3-cups 2.2-cvs2001062 KDE print system (CUPS support) ii kdepasswd 2.2-cvs2001062 A Password changer frontend for KDE ii kdewallpapers 2.2-cvs2001062 Some wallpapers for KDE ii kdf2.2-cvs2001062 Disk space GUI for KDE ii kdict 2.2-cvs2001062 dict client based on KDE/QT ii kedit 2.2-cvs2001062 A simple text editor for KDE ii kfract 2.2-cvs2001062 fractal generator for KDE ii kghostview 2.2-cvs2001062 PostScript viewer for KDE. ii kiconedit 2.2-cvs2001062 An icon editor for creating KDE icons ii kit2.2-cvs2001062 AOL Instant messanger frontend for KDE ii kmail 2.2-cvs2001062 Mail Client based on QT and KDE ii kmid 2.2-cvs2001062 midi/karaoke player for KDE ii kmix 2.2-cvs2001062 KDE based mixer app ii knewsticker2.2-cvs2001062 A News ticker for KDE ii knode 2.2-cvs2001062 News reader for KDE ii konqueror 2.2-cvs2001062 KDE's advanced File Manager, Web Browser and ii konsole2.2-cvs2001062 X terminal emulation for KDE ii korn 2.2-cvs2001062 Mail notifier for KDE ii kpackage 2.2-cvs2001062 Software package tool for KDE ii kpaint 2.2-cvs2001062 A Simple Paint Program for KDE ii kruler 2.2-cvs2001062 a screen ruler and color measurement tool fo ii kscd 2.2-cvs2001062 KDE based cd player ii kscreensaver 2.2-cvs2001062 Screen savers for KDE ii ksirc 2.2-cvs2001062 IRC Client based on QT and KDE ii ksnapshot 2.2-cvs2001062 Screenshot application for KDE ii ksysctrl 2.2-cvs2001062 Hardware configuration tool for KDE ii ksysv 2.2-cvs2001062 SysV-style init configuration editor ii kuser 2.2-cvs2001062 A user/group administration tool for KDE ii kview 2.2-cvs2001062 A simple image viewer/converter for KDE. ii libkdenetwork1 2.2-cvs2001062 Common libraries needed for KDE network appl ii libkonq3 2.2-cvs2001062 Core libraries for KDE's file manager ii libmimelib-dev 2.2-cvs2001062 mime library - development version ii libmimelib12.2-cvs2001062 mime libraries needed for some KDE applicati ii lilo-config2.2-cvs2001062 lilo configuration plugin for KDE ii mpeglib2.2-cvs2001062 mp3 and mpeg I video/audio library for linux ii secpolicy 2.2-cvs2001062 PAM security policy configuration tool [EMAIL PROTECTED]:/home/david# dpkg --list | grep -i 2.2-cvs2001060 ii kab2.2-cvs2001060 An addressbook for KDE ii karm 2.2-cvs2001060 A time tracker for KDE ii kcalc 2.2-cvs2001060 A calculator for KDE ii kcharselect2.2-cvs2001060 A Character set selector for KDE ii kdebase-doc2.2-cvs2001060 Documentation for Applications in kdebase ii kdelibs3-doc 2.2-cvs2001060 KDE core library documentation ii kdm2.2-cvs2001060 The K Desktop Manager ii keystone 2.2-cvs2001060 Virtual Network Computer Client for KDE i
Re: kde2.2-beta1
On Thursday 28 June 2001 02:40 pm, Ivan E. Moore II wrote: > > So, I'm now running beta-1 on my box, and enjoying the hell out of all > > the nifty new options (and speedups, thanks!). All of the crash bugs I > > was having with alpha2 in the kcontrol panel are gone, they all work > > (pretty much, I have a reproducible bug I'll be filing in a minute) > > flawlessly. However, konq crashes tons more than it did, and frequently > > the kio_http hangs and I have to manually kill it and restart konq before > > I can continue surfing. The error I get is the exact same one I got > > before when going through an authenticating proxy (http protocol died > > unexpectedly, pre 2.1.2 days), but in this case it works great for a few > > minutes, then dies. Is anyone else seeing this, or is this a case of me > > being screwed by our auth_proxy? Or (gulp) can this be solved by blowing > > away my .kde dir? I'm crossposting this with debian-kde and kfm-devel, > > as I'm not yet sure if this is a packaging issue, or a "hard core" kde > > issue. If there's something else I can do, please tell me and I'll do > > it. If it's of interest, if I run konqueror from the command line, it > > outputs this when it errors: > > > > kio (KRun): ERROR: 0x83ad520 ERROR 43 The process for the > > http://slashdot.org protocol > > died unexpectedly. > > > > and it won't work again until I kill the kio_http slave (after closing > > konq). Here's a listing of the beta1 packages I still have installed, > > followed by the alpha2 (just in case that's screwing it up somehow: > > I'm glad to hear that your having a mostly good experience with the beta. > I personally have not had any problems with konq however I do not use a > proxy from here. I'll set one up so that I can do some tests... > > Ivan Yes, let me reiterate that everything else is going swimmingly (my respect-o-meter for all kde hackers is shooting through the roof). However, please note when you set up the proxy, make sure it's authenticating, that seems to trigger more bugs :-) In the meantime, I'm going to blow away my ..kde (gahk) and see if that cleans anything up. It's now gone through 2.1.0, ..1, .2, pre-alpha, then back to .2, and alpha2, and beta1. Something could very well have gotten screwed up in all that, that wasn't exposed until now (or created until now). I'll make sure and report on the efficacy. -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: kdelibs3 and beta1
On Thursday 28 June 2001 03:30 pm, Dan Berdine wrote: > When I try to update to the kde2.2beta1 with dselect, all the beta > packages depend on kdelibs3 >=2.2-cvs20010622-1 but kdelibs3 isn't > updated beyond 2.1.2. I'm using http://http.us.debian.org/, should I > be looking at a different mirror? > > Thanks, > > -Dan > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] You can get all of the incoming .debs at http://incoming.debian.org. Of course, if you install them before they are "official", you'll have to do it manuall, but it's not that hard (I did it this morning). Just download the kdelibs3 .deb, dpkg -i foo.deb, then apt-get upgrade, and repeat (you'll also be missing other packages that'll you need to download). Or, wait until (probably) tomorrow. -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: kde2.2-beta1
On Thursday 28 June 2001 04:23 pm, David Bishop wrote: > Yes, let me reiterate that everything else is going swimmingly (my > respect-o-meter for all kde hackers is shooting through the roof). > However, please note when you set up the proxy, make sure it's > authenticating, that seems to trigger more bugs :-) In the meantime, I'm > going to blow away my ..kde (gahk) and see if that cleans anything up. > It's now gone through 2.1.0, ..1, .2, pre-alpha, then back to .2, and > alpha2, and beta1. Something could very well have gotten screwed up in all > that, that wasn't exposed until now (or created until now). I'll make sure > and report on the efficacy. Let me be so crass as to follow-up my own email, "initializing" .kde didn't fix anything. I was able to goto debian.org from the splash page link, tried to type in slashdot.org, and immediately got the "http protocol unexpectedly died" error. The *only* "weird" thing about my setup is that I'm running the qt library that Jen compiled a few days ago, to get flash working. Could that be the root cause? I didn't even think of it 'till now. Jen, are you running the beta yet? Any issues? -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: kde2.2-beta1
Suprising nobody, that didn't help. Aargh. I can almost *taste* the desktop nirvana that is kde 2.2 *grin*. On Thursday 28 June 2001 03:44 pm, Ivan E. Moore II wrote: > i doubt it..you can grab the new libqt packages out of incoming and find > out. > > Ivan > > On Thu, Jun 28, 2001 at 04:37:37PM -0700, David Bishop wrote: > > On Thursday 28 June 2001 04:23 pm, David Bishop wrote: > > > > > > > Yes, let me reiterate that everything else is going swimmingly (my > > > respect-o-meter for all kde hackers is shooting through the roof). > > > However, please note when you set up the proxy, make sure it's > > > authenticating, that seems to trigger more bugs :-) In the meantime, > > > I'm going to blow away my ..kde (gahk) and see if that cleans anything > > > up. It's now gone through 2.1.0, ..1, .2, pre-alpha, then back to .2, > > > and alpha2, and beta1. Something could very well have gotten screwed > > > up in all that, that wasn't exposed until now (or created until now). > > > I'll make sure and report on the efficacy. > > > > Let me be so crass as to follow-up my own email, "initializing" .kde > > didn't fix anything. I was able to goto debian.org from the splash page > > link, tried to type in slashdot.org, and immediately got the "http > > protocol unexpectedly died" error. The *only* "weird" thing about my > > setup is that I'm running the qt library that Jen compiled a few days > > ago, to get flash working. Could that be the root cause? I didn't even > > think of it 'till now. Jen, are you running the beta yet? Any issues? > > -- > > "To me vi is Zen. To use vi is to practice zen. Every command is > > a koan. Profound to the user, unintelligible to the uninitiated. > > You discover truth everytime you use it." [EMAIL PROTECTED] > > > > [EMAIL PROTECTED] > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > > [EMAIL PROTECTED] > > ---end quoted text--- -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: kde2.2-beta1
On Thursday 28 June 2001 18:28, Jens Hoffmann wrote: > On Friday 29 June 2001 01:37, David Bishop wrote: > > Let me be so crass as to follow-up my own email, "initializing" .kde > > didn't fix anything. I was able to goto debian.org from the splash page > > link, tried to type in slashdot.org, and immediately got the "http > > protocol unexpectedly died" error. The *only* "weird" thing about my > > setup is that I'm running the qt library that Jen compiled a few days > > ago, to get flash working. Could that be the root cause? I didn't even > > think of it 'till now. Jen, are you running the beta yet? Any issues? > > I have the beta running right now. > konqueror works fine so far - no crashes, but i don't use a proxy. > > And yes the beta is really nice! :) > > > Jens *thpththptph* to you too.. ;-) David
Re: Create new users in a special way
I would suggest debian-user, as I don't see how KDE relates to your question. Have fun! On Friday 29 June 2001 02:45 am, Heidelinde Meier wrote: > Hello! > > Perhaps my question is not too difficult for you to answer: > I want to create more than 5000 new users on my system. > Because there are 5000 users who already got their password, that means > for me: I already got the complete files > /etc/passwd and /etc/shadow on my system. > > Now I want to create /home/directories in the way the programm "adduser" > create /home/directories /copying files from /etc/skel and copy them in > user's home directory, and so on. > > Now my question: I don't want to type in every information on each user > while executing "adduser", because "adduser" asks for the password, the > user's identity - these should be ignored. > For me it would be easy to type in one command (which can be filled by > the information that is given from the file /etc/passwd) , perhaps with > "adduser" and lots of options, but without typing the information by > hand. The rest should be automatically generated. > > Perhaps you have some nice ideas on that. > > Hope you understand my English - thanks. > > Heide -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
kdm beta1
It's just my week to discover bugs :-) This is what I get while trying to install the latest kdm from incoming. I can't imagine what I'm doing wrong, and since I'm always right/perfect, it must be your fault *grin*. [EMAIL PROTECTED]:/home/david/tmp# dpkg -i kdm_2.2.0-0beta1-1_i386.deb (Reading database ... 75907 files and directories currently installed.) Preparing to replace kdm 4:2.2-cvs20010602-1 (using kdm_2.2.0-0beta1-1_i386.deb) ... cp: omitting directory `/etc/X11/kdm/authdir' cp: cannot stat `/etc/X11/kdm/kdmrc': No such file or directory cp: omitting directory `/etc/X11/kdm/pixmaps' dpkg: error processing kdm_2.2.0-0beta1-1_i386.deb (--install): subprocess pre-installation script returned error exit status 1 /var/lib/dpkg/info/kdm.postinst: cleanup: command not found dpkg: error while cleaning up: subprocess post-installation script returned error exit status 127 Errors were encountered while processing: kdm_2.2.0-0beta1-1_i386.deb [EMAIL PROTECTED]:/home/david/tmp# -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: KDE 2.2beta1 impressions
The konsole now defaults to having no history, so it's not the keys, you just need to go into the settings and set the history from "1" to whatever (usually 1000 for me). I don't remember exactly which menu it's in, and I just finished uninstalling everything having to do with kde in an attempt to "reinitialize" all my settings, and haven't gotten around to reinstalling yet :-) Dunno about arts HTH, D.A.Bishop On Fri, Jun 29, 2001 at 07:26:20PM +0200, Stephan Jaensch wrote: > Hi, > > > first of all, great work with the 2.2beta1 packages, Ivan! Keep up the > excellent work! > > Now, for the bugs I have found... :-) > > arts alsa support seems to be linked against alsa 0.5. If I try to start > artsd with alsa support it just segfaults. Since this is unstable, I think > artsd should be linked against alsa-0.9. However, when I tried compiling KDE > on my own this failed, so some source modifications are needed... > > Second, pageup/pagedown/home/end do not work anymore in konsole. Seems like > the old problem we had some time ago... > > That's all! Everything else works just as expected! > > > Ciao... > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: KDE 2.2beta1 impressions
All ready tried that, didn't help. But I also have a lot of left-over packages from ald versions of kde lying around, and want to make sure that everything is "latest and greatest", which apt-get normally handles really well, but doesn't cover all possible bases (for instance, I still have obsoleted packages installed like aktion, which by itself won't cause the problems I am having, but there are others like it). IOW, it's not the per-user stuff that is crashing me :-) And looking back at my email s/settings/packages/. On Fri, Jun 29, 2001 at 01:41:49PM -0500, Tom Joseph wrote: > Um, couldn't you just remove ~/.kde ...? Does KDE keep per-user config > stuff anywhere else? > > --Tom Joseph > > On Fri, 29 Jun 2001, David Bishop wrote: > > > > > The konsole now defaults to having no history, so it's not the keys, you > > just need to go into the settings and set the history from "1" to whatever > > (usually 1000 for me). I don't remember exactly which menu it's in, and I > > just finished uninstalling everything having to do with kde in an attempt > > to "reinitialize" all my settings, and haven't gotten around to > > reinstalling yet :-) Dunno about arts > > > > HTH, > > > > D.A.Bishop > > > > On Fri, Jun 29, 2001 at 07:26:20PM +0200, Stephan Jaensch wrote: > > > Hi, > > > > > > > > > first of all, great work with the 2.2beta1 packages, Ivan! Keep up the > > > excellent work! > > > > > > Now, for the bugs I have found... :-) > > > > > > arts alsa support seems to be linked against alsa 0.5. If I try to start > > > artsd with alsa support it just segfaults. Since this is unstable, I think > > > artsd should be linked against alsa-0.9. However, when I tried compiling > > > KDE > > > on my own this failed, so some source modifications are needed... > > > > > > Second, pageup/pagedown/home/end do not work anymore in konsole. Seems > > > like > > > the old problem we had some time ago... > > > > > > That's all! Everything else works just as expected! > > > > > > > > > Ciao... > > > > > > > > > -- > > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: KDE 2.2beta1 impressions
On Fri, Jun 29, 2001 at 01:07:58PM -0600, Ivan E. Moore II wrote: > On Fri, Jun 29, 2001 at 01:01:34PM -0600, David Bishop wrote: > > > > All ready tried that, didn't help. But I also have a lot of left-over > > packages from ald versions of kde lying around, and want to make sure that > > everything is "latest and greatest", which apt-get normally handles really > > well, but doesn't cover all possible bases (for instance, I still have > > obsoleted packages installed like aktion, which by itself won't cause the > > problems I am having, but there are others like it). IOW, it's not the > > per-user stuff that is crashing me :-) And looking back at my email > > s/settings/packages/. > > > aktion is not obsolete. :) > Oh. Heh. I, um, knew that :-P Gah, is today Monday? It feels like a monday.. > -- > > Ivan E. Moore II > [EMAIL PROTECTED] > http://snowcrash.tdyc.com > GPG KeyID=90BCE0DD > GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: KDE 2.2beta1 impressions
Yep, I do know that... Which is why when I thought it was my personal conf, I 'mv .kde .kdebackup'ed instead of 'rm -fR .kde'. When that didn't fix anything, I moved it right back. I can test software *and* keep my config :-P David On Fri, Jun 29, 2001 at 03:40:22PM -0500, Tom Joseph wrote: > That's true but part of the territory when testing software - I just > assumed everyone would know that... > > --Tom Joseph > > On Fri, 29 Jun 2001, Andre Alexander Bell wrote: > > > On Friday, 29. June 2001 20:41, Tom Joseph wrote: > > > Um, couldn't you just remove ~/.kde ...? Does KDE keep per-user config > > > stuff anywhere else? > > > > Sure, but then you might loose some data you want to keep. (Knotes, > > Kab-Adressbook, Some programm configurations...) > > > > Andre > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: overlapping pacakges
On Saturday 30 June 2001 08:57, Jens Benecke wrote: > On Sat, Jun 30, 2001 at 04:51:59PM +0200, Jens Benecke wrote: > > On Sat, Jun 30, 2001 at 12:01:33AM -0700, Ilan Rabinovitch wrote: > > > Hey, > > > > > > I noticed several of the KDE packages seem to have overlapping files.. > > > > Worse, some of the new packages have directories in places that had been > > symlinks or file before. e.g. I just got > > follow-up: > > The directory actually doesn't exist BUT it is still in dpkg's file lists, > i.e. therefore dpkg complains. The various conflicts are (drum roll please): dpkg: error processing /var/cache/apt/archives/ksirc_4%3a2.2-cvs20010622-1_i386.deb (--unpack): trying to overwrite `/usr/share/icons/hicolor/16x16/apps/ksirc.png', which is also in package keystone dpkg-deb: subprocess paste killed by signal (Broken pipe) [EMAIL PROTECTED]:/var/cache/apt/archives$ dpkg -i konqueror_4%3a2.2.0-0beta1-2_i386.deb kdebase-libs_4%3a2.2.0-0beta1-2_i386.deb dpkg: considering removing kdebase-libs in favour of konqueror ... dpkg: no, cannot remove kdebase-libs (--auto-deconfigure will help): ksysctrl depends on kdebase-libs kdebase-libs is to be removed. dpkg: regarding konqueror_4%3a2.2.0-0beta1-2_i386.deb containing konqueror: konqueror conflicts with kdebase-libs (<< 4:2.2-alpha1-0) kdebase-libs (version 4:2.1.1.0-10) is installed. dpkg: error processing konqueror_4%3a2.2.0-0beta1-2_i386.deb (--install): conflicting packages - not installing konqueror (Reading database ... 61579 files and directories currently installed.) Preparing to replace kdebase-libs 4:2.1.1.0-10 (using kdebase-libs_4%3a2.2.0-0beta1-2_i386.deb) ... Unpacking replacement kdebase-libs ... Replacing files in old package kdebase ... dpkg: error processing kdebase-libs_4%3a2.2.0-0beta1-2_i386.deb (--install): trying to overwrite `/usr/lib/kde2/libkshellcmdplugin.so', which is also in package konqueror Unpacking replacement kdelibs3 ... dpkg: error processing kdelibs3_4%3a2.2.0-0beta1-1_i386.deb (--install): trying to overwrite `/usr/lib/kde2/kio_help.so', which is also in package kdebase-libs dpkg: error processing kdebase-libs_4%3a2.2.0-0beta1-2_i386.deb (--install): trying to overwrite `/usr/lib/kde2/libkcm_screensaver.la', which is also in package kscreensaver dpkg: error processing /var/cache/apt/archives/knode_4%3a2.2-cvs20010622-1_i386.deb (--unpack): trying to overwrite `/usr/share/icons/hicolor/16x16/apps/knode.png', which is also in package keystone This is on a box going straight from 2.1.2 to beta1 (well, latest available anyways). Also, there wasn't anything broken that dpkg couldn't fix (not using any force options, though I did have to uninstall konq temporarily). Hope that helps! Yours truly, David "The Bug Finder" Bishop
latest konq dieing with auth_proxy
That is *definetly* the problem, after extensive testing, and now I have the auth_proxy setup at home to prove it. Ivan, I've setup squid with authentication, and you can use it to test (in case you haven't had time in the last couple days to do it yourself). Email me privately and I'll get you the hostname/logon information. Everyone else: if you are currently in a situation where you have to use an authenticating proxy, do not upgrade to the latest kde packages. You *will* get frustrated as hell :-) David
Re: KDE2.2 Beta1, terminal emulation
Haven't tried noatun yet, and with most everything else, I've been seeing speedups, but as for the x-terminal-emulator, try looking in /etc/alternatives for x-terminal-emulator and seeing if 1) it is there and 2) that it's pointing to konsole. However, I just looked and on my box it's pointing to xterm. Hrrm. I don't know how that works. Ivan, does the first terminal program that gets installed set that link, and all the rest leave it alone? I guessing that the link is there, but it's dangling for whatever reason, and when konsole was installed it just checked to see if it was there, not that it was valid. Of course, and as always, I'm probably talking out of my buttocks B-) HTH, D.A.Bishop On Saturday 30 June 2001 17:14, Dan Berdine wrote: > Been using the beta a while, mostly really nice, but of course I have > noticed a few minor bugs... > > I set Konsole to be used as the default terminal emulator, but every > app I try to launch which should run in a terminal still complains that > it can't find x-terminal-editor. > > Also some things tend to be a little slower than before (noatun skips a > little and holds up the gui even tho it takes like .3% CPU and arts is > only using maybe 7%) but I expect thats just a beta not being optimized > yet... > > I think everything else I'v had a problem with has been mentioned > already... > > Quite nice on the whole, great job :) > > -Dan > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED]
Re: KDE2.2 Beta1, terminal emulation
On Saturday 30 June 2001 18:30, Dan Berdine wrote: > On Saturday 30 June 2001 07:37 pm, David Bishop wrote: > > Haven't tried noatun yet, and with most everything else, I've been > > seeing speedups, but as for the x-terminal-emulator, try looking in > > /etc/alternatives for x-terminal-emulator and seeing if 1) it is > > there and 2) that it's pointing to konsole. However, I just looked > > and on my box it's pointing to xterm. Hrrm. I don't know how that > > works. Ivan, does the first terminal program that gets installed set > > that link, and all the rest leave it alone? I guessing that the link > > is there, but it's dangling for whatever reason, and when konsole was > > installed it just checked to see if it was there, not that it was > > valid. Of course, and as always, I'm probably talking out of my > > buttocks B-) > > ah, thanks, it was pointing to 'powershell' whatever that is... xterm > works. > > Not sure why, but this reminds me of another thing I'v been wondering > about since I started using KDE... Kedit, Kwrite, and now Kate. What > gives? Do we just play with all three till one strikes us as good? As > far as I can tell the difference in these are nowhere near significant > enough to mean they are meant for different purposes... > > Oh well :) Thanks again, > > -Dan Again, probably talking out of my butt, but it looks like kate is based off of kwrite (if you look at the online help, there are a lot of "thanks to foo kwrite developer" in there). So I think the split is: kedit == textpad while kate == kde version of gvim. At least on my system kedit starts a lot quicker that kate does, so it must be doing *something* more :-). D.A.Bishop P.S. I'm CC:ing the list in case anyone else has your problem. One less person bugging Ivan about something is one step closer to having a happy maintainer *grin*
more "protocol dying unexpectedly"
But now in the help screen. This is 100% reproducible on my system. Open any kde app, select help->contents. Wait for it to load, the click on "introduction". Then click on "next". The viewing window will go blank and an error message pops up saying "the process for the help protocol died unexpectedly". If it doesn't crap out the first time you click next, it will the second. Is anyone else seeing this? I have testing using kate, kmail, and konqy (well, duh, david, they are all using the same help subsystem *slaps self*). I don't know about anyone else, but I'm *excited* to be finding all this stuff. It feels like I'm actually contributing something. HTH, David
Re: more "protocol dying unexpectedly"
On Saturday 30 June 2001 20:57, Jaldhar H. Vyas wrote: > On Sat, 30 Jun 2001, David Bishop wrote: > > Is anyone else seeing this? > > Yup. Then I'll file a bug report with the kde guys. Thanks for the conformation. David
Re: kdm won't start
On Sunday 01 July 2001 08:37, Jonathan Schmitt wrote: > Hi, > after I upgraded to x4.1.0, kde2 wouldn't start anymore. I found out, that > some files had moved to other directorys and got 'startx' working. > But kdm still isn't working. I then looked through the files located in > /usr/X11/kdm but couldn't find an error there (well, no obvious error). > Running kdm with the -debug option results in the attached entry in > /var/log/daemon.log. > Unfortunately, as I have no log of an working kdm here, I can't see an > error there, except two things: > the file xdm-keys is not present on the System > the authdir directory is empty. > > Anyone an idea? Thanks >js I know this is the "M$" way, but I just uninstalled kdm and reinstalled and it worked fine. Oh, and ran dpkg --purge kdm as well. See if that fixes it. David
Re: pure_virtual the never ending story
On Monday 02 July 2001 11:26 am, Arne Scheffler wrote: > Ivan E. Moore II wrote: > > On Mon, Jul 02, 2001 at 04:15:29PM +0200, Arne Scheffler wrote: > >>Hi, > >>I follow this list a while and I know about the pure_virtual problem > >>with libqt and libqt-gl. > >>My Problem is that I only got libqt installed. And if I start kde > >>it stops in the starting phase with a message dialog, where it tells me > >>that something went wrong with dcop. When I start dcopserver manually it > >>claims the following : > >>--- > >>dcopserver: error while loading shared libraries: /usr/lib/libqt.so.2: > >>undefined symbol: __pure_virtual > >>--- > >>So I don't know really what I can do now to solve this problem. A new > >>installation of the kde & qt packages doesn't change anything. > >> > >>Some hints ? > >> > >>I'm running testing on a powerpc machine. > > > > either wait until the packages from unstable make their way into testing > > or grab them from testing. > > They are grabbed from testing. > > arne I think he meant "grab them from unstable from *within* testing". The one's in testing are the old libraries, suspectible to the pure_virtual problem. The one's in unstable aren't. Thus, you can wait for them to filter down, or you can get them yourself. Your choice :-) -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: preset bookmarks
On Tuesday 03 July 2001 01:19 pm, Ivan E. Moore II wrote: > ok all you kde junkies...anyone know how I can setup a default bookmark > list so that upon installation a user will have a few bookmarks (ie things > like www.debian.org/debianplanet/etc...)? > > Ivan I'll say the obvious one: kde.themes.org. Of course, my mind just went completely blank and I can't think of any others :-P Oh, take that back: dot.kde.org. *Now* I can't think of any others -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: preset bookmarks
On Tuesday 03 July 2001 02:25 pm, Ivan E. Moore II wrote: > On Tue, Jul 03, 2001 at 02:46:23PM -0700, David Bishop wrote: > > On Tuesday 03 July 2001 01:19 pm, Ivan E. Moore II wrote: > > > ok all you kde junkies...anyone know how I can setup a default bookmark > > > list so that upon installation a user will have a few bookmarks (ie > > > things like www.debian.org/debianplanet/etc...)? > > > > > > Ivan > > > > I'll say the obvious one: kde.themes.org. Of course, my mind just went > > completely blank and I can't think of any others :-P Oh, take that back: > > dot.kde.org. *Now* I can't think of any others > > ok...let me rephrase this. > > I need to know *how* to do this. > > but now that you said this...submit your recommendations as well. :) > > Ivan After I got over the embarrasment, wouldn't this integrate nicely with the code that gets run now the first time someone logs in (to setup themes and stuff)? You can just append a call to copy over some default bookmarks.xml file from /usr/share/doc/konqy/. *shrug* Just don't look to me for the implementation *grin* Oh, and I still can't think of any other sites, well, except sluggy.com. *Everybody* should read sluggy. -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: stable -> testing kde problems
On Wednesday 04 July 2001 14:30, uhlhorsr wrote: > I just upgraded my potato box to testing and am having problems getting kde > set up. I noticed there is no task-kde in testing (correct?). So I manually > picked the kde debs with dselect. I got kdm running fine, but when I try to > login via kdm, the machine hangs for a few seconds and then dumps me back > to kdm. I can however get kdm to lauch blackbox without problems though. > What am I missing/doing wrong? > > FYI: This was inspired by the "upgrade" to a geforce2 mx video card. Any > relation? > > -stephen Once you start blackbox, try running /usr/bin/kde2 by hand from within a terminal. $'s to donut holes that will error out and give you the root cause. Once you get that error message, if you are still lost, post it to the group and we can go from there. HTH, D.A.Bishop P.S. Re: the geforce, no. As long as X starts, you shouldn't be having any driver related issues. At least, not at this point in the process :-)
Re: KDE programming
I would suggest installing task-kde-devel and kdevelop, and go from there. They should get all you need :-) HTH, David On Monday 09 July 2001 20:21, John Batistic wrote: > I have purchased the KDE 2/Qt Programming Bible by Arthur Griffith. > > In trying to work through the first tutorial I find that none of the > programming packages seem to be present in my Debian KDE 2.1.2. > > Naturally, the files in the accompanying CD are not currrent, and I > cannot find debs for the ones I think I need. > > Can some-one advise me on the best course of action? > or am I on the wrong list. > > Thanks > John Batistic. > > --- from NEW ZEALAND - a natural habitat for the PENGUIN --- > --- registered Linux user # 205322 - running Libranet Linux ---
Re: still broken, need help: DCOP problem
Typical troubleshooting for dcop involved shutting everything re: kde down, then blowing away everything kde related in /tmp, mv'ing .kde to .kdeback and recreating it to see if that helps (if not, just mv it right back), doing a dpkg --purge on the kdebase & kdelibs debs and reinstalling them, and, well, if none of that works, then a fill 'dpkg --list | grep -i kde > kdelist' and then doing a quick shell script to iterate through that and removed/purge everything and then using the same list to apt-get with. If *that* doesn't fix it, well then, you're screwed :-) But I'm pretty sure it'll start back up a few steps before that. HTH, D.A.Bishop On Thursday 12 July 2001 07:49 am, James D. Freels wrote: > I didn't get a response to the last query, so I thought I would try again. > > I have a current Debian/Woody system. I recently upgraded to 2.2.0beta1. > Things went OK for a day or two, but then I upgraded to new packages again > on 7/10. Then for some reason I do not understand, kde will not start now. > > The symptom (error messages) are DCOP error messages for essentially every > kde application. It will not even get past the initialization phase. > > What package supplies DCOP? (kdebase ?) perhaps I should try to reinstall > the kde packages? > > Need some guidance here... -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
re: debian and kde2.2
This is just a pre-emptive feature request: Ivan, please include the patches by Dawit Alemayehu wrt proxy and https in your 2.2beta packages. I know sometimes debian packages are base source + patches and I'm hoping this will be one of those times :-) The benefits are that many, many, corporate-type users (like myself) will be able to actually use konq all the time, rather than just most. The patches are available at: http://users.starpower.net/adawit/kde2/patches/proxy.tgz http://users.starpower.net/adawit/kde2/patches/proxy.diff and the instructions are just: Untar/Uncompress (tar -zxvf) the contents of the tgz file package into kdebase/kcontrol/kio and apply the patch from the same directory. The will undoutably be rolled into the 2.2.1 release, but until then. Anyways, just a thought. Thanks for your time! -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: debian and kde2.2
Now following up my own email, in very poor form, it appears that the patches I'm referencing are just for the dialogue, not actually authenticating-proxy-https support, which is partially in cvs. So, pretty much, never mind :-) I have no problem hand editing a file, so long as it works. I'll go back to sleep now.. On Tuesday 17 July 2001 09:00 am, David Bishop wrote: > This is just a pre-emptive feature request: Ivan, please include the > patches by Dawit Alemayehu wrt proxy and https in your 2.2beta packages. I > know sometimes debian packages are base source + patches and I'm hoping > this will be one of those times :-) The benefits are that many, many, > corporate-type users (like myself) will be able to actually use konq all > the time, rather than just most. The patches are available at: > http://users.starpower.net/adawit/kde2/patches/proxy.tgz > http://users.starpower.net/adawit/kde2/patches/proxy.diff > > and the instructions are just: > Untar/Uncompress (tar -zxvf) the contents of the tgz file package into > kdebase/kcontrol/kio and apply the patch from the same directory. > > The will undoutably be rolled into the 2.2.1 release, but until then. > > Anyways, just a thought. Thanks for your time! -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Konqueror not justifying text?
I can confirm this with the latest 2.2beta packages. On Thursday 19 July 2001 01:30 am, Rogério Brito wrote: > Dear all, > > I'd like to ask you to see if Konqueror is rendering my diary > (http://www.ime.usp.br/~rbrito/diary/) as justified text or if > it is only showing up as left-aligned text. > > I'm using a Cascading Style Sheet (CSS) setting the alignment > mode for paragraphs as justified, but it seems to have no > effect with both Konqueror and Opera, but it *does* work with > Internet Explorer, Netscape 4.77 and Mozilla 0.9.2. > > I've already checked obvious things like seeing if Konqueror > and Opera were caching old/wrong versions of my CSS, and if I > got my CSS syntax correct (I validated it). > > Just as background information, I am using TrueType fonts with > all browsers (Verdana, to be more specific, since I find it > one of the most readable fonts). Is there something related to > both Opera and Konqueror being qt applications? I'm using > potato here, with Ivan's latest packages. > > Can anybody help? Am I doing something incorrectly? > > > Thank you very much for any help, Roger... > > P.S.: I tested both Konqueror and Opera with a fake user and got the > same results (non-justifying text). And the weird thing is that I have > a strong impression that both browsers were justifying text some weeks > ago. Am I dreaming? -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Kmail problems
Have you upgraded since? There was a bug there for a couple days where this happened, fixed since. OTOH, you might have found a new one :-) On Friday 20 July 2001 12:54 pm, Cajus Pollmeier wrote: > Hi list. > > Since I upgraded last week (sid/unstable) there's a little problem with > kmail. It doesn't get mails out of any pop3 Mailbox. > Starting kmail on the console results in this - after clicking on the > "fetch mail" icon: > > QObject::connect: No such signal QObject::data(KIO::Job*,const QByteArray&) > QObject::connect: (sender name: 'unnamed') > QObject::connect: (receiver name: 'unnamed') > QObject::connect: No such signal QObject::result(KIO::Job*) > QObject::connect: (sender name: 'unnamed') > QObject::connect: (receiver name: 'unnamed') > > QObject::connect: No such signal QObject::data(KIO::Job*,const QByteArray&) > QObject::connect: (sender name: '~A~A³³~A~A~A~A ~A > ~A¨~A¨~A°~A°~A¸~A¸~AÀ~AÀ~AÈ~AÈ~AÐ~AÐ~AØ~AØ~Aà~Aà~Aè~Aè~Að~Að~Aø~Aø~A') > QObject::connect: (receiver name: 'unnamed') > QObject::connect: No such signal QObject::result(KIO::Job*) > QObject::connect: (sender name: '~A~A³³~A~A~A~A ~A > ~A¨~A¨~A°~A°~A¸~A¸~AÀ~AÀ~AÈ~AÈ~AÐ~AÐ~AØ~AØ~Aà~Aà~Aè~Aè~Að~Að~Aø~Aø~A') > QObject::connect: (receiver name: 'unnamed') > > Is there anything that I can do about that? > > Thanks, > -Cajus -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Kmail problems
On Saturday 21 July 2001 02:15, Cajus Pollmeier wrote: > > Have you upgraded since? There was a bug there for a couple days where > > this > > happened, fixed since. OTOH, you might have found a new one :-) > > Well. I've upgraded just some seconds ago. But it stays at it is. Maybe > I should step back, compiling the cvs every day ;-) > Is the debian version of kde-2.2-beta1 based on cvs? The first version of > it had no problems with kmail... > > -Cajus I'm pretty sure (don't quote me) that the latest sid packages are beta2.2+ a few days of cvs. Since this is reproceable with latest cvs, I would recommend trying [EMAIL PROTECTED], posting a debug-enabled backtrace and terminal output dump, along with how you reproduce this. They are quite nice over there :-) HTH, D.A.Bishop
OT: debian keyring
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Being somewhat new to this stuff, how do I check that the gpg signature on an email matches that of the public key fingerprint registered with debian when you become a developer? I.E., assuming Eray *does* finally make it through the new-dev process, and he continues to gpg-sign his mails like a good dev, how do I make sure it's really him? All kmail says is "signed by unknown key blah". Now, I could goto the website and manually check in the debian developer's database (db.debian.org) but that's painfull, and someone has surely come up with a better way. I'm on enough mailing lists with enough different people posting, that I can't possible check each individual's key by hand. So, please reply with comments, off list if you feel bad about the subject(though traffic's been so low lately.), and help me out. 'Cuz it's *got* to be easier than I'm making it out to be. Thanks, D.A.Bishop -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7XPgpKEJ4huP2XBERAuwLAKC2Zxkg9EcMMqaVpI+pCyEhloimDwCgoq3y bhj5FzIVZQMuAcZ59hmWyQE= =HWNl -END PGP SIGNATURE-
Re: Keys don't work properly in konsole
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 26 July 2001 02:26 am, Felix E. Klee wrote: > Hi, > > on my Potato system with the latest KDE 2.1-installation and the debian > XFree86 4.0.3 packages installed I have trouble with certain key-events > in konsole: even though I selected > xterm (XFree 4.x.x) > as a keyboard setting I can't use the begin or end keys. Is this a known > bug in KDE? Are there any workarounds? > > TIA, > > Felix I've found that I have to play around with the setting of $TERM, the keymaping of konsole, depending on what shell I'm using, and also what OS (bash on solaris works different when I'm telneted to a sun box than it does in linux). However, I've never had a situation that I wasn't able to find the "right" combo... For example, to get all my keys working correctly, I use xterm (xfree 3.x.x), with $TERM=xterm. That gives me color in vim, working backspace *and* delete, and pgup/pgdwn. - -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7YDkr14eKrYdPXKkRAjy2AJ4xalBL2HA9xLVg6VaUjmTjsFumLACfW1eO Sy9ASTNoSwtUKGP9d/uyx8k= =wa12 -END PGP SIGNATURE-
Re: kde 2.2beta
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 26 July 2001 04:08 am, David Dayan-Rosenman wrote: > Hi, > I'd like to upgrade to KDE 2.2beta but I don't quite know how to proceed. > Could anyone help me with an apt line ? or with a quick explanation of CVS > ? Or with a link to nay of the previous ? > > Thanks > > David If you are running unstable, just apt-get upgrade. If not, well, good luck :-) It takes me Pii350 w/768Megs of ram several hours just to compile the kdenetwork module, let along everything else. I would recommend either running unstable if you want the beta, or waiting. Self-compilation is just too painful... Especially if you get 95% of the way through a module and it dies (it is cvs, natch), necessitating starting over after a cvsup. Btw, that's painful experience talking ;-) - -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7YDnP14eKrYdPXKkRAldgAJ9qSJQMonvPf62x39BXf9GEV7IxEQCfZQwh eSZJeHi6X1DskgdhaiI9NNI= =Awt9 -END PGP SIGNATURE-
Re: Single vs double click desktop
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 26 July 2001 05:30 am, c wrote: > The option to select a single or double click > desktop launch method exists when installing > KDE for the first time but where is that > setting located after installation ? > > --markc It took me a couple minutes searching as well, but it's in the control center under peripherals -> mouse. - -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7YDsf14eKrYdPXKkRAli2AJsHTfu2gA5jAzGy8P7cVhu0nzBLdwCgrHTV fmhBaA+KZgxQ0ihCI0Wduq8= =426i -END PGP SIGNATURE-
Re: Keys don't work properly in konsole
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > I've found that I have to play around with the setting of $TERM, the > > keymaping of konsole, depending on what shell I'm using, and also what OS > > (bash on solaris works different when I'm telneted to a sun box than it > > does in linux). However, I've never had a situation that I wasn't able > > to find the "right" combo... For example, to get all my keys working > > correctly, I use xterm (xfree 3.x.x), with $TERM=xterm. That gives me > > color in vim, working backspace *and* delete, and pgup/pgdwn. > > Hello, > > I too was following this link with great interest. Due to the same > reasons. Some time ago (months now) I lost the use of the HOME & END keys > while within X. I, as usual, didn't get too excited about it due to running > UNSTABLE and figuring it would be dealt with in time. Then when the > question was finally asked, my interest was peeked. > > David, where are you implimenting this "...$TERM=xterm..." command at? I > tried it from within a term, a console, via my .bash_profile, and so far > haven't had any luck at all. It's not a massively urgent thing, but I > really would like the use of those keys back. :--) I'm sorta a console > junkie so I have a number of xterms open and running while within X and > it's a bit of a pain to not have the functional keys when coding, etc. > I'm just setting my $TERM variable to xterm. If using bash, try "export TERM=xterm". (notice no $). I *believe* (as in, don't quote me) that is set automatically when you open a new console window with the default being the "xterm (xfree 3.x.x) setting. If you switched that to "linux console", then your $TERM would be eq to linux when opening a new konsole. Notice no switching will affect your existing konsole sessions, hence playing around with it manually (i.e., the export thing). So, to summarize: open konsole, check your $TERM variable (echo $TERM) change your keyboard settings to xterm 3.x.x export TERM=xterm try various keys if it didn't work, change to xterm 4.x.x keep $TERM the same try again if it didn't work, change to linux console export TERM=linux try again if it didn't work, change to vt100 export TERM=vt100 rinse, repeat. Hope that helps... That's what I had to do to get mine working right, but I'm positive the "perfect combo" depends on what keyboard you are using, Xfree setttings, and various other factors, so that the same combo won't work for all people. - -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7YHIT14eKrYdPXKkRAjQtAJ9UlN3by9+ERR73TRnzl6dLFx4hzgCgjbBI GDLBvK0SJ4ZDPLayJVAdD70= =zdUf -END PGP SIGNATURE-
Re: broken ssl support in kdelibs3-crypto (2.2.0-0beta1-7)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > are you using a proxy? I know there are still some bits that have been > fixed since the version your running... > > Ivan Does this mean that there is a version of the kdelibs (not yet packaged) that makes https work with authentication proxies? I'm running latest sid and it still fails for me. However, plain http works like gangbusters! Wahoo! ;-) - -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7ZsrQ14eKrYdPXKkRAnnPAKCE3VTf7s8fDSiAG/dWNihPUBuqBwCghGsQ XFhZv5WKSDX4gJnsz6hYrrE= =sZfi -END PGP SIGNATURE-
Re: broken ssl support in kdelibs3-crypto (2.2.0-0beta1-7)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > So, for the moment at least, I've just turned off TLS support and > everything works ok. Didn't help my "not-through-an-authenticating-proxy" problem. Oh, well. - -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7ZvBb14eKrYdPXKkRAi+WAJ4mO91bW2Uu5gfmrIPhlpzTJwlh3wCfUxQ0 0p/J/r7eznlWZUdjE4Z/ZCM= =Q5jZ -END PGP SIGNATURE-
Re: Compile small KDE application
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 you need not only the libs, but the dev stuff. Easiest thing to do is just apt-get install task-kde-devel. That will give you all you need. On Friday 03 August 2001 08:37 am, Emil Wilmanski wrote: > Hello > > I'm using Debian with KDE v.2.1.1 and i try compile some programs. In > fiew ones I have problem to do it: > > checking for KDE... libraries /usr/local/kde/lib, > headers /usr/local/kde/include > checking for extra includes... no > checking for extra libs... no > checking for KDE headers installed... configure: error: your system is > not able to compile a small KDE application! > Check, if you installed the KDE header files correctly. > > I don't idea to how make it. I tryed install all KDE libs from deb, next > I instaled libs from src and it not worked to. > > Have any some ideas about how to do it?? > > > Emil W. - -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7atdZ14eKrYdPXKkRAp3YAKCeOi3RLn7U7XJOV4QSXr9jxDoMVwCghRP7 XAtmHqpiZfs7f+GgwaCE9M4= =8FPS -END PGP SIGNATURE-
Re: Compile small KDE application
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 03 August 2001 09:34 am, Kolja Brix wrote: > Hello! > > Am Freitag, 3. August 2001 18:54 schrieb David Bishop: > > you need not only the libs, but the dev stuff. Easiest thing to do is > > just apt-get install task-kde-devel. That will give you all you need. > > I tried this on my Debian potato using deselect. Result: > > task-kde-devel not installed ; install (was: install). Optional > task-kde-devel recommends kdesdk > kdesdk does not appear to be available > > Where can I get this package? > > Thank you! Probably depends on what version of debian you're running. If you're running sid, try installing kde-devel (no task) instead. And yes, that was my mistake :-) For any other version, I dunno. All I have is sid ;-) (on five boxes and counting.). I would check incoming.debian.org, and see if what you're missing is there. - -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7aubV14eKrYdPXKkRAmLCAJ9pWuR9nChjzf14lu/zb4v9L/vnRQCcClVo T+M2qpNMXJw7XxKdUyaIDno= =nDfs -END PGP SIGNATURE-
Re: KPilot and KOrganizer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 06 August 2001 05:43 am, David Morgan wrote: > Has anyone succeded in getting the Debian Potato packages of KPilot and > KOrganizer to work together, i.e. to sync from KOrganizer to and from the > Pilot? > > I've looked on this list and on the KDE PIM list and can find several > people reporting that it doesn't work, but no real solution. I have set the > appropriate conduits up as "active" and have pointed them to my KOrganizer > vcs file. > > Not sure what to try next. According to the kpilot-list, they recently (as in *just*) fixed a bug where that wouldn't work. Unfortunetly, the "solution" is upgrade-to-latest-cvs, or wait-for-ivan-to-package-latest-cvs. Sorry, and hth. - -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7btDR14eKrYdPXKkRAje/AJ0Z45gd0om1p6uuWJMq5OrjIUJx1ACgiFU+ Fadt6jf6wBGbqxubwD+c/qA= =4+4t -END PGP SIGNATURE-
Re: How install KDE with Woody/testing? (2)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 06 August 2001 20:34, tluxt wrote: > I tried something like this - I did the dist-upgrade, but didnt use -fuy. > I then ran dselect and let it install sone packages it wanted to. > I then ran tasksel, selecting to install: > 1. X > 2. GUI - (a combination of GNOME & KDE) At this stage, just install X, you can install kde "manually" later, not in dselect. > > but, something(s) must not have worked properly, because : > 1. I never got the GUI based X config screen (to config mouse, >vid card, monitor, refresh rates). I did get some text mode questions >about these items. I answered them, and it accepted the answers. normall. Debian (i don't think) has a gui X configurator. Maybe progeny does. > 2. Neither startx nor start-kde work - they both complain about being >unable to open an X display, I think. The last few lines of this output would have been great :-) > 3. When I reboot, the login comes up in text mode, not GUI mode. One of >the last lines from the boot messages is about starting some Gnome > thing, but no mention is make of KDE in those messages. Probably gdm. You say at the end this is taken care of, so I won't worry about it. > Questions: > 1. Is there a program run by the package installer that will come up to >help me configure X? If yes: Do you know the program's name? >If no, what program should I run to configure X? dpkg-reconfigure -p=low xserver-xfree86 >(I suspect the answer above is yes, so then:) Is that configure program >a GUI based config program? What is it's name? XF86Setup? >I searched for XF86Setup - it isn't on my system. But, xf86config is. >I used xf86config to generate a config file. You can also run xf86config, but it is also not gui based. >Is that the best way being used to configure X? Should that be run >automatically at some point by the package installer, or am >I supposed to run it on my own? It should have run automatically, in fact, it sounds like it did (when you answered those few questions in text mode). My best guess is that your debconf "ask me no questions below this priority level" level is set too high, and it skipped something that it needed to ask directly. Oh, well. > 2. At some point after doing the apt-get dist-upgrade I got a question > about which interface type to use for package configuration: >slang, dialog, text, (& 2 others, I think). I tried slang one time, >but got errors about slang & perl during package installation, IIRC. > >Which interface type should be chosen at this question? (I think >slang is definitely out, but I want to ensure that the best X config >program runs, and I suspect that that is the GUI based config program, >not just some text questions. The GUI based config program at least >allows immediate verification that the mouse is working, and that a >GUI screen is capable of operating with the video hw.) None of those are gui, iirc. The slang was complaining about missing libterm-stool-something. I would go with dialog. it works fine, and is a bit more than just a command line in black and white. > 3. I have NOT, at any time, put the KDE deb line into sources.list. >Is that the correct way to do this procedure? yes. >*1 Woody, at this time, presumably in practicality means testing, >since "woody" doesn't really exist yet (there are just >packages in "testing", "woody" won't exist until those packages, and > other stuff are released, some months from now)) Woody == testing. one and the same :-) > > If you're on a > > 56k line (like I am), be prepared for a long wait; it took about 20 > > hours of downloading for me to get a fairly complete setup with > > KDE2.1.1 (the latest at the time) and the Debian GNOME packages. > > 4. Is there some way to avoid having to DL the Gnome packages? (If they >aren't necessary, I'd prefer to not dl them over a 56K modem.) I >didn't see a "KDE only" tasksel option. (Should I use dselect, >not tasksel?) Is there some way to get "KDE only" to appear >as a tasksel option? Yes. One install just select X, not "gui". Then when you're done, run 'apt-get install task-kde'. That will drag down all kde stuff, no gnome. On my box at work, I have no gnome code at all. And gtk only for the gimp :-) > 5. How do I ensure I am using debconf, not debconf-tiny? >Where can I find out more about debconf? I searched for it under >documentation on the Debian website, but there was no info there. >Did I miss something? Do I have to read the source? Or, basically - >in a sentence or two, what should I know about debconf? apt-get install debconf. If it's already install, it comes back saying so. Otherwise, it uninstalles debconf-tiny, and updates to debconf. > One problem I seem to be having is getting xf86config to use a SVGA > ability, not just a 640x480 vga siz
Re: help with korganizer-second request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All the ? icon means is that it doesn't have it's own icon. I'm not sure how to fix that, but it isn't affecting you :-) I just tried, and while I don't think the sound played (I'm also listening to Radiohead via xmms-arts, so I can't say for certain ;-), I definetly got the pop-up "YOU HAVE A MEETING" window. As I seem to be the third person confiming this "works for me", I would suggest looking into a dpkg --purge of the korganizer package, rm'ing your config file in .kde/share/config, and reinstalling it. If that still doesn't work. Dunno :-) HTH, D.A.Bishop On Friday 10 August 2001 08:01 am, James D. Freels wrote: > I really need the notification feature to remind me of meetings. > > The right click on the Korgainzer alarm monitor reveals a check by > "alarms enabled". However, just above that there is an "AlarmDaemon" > button that has a question-mark icon. The entire button is darkened as > if it may not be functional? > > Perhaps I am missing a package? > > On Friday 10 August 2001 10:32 am, David Morgan wrote: > > I use KOrganizer as a diary and to-do list, but not really the > > notification feature. > > > > Do you have the KOrganiser Alarm Monitor running in the panel (down > > by the Klipper mini-icon on mine)? Right clicking on this gives a > > menu with the option to enable alarms. If that is not there then the > > alarm daemon may not be running. > > > > On Friday 10 August 2001 1:51 pm, James D. Freels wrote: > > > Anyone else even use korganizer at all ? > > > > > > On Thursday 09 August 2001 01:38 pm, James D. Freels wrote: > > > > Perhaps, this is not the correct forum, but I am definitely a > > > > debian and kde user. > > > > > > > > I have been trying korganizer. Everything appears to be working > > > > except the notification feature. When an appointment hits, there > > > > is not e-mail, no sounds played, no beep, no pop-up window. > > > > Nothing. > > > > > > > > Does anyone know what I might be missing here? - -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7dAu+14eKrYdPXKkRAjHQAKCd8GNaz5rhYIg5KgXDPYP1bQh1qwCeOgKx jqtwnen4cQXhUk4VGlieNXk= =ibqy -END PGP SIGNATURE-
Re: SSL not working with KDE 2.2-final
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 17 August 2001 12:33 am, Mike Williams wrote: > Using konqueror under KDE 2.2, I can no longer access HTTPS sites. For > instance, when I attempt to access https://sourceforge.net the following > error is reported: > > kio (KRun): ERROR: 0x83aa200 ERROR 23 Could not connect to host > > I'm behind a firewall, and have HTTP/HTTPS/FTP proxies set (these work with > Netscape, and worked with konqueror-2.1.1). Various version numbers: > > ii kdebase2.2.0-final-1 KDE core applications > ii kdebase-crypto 2.2.0-final-1 KDE core applications (Crypto modules) > ii kdelibs3 2.2.0-final-1 KDE core libraries (runtime files) > ii kdelibs3-crypt 2.2.0-final-1 KDE core libraries (Crypto Modules) > ii libssl0.9.60.9.6b-1 SSL shared libraries > > Anyone else having similar problems? Yes, this is a known issue with proxies (particularly authenticating proxies) and konq. Dawit is working on it, as far as I know, that's the official word. (I've reported this via bugs.kde.org, do a search for "authenticating proxies konq" and add new info if you have it) HTH. - -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7fTNh14eKrYdPXKkRAsNTAJ40DO/HEEQLXjqhEba5wjdHec8l5gCff+83 7vPMCn2H/4x3Pfgmf2/MpCQ= =YJuC -END PGP SIGNATURE-
Re: Printing with KDE 2.2
On Wednesday 05 September 2001 08:52 am, Gilger.John wrote: > G'Morning Wondrous Wizards, > > I recently upgraded to Sid and KDE 2.2. My printer, which worked > perfectly with Woody and KDE 2.1 doesn't want to play with Sid and KDE > 2.2. I used Apsfilter to setup my /etc/printcap file (if that has > anything to do with this) > > TIA > > John Twould be nice if you could expound a bit on what /exactly/ the problem is (error messages, whatnot), along with what printing sub-system you use (lpr vs. cups vs. whatever). Oh, and what printer you use would be helpful as well :-) -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: audiocd ioslave
On Wednesday 05 September 2001 10:40 am, Jonathan Riddell wrote: > Horrors, the best part of upgrading kde 2.2 doesn't seem to have > materialised, there isn't the audiocd: ioslave installed. > > Is there a nice easy apt-get style or even hard and difficult way of > installing it? > > Jonathan Riddell It really, truly, should have been installed. Are you having problems accessing it (there are some common gotchas), or did you somehow manually verify that there is no such ioslave on your computer? I don't think it's the same problems, but as an aside, you'll want to install konq-plugins. It's a collection of really cool konq stuff that isn't (I don't think) installed by default. HTH, D.A.Bishop
Re: Printing with KDE 2.2
> Would it be better to change from lpr to lnprg or cups? Yes :-) Switching to cups is painless, and easy. If this is a home pc, apt-get install cupsys cupsys-client kups, configure the server by going to localhost:631, and configure kde to use the localhost cups server. I use it at both work (with a color laser) and home (with an Epson 777 via usb), and it's just great! But I've hated the lpr/lpd/printcap "solution" since day one... If you are having problems getting cups working, I'll be happy to help you walk through the install process. -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Printing with KDE 2.2
On Wednesday 05 September 2001 01:15 pm, Jens Benecke wrote: > On Wed, Sep 05, 2001 at 01:14:56PM -0700, David Bishop wrote: > > > Would it be better to change from lpr to lnprg or cups? > > > > Yes :-) Switching to cups is painless, and easy. If this is a home pc, > > apt-get install cupsys cupsys-client kups, configure the server by going > > to localhost:631, and configure kde to use the localhost cups server. I > > use it at both work (with a color laser) and home (with an Epson 777 via > > usb), and it's just great! But I've hated the lpr/lpd/printcap > > "solution" since day one... > > The coolest thing about CUPS is that once you have _one_ CUPS server in > your network and you configure it as master, it will automatically know > and publish _every_ printer in your network (as long as they are public). > Just activate the browsing feature in cups.conf. > > No local drivers, no hassle, no installing anything. That's why I prefaced with "if this is a home pc". If it's on a coporate lan, then I would have walked him through the whole networking thang. :) And yes, it's very, very, cool (says someone who spent many frustrating hours trying to get remote lpd/r working, g). David
Re: audiocd ioslave
On Wednesday 05 September 2001 02:01 pm, Jonathan Riddell wrote: > > > Horrors, the best part of upgrading kde 2.2 doesn't seem to have > > > materialised, there isn't the audiocd: ioslave installed. > > > > I have the same problem : In konqueror In get "file or directory / > > doesn't exist" (in french) when I try audiocd:/ > > > > Could you help me ? > > Ah hah, it was the kdebase-audilibs package. Fantastic. > > I got that message when there wasn't a CD in the drive. Maybe check that > it is an audio cd and that /dev/cdrom is pointing to your cd-drive. > > Jonathan Riddell The other common causes are that you don't have rw access to the device (ls -l /dev/hd[whatever]), or that you are using scsi emulation, and you don't have rw access to the sg device (usually /dev/sg0 (i think)). -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Printing with KDE 2.2
Well, after searching around, I can't find anything regarding running
external scripts with cups. The only *workaround* I can find would be to
somehow make a "filter" that every job passes though, which runs your script.
I would be willing to bet that it's just an oversight on my part, and a quick
post to the cups newsgroups
(http://www.cups.org/newsgroups.php?Gcups.general+H+VR) would get you an
answer. However, I also found built-in job accounting (job-billing,
according to ipp), that would probably fit the bill, if you invested a bit of
time rewritting your scripts. If you combine job-billing with user
authentication (both native in cups 1.1), you should be set.
HTH,
D.A.Bishop
> Now while we're at it, could you tell me how to integrate custom scripts in
> the CUPS system? What I want is this:
>
> - CUPS receives a printing job (always Postscript)
> - CUPS counts pages (optional)
> - CUPS calls an external script like this
> /accounter.pl $USER $JOBFILE
> - IF this script exits with 0, CUPS continues, otherwise the job is
> discarded
> - IF the print was successful, CUPS calls another script
> /accounter_success.pl $USER $JOBFILE
>
>
> Alternatively: don't call scripts, but open a TCP connection to a specified
> port and 'ask' (via custom commands) a server script for permission to
> print. The chat would look like this (this is actually what the perl script
>
> does, which is currently running with lprng):
> >>> input
>
> <<< return
>
> Connected to Xxx.xxx.xxx.xx.
> Escape character is ^].
>
> >>> auth 3ac141b58e28162dedf29f754045c2cf # or something
>
> <<< auth ok
>
> >>> check $USER $NUMBER # may $USER print $NUMBER pages?
>
> <<< [ok|fail $ERRMSG]
>
> when ok, start the job (optionally keep the connection),
> else quit + mail $ERRMSG to $USER ("your quota is empty" etc).
>
> if printing succeeded:
> >>> deduct $USER $PAGES
>
> <<< [ok|fail $ERRMSG]
>
> >>> exit
>
> mail $ERRMSG to admin if failed.
Re: Trying to circle in on bug, assistance needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 21 September 2001 05:58 am, Volker Schlecht wrote: > A few weeks ago, I reported bug #108698 against konqueror, which has > been tagged unreproducible by Ivan. I have since waited for 2.2.1 to > be released, hoping that they would silently fix it. > > Apparently they didn't, though - so since my system seems to be the > only one where the problem occurs, I decided to try and find the > problem myself, which is as follows: > > HTML preview in general seems to be broken. When I have it enabled and > look at a directory containing a couple of HTML files, CPU load goes > up to 100% for a 1-2 minutes, and X completely freezes. For brief > period each two minutes or so, X wakes up again, giving me the chance > to press the back button to get out of the directory in question > again. If I don't X will freeze again for 1-2 Minutes. Running it for > a couple of hours overnight will finally display all the HTML previews. > > The bug report only mentions viewing the contents of .tar.gz's, > however currently, using konqueror 2.2.1 from unstable (on an > otherwise woody system) that happens with normal directories also. > > I have checked bugs.kde.org to see if such a problem had been already > reported, but I couldn't find any mention of it. > > Does anyone here have the same problem, or any suggestions by what it > could be caused? Just tested on directory with 8 html files, no problem. Took a couple seconds to generate previews, but nothing serious, and immediately cpu usage dropped back to normal. Just tried with a .tar.gz file as well, worked even faster than I expected. This is on a pii 350, nothing special (oh, and I'm straight sid). Sorry :-) - -- "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7q1b314eKrYdPXKkRAlU8AKCQqsJ7wkKtRDzkKXA7cv8pgcam4wCeMW9/ 1AJQXk9h+HUMZ9kg2X9bxN0= =sgG2 -END PGP SIGNATURE-
Re: 2.2.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 21 September 2001 08:53 am, Jens Benecke wrote: > On Thu, Sep 20, 2001 at 06:39:01PM -0400, David Kuntz wrote: > > I'm in - anyone have a paypal account we can use, maybe? > > Unfortunately, I don't. Neither do I have a credit card, =;) > > Last time I did this (also a reward) most participants were in Germany and > they just did a money transfer via bank, which wasn't any trouble. I may > not have thought far enough ... maybe I should actually open a Paypal > account to carry this through. > > Suggestions? Well, at this point it becomes a trust issue. I've hung around this list for a long time, and I have an already set-up paypal account that I would be willing to use for this, but not that many of you know me. If it's acceptable to the list, I will collect the donations, and then either wire the money to Ivan (where does he live??), wire it to somebody near him to buy the reward, or buy it myself and ship it. But it requires you guys sending money to my paypal account :-) My personal information: David A. Bishop 9014 Woodside Ct. Boise, ID 83704 home email: [EMAIL PROTECTED] work email: [EMAIL PROTECTED] paypal account: [EMAIL PROTECTED] or [EMAIL PROTECTED] Home phone: (208)376-5902 Work phone: (208)363-3648 Cell phone: (208) 283-0909 If someone else on the list want's to verify that information, that's fine. If there is an alternative method of collecting the money, that's great also. - -- D.A.Bishop -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7q3UPKEJ4huP2XBERAp4VAKCyWS2gXSt3Ie0yc8Vpfg+KNbY/qwCgxYTp q5vnqmsNhVQX5IrwRUBTTdQ= =cn7L -END PGP SIGNATURE-
Re: 2.2.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 21 September 2001 09:36 am, Jens Benecke wrote: > On Fri, Sep 21, 2001 at 10:12:46AM -0700, David Bishop wrote: > > On Friday 21 September 2001 08:53 am, Jens Benecke wrote: > > > On Thu, Sep 20, 2001 at 06:39:01PM -0400, David Kuntz wrote: > > > > I'm in - anyone have a paypal account we can use, maybe? > > > > > > Unfortunately, I don't. Neither do I have a credit card, =;) Last time > > > I did this (also a reward) most participants were in Germany and they > > > just did a money transfer via bank, which wasn't any trouble. I may > > > not have thought far enough ... maybe I should actually open a Paypal > > > account to carry this through. Suggestions? > > > > Well, at this point it becomes a trust issue. I've hung around this list > > Almost everything is a trust issue. Or did you audit the binaries Ivan > provided byte by byte? ;) Of course! Doesn't everybody? *grin* > > for a long time, and I have an already set-up paypal account that I would > > be willing to use for this, but not that many of you know me. If it's > > acceptable to the list, I will collect the donations, and then either > > wire the money to Ivan (where does he live??), wire it to somebody near > > http://www.kde.org/people/ivan.html :) Okay, I'm in Idaho, we're really close to Colorado. > > him to buy the reward, or buy it myself and ship it. But it requires you > > guys sending money to my paypal account :-) > > I will gladly let you take over if you can arrange it more easily. And I > don't think you will run away with the money ;) Well, everyone who chimed in with the me too!, send whatever you can via paypal to [EMAIL PROTECTED], I'll total it up and we can hash out what to get him. If you don't have a paypal account, you can send a check that I'll cover (i.e., somebody said to do this before he got back, so if you send a check tell me, I'll put that amount of money into paypal and just cash the check when it get's here). Sound agreeable? - -- D.A.Bishop -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7q3xAKEJ4huP2XBERAm+ZAKCvypsfUzCj70TF2hqVGjM0Fn2uRQCfdHfm nGWsRps/kxu00+p+fUSZ9gY= =MsOj -END PGP SIGNATURE-
