date:20220325

*** This bug is a duplicate of bug 1965702 ***
https://bugs.launchpad.net/bugs/1965702

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1965702, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1966527/+attachment/5573059/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1966527/+attachment/5573061/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1966527/+attachment/5573064/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1966527/+attachment/5573065/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1966527/+attachment/5573066/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1966527/+attachment/5573067/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1966527/+attachment/5573068/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1965702

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Occurs when attempting to add microsoft account from the menu.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu8
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 18:39:27 2022
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-03-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  ProcCmdline: gnome-control-center
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff15182330b:mov0x8,%rax
   PC (0x7ff15182330b) ok
   source "0x8" (0x0008) not located in a known VMA region (needed readable 
region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0
   ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1964674] Re: FFe: Sync libvdpau 1.5-1 (main) from Debian sid (main)

2022-03-25 Thread Steve Langasek

This looks incomplete from the perspective of an FFe. Is this actually
a complete description of the new features present in this new upstream
version? An FFe should address the full scope of new features in order
to assess the risk of taking it as a late change, not just the feature
you're interested in that you believe justifies the inclusion.

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

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

Title:
FFe: Sync libvdpau 1.5-1 (main) from Debian sid (main)

Status in libvdpau package in Ubuntu:
Incomplete

Bug description:
Please sync libvdpau 1.5-1 (main) from Debian sid (main)

Explanation of FeatureFreeze exception:
Add AV1 support, the best patent-free codec, used by YouTube, Netflix and
many others.
Tested in my PPA:
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers/+packages?field.name_filter=libvdpau&field.status_filter=published

Changelog entries since current jammy version 1.4-3build1:

libvdpau (1.5-1) unstable; urgency=medium

[ Debian Janitor ]
* Remove constraints unnecessary since buster:
+ Build-Depends: Drop versioned constraint on meson.

[ Luca Boccassi ]
* d/watch: remove signature download, release tarball is no longer
signed.
* New upstream release.
* Bump Standards-Version to 4.6.0, no changes.
* Bump d/copyright year range.
* Set Homepage to landing page, and Source to Gitlab repo.

-- Luca Boccassi Thu, 10 Mar 2022 22:33:21 +

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

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1957050] Re: [MIR] suitesparse-graphblas

2022-03-25 Thread Jeremy Bicha

I'm closing this bug since the package is no longer on the list to be
promoted to main.

** Changed in: suitesparse-graphblas (Ubuntu)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to suitesparse-graphblas in Ubuntu.
https://bugs.launchpad.net/bugs/1957050

Title:
  [MIR] suitesparse-graphblas

Status in suitesparse-graphblas package in Ubuntu:
  Won't Fix

Bug description:
  [Availability]
  The package suitesparse-graphblas is already in Ubuntu universe.
  The package suitesparse-graphblas builds for the architectures it is designed 
to work on.
  It currently builds and works for architectures: amd64 arm64 armhf ppc64el 
riscv64 s390x
  Link to package https://launchpad.net/ubuntu/+source/suitesparse-graphblas

  [Rationale]
  - The package suitesparse-graphblas is required in Ubuntu main to replace the 
current outdated copy included in suitesparse

  It's following up the change in
  https://launchpad.net/ubuntu/+source/suitesparse/1:5.10.1+dfsg-3

  [Security]
  - No CVEs/security issues in this software in the past
  - no `suid` or `sgid` binaries
  - no executables in `/sbin` and `/usr/sbin`
  - Package does not install services, timers or recurring jobs
  - Packages does not open privileged ports (ports < 1024)
  - Packages does not contain extensions to security-sensitive software

  [Quality assurance - function/usage]
  - The package works well right after install

  [Quality assurance - maintenance]
  - The package does not deal with exotic hardware we cannot support

  [Quality assurance - testing]
  - The package doesn't run tests during the build. It's not a regression 
compared to the current situation but it is something we should work toward 
resolving.
  The lack of tests has been reported to Debian, 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003883
  And on launchpad assigned to canonical-desktop-team, 
https://bugs.launchpad.net/ubuntu/+source/suitesparse-graphblas/+bug/1958152
  - Similarly there is no autopkgtest, which is identic to the current 
situation pre split. It's mentioned in the previously referenced reports.
  - The lack of tests was discussed in the MIR team meeting and it was agreed 
the issue wouldn't be a blocker for promotion since it's not a regression over 
the current situation.

  [Quality assurance - packaging]
  - debian/watch is present and works
  - lintian --pedantic only warns about lines > 512 chars in upstream sources 
which doesn't sound like something we need to worry about
  - This package does not rely on obsolete or about to be demoted packages.
  - This package has no python2 or GTK2 dependencies

  - The package will be installed by default, but does not ask debconf questions
  - Packaging and build is easy, link to d/rules 
https://salsa.debian.org/science-team/suitesparse-graphblas/-/blob/master/debian/rules

  [UI standards]
  - Application is not end-user facing (does not need translation)

  [Dependencies]
  - No further depends or recommends dependencies that are not yet in main

  [Standards compliance]
  - This package correctly follows FHS and Debian Policy

  [Maintenance/Owner]
  - Owning Team will be desktop-packages
  - Team is already subscribed to the package

  - This does not use static builds
  - This does not use vendored code

  [Background information]
  The Package description explains the package well
  Upstream Name is GraphBLAS
  Link to upstream project https://people.engr.tamu.edu/davis/GraphBLAS.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/suitesparse-graphblas/+bug/1957050/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966519] Re: hard shutdown after close laptop lid

2022-03-25 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  hard shutdown after close laptop lid

Status in xorg package in Ubuntu:
  New

Bug description:
  shutdown on close screen lid and when i reopen the lid it is
  completely shutdown and i must press the power button and start boot
  sequence, i have set in gnome-tweaks action,the after close the lid
  memory suspend, but evidently it is not working. Sorry for my english.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 20:59:38 2022
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.32, 5.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d3) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Cezanne [103c:8895]
  InstallationDate: Installed on 2022-03-23 (1 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210502)
  MachineType: HP HP EliteBook 845 G8 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic 
root=UUID=e3adb113-cca4-4316-9c3b-edc124da9ca4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 8.3
  dmi.bios.vendor: HP
  dmi.bios.version: T82 Ver. 01.08.03
  dmi.board.name: 8895
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 43.2A.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 67.42
  dmi.modalias: 
dmi:bvnHP:bvrT82Ver.01.08.03:bd02/11/2022:br8.3:efr67.42:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.2A.00:cvnHP:ct10:cvr:sku48R69EA#BCM:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 845 G8 Notebook PC
  dmi.product.sku: 48R69EA#BCM
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966519] [NEW] hard shutdown after close laptop lid

2022-03-25 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

