[Bug 231180] Re: PolicyKit fails after restarting dbus (restarting all dbus services)
Whenever I run Likewise-Open-gui to connect to the corporate domain in my office, after successfully joining the domain it seems my desktop jumps through some hoops, screen flickers a few times, nautilus opens a window to my home folder, nm-applet disappears, and when I check my syslog it is being flooded with the same message: console-kit-daemon[5583]: WARNING: Could not acquire name; will retry. console-kit-daemon[5583]: WARNING: Failed to acquire org.freeedsktop.ConsoleKit Cheers -- PolicyKit fails after restarting dbus (restarting all dbus services) https://bugs.launchpad.net/bugs/231180 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205111] Re: likewise-open service does not start automatically
I purged and reinstalled likewise-open as per above note. Sorry I did not capture any output from that. Post install did run and as I posted above - the appropriate links are placed: lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc2.d/S20likewise-open -> ../init.d/likewise-open lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc3.d/S20likewise-open -> ../init.d/likewise-open lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc4.d/S20likewise-open -> ../init.d/likewise-open lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc5.d/S20likewise-open -> ../init.d/likewise-open This will result in likewise-winbindd starting at system startup. So installation is not a problem. It is after first trying the system, to log in and log out, of a domain that the startup links are subsequently removed. So... as per my last note the above startup links are REMOVED after: - successful install of likewise-open - logging in a a local user - running the likewise-open-gui to perform a successful connection to the domain - using likewise-open-gui to disconnect from the domain I also notice that at the time of a successful connect to a domain a lot of odd things happens at my gnome desktop: - the desktop loses all icons and panels. just selected wallpaper is present - after a moment the desktop icons all return but things like conky, nm-applet need to be manually restarted - if pidgin is running but minimised to the notification area - after the desktop revives pidgin is no longer minimised and also a folder of my home directory opens on the desktop of its own accord. (the above is also repeated when I use the gui to disconnect from the domain) Adding some more - I notice that when I initiate a connection to a domain my syslog gets flooded with the following messages: console-kit-daemon[5583]: WARNING: Could not acquire name; will retry. console-kit-daemon[5583]: WARNING: Failed to acquire org.freeedsktop.ConsoleKit The above messages begin with a connection to a domain initiated as above with the gui. They do NOT stop when I disconnect from the domain. After disconnecting from the domain I can use my desktop and applications but initiating a log-out of the desktop account, or attempting to shutdown the PC, will result in a hang. I can CTRL-ALT-F1 to a command prompt and restart the gdm but my system is still not stable and I need to reboot. Also look at this bug report: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/231180 Cheers -- likewise-open service does not start automatically https://bugs.launchpad.net/bugs/205111 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205111] Re: likewise-open service does not start automatically
- note all my above comments refer to this situation a. boot up ubuntu 8.04 b. log in as a local user c. at the desktop can see likewise-winbindd did start up at system start if I pull up a terminal and "sudo /etc/init.d/likewise-open status" d. then use the likewise-open-gui to join my PC to a domain Weird things happen on my desktop (see above). syslog (daemon log) is flooded with warnings (see above). I did some further testing: a. boot up ubuntu 8.04 b. log in as local user c. at the desktop can see likewise-winbindd did start up at system start if I pull up a terminal and "sudo /etc/init.d/likewise-open status" d. then open a terminal window and use the likewise-open-cli to join my PC to a domain Same weird things happen on my desktop Now maybe so far my problem is a user problem - not knowing how to use likewise-open properly. Because in all the above scenarios I had never been able to log in to the domain from the ubuntu gui (gdm) screen. Always failed. All I knew was that likewise-winbindd was running and thought that was all was needed. I did some further reading and testing: a. boot up ubuntu 8.04 b. at the gdm GUI login screen I CTRL-ALT-F1 to a cli session. c. in that cli session I initiated a likewise-open-cli domain join. Enter user password - SUCCESS d. then CTRL-ALT-F7 back to the gdm login screen and log in with [EMAIL PROTECTED] and get a successful domain user log on. Here I notice: - I have a new desktop as if a first time user. My "home" directory is /home/DOMAIN/user (not /home/user) - Everything works nicely. I see all the domain servers and PC's in Places>Network - No problem with the logfile getting flooded with warning messages. - When I log out no hangs or problems. Wooohoo!!! So Sweet! Very slick. Very nice. So I am wondering now if the problems I have in the first scenario (logged in as local user - using likewise-open CLI or GUI commands to then join domain) - is because I am doing the wrong thing? Should I be able to do this? Or am I using likewise-open incorrectly if I do that? In summary: Likewise-open only works properly for me when (as well as having likewise-winbindd daemon running) I first drop to a command prompt and join to the domain BEFORE I log in at the gdm GUI (and perhaps that is how its supposed to work??) -- likewise-open service does not start automatically https://bugs.launchpad.net/bugs/205111 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205111] Re: likewise-open service does not start automatically
Hi Brian, Yes I was aware of the need to edit /etc/nsswitch.conf and have been using a corrected version of that file in all the examples above. So there are two queries I have: 1. Do we really need (is this the correct and expected process) to: - stop at the login screen, - CTRL-ALT-F1 to a terminal, - start likewise-winbindd (if it is not running), - initiate a domain-join at the CLI - CTRL-ALT-F7 back to the GDM login prompt - log in using this format "[EMAIL PROTECTED]" 2. If I create the links in /etc/rc2.d (and other runlevels) so that likewise-winbindd will autostart, these links get deleted every time I leave a domain. This results in likewise-winbindd not starting automatically next reboot. -- likewise-open service does not start automatically https://bugs.launchpad.net/bugs/205111 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205111] Re: likewise-open service does not start automatically
In the top summary there is a workaround described. This part is not correct: "It looks like the likewise-open script is not set to start with the system. To fix the problem permanently, running sysv-rc-conf and turning the likewise-open service on for runlevels 2,3,4,5 (for example) seems to work." Seems no matter which method is used to turn the service on for various runlevels. When you "leave" a domain, the start scripts are removed. Service will not be started at next system startup. Workaround.. either: - remember to check if likewise service is running, and start it if needed, before attempting to join a domain or - create an entry in the ubuntu "sessions" application to start the service at each reboot and forget about run scripts. Cheers -- likewise-open service does not start automatically https://bugs.launchpad.net/bugs/205111 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205111] Re: likewise-open service does not start automatically
The problem is not yet fixed. -- likewise-open service does not start automatically https://bugs.launchpad.net/bugs/205111 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205111] Re: likewise-open service does not start automatically
I found that I can execute: sudo update-rc.d likewise-open defaults and the appropriate links are placed: lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc2.d/S20likewise-open -> ../init.d/likewise-open lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc3.d/S20likewise-open -> ../init.d/likewise-open lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc4.d/S20likewise-open -> ../init.d/likewise-open lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc5.d/S20likewise-open -> ../init.d/likewise-open and if I restart then likewise-winbindd will start at system start. If I then log in as a user at GDM, and execute the GUI to connect to a domain, successful. Later disconnect from the domain. Then check - the above links have been removed. This will mean on the next restart likewise-winbindd will not auto start at system startup. Something, some part of the process of connecting and disconnecting from a domain deletes the links needed for autostart with system. Cheers -- likewise-open service does not start automatically https://bugs.launchpad.net/bugs/205111 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 215614] Re: Evolution Exchange unreliability in Hardy
I have done no definitive testing and can therefore add no more than a possibly infuriating "me too" with regards to evolution being pretty much unusable for business purposes with an exchange 2003 mail server - ever since I upgraded to ubuntu 9.04 (Jaunty). (I keep the OS and all updates up to date) It starts up and runs and checks for email and is usable for a few minutes, maybe 5 or 10-15 minutes, then it basically loses connection to back end(?) with no warning. Sent mails dont go out. It doesnt get new inbound email. Close and reopen evolution does not help. Using "evolution --force- shutdown" and restart evolution gets it up again for another 5-15 minutes. With guidance I am happy to find and send up logs etc. -- Evolution Exchange unreliability in Hardy https://bugs.launchpad.net/bugs/215614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
