Re: Hardy Alpha-4 synaptic error
Richard Mancusi wrote: Okay, I did another clean install and can repeat the problem. On a test system I always set a root password and allow root logon. Yes, I know that isn't a great idea, but it comes in handy on a test system. As soon as I set a root password in System/Administration/Users and Groups the root user Home directory moved from /root to /home/root. I guess it's a matter of opinion as to whether this is a bug. Ubuntu and common sense tells you to not set a root password. But if you are going to allow it, it should work correctly. I leave that to the developers. Agreed, setting a root password is a common Unix feature that should remain possible to do with a simple 'sudo passwd' or optionally using the Users admin tool. This should always work, regardless of what policy we'd like to promote about the root account: here it is simply a bug. Please open a bug report on users-admin. Anyway, forbidding to set a root password should be done in a smarter way if we wanted to do so. Cheers -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-4 synaptic error
On su, 2008-02-03 at 09:05 -0600, Richard Mancusi wrote: [EMAIL PROTECTED]:~$ gksu update-manager warning: could not initiate dbus You don't need to run update-manager as root. It will switch to root (and ask for username then) when it needs it. This should at least fix the dbus initialization problem. (I don't know about the other problems, which may be unrelated.) -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-4 synaptic error
On Feb 3, 2008 9:13 AM, Lars Wirzenius [EMAIL PROTECTED] wrote: On su, 2008-02-03 at 09:05 -0600, Richard Mancusi wrote: [EMAIL PROTECTED]:~$ gksu update-manager warning: could not initiate dbus You don't need to run update-manager as root. It will switch to root (and ask for username then) when it needs it. This should at least fix the dbus initialization problem. (I don't know about the other problems, which may be unrelated.) That fixed the dbus problem. The password works, gui comes up showing the available updates, then back to a window with my initial error: -- An error occured The following details are provided: E:ERROR: could not create configuration directory /home/root/.synaptic - mkdir (2 No such file or directory) -- Terminal output = current dist not found in meta-release file -rich -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-4 synaptic error
Richard Mancusi wrote: On Feb 3, 2008 9:13 AM, Lars Wirzenius [EMAIL PROTECTED] wrote: On su, 2008-02-03 at 09:05 -0600, Richard Mancusi wrote: [EMAIL PROTECTED]:~$ gksu update-manager warning: could not initiate dbus You don't need to run update-manager as root. It will switch to root (and ask for username then) when it needs it. This should at least fix the dbus initialization problem. (I don't know about the other problems, which may be unrelated.) That fixed the dbus problem. The password works, gui comes up showing the available updates, then back to a window with my initial error: -- An error occured The following details are provided: E:ERROR: could not create configuration directory /home/root/.synaptic - mkdir (2 No such file or directory) -- Terminal output = current dist not found in meta-release file Could you run this and tell us what it shows: sudo -H bash -c 'echo $HOME' -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-4 synaptic error
On Feb 2, 2008 10:59 PM, scott [EMAIL PROTECTED] wrote: Try opening a terminal and typing 'gksu synaptic' or 'gksu update-manager'. Regards, Scott The administrative tasks password box comes up and accepts the password. Then update manager gui appears showing 32 updates. However the terminal shows: -- [EMAIL PROTECTED]:~$ gksu update-manager warning: could not initiate dbus Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put ORBIIOPIPv4=1 in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf current dist not found in meta-release file -- Terminal output from attempting to close the update manager: -- Traceback (most recent call last): File /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py, line 357, in lambda self.button_close.connect(clicked, lambda w: self.exit()) File /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py, line 830, in exit self.save_state() File /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py, line 838, in save_state gconf.VALUE_INT, gconf.VALUE_INT, x, y) gobject.GError: No database available to save your configuration: Unable to store a value at key '/apps/update-manager/window_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put ORBIIOPIPv4=1 in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf -- A crash report warning is issued - however it can't be reported: -- Problem in update-manager The problem cannot be reported: You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs: libgcc1, xinit, cpp-4.2, libffi4, libxml2, libsasl2-2, coreutils, libsasl2-modules, gcc-4.2-base, libstdc++6 -- This was a clean install in the manner I believed the average user would do. Use entire disk, allow Ubuntu to partition, everything very basic. hth -rich -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Fwd: Hardy Alpha-4 synaptic error
-- Forwarded message -- From: Richard Mancusi [EMAIL PROTECTED] Date: Feb 3, 2008 9:46 AM Subject: Re: Hardy Alpha-4 synaptic error To: Jason Crain [EMAIL PROTECTED] On Feb 3, 2008 9:35 AM, Jason Crain [EMAIL PROTECTED] wrote: Could you run this and tell us what it shows: sudo -H bash -c 'echo $HOME' /home/root -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-4 synaptic error
Richard Mancusi wrote: -- Forwarded message -- From: Richard Mancusi [EMAIL PROTECTED] Date: Feb 3, 2008 9:46 AM Subject: Re: Hardy Alpha-4 synaptic error To: Jason Crain [EMAIL PROTECTED] On Feb 3, 2008 9:35 AM, Jason Crain [EMAIL PROTECTED] wrote: Could you run this and tell us what it shows: sudo -H bash -c 'echo $HOME' /home/root That's pretty strange. Try running sudo usermod -d /root root to set root's home dir. If that doesn't work, you may have to look at root's .bash* or .profile files to see if $HOME is being set anywhere. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-4 synaptic error
On Feb 3, 2008 10:15 AM, Jason Crain [EMAIL PROTECTED] wrote: On Feb 3, 2008 9:35 AM, Jason Crain [EMAIL PROTECTED] wrote: Could you run this and tell us what it shows: sudo -H bash -c 'echo $HOME' /home/root That's pretty strange. Try running sudo usermod -d /root root to set root's home dir. If that doesn't work, you may have to look at root's .bash* or .profile files to see if $HOME is being set anywhere. Okay - that did it, sudo -H bash -c 'echo $HOME' now shows /root and I was able to do the updates and I added build-essential as a test via Synaptic Package Manager. Thank you for fixing my problem - I hope it is localized to me and not a Ubuntu problem. I know everything I did post install and may research this some more. tnx -rich -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-4 synaptic error
On Feb 3, 2008 10:32 AM, Richard Mancusi [EMAIL PROTECTED] wrote: On Feb 3, 2008 10:15 AM, Jason Crain [EMAIL PROTECTED] wrote: On Feb 3, 2008 9:35 AM, Jason Crain [EMAIL PROTECTED] wrote: Could you run this and tell us what it shows: sudo -H bash -c 'echo $HOME' /home/root That's pretty strange. Try running sudo usermod -d /root root to set root's home dir. If that doesn't work, you may have to look at root's .bash* or .profile files to see if $HOME is being set anywhere. Okay - that did it, sudo -H bash -c 'echo $HOME' now shows /root and I was able to do the updates and I added build-essential as a test via Synaptic Package Manager. Thank you for fixing my problem - I hope it is localized to me and not a Ubuntu problem. I know everything I did post install and may research this some more. tnx -rich Okay, I did another clean install and can repeat the problem. On a test system I always set a root password and allow root logon. Yes, I know that isn't a great idea, but it comes in handy on a test system. As soon as I set a root password in System/Administration/Users and Groups the root user Home directory moved from /root to /home/root. I guess it's a matter of opinion as to whether this is a bug. Ubuntu and common sense tells you to not set a root password. But if you are going to allow it, it should work correctly. I leave that to the developers. -rich -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Hardy Alpha-4 synaptic error
After a clean install (i386 desktop) I receive an error when attempting either: 1. System/Administration/Update Manager 2. System/Administration/Synaptic Package Manager An error occured The following details are provided: E:ERROR: could not create configuration directory /home/root/.synaptic - mkdir (2 No such file or directory) I do have a directory /root/.synaptic and obviously there is no such thing as /home/root where it appears to be looking. -rich -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-4 synaptic error
Try opening a terminal and typing 'gksu synaptic' or 'gksu update-manager'. Regards, Scott Richard Mancusi wrote: After a clean install (i386 desktop) I receive an error when attempting either: 1. System/Administration/Update Manager 2. System/Administration/Synaptic Package Manager An error occured The following details are provided: E:ERROR: could not create configuration directory /home/root/.synaptic - mkdir (2 No such file or directory) I do have a directory /root/.synaptic and obviously there is no such thing as /home/root where it appears to be looking. -rich signature.asc Description: OpenPGP digital signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