shutdown on close screen lid and when i reopen the lid it is completely
shutdown and i must press the power button and start boot sequence, i
have set in gnome-tweaks action,the after close the lid memory suspend,
but evidently it is not working. Sorry for my english.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
Uname: Linux 5.13.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 25 20:59:38 2022
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.1.32, 5.13.0-37-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d3) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Cezanne [103c:8895]
InstallationDate: Installed on 2022-03-23 (1 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210502)
MachineType: HP HP EliteBook 845 G8 Notebook PC
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic 
root=UUID=e3adb113-cca4-4316-9c3b-edc124da9ca4 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/11/2022
dmi.bios.release: 8.3
dmi.bios.vendor: HP
dmi.bios.version: T82 Ver. 01.08.03
dmi.board.name: 8895
dmi.board.vendor: HP
dmi.board.version: KBC Version 43.2A.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 67.42
dmi.modalias: 
dmi:bvnHP:bvrT82Ver.01.08.03:bd02/11/2022:br8.3:efr67.42:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.2A.00:cvnHP:ct10:cvr:sku48R69EA#BCM:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP EliteBook 845 G8 Notebook PC
dmi.product.sku: 48R69EA#BCM
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug impish ubuntu wayland-session
-- 
hard shutdown after close laptop lid
https://bugs.launchpad.net/bugs/1966519
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966105] Re: [UIFe] Upload wallpaper competition finalists for Jammy

** Changed in: ubuntu-wallpapers (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-wallpapers (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-wallpapers in Ubuntu.
https://bugs.launchpad.net/bugs/1966105

Title:
  [UIFe] Upload wallpaper competition finalists for Jammy

Status in ubuntu-wallpapers package in Ubuntu:
  In Progress

Bug description:
  Prompted by a discussions on Discourse with members of the Desktop
  Team, we are filing a UIFe to upload the finalists of the wallpaper
  competition, which will give us all ten final images in the ISO
  instead of the top four.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966505] [NEW] Lock screen should listen for fingerprint immediately

2022-03-25 Thread Robin Sheat

Public bug reported:

I have a laptop with a fingerprint reader that works fine. When the screensaver 
comes on, I can unlock one of two ways:
1) enter my password,
2) press a key and then press the fingerprint reader

With 2) I'm required to press a key before the fingerprint reader starts
listening. Instead, it should listen all the time so that I can just
open the laptop to wake it from suspend, or if not suspended I can just
press the fingerprint reader and have it unlock immediately. This way
it'll behave more similar to how a phone's fingerprint reader does and
save a (minor) unnecessary interaction.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-screensaver (not installed)
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 25 18:50:10 2022
InstallationDate: Installed on 2022-03-23 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
SourcePackage: gnome-screensaver
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-screensaver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Lock screen should listen for fingerprint immediately

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  I have a laptop with a fingerprint reader that works fine. When the 
screensaver comes on, I can unlock one of two ways:
  1) enter my password,
  2) press a key and then press the fingerprint reader

  With 2) I'm required to press a key before the fingerprint reader
  starts listening. Instead, it should listen all the time so that I can
  just open the laptop to wake it from suspend, or if not suspended I
  can just press the fingerprint reader and have it unlock immediately.
  This way it'll behave more similar to how a phone's fingerprint reader
  does and save a (minor) unnecessary interaction.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 18:50:10 2022
  InstallationDate: Installed on 2022-03-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966502] gjs-console crashed with SIGSEGV

StacktraceTop:
 lookup_opcode_desc(gfx_ver*, opcode_desc const**, unsigned int, unsigned int 
opcode_desc::*, intel_device_info const*, unsigned int) [clone .isra.0] 
(index_ver=0x2a0, index_descs=0x0, index_size=index_size@entry=84, 
key=key@entry=&opcode_desc::ir, k=k@entry=60, devinfo=, 
devinfo=) at ../src/intel/compiler/brw_eu.cpp:720
 brw_opcode_desc (devinfo=, devinfo=, 
opcode=BRW_OPCODE_RNDZ) at ../src/intel/compiler/brw_eu.cpp:750
 is_3src (devinfo=, devinfo=, 
opcode=BRW_OPCODE_RNDZ) at ../src/intel/compiler/brw_eu.h:1942
 backend_instruction::is_3src (this=0x5630ee102870, devinfo=0x5630ecaafa00, 
this=0x5630ee102870, devinfo=0x5630ecaafa00) at 
../src/intel/compiler/brw_shader.cpp:890
 can_take_stride (devinfo=0x5630ecaafa00, stride=1, arg=0, 
dst_type=BRW_REGISTER_TYPE_F, inst=0x5630ee102870) at 
../src/intel/compiler/brw_fs_copy_propagation.cpp:398


** Tags removed: need-amd64-retrace

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

Title:
  gjs-console crashed with SIGSEGV

Status in gjs package in Ubuntu:
  New

Bug description:
  This crash happens when starting Gnome Extensions.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gjs 1.72.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 14:08:33 2022
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2020-02-26 (757 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225.4)
  ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Extensions
  SegvAnalysis:
   Segfault happened at: 0x7f312f6ecfeb:mov(%rdi),%edi
   PC (0x7f312f6ecfeb) ok
   source "(%rdi)" (0x02a0) not located in a known VMA region (needed 
readable region)!
   destination "%edi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gjs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: gjs-console crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo 
vboxusers wireshark
  separator:

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu

2022-03-25 Thread Robin Sheat

This is reproducible in 22.04 also

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

Title:
  Nautilus crashes when opening places from the dock contextmenu

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 21.04, Nautilus crashes every time I try to
  open a second folder by right-clicking on the Nautilus icon in the
  "Favorites" left sidebar (i.e., launch panel) and selecting a
  bookmarked "Places" folder. Normally, this would open a second
  Nautilus window for the selected folder, but instead, any open
  Nautilus windows disappear and no window opens for the selected
  folder. In other words, Nautilus crashes. This did not occur on Ubuntu
  20.10.

  This AskUbuntu post describes the same issue:
  https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying-
  to-open-another-window-by-right-clicking-the-nautil

  If, instead, I right-click the Nautilus icon, select "New Window" and
  then select the desired "Places" folder from the left sidebar of the
  newly opened window, Nautilus does not crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  4 13:36:13 2021
  InstallationDate: Installed on 2020-02-05 (514 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago)
  usr_lib_nautilus:
   evince40.1-1
   file-roller   3.38.1-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966501] xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic()

StacktraceTop:
 map_pid_if_needed (app_info=, pid=, 
error=0x7f2fd1cdf6e8) at src/realtime.c:65
 map_pid_if_needed (app_info=0x7f2fb80077f0, pid=pid@entry=0x7f2fd1cdf6f4, 
error=error@entry=0x7f2fd1cdf6e8) at src/realtime.c:58
 handle_make_thread_realtime_with_pid (object=, 
invocation=0x7f2fcc018dc0, process=, thread=6, priority=5) at 
src/realtime.c:124
 ffi_call_unix64 () at ../src/x86/unix64.S:105
 ffi_call_int (cif=, fn=, rvalue=, 
avalue=, closure=) at ../src/x86/ffi64.c:672


** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1966501

Title:
  xdg-desktop-portal crashed with SIGSEGV in
  g_cclosure_marshal_generic()

Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  closure_marshal_generic()

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal 1.14.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 18:11:56 2022
  ExecutablePath: /usr/libexec/xdg-desktop-portal
  InstallationDate: Installed on 2022-03-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  ProcCmdline: /usr/libexec/xdg-desktop-portal
  SegvAnalysis:
   Segfault happened at: 0x556025d66421:mov0x8(%rax),%rcx
   PC (0x556025d66421) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xdg-desktop-portal
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966501/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966501] [NEW] xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic()

