Patch rejected, since a better patch is already in Ubuntu and this bug
is already marked "Fix Released"
--
40-permissions.rules includes non-existent groups
https://bugs.launchpad.net/bugs/38203
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscrib
Patch to udev-108 to remove references from rules.d/40-permissions.rules.
Please apply this minorly trivial fix to udev.
Seriously, why has this bug been in this state for a year? If I'm making a
change to several thousand machines so that they boot correctly, it leaves the
realm of 'trivial to
** Changed in: udev (Ubuntu)
Status: In Progress => Fix Released
--
40-permissions.rules includes non-existent groups
https://bugs.launchpad.net/bugs/38203
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing lis
** Changed in: udev (Ubuntu)
Status: Confirmed => In Progress
--
40-permissions.rules includes non-existent groups
https://bugs.launchpad.net/bugs/38203
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
u
Still exists in Feisty Beta 1...please..
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Still exists in Feisty Herd 5... this is an incredibly annoying bug for
LDAP users
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: upstart (Ubuntu)
Status: Unconfirmed => Rejected
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This problem is still in Feisty Herd 3.
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This is probably related
https://launchpad.net/distros/ubuntu/+source/libnss-ldap/+bug/51315
Creating system group 'nvram' manually seems to work.
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
No, it fixes the symptoms. The problem (referenced local groups are not
present) still exists.
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Torsten's config change definitely fixes the problem.
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
as matt mossholder wrote me:
just activating
# soft: return immediately on server failure
bind_policy soft
in /etc/libnss-ldap.conf
fixed the timeout problem
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Ignore my comment about #63131 -- that was a red herring.
I do note that the scanner group was created already for me by the edgy
live install CD, but not the nvram group. Commenting out the nvram
entry in that file prevented the long timeout.
On a tangent: it looks like the "cycles" in timeout
It looks like this will be fixed once the sync mentioned in #63131:goes
through.
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This one also bit me. I thought I had set up LDAP incorrectly, because
the timeout values seemed to be cycling (in retrospect, this is probably
due to having more than one nonexistent group).
** Bug 64307 has been marked a duplicate of this bug
--
40-permissions.rules includes non-existent grou
Markus, forgot your Question: the latest Updates where/are applied and
in case of Edgy: yes - since applying the Update 2 days ago this little thing
lets me wait so long to start Edgy ;)
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing
hmm, if i would know which groups udev would like to look up it may be
a simple fix, wouldn't it?
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Yes, it's annoying. I'm not sure, but I think it's gotten worse lately. Was
there an upgrade of libnss?
Well, I was able to tweak ldap timeouts by using hard to find settings in
/etc/libnss-ldap.conf:
nss_reconnect_tries
nss_reconnect_sleeptime
nss_reconnect_maxsleeptime
nss_reconnect_maxconntrie
On 21:24 Do 05 Okt, Scott James Remnant wrote:
> ** Bug 64195 has been marked a duplicate of this bug
>
> --
> 40-permissions.rules includes non-existent groups
> https://launchpad.net/bugs/38203
maybe this bug has now more priority then LOW 'cause the
boot process now takes up to 2 and a half m
** Bug 64195 has been marked a duplicate of this bug
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug 51340 has been marked a duplicate of this bug
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
21 matches
Mail list logo
