fuse-utils 2.5.3-2.1ubuntu3 installation (edgy) crashes in post installation phase

I have a similar problem with the latest update. It tries to reload the module, but I have my own kernel, and fuse in my case _is not a module_.

Question: Should packages depend of a particular setup of the kernel, like this? I really don't think so. And it _really shouldn't fail the update process making other package updates messy_.

This is from now on critical, buggy apps ok, but stop messing up the package system.

fuse (2.5.3-2.1ubuntu4) edgy; urgency=low
 .
   * remove the debian modprobe code and the useless udev reload from
     fuse-utils.postinst. it hangs the install if fuse is already
     loaded (closes malone #65235)

since a standalone modprobe will fail gracefully if the module isnt available, calling modprobe wont do any harm from the postinst ... the original debian code forced modprobe through the --first-time option to fail completely if it couldnt be executed (if there is no module or its already loaded)

I have no idea what you're talking about. There's still an issue, for each update, fuse-utils breaks.

well, i tested on 6 different systems with three different arches here, obviously it works fine ...

Preparing to replace fuse-utils 2.4.2-0ubuntu3 (using .../fuse-utils_2.5.3-2.1ubuntu4_i386.deb) ...
Unpacking replacement fuse-utils ...
Setting up fuse-utils (2.5.3-2.1ubuntu4) ...
creating fuse device...
udev active, devices will be created in /dev/.static/dev/
creating fuse group...
The group `fuse' already exists as a system group. Exiting...
An override for "/usr/bin/fusermount" already exists, aborting
ogra@edubuntu:~$

$LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 sudo apt-get install fuse-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  fuse-module
The following NEW packages will be installed:
  fuse-utils
0 upgraded, 1 newly installed, 0 to remove and 11 not upgraded.
Need to get 0B/56.6kB of archives.
After unpacking 180kB of additional disk space will be used.
Selecting previously deselected package fuse-utils.
(Reading database ... 198071 files and directories currently installed.)
Unpacking fuse-utils (from .../fuse-utils_2.5.3-2.1ubuntu4_i386.deb) ...
Setting up fuse-utils (2.5.3-2.1ubuntu4) ...
creating fuse device...
udev active, devices will be created in /dev/.static/dev/
creating fuse group...
The group `fuse' already exists as a system group. Exiting...
FATAL: Module fuse not found.
dpkg: error processing fuse-utils (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 fuse-utils
E: Sub-process /usr/bin/dpkg returned an error code (1)

ping

Does the maintainer of this package somehow believe that this issue is fixed?

On Sunday 29 October 2006 16:39, Gustaf wrote:
> Does the maintainer of this package somehow believe that this issue is
> fixed?

The current one seems to work:

$sudo apt-get install fuse-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package fuse-utils is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
buz@buznote:~$ sudo apt-get install fuse-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  fuse-utils
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 56.6kB of archives.
After unpacking 180kB of additional disk space will be used.
Get:1 http://ch.archive.ubuntu.com edgy/main fuse-utils 2.5.3-2.1ubuntu4
[56.6kB]
Fetched 56.6kB in 0s (138kB/s)
Selecting previously deselected package fuse-utils.
(Reading database ... 158447 files and directories currently installed.)
Unpacking fuse-utils (from .../fuse-utils_2.5.3-2.1ubuntu4_i386.deb) ...
Setting up fuse-utils (2.5.3-2.1ubuntu4) ...
creating fuse device...
udev active, devices will be created in /dev/.static/dev/
creating fuse group...
Adding group `fuse' (115)...
Done.

$ sudo apt-get remove fuse-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
  fuse-utils
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  fuse-utils
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 180kB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 158464 files and directories currently installed.)
Removing fuse-utils ...
Removing group `fuse'...
done.
$ sudo apt-get install fuse-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  fuse-utils
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/56.6kB of archives.
After unpacking 180kB of additional disk space will be used.
Selecting previously deselected package fuse-utils.
(Reading database ... 158448 files and directories currently installed.)
Unpacking fuse-utils (from .../fuse-utils_2.5.3-2.1ubuntu4_i386.deb) ...
Setting up fuse-utils (2.5.3-2.1ubuntu4) ...
creating fuse device...
udev active, devices will be created in /dev/.static/dev/
creating fuse group...
Adding group `fuse' (115)...
Done.

not for statically compiled kernels without module support it seems ... i'll prepare something for the edgy-updates repo soon...

I do have module support, however fuse is statically compiled.
I don't think a package requiring a certain kernel driver/code should require it to be compiled in a specific fashion - module vs static. It should detect it through /proc or whatever. This is usually the case, but with fuse-utils it's not.
Thanks for looking into it.

I have the same problem with fuse-utils 2.5.3-2.1ubuntu4. I also have my own kernel with fuse support compiled in statically, and so obviously no fuse module.
Is there any progress on this bug?