Re: Upgraded to woody and printing from KDE stopped
On Fri, Mar 29, 2002 at 22:30, Gruetzner wrote: I then manually editted /etc/printcap, changing the semi-colon ( ; ) after hl1250 to a colon ( : ). That fixed one error message. The error message now reads: No, this was not good. I have this line in my printcap file: lp|cdj970;r=600x600;q=medium;c=full;p=a4;m=auto:\ Without knowing so much about the way apsfilter works, I guess cdj970;r=600x600;q=medium;c=full;p=a4;m=auto are parameters for apsfilter. So, you should not play around with these. Try printing a testpage with your old printcap (; instead of :). Yes, you were right. This problem is not fixed in the current KDE packages and you should file a bug. The parsing of the printer name from the printcap file does not work properly. It should stop at the first pipe '|' as pipes separate alternative names for the same printer. However, it does not. A quick workaround is to login as root and to set in the KDE Control Center under System/printer the correct printer name. Then printing should work for you even with KDE. :-) Bye, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kde packages broken?
I believe a better audience for you question is the debian-kde list. I have reformatet your message for better readability and sent it there. [Juha Jäykkä] What is wrong with the various woody kde packages (knode, kdebase3, keystone, kdebase3-bin...), since almost every time I upgrade my woodys some of them fail. Usually because dpkg tries to unpack a file from package A over a file which also exists in package B? I have noticed this many times upgrading from potato to woody with various packages but kde packages are the only ones I have seen doing this in a woody - woody upgrade! Usually this is fixed by removing the other for a while and then reinstalling it later or simply saying apt-get -f install A B - luckily when kdebase3 and kdebase3-bin were borken, this helped since removing either... Now keystone and knode are not fixable by this, though. I would hate to file bug reports against woody packages at this time - especially since this seems to happen again and again with kde packages. Is there some reason why it is only kde? -- --- | Juha Jäykkä, [EMAIL PROTECTED]| | home: http://www.utu.fi/~juolja/ | --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bastian Gläßer/PD/Kreditwerk ist außer Haus.
Ich werde ab 26.03.2002 nicht im Büro sein. Ich kehre zurück am 23.12.2024. Ich werde Ihre Nachricht überhaupt nicht mehr beantworten. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Out of Office AutoReply: KDE 3.0rc3 Debs???
On Sat, 30 Mar 2002 05:15, Chris Cheney wrote: When you are away from the office DO NOT SET YOUR MAILER TO RESPOND TO LIST TRAFFIC!!! Best thing to do for those cases is to write a little perl script to make a direct connection to port 25 of their mail server and send the message to them with theirown email address as the from field in the envelope and the header. Then you won't get a vacation response from telling them their vacation program sucks. -- If you send email to me or to a mailing list that I use which has 4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.0rc3 Debs???
[Chris Cheney] KDE 3.0 final has been tagged and I am working on finishing up the debs for it currently. It will probably take a few more days. Do you plan to include KDE 3.0 in Woody instead of KDE 2.2.2? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgraded to woody and printing from KDE stopped
On Friday 29 March 2002 23:36, Steffen Evers wrote: On Fri, Mar 29, 2002 at 22:30, Gruetzner wrote: I then manually editted /etc/printcap, changing the semi-colon ( ; ) after hl1250 to a colon ( : ). That fixed one error message. The error message now reads: No, this was not good. I have this line in my printcap file: lp|cdj970;r=600x600;q=medium;c=full;p=a4;m=auto:\ Without knowing so much about the way apsfilter works, I guess cdj970;r=600x600;q=medium;c=full;p=a4;m=auto are parameters for apsfilter. So, you should not play around with these. Try printing a testpage with your old printcap (; instead of :). A catastrophe error message popped up: bad printer name. Yes, you were right. This problem is not fixed in the current KDE packages and you should file a bug. The parsing of the printer name from the printcap file does not work properly. It should stop at the first pipe '|' as pipes separate alternative names for the same printer. However, it does not. That is likely part of the problem. I need to research *how* to file a bug report--and with whom? Apsfilter? Debian-kde? Someone else? A quick workaround is to login as root and to set in the KDE Control Center under System/printer the correct printer name. Then printing should work for you even with KDE. :-) Well, I did that. It totally rewrote printcap to remove the filters, which was fine for simple text documents, but leaves a lot to be desired elsewhere! I went back and SETUP the apsfilter, and changed the first line from aps1|hl1250;r=600x600;q=medium;c=full;p=letter;m=auto:\ to aps1|hl1250:r=600x600;q=medium;c=full;p=letter;m=auto:\ This produced the bad printer name catastrophe. So, I changed it to aps1:r=600x600;q=medium;c=full;p=letter;m=auto:\ ...and it printed (from KWord)--except the first two lines were missing (outside the margins?) and there was only one typeface (~arial). However, fontsize (10pt, 12pt) and bolding appeared to work fine! Thanks again for the help. Eventually migrating to CUPS may help, but that appears to be a future try. Have a great day! James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.0rc3 Debs???
On Sat, Mar 30, 2002 at 01:13:59PM +0100, Petter Reinholdtsen wrote: [Chris Cheney] KDE 3.0 final has been tagged and I am working on finishing up the debs for it currently. It will probably take a few more days. Do you plan to include KDE 3.0 in Woody instead of KDE 2.2.2? No. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
making a file with root permissions
Greetings Bill: So sorry you spent so much time fooling with the file. A quick call here could have saved you some time, though I do admit to being gone a lot of yesterday! If you still have the file on your drive, probably in /home/bill/YourFileName, then you can simply move it with the 'mv' command as root! Also note that you can do a dir that is quite powerful: 'ls -al'. 'ls' by it self will show files and directories that are not hidden. By adding the '-al' to the 'ls' command, you can see the whole directory, hidden files, who *owns* the file, what *group* the file belongs to, and *who* can *read* the file! This will also show if it can be *executed*! Very powerful. The next is way to do something special is to vi! open a Konsole, switch to superuser: 'su -', and do note that space and hiphen, that makes you root with all of roots *extra stuff (tm)* :) Now open a vi with the command 'vi'. You now have the most powerful and fastest editor at your disposal. This is a command driven editor, and it doesn't come with a newbieuserfriendly gui. . . To add stuff to your file, first press 'i' for (i)nsert, type your text. Now get out of insert mode with the 'esc' key. Now save your document by pressing and holding the shift key, and pressing the letters 'zz'. The whole thing would look like this: vi AFunnyLetterToJaye.txt(this creates the name and opens the editor i starts the insert mode esc back to editor command mode Shift zz saves the precious work and exits the editor. Emacs is also workable and useable I THINK as superuser. I hear the echo like voice say: Hey Jaye, I DID save that file that I created as user bill, what else do I need to do after I move it? Very good question Bill! I would change the owner group flags to root. That is really simple: chown (CHange OWNer) is the command to do this. we would issue the command: chown root.root YourFileName (enter) :) Note the first root is the owner, followed by the period and no spaces, the second root is the group. What the hell are groups for? Bill, you are delighting me with these great questions! The owner and groups are important for keeping a tight lock on security of your computer. I don't want the world to have access to my sound system, so I changed all my group for sound to 'audio', then I only added two people to that group, root and jaye. Now if *anyone* else were to log onto my box, they can't touch my sound card, and those programs that need my sound. Not much security there, but that is only at first glance. If a program has a security vulnerability that could possibly give root permissions on a buffer overflow to my sound demon, then I COULD have had a problem. But my group effort took care of the problem before it could ever be exploited. Another very good idea is the 'disk' group. Bill needs to save stuff to the hard drive, floppy, cdburner etc. However, joeBlow doesn't need this right. Joeblow might be just simply looking at the webpage my computer provides, but that is purely a readonly issue. So, bill could hack his way on the box, yet still not have the right to save a simple text file on the drives! That is the *root* of this simple security measure, and the root of much anger by newbies that don't read manuals. There are several basic, and simple commands I think any user should know. They are not specifically related to just linux, since I have the same feeling when I am in a DOS command mode. Things like dir and 'ls' are basics. 'md' and 'mkdir', 'del' 'rm'. Note however that linux provides many many extra functional arguements for each of the commands. 'man ls' will give you a very good idea of what I mean. Now, reading a (man)ual page is ok, but here is another trick you have. Open up konqueror web browser. Now, in the url field, enter: #ls (click go). Your browser has the ability to uncompress that manual page, then display it on your web browser, *and* add hyperlinks to related pages! Some times I like using it with the scroll bar, other times, a simple console (Konsole) is what I prefer. I have a good book here, if you would like to borrow it. It applies to all linux, but is clearly slanted to the redhat and mandrake flavors. It applies generically, and I think it helps take out the unknown elements. End of essay :) tatah Bill, 73 -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
making a file with root permissions
Oops. (note red face) Please disregard my last post :) -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
KDE 3
I compiled KDE3.0rc3 for my system and I am wondering, how do I boot into it? I am currently using Libranet linux (based on debian), and when I start up, I get a gnome login manager where I can choose which window manager I want to boot into, but I can't figure out how to add kde 3 to my choices. Any ideas? Thanks in advance. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Unidentified subject!
unsubscribe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
gnupg kmail signing message
Greetings: I have configured gnupg, then built and published my keys to the mit server. Next I configured kmail to use gpg. I can now quickly encrypt messages, however, I can not sign them. The pad lock is usable, but the ksign icon is grayed out. What other step is needed to actually sign mail with kmail? tia -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgraded to woody and printing from KDE stopped
On Sat, Mar 30, 2002 at 09:51, Gruetzner wrote: That is likely part of the problem. I need to research *how* to file a bug report--and with whom? Apsfilter? Debian-kde? Someone else? Install package bug or better reportbug. Then you just type 'reportbug PACKAGENAME'. Make sure that your EMAIL variable is set correctly before that (with bash: 'export EMAIL=Your Name [EMAIL PROTECTED]' put this in your .bashrc) Finding the correct package name could be tricky sometimes. In your case, is there something like kprint? I do not know ... A quick workaround is to login as root and to set in the KDE Control Center under System/printer the correct printer name. Then printing should work for you even with KDE. :-) Some of the things I have told you were wrong. I have checked all of it again and here is my solution: Reinstall apsfilter by calling apt-get --purge remove apsfilter apt-get install apsfilter apsfilterconfig lpc reread DO NOT edit the printcap file manually!!! Check if regular printing works with lpr PSFILE or a2ps ASCII-FILE. Ok, this should work now. Then in KDE (logged in as the regular user) go to ControlCenter-System-Printing and set the print system (at bottom) to UNIX-LPD-print-system. Now, printing for that user should work even from KDE. Test it by printing a text file from Konqueror. This worked for me and now my printing system is set up properly the first time. :-) Hope you can say the same afterwards. Bye, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: gnupg kmail signing message
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 30 March 2002 01:00 pm, you wrote: Am Samstag, 30. März 2002 21:09 schrieb Jaye Inabnit ke6sls: Greetings: I have configured gnupg, then built and published my keys to the mit server. Next I configured kmail to use gpg. I can now quickly encrypt messages, however, I can not sign them. The pad lock is usable, but the ksign icon is grayed out. What other step is needed to actually sign mail with kmail? You have to specify the gpg user identity. In KMail from KDE2.2.2 this is a field for every KMail identity profile (before it was one for all profiles). HS That was exactly what I needed Hendrik. Thank you so much for the kind reply. I can now encrypt and sign messages now. tatah - -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8pivEZHBxKsta6kMRAvGjAJ4wpHYL9dMJuzISq//63sU8YpLkXACeJI5m iw4diqJ4AVuK2K0gd5ogpMA= =LPkE -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3
On Saturday 30 Mar 2002 7:42 pm, TB wrote: I compiled KDE3.0rc3 for my system and I am wondering, how do I boot into it? I am currently using Libranet linux (based on debian), and when I start up, I get a gnome login manager where I can choose which window manager I want to boot into, but I can't figure out how to add kde 3 to my choices. Any ideas? Assuming you built kdm and had it installed into /usr/local/kde (the default) then add a line into /etc/inittab kde:5:respawn:/usr/local/kde/bin/kdm You will also need to setup a .xsession file in your home directory with #!/bin/sh # setup for kde development export QTDIR=/usr/src/kde/qt-copy export KDEDIR=/usr/local/kde #Set up library path export LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib export PATH=~/bin:$QTDIR/bin:$KDEDIR/bin:$PATH export MANPATH=$QTDIR/man:$MANPATH exec startkde -- Alan Chandler [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3
On Saturday 30 Mar 2002 9:13 pm, Alan Chandler wrote: On Saturday 30 Mar 2002 7:42 pm, TB wrote: I compiled KDE3.0rc3 for my system and I am wondering, how do I boot into it? I am currently using Libranet linux (based on debian), and when I start up, I get a gnome login manager where I can choose which window manager I want to boot into, but I can't figure out how to add kde 3 to my choices. Any ideas? Assuming you built kdm and had it installed into /usr/local/kde (the default) then add a line into /etc/inittab kde:5:respawn:/usr/local/kde/bin/kdm I forgot you also need to set the default run-level to 5 in /etc/inittab id:5:initdefault: is the line you need to set. -- Alan Chandler [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