2022-03-25 Thread Norbert Cserpnyák

Public bug reported:

closure_marshal_generic()

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: xdg-desktop-portal 1.14.1-1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 25 18:11:56 2022
ExecutablePath: /usr/libexec/xdg-desktop-portal
InstallationDate: Installed on 2022-03-25 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
ProcCmdline: /usr/libexec/xdg-desktop-portal
SegvAnalysis:
 Segfault happened at: 0x556025d66421:  mov0x8(%rax),%rcx
 PC (0x556025d66421) ok
 source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
 destination "%rcx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xdg-desktop-portal
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libffi.so.8
 ?? () from /lib/x86_64-linux-gnu/libffi.so.8
 g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

** Affects: xdg-desktop-portal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash jammy wayland-session

** Information type changed from Private to Public

** Description changed:

- -closure_marshal_generic()
+ closure_marshal_generic()
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal 1.14.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 18:11:56 2022
  ExecutablePath: /usr/libexec/xdg-desktop-portal
  InstallationDate: Installed on 2022-03-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  ProcCmdline: /usr/libexec/xdg-desktop-portal
  SegvAnalysis:
-  Segfault happened at: 0x556025d66421:mov0x8(%rax),%rcx
-  PC (0x556025d66421) ok
-  source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
-  destination "%rcx" ok
-  Stack memory exhausted (SP below stack segment)
+  Segfault happened at: 0x556025d66421:mov0x8(%rax),%rcx
+  PC (0x556025d66421) ok
+  source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
+  destination "%rcx" ok
+  Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xdg-desktop-portal
  StacktraceTop:
-  ?? ()
-  ?? ()
-  ?? () from /lib/x86_64-linux-gnu/libffi.so.8
-  ?? () from /lib/x86_64-linux-gnu/libffi.so.8
-  g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  ?? ()
+  ?? ()
+  ?? () from /lib/x86_64-linux-gnu/libffi.so.8
+  ?? () from /lib/x86_64-linux-gnu/libffi.so.8
+  g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1966501

Title:
  xdg-desktop-portal crashed with SIGSEGV in
  g_cclosure_marshal_generic()

Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  closure_marshal_generic()

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal 1.14.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 18:11:56 2022
  ExecutablePath: /usr/libexec/xdg-desktop-portal
  InstallationDate: Installed on 2022-03-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  ProcCmdline: /usr/libexec/xdg-desktop-portal
  SegvAnalysis:
   Segfault happened at: 0x556025d66421:mov0x8(%rax),%rcx
   PC (0x556025d66421) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xdg-desktop-portal
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linu

[Desktop-packages] [Bug 1966502] [NEW] gjs-console crashed with SIGSEGV

2022-03-25 Thread Eric Carvalho

Public bug reported:

This crash happens when starting Gnome Extensions.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gjs 1.72.0-1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 25 14:08:33 2022
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2020-02-26 (757 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225.4)
ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Extensions
SegvAnalysis:
 Segfault happened at: 0x7f312f6ecfeb:  mov(%rdi),%edi
 PC (0x7f312f6ecfeb) ok
 source "(%rdi)" (0x02a0) not located in a known VMA region (needed 
readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gjs
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
Title: gjs-console crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers 
wireshark
separator:

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


** Tags: amd64 apport-crash jammy need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gjs-console crashed with SIGSEGV

Status in gjs package in Ubuntu:
  New

Bug description:
  This crash happens when starting Gnome Extensions.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gjs 1.72.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 14:08:33 2022
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2020-02-26 (757 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225.4)
  ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Extensions
  SegvAnalysis:
   Segfault happened at: 0x7f312f6ecfeb:mov(%rdi),%edi
   PC (0x7f312f6ecfeb) ok
   source "(%rdi)" (0x02a0) not located in a known VMA region (needed 
readable region)!
   destination "%edi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gjs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: gjs-console crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo 
vboxusers wireshark
  separator:

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966317] Re: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()

2022-03-25 Thread Brian Murray

I wonder if this bucket is the same crash:

https://errors.ubuntu.com/problem/032cbaffce29195785ab96c0724c284cf5c2426f

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

Title:
  gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()

Status in gvfs package in Ubuntu:
  New

Bug description:
  I encountered this crash during a dist-upgrade from impish to jammy,
  i.e. running `do-release-upgrade --devel-release`. My desktop session
  crashed, and my VM can no longer boot the desktop (but I can ssh
  still).

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gvfs-fuse 1.47.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Thu Mar 24 12:10:04 2022
  ExecutablePath: /usr/libexec/gvfsd-fuse
  ExecutableTimestamp: 1615801987
  InstallationDate: Installed on 2022-02-02 (49 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
  ProcCwd: /home/nr
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   __pthread_setname_np (th=1251, name=0x6 ) at ./nptl/pthread_setname.c:32
   ?? ()
  Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()
  UpgradeStatus: Upgraded to impish on 2022-03-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966317] Re: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()

2022-03-25 Thread Brian Murray

I believe this failed to retrace because the packages installed are
likely a mix of ones from impish and jammy.

** Tags added: rls-jj-incoming

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

Title:
  gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()

Status in gvfs package in Ubuntu:
  New

