[Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"

2022-01-12 Thread Launchpad Bug Tracker
This bug was fixed in the package gvfs - 1.48.1-2ubuntu5

---
gvfs (1.48.1-2ubuntu5) jammy; urgency=medium

  * debian/patches/new-meson-build.patch:
- don't use positional arguments in the 18n merge function, fix the
  build with the new meson version

 -- Sebastien Bacher   Wed, 12 Jan 2022 16:35:28
+0100

** Changed in: gvfs (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1956949

Title:
  CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1945061] Re: gdm3 crashed with SIGSEGV in ensure_display_for_seat()

2022-01-12 Thread Daniel van Vugt
** Tags added: fixed-in-41.3 fixed-upstream

** Changed in: gdm3 (Ubuntu)
   Status: Triaged => Fix Committed

** Description changed:

  https://errors.ubuntu.com/problem/131b21d4843931d315a4548121d7d352cfd1e3a8
+ https://errors.ubuntu.com/problem/175aaeced63f2d1fd3c1361b9802cfff7821bd42
  
  ---
  
  no time for handling, hope everything required in automatically attached
  files
  
  ubuntu impish proposed
  
  i5 + amd 6000 (radeon) in hp g6 notebook
  
  switched from wayland to xorg by adjusting gdm config file
  
  reason for editing config file: want to try out to switch gpu for
  ui/games
  
  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gdm3 41~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Sep 25 17:42:29 2021
  ExecutablePath: /usr/sbin/gdm3
  ProcCmdline: /usr/sbin/gdm3
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x5638df1e412a:mov(%r15),%rcx
   PC (0x5638df1e412a) ok
   source "(%r15)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gdm3
  StacktraceTop:
   ?? ()
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gdm3 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  mtime.conffile..etc.gdm3.custom.conf: 2021-09-25T17:42:14.958231
  separator:

** Tags added: jammy

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1945061

Title:
  gdm3 crashed with SIGSEGV in ensure_display_for_seat()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1945061/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1957711] Re: Switching users causes system crash

2022-01-12 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1945061 ***
https://bugs.launchpad.net/bugs/1945061

Actually nevermind that. I can tell from the hexadecimal addresses in
the stack trace that this is bug 1945061.

** This bug has been marked a duplicate of bug 1945061
   gdm3 crashed with SIGSEGV in ensure_display_for_seat()

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1957711

Title:
  Switching users causes system crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1957711/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1957728] Re: /usr/sbin/gdm3:11:ensure_display_for_seat:on_display_status_changed:closure_invoke_notifiers:g_closure_invoke:g_value_set_gtype

2022-01-12 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1945061 ***
https://bugs.launchpad.net/bugs/1945061

** This bug has been marked a duplicate of bug 1945061
   gdm3 crashed with SIGSEGV in ensure_display_for_seat()

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1957728

Title:
  
/usr/sbin/gdm3:11:ensure_display_for_seat:on_display_status_changed:closure_invoke_notifiers:g_closure_invoke:g_value_set_gtype

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1957728/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1957728] [NEW] /usr/sbin/gdm3:11:ensure_display_for_seat:on_display_status_changed:closure_invoke_notifiers:g_closure_invoke:g_value_set_gtype

2022-01-12 Thread errors.ubuntu.com bug bridge
*** This bug is a duplicate of bug 1945061 ***
https://bugs.launchpad.net/bugs/1945061

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gdm3.  This problem was most recently seen with package version 41~rc-0ubuntu2, 
the problem page at 
https://errors.ubuntu.com/problem/175aaeced63f2d1fd3c1361b9802cfff7821bd42 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: impish

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1957728

Title:
  
/usr/sbin/gdm3:11:ensure_display_for_seat:on_display_status_changed:closure_invoke_notifiers:g_closure_invoke:g_value_set_gtype

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1957728/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1957181] Re: Xorg freeze

2022-01-12 Thread Daniel van Vugt
Thanks for the bug report.

It sounds like GNOME (in the mutter component) has frozen. When this
happens the cursor will still move because it is managed by the Xorg
process, but the screen contents are managed by the gnome-shell process.

