[Bug 1978310] Re: jammy, noble: Installing fuse package removes other important packages
Jeremy Bícha
1978310 at bugs.launchpad.net
Thu Sep 12 14:51:03 UTC 2024
** Description changed:
- I installed the `fuse` package in my fresh Ubuntu 22.04 installation and
- later started getting weird behavior in some applications (such as
- Chrome). I believe this might be related, as installing `fuse` caused
- many packages to be removed.
+ Impact
+ ------
+
+ Test Case
+ ---------
+
+ What Could Go Wrong
+ -------------------
+
+ Other Info
+ ----------
+ This is being fixed by adding a transitional package fuse built by the fuse3 source package. We are doing it in the fuse3 source package because we need to also remove the Conflicts and change the Breaks to a versioned Breaks so since we need to update fuse3 anyway, there doesn't seem to be much benefit to also uploading the fuse source package.
+
+ On the other hand, Launchpad will not allow the fuse source package to
+ be updated if it still builds the out-of-date fuse binary package.
+ Therefore, I think I'll just upload fuse removing the fuse binary
+ package but we could set it as blocked in proposed. That way, it is more
+ convenient in case someone needs to do a Security update or SRU later.
+
+ This still seems like it would be smoother than requiring 2 source
+ packages to be uploaded to fix the SRU and having to deal with phasing
+ etc.
+
+ Original Bug Report
+ -------------------
+ I installed the `fuse` package in my fresh Ubuntu 22.04 installation and later started getting weird behavior in some applications (such as Chrome). I believe this might be related, as installing `fuse` caused many packages to be removed.
This was reported by others here:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148
-
apt log shows this:
`
Start-Date: 2022-06-04 10:31:38
Commandline: apt install fuse
Requested-By: thomas (1000)
Install: libfuse2:amd64 (2.9.9-5ubuntu3, automatic), fuse:amd64 (2.9.9-5ubuntu3)
Remove: ntfs-3g:amd64 (1:2021.8.22-3ubuntu1), xdg-desktop-portal-gtk:amd64 (1.14.0-1build1), xdg-desktop-portal-gnome:amd64 (42.1-0ubuntu1), gvfs-fuse:amd64 (1.48.1-4), ubuntu-desktop:amd64 (1.481), gnome-shell-
extension-desktop-icons-ng:amd64 (43-2), fuse3:amd64 (3.10.5-1build1), ubuntu-desktop-minimal:amd64 (1.481), xdg-desktop-portal:amd64 (1.14.3-0ubuntu2.22.04.1)
End-Date: 2022-06-04 10:31:57
`
So, installing `fuse` removes packages such as `ubuntu-desktop` and
`xdg-desktop-portal`, which (I believe) are important packages and
should not be removed.
System information:
Ubuntu 22.04 running on amd64 hardware
** Description changed:
Impact
------
Test Case
---------
What Could Go Wrong
-------------------
Other Info
----------
This is being fixed by adding a transitional package fuse built by the fuse3 source package. We are doing it in the fuse3 source package because we need to also remove the Conflicts and change the Breaks to a versioned Breaks so since we need to update fuse3 anyway, there doesn't seem to be much benefit to also uploading the fuse source package.
On the other hand, Launchpad will not allow the fuse source package to
be updated if it still builds the out-of-date fuse binary package.
Therefore, I think I'll just upload fuse removing the fuse binary
package but we could set it as blocked in proposed. That way, it is more
convenient in case someone needs to do a Security update or SRU later.
+ I'll use a separate LP bug to set the block-proposed tag just for source
+ package fuse.
This still seems like it would be smoother than requiring 2 source
packages to be uploaded to fix the SRU and having to deal with phasing
etc.
Original Bug Report
-------------------
I installed the `fuse` package in my fresh Ubuntu 22.04 installation and later started getting weird behavior in some applications (such as Chrome). I believe this might be related, as installing `fuse` caused many packages to be removed.
This was reported by others here:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148
apt log shows this:
`
Start-Date: 2022-06-04 10:31:38
Commandline: apt install fuse
Requested-By: thomas (1000)
Install: libfuse2:amd64 (2.9.9-5ubuntu3, automatic), fuse:amd64 (2.9.9-5ubuntu3)
Remove: ntfs-3g:amd64 (1:2021.8.22-3ubuntu1), xdg-desktop-portal-gtk:amd64 (1.14.0-1build1), xdg-desktop-portal-gnome:amd64 (42.1-0ubuntu1), gvfs-fuse:amd64 (1.48.1-4), ubuntu-desktop:amd64 (1.481), gnome-shell-
extension-desktop-icons-ng:amd64 (43-2), fuse3:amd64 (3.10.5-1build1), ubuntu-desktop-minimal:amd64 (1.481), xdg-desktop-portal:amd64 (1.14.3-0ubuntu2.22.04.1)
End-Date: 2022-06-04 10:31:57
`
So, installing `fuse` removes packages such as `ubuntu-desktop` and
`xdg-desktop-portal`, which (I believe) are important packages and
should not be removed.
System information:
Ubuntu 22.04 running on amd64 hardware
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to fuse in Ubuntu.
https://bugs.launchpad.net/bugs/1978310
Title:
jammy,noble: Installing fuse package removes other important packages
Status in fuse package in Ubuntu:
Triaged
Status in fuse3 package in Ubuntu:
Fix Committed
Status in fuse source package in Jammy:
Won't Fix
Status in fuse3 source package in Jammy:
Triaged
Status in fuse source package in Noble:
Won't Fix
Status in fuse3 source package in Noble:
Triaged
Bug description:
Impact
------
Test Case
---------
What Could Go Wrong
-------------------
Other Info
----------
This is being fixed by adding a transitional package fuse built by the fuse3 source package. We are doing it in the fuse3 source package because we need to also remove the Conflicts and change the Breaks to a versioned Breaks so since we need to update fuse3 anyway, there doesn't seem to be much benefit to also uploading the fuse source package.
On the other hand, Launchpad will not allow the fuse source package to
be updated if it still builds the out-of-date fuse binary package.
Therefore, I think I'll just upload fuse removing the fuse binary
package but we could set it as blocked in proposed. That way, it is
more convenient in case someone needs to do a Security update or SRU
later. I'll use a separate LP bug to set the block-proposed tag just
for source package fuse.
This still seems like it would be smoother than requiring 2 source
packages to be uploaded to fix the SRU and having to deal with phasing
etc.
Original Bug Report
-------------------
I installed the `fuse` package in my fresh Ubuntu 22.04 installation and later started getting weird behavior in some applications (such as Chrome). I believe this might be related, as installing `fuse` caused many packages to be removed.
This was reported by others here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1970148
apt log shows this:
`
Start-Date: 2022-06-04 10:31:38
Commandline: apt install fuse
Requested-By: thomas (1000)
Install: libfuse2:amd64 (2.9.9-5ubuntu3, automatic), fuse:amd64 (2.9.9-5ubuntu3)
Remove: ntfs-3g:amd64 (1:2021.8.22-3ubuntu1), xdg-desktop-portal-gtk:amd64 (1.14.0-1build1), xdg-desktop-portal-gnome:amd64 (42.1-0ubuntu1), gvfs-fuse:amd64 (1.48.1-4), ubuntu-desktop:amd64 (1.481), gnome-shell-
extension-desktop-icons-ng:amd64 (43-2), fuse3:amd64 (3.10.5-1build1), ubuntu-desktop-minimal:amd64 (1.481), xdg-desktop-portal:amd64 (1.14.3-0ubuntu2.22.04.1)
End-Date: 2022-06-04 10:31:57
`
So, installing `fuse` removes packages such as `ubuntu-desktop` and
`xdg-desktop-portal`, which (I believe) are important packages and
should not be removed.
System information:
Ubuntu 22.04 running on amd64 hardware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1978310/+subscriptions
More information about the foundations-bugs
mailing list