Reboot needed after domainjoin before login into Gnome as a domain user
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
likewise-open (Ubuntu) |
Fix Released
|
Medium
|
Thierry Carrez | ||
likewise-open5 (Ubuntu) |
Fix Released
|
High
|
Thierry Carrez | ||
ubuntu-docs (Ubuntu) |
Fix Released
|
Wishlist
|
Joel Goguen |
Bug Description
Binary package hint: likewise-open5
I struggled for a good title to this bug report. I would just like to report my experience with this package which has been less than good.
I have tried this package twice from clean and updated installs, once on Ubuntu 9.04 Alpha 6 and twice on the Beta. No other third party sw/ is installed. This in vanilla 9.04 updated with likewise-open5.
I am running using the AMD64 alternate install on a Dell D820 Laptop (wired networking).
On both attempts at using this package, it installed correctly. Using the likewise-open5-gui package I joined an AD domain. However, on first (and every) domain login, I get a Failed to initialise HAL error. After that I get continuous launch of something. I can't say what as my the "something" is started again and again and again filling my task panel with no end. The only option I have to stop this is to log out. If I login with a domain account I get the same again.
So, sod it I think. Not ready yet. Not released, no problems, I'll just uninstall it and I'll be OK.
When uninstalling the package it says it leaves the domain. This seems to be from a client perspective only as the laptop is still visible AD and has to be removed on the domain controller.
After the uninstall, and reboot, when I login (with a local account) my network no longer works. I just see the animated connecting icon. This never stops and I never get an address. If I reconfigure to use a static address, then networking is OK. If I change back to DHCP (good for home and work), then no address again. Not good.
The only way I know of getting everything working again then is to reinstall the laptop.
I'm sure you probably would like a bit more detail for this. Depending on what is requested I will be able to repeat, but given the amount of time it consumes to get everything working again I don't want to repeat too many times so please be explicit as to what is needed. Note I am on GMT+12 (NZ).
Currently I have likewise 4 installed and will try to join the domain, login, leave the domain tomorrow.
I see there is perhaps a feature freeze exception for likewise-open5 such that it might officially get into 9.04. From my perspective it really does not look good (on AMD64).
Changed in likewise-open5 (Ubuntu): | |
status: | Triaged → In Progress |
Changed in likewise-open (Ubuntu): | |
assignee: | nobody → ttx |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in ubuntu-docs (Ubuntu): | |
assignee: | nobody → Joel Goguen (jgoguen) |
status: | Confirmed → In Progress |
tags: | added: patch |
Thanks for testing and reporting those bugs.
There are in fact several separate issues. I'll keep this bug centered on the main issue you reported, "Failed to initialize HAL" followed by various breakage when logging in as a domain user just after joining the domain.
Likewise Open 5 apparently requires DBUS to be completely restarted when likewise-open 4 was happy with DBUS just reloading the configuration. Since restarting DBUS when logged in also results in various desktop breakage, I think we need to ask the user to reboot after joining the domain.
Could you please test that if you:
- Install Likewise Open 5
- Join the domain
- Reboot your machine
- Log in as domain user
Then you don't get the "Failed to initialise HAL" error or other issues ?
If you confirm that it avoids the issue, then we'll add some dialog to ask the user to reboot after a domain join.