Please try removing DisplayLink from the equation by unplugging your
dock or any other USB display adapter. Does the bug still occur using
only the laptop screen?

** Tags added: displaylink evdi

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- Xorg freeze
+ Screen freeze

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1957181

Title:
  Screen freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1957181/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1957711] Re: Switching users causes system crash

2022-01-12 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1945061 ***
https://bugs.launchpad.net/bugs/1945061

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Tags added: impish

** Changed in: gdm3 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1957711

Title:
  Switching users causes system crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1957711/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1957181] [NEW] Xorg freeze

2022-01-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When having more than one window open, e.g. Firefox and a terminal and
then to swap between the two. The clicking with the mouse stops working
but it still moves. For instance when I hover over text or not the
cursor does not change. Sometimes I can still click or select text in
the original window but the coordinates of the mouse are not where the
cursor is displayed. Sometimes the keyboard dies too e.g. Alt+F2 does
not work. Killing XOrg (if possible) seems to revert things to a working
state.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
Uname: Linux 5.4.0-92-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 12 15:24:16 2022
DistUpgraded: 2020-09-07 08:54:13,457 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 evdi, 1.7.0, 4.15.0-70-generic, x86_64: installed
 evdi, 1.7.0, 5.4.0-91-generic, x86_64: installed
 evdi, 1.7.0, 5.4.0-92-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Today
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:225c]
InstallationDate: Installed on 2019-02-13 (1063 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 20KGS5DU00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic 
root=UUID=c1172559-29d0-4c7c-bfab-574068d6d5cc ro quiet 
splash,psmouse.synaptics_intertouch=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-09-07 (492 days ago)
acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
dmi.bios.date: 10/13/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET75W (1.50 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KGS5DU00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KGS5DU00
dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug displaylink evdi focal freeze third-party-packages 
ubuntu
-- 
Xorg freeze
https://bugs.launchpad.net/bugs/1957181
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to mutter in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1956916] Re: [22.04] Unable to set Left Alt + Left Shift key combination to switch keyboard layouts

2022-01-12 Thread Daniel van Vugt
Please report the bug to the developers at
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues and then
tell us the new issue ID.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1956916

Title:
  [22.04] Unable to set Left Alt + Left Shift key combination to switch
  keyboard layouts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1956916] Re: [22.04] Unable to set Left Alt + Left Shift key combination to switch keyboard layouts

2022-01-12 Thread Daniel van Vugt
** Package changed: gnome-shell (Ubuntu) => gnome-control-center
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1956916

Title:
  [22.04] Unable to set Left Alt + Left Shift key combination to switch
  keyboard layouts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1957718] [NEW] package libnautilus-extension1a:amd64 1:40.2-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

2022-01-12 Thread Nick Majdanski
Public bug reported:

Not sure what the issue is. A message pops up and says there is an
issue.

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: libnautilus-extension1a:amd64 1:40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Uname: Linux 5.13.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
AptOrdering:
 ghostscript-x:amd64: Install
 ghostscript:amd64: Install
 libgs9:amd64: Install
 libgs9-common:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Jan 12 19:29:51 2022
DpkgHistoryLog:
 Start-Date: 2022-01-12  19:29:40
 Commandline: /usr/bin/unattended-upgrade
 Upgrade: ghostscript-x:amd64 (9.54.0~dfsg1-0ubuntu2, 9.54.0~dfsg1-0ubuntu2.1), 
libgs9-common:amd64 (9.54.0~dfsg1-0ubuntu2, 9.54.0~dfsg1-0ubuntu2.1), 
ghostscript:amd64 (9.54.0~dfsg1-0ubuntu2, 9.54.0~dfsg1-0ubuntu2.1), 
libgs9:amd64 (9.54.0~dfsg1-0ubuntu2, 9.54.0~dfsg1-0ubuntu2.1)
DuplicateSignature:
 package:libnautilus-extension1a:amd64:1:40.2-1ubuntu1
 Setting up libgs9:amd64 (9.54.0~dfsg1-0ubuntu2.1) ...
 dpkg: error processing package libuno-sal3 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
GsettingsChanges:
 