Bug description:
  I encountered this crash during a dist-upgrade from impish to jammy,
  i.e. running `do-release-upgrade --devel-release`. My desktop session
  crashed, and my VM can no longer boot the desktop (but I can ssh
  still).

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gvfs-fuse 1.47.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Thu Mar 24 12:10:04 2022
  ExecutablePath: /usr/libexec/gvfsd-fuse
  ExecutableTimestamp: 1615801987
  InstallationDate: Installed on 2022-02-02 (49 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
  ProcCwd: /home/nr
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   __pthread_setname_np (th=1251, name=0x6 ) at ./nptl/pthread_setname.c:32
   ?? ()
  Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()
  UpgradeStatus: Upgraded to impish on 2022-03-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session

2022-03-25 Thread Mike Pontillo

Thanks for your attention to this bug, Daniel.

For the record, I don't think a set up like this is particularly weird;
I'm seeing this issue on a laptop with embedded NVIDIA graphics. The
"second video card", in my case, is the integrated Intel graphics card.

Also, I'm not sure if this is related, but yesterday I saw a regression
that caused my second monitor to fail; the only workaround I found was
to downgrade to nvidia-driver-470 from nvidia-driver-510. (That is,
nvidia-driver-510 wasn't causing me too much trouble when I first
installed Jammy from the March 21st image; it took a day or two of
updating, then started causing me issues yesterday .)

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

Title:
  gnome-shell crashes (fatal error logged in create_fallback_offscreen)
  when attempting to enable second monitor on second GPU (Nvidia >= 495)
  in a Wayland session

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  This is on my weird desktop setup, with one monitor plugged into an
  AMD card and one into an NVIDIA card.

  When using the Wayland session, by default Shell will come up on the
  monitor connected to the AMD card, and the second (NVIDIA) monitor
  will be blank. Attempting to enable the second monitor in Display
  Settings will immediately and reproducibly crash gnome-shell.

  This is trivial for me to reproduce, so if you need patches tested I
  can easily do so.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 
5.15.0+bcachefs.git2026.1fa97551d-1.1-generic 5.15.2
  Uname: Linux 5.15.0+bcachefs.git2026.1fa97551d-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 09:37:51 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-11-02 (125 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 41.3-3ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   meta_monitor_mode_foreach_crtc () at /lib/x86_64-linux-gnu/libmutter-9.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to jammy on 2021-11-02 (124 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

2022-03-25 Thread Kai-Heng Feng

I enabled proposed and upgrade alsa-ucm-conf, then reboot the system.

I plugged a microphone to the rear panel, made sure it works, then I
plugged a speaker to line-out, and made sure both speaker and mic are
working. So the original issue is solved by this SRU.

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  On P620, only single port can work on rear panel. For example, when the 
Line-Out is plugged, the Mic won't work anymore.

  [Fix]
  Use upstream version of UCM to handle port priority correctly, instead of 
separate ports into different profiles.

  [Test]
  Once the UCM is in place, all three ports of rear panel work correctly.

  [Where problems could occur]
  UCM is not a static thing - it's actually interpreted differently at higher 
level. So any change in userspace daemons other than PulseAudio may not like 
the change and can interpret the UCM in another way.

  == Original Bug Report ==
  After backporting following patches from PA and alsa-ucm-conf and then it 
works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused

2022-03-25 Thread MangoCats

I found this bug because I was searching for the message:

gnome-shell[PID]: Unable to connect to ibus: Could not connect:
Connection refused

in my journalctl output from a relatively new Ubuntu 21.10 install.  No
apparent problems, but I was looking to see if I should be concerned?

Summary: Still present in some Ubuntu 21.10 logs.

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

Title:
  Unable to connect to ibus: Could not connect: Connection refused

Status in gnome-shell package in Ubuntu:
  Expired
Status in ibus package in Ubuntu:
  Expired

Bug description:
  Get this logged:

  oem@ubuntu:~$ journalctl -b | grep ibus

  dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
  pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1084]: Unable to connect to ibus: Could not connect:
  Connection refused

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting QT_IM_MODULE=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting XMODIFIERS=@im=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting GTK_IM_MODULE=ibus

  dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
  pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1435]: Unable to connect to ibus: Could not connect:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  5 07:43:59 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966105] Re: [UIFe] Upload wallpaper competition finalists for Jammy

2022-03-25 Thread Brian Murray

I approve of adding these wallpapers to Jammy.

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-wallpapers in Ubuntu.
https://bugs.launchpad.net/bugs/1966105

Title:
  [UIFe] Upload wallpaper competition finalists for Jammy

Status in ubuntu-wallpapers package in Ubuntu:
  Triaged

Bug description:
  Prompted by a discussions on Discourse with members of the Desktop
  Team, we are filing a UIFe to upload the finalists of the wallpaper
  competition, which will give us all ten final images in the ISO
  instead of the top four.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1965809] Re: 22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem crashed with SIGSEGV in magazine_chain_pop_head()

2022-03-25 Thread XA Hydra

After many reboots and log out / log in cycles, I have noticed that this
happens 95% of the time in Wayland, but hasn't happened once in Xorg

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1965809

Title:
  22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem
  crashed with SIGSEGV in magazine_chain_pop_head()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Attempting to open videos in multiple formats (tried .webm and .mp4 so
  far) results in ‘specified movie could not be found’ errors in Videos.

  I’ve moved them into multiple folders with the same result. If I hit
  the upper left button ’ < ’ I can see the file just fine

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libgstreamer1.0-0 1.20.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 14:20:08 2022
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2022-02-17 (32 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f023771dd0c :mov
0x8(%r12),%rax
   PC (0x7f023771dd0c) ok
   source "0x8(%r12)" (0x55e51814962008) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: totem crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1965809/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966336] Re: gnome-disks crashed with SIGSEGV in get_all_native_children()

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

** Information type changed from Private to Public

** Changed in: gnome-disk-utility (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-disks crashed with SIGSEGV in get_all_native_children()

Status in gnome-disk-utility package in Ubuntu:
  Incomplete

Bug description:
  double boot issues too => daemon snap failed

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-disk-utility 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 21:49:25 2022
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2022-03-23 (1 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f00f45ae3b2:mov0x18(%rax),%rdi
   PC (0x7f00f45ae3b2) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_window_begin_draw_frame () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-disks crashed with SIGSEGV in gdk_window_begin_draw_frame()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1910877] Re: DejaDup does not display an icon in the panel

2022-03-25 Thread Martin Wimpress 

** No longer affects: ubuntu-mate

** Changed in: mate-panel (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1910877

Title:
  DejaDup does not display an icon in the panel

Status in deja-dup package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  When DejaDup is performing a backup, there is no icon in the panel on
  Ubuntu Mate 20.04. (There is in 18.04).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1910877/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error

We saw a few reports in 2020 and no real activity since, it doesn't seem
an high importance issue at this point so I'm going to lower the setting
and unassign for now since we have other higher priority work in the
queue

** Changed in: thunderbird (Ubuntu)
   Importance: High => Low

** Changed in: thunderbird (Ubuntu)
 Assignee: Olivier Tilloy (osomon) => (unassigned)

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

Title:
  thunderbird fails to open, xml parse error

Status in thunderbird package in Ubuntu:
  Confirmed
Status in thunderbird source package in Groovy:
  Won't Fix

Bug description:
  launching thunderbird opens a small browser window displaying the
  following error:

  XML Parsing Error: undefined entity
  Location: chrome://messenger/content/messenger.xhtml
  Line Number 905, Column 3:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1965558] Re: Cannot change wallpaper by right-clicking image in dark theme

2022-03-25 Thread Jeremy Bicha

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

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

Title:
  Cannot change wallpaper by right-clicking image in dark theme

Status in nautilus package in Ubuntu:
  Fix Committed
Status in nautilus source package in Jammy:
  Fix Committed

Bug description:
  With the light theme enabled, you can set the desktop wallpaper by
  right-clicking on an image file's icon in the file manager and
  selecting "Set As Wallpaper". When you do this the Desktop wallpaper
  changes straight away.

  Now change to dark theme and repeat the above steps. The wallpaper
  never changes. You can however change the wallpaper fine using Gnome
  settings -> Appearance.

  Thanks
  Nick

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu6
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 18 16:14:38 2022
  InstallationDate: Installed on 2022-02-28 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966443] Re: I can't start it

*** This bug is a duplicate of bug 1965897 ***
https://bugs.launchpad.net/bugs/1965897

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1965897, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1966443/+attachment/5572929/+files/CoreDump.gz

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1966443/+attachment/5572933/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1966443/+attachment/5572934/+files/ProcStatus.txt

** This bug has been marked a duplicate of bug 1965897
   gnome-shell crashed with SIGSEGV in meta_window_get_window_type(window=NULL) 
from meta_window_actor_queue_destroy() from 
meta_compositor_real_remove_window() from meta_window_unmanage() from 
meta_display_unmanage_windows()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  I can't start it

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  For "https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1966221"

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 21:29:03 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1647578316
  GsettingsChanges: b'org.gnome.desktop.app-folders' b'folder-children' 
b"['Utilities', 'YaST']"
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/xiaozhangup
  ProcEnviron:
   LANG=zh_CN.UTF-8
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

2022-03-25 Thread Zhang

