Your message dated Wed, 24 May 2006 12:42:34 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368674: udev: /dev/fuse is not created root:fuse
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: udev
Version: 0.092-1

Hi,

I'm experiencing old #334439 (udev: /dev/fuse node is created with wrong
group owner) with the current version of udev:

  % grep fuse /etc/udev/rules.d/020_permissions.rules
  KERNEL=="fuse",                                 GROUP="fuse"

  % ls -l /dev/fuse
  ls: /dev/fuse: No such file or directory

  % sudo modprobe fuse

  % ls -l /dev/fuse
  crw-rw---- 1 root root 10, 229 May 24 02:25 /dev/fuse

Thanks,

-- 
Adeodato Simó                                     dato at net.com.org.es
Debian Developer                                  adeodato at debian.org
 
                                   Listening to: Jay-Jay Johanson - Kate



--- End Message ---
--- Begin Message ---
* Marco d'Itri [Wed, 24 May 2006 09:31:28 +0200]:

> On May 24, Adeodato Simó <[EMAIL PROTECTED]> wrote:

> > I'm experiencing old #334439 (udev: /dev/fuse node is created with wrong
> > group owner) with the current version of udev:

> >   % grep fuse /etc/udev/rules.d/020_permissions.rules
> >   KERNEL=="fuse",                                 GROUP="fuse"
> So it's obviously not old #334439.

> Please report the output of udevtest for the /dev/fuse $DEVPATH.
> Also, check daemon.log for errors.

It works today. Now I remember I installed fuse-utils yesterday, which
means the fuse group did not still exist when udev started. Restarting
udev (or rebooting the system, obviously) fixes the issue.

This behavior seems like the only one possible, so closing the bug.

-- 
Adeodato Simó                                     dato at net.com.org.es
Debian Developer                                  adeodato at debian.org
 
Que no te vendan amor sin espinas
                -- Joaquín Sabina, Noches de boda


--- End Message ---

Reply via email to