InstallationDate: Installed on 2021-04-28 (260 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2
 apt  2.3.9
SourcePackage: nautilus
Title: package libnautilus-extension1a:amd64 1:40.2-1ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: Upgraded to impish on 2021-10-14 (90 days ago)
usr_lib_nautilus:
 evince40.4-2
 file-roller   3.40.0-2
 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2
 nautilus-share0.7.3-2ubuntu4

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package impish need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1957718

Title:
  package libnautilus-extension1a:amd64 1:40.2-1ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1957718/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1957716] Re: Update for CVE-2021-43860 and second github advisory

2022-01-12 Thread Seth Arnold
** Also affects: flatpak (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: flatpak (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: flatpak (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to flatpak in Ubuntu.
https://bugs.launchpad.net/bugs/1957716

Title:
  Update for CVE-2021-43860 and second github advisory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1957716/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1957716] [NEW] Update for CVE-2021-43860 and second github advisory

2022-01-12 Thread Andrew Hayzen
*** This bug is a security vulnerability ***

Public security bug reported:

[Links]
https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j
https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx
https://security-tracker.debian.org/tracker/CVE-2021-43860

[Impact]
Versions in Ubuntu right now:
Jammy: 1.12.2-2
Impish: 1.10.2-3ubuntu0.1
Focal: 1.6.5-0ubuntu0.4
Bionic: 1.0.9-0ubuntu0.4

Affected versions:
all

Patched versions:
1.12.3, 1.10.6

[Test Case]
Unknown

[Regression Potential]
Flatpak has a test suite, which is run on build across all relevant 
architectures and passes.

There is also a manual test plan
https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .

Flatpak has autopkgtests enabled
http://autopkgtest.ubuntu.com/packages/f/flatpak .

Regression potential is low, and upstream is very responsive to any
issues raised.

[Patches]
There are two separate github advisories but only one of them has a CVE.

The advisory with the CVE has 5 patches, the other has 2 patches.


[Other Information]

For the first advisory with the CVE:

Ryan Gonzalez discovered that Flatpak doesn't properly validate that the
permissions displayed to the user for an app at install time match the
actual permissions granted to the app at runtime, in the case that
there's a null byte in the metadata file of an app. Therefore apps can
grant themselves permissions without the consent of the user.

Flatpak shows permissions to the user during install by reading them
from the "xa.metadata" key in the commit metadata. This cannot contain a
null terminator, because it is an untrusted GVariant. Flatpak compares
these permissions to the actual metadata, from the "metadata" file to
ensure it wasn't lied to.

However, the actual metadata contents are loaded in several places where
they are read as simple C-style strings. That means that, if the
metadata file includes a null terminator, only the content of the file
from before the terminator gets compared to xa.metadata. Thus, any
permissions that appear in the metadata file after a null terminator are
applied at runtime but not shown to the user. Maliciously crafted apps
can use this to give themselves hidden permissions.

In addition, a similar weakness was discovered, where if the permissions
in the summary metadata are invalid, they would not be displayed to the
user, but the the actual permissions would be granted, even though it
didn't match the invalid version.


For the second advisory:

flatpak-builder applies finish-args last in the build. At this point the
build directory will have the full access that is specified in the
manifest, so running flatpak build against it will gain that
permissions. Normally this will not be done, so this is not problem.
However, if --mirror-screenshots-url is specified, then flatpak-builder
will launch flatpak build --nofilesystem=host appstream-utils mirror-
screenshots after finalization, which can lead to issues even with the
--nofilesystem=host protection.


These changes result in a behaviour change as debian have noted in their
changelog:

  * Behaviour changes, as a result of how GHSA-8ch7-5j3h-g4fx was fixed:
- --nofilesystem=host is now special-cased to negate all --filesystem
  permissions. Previously, it would cancel out --filesystem=host but
  not --filesystem=/some/dir.
- --nofilesystem=home is now special-cased to negate several
  home-directory-related filesystem permssions such as
  --filesystem=xdg-config/foo, not just --filesystem=host.

** Affects: flatpak (Ubuntu)
 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) => Andrew Hayzen (ahayzen)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to flatpak in Ubuntu.
https://bugs.launchpad.net/bugs/1957716

Title:
  Update for CVE-2021-43860 and second github advisory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1957716/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1957711] [NEW] Switching users causes system crash