It is important to note that before this problem occurred, I used "apt-
get dist-upgrade" to force some packages to be updated, and this is what
I did at the time.

Start-Date: 2022-03-23  20:46:02
Commandline: apt-get dist-upgrade
Requested-By: xiaozhangup (1000)
Upgrade: libglx-mesa0:amd64 (21.3.5-1ubuntu1, 22.0.0-0ubuntu1), 
libglx-mesa0:i386 (21.3.5-1ubuntu1, 22.0.0-0ubuntu1), libgbm1:amd64 
(21.3.5-1ubuntu1, 22.0.0-0ubuntu1), libgbm1:i386 (21.3.5-1ubuntu1, 
22.0.0-0ubuntu1), libgl1-mesa-dri:amd64 (21.3.5-1ubuntu1, 22.0.0-0ubuntu1), 
libgl1-mesa-dri:i386 (21.3.5-1ubuntu1, 22.0.0-0ubuntu1), libglapi-mesa:amd64 
(21.3.5-1ubuntu1, 22.0.0-0ubuntu1), libglapi-mesa:i386 (21.3.5-1ubuntu1, 
22.0.0-0ubuntu1), libegl-mesa0:amd64 (21.3.5-1ubuntu1, 22.0.0-0ubuntu1), 
libegl-mesa0:i386 (21.3.5-1ubuntu1, 22.0.0-0ubuntu1)
End-Date: 2022-03-23  20:46:14


Incidentally, using the command "GSK_RENDERER=Cairo gnome-extensions-
app" will start the application normally

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

2022-03-25 Thread Zhang

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966443

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966440] Re: gnome-shell crashes often when using the menu (start) button

2022-03-25 Thread KaOS-bEat

I noticed gnome-shell is not up to date, but it won't update


sudo apt-get install gnome-shell
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gstreamer1.0-pipewire : Depends: pipewire (= 0.3.48-1ubuntu1) but 
0.3.48.r23.g8673f8c-3~ubuntu20.04 is to be installed
 Depends: libpipewire-0.3-0 (= 0.3.48-1ubuntu1) but 
0.3.48.r23.g8673f8c-3~ubuntu20.04 is to be installed
 libwacom2 : Depends: libwacom-common (= 1.3-2ubuntu3) but 2.1.0-2 is to be 
installed
 Recommends: libwacom-bin (= 1.3-2ubuntu3)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.


I tried uninstalling pipewire, kdid not help. I have never touched the libwacom 
package

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

Title:
  gnome-shell crashes often when using the menu (start) button

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy

  
  I upgraded from 20.04 LTS

  
  gnome-shell:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 42~beta-1ubuntu3
Version table:
   42~beta-1ubuntu3 500
  500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
   *** 3.36.9-0ubuntu0.20.04.2 100
  100 /var/lib/dpkg/status

  
  When I press the "windows" key and start searching for an app this works 
fine, and I can launch the app. However immediately afterwards all windows 
freeze, loose their decoration/position. Then the  screen flashes and we're 
back. All notification in the queue pop up again as well.

  It happens almost every time.

  I checked the PID of the gnome-shell in top, and it effectively changes so I 
believe the gnome-shell crashes. It shouldn't. 
  How can I collect relevant debug info?
  I cannot seem to find a cause.
  I'm using nvidia-drivers if that matters.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 13:21:03 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-09-28 (177 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966440] [NEW] gnome-shell crashes often when using the menu (start) button

2022-03-25 Thread KaOS-bEat

Public bug reported:

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
Codename:   jammy


I upgraded from 20.04 LTS


gnome-shell:
  Installed: 3.36.9-0ubuntu0.20.04.2
  Candidate: 42~beta-1ubuntu3
  Version table:
 42~beta-1ubuntu3 500
500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
 *** 3.36.9-0ubuntu0.20.04.2 100
100 /var/lib/dpkg/status


When I press the "windows" key and start searching for an app this works fine, 
and I can launch the app. However immediately afterwards all windows freeze, 
loose their decoration/position. Then the  screen flashes and we're back. All 
notification in the queue pop up again as well.

It happens almost every time.

