kdm and afs fails
Hi! I'm currently experimenting with an AFS enabled Client with KDE. My home directory is placed on an AFS drive, so I need to get the tokens while logging in. To establish a proper login via ssh, I modified the pam.d/ssh config like this: 8< #%PAM-1.0 auth required pam_nologin.so auth [success=ok default=1] pam_krb5.so forwardable auth [default=done] pam_openafs_session.so use_first_pass auth sufficient pam_ldap.so use_first_pass auth required pam_unix.so try_first_pass auth required pam_env.so # [1] accountsufficient pam_krb5.so accountsufficient pam_ldap.so accountrequired pam_unix.so sessionrequired pam_mkhomedir.so skel=/etc/skel umask=0077 sessionoptional pam_krb5.so sessionoptional pam_ldap.so sessionrequired pam_unix.so sessionoptional pam_lastlog.so # [1] sessionoptional pam_motd.so # [1] sessionoptional pam_mail.so standard noenv # [1] sessionrequired pam_limits.so password required pam_cracklib.so retry=3 minlen=6 difok=3 password required pam_unix.so use_authtok nullok md5 >8 When logging in via ssh, I get my kerberos ticket and the afs token. Everything's fine. Using the same pam.d file for KDM fails for some reason. After moving myself to a non-AFS directory, I can see this behaviour: I get the kerberos ticket... [EMAIL PROTECTED]:~$ klist Ticket cache: FILE:/tmp/krb5cc_E7R4tK Default principal: [EMAIL PROTECTED] Valid starting ExpiresService principal 05/08/03 08:02:22 05/08/03 18:02:22 krbtgt/[EMAIL PROTECTED] Kerberos 4 ticket cache: /tmp/tkt1001 klist: You have no tickets cached [EMAIL PROTECTED]:~$ But the afs token is not present. The logfile (and even the aklog command) say... [EMAIL PROTECTED]:~$ aklog aklog: Couldn't get polle.local AFS tickets: aklog: Decrypt integrity check failed while getting AFS tickets [EMAIL PROTECTED]:~$ BUT - after using kinit to get the ticket manually, aklog works fine. I noticed that kdebase can be compiled using --with-afs. Do I need to recompile kdebase? Normally pam should work out of the box... Just confused, Cajus
Re: agypten gpg-agent segfaults
On Thursday 08 May 2003 05:28, Greg Cockburn wrote: > If anyone has any ideas or pointers that would be great, Have you tried recompiling your gpg-agent? Maybe some libraries were updated... (Just to warn you: I don't know at all what your problem is and this is just a completely wild guess.) -- -M --- Magnus von Koeller --- email:[EMAIL PROTECTED] address: Heinrich-Heine-Str. 10 D-38102 Braunschweig / Germany phone:+49-531-2094886 mobile: +49-179-4562940 web: http://www.vonkoeller.de pgpgFtm2Pp3Sg.pgp Description: signature
Kmail Crash for unknown gpg keys
I have kmail installed whith crypto-plugin compiled as told at: http://kmail.kde.org/kmail-pgpmime-howto.html But I have two problems: 1) It happens sometimes when I'm typing my gpg-key password that pinentry exits when I type too fast. I meen when two letters are entered very fastly ;-). So it comes back to the mail editor and tells me my password is incorrect. Sometimes I have to type it five or six times for it to be accepted. 2) Kmail crashes when I want to see a signed mail I don't have the key i my keyring. (It doesn't crashes fully since I have to wait for 2 or 3 min before it comes back). It is a heavy loss of time when reading this list ;-). I use sarge (testing) and I tried to recompile all the OpenPGP plugin for Kmail but it didn't change anything. I don't want to try again because of the mess there is in sarge for QT libs (I can't compile or install any package using them). I use this plugin: "gpgme-openpgp.so". There is another ".so" file in the same dir called "gpgme-smime.so" but seems it is useless for Kmail. If someone can help me. thank you -- Germs pgpZoJZqrjolo.pgp Description: signature
Re: agypten gpg-agent segfaults
several times :-( On Thu, 08 May 2003 19:34, Magnus von Koeller wrote: > On Thursday 08 May 2003 05:28, Greg Cockburn wrote: > > If anyone has any ideas or pointers that would be great, > > Have you tried recompiling your gpg-agent? Maybe some libraries were > updated... (Just to warn you: I don't know at all what your problem > is and this is just a completely wild guess.) -- Greg Cockburn, LCA Performance Magic WGTN, NZ Cell: +64 25 275 6378 Ph: +64 4 971 1980 ICQ: 19058919
Terminals - Comparison ?
Just started using Debian and KDE again recently and I have a question: What are the different terminals available and what are their advantages and disadvantages? So far, I've just been using Konsole, as that's the one I get get by clicking on the menu bar (I've got a default set-up right now). My only complaint right now is that the 'Page Up' and 'Page Down' keys do not work, but what else should I expect from my term? What kinds of flexibilities should I expect? Feel free to educate me. Thanx, msd
Re: Problem with upgrading to KDE 3.1.1 on Debian woody: finally solved
[ Please CC me on replies as I'm not suscribed to -kde ] Hi all, On Tue, May 06, 2003 at 11:48:41PM +0800, R (Chandra) Chandrasekhar wrote: > Guillem Jover wrote: > > deb http://www.hadrons.org/~guillem/debian woody/binary/ > > I installed this package and found that kdm did not crash. However, > after each startup of the X server, I get a > "Print jobs for ps: KJobViewer" > window popping up. Why, I do not know. This does not happen with > xfs-xtt, for instance. Did you upgraded any other kde related package? Do you have a standard testing installation, or any external apt repositories? > >Also there are certain fonts that when installed, make X crash. > >If the above don't solve the problem could you send me the output of: > > > > xfstt --gslist --sync > > Output file of this is attached as xfstt_output.txt Ok thanks. But if now it doesn't crash I don't think it is related with the fonts. > My current workaround is to use xfs-xtt instead of xfstt. I am confused > about whether I also need xfs or whether I need only ONE of xfs, xfs-xtt > OR xfstt. Advice on this is most appreciated. The rendering engines are different, you'll have to decide which one looks better :>. Also now xfs should support truetype fonts. You will need either xfs or xfs-xtt or xfs + xfstt. > Also, after the last kdm crash report, I found I needed to install > xlibmesa3-glu version 4.2.1-6 to make .jpg KDE wallpapers and > screensavers work. Because kdm needs a background (Debian) wallpaper on > my machine, this could also have contributed to kdm crashing. I hope > this helps rather than confuses! Could you uninstall this package to see if it crashes, so we can discard one possible problem? regards, guillem
Re: Terminals - Comparison ?
>Just started using Debian and KDE again recently and I have a question: What >are the different terminals available and what are their advantages and >disadvantages? > Talk about a loaded question (-; That all depends on what you expect from a terminal. Basically, they just provide a simulation of a shell login CLI. After that, the rest is eye candy. Konsole is the standard shell for KDE. It's very useful, including the ability to open several terminals in one window using tabs to access them. Eterm is a very pretty terminal with lots of extra eye candy. You can set images for the background and even set transparency if you likt that sort of thing. Xterm is the bog standard of X. It only provides the minimal functionality, but doen't need a lot of extra libs to run. Gnome has thier own. But I think at this point konsole and Gnome term are pretty similar in use and functionality. Of course there is probably a lot list of others that I have never even heard of. >So far, I've just been using Konsole, as that's the one I get get by clicking on >the menu bar (I've got a default set-up right now). My only complaint right now >is that the 'Page Up' and 'Page Down' keys do not work, but what else should I >expect from my term? What kinds of flexibilities should I expect? > Well, Page Up and Page Down usually doesn't work in a regular terminal either. At least not the way you might think they should. Actually you need to use Page Up and Page Down, I think, to get the terminal to scroll. At least that's how I do it. This is a feature of the console, not a limitation of the terminal program. It was a little strange to me at first, but now it's become second nature that I try to do it on M$Windows boxes all the time now (-; >Feel free to educate me. > If it's education you want, search the web. There are lots of sites with loads of information. Doing a google for xterm should give a rather comprehensive list of terminal programs. Check their sites for info. There are also quite a few UNIX teaching sites as well. Anything about UNIX can usually be applied directly to a Linux box. Cheers, John Gay
Re: Terminals - Comparison ?
On Thursday 08 May 2003 03:52 pm, John Gay wrote: > Konsole is the standard shell for KDE. It's very useful, including the > ability to open several terminals in one window using tabs to access them. > > Eterm is a very pretty terminal with lots of extra eye candy. You can set > images for the background and even set transparency if you likt that sort > of thing. Not to be pedantic, but konsole does this too. Of course, some people like to have borderless consoles (usually monitoring /var/log/messages or something) sitting on their desktop; for that, aterm is usually the best, in that it offers the transparency and image control of both konsole and eterm without the extra weight. Eterm does have "themes," so that you can change the menus and whatnot, but the only advantage I can see for this is with IRC or ssh sessions, in which case konsole has its bookmarks. :Peter -- Oh what a tangled web they weave who try a new word to conceive!
sim 0.8.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hello, has anyone seen debian packages (sid) for sim.0.8.2? thank you wolfgang - -- ... there are 10 types of people in the world - those who understand binary and those who don't. Micro$oft gives you Windows, Linux gives you the whole house. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+uudquEUiBhld/2URApc2AJ0bkZWwbne2qFv6oDzAE9M+afImdwCfULbI xXJb/fVf5yQhkLmpHObZehM= =Xh8R -END PGP SIGNATURE-
Re: Terminals - Comparison ?
On Thu, May 08, 2003 at 04:39:02PM -0500, Peter Clark wrote: > > On Thursday 08 May 2003 03:52 pm, John Gay wrote: > > > Eterm is a very pretty terminal with lots of extra eye > > candy. You can set images for the background and even > > set transparency if you likt that sort of thing. > > Not to be pedantic, but konsole does this too. Indeed, and konsole's support for transparency is better (at least easier to configure) than gnome-terminal's. In particular, I like to use a transparent background, but I like it to be muted nearly white, regardless of the color of the desktop background image. gnome-terminal allows the transparent background easily to be shaded, but only toward black. Perhaps there is a way to hack a config file with vi in order to get gnome-terminal to do what I want. But konsole let's me get the right behavior from the standard control interface. -- Thomas E. Vaughan (303) 939-6386 Ball Aerospace, Boulder
Re: Terminals - Comparison ?
On Thu, 8 May 2003 21:52:39 +0100, John Gay wrote: [ Michael S Daines wrote :] >>Just started using Debian and KDE again recently and I have a >>question: What are the different terminals available and what >>are their advantages and disadvantages? >> >Talk about a loaded question (-; > >That all depends on what you expect from a terminal. Basically, they just >provide a simulation of a shell login CLI. After that, the rest is eye >candy. Hmm .. I have to disagree here - there's also the question of which real-world terminal(s) is(are) emulated by the terminal package. If all you need to do is run a shell and interact with simple scroll-mode commands then you won't care much about the emulation, but if you want to login to the usual kind of applications on legacy (big-iron) remote systems (via Telnet or SSH), or if you want to use a local screen-mode Linux application (e.g. a decent editor, or a curses application) then you need to think about the emulation your terminal provides. This has a bearing on which format effectors (escape sequences) the (emulated) terminal can understand and obey. (AFAIK) All Linux terminal emulations will offer the standard "Linux console" emulation - which seems intended for simple scroll mode command input & output, but also supports the popular editors. If you run something that produces output that looks all messed up, then it's likely you've either configured the wrong terminal type environment variable ($TERM), or your terminal doesn't support some of the escape sequences that the software is using. Most emulations generally also mimic one or other of the terminals in the legendary DEC VTnnn series (for both Linux and Win32), and, of those, most emulations actually try to implement no more than the VT102, which was a fairly basic terminal. I believe this applies to xterm, eterm, and rxvt. At my place of work, we run a lot of VMS-based "green-screen" applications which want to use terminal escape sequences that only a VT420 offers, and also some which were introduced with VT220s. I believe Konsole offers "VT220+", which is VT220 with some of the more useful enhancements from VT320 onwards. Most people can just ignore all this, but it becomes an issue for some of us. One of my usual quests on any given machine I have to use is to find a good VT420 emulation. I'd also pay good beer to find a useful HP9000 terminal emulation (for running things on HPUX systems) - all pointers gratefully received. For my purposes, Konsole is currently far and away the best terminal package for use on KDE. If you run any other terminal package, make sure it's patched up to date - a serious security issue was discovered relatively recently (Feb.2003) to do with the way almost all Linux terminal emulations handled an escape sequence whose purpose is to set the window title. (See http://www.iss.net/security_center/static/11414.php) I've droned on far too long now ;-) - sorry. Nick Boyce Bristol, UK -- `To alcohol! The cause of, and solution to, all of life's problems' --Homer J. Simpson
