automount key .hidden not found in map source(s).
Using autofs-ldap, auto.master etc in LDAP.
User can access auto mounts via terminal fine. Nautilus just sits there
doing nothing.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
automount key .hidden not found in map source(s).
Using autofs-ldap, auto.master etc in LDAP.
User can access auto mounts via terminal fine. Nautilus just sits there
doing nothing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Using nut-client from precise, missing init script for running upsmon.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/920844
Title:
nut-client is missing /etc/init.d/ups-monitor for
Using nut-client from precise, missing init script for running upsmon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920844
Title:
nut-client is missing /etc/init.d/ups-monitor for MODE=netclient
1. Log in setting fluxbox as window manager, right click on desktop and open
Chrome or firefox, download file, save to location, have nautilus starts. Right
click on desktop to open some other program, get context menu for creating new
folder etc
2. Expected behavior, right clicking on desktop
In reference to LDAP, it probably is the same bug, if you're using
autofs-ldap which is part of the same source package then you can have
you auto.master in LDAP, so you probably don't have openldap running
locally, but require the network to be working before starting autofs to
do ldap queries to
In reference to LDAP, it probably is the same bug, if you're using
autofs-ldap which is part of the same source package then you can have
you auto.master in LDAP, so you probably don't have openldap running
locally, but require the network to be working before starting autofs to
do ldap queries to
I am experiencing a similar problem. Same error messages. Recently
upgraded from 8.04 LTS to 10.04 LTS. Although it is an intermittent
problem and I cannot pin down why it sometimes works or doesn't work.
When getting these error messages none of the menu bars appear. When
there's not a problem
