Bug#327191: kdm resets after login because of problem in ~/*profile
The exact line which seems to have posed problem was export DISPLAY=john:0.0 in .bash_profile. I'm a bit stumped as to why that is troublesome, though I guess it must conflict with the env var set by X (which is just 0:0). I think I added that line when I had XDMCP enabled and was doing stuff on another display-less machine. That way when I'd login through SSH, I could immediately launch a program that would display on my local machine. I guess I'll have to do a little more work for the script to distinguish between being launched by X or during a login. It would be useful to warn the user of this 'new' behaviour, maybe in /usr/share/doc/NEWS.Debian. This seems quite reasonable. For the record, are you requesting that the new behaviour be reverted, or simply that users be given better notice to allow them to adapt with less hassle and frustration? Oh no, I wouldn't dare request a behaviour change. After all, I expect that being The Great Respected Maintainer, you know what you're doing ;). No, just giving users better notice should be enough. For example, a nice blatant warning during the pre-configure phase, as well as something in /usr/share/doc/kdm other than the changelog (through which I went, and must've missed that part, or dismissed as irrelevant) John
Processed: Re: Bug#327191: kdm resets after login because of problem in ~/*profile
Processing commands for [EMAIL PROTECTED]: tags 327191 pending Bug#327191: kdm resets after login because of problem in ~/*profile There were no tags set. Tags added: pending stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327191: kdm resets after login because of problem in ~/*profile
tags 327191 pending stop On September 9, 2005 08:42, Jean de Largentaye wrote: Oh no, I wouldn't dare request a behaviour change. After all, I expect that being The Great Respected Maintainer, you know what you're doing ;). That's the theory, anyway :) No, just giving users better notice should be enough. For example, a nice blatant warning during the pre-configure phase, as well as something in /usr/share/doc/kdm other than the changelog (through which I went, and must've missed that part, or dismissed as irrelevant) I've added a lengthy item to the NEWS.Debian for kdm, so users shouldn't be left in the dark. If you use apt-listchanges, it will be displayed automatically; otherwise it will be located in /usr/share/doc/kdm. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327191: kdm resets after login because of problem in ~/*profile
Package: kdm Version: 4:3.4.2-2 Severity: important Because KDM sources the ~/*profile login scripts in /etc/kde3/kdm/Xsessions and because of previously (and as yet) undetected problems in these scripts, KDM resets after login, considering the session has ended. These scripts worked fine previously (and still do, in, say, GDM). Obviously this is a user error, but it is uncovered by the new sourcing behaviour. Because there was no problem in KDM itself, and the session exited 'normally', the problem was very difficult to track down. This effectively rendered KDM useless. It would be useful to warn the user of this 'new' behaviour, maybe in /usr/share/doc/NEWS.Debian. John de Largentaye -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kdm depends on: ii debconf [debconf-2.0] 1.4.58 Debian configuration management sy ii kdebase-bin 4:3.4.2-2 core binaries for the KDE base mod ii kdebase-data 4:3.4.2-2 shared data files for the KDE base ii kdelibs4c24:3.4.2-3 core libraries for all KDE applica ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libgcc1 1:4.0.1-6 GCC support library ii libpam-runtime0.76-23Runtime support for the PAM librar ii libpam0g 0.76-23Pluggable Authentication Modules l ii libqt3-mt 3:3.3.4-7 Qt GUI Library (Threaded runtime v ii libstdc++64.0.1-6The GNU Standard C++ Library v3 ii libx11-6 6.8.2.dfsg.1-6 X Window System protocol client li ii libxau6 6.8.2.dfsg.1-6 X Authentication library ii libxdmcp6 6.8.2.dfsg.1-6 X Display Manager Control Protocol ii libxtst6 6.8.2.dfsg.1-6 X Window System event recording an ii xbase-clients 6.8.2.dfsg.1-6 miscellaneous X clients ii xlibs 6.8.2.dfsg.1-6 X Window System client libraries m Versions of packages kdm recommends: ii logrotate 3.7.1-2Log rotation utility -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327191: kdm resets after login because of problem in ~/*profile
On September 8, 2005 05:21, Jean de Largentaye wrote: Because KDM sources the ~/*profile login scripts in /etc/kde3/kdm/Xsessions and because of previously (and as yet) undetected problems in these scripts, KDM resets after login, considering the session has ended. These scripts worked fine previously (and still do, in, say, GDM). Obviously this is a user error, but it is uncovered by the new sourcing behaviour. Because there was no problem in KDM itself, and the session exited 'normally', the problem was very difficult to track down. GDM's Xsession script doesn't source ~/.bash_profile, ~/.profile, or even /etc/profile. It used to, once upon a time, but this was disabled, because users complained of exactly the behaviour you are now encountering. See bug #155335. KDM has long supported the sourcing of $HOME login scripts, but this functionality was disabled by the maintainer at the time. This lack was the origin of a number of bug reports. I decided to stop disabling this functionality in the 3.4.0 packages that were placed on alioth earlier this year, and subsequent 3.4.x updates, and everything seemed to be fine, i.e. there were no complaints that I can recall, other than a problem with zsh that I fixed. Thus I didn't give much more thought to the matter, and the change was mentioned only in the changelog. It would be useful to warn the user of this 'new' behaviour, maybe in /usr/share/doc/NEWS.Debian. This seems quite reasonable. For the record, are you requesting that the new behaviour be reverted, or simply that users be given better notice to allow them to adapt with less hassle and frustration? I'm CCing debian-kde, because people there have encountered this problem as well, and may wish to comment. Cheers, Christopher Martin pgpS7rK4Fk8cD.pgp Description: PGP signature
