** Merge proposal linked:
https://code.launchpad.net/~canonical-desktop-team/ubuntu/+source/gdm3/+git/gdm3/+merge/349818
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~canonical-desktop-team/ubuntu/+source/gdm3/+git/gdm3/+merge/348784
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Changed in: gdm
Status: Confirmed => Won't Fix
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status
** Changed in: gdm
Status: New = Confirmed
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status in
This bug was fixed in the package lightdm - 1.12.3-0ubuntu1
---
lightdm (1.12.3-0ubuntu1) utopic; urgency=medium
* New upstream release:
- Fix pipe file descriptor leak for each greeter session. (LP: #1190344)
- Don't attempt generate D-Bus seat/session removal signals on
I have successfully installed and run lightdm 1.12.3-0ubuntu1 from
utopic-proposed. The behavior in case of a syntax error in ~/.profile
has changed in accordance with the test case in the bug description.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received
Hello Egon, or anyone else affected,
Accepted lightdm into utopic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.12.3-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Ok, thanks, Daniel. This way I learned something new. :)
I think the reason for the confusion is that stderr is already
redirected when the code in ~/.profile is run. It's done through this
line in /usr/sbin/lightdm-session:
. $CONFIG_FILE 2$ERR
So if you want it to work as before, you need
On 25.02.2015 23:42, Gunnar Hjalmarsson wrote:
Thanks for your comments!
On 2015-02-25 19:56, Daniel Hahler wrote:
set -x
exec 1$logfile
exec 2$logfile
Really using the exec command in ~/.profile would stop the execution
of the main process (/usr/sbin/lightdm-session), so I
Thanks for working on this!
For what it's worth, I've been using the following, and had to move the
set -x now below the exec 2$logfile, otherwise this was detected
as being an error.
1. I've been using the following in ~/.profile, mainly for debugging
purposes:
Hi Daniel,
Thanks for your comments!
On 2015-02-25 19:56, Daniel Hahler wrote:
set -x
exec 1$logfile
exec 2$logfile
Really using the exec command in ~/.profile would stop the execution
of the main process (/usr/sbin/lightdm-session), so I suppose your
~/.profile did not literally
This bug was fixed in the package lightdm - 1.10.4-0ubuntu2
---
lightdm (1.10.4-0ubuntu2) trusty; urgency=medium
* debian/config-error-dialog.sh:
* debian/lightdm-session:
- Use bash for the session to improve error handling (LP: #678421)
* debian/control:
- Depend on
This bug was fixed in the package gdm - 3.10.0.1-0ubuntu7.1
---
gdm (3.10.0.1-0ubuntu7.1) utopic; urgency=medium
* debian/patches/ubuntu_config_error_dialog.patch:
- Show warning dialog in case of error in ~/.profile etc. and
don't let a syntax error make the login fail
I verified gdm on utopic with both a valid and broken .profile, all
working as expected
--
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/678421
Title:
Error message for a
Thanks Tim, with that all the SRUs have been verified at last. :)
** Tags removed: verification-done-trusty verification-needed-utopic
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm
This bug was fixed in the package gdm - 3.10.0.1-0ubuntu3.1
---
gdm (3.10.0.1-0ubuntu3.1) trusty; urgency=medium
* debian/patches/ubuntu_config_error_dialog.patch:
- Show warning dialog in case of error in ~/.profile etc. and
don't let a syntax error make the login fail
Sorry, misunderstanding. I restored the previous tags, which seem to be
correct.
** Tags removed: verification-done
** Tags added: verification-done-trusty verification-needed-utopic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Tags removed: verification-done-utopic-lightdm verification-needed
** Tags added: verification-needed-utopic
--
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/678421
Title:
** Tags removed: verification-done-trusty verification-needed-utopic
** Tags added: verification-done
--
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/678421
Title:
Error
@Gunnar - the SRU team tools understand the tags v-done and
v-done-$release, but not v-done-$release-$package.
** Tags removed: verification-done-trusty-gdm verification-done-trusty-lightdm
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of
Thanks for the correction, Brian.
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome
** Branch linked: lp:ubuntu/utopic-proposed/gdm
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM:
Hello Egon, or anyone else affected,
Accepted gdm into utopic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gdm/3.10.0.1-0ubuntu7.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/trusty-proposed/gdm
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM:
Hello Egon, or anyone else affected,
Accepted gdm into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/gdm/3.10.0.1-0ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: gdm (Debian)
Status: Unknown = New
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status
** Bug watch added: Debian Bug tracker #774798
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774798
** Also affects: gdm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774798
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
** Changed in: gdm (Ubuntu Trusty)
Status: Triaged = In Progress
** Changed in: gdm (Ubuntu Trusty)
Assignee: (unassigned) = Gunnar Hjalmarsson (gunnarhj)
** Changed in: gdm (Ubuntu Utopic)
Status: Triaged = In Progress
** Changed in: gdm (Ubuntu Utopic)
Assignee:
** Branch linked: lp:~gunnarhj/ubuntu/utopic/gdm/config-error-dialog
** Branch linked: lp:~gunnarhj/ubuntu/trusty/gdm/config-error-dialog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Branch unlinked: lp:lightdm/1.10
** Branch unlinked: lp:lightdm/1.12
--
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/678421
Title:
Error message for a faulty
** Branch linked: lp:ubuntu/vivid-proposed/gdm
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM:
This bug was fixed in the package gdm - 3.14.0-0ubuntu2
---
gdm (3.14.0-0ubuntu2) vivid; urgency=medium
* debian/patches/ubuntu_config_error_dialog.patch:
- Show warning dialog in case of error in ~/.profile etc. and
don't let a syntax error make the login fail (LP:
Hello Egon, or anyone else affected,
Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.4-0ubuntu2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/trusty-proposed/lightdm
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status in
I have successfully installed and run lightdm 1.10.4-0ubuntu2 from
trusty-proposed. The behavior in case of a syntax error in ~/.profile
has changed in accordance with the test case in the bug description.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received
** Branch linked: lp:~gunnarhj/lightdm/config-error-dialog_utopic
** Branch linked: lp:~gunnarhj/lightdm/config-error-dialog_trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Branch linked: lp:ubuntu/vivid-proposed/lightdm
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status in
This bug was fixed in the package lightdm - 1.13.0-0ubuntu2
---
lightdm (1.13.0-0ubuntu2) vivid; urgency=medium
* debian/config-error-dialog.sh:
* debian/lightdm-session:
- Use bash for the session to improve error handling (LP: #678421)
* debian/control:
- Depend on
Thanks for looking at it, Martin.
Actually I may have found a relatively trivial solution using trap();
please see attached diff.
** Patch added: possible-fix.diff
https://bugs.launchpad.net/ubuntu/trusty/+source/lightdm/+bug/678421/+attachment/4263541/+files/possible-fix.diff
--
You
Hah, nice! Works for me, too.
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display
** Branch linked: lp:~gunnarhj/lightdm/config-error-dialog
--
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/678421
Title:
Error message for a faulty ~/.profile script
. $CONFIG_FILE 2$ERR
OTOH, I suppose that switching to bash wouldn't be approved just like that. ;)
Bash's input redirection simply is way more powerful. Granted, bash
takes a tad longer to start up, but any tee or other external program
which you call in addition will probably hurt
On Nov 18, 2014, at 02:41 PM, Martin Pitt wrote:
Bash's input redirection simply is way more powerful. Granted, bash
takes a tad longer to start up, but any tee or other external program
which you call in addition will probably hurt performance just as much.
Purely selfishly, switching back to
I have been googling and experimenting a bit. Basically I'd like to
change:
. $CONFIG_FILE 2$ERR
to something along these lines:
. $CONFIG_FILE 2 (tee $ERR 2)
There is just one tiny problem: It's bash syntax and doesn't work in sh.
If I change the shebang line of /usr/sbin/lightdm-session
** Branch linked: lp:ubuntu/lightdm
** Branch linked: lp:ubuntu/utopic-proposed/lightdm
--
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/678421
Title:
Error message for a
apt-mark lightdm hold apt-get dist-upgrade reboot
Indeed, logins are fine.
--
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/678421
Title:
Error message for a faulty
Hmm, as 1.13.0-0ubuntu1 just showed up in vivid, it broke my login in
the follow way. Note that I always try devel channel updates in a VM
with a snapshotted disk so I'm able to revert and do some further
investigating. Looking at the dist-upgrade packages, I suspect the
lightdm changes are
For now I'll keep the hold on lightdm, but if Robert or someone else
wants to debug in real-time, ping me on irc.
--
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/678421
Hi Barry!
On 2014-11-14 17:56, Barry Warsaw wrote:
So, when I log in, I do get several warnings in a dialog. Most are
because I use `source` instead of `.` to source other shell files.
What shell is lightdm using these days?
It has always been using Bourne shell, so source is not
Hi Gunnar.
On Nov 14, 2014, at 07:07 PM, Gunnar Hjalmarsson wrote:
It has always been using Bourne shell, so source is not understood.
You have obliviously been running your system without the configuration
in those other shell files.
Sure, it's entirely possibly that my login has been silently
Being thrown back indicates a syntax error. One thing you could do is
testing each one of your sourced files like this:
sh -n file
The files must pass that test, or else you won't be able to log in.
This is what the new lightdm code does, but it does not work
recursively...
--
You received
On 2014-11-14 20:43, Barry Warsaw wrote:
Sure, it's entirely possibly that my login has been silently ignoring
the non-sh syntax errors, so in that respect, getting notification of
them now is a good thing.
The use of commands unknown to sh is one kind of error that was silently
ignored.
On Nov 14, 2014, at 08:15 PM, Gunnar Hjalmarsson wrote:
Being thrown back indicates a syntax error.
Are those errors logged anywhere permanently?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
On 2014-11-14 21:45, Barry Warsaw wrote:
On Nov 14, 2014, at 08:15 PM, Gunnar Hjalmarsson wrote:
Being thrown back indicates a syntax error.
Are those errors logged anywhere permanently?
I don't know. Syntax errors directly in e.g. ~/.profile or /etc/profile
are logged in ~/.xsession-errors
On Nov 14, 2014, at 09:59 PM, Gunnar Hjalmarsson wrote:
I don't know. Syntax errors directly in e.g. ~/.profile or /etc/profile
are logged in ~/.xsession-errors both with the latest lightdm version
and with previous versions, but I don't know whether syntax errors in
files which are sourced from
I created the file /etc/profile.d/wrong.sh with a sh syntax error. With
lightdm 1.12.1-0ubuntu1 the reason for the login failure is logged in
~/.xsession-errors, but with the latest lightdm version it's not. So
there is a regression with the fix of this bug.
The reason is that stderr is
On Nov 14, 2014, at 11:38 PM, Gunnar Hjalmarsson wrote:
Right now I don't know how to best deal with this issue. Any advice
appreciated.
Probably use tee(1) to get the output both into the temp file and
~/.xsession-errors.
--
You received this bug notification because you are a member of
On 2014-11-15 00:49, Barry Warsaw wrote:
On Nov 14, 2014, at 11:38 PM, Gunnar Hjalmarsson wrote:
Right now I don't know how to best deal with this issue. Any
advice appreciated.
Probably use tee(1) to get the output both into the temp file and
~/.xsession-errors.
Yeah.. But I fear that
Hello Egon, or anyone else affected,
Accepted lightdm into utopic-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lightdm/1.12.2-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I have successfully installed and run lightdm 1.12.2-0ubuntu1 from
utopic-proposed. The behavior in case of a syntax error in ~/.profile
has changed in accordance with the test case in the bug description.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received
I've removed the tasks on LightDM (the project) as the fixes for this
were all in debian/.
** No longer affects: lightdm/1.12
** No longer affects: lightdm/1.10
** No longer affects: lightdm
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
This bug was fixed in the package lightdm - 1.13.0-0ubuntu1
---
lightdm (1.13.0-0ubuntu1) vivid; urgency=medium
* New upstream release:
- Fix crash when having configuration keys defined in multiple places
(LP: #1377373)
- Fix pipe file descriptor leak for each
** Branch linked: lp:~gunnarhj/ubuntu/vivid/gdm/config-error-dialog
--
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/678421
Title:
Error message for a faulty ~/.profile
** Changed in: gdm (Ubuntu)
Status: Triaged = In Progress
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) = Gunnar Hjalmarsson (gunnarhj)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Branch linked: lp:~gunnarhj/lightdm/lp-678421-utopic
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status
** Description changed:
+ trusty and utopic SRU requests
+ ==
+
+ [Impact]
+
+ In case of a syntax error in either of ~/.profile or a few other similar
+ files, the Xorg login is interrupted, and the user is taken back to the
+ login screen without an explanation.
** Branch linked: lp:~gunnarhj/lightdm/lp-678421-trusty
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status
** Changed in: lightdm/1.10
Status: In Progress = Fix Committed
** Changed in: lightdm/1.12
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Bug watch added: GNOME Bug Tracker #738970
https://bugzilla.gnome.org/show_bug.cgi?id=738970
** Also affects: gdm via
https://bugzilla.gnome.org/show_bug.cgi?id=738970
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
** Changed in: gdm
Status: Unknown = New
** Changed in: gdm
Importance: Unknown = Medium
--
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/678421
Title:
Error
Gunnar,
Running it through sh -n is definitively a good way how to test a
shell script. It of course will miss a lot of errors (variable typos,
failing programs in a set -e script, etc.), but it at least will catch
obvious syntax errors. So ignoring faulty scripts and showing some error
message
** Changed in: lightdm
Milestone: None = 1.13.0
** Changed in: lightdm
Importance: Undecided = Medium
** Changed in: lightdm
Importance: Medium = Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in
** Also affects: gdm (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: gdm (Ubuntu Utopic)
Importance: Low
Status: Triaged
** Also affects: lightdm (Ubuntu Utopic)
Hi Gunnar,
It would make the file not being loaded in case of a syntax error, and
an entry printed to ~/.xsession-errors.
I don't know if it's better to ignore this file in case of syntax errors
or to refuse to start a new session but for me, the most interesting
thing is to notify the user
I think we would also prefer a dialog, but I will take errors in
~/.xsession-errors over nothing. We can instruct our support staff to
look there for these errors; right now there are no errors anywhere and
so it is difficult to debug the root cause of the problem.
-A
--
You received this bug
And I who thought it was so elegant to fix this bug with a few
characters of code. ;)
I suppose we could do a solution with zenity/kdialog, but before
spending time on such a proposal (involving gettext etc.), I would like
to know for sure that sh -n is an acceptable testing method. (Please
note
Hi Matthieu,
That sh -n option sounds interesting indeed, and I just prepared a
merge proposal for lightdm. It would make the file not being loaded in
case of a syntax error, and an entry printed to ~/.xsession-errors.
** Changed in: lightdm
Status: New = In Progress
** Changed in:
Hello,
I also confirm that this bug can still be annoying with the latest versions of
GDM and LightDM :-)
And it can be an easy way to make some jokes just by modifying the .profile!
Then it will be hard for the user to understand why he can no longer start a
new session.
Is it maybe possible
78 matches
Mail list logo
