I was going to request this change into Debian as well, but appears that
has already been attempted and was rejected due to "qtchooser is dead
upstream". https://salsa.debian.org/qt-kde-
team/qt/qtchooser/-/merge_requests/2
I wonder if the situation can be improved though as if you are trying to
@alexmurray, hey, I believe that commit was reverted later as it caused
a behavioural regression? The Github advisory
(https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx)
was changed to point to a different commit
Please find attached the debdiff for Ubuntu 21.10 impish. I have
performed some testing in a VM and built in a PPA.
** Attachment added: "Impish CVE debdiff"
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1957716/+attachment/5557881/+files/flatpak_impish_lp1957716.debdiff.gz
--
You
** Changed in: flatpak (Ubuntu Impish)
Status: New => In Progress
** Changed in: flatpak (Ubuntu Impish)
Assignee: (unassigned) => Andrew Hayzen (ahayzen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Links]
https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j (
CVE-2021-43860 )
https://security-tracker.debian.org/tracker/CVE-2021-43860
https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx (
CVE-2022-21682 )
** Description changed:
[Links]
https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j (
CVE-2021-43860 )
https://security-tracker.debian.org/tracker/CVE-2021-43860
https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx (
CVE-2022-21682 )
Note that Jammy now has 1.12.3-1 so is fixed.
** Summary changed:
- Update for CVE-2021-43860 and second github advisory
+ Update for CVE-2021-43860 and CVE-2022-21682
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21682
** Description changed:
[Links]
-
** Changed in: flatpak (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957716
Title:
Update for CVE-2021-43860 and second github advisory
To manage
Can someone with permission add impish, focal, bionic as affected
series? (hirsute i assume we can skip as it's about to EOL).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957716
Title:
Update
ntu)
Importance: Undecided
Assignee: Andrew Hayzen (ahayzen)
Status: In Progress
** Information type changed from Public to Public Security
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-43860
** Changed in: flatpak (Ubuntu)
Assignee: (unassigned) =>
Public bug reported:
Since the appdata changes in the recent upload, steam-installer doesn't
appear in the software stores.
Lets revert back to our downstream changes for now as this was an
experiment.
** Affects: steam (Ubuntu)
Importance: Undecided
Assignee: Andrew Hayzen (ahayzen
** Summary changed:
- Merge steam 1.0.0.73-1 from debian sid to ubuntu jammy
+ Merge steam 1.0.0.74-1 from debian sid to ubuntu jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951894
Title:
I've done some exploratory testing of Wayland/portal related tests from
the test plan on a Impish VM and things are working normally.
$ apt policy flatpak
flatpak:
Installed: 1.10.2-3ubuntu0.1
Candidate: 1.10.2-3ubuntu0.1
Version table:
*** 1.10.2-3ubuntu0.1 500
500
I've done some exploratory testing of Wayland/portal related tests from
the test plan on a Hirsute VM and things are working normally.
$ apt policy flatpak
flatpak:
Installed: 1.10.2-1ubuntu1.1
Candidate: 1.10.2-1ubuntu1.1
Version table:
*** 1.10.2-1ubuntu1.1 500
500
I've done some exploratory testing of Wayland/portal related tests from
the test plan on a Bionic VM and things are working normally.
$ apt policy flatpak
flatpak:
Installed: 1.0.9-0ubuntu0.4
Candidate: 1.0.9-0ubuntu0.4
Version table:
*** 1.0.9-0ubuntu0.4 500
500
I've done some exploratory testing of Wayland/portal related tests from
the test plan on a Focal VM and things are working normally.
$ apt policy flatpak
flatpak:
Installed: 1.6.5-0ubuntu0.4
Candidate: 1.6.5-0ubuntu0.4
Version table:
*** 1.6.5-0ubuntu0.4 500
500
Sorry, I somehow missed comment 11 and was thinking we were still
waiting for the libseccomp decision. I'll check the packages now!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946578
Title:
** Summary changed:
- Merge steam 1.0.0.72-2 from debian sid to ubuntu jammy
+ Merge steam 1.0.0.73-1 from debian sid to ubuntu jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951894
Title:
Public bug reported:
Debian has a newer version of steam packaging available, let's merge the
changes into the Ubuntu version to bring us back into sync.
** Affects: steam (Ubuntu)
Importance: Undecided
Assignee: Andrew Hayzen (ahayzen)
Status: In Progress
** Changed
Please find attached the debdiff for Ubuntu 18.04 bionic. I have
performed some testing in a VM and built in a PPA.
Note that for bionic (same as focal), we likely want to use the version
of libseccomp2 from bionic-updates ( 2.5.1-1ubuntu1~18.04.1) rather than
focal-security (
nchpad.net/ubuntu/+source/flatpak/+bug/1946578/+attachment/5534670/+files/focal_flatpak_1.6.5-0ubuntu0.3_to_1.6.5-0ubuntu0.4.debdiff.gz
** Changed in: flatpak (Ubuntu Bionic)
Status: New => In Progress
** Changed in: flatpak (Ubuntu Bionic)
Assignee: (unassigned) => Andrew Hayzen (a
)
Assignee: (unassigned) => Andrew Hayzen (ahayzen)
** Changed in: flatpak (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946578
Title:
So hirsute and impish have libseccomp 2.5.1, but focal and bionic have
2.4.3 in the security pocket and 2.5.1 in the updates pocket. I'm not
sure if there is procedure here to try and pull 2.5.1 of focal and
bionic into the security pocket with flatpak - if that is needed to
solve the security
Please find attached the debdiff for Ubuntu 21.04 hirsute. I have
performed some testing in a VM and built in a PPA.
Let me know if anything has been done incorrectly.
** Attachment added: "Hirsute CVE debdiff"
Please find attached the debdiff for Ubuntu 21.10 impish. I have
performed some testing in a VM and built in a PPA.
Let me know if anything has been done incorrectly.
** Attachment added: "Impish CVE debdiff"
** Changed in: flatpak (Ubuntu Impish)
Status: New => In Progress
** Changed in: flatpak (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: flatpak (Ubuntu Hirsute)
Assignee: (unassigned) => Andrew Hayzen (ahayzen)
--
You received this bug notification be
If someone has the permissions could they add bionic, focal, hirsute,
and impish as affected series ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946578
Title:
Placeholder for CVE-2021-41133
To
buses.
** Information type changed from Public to Public Security
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41133
** Changed in: flatpak (Ubuntu)
Assignee: (unassigned) => Andrew Hayzen (ahayzen)
--
You received this bug notification because you are a member
Public bug reported:
[Links]
https://github.com/flatpak/flatpak/security/advisories/GHSA-67h7-w3jq-vh4q
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995935
https://security-tracker.debian.org/tracker/CVE-2021-41133
** Affects: flatpak (Ubuntu)
Importance: Undecided
Status: New
Reported an issue upstream https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4626
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4626
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4626
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
What Happened
- 1) Installed the package gnome-session (ensuring it is the latest version)
- 2) At gdm picked "GNOME" and not "Ubuntu"
- 3) Reboot and login to the desktop
- 4) Notice that initially the activity overview is shown (correctly)
- 5) Then within a second or
OK, I've figured out what is going on. If you are on the activities
overview and you change the resolution of the VM it then goes back to
the desktop.
I'll see if there are any bugs upstream as it happens on Fedora rawhide
as well ...
** Summary changed:
- gnome-session impish 40 update login
Public bug reported:
What Happened
1) Installed the package gnome-session (ensuring it is the latest version)
2) At gdm picked "GNOME" and not "Ubuntu"
3) Reboot and login to the desktop
4) Notice that initially the activity overview is shown (correctly)
5) Then within a second or so, something
Find attached a debdiff for Ubuntu impish which takes 1.10.2-3 to
1.10.3-0ubuntu1.
This is also available in a PPA here
https://launchpad.net/~ahayzen/+archive/ubuntu/flatpak-manual-
uploads-1-10-3-clean-1-impish
** Attachment added: "flatpak_1.10.2-3.to.1.10.3-0ubuntu1.debdiff.gz"
** Description changed:
- Placeholder
+ There is an upstream update to the 1.10 series, this allows us to drop
+ all patches as they are applied upstream.
+
+ Note we cannot sync from Debian as they have moved unstable to the pre-
+ release 1.11 series temporarily.
+
+ [Upstream changes]
+ This
Public bug reported:
Placeholder
** Affects: flatpak (Ubuntu)
Importance: Undecided
Assignee: Andrew Hayzen (ahayzen)
Status: In Progress
** Changed in: flatpak (Ubuntu)
Status: New => In Progress
** Changed in: flatpak (Ubuntu)
Assignee: (unassigned) =>
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This does seem curious, did you solve the issue? were you able to
navigate to the download manifest via your web browser at the time of
the error?
Looking at later versions of the steam debian package, "curl" has
).
** Affects: steam (Ubuntu)
Importance: Undecided
Assignee: Andrew Hayzen (ahayzen)
Status: In Progress
** Changed in: steam (Ubuntu)
Assignee: (unassigned) => Andrew Hayzen (ahayzen)
** Changed in: steam (Ubuntu)
Status: New => In Progress
--
You received th
tl;dr; Flatpak currently considers remotes as trusted, so after you have
added one with a password at system level, you don't need a password to
install apps for that remote.
I don't about how polkit rules work, but this is just a comment
describing what happens from a user perspective with
I've also done some exploratory testing of .desktop icon related tests
from the test plan on a Bionic VM and things are working normally.
$ apt policy flatpak
flatpak:
Installed: 1.0.9-0ubuntu0.3
Candidate: 1.0.9-0ubuntu0.3
Version table:
*** 1.0.9-0ubuntu0.3 500
500
@Steve Beattie, was there any progress on this or anything I can do to
help ? Or is it just stuck in a queue of items to be reviewed? :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918482
Title:
Thanks for reviewing these updates!
I've done some exploratory testing of .desktop icon related tests from
the test plan on a Focal VM and things are working normally.
$ apt policy flatpak
flatpak:
Installed: 1.6.5-0ubuntu0.3
Candidate: 1.6.5-0ubuntu0.3
Version table:
*** 1.6.5-0ubuntu0.3
Upstream bug is here https://github.com/AyatanaIndicators/ayatana-
indicator-keyboard/issues/5
** Bug watch added:
github.com/AyatanaIndicators/ayatana-indicator-keyboard/issues #5
https://github.com/AyatanaIndicators/ayatana-indicator-keyboard/issues/5
--
You received this bug notification
Reported a bug upstream with some analysis of the issue.
https://github.com/mate-desktop/mate-control-center/issues/640
** Bug watch added: github.com/mate-desktop/mate-control-center/issues #640
https://github.com/mate-desktop/mate-control-center/issues/640
--
You received this bug
Hirsute now contains 1.10.2-1 with the fix, so I am marking it as fixed
released.
** Changed in: flatpak (Ubuntu)
Status: In Progress => Fix Released
** Description changed:
[Links]
https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp
qpp-1.patch" to "CVE-2021-21381-1.patch"
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-21381
** Changed in: flatpak (Ubuntu Bionic)
Assignee: (unassigned) => Andrew Hayzen (ahayzen)
** Changed in: flatpak (Ubuntu Focal)
Assignee: (unassigned) => A
** Description changed:
[Links]
https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp
https://github.com/flatpak/flatpak/pull/4156
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859
[Impact]
Versions in Ubuntu right now:
Hirsute: 1.10.1-4
Groovy:
If someone has the permissions could they add bionic, focal, and groovy
as affected series ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918482
Title:
Update for GHSA-xgh4-387p-hqpp
To manage
This is the bionic debdiff.
** Description changed:
- Patches and description coming soon ! I need this to generate a LP bug
- number :-)
+ [Links]
+ https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp
+ https://github.com/flatpak/flatpak/pull/4156
+
+ [Impact]
+ Versions
So we do not have a CVE yet, I believe one will be auto assigned via
github at some point (I don't know how long this takes :-) ).
I realised there is a typo in the bionic changelog "- GHSA-xgh4-387p-
hqpp-1" should be "- GHSA-xgh4-387p-hqpp". But once a CVE is available
this line will need to
This is the focal debdiff.
** Attachment added: "[focal]
flatpak_1.6.5-0ubuntu0.2_to_flatpak_1.6.5-0ubuntu0.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+attachment/5475503/+files/flatpak_1.6.5-0ubuntu0.2_to_flatpak_1.6.5-0ubuntu0.3.debdiff.gz
--
You received
This is the groovy debdiff.
** Attachment added: "[groovy]
flatpak_1.8.2-1ubuntu0.1_to_flatpak_1.8.2-1ubuntu0.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+attachment/5475504/+files/flatpak_1.8.2-1ubuntu0.1_to_flatpak_1.8.2-1ubuntu0.2.debdiff.gz
--
You received
Public bug reported:
Patches and description coming soon ! I need this to generate a LP bug
number :-)
** Affects: flatpak (Ubuntu)
Importance: Undecided
Assignee: Andrew Hayzen (ahayzen)
Status: In Progress
** Changed in: flatpak (Ubuntu)
Assignee: (unassigned
@jik, I think that you need the package gnome-remote-desktop, this has a
MIR request in bug 1802614. And then another package will need to
recommend it to have it installed by default, you can follow this on the
Trello board here https://trello.com/c/NnUq5bHv/15-mir-gnome-remote-
** Description changed:
- Placeholder as we merge the latest changes from Debian sid to Ubuntu
- hirsute.
+ Debian has a newer version of steam packaging available, let's merge the
+ changes into the Ubuntu version to bring us back into sync.
--
You received this bug notification because you
@Paulo, was there any progress on this or anything you need help with ?
I've posted debdiffs for focal and groovy. Sounds like you have a diff
for bionic.
Let me know if there is anything I can do to help this move to the next
step :-)
--
You received this bug notification because you are a
Public bug reported:
Placeholder as we merge the latest changes from Debian sid to Ubuntu
hirsute.
** Affects: steam (Ubuntu)
Importance: Undecided
Assignee: Andrew Hayzen (ahayzen)
Status: In Progress
** Changed in: steam (Ubuntu)
Assignee: (unassigned) => Andrew Hay
Please find attached the debdiff for Ubuntu 20.10 groovy. This includes
a similar set of patches to the focal set and has been picked from
between the 1.8.4 and 1.8.5 tags.
Let me know if anything has been done incorrectly or missed any commits.
I will leave it up to the security team to decide
@Kleber I have installed the focal hwe kernel from proposed (as seen
below). So far when A/B testing this kernel it is working correctly :-)
I will continue running this kernel and report any issues I have.
Also note that I have been continuously running the test kernel (from
comment 22) since
@Paulo, Thanks !
BTW smcv just pointed out two more potential patches that could be
included in the focal 1.6 patch, these are only for users that use
setuid on the bubblewrap binary though (users who disable user
namespaces - like Debian). It would be up to us if we want to include
them. See
1.8.5 has landed in hirsute now, so marking hirsute as fixed released.
** Changed in: flatpak (Ubuntu Hirsute)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Marcelo So far it looks good :-) It passes the "fio" command test when
A/B testing between a known bad kernel and this new kernel. I will
continue running it on this machine over the weekend to ensure longer
usage doesn't have any remaining issues - but looks like it resolves the
issue so far :-D
Thanks! I'll take a look :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910866
Title:
nvme drive fails after some time
To manage notifications about this bug go to:
@kaihengfeng Thanks for the quick response! bug 1908555 linked there
only lists groovy as a target series, I hope that this will also be
applied to the focal HWE kernel :-)
Also I am happy to test any kernel in a -proposed channel or PPA to
confirm it fixes the issue if that helps :-)
--
You
@kaihengfeng
So v5.7 was fine and after many reboots it has been found that this
commit below introduced the issue.
Do I also need to find when the issue was resolved ? (between v5.8-rc1
and v5.9.10) or is this information enough ?
54b2fcee1db041a83b52b51752dade6090cf952f is the first bad
** Changed in: flatpak (Ubuntu Focal)
Status: New => In Progress
** Changed in: flatpak (Ubuntu Focal)
Assignee: (unassigned) => Andrew Hayzen (ahayzen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If anyone has the permission to propose this bug for the series, bionic,
focal, and groovy that would be useful :-)
** Description changed:
+ [Links]
+
+ Upstream Advisory:
https://github.com/flatpak/flatpak/security/advisories/GHSA-4ppf-fxf6-vxg2
+ Debian:
Please find attached the debdiff for Ubuntu 20.04 focal. I have tested
this using the manual test plan in a VM and built in a PPA.
Let me know if anything has been done incorrectly.
** Summary changed:
- Placeholder for ghsa-4ppf-fxf6-vxg2
+ Update for ghsa-4ppf-fxf6-vxg2
** Description
Also note that hirsute now has 1.8.5 in hirsute-proposed (which contains
the fix), although it looks like s390x has failed in the tests - I
wonder if a retest will make it pass or if it is a genuine failure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-21261
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911473
Title:
Placeholder for ghsa-4ppf-fxf6-vxg2
To manage notifications
@Paulo
hirsute - can sync 1.8.5 from debian sid which contains the fix.
groovy - is a tricky one as it is one step behind in terms of microreleases
(1.8.3) so either needs backporting or bumping to 1.8.5
focal - upstream have created a branch for me with relevant patches that allow
it to build,
@Paulo, Hi yes there is no CVE yet, but I believe upstream have
requested one via github (I can see it says one has been requested). I
will also try to submit debdiffs for Ubuntu 20.04 shortly (hopefully
later tonight if testing goes well).
--
You received this bug notification because you are a
This is now public.
** Information type changed from Private Security to Public Security
** Description changed:
Placeholder for ghsa-4ppf-fxf6-vxg2 as I prepare the debdiffs.
This issue will be made public I believe on 14/01/2021 daytime CET.
-
[Impact]
Versions in Ubuntu
And the bisect between 5.4.78 (good) and 5.8.18 (bad).
The following results with the mainline kernel
v5.8.18/FAIL
v5.8.4/ FAIL
v5.8-rc5/ FAIL
v5.8-rc1/ FAIL
v5.7.19/PASS
v5.7.18/PASS
v5.7.16/
So bisecting between 5.8.18 (bad) and 5.11-rc3 (good).
The following results with the mainline kernel
v5.11-rc3/ PASS
v5.9.12/PASS
v5.9.10/PASS
v5.9.9/ MISSING
v5.9.8/ FAIL (could not boot long enough for full test)
OK, so using https://people.canonical.com/~kernel/info/kernel-version-
map.html that states that Ubuntu kernel 5.8.0-36.40~20.04.1 matches
mainline version 5.8.18. I have installed 5.8.18 and it fails ! So it is
not the Ubuntu patches.
Ubuntu Kernels:
linux-image-5.4.0-59-generic: PASS
@kaihengfeng
I have found that running the command "fio --name=basic
--directory=/path/to/empty/directory --size=1G --rw=randrw --numjobs=4
--loops=5" runs fine on linux-image-5.4.0-59-generic but when trying
with linux-image-5.8.0-36-generic it would freeze the system in the
"Laying out IO file"
FYI I have captured the `sudo lspci -vv` output on the kernel 5.8
*before* the issue here https://pastebin.ubuntu.com/p/GtZyTWzKTd/ it is
subtly different to the 5.4 kernel (which has not had the issue) in case
that mattered.
I was also able to reproduce the issue again by causing high disk I/O,
Note for me it is happening quite rapidly (sometimes after 5-10 minutes)
of high disk load. Eg the first times it happened when apt was running
update-grub and then when pip3 install was running. Then to capture the
logs above i started a `find /` and `find ~` at the same time and this
was enough
@kairhengfeng Yes this is a regression after the upgrade from 5.4 to
5.8. After the upgrade I had it multiple times and now I have switched
back to 5.4 my machine is stable again.
I do not think I can run `lspci -vv` *after* the issue happens, as my
NVMe drive goes read-only, so all commands
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
>From what I can see libudev1 has been a depends for a while in the
Debian and Ubuntu Steam packaging and on my system Steam has correctly
installed libudev1:i386. Therefore I am going to mark this bug as fixed
*** This bug is a duplicate of bug 1584298 ***
https://bugs.launchpad.net/bugs/1584298
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1584298, so it is being marked as such. Please
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This sounds like the steam binary itself has crashed and is not related
to the packaging. I am going to mark the bug as incomplete, please
provide more details to the crash and confirm that it still happens on
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I think this is likely to be due to the debconf question for the steam
license question not being answered correctly, this was dropped in the
steam package version 1:1.0.0.54+repack-2ubuntu4 as not all software
*** This bug is a duplicate of bug 1631980 ***
https://bugs.launchpad.net/bugs/1631980
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1631980, so it is being marked as such. Please
*** This bug is a duplicate of bug 1631980 ***
https://bugs.launchpad.net/bugs/1631980
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1631980, so it is being marked as such. Please
*** This bug is a duplicate of bug 1255794 ***
https://bugs.launchpad.net/bugs/1255794
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1255794, so it is being marked as such. Please
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This issue is likely similar to others which are related to the steam
license question not being answered, this was dropped in the steam
package version 1:1.0.0.54+repack-2ubuntu4 as not all software centre's
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The libtxc-dxtn-s2tc0 has been removed from later versions of Ubuntu and
it has been removed as a dependency in the Ubuntu steam packaging since
1:1.0.0.67-2ubuntu1 (Ubuntu 21.04). Therefore I am marking this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The package libtxc-dxtn-s2tc has been removed from later versions of
Ubuntu, therefore I am going to mark this bug as invalid for Steam.
** Changed in: steam (Ubuntu)
Status: Confirmed => Invalid
--
You
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I can reproduce this issue, but I think that is potentially a security
feature of the gnome-shell-extension-desktop-icons. As if you navigate
to the folder in Nautilus, then select open, it allows for running the
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
mesa-vulkan-drivers was added as a recommends for Debian packaging as of
version 1.0.0.56-2 and therefore to the Ubuntu packaging as of version
1:1.0.0.61-2ubuntu1 (Ubuntu 20.04).
For Nvidia the Ubuntu package
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The Steam package has been updated in future releases of Ubuntu.
The "steam-launcher" package and
http://repo.steampowered.com/steam/presice repository you mention as
having installed come from Valve themselves
*** This bug is a duplicate of bug 1273027 ***
https://bugs.launchpad.net/bugs/1273027
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The "subprocess new pre-installation script returned error exit status
30" that apport has reported here has been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This bug appears that it is an issue with the steam binary itself and
not with the Ubuntu packaging, I have not been able to locate anything
that attempts to connect to the network.
This issue would be better
*** This bug is a duplicate of bug 1273027 ***
https://bugs.launchpad.net/bugs/1273027
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Looking at dpkg terminal this appears to have failed due to the license
agreement popup, which has been solved in bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On Ubuntu 20.04 I am not able to reproduce this issue, therefore I am
going to mark this as incomplete. Please comment if you are still having
this issue.
** Changed in: steam (Ubuntu)
Status: New =>
*** This bug is a duplicate of bug 1273027 ***
https://bugs.launchpad.net/bugs/1273027
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1273027, so it is being marked as such. Please
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
As per the Debian changelog entry below this has been fixed in the
upstream Debian packaging. And since Ubuntu package version
1:1.0.0.61-2ubuntu1 (Ubuntu 20.04) those changes have been present in
the Ubuntu
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
All of these bugs appear to happen when steam has failed to install
correctly (due to the license agreement question being declined) and
then the user attempting to remove/upgrade the broken package.
As the steam
1 - 100 of 716 matches
Mail list logo
