I came across this problem when doing a clean install of Lucid.
I had an existing /home partition which was not formatted. I'm not sure
if the installer overwrote my .bashrc, but I couldn't login to GDM after
the install was finished. I overwrote my .bashrc with the default Lucid
skeleton
While researching this problem further, I stumbled across this page:
https://wiki.ubuntu.com/DashAsBinSh
Prior to the release of 6.10, Ubuntu developers made a conscious
decision to change the default shell (the shell that is used to load
scripts in /etc/profile.d) from bash to dash. dash is
I can confirm that this is a problem in Ubuntu 9.10 (Karmic Koala).
I have files in /etc/profile.d that use bash-isms (source and declare,
for example). When logging in from a regular terminal (pressing
CTRL+ALT+F2 at the gdm login window) there is no problem, but when I
login in from gdm, the
This has reared itself again in Karmic.
/etc/gdm/Xsession uses /bin/dash as its parser, but sets the $SHELL
environment variable to /bin/bash (!). This makes any ~/.profile that
uses bash-isms kill the gdm login process.
--
shopt xsession error upon login
https://bugs.launchpad.net/bugs/60079
I had a similar problem not being able to log in to the default GNOME
session ( your last session lasted less than 10 seconds message). The
problem came from the fact that I had created a .profile symlink linking
to .bashrc. unlink .profile fixed the problem for me
--
shopt xsession error upon
As described in the previous comments, your report lacks the information
we need to investigate the problem further. We'll close this report for
now - please reopen it if you can give us the missing information.
** Changed in: gdm (Ubuntu)
Status: Needs Info = Rejected
--
shopt xsession
Right, I see what's going on here. I edited my /etc/profile not to check
for these two variables.
I would say that was a misunderstanding on my part and those others who
removed the checks.
I have added the checks back in and everything works fine.
--
shopt xsession error upon login
Thank you for confirming that Noah. Benjamin, did you change your
profile?
** Changed in: gdm (Ubuntu)
Status: Unconfirmed = Needs Info
--
shopt xsession error upon login
https://launchpad.net/bugs/60079
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
nope, I didn't edit /etc/profile, nor do I have a ~/.profile file, only
~/.bashrc
looking at it closely, it's the one from /etc/skel/.bashrc with a few
aliases and env vars added, and a set -o vi
I can't imagine that would trigger bash-specific behavior, but I
dunno...
--
shopt xsession error
that's not likely due to some user file, what do you have to
/etc/profile? Could you copy it to a comment?
--
shopt xsession error upon login
https://launchpad.net/bugs/60079
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
attached is my /etc/profile
** Attachment added: /etc/profile
http://librarian.launchpad.net/6339021/profile
--
shopt xsession error upon login
https://launchpad.net/bugs/60079
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
the profile looks like the stock one, did you change any of the xorg
startup files? could that change make bash_completion be loaded?
--
shopt xsession error upon login
https://launchpad.net/bugs/60079
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
The bug is marked rejected because nobody reopened it, doing that now.
That doesn't really look like a gdm bug though, the /etc/gdm/Xsession
instructions work fine with sh. The /etc/profile file is loaded, it
sources bash.bashrc only if PS1 and BASH are set, is that the case when
gdm is starting?
Bump. Why is this still at rejected?
--
shopt xsession error upon login
https://launchpad.net/bugs/60079
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Where do you have your bash specific commands, shouldn't your startup
file use #!/bin/bash if you are using them?
--
shopt xsession error upon login
https://launchpad.net/bugs/60079
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
No, my file of bash specific start up commands is in /etc/bash.bashrc
which is sourced from /etc/profile
You cannot put the hash bang at the top of a sourced file.
I do not think I am alone in having bash specific stuff in these files
which is why there are a few other cases of people
I can confirm that this a bug for me too.
My global /etc/bash.bashrc file is sourcing /etc/bash_completion which
in turn exits with a error status of 2 with the following message:
/etc/bash_completion: 44: Syntax error: Bad substitution
You can reproduce by sourcing /etc/bash_completion your
that looks like a bash bug, not a gdm one
--
shopt xsession error upon login
https://launchpad.net/bugs/60079
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
https://launchpad.net/ubuntu/+source/bash/+bug/82276
--
shopt xsession error upon login
https://launchpad.net/bugs/60079
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Should I refile against Ubuntu bash?
--
shopt xsession error upon login
https://launchpad.net/bugs/60079
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I think I have figured it out...
My /etc/profile was sourcing /etc/bash.bashrc every time.
You must have made a change to /etc/X11/Xsession recently that means
when you source /etc/profile under sh you end up sourcing
/etc/bash.bashrc.
I assume I am in the wrong here so I have removed the line
Thinking about it a little more... this is happening becuase I have bash
specific commands in one of my startup files. The gdm package is
sourcing my startup files under sh.
I think therefor that the bug is with the gdm package.
--
shopt xsession error upon login
Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.
** Changed in: gdm (Ubuntu)
Status: Needs Info = Rejected
--
shopt xsession error upon login
https://launchpad.net/bugs/60079
--
the session to start is written to .dmrc. Do you have the same issue if
you pick GNOME from the sessions list?
--
shopt xsession error upon login
https://launchpad.net/bugs/60079
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Thanks for your bug. What session did you pick from gdm? gdm has no
reason to use .bashrc if bash is not used. Using to shopt to .bashrc
doesn't stop the session to start on my edgy desktop
** Changed in: gdm (Ubuntu)
Importance: Untriaged = Low
Assignee: (unassigned) = Ubuntu Desktop
How would I go about figuring out what session I've got? When I'm in
gdm, it just says last session and an ls -la in my home dir doesn't
give me anything with session in the name.
I'm starting up in gnome, if that's what you're referring to.
--
shopt xsession error upon login
26 matches
Mail list logo
