[Touch-packages] [Bug 794315] Re: lightdm forgets to source /etc/profile and ~/.profile

[Daniel Colascione]

Derek, sourcing .profile makes perfect sense. You can't rely on having a
terminal or really being interactive or anything else _anyway_, and in
practice, long experience shows that sourcing profile in Xsession
actually doesn't cause any problems in practice. Display managers should
_always_ source .profile.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/794315

Title:
  lightdm forgets to source /etc/profile and ~/.profile

Status in Light Display Manager:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm package in Debian:
  Confirmed

Bug description:
  Binary package hint: lightdm

  /etc/gdm/Xsession had this code:
# First read /etc/profile and .profile
test -f /etc/profile && . /etc/profile
test -f "$HOME/.profile" && . "$HOME/.profile"
# Second read /etc/xprofile and .xprofile for X specific setup
test -f /etc/xprofile && . /etc/xprofile
test -f "$HOME/.xprofile" && . "$HOME/.xprofile"
  so that, for example, ~/bin gets added to the path (by the default 
~/.profile), and any user-customized environment setup gets run.

  After switching from gdm to lightdm, this no longer happens.  This is
  going to be a regression now that lightdm is becoming the default
  display manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.3.7-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
  Uname: Linux 2.6.39-3-generic x86_64
  NonfreeKernelModules: openafs
  Architecture: amd64
  Date: Tue Jun  7 19:27:11 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.utf8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/794315/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1495027] [NEW] unity_support_test should not write to hardcoded file in /tmp

[Daniel Colascione]

Public bug reported:

unity_support_test writes to a file called /tmp/unity_support_test.0 no
matter what value is set in TMP, TMPDIR, and so on. This tool should
respect user preferences and not hardcode the temporary directory.

** Affects: nux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nux in Ubuntu.
https://bugs.launchpad.net/bugs/1495027

Title:
  unity_support_test should not write to hardcoded file in /tmp

Status in nux package in Ubuntu:
  New

Bug description:
  unity_support_test writes to a file called /tmp/unity_support_test.0
  no matter what value is set in TMP, TMPDIR, and so on. This tool
  should respect user preferences and not hardcode the temporary
  directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1495027/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp