** Changed in: lightdm (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228079
Title:
Login issue: Lightdm + LDAP + Kerberos
To manage
** Changed in: lightdm (Ubuntu)
Assignee: (unassigned) => Wojciech (wojaugustow)
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks @mloebl, it works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228079
Title:
Login issue: Lightdm + LDAP + Kerberos
To manage notifications about this bug go to:
Hi, I've filed a bug internally on the PBIS Open bugzilla, to change the
common-session entry from sufficient to optional (which is the
same as [success=ok default=ignore] and looks cleaner).
Thanks for picking this up for us!
--
You received this bug notification because you are a member of
@Rob A - Thanks for the follow-up! I can confirm on 14.04 it's also
working well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228079
Title:
Login issue: Lightdm + LDAP + Kerberos
To manage
I have now applied a patch from Ted to start indicators via upstart
user session in ubiquity and it fails the installer in a similar
fashion. This clearly shows that indicators under upstart user session
tasks are not ready yet, nor were tested under lightdm ubiquity.
** Changed in: lightdm
/sbin must be in all users path on Ubuntu. It is the default, and many
thing will not work, if /sbin is not the default path.
Default path on ubuntu is usually set in /etc/environment and has:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
Can you
The workaround with common-session allowed me to log in on my pbis
activated machine as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228079
Title:
Login issue: Lightdm + LDAP + Kerberos
To
This worked for me as well. After applying the fix, unbinding from AD
recognizes that the PAM configuration was manually edited and asks the
user if he wants the system to administer the configuration, or if he
would like to do so manually going forward.
Obviously typical PBIS users want the
Ok, I may have a workaround (not sure yet of any side effects or what
else could be broken...)
Since we did the symlink to /bin/init, this is what .Xsession looks like as we
know:
init: unity-gtk-module main process (3055) terminated with status 127
init: logrotate pre-start process (3053)
After I put in the symlink for initctl into /bin path above and could log in, I
ran into an issue where I was having odd errors like not authorized in the disk
tool, and Network settings within UI were inaccessible, etc This is beyond the
other weird issues with the path stuff from above... I
No symlinks needed for init or initctl and able to log in using pbis as
a domain user with the common-session change.
Is this a bug with Ubuntu or pbis?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This affects installs based on the latest PowerBroker Identity Services
software (downloaded directly from their site, not installed via the
Ubuntu repositories).
In my case, I had PBIS 7.5.1 installed and working before I upgraded. I
did not think to unbind myself from the domain before
Also noticed if I log in via terminal as a domain user, stop lighdm, run
startx, desktop comes up (but no indicator panel on bar.)
I should have also noted in the previous post I was on 13.04 and it
worked fine, and didn't have any problems until upgrading to 13.10.
--
You received this bug
Same problem here, I just upgraded Ubuntu from 13.04 to 13.10
Right now I'm using pbis-open lastest version (7.5.2.1527). This versions
worked fine justa few hours before upgrade.
Upgrade was normal, but when I tried to start session with any domain
user I got a few flashes and returned to
Hmm, I wonder if this could be some odd path issue, status 127 means
command not found. Also would explain why we had to do the symbolic
link for /sbin/init . $PATH getting squashed somehow?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: lightdm (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228079
Title:
Login issue: Lightdm + LDAP + Kerberos
To manage notifications
I'm also seeing this on Gnome Ubuntu as well after staging up a VM to
test it. I have to do the sym link to init, and then once i log in, get
the black screen with a cursor. Not looking like a lightdm issue now.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I believe I am seeing the same problem. I use pbis-open for integration
with Active DIrectory. If I log in as a local user, works fine. However
if I login as a user on the domain, I see the identical problems and
errors in the log as ernst-l.
--
You received this bug notification because you
Installed GDM and set is as default display manger.
service lightdm stop
service gdm start
gives a blank screen. A reboot never goes to the login screen but the
splash screen stays forever. Login on the console is possible.
Ubuntu 13.04: LightDM works without any problems.
--
You received
Would you be able to try this with another display manager, e.g. gdm?
Can you see what $PATH is set to when logging in on a terminal? It looks
at first glance like the session can't find upstart, and that can't find
the session processes to run.
** Changed in: lightdm (Ubuntu)
Status: New
21 matches
Mail list logo