I checked the PID of the gnome-shell in top, and it effectively changes so I 
believe the gnome-shell crashes. It shouldn't. 
How can I collect relevant debug info?
I cannot seem to find a cause.
I'm using nvidia-drivers if that matters.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
Uname: Linux 5.15.0-22-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 25 13:21:03 2022
DisplayManager: gdm3
InstallationDate: Installed on 2021-09-28 (177 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy third-party-packages

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

Title:
  gnome-shell crashes often when using the menu (start) button

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy

  
  I upgraded from 20.04 LTS

  
  gnome-shell:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 42~beta-1ubuntu3
Version table:
   42~beta-1ubuntu3 500
  500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
   *** 3.36.9-0ubuntu0.20.04.2 100
  100 /var/lib/dpkg/status

  
  When I press the "windows" key and start searching for an app this works 
fine, and I can launch the app. However immediately afterwards all windows 
freeze, loose their decoration/position. Then the  screen flashes and we're 
back. All notification in the queue pop up again as well.

  It happens almost every time.

  I checked the PID of the gnome-shell in top, and it effectively changes so I 
believe the gnome-shell crashes. It shouldn't. 
  How can I collect relevant debug info?
  I cannot seem to find a cause.
  I'm using nvidia-drivers if that matters.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 13:21:03 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-09-28 (177 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1861609] Re: [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from

2022-03-25 Thread Josué Casado Rabasco

Hi, I have tried this solution, but when I use Ubuntu on Wayland, it
goes extremely slow (for example the mouse pointer). Does anyone know
why is it happening?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1861609

Title:
  [focal] Xorg crashed with assertion failure (usually in a VM) at
  [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized'
  failed] and call stack comes from DRIMoveBuffersHelper

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Xorg crashed with assertion failure (usually in a VM):

  privates.h:121: dixGetPrivateAddr: Assertion `key->initialized'
  failed.

  and call stack comes from DRIMoveBuffersHelper

  WORKAROUND

  Select 'Ubuntu on Wayland' on the login screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861609/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966436] [NEW] Bluetooth fails to connect "br-connection-profile-unavailable"

2022-03-25 Thread EdwardO

Public bug reported:

How to reproduce:

> bluetoothctl scan on
Discovery started
...
> bluetoothctl connect 94:DB:56:8E:0B:96
Attempting to connect to 94:DB:56:8E:0B:96
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable

> systemctl status bluetooth
bluetooth.service - Bluetooth service
 Loaded: loaded
...
mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: 
src/service.c:btd_service_connect() a2dp-sink profile connect failed for 
94:DB:56:8E:0B:96: Protocol not available

Notes:
kernel-5.15, bluez-5.64
Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Dell Precision 3560
Unfortunately I did not test before upgrade to 22.04.
Tried installing pipewire-pulse, blueman, but this is lower-level.
There are reports of similar errors popping up in Arch and Manjaro recently:
https://bbs.archlinux.org/viewtopic.php?id=270465
https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Fri Mar 25 12:56:34 2022
InstallationDate: Installed on 2022-03-04 (21 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Precision 3560
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES 
nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago)
dmi.bios.date: 09/13/2021
dmi.bios.release: 1.12
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.2
dmi.board.name: 095HH7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22:
dmi.product.family: Precision
dmi.product.name: Precision 3560
dmi.product.sku: 0A22
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 44:E5:17:BC:00:DD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:24189 acl:41 sco:0 events:519 errors:0
TX bytes:8252 acl:33 sco:0 commands:239 errors:0
modified.conffile..etc.cron.daily.apport: [deleted]

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Bluetooth fails to connect "br-connection-profile-unavailable"

Status in bluez package in Ubuntu:
  New

Bug description:
  How to reproduce:

  > bluetoothctl scan on
  Discovery started
  ...
  > bluetoothctl connect 94:DB:56:8E:0B:96
  Attempting to connect to 94:DB:56:8E:0B:96
  Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable

  > systemctl status bluetooth
  bluetooth.service - Bluetooth service
   Loaded: loaded
  ...
  mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: 
src/service.c:btd_service_connect() a2dp-sink profile connect failed for 
94:DB:56:8E:0B:96: Protocol not available

  Notes:
  kernel-5.15, bluez-5.64
  Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
  Dell Precision 3560
  Unfortunately I did not test before upgrade to 22.04.
  Tried installing pipewire-pulse, blueman, but this is lower-level.
  There are reports of similar errors popping up in Arch and Manjaro recently:
  https://bbs.archlinux.org/viewtopic.php?id=270465
  https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Mar 25 12:56:34 2022
  InstallationDate: Installed on 2022-03-04 (21 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Precision 3560
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES 
nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago)
  dmi.bios.date: 09/13/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.2
  dmi.board.name: 095HH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias

[Desktop-packages] [Bug 1966433] [NEW] Pipewire services start up on remote (ssh) logins

2022-03-25 Thread Daniel Richard G.

Public bug reported:

This concern pipewire 0.3.48-1ubuntu1 in Ubuntu jammy.

I log into an installed system via ssh, and I see

skunk@darkstar:~$ ps auxww | grep skunk
root   13771  0.5  0.1  19772 12224 ?Ss   07:35   0:00 sshd: skunk 
[priv]
skunk  13774  5.4  0.1  17160  9940 ?Ss   07:35   0:00 
/lib/systemd/systemd --user
skunk  13775  0.0  0.0  25600  5292 ?S07:35   0:00 (sd-pam)
skunk  13782  0.4  0.0  34460  6360 ?Ssl  07:35   0:00 
/usr/bin/pipewire
skunk  13783  0.4  0.0  18632  6856 ?Ssl  07:35   0:00 
/usr/bin/pipewire-media-session
skunk  13801  0.0  0.0   8412  4340 ?Ss   07:35   0:00 
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile 
--systemd-activation --syslog-only
skunk  13831  0.0  0.0  19932  8052 ?S07:35   0:00 sshd: 
skunk@pts/0
skunk  13832  0.0  0.0   5256  4124 pts/0Ss   07:35   0:00 -bash
skunk  13854  0.0  0.0   7692  3328 pts/0R+   07:35   0:00 ps auxww
skunk  13855  0.0  0.0   4024  2144 pts/0S+   07:35   0:00 grep 
--color=auto skunk

Pipewire is a multimedia service. It should not be running in a remote,
non-graphical login.

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


** Tags: jammy

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

Title:
  Pipewire services start up on remote (ssh) logins

Status in pipewire package in Ubuntu:
  New

Bug description:
  This concern pipewire 0.3.48-1ubuntu1 in Ubuntu jammy.

  I log into an installed system via ssh, and I see

  skunk@darkstar:~$ ps auxww | grep skunk
  root   13771  0.5  0.1  19772 12224 ?Ss   07:35   0:00 sshd: 
skunk [priv]
  skunk  13774  5.4  0.1  17160  9940 ?Ss   07:35   0:00 
/lib/systemd/systemd --user
  skunk  13775  0.0  0.0  25600  5292 ?S07:35   0:00 (sd-pam)
  skunk  13782  0.4  0.0  34460  6360 ?Ssl  07:35   0:00 
/usr/bin/pipewire
  skunk  13783  0.4  0.0  18632  6856 ?Ssl  07:35   0:00 
/usr/bin/pipewire-media-session
  skunk  13801  0.0  0.0   8412  4340 ?Ss   07:35   0:00 
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile 
--systemd-activation --syslog-only
  skunk  13831  0.0  0.0  19932  8052 ?S07:35   0:00 sshd: 
skunk@pts/0
  skunk  13832  0.0  0.0   5256  4124 pts/0Ss   07:35   0:00 -bash
  skunk  13854  0.0  0.0   7692  3328 pts/0R+   07:35   0:00 ps auxww
  skunk  13855  0.0  0.0   4024  2144 pts/0S+   07:35   0:00 grep 
--color=auto skunk

  Pipewire is a multimedia service. It should not be running in a
  remote, non-graphical login.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966413] [NEW] --no-oem option is broken

2022-03-25 Thread eoli3n

Public bug reported:

$ ubuntu-drivers --no-oem install
Traceback (most recent call last):
  File "/usr/bin/ubuntu-drivers", line 490, in 
greet()
  File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke
Command.invoke(self, ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in 
new_func
return ctx.invoke(f, obj, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
  File "/usr/bin/ubuntu-drivers", line 376, in greet
config.no_oem = install_oem_meta
NameError: name 'install_oem_meta' is not defined

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-drivers-common 1:0.9.0~0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Mar 25 11:44:15 2022
InstallationDate: Installed on 2022-03-25 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 TERM=xterm-kitty
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1966413

Title:
  --no-oem option is broken

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  $ ubuntu-drivers --no-oem install
  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 490, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke
  Command.invoke(self, ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
  return callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
  return callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 376, in greet
  config.no_oem = install_oem_meta
  NameError: name 'install_oem_meta' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-drivers-common 1:0.9.0~0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Mar 25 11:44:15 2022
  InstallationDate: Installed on 2022-03-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-kitty
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1966413/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1872594] Re: Ubuntu logo shifts vertically when the login screen appears

** Summary changed:

- Ubuntu logo shifts vertically when the purple login screen appears
+ Ubuntu logo shifts vertically when the login screen appears

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

Title:
  Ubuntu logo shifts vertically when the login screen appears

Status in gnome-shell package in Ubuntu:
  Triaged
Status in plymouth package in Ubuntu:
  Triaged

Bug description:
  Ubuntu logo shifts upward about 1px when the purple login screen
  appears.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

2022-03-25 Thread Timo Aaltonen

Hello jeremyszu, or anyone else affected,

Accepted alsa-ucm-conf into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu0.13 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  On P620, only single port can work on rear panel. For example, when the 
Line-Out is plugged, the Mic won't work anymore.

  [Fix]
  Use upstream version of UCM to handle port priority correctly, instead of 
separate ports into different profiles.

  [Test]
  Once the UCM is in place, all three ports of rear panel work correctly.

  [Where problems could occur]
  UCM is not a static thing - it's actually interpreted differently at higher 
level. So any change in userspace daemons other than PulseAudio may not like 
the change and can interpret the UCM in another way.

  == Original Bug Report ==
  After backporting following patches from PA and alsa-ucm-conf and then it 
works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

2022-03-25 Thread Kai-Heng Feng

** Description changed:

- After backporting following patches from PA and alsa-ucm-conf and then
- it works.
+ == SRU Justification ==
+ [Impact]
+ On P620, only single port can work on rear panel. For example, when the 
Line-Out is plugged, the Mic won't work anymore.
+ 
+ [Fix]
+ Use upstream version of UCM to handle port priority correctly, instead of 
separate ports into different profiles.
+ 
+ [Test]
+ Once the UCM is in place, all three ports of rear panel work correctly.
+ 
+ [Where problems could occur]
+ UCM is not a static thing - it's actually interpreted differently at higher 
level. So any change in userspace daemons other than PulseAudio may not like 
the change and can interpret the UCM in another way.
+ 
+ == Original Bug Report ==
+ After backporting following patches from PA and alsa-ucm-conf and then it 
works.
  
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355
  
  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-Audio
  [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]
  
  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test
  
  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  On P620, only single port can work on rear panel. For example, when the 
Line-Out is plugged, the Mic won't work anymore.

  [Fix]
  Use upstream version of UCM to handle port priority correctly, instead of 
separate ports into different profiles.

  [Test]
  Once the UCM is in place, all three ports of rear panel work correctly.

  [Where problems could occur]
  UCM is not a static thing - it's actually interpreted differently at higher 
level. So any change in userspace daemons other than PulseAudio may not like 
the change and can interpret the UCM in another way.

  == Original Bug Report ==
  After backporting following patches from PA and alsa-ucm-conf and then it 
works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl

** No longer affects: gjs (Ubuntu)

** No longer affects: mozjs91 (Ubuntu)

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

Title:
  [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer
  from js::gc::PostWriteBarrierImpl

Status in gjs:
  Unknown
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Core was generated by `gnome-shell --sm-disable --mode=ubiquity'.
  Program terminated with signal SIGSEGV, Segmentation fault.

  In mozjs91:

  #0 0x7f5a697c3f44 in js::gc::Cell::storeBuffer (this=, 
this=)
  at .././js/src/gc/Cell.h:357
  #1 js::gc::PostWriteBarrierImpl (next=, 