2022-01-12 Thread GB
Public bug reported:

Ubuntu 21.10

gdm3:
  Installed: 41~rc-0ubuntu2
  Candidate: 41~rc-0ubuntu2
  Version table:
 *** 41~rc-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status

Steps to reproduce:

1. Log in as any user
2. In the top right of the screen, click the power icon (⏻)
3. Select [Power Off/Log Out]
4. Select [Switch User]
5. Select any user that is NOT the user which is still currently logged in
6. Operating system is now frozen, mouse and keyboard don't respond, and user 
is never logged in.
7. Pressing [CTRL] + [ALT] + [DEL] appears to cause the system to crash

Apport.log: https://pastebin.com/srFwgfAh

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Crash log"
   
https://bugs.launchpad.net/bugs/1957711/+attachment/5553637/+files/gdm3.0.crash

** Package changed: apport (Ubuntu) => gdm3 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1957711

Title:
  Switching users causes system crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1957711/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1957711] [NEW] Switching users causes system crash

2022-01-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Ubuntu 21.10

gdm3:
  Installed: 41~rc-0ubuntu2
  Candidate: 41~rc-0ubuntu2
  Version table:
 *** 41~rc-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status

Steps to reproduce:

1. Log in as any user
2. In the top right of the screen, click the power icon (⏻)
3. Select [Power Off/Log Out]
4. Select [Switch User]
5. Select any user that is NOT the user which is still currently logged in
6. Operating system is now frozen, mouse and keyboard don't respond, and user 
is never logged in.
7. Pressing [CTRL] + [ALT] + [DEL] appears to cause the system to crash

Apport.log: https://pastebin.com/srFwgfAh

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Switching users causes system crash
https://bugs.launchpad.net/bugs/1957711
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gdm3 in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"

2022-01-12 Thread Sebastien Bacher
** Changed in: gvfs (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1956949

Title:
  CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1956916] Re: [22.04] Unable to set Left Alt + Left Shift key combination to switch keyboard layouts

2022-01-12 Thread Leonid Golouz
Tried both "Ubuntu" and "Ubuntu on Wayland" and saw no difference
between these two options. There is no way to change key combination to
Left Alt + Left Shift with any option selected.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1956916

Title:
  [22.04] Unable to set Left Alt + Left Shift key combination to switch
  keyboard layouts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956916/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"

2022-01-12 Thread Paride Legovini
@Bernd "not being seeded" means that unionfs-fuse isn't in the set of
packages that define what goes into the Ubuntu 'main' component. In
summary this is done by choosing some "seed" packages and computing
their (build-)dependency tree, see [1,2] if you want to know more.

Automatic syncing of unionfs-fuse from Debian won't happen at the moment
because the package in Ubuntu has Ubuntu specific changes. By looking at
the package changelog these are:

* No change rebuild to pick up -fPIE compiler default
* Merge from Debian unstable (LP: #1476699). Remaining changes:
  - debian/control: Add Multi-Arch: foreign.

Of course only the second one is a "real" change. If you can add

  Multi-Arch: foreign

to d/control in Debian then we can make unionfs-fuse auto-sync again to
Ubuntu. See [3,4] for more details in Multi-Arch.

[1] https://wiki.ubuntu.com/SeedManagement
[2] https://wiki.ubuntu.com/Germinate
[3] https://wiki.debian.org/MultiArch/Hints
[4] https://wiki.ubuntu.com/MultiarchSpec

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1956949

Title:
  CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1956581] Re: make gtk 3.24.31 available in Ubuntu 21.*

2022-01-12 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1913775 ***
https://bugs.launchpad.net/bugs/1913775

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 1913775, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Low => High

** This bug has been marked a duplicate of bug 1913775
   Copy from Firefox Wayland fails to be pasted anywhere else

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1956581

Title:
  make gtk 3.24.31 available in Ubuntu 21.*

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1956581/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1936303] Re: [SRU] Debounce multiple rfkill events

2022-01-12 Thread jeremyszu
** Changed in: oem-priority
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1936303

Title:
  [SRU] Debounce multiple rfkill events

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1936303/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs