Bug#327191: kdm resets after login because of problem in ~/*profile - Debian

This is a discussion on Bug#327191: kdm resets after login because of problem in ~/*profile - Debian ; 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 > ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Bug#327191: kdm resets after login because of problem in ~/*profile

  1. 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

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.1 (GNU/Linux)
    Comment: Signed by Christopher Martin

    iD8DBQBDIDbEU+gWW+vtsysRAhMFAJ4sk9QQpwFlPJjmkmJkEy +Atc3g9gCfWYEt
    VwmTAn8eoA9DqjxZ62796hc=
    =LYb1
    -----END PGP SIGNATURE-----


  2. 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

  3. 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 debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  4. Re: Bug#327191: kdm resets after login because of problem in ~/*profile

    On Friday 09 September 2005 14:42, Jean de Largentaye wrote:
    > The exact line which seems to have posed problem was
    > export DISPLAY=john:0.0


    use ssh -X and remove the DISPLAY setting.

    Achim

    > 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
    >
    >


    --
    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.
    -- reddy@lion.austin.ibm.com


    --
    To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

+ Reply to Thread