prev=, cellp=)
  at .././js/src/gc/StoreBuffer.h:654
  #2 js::gc::PostWriteBarrier (next=, 
prev=, vp=)
  at .././js/src/gc/StoreBuffer.h:666
  #3 js::InternalBarrierMethods::postBarrier (next=, prev=,
  vp=0x7f5a5002b200) at .././js/src/gc/Barrier.h:333
  #4 js::InternalBarrierMethods::postBarrier 
(vp=0x7f5a5002b200, prev=,
  next=) at .././js/src/gc/Barrier.h:332
  #5 0x7f5a6b637722 in js::BarrierMethods::postWriteBarrier 
(next=,
  prev=, vp=, vp=, 
prev=, next=)
  at /usr/include/mozjs-91/js/RootingAPI.h:770
  #6 JS::Heap::postWriteBarrier (next=, 
prev=, this=,
  this=, prev=, next=) at 
/usr/include/mozjs-91/js/RootingAPI.h:361
  #7 JS::Heap::~Heap (this=, this=)
  at /usr/include/mozjs-91/js/RootingAPI.h:323
  #8 mozilla::detail::VectorImpl, 0ul, 
js::SystemAllocPolicy, false>::destroy (
  aEnd=0x7f5a5002b218, aBegin=) at 
/usr/include/mozjs-91/mozilla/Vector.h:65
  #9 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector 
(this=,
  this=) at /usr/include/mozjs-91/mozilla/Vector.h:901
  #10 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector 
(this=,
  this=) at /usr/include/mozjs-91/js/GCVector.h:43
  #11 GjsContextPrivate::~GjsContextPrivate (this=, 
this=) at ../gjs/context.cpp:482
  #12 0x7f5a6b638978 in gjs_context_finalize (object=0x557e2a3f7180) at 
../gjs/context.cpp:495
  #13 0x7f5a6c0d2dfd in g_object_unref () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #14 0x7f5a6c31d77d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:703
  #15 0x557e2950bece in main (argc=, argv=) 
at ../src/main.c:659

  In mozjs78:

  See bug 1947130

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966386] Re: /usr/libexec/xdg-desktop-portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

2022-03-25 Thread Bug Watch Updater

** Changed in: xdg-desktop-portal
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1966386

Title:
  /usr/libexec/xdg-desktop-
  
portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

Status in xdg-desktop-portal:
  New
Status in xdg-desktop-portal package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xdg-desktop-portal.  This problem was most recently seen with package version 
1.14.1-1, the problem page at 
https://errors.ubuntu.com/problem/34483c95acb7a7b00ab9e83731350bf5e4233db0 
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/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-desktop-portal/+bug/1966386/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1928262] Re: Too few images in 21.04

Thank you for reporting this bug to Ubuntu.
Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.


** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-wallpapers in Ubuntu.
https://bugs.launchpad.net/bugs/1928262

Title:
  Too few images in 21.04

Status in ubuntu-wallpapers package in Ubuntu:
  Won't Fix

Bug description:
  After upgraded from Ubuntu 20.10 to 21.04 i see only 5 picture for desktop 
background:
  https://imgur.com/a/P9Rgfgb

  As far as i understand and according to source should be more images in deb 
package:
  https://launchpad.net/ubuntu/+source/ubuntu-wallpapers/21.04.1-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-wallpapers-hirsute 21.04.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 13 00:49:12 2021
  Dependencies:
   
  InstallationDate: Installed on 2018-05-02 (1106 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-wallpapers
  UpgradeStatus: Upgraded to hirsute on 2021-05-12 (0 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966105] Re: [UIFe] Upload wallpaper competition finalists for Jammy

** Tags added: jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-wallpapers in Ubuntu.
https://bugs.launchpad.net/bugs/1966105

Title:
  [UIFe] Upload wallpaper competition finalists for Jammy

Status in ubuntu-wallpapers package in Ubuntu:
  Confirmed

Bug description:
  Prompted by a discussions on Discourse with members of the Desktop
  Team, we are filing a UIFe to upload the finalists of the wallpaper
  competition, which will give us all ten final images in the ISO
  instead of the top four.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966105] Re: [UIFe] Upload wallpaper competition finalists for Jammy

2022-03-25 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-wallpapers in Ubuntu.
https://bugs.launchpad.net/bugs/1966105

Title:
  [UIFe] Upload wallpaper competition finalists for Jammy

Status in ubuntu-wallpapers package in Ubuntu:
  Confirmed

Bug description:
  Prompted by a discussions on Discourse with members of the Desktop
  Team, we are filing a UIFe to upload the finalists of the wallpaper
  competition, which will give us all ten final images in the ISO
  instead of the top four.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1962761] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

that's fixed in nautilus 42.0

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  It's part of a chain of bugs that come one after another as I try to
  report each one of them.

  Never saw this behavior before

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42~beta-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 25 20:32:37 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2022-01-03 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=ro_RO.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f5f445b49a8 :   cmp
%rax,(%rbx)
   PC (0x7f5f445b49a8) ok
   source "%rax" ok
   destination "(%rbx)" (0x71818181c7808080) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_widget_get_ancestor () at /lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:
   evince41.3-3
   file-roller   3.41.90-1
   nautilus-extension-gnome-terminal 3.43.90-1ubuntu1
   nautilus-share0.7.3-2ubuntu4

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966386] Re: /usr/libexec/xdg-desktop-portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

** Bug watch added: github.com/flatpak/xdg-desktop-portal/issues #709
   https://github.com/flatpak/xdg-desktop-portal/issues/709

** Also affects: xdg-desktop-portal via
   https://github.com/flatpak/xdg-desktop-portal/issues/709
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1966386

Title:
  /usr/libexec/xdg-desktop-
  
portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

Status in xdg-desktop-portal:
  Unknown
Status in xdg-desktop-portal package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xdg-desktop-portal.  This problem was most recently seen with package version 
1.14.1-1, the problem page at 
https://errors.ubuntu.com/problem/34483c95acb7a7b00ab9e83731350bf5e4233db0 
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/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-desktop-portal/+bug/1966386/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966130] Re: xdg-desktop-portal crashed with SIGSEGV in map_pid_if_needed()

*** This bug is a duplicate of bug 1966386 ***
https://bugs.launchpad.net/bugs/1966386

** This bug has been marked a duplicate of bug 1966386
   
/usr/libexec/xdg-desktop-portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1966130

Title:
  xdg-desktop-portal crashed with SIGSEGV in map_pid_if_needed()

Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  This crash happens while starting Epiphany. Despite the crash, the
  browser seems to work correctly.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal 1.14.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 17:58:47 2022
  ExecutablePath: /usr/libexec/xdg-desktop-portal
  InstallationDate: Installed on 2020-02-26 (755 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225.4)
  ProcCmdline: /usr/libexec/xdg-desktop-portal
  SegvAnalysis:
   Segfault happened at: 0x564faad74421:mov0x8(%rax),%rcx
   PC (0x564faad74421) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xdg-desktop-portal
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo 
vboxusers wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966130/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966386] Re: /usr/libexec/xdg-desktop-portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

2022-03-25 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xdg-desktop-portal (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1966386

Title:
  /usr/libexec/xdg-desktop-
  
portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

Status in xdg-desktop-portal:
  Unknown
Status in xdg-desktop-portal package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xdg-desktop-portal.  This problem was most recently seen with package version 
1.14.1-1, the problem page at 
https://errors.ubuntu.com/problem/34483c95acb7a7b00ab9e83731350bf5e4233db0 
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/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-desktop-portal/+bug/1966386/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966386] [NEW] /usr/libexec/xdg-desktop-portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

2022-03-25 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xdg-desktop-portal.  This problem was most recently seen with package version 
1.14.1-1, the problem page at 
https://errors.ubuntu.com/problem/34483c95acb7a7b00ab9e83731350bf5e4233db0 
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: xdg-desktop-portal (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: jammy rls-jj-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1966386

Title:
  /usr/libexec/xdg-desktop-
  
portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

Status in xdg-desktop-portal package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xdg-desktop-portal.  This problem was most recently seen with package version 
1.14.1-1, the problem page at 
https://errors.ubuntu.com/problem/34483c95acb7a7b00ab9e83731350bf5e4233db0 
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/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966386/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966386] Re: /usr/libexec/xdg-desktop-portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

The issue seems to have started this cycle and the reports seem to be
coming from using epiphany so maybe something the client is doing wrong
leading to the crash?

** Changed in: xdg-desktop-portal (Ubuntu)
   Importance: Undecided => High

** Tags added: rls-jj-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1966386

Title:
  /usr/libexec/xdg-desktop-
  
portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int

Status in xdg-desktop-portal package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xdg-desktop-portal.  This problem was most recently seen with package version 
1.14.1-1, the problem page at 
https://errors.ubuntu.com/problem/34483c95acb7a7b00ab9e83731350bf5e4233db0 
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/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966386/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal

** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu Jammy)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: mutter (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: mutter (Ubuntu Jammy)
   Importance: Undecided => High

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2194
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2194

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2194
   Importance: Unknown
   Status: Unknown

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

Title:
  [jammy][regression] gnome-shell PolicyKit password prompt sends
   keys to the terminal

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-shell source package in Jammy:
  In Progress
Status in mutter source package in Jammy:
  In Progress

Bug description:
  This is a regression not seen until this week (not seen until March 4
  at least).  Calling debsign from a terminal pops up the window to
  enter the key, but the terminal is sent continuous  keys and
  the terminal scrolls down with empty input lines. You can still sign
  the file, however you end up with an empty scroll buffer if the
  signing takes too long time.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1951220] Re: Caja and Nautilus umacceptably slow for more than 50 files

Thank you for your bug report. What Ubuntu serie are you using and what
updates did you install that created the issue?

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

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

Title:
  Caja and Nautilus umacceptably slow for more than 50 files

Status in caja package in Ubuntu:
  Incomplete
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  The latest update of Caja seems to have replaced the existing
  algorithms with ones that do not scale. Right clicking takes >3
  minutes to open the menu if there are more than 300 files in the
  current folder. Opening a directory with 12,000 files takes so long
  that I get to catch up on my reading.

  Also Caja frequently crashes (even more often than Chrome).

  This was not a problem in earlier versions of Ubuntu MATE (18.04
  through 20.04.3 without the last 3 updates).

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966334] Re: GLVND: Set current thread state to NULL in teardown

Thank you for the bug report. It seems like a fix worth cherrypicking
but could you maybe give an example of impact the issue has which is
user visible? It would help especially for a stable update to have a
testcase to verify the fix and to justify the importance. If it's not
impacting anyone in a visible fashion then maybe it's not such an issue

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

Title:
  GLVND: Set current thread state to NULL in teardown

Status in libglvnd package in Ubuntu:
  Confirmed

Bug description:
  A new fix has been merged into the libglvnd repo at
  https://gitlab.freedesktop.org/glvnd/libglvnd

  This change fixes an issue where if eglReleaseThread gets externally called 
after the EGL destructor, a  double free occurs due to the threadState that 
eglReleaseThread checks is not null being not null despite being freed by the 
destuctor.
  The change makes the threadState null in the destructor to fix this.

  Can this make it into the libs in 20.04 LTS?

  Source package where the issue is encountered:
  https://launchpad.net/ubuntu/+source/libglvnd/1.3.2-1~ubuntu0.20.04.2

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1964545] Re: 42beta: moving mouse as screen is fading to screensaver prevents input to shell

2022-03-25 Thread Till Kamppeter

If this situation occurs for me and I press ALT + TAB then, I get back
to normal and can use mouse and keyboard as usual again.

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

Title:
  42beta: moving mouse as screen is fading to screensaver prevents input
  to shell

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Jammy:
  Triaged

Bug description:
  [Impact]

  If you move the mouse as the system fades into black for the
  screensaver, the screensaver will be prevented as normal, but the user
  will not be able to interact with the shell.

  Mouse clicks are ignored, and most key presses are ignored too.

  Workaround is to press super to enter shell overview, then super again
  to close, and mouse clicks will begin working again.

  gnome-shell 42~beta-1ubuntu2 from -proposed.

  [Testcase]

  1) Leave your system idle, until the screen starts fading to black
  2) As the screen is fading to black, move the mouse to prevent screensaver.
  3) Attempt to click any window or type something

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1964545] Re: 42beta: moving mouse as screen is fading to screensaver prevents input to shell