date:20220330

Sounds like bug 1832958 (https://github.com/micheleg/dash-to-
dock/issues/963) but I'm not sure because that one is difficult to
understand.

** Bug watch added: github.com/micheleg/dash-to-dock/issues #963
   https://github.com/micheleg/dash-to-dock/issues/963

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Glitch on multiple windows selector when auto-hide is enabled

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Currently testing a fresh install of the beta for 22.04.
  All packages are up to date.

  When having the dock auto-hide option enabled, a glitch occurs when opening 
the windows selector (when multiple instances of the same program are opened).
  The selector does open, but the dock will hide itself immediately instead of 
waiting for a selection. Selecting a window will then cause a glitch where the 
selector will align with the hidden dock in a non natural way before 
disappearing.

  A proposed fix would be to prevent the dock from auto-hiding when the
  miniatures selector opens and wait for a second input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967121/+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 1832958] Re: Quirky preview behavior when autohide is on

** No longer affects: dash-to-dock

** Bug watch removed: github.com/micheleg/dash-to-dock/issues #963
   https://github.com/micheleg/dash-to-dock/issues/963

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

Title:
  Quirky preview behavior when autohide is on

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  See details in my upstream report: https://github.com/micheleg/dash-
  to-dock/issues/963

  Also reporting here because it affects configurations supported by
  Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1832958/+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 1927948] Re: Windows switch monitor after resuming from sleep

See also bug 1778983.

** Tags removed: hirsute
** Tags added: jammy

** Changed in: gnome-shell (Ubuntu)
   Status: Won't Fix => Confirmed

** Changed in: mutter (Ubuntu)
   Status: Won't Fix => Confirmed

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

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

-- 
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/1927948

Title:
  Windows switch monitor after resuming from sleep

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  What I expect:

  Window layout/positioning is identical after resume from sleep.

  What I observe:

  After resume from sleep, windows appear on a different monitor than
  before.

  I found this possibly relevant GNOME bug:

  https://gitlab.gnome.org/GNOME/mutter/-/issues/1419

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mutter 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 10 13:40:28 2021
  InstallationDate: Installed on 2019-12-02 (524 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1927948/+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 1967182] Re: windows change desktop after lock screen

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1927948, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Tags added: multimonitor

** This bug has been marked a duplicate of bug 1927948
   Windows switch monitor after resuming from sleep

-- 
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/1967182

Title:
  windows change desktop after lock screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  So I have a dual screen setup where my primary monitor isn't the
  laptop built-in but an external wide screen.

  So I would have 2 or 3 virtual desktop with various content organized
  (mail, development, personal)

  After a long break with the screen locked when I come back to my
  computer, my windows have moved from Virtual desktop to another and
  sometime from one monitor to another.

  let me know if you need more information

  Matthieu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 16:44:57 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-01-05 (815 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-01-27 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967182/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

BTW the fix is two commits. It won't work if you only use the one
mentioned in comment #13.

-- 
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/1959888

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  When an external display is connected to my laptop, running Ubuntu
  22.04, the display is detected and I am sent to the login screen.
  After logging in again, the display is not running, although the
  primary laptop display works fine. The external monitor is looking for
  connection in that moment, which it never founds.

  The bug is tested on two Samsung monitors: S24R350FHUXEN and
  S22F350FHU.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  495.46  Wed Oct 27 16:31:33 
UTC 2021
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1)
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  3 13:25:04 2022
  DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/495.46, 5.15.0-17-generic, x86_64: installed
   nvidia/495.46, 5.15.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f]
  InstallationDate: Installed on 2021-09-09 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. G3 3579
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.109-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  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/mutter/+bug/1959888/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

The crash is bug 1964037 but it's the same fix for this bug. I'll
proposed a distro patch to mutter soon because it seems fairly common
that people plug a monitor into their hybrid laptop.

-- 
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/1959888

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  When an external display is connected to my laptop, running Ubuntu
  22.04, the display is detected and I am sent to the login screen.
  After logging in again, the display is not running, although the
  primary laptop display works fine. The external monitor is looking for
  connection in that moment, which it never founds.

  The bug is tested on two Samsung monitors: S24R350FHUXEN and
  S22F350FHU.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  495.46  Wed Oct 27 16:31:33 
UTC 2021
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1)
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  3 13:25:04 2022
  DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/495.46, 5.15.0-17-generic, x86_64: installed
   nvidia/495.46, 5.15.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f]
  InstallationDate: Installed on 2021-09-09 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. G3 3579
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.109-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  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/mutter/+bug/1959888/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

2022-03-30 Thread jeremyszu

Follow-up from comment#12, I can reproduce this issue on I+N (external
hdmi port wires to dGPU) on DELL-Precision-7760.

---
 三  31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc27c980 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce0075bc40 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce0075bc40 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce0075bf50 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:41 ubuntu-Precision-7760 gnome-shell[2492]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
 三  31 10:57:41 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: 
assertion 'width > 0' failed
 三  31 10:57:42 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: 
assertion 'width > 0' failed
 三  31 10:57:42 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: 
assertion 'width > 0' failed
 三  31 10:57:42 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: 
assertion 'width > 0' failed
 三  31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faf74004130 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce03b87330 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55cdffba6760 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc2f7df0 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc23df40 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: Created gbm renderer 
for '/dev/dri/card1'
 三  31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: Failed to allocate 
onscreen framebuffer for /dev/dri/card1: Failed to create gbm_surface: 
Operation not permitted
 三  31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: GNOME Shell crashed 
with signal 5
 三  31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: == Stack trace for 
context 0x55cdfef5c180 ==
 三  31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: Failed to create 
fallback offscreen framebuffer: Failed to create texture 2d due to size/format 
constraint
...
 三  31 10:57:56 ubuntu-Precision-7760 gnome-shell[5958]: Running GNOME Shell 
(using mutter 42.beta) as a Wayland display server
---

Which also break the auto-login feature (after auto-login, gnome restart
then screen back to gdm login shell)

$ dpkg -l | grep mutter
ii  gir1.2-mutter-10:amd64 42~beta-1ubuntu2 
   amd64GObject introspection data for Mutter
ii  libmutter-10-0:amd64   42~beta-1ubuntu2 
   amd64window manager library from the Mutter window manager
ii  mutter-common  42~beta-1ubuntu2 
   all  shared files for the Mutter window manager

Hi Daniel,

Do you have a PPA could try your patch like this
https://gitlab.gnome.org/vanvugt/mutter/-/commit/8354289650aa3ae0c531820d3a95251b627f9eb4
?

** Changed in: oem-priority
   Status: New => Confirmed

-- 
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/1959888

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  When an external display is connected to my laptop, running Ubuntu
  22.04, the display is detected and I am sent to the login screen.
  After logging in again, the display is not running, although the
  primary laptop display works fine. The external monitor is looking for
  connection in that moment, which it never founds.

  The bug is tested on two Samsung monitors: S24R350FHUXEN and
  S22F350FHU.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux

[Desktop-packages] [Bug 1967204] Re: "help" app (yelp) just displays a blank window with "Ubuntu Desktop Guide" title on rpi

2022-03-30 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1967204

** Tags added: iso-testing

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

Title:
  "help" app (yelp) just displays a blank window with "Ubuntu Desktop
  Guide" title on rpi

Status in yelp package in Ubuntu:
  New

Bug description:
  I'm using the jammy beta (20220329) image running on an rpi4 8GB
  clicking on the "help" app in the dock launches a window with the title 
"Ubuntu Desktop Guide". The icons for forward/back, bookmarks, search, etc. are 
all visible at the top of the window, but everything else in the window is just 
a blank white area. On amd64, however, it seems to work fine.

  I also noticed that if I move the mouse around through the area, the
  pointer sometimes changes, and if I hover there for a second, a
  tooltip comes up with things like "Start applications" or "Visual
  overview of Gnome". I can click on these and it seems to take me
  forward to something, because the back icon is no longer greyed out,
  but I still can't see any content in the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yelp 42.0-1
  ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19
  Uname: Linux 5.15.0-1003-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 21:47:52 2022
  ImageMediaBuild: 20220329
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1967204/+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 1964724] Re: the laptop is slowing down I suspect the graphics

Thanks for the bug report.

You seem to be using graphics packages that are not from Ubuntu, but
from the "oibaf" PPA. That's unsupported and known to cause bugs like
this.

Please remove the PPA from your system and then open new bugs if you
encounter further problems.


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

** Changed in: ubuntu
   Status: New => Invalid

-- 
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/1964724

Title:
  the laptop is slowing down I suspect the graphics

Status in Ubuntu:
  Invalid

Bug description:
  I am sure that the video driver does not work because it is very
  stupid

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-36.41~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 14 01:26:27 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:081b]
  InstallationDate: Installed on 2022-03-11 (2 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Acer Aspire V5-132P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-36-generic 
root=UUID=3ed9b8cd-2125-43f4-af3a-b14a5314ae6e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 07/19/2013
  dmi.bios.release: 2.4
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.04
  dmi.board.name: Angel_CY
  dmi.board.vendor: Acer
  dmi.board.version: V2.04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.04
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.04:bd07/19/2013:br2.4:efr1.5:svnAcer:pnAspireV5-132P:pvrV2.04:rvnAcer:rnAngel_CY:rvrV2.04:cvnAcer:ct9:cvrV2.04:skuAspireV5-132P_081B_2.04:
  dmi.product.family: Aspire V5-132P
  dmi.product.name: Aspire V5-132P
  dmi.product.sku: Aspire V5-132P_081B_2.04
  dmi.product.version: V2.04
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110+git2203100500.7c28f5~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.1~git2203130600.177805~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1964724/+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 1967204] [NEW] "help" app (yelp) just displays a blank window with "Ubuntu Desktop Guide" title on rpi

Public bug reported:

I'm using the jammy beta (20220329) image running on an rpi4 8GB
clicking on the "help" app in the dock launches a window with the title "Ubuntu 
Desktop Guide". The icons for forward/back, bookmarks, search, etc. are all 
visible at the top of the window, but everything else in the window is just a 
blank white area. On amd64, however, it seems to work fine.

I also noticed that if I move the mouse around through the area, the
pointer sometimes changes, and if I hover there for a second, a tooltip
comes up with things like "Start applications" or "Visual overview of
Gnome". I can click on these and it seems to take me forward to
something, because the back icon is no longer greyed out, but I still
can't see any content in the window.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: yelp 42.0-1
ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19
Uname: Linux 5.15.0-1003-raspi aarch64
ApportVersion: 2.20.11-0ubuntu79
Architecture: arm64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 21:47:52 2022
ImageMediaBuild: 20220329
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: yelp
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 arm64-image iso-testing jammy raspi-image 
wayland-session

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

Title:
  "help" app (yelp) just displays a blank window with "Ubuntu Desktop
  Guide" title on rpi

Status in yelp package in Ubuntu:
  New

Bug description:
  I'm using the jammy beta (20220329) image running on an rpi4 8GB
  clicking on the "help" app in the dock launches a window with the title 
"Ubuntu Desktop Guide". The icons for forward/back, bookmarks, search, etc. are 
all visible at the top of the window, but everything else in the window is just 
a blank white area. On amd64, however, it seems to work fine.

  I also noticed that if I move the mouse around through the area, the
  pointer sometimes changes, and if I hover there for a second, a
  tooltip comes up with things like "Start applications" or "Visual
  overview of Gnome". I can click on these and it seems to take me
  forward to something, because the back icon is no longer greyed out,
  but I still can't see any content in the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yelp 42.0-1
  ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19
  Uname: Linux 5.15.0-1003-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 21:47:52 2022
  ImageMediaBuild: 20220329
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1967204/+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 1967150] Re: gnome-shell crashed with SIGSEGV

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1964458, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1964458
   [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from 
js::gc::PostWriteBarrierImpl

-- 
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/1967150

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This was running a live session of the jammy beta candidate image
  20220329.1 in qemu. I let it sit for a bit after booting, came back to
  the session and came out of the screen blank and saw it reporting this
  crash had occurred.  The session has been up 41 minutes but the files
  in /var/crash are timestamped from just a few minutes ago so I think
  it may have happened coming out of the screen blank.

  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
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 14:31:13 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C.UTF-8
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SegvAnalysis:
   Segfault happened at: 0x7f8255af2f44:mov(%rsi),%rax
   PC (0x7f8255af2f44) ok
   source "(%rsi)" (0x35d82c10) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f8255af2f44 in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
  StacktraceTop: ?? ()
  Title: gnome-shell 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-shell/+bug/1967150/+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 1967176] Re: gnome-shell crashed with SIGSEGV

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace).
This might be caused by some outdated packages which were installed on
your system at the time of the report. Please upgrade your system to the
latest package versions. If you still encounter the crash, please file a
new report.

Thank you for your understanding, and sorry for the inconvenience!


** Changed in: gnome-shell (Ubuntu)
   Status: New => Invalid

-- 
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/1967176

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  2) apt-cache policy gnome-shell
  gnome-shell:
Installed: 42~beta-1ubuntu3
Candidate: 42~beta-1ubuntu3
Version table:
   *** 42~beta-1ubuntu3 500
  500 http://mirror.docker.ru/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  nvidia 1030. nvidia-driver-510

  3) What you expected to happen
  just logout and login again

  4) What happened instead
  after logout and login again, apport reported this crash.

  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
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 22:40:45 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-25 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7ffbc79eda7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60
  StacktraceTop: ?? ()
  Title: gnome-shell 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-shell/+bug/1967176/+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 1966905] Re: Valgrind memory errors in gnome-shell 42 from accountsservice

I never narrowed down the test case to reproduce this -- it just
happened once in every few attempts to valgrind gnome-shell.

-- 
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/1966905

Title:
  Valgrind memory errors in gnome-shell 42 from accountsservice

Status in accountsservice:
  Unknown
Status in accountsservice package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511== 
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)

[Desktop-packages] [Bug 1966921] Re: Display freezes after entering password from login screen

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

-- 
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/1966921

Title:
  Display freezes after entering password from login screen

Status in mutter package in Ubuntu:
  Invalid

Bug description:
  The display freezes with the same background colour as the login
  screen. The mouse pointer no longer moves. I was unable to change to
  another VT when the display freezes. Only a press of the power button
  seemed to make the laptop respond by triggering a shutdown.

  I've had to switch to "GNOME on Xorg" to be able to login/see the
  desktop. Wayland was working fine until some time around the last
  week.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42~beta-1ubuntu2
  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: GNOME
  Date: Tue Mar 29 18:34:41 2022
  InstallationDate: Installed on 2021-09-13 (196 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966921/+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 1967174] Re: Installing with zfs results in bpool, rpool drives locked on the dock

Please try:

  gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts
false


** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Installing with zfs results in bpool, rpool drives locked on the dock

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I installed the ubuntu 20220329 jammy beta with zfs root selected.
  After installation, there are drives on the dock for the zfs bpool and
  rpool (and in my case also a "1.6GB Encrypted" device since I also
  selected disk encryption at install time). These don't do anything
  useful when you click on them, and the only option when right-clicking
  is to mount them, which also doesn't result in anything observable
  from the UI (indeed, they should already be in use). Nor are they
  removable or 'un-pinnable' from the dock. You're just stuck with them
  taking up space.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 13:25:07 2022
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967174/+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 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen

** Tags added: impish

-- 
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/1882353

Title:
  Ubuntu Dock and Top bar accessible from lockscreen

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  This is a very serious security issue:

  When I lock my desktop with SUPER (windows) + L my screen gets locked
  and goes to black. Sometimes when I return to my PC and move my mouse
  to turn my screen back on I notice that the Ubuntu Dock + the Top Bar
  are accessible from the lockscreen.

  I unfortunately can't remember if they were accessible from the moment
  I locked the screen or became accessible after returning from fade to
  black. (This is not the first time this issue happened.)

  I was able to open the settings menu from the top bar and use all
  indicators. You can actually start the programs in the Ubuntu Dock and
  give keyboard inputs to them. For example I was able to start the
  terminal emulator from the lock screen and run firefox and other
  applications. So an attacker could run arbitrary commands with user
  privileges from the lockscreen!

  The indicators drop down menus were fully visible on the lock screen
  while the Dock applications remained hidden "behind" the lockscreen
  (however still accessible via keyboard as described above).

  I have attached a screenshot of the bug. I unfortunately had no camera
  at hand to film me running terminal commands.

  Please contact me if you need additional information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 13:35:28 2020
  InstallationDate: Installed on 2015-12-22 (1627 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1882353/+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 1965686] Re: After the laptop comes out of sleep mode, the desktop environment for some reason breaks and appears crashes window

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

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

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

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

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


** Package changed: gnome-shell (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

-- 
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/1965686

Title:
  After the laptop comes out of sleep mode, the desktop environment for
  some reason breaks and appears crashes window

Status in Ubuntu:
  Incomplete

Bug description:

  I've been running Ubuntu 20.04 for about a month now. Lock screen is
  crashing the UI in 20.04.

  I don't know how to stop crashing my screen so I forcefully press
  power off button and turn on again my computer every time I use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 22:26:56 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-18 (61 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1965686/+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 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen

2022-03-30 Thread Launchpad Bug Tracker

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

-- 
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/1882353

Title:
  Ubuntu Dock and Top bar accessible from lockscreen

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  This is a very serious security issue:

  When I lock my desktop with SUPER (windows) + L my screen gets locked
  and goes to black. Sometimes when I return to my PC and move my mouse
  to turn my screen back on I notice that the Ubuntu Dock + the Top Bar
  are accessible from the lockscreen.

  I unfortunately can't remember if they were accessible from the moment
  I locked the screen or became accessible after returning from fade to
  black. (This is not the first time this issue happened.)

  I was able to open the settings menu from the top bar and use all
  indicators. You can actually start the programs in the Ubuntu Dock and
  give keyboard inputs to them. For example I was able to start the
  terminal emulator from the lock screen and run firefox and other
  applications. So an attacker could run arbitrary commands with user
  privileges from the lockscreen!

  The indicators drop down menus were fully visible on the lock screen
  while the Dock applications remained hidden "behind" the lockscreen
  (however still accessible via keyboard as described above).

  I have attached a screenshot of the bug. I unfortunately had no camera
  at hand to film me running terminal commands.

  Please contact me if you need additional information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 13:35:28 2020
  InstallationDate: Installed on 2015-12-22 (1627 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1882353/+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 1965869] Re: Screen only partially locked. Password promt was visible, but switching to window and typing eg in terminal was possible

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1882353, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1882353
   Ubuntu Dock and Top bar accessible from lockscreen

-- 
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/1965869

Title:
  Screen only partially locked. Password promt was visible, but
  switching to window and typing eg in terminal was possible

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Today I returned to my PC, which was on over night.

  The screen was only partially locked. The password prompt was full
  screen except the start menu on the left was visible. I was able to
  click on the Icons of running applications and was able to type in an
  open terminal which responded correctly and executed the commands (I
  tried "reset").

  I have no Idea what can cause this issue and would appreciate help on
  how to gather information that can help the Ubuntu team find the cause
  of the issue.

  I saved copies of dmesg, syslog and kern.log.
  I have not tried reproducing the bug.
  I do not know if I actively locked the screen or if I just walked off 
yesterday.

  Best Regards,
  Chris

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 22 08:16:18 2022
  InstallationDate: Installed on 2021-12-13 (98 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  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/1965869/+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 1965563] Re: gnome-extensions-app fails to start (Protocol error)

So this is GTK only? GTK4 only?

-- 
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/1965563

Title:
  gnome-extensions-app fails to start (Protocol error)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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)"

We should confirm whether gnome-chess has the same stack trace (hence
comment #3). According to comment #4, the original reporter is only
confirmed to have encountered bug 1965897. So the gnome-chess issue
might be off-topic here.

-- 
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 Mesa:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  In Progress

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/mesa/+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 1967079] Re: gnome-shell crashed with SIGSEGV in app_info_has_action() from g_desktop_app_info_launch_action()

I meant that if you can reproduce the crash then please try disabling
ubuntu-d...@ubuntu.com

Otherwise we should still keep this bug open to avoid duplicates (and
increase collaboration) when the next person encounters the crash.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967079/+attachment/5574678/+files/CoreDump.gz

** Information type changed from Private to Public

-- 
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/1967079

Title:
  gnome-shell crashed with SIGSEGV in app_info_has_action() from
  g_desktop_app_info_launch_action()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Error occurred on initial login to system

  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 09:35:17 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-29 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_desktop_app_info_launch_action () from 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
   shell_app_launch_action () from /usr/lib/gnome-shell/libgnome-shell.so
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_desktop_app_info_launch_action()
  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-shell/+bug/1967079/+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 1967198] [NEW] gnome-initial-setup icon in dock is badly sized

Public bug reported:

I noticed this while testing the beta jammy image (20220329) on arm64,
but I checked and I see the same issue on amd64 as well. The best way I
can describe it, is that it looks squished, as if it was sized
incorrectly. I'll attach a screenshot showing the problem also.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-initial-setup 42.0.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19
Uname: Linux 5.15.0-1003-raspi aarch64
ApportVersion: 2.20.11-0ubuntu79
Architecture: arm64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 21:12:45 2022
ImageMediaBuild: 20220329
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 arm64-image jammy raspi-image wayland-session

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

Title:
  gnome-initial-setup icon in dock is badly sized

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  I noticed this while testing the beta jammy image (20220329) on arm64,
  but I checked and I see the same issue on amd64 as well. The best way
  I can describe it, is that it looks squished, as if it was sized
  incorrectly. I'll attach a screenshot showing the problem also.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-initial-setup 42.0.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19
  Uname: Linux 5.15.0-1003-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 21:12:45 2022
  ImageMediaBuild: 20220329
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1967198/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Committed

** Tags added: fixed-in-42.1 fixed-upstream

-- 
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/1959888

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  When an external display is connected to my laptop, running Ubuntu
  22.04, the display is detected and I am sent to the login screen.
  After logging in again, the display is not running, although the
  primary laptop display works fine. The external monitor is looking for
  connection in that moment, which it never founds.

  The bug is tested on two Samsung monitors: S24R350FHUXEN and
  S22F350FHU.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  495.46  Wed Oct 27 16:31:33 
UTC 2021
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1)
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  3 13:25:04 2022
  DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/495.46, 5.15.0-17-generic, x86_64: installed
   nvidia/495.46, 5.15.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f]
  InstallationDate: Installed on 2021-09-09 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. G3 3579
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.109-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  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/mutter/+bug/1959888/+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

Fixed in mutter 42.1 but we should probably patch it in sooner than that
for jammy.

** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Committed

** Tags added: fixed-in-42.1 fixed-upstream

-- 
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:
  Fix Committed

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 1964541] Re: Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 (Wayland session)

I attempted to bisect mutter for this but could not get the firefox snap
binaries to run at all in my development builds. Missing some
environment created by a proper login I guess, so what environment is
required for snaps?

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

Title:
  Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell
  42 (Wayland session)

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.

  syslog has the following:

  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.

  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1964541/+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 1931902] Re: [AMD Ellesmere] Crackling sound on Pulseaudio

2022-03-30 Thread Matheus Reich

The issue goes away when speech-dispatcher is uninstalled, meaning that
this package is related to the bug in question, and is resolved once it
is removed.

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

Title:
  [AMD Ellesmere] Crackling sound on Pulseaudio

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  While playing back any sounds, a certain crackling sound (static) will
  play with a fixed delay of the sound being played. The amount and
  volume of the static will depend on the sound/music that is being
  played, and this only starts occurring after a somewhat long time (30
  minutes or more). What is interesting to see is that while playing
  back music from Spotify (Snap) the static will only start after a
  second or so, but when playing YouTube videos on Firefox, it will be
  immediate and output that static while the video is playing.

  I've added two sound recordings, one while playing back a song from
  Spotify and the other while playing a song from YouTube. This issue
  goes away when restarting the PulseAudio service, but it comes back
  after a random amount of time.

  1) Description:   Ubuntu 21.04
  Release:  21.04

  2) pulseaudio:
Installed: 1:14.2-1ubuntu1
Candidate: 1:14.2-1ubuntu1
Version table:
   1:14.2-1ubuntu1.1 1 (phased 10%)
  500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:14.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  matheus   18662 F pulseaudio
   /dev/snd/controlC2:  matheus   18662 F pulseaudio
   /dev/snd/controlC0:  matheus   18662 F pulseaudio
   /dev/snd/pcmC0D8p:   matheus   18662 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 14 16:58:43 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-05-03 (41 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931902/+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 1931902] Re: [AMD Ellesmere] Crackling sound on Pulseaudio

2022-03-30 Thread Matheus Reich

@ppq

I've actually been able to determine what the issue was. The speech-
dispatcher package is the one causing issues. It is possible to
uninstall it from any Ubuntu installation (or Ubuntu-based distros). But
to make sure that indeed this is what is causing the issue in your case,
try to run this command on your Terminal:

speech-dispatcher -K

And check if the crackling noise will go away. If it does, uninstall it
using apt:

sudo apt remove speech-dispatcher (or replace remove with autoremove if
you want to also uninstall any packages related to speech-dispatcher).

It seems that this package will stop behaving correctly after some time
with the system running, and will interfere with everything that
pulseaudio will output.

** Also affects: speech-dispatcher (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1931902

Title:
  [AMD Ellesmere] Crackling sound on Pulseaudio

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  While playing back any sounds, a certain crackling sound (static) will
  play with a fixed delay of the sound being played. The amount and
  volume of the static will depend on the sound/music that is being
  played, and this only starts occurring after a somewhat long time (30
  minutes or more). What is interesting to see is that while playing
  back music from Spotify (Snap) the static will only start after a
  second or so, but when playing YouTube videos on Firefox, it will be
  immediate and output that static while the video is playing.

  I've added two sound recordings, one while playing back a song from
  Spotify and the other while playing a song from YouTube. This issue
  goes away when restarting the PulseAudio service, but it comes back
  after a random amount of time.

  1) Description:   Ubuntu 21.04
  Release:  21.04

  2) pulseaudio:
Installed: 1:14.2-1ubuntu1
Candidate: 1:14.2-1ubuntu1
Version table:
   1:14.2-1ubuntu1.1 1 (phased 10%)
  500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:14.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  matheus   18662 F pulseaudio
   /dev/snd/controlC2:  matheus   18662 F pulseaudio
   /dev/snd/controlC0:  matheus   18662 F pulseaudio
   /dev/snd/pcmC0D8p:   matheus   18662 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 14 16:58:43 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-05-03 (41 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931902/+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

2022-03-30 Thread Aidan Foster

I do think it is worth mentioning that since it is a in issue that shows
up in the Vulkan CTS, it is likely that it will also show up in other
applications. It may also occur on other platforms, but the two I listed
are the only ones that I confirmed the issue is reproducing on.

-- 
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 1931902] Re: [AMD Ellesmere] Crackling sound on Pulseaudio

2022-03-30 Thread ppq

I am experiencing this issue in Xubuntu 22.04, pulseaudio 
1:15.99.1+dfsg1-1ubuntu1, with this Hardware: 
GIGABYTE B550I AORUS Pro AX (BIOS F15 with AGESA ComboV2 1.2.0.5); 
Ryzen 7 5700G (Cezanne) with integrated graphics; 
audio output via HDMI (mainboard).

-- 
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/1931902

Title:
  [AMD Ellesmere] Crackling sound on Pulseaudio

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  While playing back any sounds, a certain crackling sound (static) will
  play with a fixed delay of the sound being played. The amount and
  volume of the static will depend on the sound/music that is being
  played, and this only starts occurring after a somewhat long time (30
  minutes or more). What is interesting to see is that while playing
  back music from Spotify (Snap) the static will only start after a
  second or so, but when playing YouTube videos on Firefox, it will be
  immediate and output that static while the video is playing.

  I've added two sound recordings, one while playing back a song from
  Spotify and the other while playing a song from YouTube. This issue
  goes away when restarting the PulseAudio service, but it comes back
  after a random amount of time.

  1) Description:   Ubuntu 21.04
  Release:  21.04

  2) pulseaudio:
Installed: 1:14.2-1ubuntu1
Candidate: 1:14.2-1ubuntu1
Version table:
   1:14.2-1ubuntu1.1 1 (phased 10%)
  500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:14.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  matheus   18662 F pulseaudio
   /dev/snd/controlC2:  matheus   18662 F pulseaudio
   /dev/snd/controlC0:  matheus   18662 F pulseaudio
   /dev/snd/pcmC0D8p:   matheus   18662 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 14 16:58:43 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-05-03 (41 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931902/+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 1966572] Re: Chromium Zero Day

2022-03-30 Thread B[]

I re-read the front page and apparently the PPA is managed on GitHub,
I've opened a ticket [1] over there and pointed it back to this one.

[1] https://github.com/saiarcot895/chromium-ubuntu-build/issues/123

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

Title:
  Chromium Zero Day

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Please see: https://chromereleases.googleblog.com/2022/03/stable-
  channel-update-for-desktop_25.html

  Apparently this also affects the Chromium package and is being
  actively exploited in the wild:

  > [$TBD][1309225] High CVE-2022-1096: Type Confusion in V8. Reported
  by anonymous on 2022-03-23

  Please update from Version 97.0.4692.20 (last updated 2021-11-26) to
  latest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1966572/+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 1966572] Re: Chromium Zero Day

2022-03-30 Thread B[]

@seth-arnold I'm not sure snap does think it has the package?

```
$ apt-file show chromium-browser
chromium-browser: /usr/bin/chromium-browser
chromium-browser: /usr/share/applications/chromium-browser.desktop
chromium-browser: /usr/share/apport/package-hooks/chromium-browser.py
chromium-browser: /usr/share/doc/chromium-browser/changelog.Debian.gz
chromium-browser: /usr/share/doc/chromium-browser/copyright
chromium-browser: /usr/share/icons/hicolor/128x128/apps/chromium-browser.png
chromium-browser: /usr/share/icons/hicolor/22x22/apps/chromium-browser.png
chromium-browser: /usr/share/icons/hicolor/24x24/apps/chromium-browser.png
chromium-browser: /usr/share/icons/hicolor/256x256/apps/chromium-browser.png
chromium-browser: /usr/share/icons/hicolor/48x48/apps/chromium-browser.png
chromium-browser: /usr/share/icons/hicolor/64x64/apps/chromium-browser.png
chromium-browser: /usr/share/lintian/overrides/chromium-browser
chromium-browser: /usr/share/pixmaps/chromium-browser.png
```

```
$ sudo snap refresh
All snaps up to date.
```

```
$ sudo snap list
Name   Version  RevTracking Publisher   Notes
bare   1.0  5  latest/stablecanonical✓  base
core18 20220309 2344   latest/stablecanonical✓  base
gnome-3-34-18040+git.3556cb377 latest/stable/…  canonical✓  -
gtk-common-themes  0.1-59-g7bca6ae  1519   latest/stable/…  canonical✓  -
snapd  2.54.4   15177  latest/stablecanonical✓  snapd
```

As far as I can tell, snap doesn't think it has control over Chromium.
Unless apt somehow hides its control over Chromium (which would seem
weird).

Running `sudo apt-get update && sudo apt-get upgrade` I also get no
offer to upgrade Chromium.

I should also mention that I specifically run this version:
https://launchpad.net/%7Esaiarcot895/+archive/ubuntu/chromium-beta

** Bug watch added: github.com/saiarcot895/chromium-ubuntu-build/issues #123
   https://github.com/saiarcot895/chromium-ubuntu-build/issues/123

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

Title:
  Chromium Zero Day

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Please see: https://chromereleases.googleblog.com/2022/03/stable-
  channel-update-for-desktop_25.html

  Apparently this also affects the Chromium package and is being
  actively exploited in the wild:

  > [$TBD][1309225] High CVE-2022-1096: Type Confusion in V8. Reported
  by anonymous on 2022-03-23

  Please update from Version 97.0.4692.20 (last updated 2021-11-26) to
  latest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1966572/+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 1965563] Re: gnome-extensions-app fails to start (Protocol error)

2022-03-30 Thread Gunnar Hjalmarsson

I see a similar error message when trying to start yelp:

$ yelp
Gdk-Message: 01:23:31.232: Error flushing display: Protocol error
$ gnome-extensions-app
Gdk-Message: 01:23:48.075: Error reading events from display: Protocol error

-- 
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/1965563

Title:
  gnome-extensions-app fails to start (Protocol error)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1966572] Re: Chromium Zero Day

2022-03-30 Thread Seth Arnold

The 20.04 LTS chromium-browser deb package exists only to install the
chromium snap and deliver a few files to the filesystem outside the snap
packaging system:

$ apt-file show chromium-browser
chromium-browser: /usr/bin/chromium-browser
chromium-browser: /usr/share/applications/chromium-browser.desktop
chromium-browser: /usr/share/apport/package-hooks/chromium-browser.py
chromium-browser: /usr/share/doc/chromium-browser/changelog.Debian.gz
chromium-browser: /usr/share/doc/chromium-browser/copyright
chromium-browser: /usr/share/icons/hicolor/128x128/apps/chromium-browser.png
chromium-browser: /usr/share/icons/hicolor/22x22/apps/chromium-browser.png
chromium-browser: /usr/share/icons/hicolor/24x24/apps/chromium-browser.png
chromium-browser: /usr/share/icons/hicolor/256x256/apps/chromium-browser.png
chromium-browser: /usr/share/icons/hicolor/48x48/apps/chromium-browser.png
chromium-browser: /usr/share/icons/hicolor/64x64/apps/chromium-browser.png
chromium-browser: /usr/share/lintian/overrides/chromium-browser
chromium-browser: /usr/share/pixmaps/chromium-browser.png
$ 

The deb package doesn't need to be updated for snapd to automatically
install a chromium update when one is made available.

Check snap info chromium on your system to see if you've received the
update yet.

Thanks

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

Title:
  Chromium Zero Day

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Please see: https://chromereleases.googleblog.com/2022/03/stable-
  channel-update-for-desktop_25.html

  Apparently this also affects the Chromium package and is being
  actively exploited in the wild:

  > [$TBD][1309225] High CVE-2022-1096: Type Confusion in V8. Reported
  by anonymous on 2022-03-23

  Please update from Version 97.0.4692.20 (last updated 2021-11-26) to
  latest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1966572/+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 1966572] Re: Chromium Zero Day

2022-03-30 Thread B[]

@mdeslaur I see that the fix appears to be specifically for Ubuntu 18.04
LTS. The Chromium Browser package [1] appears to also support 20.04 LTS.
Should this be marked as 'Fix Released' before all affected versions
have a release?

[1] https://launchpad.net/ubuntu/+source/chromium-browser

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

Title:
  Chromium Zero Day

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Please see: https://chromereleases.googleblog.com/2022/03/stable-
  channel-update-for-desktop_25.html

  Apparently this also affects the Chromium package and is being
  actively exploited in the wild:

  > [$TBD][1309225] High CVE-2022-1096: Type Confusion in V8. Reported
  by anonymous on 2022-03-23

  Please update from Version 97.0.4692.20 (last updated 2021-11-26) to
  latest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1966572/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share

2022-03-30 Thread Matthew Ruffell

Hi everyone, Fady, renbag,

I have been working on this bug on and off for a little while now, but I
am stuck because I can't reproduce what you are all seeing. Having a
reproducer will greatly speed up getting a fix created for this issue.

In my client gvfsd is always started via systemd --user, so I must be
configuring something differently. Can you try out my reproducer and let
me know what you are configuring differently?

Instructions to reproduce:

You will need a 20.04 server instance, and a 20.04 Desktop instance.

To set up the server:

1) Create a fresh 20.04 server instance
2) sudo apt update
3) sudo apt upgrade
4) sudo hostnamectl set-hostname samba-dc
5) sudo vim /etc/hosts
Add an entry with its IP address, e.g.:
192.168.122.199samba-dc samba-dc.example.com
6) sudo apt install -y samba smbclient winbind libpam-winbind libnss-winbind 
krb5-kdc libpam-krb5
Note: skip config of kerberos KDC.
7) sudo rm /etc/krb5.conf
8) sudo rm /etc/samba/smb.conf
9) sudo samba-tool domain provision --server-role=dc --use-rfc2307 
--dns-backend=SAMBA_INTERNAL --realm=samba-dc.EXAMPLE.COM --domain=SAMBA 
--adminpass=Password1
10) sudo cp /var/lib/samba/private/krb5.conf /etc/krb5.conf
11) sudo systemctl mask smbd nmbd winbind
12) sudo systemctl disable smbd nmbd winbind
13) sudo systemctl stop smbd nmbd winbind
14) sudo systemctl unmask samba-ad-dc
15) sudo systemctl start samba-ad-dc
16) sudo systemctl enable samba-ad-dc
17) sudo reboot
18) sudo systemctl stop systemd-resolved
19) sudo systemctl disable systemd-resolved
20) cat << EOF >> /etc/resolv.conf
nameserver 192.168.122.199
search SAMBA
EOF
21) sudo reboot
22) host -t SRV _ldap._tcp.samba-dc.example.com
_ldap._tcp.samba-dc.example.com has SRV record 0 100 389 
samba-dc.samba-dc.example.com.
23) $ smbclient -L localhost -N
Anonymous login successful

Sharename   Type  Comment
-     ---
sysvol  Disk  
netlogonDisk  
IPC$IPC   IPC Service (Samba 4.13.17-Ubuntu)
SMB1 disabled -- no workgroup available
24) $ smbclient //localhost/netlogon -UAdministrator -c 'ls'
Enter SAMBA\Administrator's password: 
  .   D0  Mon Feb 28 04:23:22 2022
  ..  D0  Mon Feb 28 04:23:27 2022

9983232 blocks of size 1024. 7995324 blocks available
25) kinit administrator
Password for administra...@samba-dc.example.com: 
Warning: Your password will expire in 41 days on Mon Apr 11 04:23:27 2022
26) klist
Ticket cache: FILE:/tmp/krb5cc_1000
Default principal: administra...@samba-dc.example.com

Valid starting ExpiresService principal
02/28/22 04:32:47  02/28/22 14:32:47  
krbtgt/samba-dc.example@samba-dc.example.com
renew until 03/01/22 04:32:44
27)


Create a share:
28) sudo mkdir -p /srv/samba/Demo/
29) sudo vim /etc/samba/smb.conf
[Demo]
path = /srv/samba/Demo/
read only = no
30) sudo chmod 0770 /srv/samba/Demo/


Install a fresh 20.04.4 Desktop instance, and run the following:

31) sudo apt install realmd smbclient
32) sudo vim /etc/hosts
Add an entry with its IP address, e.g.:
192.168.122.199samba-dc samba-dc.example.com
33) sudo realm join --user=Administrator SAMBA-DC.EXAMPLE.COM
$ smbclient -U Administrator //samba-dc.example.com/demo
Enter WORKGROUP\Administrator's password: 
Try "help" to get a list of possible commands.
smb: \> ls
  .   D0  Mon Mar  7 15:20:30 2022
  ..  D0  Mon Mar  7 15:20:30 2022

9983232 blocks of size 1024. 7686220 blocks available
$ smbclient //samba-dc.example.com/demo -k
gensec_spnego_client_negTokenInit_step: Could not find a suitable mechtype in 
NEG_TOKEN_INIT
session setup failed: NT_STATUS_INVALID_PARAMETER

Now open Nautilus, add smb://samba-dc.example.com/demo as a share, and you will
be faced with a dialog box asking for username / password credentials. Close
Nautilus.

Let's get a kerberos ticket:

$ kinit administra...@samba-dc.example.com
Password for administra...@samba-dc.example.com: 
Warning: Your password will expire in 11 days on Mon 11 Apr 2022 16:23:27
$ smbclient //samba-dc.example.com/demo -k
Try "help" to get a list of possible commands.
smb: \> ls
  .   D0  Mon Mar  7 15:20:30 2022
  ..  D0  Mon Mar  7 15:20:30 2022

9983232 blocks of size 1024. 7616832 blocks available

34) Open Nautilus, add smb://samba-dc.example.com/demo as a share, and it will
open correctly using kerberos credentials.

When I look at my process list, gvfsd is where it is suppose to be, under the
systemd user session:

$ ps auxf
...
ubuntu  1207  0.5  0.2  19008 10128 ?Ss   12:12   0:00 
/lib/systemd/systemd --user
ubuntu  1208  0.0  0.0 179632  3544 ?S12:12   0:00  \_ (sd-pam)
ubuntu

[Desktop-packages] [Bug 1954413] Re: firefox snap cannot be started: firefox already running

2022-03-30 Thread Samuel Walladge

I have a similar issue (let me know if I should open a new bug):
launching firefox for the first time (ie. while it's not running) works
fine.  But, once it's running, any further invocation of firefox fails
with the "Firefox is already running..." dialog - for example, clicking
on a url in a terminal, or running `firefox https://example.com`.

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

Title:
  firefox snap cannot be started: firefox already running

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  On my lapttop version 747 of the Firefox app is installed.

  Whenever I try to launch /snap/bin/firefox I get a popup that Firefox
  is already running.

  ps -aux does not show any such process.
  Rebooting and deleting lock files in ~/.mozilla does not solve the problem.

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1954413/+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 1967182] [NEW] windows change desktop after lock screen

2022-03-30 Thread Matthieu Clemenceau

Public bug reported:

Hello,

So I have a dual screen setup where my primary monitor isn't the laptop
built-in but an external wide screen.

So I would have 2 or 3 virtual desktop with various content organized
(mail, development, personal)

After a long break with the screen locked when I come back to my
computer, my windows have moved from Virtual desktop to another and
sometime from one monitor to another.

let me know if you need more information

Matthieu

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 16:44:57 2022
DisplayManager: gdm3
InstallationDate: Installed on 2020-01-05 (815 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-01-27 (62 days ago)

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


** Tags: amd64 apport-bug jammy third-party-packages uec-images wayland-session

-- 
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/1967182

Title:
  windows change desktop after lock screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  So I have a dual screen setup where my primary monitor isn't the
  laptop built-in but an external wide screen.

  So I would have 2 or 3 virtual desktop with various content organized
  (mail, development, personal)

  After a long break with the screen locked when I come back to my
  computer, my windows have moved from Virtual desktop to another and
  sometime from one monitor to another.

  let me know if you need more information

  Matthieu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 16:44:57 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-01-05 (815 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-01-27 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967182/+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 1966418]

The first 2 did not work for me but the 3rd did.

iris

$ MESA_LOADER_DRIVER_OVERRIDE=iris yelp
EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
Unsupported modifier, resource creation failed.
XXX: resource creation failed

zink

$ MESA_LOADER_DRIVER_OVERRIDE=zink yelp
MESA-INTEL: warning: Performance support disabled, consider sysctl 
dev.i915.perf_stream_paranoid=0

MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0

EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

i965

$ MESA_LOADER_DRIVER_OVERRIDE=i965 yelp
libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so: 
cannot open shared object file: No such file or directory (search paths 
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

WaylandCompositor requires eglBindWaylandDisplayWL, eglUnbindWaylandDisplayWL 
and eglQueryWaylandBuffer.
Nested Wayland compositor could not initialize EGL
libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so: 
cannot open shared object file: No such file or directory (search paths 
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1966418/+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 1966418]

I reported this issue to Mesa also.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/6236

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1966418/+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 1966418]

2022-03-30 Thread Adrian Perez

(In reply to Jeremy Bicha from comment #4)
> The first 2 did not work for me but the 3rd did.
> 
> iris
> 
> $ MESA_LOADER_DRIVER_OVERRIDE=iris yelp
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
> Unsupported modifier, resource creation failed.
> XXX: resource creation failed
> 
> zink
> 
> $ MESA_LOADER_DRIVER_OVERRIDE=zink yelp
> MESA-INTEL: warning: Performance support disabled, consider sysctl
> dev.i915.perf_stream_paranoid=0
> 
> MESA-INTEL: warning: Performance support disabled, consider sysctl
> dev.i915.perf_stream_paranoid=0
> 
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

Zink will use internally lower-level parts from the Iris driver to access
the hardware, so at least this indicates that the issue is *below* the
OpenGL/GLES implementation. Could be EGL or hardware access, I suppose.

> i965
> 
> $ MESA_LOADER_DRIVER_OVERRIDE=i965 yelp
> libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
> 
> WaylandCompositor requires eglBindWaylandDisplayWL,
> eglUnbindWaylandDisplayWL and eglQueryWaylandBuffer.
> Nested Wayland compositor could not initialize EGL
> libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

When a driver that was set explicitly like this fails to load, Mesa falls
back to using software rendering. This means you ended up here using the
swrast/llvmpipe driver, most likely (you can load “webkit://gpu” in the
Minibrowser or Epiphany to check this). This means that WebKit is most
likely using the GLX/EGL/OpenGL/GLES APIs correctly and the issue lies
somewhere in the Intel driver.

But the version of Mesa I am using here is the same as you and it works.
My suspicion is that one of the following is happening:

 * Patches applied by Debian/Ubuntu on top of Mesa are breaking the Intel
   driver. Here I am using Arch Linux, which does not apply any patches.
 * The Intel driver is being miscompiled somehow by the compiler toolchain
   shipped by Ubuntu. In case it helps, here Arch stable has GCC 11.2.0 as
   the default system compiler, so that's what gets used to build packages.
 * The bug could be related to your particular GPU model (and the
   corresponding code inside Mesa for it).

I hope this helps :)

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display

2022-03-30 Thread Tim Wetzel

Two points
-Have not been able to find a combination of logind parameters that avoids this 
issue.
-Have also found that this problem is not limited to HDMI connection. It has 
also now appeared on a T480 in UltraDock using DP++ connection to external 
display. Again, the external display is the primary (only) monitor in use: 
laptop is docked, lid down, and uses external wireless Lenovo keyboard and 
mouse. On power up, after entering Ubuntu password, the system suspends

Please fix this!!! This has been an issue ever since the Ubuntu 20.04
updates September 2020!!!

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

Title:
  Going to sleep instead of logging in while lid closed & external
  display

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have the above described problem, which seems to be very similar to
  bug #1716160

  - laptop is in docking station and 2 monitors are connected (HDMI,
  DVI)

  - If the lid is closed and I boot the laptop I can input my
  credentials in the login screen and after hitting ENTER the laptop
  goes to sleep

  - If I then press the power button of the docking station the laptop
  wakes up and goes straight to the ubuntu environment w/o any user
  identification

  The device is a Lenovo T420 with classic docking station. Ubuntu
  18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated
  Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior
  independent of the graphics used.

  I do not know what to do now since the latest state of bug #1716160 is
  "fix released" and so I guess it should be part of the ubuntu version
  I use?

  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 20:10:15 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-08-13 (14 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.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-settings-daemon/+bug/1841826/+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 1967174] Re: Installing with zfs results in bpool, rpool drives locked on the dock

2022-03-30 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1967174

** Tags added: iso-testing

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

Title:
  Installing with zfs results in bpool, rpool drives locked on the dock

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I installed the ubuntu 20220329 jammy beta with zfs root selected.
  After installation, there are drives on the dock for the zfs bpool and
  rpool (and in my case also a "1.6GB Encrypted" device since I also
  selected disk encryption at install time). These don't do anything
  useful when you click on them, and the only option when right-clicking
  is to mount them, which also doesn't result in anything observable
  from the UI (indeed, they should already be in use). Nor are they
  removable or 'un-pinnable' from the dock. You're just stuck with them
  taking up space.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 13:25:07 2022
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967174/+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 1967176] gnome-shell crashed with SIGSEGV

Stacktrace:
 #0  0x7ffbc79eda7c in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60
StacktraceSource: #0  0x7ffbc79eda7c in ?? ()
StacktraceTop: ?? ()


** 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/1967176

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  2) apt-cache policy gnome-shell
  gnome-shell:
Installed: 42~beta-1ubuntu3
Candidate: 42~beta-1ubuntu3
Version table:
   *** 42~beta-1ubuntu3 500
  500 http://mirror.docker.ru/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  nvidia 1030. nvidia-driver-510

  3) What you expected to happen
  just logout and login again

  4) What happened instead
  after logout and login again, apport reported this crash.

  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
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 22:40:45 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-25 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7ffbc79eda7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60
  StacktraceTop: ?? ()
  Title: gnome-shell 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-shell/+bug/1967176/+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 1967176] [NEW] gnome-shell crashed with SIGSEGV

2022-03-30 Thread Vladimir

Public bug reported:

1) lsb_release -rd
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04

2) apt-cache policy gnome-shell
gnome-shell:
  Installed: 42~beta-1ubuntu3
  Candidate: 42~beta-1ubuntu3
  Version table:
 *** 42~beta-1ubuntu3 500
500 http://mirror.docker.ru/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status

nvidia 1030. nvidia-driver-510

3) What you expected to happen
just logout and login again

4) What happened instead
after logout and login again, apport reported this crash.

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
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 22:40:45 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2022-03-25 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=ru_RU.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
 #0  0x7ffbc79eda7c in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

** Affects: gnome-shell (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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967176

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  2) apt-cache policy gnome-shell
  gnome-shell:
Installed: 42~beta-1ubuntu3
Candidate: 42~beta-1ubuntu3
Version table:
   *** 42~beta-1ubuntu3 500
  500 http://mirror.docker.ru/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  nvidia 1030. nvidia-driver-510

  3) What you expected to happen
  just logout and login again

  4) What happened instead
  after logout and login again, apport reported this crash.

  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
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 22:40:45 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-25 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7ffbc79eda7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60
  StacktraceTop: ?? ()
  Title: gnome-shell 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-shell/+bug/1967176/+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 1967168] Re: [Wayland] Yelp does not show the documentation

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

Thank you for taking the time to report this bug. I'm marking this a
duplicate of https://launchpad.net/bugs/1966418

** This bug has been marked a duplicate of bug 1966418
   [jammy regression] Evolution does not display message content anymore

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

Title:
  [Wayland] Yelp does not show the documentation

Status in ubuntu-docs package in Ubuntu:
  Invalid
Status in yelp package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 development branch @ 30/03/2022

  Opening yelp ?-icon does not show the help documentation items on Wayland only
  on Xorg it works

  The items exist, as hovering the mouse pointer over they show tooltips
  but overall the whole window is blank, see screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-docs 22.04.2
  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 30 19:12:52 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1967168/+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 1967175] [NEW] Righ click on links menu doesn't render 99.0.4844.84

2022-03-30 Thread Valtteri Suojanen

Public bug reported:

snap info chromium
name:  chromium
summary:   Chromium web browser, open-source version of Chrome
publisher: Canonical✓
store-url: https://snapcraft.io/chromium
contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license:   unset
description: |
  An open-source browser project that aims to build a safer, faster, and more
  stable way for all Internet users to experience the web.
commands:
  - chromium.chromedriver
  - chromium
snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/stable
refresh-date: 3 days ago, at 10:51 EEST
channels:
  latest/stable:99.0.4844.84  2022-03-26 (1945) 141MB -
  latest/candidate: 99.0.4844.84  2022-03-26 (1945) 141MB -
  latest/beta:  100.0.4896.46 2022-03-18 (1943) 137MB -
  latest/edge:  101.0.4951.7  2022-03-28 (1947) 139MB -
installed:  99.0.4844.84 (1945) 141MB -

lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04

Right clicking web links with text or link buttons is expected to open a menu. 
However the right click menu doesn't render. Instead right clicking opens a 
black background (without any text/shape).
Right clicking link with plain image works
(https://askubuntu.com/)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Righ click on links menu doesn't render 99.0.4844.84

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  store-url: https://snapcraft.io/chromium
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: 3 days ago, at 10:51 EEST
  channels:
latest/stable:99.0.4844.84  2022-03-26 (1945) 141MB -
latest/candidate: 99.0.4844.84  2022-03-26 (1945) 141MB -
latest/beta:  100.0.4896.46 2022-03-18 (1943) 137MB -
latest/edge:  101.0.4951.7  2022-03-28 (1947) 139MB -
  installed:  99.0.4844.84 (1945) 141MB -

  lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  Right clicking web links with text or link buttons is expected to open a 
menu. 
  However the right click menu doesn't render. Instead right clicking opens a 
black background (without any text/shape).
  Right clicking link with plain image works
  (https://askubuntu.com/)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967175/+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 1967174] Re: Installing with zfs results in bpool, rpool drives locked on the dock

Here's a screenshot showing the drives

** Attachment added: "zfs-dock.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967174/+attachment/5574890/+files/zfs-dock.png

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

Title:
  Installing with zfs results in bpool, rpool drives locked on the dock

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I installed the ubuntu 20220329 jammy beta with zfs root selected.
  After installation, there are drives on the dock for the zfs bpool and
  rpool (and in my case also a "1.6GB Encrypted" device since I also
  selected disk encryption at install time). These don't do anything
  useful when you click on them, and the only option when right-clicking
  is to mount them, which also doesn't result in anything observable
  from the UI (indeed, they should already be in use). Nor are they
  removable or 'un-pinnable' from the dock. You're just stuck with them
  taking up space.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 13:25:07 2022
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967174/+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 1967174] [NEW] Installing with zfs results in bpool, rpool drives locked on the dock

Public bug reported:

I installed the ubuntu 20220329 jammy beta with zfs root selected. After
installation, there are drives on the dock for the zfs bpool and rpool
(and in my case also a "1.6GB Encrypted" device since I also selected
disk encryption at install time). These don't do anything useful when
you click on them, and the only option when right-clicking is to mount
them, which also doesn't result in anything observable from the UI
(indeed, they should already be in use). Nor are they removable or 'un-
pinnable' from the dock. You're just stuck with them taking up space.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 13:25:07 2022
InstallationDate: Installed on 2022-03-30 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell-extension-ubuntu-dock (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-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1967174

Title:
  Installing with zfs results in bpool, rpool drives locked on the dock

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I installed the ubuntu 20220329 jammy beta with zfs root selected.
  After installation, there are drives on the dock for the zfs bpool and
  rpool (and in my case also a "1.6GB Encrypted" device since I also
  selected disk encryption at install time). These don't do anything
  useful when you click on them, and the only option when right-clicking
  is to mount them, which also doesn't result in anything observable
  from the UI (indeed, they should already be in use). Nor are they
  removable or 'un-pinnable' from the dock. You're just stuck with them
  taking up space.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 13:25:07 2022
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967174/+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-30 Thread Nicholas Harvey

I've just tried this fix in Jammy nightly and it works for me. Thanks!

-- 
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 Released
Status in nautilus source package in Jammy:
  Fix Released

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 1967109] Re: Xubuntu Docs installed at /usr/share/xubuntu-docs/index.html is not accessible with firefox snap

** Also affects: firefox (Ubuntu Jammy)
   Importance: Medium
   Status: Triaged

** Also affects: xubuntu-default-settings (Ubuntu Jammy)
   Importance: High
   Status: Triaged

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

Title:
  Xubuntu Docs installed at /usr/share/xubuntu-docs/index.html is not
  accessible with firefox snap

Status in firefox package in Ubuntu:
  Triaged
Status in xubuntu-default-settings package in Ubuntu:
  Triaged
Status in firefox source package in Jammy:
  Triaged
Status in xubuntu-default-settings source package in Jammy:
  Triaged

Bug description:
  Xubuntu's documentation is stored at /usr/share/xubuntu-
  docs/index.html

  The firefox snap is not able to access this file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967109/+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 1967111] Re: exo-open --launch WebBrowser does not work with firefox snap

** Also affects: exo (Ubuntu Jammy)
   Importance: High
   Status: New

** Also affects: firefox (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Changed in: exo (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: firefox (Ubuntu Jammy)
   Status: New => Triaged

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

Title:
  exo-open --launch WebBrowser does not work with firefox snap

Status in exo package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  Triaged
Status in exo source package in Jammy:
  Triaged
Status in firefox source package in Jammy:
  Triaged

Bug description:
  With Firefox set as the default browser, `exo-open --launch
  WebBrowser` only outputs the current env vars (seen below).

  Passing in an additional parameter (`exo-open --launch WebBrowser
  google.com`) works as expected.

  SHELL=/bin/bash
  
SESSION_MANAGER=local/xubuntu:@/tmp/.ICE-unix/4173,unix/xubuntu:/tmp/.ICE-unix/4173
  WINDOWID=73400323
  QT_ACCESSIBILITY=1
  COLORTERM=truecolor
  XDG_CONFIG_DIRS=/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
  XDG_MENU_PREFIX=xfce-
  CLUTTER_BACKEND=x11
  SSH_AUTH_SOCK=/run/user/999/keyring/ssh
  DESKTOP_SESSION=xubuntu
  XDG_SEAT=seat0
  PWD=/home/xubuntu
  LOGNAME=xubuntu
  XDG_SESSION_DESKTOP=xubuntu
  QT_QPA_PLATFORMTHEME=gtk2
  XDG_SESSION_TYPE=x11
  PANEL_GDK_CORE_DEVICE_EVENTS=0
  GPG_AGENT_INFO=/run/user/999/gnupg/S.gpg-agent:0:1
  XAUTHORITY=/home/xubuntu/.Xauthority
  XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/xubuntu
  HOME=/home/xubuntu
  LANG=en_US.UTF-8
  
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
  XDG_CURRENT_DESKTOP=XFCE
  VTE_VERSION=6790
  XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
  LESSCLOSE=/usr/bin/lesspipe %s %s
  XDG_SESSION_CLASS=user
  TERM=xterm-256color
  GTK_OVERLAY_SCROLLING=0
  LESSOPEN=| /usr/bin/lesspipe %s
  USER=xubuntu
  DISPLAY=:0.0
  SHLVL=1
  XDG_VTNR=7
  XDG_SESSION_ID=c2
  XDG_RUNTIME_DIR=/run/user/999
  
XDG_DATA_DIRS=/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share
  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
  GDMSESSION=xubuntu
  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/999/bus
  _=/usr/bin/exo-open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exo/+bug/1967111/+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 1967168] Re: [Wayland] Ubuntu-docs does not show the documentation

2022-03-30 Thread lotuspsychje

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

** Changed in: ubuntu-docs (Ubuntu)
   Status: Confirmed => Invalid

** Description changed:

  Ubuntu 22.04 development branch @ 30/03/2022
  
- Opening ubuntu-docs ?-icon does not show the help documentation items on 
Wayland only
+ Opening yelp ?-icon does not show the help documentation items on Wayland only
  on Xorg it works
  
  The items exist, as hovering the mouse pointer over they show tooltips
  but overall the whole window is blank, see screenshot
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-docs 22.04.2
  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 30 19:12:52 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- [Wayland] Ubuntu-docs does not show the documentation
+ [Wayland] Yelp does not show the documentation

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

Title:
  [Wayland] Yelp does not show the documentation

Status in ubuntu-docs package in Ubuntu:
  Invalid
Status in yelp package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 development branch @ 30/03/2022

  Opening yelp ?-icon does not show the help documentation items on Wayland only
  on Xorg it works

  The items exist, as hovering the mouse pointer over they show tooltips
  but overall the whole window is blank, see screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-docs 22.04.2
  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 30 19:12:52 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1967168/+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 1967170] [NEW] webgl broken, no gpu detected on raspberry pi 4

2022-03-30 Thread a8ksh4

Public bug reported:

Using a brand new clean install, when starting firefox, it reports no
gpus detected and is unable to use webgl.  This affects the snap firefox
and the apt installed firefox (that I used to open this report).  This
was working on my system with a prev. installation of the os a few weeks
ago, but stopped working at some point.  I did the fresh os install to
make sure it's not something I did.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: firefox 98.0.2+build1-0ubuntu0.21.10.1
ProcVersionSignature: Ubuntu 5.13.0-1022.24-raspi 5.13.19
Uname: Linux 5.13.0-1022-raspi aarch64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu71
Architecture: arm64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  drnorris952 F pulseaudio
 /dev/snd/controlC0:  drnorris952 F pulseaudio
BuildID: 20220322144853
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 10:36:48 2022
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
ImageMediaBuild: 20211013
IpRoute:
 default via 192.168.4.251 dev wlan0 proto dhcp metric 600 
 169.254.0.0/16 dev wlan0 scope link metric 1000 
 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.139 metric 600
PciNetwork:
 
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=98.0.2/20220322144853 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 arm64-image impish raspi-image wayland-session

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

Title:
  webgl broken, no gpu detected on raspberry pi 4

Status in firefox package in Ubuntu:
  New

Bug description:
  Using a brand new clean install, when starting firefox, it reports no
  gpus detected and is unable to use webgl.  This affects the snap
  firefox and the apt installed firefox (that I used to open this
  report).  This was working on my system with a prev. installation of
  the os a few weeks ago, but stopped working at some point.  I did the
  fresh os install to make sure it's not something I did.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: firefox 98.0.2+build1-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-1022.24-raspi 5.13.19
  Uname: Linux 5.13.0-1022-raspi aarch64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  drnorris952 F pulseaudio
   /dev/snd/controlC0:  drnorris952 F pulseaudio
  BuildID: 20220322144853
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 10:36:48 2022
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  ImageMediaBuild: 20211013
  IpRoute:
   default via 192.168.4.251 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.139 metric 600
  PciNetwork:
   
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @

[Desktop-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #6236
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/6236

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/6236
   Importance: Unknown
   Status: Unknown

** Changed in: liferea (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1966418/+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 1964724] Re: the laptop is slowing down I suspect the graphics

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
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/1964724

Title:
  the laptop is slowing down I suspect the graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  I am sure that the video driver does not work because it is very
  stupid

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-36.41~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 14 01:26:27 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:081b]
  InstallationDate: Installed on 2022-03-11 (2 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Acer Aspire V5-132P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-36-generic 
root=UUID=3ed9b8cd-2125-43f4-af3a-b14a5314ae6e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 07/19/2013
  dmi.bios.release: 2.4
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.04
  dmi.board.name: Angel_CY
  dmi.board.vendor: Acer
  dmi.board.version: V2.04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.04
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.04:bd07/19/2013:br2.4:efr1.5:svnAcer:pnAspireV5-132P:pvrV2.04:rvnAcer:rnAngel_CY:rvrV2.04:cvnAcer:ct9:cvrV2.04:skuAspireV5-132P_081B_2.04:
  dmi.product.family: Aspire V5-132P
  dmi.product.name: Aspire V5-132P
  dmi.product.sku: Aspire V5-132P_081B_2.04
  dmi.product.version: V2.04
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110+git2203100500.7c28f5~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.1~git2203130600.177805~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1964724/+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 1964795] Re: gnome-keyring-daemon crashed with signal 7

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  gnome-keyring-daemon crashed with signal 7

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  gnome-keyring:
Installed: 40.0-3ubuntu1
Candidate: 40.0-3ubuntu1
Version table:
   *** 40.0-3ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
  100 /var/lib/dpkg/status

  Background process crashes unexpectedly a few moments after login.

  I'm running the dev release of Jammy on a Raspberry Pi 400 with all
  updates applied.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-keyring 40.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19
  Uname: Linux 5.15.0-1003-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Mon Mar 14 15:26:41 2022
  Disassembly: => 0x:   Cannot access memory at address 0x
  ExecutablePath: /usr/bin/gnome-keyring-daemon
  ImageMediaBuild: 20201022
  ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  Signal: 7
  SourcePackage: gnome-keyring
  StacktraceTop:
   ()
   ()
   () at /lib/aarch64-linux-gnu/libgio-2.0.so.0
   g_signal_emit_valist () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-keyring-daemon crashed with signal 7
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (6 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1964795/+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 1965114] Re: computer errs

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

** Changed in: xorg (Ubuntu)
   Status: New => Invalid

-- 
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/1965114

Title:
  computer errs

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  OS  performs  errors

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
  Uname: Linux 5.4.0-105-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Mar 16 15:41:52 2022
  DistUpgraded: 2022-02-14 15:26:03,689 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad X240 [17aa:2214]
  InstallationDate: Installed on 2021-01-14 (425 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20AMCTO1WW
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-105-generic 
root=UUID=fb3eedbf-03ca-48cd-b4f6-ab7e0a3a9af6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2022-02-14 (30 days ago)
  dmi.bios.date: 08/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET76WW (2.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:svnLENOVO:pn20AMCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20AMCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X240
  dmi.product.name: 20AMCTO1WW
  dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Thu Sep 30 14:17:53 2021
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1965114/+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 1965686] Re: After the laptop comes out of sleep mode, the desktop environment for some reason breaks and appears crashes window

** Information type changed from Private Security to Public

-- 
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/1965686

Title:
  After the laptop comes out of sleep mode, the desktop environment for
  some reason breaks and appears crashes window

Status in gnome-shell package in Ubuntu:
  New

Bug description:

  I've been running Ubuntu 20.04 for about a month now. Lock screen is
  crashing the UI in 20.04.

  I don't know how to stop crashing my screen so I forcefully press
  power off button and turn on again my computer every time I use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 22:26:56 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-18 (61 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  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/1965686/+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 1965869] Re: Screen only partially locked. Password promt was visible, but switching to window and typing eg in terminal was possible

** Package changed: ubuntu => gnome-shell (Ubuntu)

** Information type changed from Private Security to Public

-- 
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/1965869

Title:
  Screen only partially locked. Password promt was visible, but
  switching to window and typing eg in terminal was possible

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Today I returned to my PC, which was on over night.

  The screen was only partially locked. The password prompt was full
  screen except the start menu on the left was visible. I was able to
  click on the Icons of running applications and was able to type in an
  open terminal which responded correctly and executed the commands (I
  tried "reset").

  I have no Idea what can cause this issue and would appreciate help on
  how to gather information that can help the Ubuntu team find the cause
  of the issue.

  I saved copies of dmesg, syslog and kern.log.
  I have not tried reproducing the bug.
  I do not know if I actively locked the screen or if I just walked off 
yesterday.

  Best Regards,
  Chris

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 22 08:16:18 2022
  InstallationDate: Installed on 2021-12-13 (98 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  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/1965869/+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 1966572] Re: Chromium Zero Day

This is published now:

https://ubuntu.com/security/notices/USN-5350-1

** Changed in: chromium-browser (Ubuntu)
   Status: New => Fix Released

** Information type changed from Private Security to Public Security

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

Title:
  Chromium Zero Day

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Please see: https://chromereleases.googleblog.com/2022/03/stable-
  channel-update-for-desktop_25.html

  Apparently this also affects the Chromium package and is being
  actively exploited in the wild:

  > [$TBD][1309225] High CVE-2022-1096: Type Confusion in V8. Reported
  by anonymous on 2022-03-23

  Please update from Version 97.0.4692.20 (last updated 2021-11-26) to
  latest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1966572/+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 1966786] Re: login screen shown twice

2022-03-30 Thread BertN45

Maybe switching from wayland to xorg caused the problem.

That menu was only present on the first login screen, so I tried moving
back to Wayland. The double login screen remained and I had the old
issues again with DOSBOX and Conky :(

-- 
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/1966786

Title:
  login screen shown twice

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The login screen is shown twice and I have to supply the password
  twice. The system works normally afterwards.  When I select auto-login
  in the settings still one login screen is shown.

  gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static)
   Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago
  Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
 Main PID: 1915 (gdm3)
Tasks: 3 (limit: 2291)
   Memory: 5.0M
  CPU: 125ms
   CGroup: /system.slice/gdm.service
   └─1915 /usr/sbin/gdm3

  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager...
  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager.
  mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) 
by (uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate 
daemon control file
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password 
to try later in open session
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: 
pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by 
(uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: 
gnome-keyring-daemon started properly and unlocked keyring
  mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was 
already dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 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: Mon Mar 28 11:48:17 2022
  InstallationDate: Installed on 2020-01-25 (793 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)

2022-03-30 Thread Brian Murray

** Also affects: libreoffice (Ubuntu Jammy)
   Importance: Medium
   Status: Triaged

** Changed in: libreoffice (Ubuntu Jammy)
Milestone: None => ubuntu-22.04

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

Title:
  libreoffice help doesn't open in firefox (404 error on
  file:///tmp/lu417531j7po.tmp/NewHelp0.html)

Status in libreoffice package in Ubuntu:
  Triaged
Status in libreoffice source package in Jammy:
  Triaged

Bug description:
  Ubuntu jammy live QA-test on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  Opened LibreOffice Writer as random apps in QA-test.
  Hit F1 to call help, and all I get is an error

  URL:  file:///tmp/lu417531j7po.tmp/NewHelp0.html

  ---
  File not found

  Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  Firefox opens as a snap; but it isn't accessing the data from
  LibreOffice.

  Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks-
  libreoffice-deb/27537

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465+canary3.3
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 17 04:46:33 2021
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+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 1966786] Re: login screen shown twice

2022-03-30 Thread BertN45

1. When I reinstalled with "sh autorun.sh", I got two terminals and the
first one said:

bertadmin@vm-ubuntu-2204:/media/bertadmin/VBox_GAs_6.1.32$ sh autorun.sh
# Option “-x” is deprecated and might be removed in a later version of 
gnome-terminal.
# Use “-- ” to terminate the options and put the command line to execute after 
it.
bertadmin@vm-ubuntu-2204:/media/bertadmin/VBox_GAs_6.1.32$ 

The Second Terminal executed the install as expected, see also
attachment.

2. When I uninstalled Virtual box with "sh VBoxLinuxAdditions.run uninstall" 
the problem disappeared. The boot and login were normal.
But the problem reappeared after a reinstall "sh VBoxLinuxAdditions.run".

3. I have upgraded the system from Ubuntu 20.04. After a while I noticed
that DOSBOX and Conky did not run anymore with wayland, so I moved back
to xorg through the menu in the login screen. According to "the
Internet", it is a known issue with Conky and DOSDOX.

Maybe switching from wayland to xorg caused the problem, but that menu
disappeared from the login screen, so I cant move back to wayland.


** Attachment added: "vbox-issue"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+attachment/5574845/+files/vbox-issue

-- 
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/1966786

Title:
  login screen shown twice

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The login screen is shown twice and I have to supply the password
  twice. The system works normally afterwards.  When I select auto-login
  in the settings still one login screen is shown.

  gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static)
   Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago
  Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
 Main PID: 1915 (gdm3)
Tasks: 3 (limit: 2291)
   Memory: 5.0M
  CPU: 125ms
   CGroup: /system.slice/gdm.service
   └─1915 /usr/sbin/gdm3

  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager...
  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager.
  mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) 
by (uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate 
daemon control file
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password 
to try later in open session
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: 
pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by 
(uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: 
gnome-keyring-daemon started properly and unlocked keyring
  mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was 
already dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 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: Mon Mar 28 11:48:17 2022
  InstallationDate: Installed on 2020-01-25 (793 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+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 1967020] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1967020/+attachment/5574824/+files/ThreadStacktrace.txt

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

** Changed in: webkit2gtk (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  WebKitWebProcess crashed with SIGSEGV

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  Evolution, when launched with Wayland, suddenly closes. When launched
  from the command line, it displays this:

  Gdk-Message: 16:42:11.320: Error flushing display: Protocol error

  If forced with --display=:0, it works, but an obvious crash in
  WebKitWebProcess occurs, hence I believe the issue lies within that.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libwebkit2gtk-4.0-37 2.35.90-1ubuntu1
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 29 16:45:19 2022
  ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
  InstallationDate: Installed on 2021-08-19 (222 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 13 43
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SegvAnalysis:
   Segfault happened at: 0x7fd90adae773:mov(%rdi),%rax
   PC (0x7fd90adae773) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: webkit2gtk
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
  Title: WebKitWebProcess crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+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 1967020] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1967020/+attachment/5574823/+files/StacktraceSource.txt

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

Title:
  WebKitWebProcess crashed with SIGSEGV

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  Evolution, when launched with Wayland, suddenly closes. When launched
  from the command line, it displays this:

  Gdk-Message: 16:42:11.320: Error flushing display: Protocol error

  If forced with --display=:0, it works, but an obvious crash in
  WebKitWebProcess occurs, hence I believe the issue lies within that.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libwebkit2gtk-4.0-37 2.35.90-1ubuntu1
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 29 16:45:19 2022
  ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
  InstallationDate: Installed on 2021-08-19 (222 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 13 43
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SegvAnalysis:
   Segfault happened at: 0x7fd90adae773:mov(%rdi),%rax
   PC (0x7fd90adae773) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: webkit2gtk
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
  Title: WebKitWebProcess crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+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 1967020] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1967020/+attachment/5574822/+files/Stacktrace.txt

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

Title:
  WebKitWebProcess crashed with SIGSEGV

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  Evolution, when launched with Wayland, suddenly closes. When launched
  from the command line, it displays this:

  Gdk-Message: 16:42:11.320: Error flushing display: Protocol error

  If forced with --display=:0, it works, but an obvious crash in
  WebKitWebProcess occurs, hence I believe the issue lies within that.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libwebkit2gtk-4.0-37 2.35.90-1ubuntu1
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 29 16:45:19 2022
  ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
  InstallationDate: Installed on 2021-08-19 (222 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 13 43
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SegvAnalysis:
   Segfault happened at: 0x7fd90adae773:mov(%rdi),%rax
   PC (0x7fd90adae773) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: webkit2gtk
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
  Title: WebKitWebProcess crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+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 1967020] WebKitWebProcess crashed with SIGSEGV

StacktraceTop:
 WebKit::LayerTreeHost::LayerTreeHost () at 
./Source/WebKit/WebProcess/WebPage/CoordinatedGraphics/LayerTreeHost.cpp:77
 std::make_unique () at 
/usr/include/c++/11/bits/unique_ptr.h:962
 WTF::makeUnique () at 
./build-soup2/WTF/Headers/wtf/StdLibExtras.h:540
 WebKit::DrawingAreaCoordinatedGraphics::enterAcceleratedCompositingMode () at 
./Source/WebKit/WebProcess/WebPage/CoordinatedGraphics/DrawingAreaCoordinatedGraphics.cpp:641
 WebKit::WebPage::WebPage () at 
./Source/WebKit/WebProcess/WebPage/WebPage.cpp:792

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

Title:
  WebKitWebProcess crashed with SIGSEGV

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  Evolution, when launched with Wayland, suddenly closes. When launched
  from the command line, it displays this:

  Gdk-Message: 16:42:11.320: Error flushing display: Protocol error

  If forced with --display=:0, it works, but an obvious crash in
  WebKitWebProcess occurs, hence I believe the issue lies within that.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libwebkit2gtk-4.0-37 2.35.90-1ubuntu1
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 29 16:45:19 2022
  ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
  InstallationDate: Installed on 2021-08-19 (222 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 13 43
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SegvAnalysis:
   Segfault happened at: 0x7fd90adae773:mov(%rdi),%rax
   PC (0x7fd90adae773) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: webkit2gtk
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
  Title: WebKitWebProcess crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+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 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

2022-03-30 Thread Launchpad Bug Tracker

This bug was fixed in the package intel-media-driver-non-free -
22.2.1+ds1-1build1

---
intel-media-driver-non-free (22.2.1+ds1-1build1) jammy; urgency=medium

  * Rebuild with the current libva version (lp: #1966571)

 -- Sebastien Bacher   Wed, 30 Mar 2022 11:16:29
+0200

** Changed in: intel-media-driver-non-free (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init
  failed

Status in intel-media-driver package in Ubuntu:
  Fix Committed
Status in intel-media-driver-non-free package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I noticed that it upgraded mesa to 22.x and now video acceleration is
  not working due to:

  ❯ vainfo 
  libva info: VA-API version 1.14.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_14
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_10
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  ~/Desktop 
  ❯ inxi -G
  Graphics:
Device-1: Intel driver: i915 v: kernel
Device-2: Generalplus GENERAL WEBCAM type: USB
  driver: snd-usb-audio,uvcvideo
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2)
  v: 4.6 Mesa 22.0.0

  I tried rebuilding the i965-va-driver, and it's still the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mesa-vdpau-drivers 22.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 10:37:41 2022
  DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-10-05 (172 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  MachineType: ASUS System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 23.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: Default string
  dmi.board.name: Pro WS W480-ACE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about

[Desktop-packages] [Bug 1949291] Re: LibreOffice has started displaying a donation nag

2022-03-30 Thread Brian Murray

** Tags added: rls-kk-incoming

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

Title:
  LibreOffice has started displaying a donation nag

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I just opened up a spreadsheet (technically a CSV file, but who's
  counting), to discover LibreOffice displaying an eye-catching blue
  "Your donations support our worldwide community." banner just below
  the toolbars and about a toolbar and a half tall.

  This irritating nag is apparently supposed to display every 90 to 180
  days with no in-application means to disable it permanently, and
  there's apparently also a "Help us make LibreOffice even better!"
  banner that can appear too.

  According to this blog post...

  https://www.remembertheusers.com/2019/11/0580-libreoffice-nag-
  notices.html

  ...it is not responsive to configuration overrides within the user
  profile and the only apparent solution that doesn't require patching
  the source and rebuilding is to create a file containing the following
  markup in `$BASEDIR/share/registry`
  (`/usr/lib/libreoffice/share/registry` as installed by the Ubuntu
  package):

  
  http://www.w3.org/2001/XMLSchema; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xmlns:oor="http://openoffice.org/2001/registry;>

http://openoffice.org/2004/installation; oor:name="Setup" 
oor:package="org.openoffice">
  

  0


  0

  

  

  Regardless of how it's achieved, I think it's tasteless, irritating,
  and probably doesn't give a very good image to any office customers
  Ubuntu may have downstream for random employees to be receiving nag
  banners like that in IT-installed software.

  Please consider patching it out or otherwise ensuring it never
  triggers in distro-provided builds of LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Oct 31 04:32:03 2021
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1949291/+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 1967150] Re: gnome-shell crashed with SIGSEGV

2022-03-30 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1967150

** Tags added: iso-testing

-- 
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/1967150

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This was running a live session of the jammy beta candidate image
  20220329.1 in qemu. I let it sit for a bit after booting, came back to
  the session and came out of the screen blank and saw it reporting this
  crash had occurred.  The session has been up 41 minutes but the files
  in /var/crash are timestamped from just a few minutes ago so I think
  it may have happened coming out of the screen blank.

  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
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 14:31:13 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C.UTF-8
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SegvAnalysis:
   Segfault happened at: 0x7f8255af2f44:mov(%rsi),%rax
   PC (0x7f8255af2f44) ok
   source "(%rsi)" (0x35d82c10) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f8255af2f44 in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
  StacktraceTop: ?? ()
  Title: gnome-shell 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-shell/+bug/1967150/+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] Re: Bluetooth fails to connect "br-connection-profile-unavailable"

2022-03-30 Thread EdwardO

Thanks for the support.

Indeed pipewire is part of the issue. Although installing kubuntu-
desktop does not force pipewire (according to
https://packages.ubuntu.com/jammy/kubuntu-desktop ), I may have enabled
it wrongly while getting Wayland screensharing to work with the
following:

sudo apt install xdg-desktop-portal-gnome gnome-remote-desktop  #
installs pipewire

systemctl --user enable pipewire-media-session
systemctl --user start pipewire-media-session
systemctl --user restart xdg-desktop-portal-gnome

This must have been what caused audio to break
(aside - I'd be happy to know the supported steps for xdg-portal sharing when 
upgrading to 22.04)

Thanks to your pointer I managed to fix it:
* recover the (wired) audio by installing wireplumber: this fixed half-setup 
pipewire situation.
* fix bluetooth by installing libspa-0.2-bluetooth (and restart bluetooth & 
wireplumber)
(see 
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1826833.html)
So, closing this, and if it is considered an unsupported solution, sorry for 
taking your time!

** Changed in: bluez (Ubuntu)
   Status: New => Invalid

** Changed in: pipewire (Ubuntu)
   Status: New => Invalid

** Changed in: pulseaudio (Ubuntu)
   Status: New => Invalid

-- 
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/1966436

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

Status in bluez package in Ubuntu:
  Invalid
Status in pipewire package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

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: 
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]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1966436/+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 1881712] Re: gnome-software says connection is metered while is not

2022-03-30 Thread caio tor

Hello the issue continues with Ubuntu Mate 20.04 while using USB
Thetering( But smartphone is using a WIfi and Not using 4g)

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

Title:
  gnome-software says connection is metered while is not

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I open gnome-software and i see a message 'automatic updates paused' for my 
connection is metered but my connection is NOT metered.
  see attached screenshot. 
  corrado@corrado-HP-x4-gg-0525ebook-PC:~$ inxi -Fx
  System:Host: corrado-HP-x4-gg-0525ebook-PC Kernel: 5.4.0-26-generic 
x86_64 bits: 64 compiler: gcc v: 9.3.0 
 Desktop: Gnome 3.36.2 Distro: Ubuntu 20.10 (Groovy Gorilla) 
  Machine:   Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook 
PC v: 0991100600087 
 serial:  
 Mobo: Hewlett-Packard model: 2211 v: 86.49 serial:  UEFI: Insyde v: F.36 
 date: 12/18/2014 
  Battery:   ID-1: BAT1 charge: 10.2 Wh condition: 16.4/16.4 Wh (100%) model: 
13-42 OA03031 status: Charging 
  CPU:   Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT 
MCP arch: Haswell rev: 1 
 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19156 
 Speed: 1696 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 1697 
2: 1696 3: 1696 4: 1697 
  Graphics:  Device-1: Intel Haswell-ULT Integrated Graphics vendor: 
Hewlett-Packard driver: i915 v: kernel 
 bus ID: 00:02.0 
 Device-2: Suyin type: USB driver: uvcvideo bus ID: 1-1.5:3 
 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: 
fbdev,vesa resolution: 1366x768~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 
Mesa 20.0.7 direct render: Yes 
  Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard 
driver: snd_hda_intel v: kernel 
 bus ID: 00:03.0 
 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: 
snd_hda_intel v: kernel bus ID: 00:1b.0 
 Sound Server: ALSA v: k5.4.0-26-generic 
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: 
Hewlett-Packard driver: r8169 v: kernel 
 port: 3000 bus ID: 08:00.0 
 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce 
 Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: 
Hewlett-Packard driver: rt2800pci v: 2.3.0 
 port: 3000 bus ID: 09:00.0 
 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d 
  Drives:Local Storage: total: 689.33 GiB used: 6.76 GiB (1.0%) 
 ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 
465.76 GiB 
 ID-2: /dev/sdb vendor: SanDisk model: SSD PLUS 240GB size: 223.57 
GiB 
  Partition: ID-1: / size: 31.25 GiB used: 6.75 GiB (21.6%) fs: ext4 dev: 
/dev/sdb5 
  Swap:  ID-1: swap-1 type: partition size: 4.00 GiB used: 0 KiB (0.0%) 
dev: /dev/sda2 
  Sensors:   System Temperatures: cpu: 39.0 C mobo: 39.0 C 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 236 Uptime: 49m Memory: 3.78 GiB used: 1.39 GiB (36.7%) 
Init: systemd runlevel: 5 Compilers: 
 gcc: 9.3.0 Shell: bash v: 5.0.16 inxi: 3.1.00 
  corrado@corrado-HP-x4-gg-0525ebook-PC:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  2 08:57:28 2020
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2020-05-26 (6 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200525)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.36.0-0ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-21 (41 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200420)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.36.0-0ubuntu3
  Package: gnome-software 3.36.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-03-30 Thread Alexander Browne

@seb128

Sorry if that sounded browbeating. My response is more like
"unfortunate, but understandable". Someone has to be first, even if
MS/Apple seem OK to leave it working.

Thanks for finding the Fedora info. I had just wondered about other
distros. Looks like the other bug they link to is a dupe of this?
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1961558

Can I suggest this be documented in the release notes, at least the
issue, but maybe even including the workaround? FWIW, I see now the file
suggested in the workaround above (/usr/lib/ssl/openssl.cnf) is a link
to /etc/ssl/openssl.cnf, so I think it shouldn't get overwritten as I
thought it might.

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1967150] gnome-shell crashed with SIGSEGV

Stacktrace:
 #0  0x7f8255af2f44 in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
StacktraceSource: #0  0x7f8255af2f44 in ?? ()
StacktraceTop: ?? ()


** 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/1967150

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This was running a live session of the jammy beta candidate image
  20220329.1 in qemu. I let it sit for a bit after booting, came back to
  the session and came out of the screen blank and saw it reporting this
  crash had occurred.  The session has been up 41 minutes but the files
  in /var/crash are timestamped from just a few minutes ago so I think
  it may have happened coming out of the screen blank.

  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
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 14:31:13 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C.UTF-8
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SegvAnalysis:
   Segfault happened at: 0x7f8255af2f44:mov(%rsi),%rax
   PC (0x7f8255af2f44) ok
   source "(%rsi)" (0x35d82c10) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f8255af2f44 in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
  StacktraceTop: ?? ()
  Title: gnome-shell 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-shell/+bug/1967150/+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 1967155] [NEW] Update gnome-online-accounts to 3.44

Public bug reported:

Minimal tracking bug if needed.

https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/master/NEWS

https://gitlab.gnome.org/GNOME/gnome-online-
accounts/-/compare/3.43.1...master?from_project_id=1666

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: In Progress


** Tags: jammy upgrade-software-version

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

Title:
  Update gnome-online-accounts to 3.44

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  Minimal tracking bug if needed.

  https://gitlab.gnome.org/GNOME/gnome-online-
  accounts/-/blob/master/NEWS

  https://gitlab.gnome.org/GNOME/gnome-online-
  accounts/-/compare/3.43.1...master?from_project_id=1666

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1967155/+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 1967150] Re: gnome-shell crashed with SIGSEGV

Marking public since this was from a live session in qemu and did not
yet contain anything I'm concerned about.

-- 
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/1967150

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This was running a live session of the jammy beta candidate image
  20220329.1 in qemu. I let it sit for a bit after booting, came back to
  the session and came out of the screen blank and saw it reporting this
  crash had occurred.  The session has been up 41 minutes but the files
  in /var/crash are timestamped from just a few minutes ago so I think
  it may have happened coming out of the screen blank.

  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
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 14:31:13 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C.UTF-8
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SegvAnalysis:
   Segfault happened at: 0x7f8255af2f44:mov(%rsi),%rax
   PC (0x7f8255af2f44) ok
   source "(%rsi)" (0x35d82c10) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f8255af2f44 in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
  StacktraceTop: ?? ()
  Title: gnome-shell 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-shell/+bug/1967150/+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 1966905] Re: Valgrind memory errors in gnome-shell 42 from accountsservice

2022-03-30 Thread Sebastien Bacher

Upstream gave some debugging hints

'So the only unref call has a matching ref call pair.  This means it
shouldn't lead to the object getting freed. But between those two calls
the property notify handlers get run, etc.  It's at least conceivable to
me that one of those handlers is accidentally unrefing the object when
it isn't supposed to.

If that is what's going on, how are we going to find out where the
handler is?  One idea,

You could try putting

g_object_unref (user);

and the top of on_new_user_loaded. This is wrong and adding a bug, but
it may also help valgrind to spot the aforementioned, theorized
preexisting extraneously unref too. This is because it will make the
user object get freed earlier, and valgrind should show where.'


Could you give it a try?

-- 
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/1966905

Title:
  Valgrind memory errors in gnome-shell 42 from accountsservice

Status in accountsservice:
  Unknown
Status in accountsservice package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511== 
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now

[Desktop-packages] [Bug 1967150] [NEW] gnome-shell crashed with SIGSEGV

Public bug reported:

This was running a live session of the jammy beta candidate image
20220329.1 in qemu. I let it sit for a bit after booting, came back to
the session and came out of the screen blank and saw it reporting this
crash had occurred.  The session has been up 41 minutes but the files in
/var/crash are timestamped from just a few minutes ago so I think it may
have happened coming out of the screen blank.

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
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 14:31:13 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 'au'), 
('xkb', 'cm'), ('xkb', 'gb')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
 PATH=(custom, no user)
 LANG=C.UTF-8
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SegvAnalysis:
 Segfault happened at: 0x7f8255af2f44:  mov(%rsi),%rax
 PC (0x7f8255af2f44) ok
 source "(%rsi)" (0x35d82c10) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
 #0  0x7f8255af2f44 in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

** Affects: gnome-shell (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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967150

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This was running a live session of the jammy beta candidate image
  20220329.1 in qemu. I let it sit for a bit after booting, came back to
  the session and came out of the screen blank and saw it reporting this
  crash had occurred.  The session has been up 41 minutes but the files
  in /var/crash are timestamped from just a few minutes ago so I think
  it may have happened coming out of the screen blank.

  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
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 14:31:13 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C.UTF-8
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SegvAnalysis:
   Segfault happened at: 0x7f8255af2f44:mov(%rsi),%rax
   PC (0x7f8255af2f44) ok
   source "(%rsi)" (0x35d82c10) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f8255af2f44 in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
  StacktraceTop: ?? ()
  Title: gnome-shell 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-shell/+bug/1967150/+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 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts

Ubuntu 21.04 is no longer supported. If you are using 21.04, please upgrade to 
21.10.
https://wiki.ubuntu.com/Releases

-- 
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/36812

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

Status in gnome-control-center:
  Unknown
Status in X.Org X server:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press  (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  For users being affected by this problem, the easiest solution for now is to 
add this PPA in your repositories:
  https://launchpad.net/~oded-geek/+archive/xorg-patches

  Practical summary of this bug for ubuntu developers (since reading 120 
comments is impractical for most):
  This problem is a really old (since 2004) issue of the xkb part of xorg; the 
main discussion was made upstream in freedesktop-bugs #865. There has been a 
patch from Ilya Murav'jov for upstream (#55), and attached here (#61).
  Upstream xorg has refused to apply the patch, mainly because it "explicitly 
contradicts the (xkb) spec"  (#84, #91).
  This patch has been reported to work for many people without any problems, 
and there is also a PPA by Oded Arbel (#95) where he maintains a patched 
version of the ubuntu xorg.
  The proper resolution of this bug would be to apply this patch to the 
upstream xorg, or at minimum to the official ubuntu xorg package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share

2022-03-30 Thread renbag

I see the same problem with Ubuntu 20.04 and 22.04, inside an Active Directory 
domain.
With slow machines (e.g. with rotational hard disks) it is always present; with 
fast machines (with SSDs) it is randomly present, maybe because it depends also 
on the time needed to contact the domain controller.

(I'm using a cinnamon desktop and I do not have ibus installed)
I have applied the following workaround:
copy /usr/lib/systemd/user/gvfs-daemon.service to 
/etc/systemd/user/gvfs-daemon.service
insert in the last file the following line, at the start of the [Service] 
section:

ExecStartPre=bash -c "for i in echo {1..20} ; do if [ $(env | grep
KRB5CCNAME) == "" ]; then sleep 0.2 ; fi ; done"

In this way it is possible to browse the network with Nemo or Nautilus,
without asking for user authentication.

When the workaround is not present I see this message in
/var/log/syslog:

Mar 30 10:30:36 pc000327 gvfsd[2656]: got no contact to IPC$
Mar 30 10:30:39 pc000327 gvfsd[2672]: Kerberos auth with 'aduser@WORKGROUP' 
(WORKGROUP\aduser) to access '10.1.0.107' not possible

(Here kerberos is not aware of the real domain name and tries the
generic WORKGROUP)

I report here also the relevant processes in the case of no workaround:

USER PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
...
root 977  0.0  0.4  78692 19508 ?Ss   12:52   0:00 
/usr/sbin/winbindd --foreground --no-process-group
root 985  0.0  0.2  78596 11168 ?S12:52   0:00 winbindd: 
domain child [PC000327]
root 989  0.1  0.7 105008 28716 ?Ss   12:52   0:00 
/usr/sbin/smbd --foreground --no-process-group
root 990  0.0  0.4  79840 17180 ?S12:52   0:00 winbindd: 
domain child [DOMAIN]
root 994  0.0  0.4  80464 16344 ?S12:52   0:00 winbindd: 
idmap child
root1002  0.0  0.5  97132 20524 ?S12:52   0:00 
/usr/lib/x86_64-linux-gnu/samba/samba-bgqd --ready-signal-fd=48 
--parent-watch-fd=12 --debuglevel=0 -F
root1014  1.2  2.5 153464 99180 ?S12:52   0:01 
/usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --logger=files
root1015  0.0  0.3  98056 14612 ?S12:52   0:00 
/usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --logger=files
root1021  0.1  0.2  57304  8144 ?Ss   12:52   0:00 
/lib/systemd/systemd-logind
root1121 15.2  2.7 272756 108420 ?   S12:52   0:18 
/usr/libexec/sssd/sssd_be --domain addomain.it --uid 0 --gid 0 --logger=files
root1213  0.0  0.2 190492 11168 ?Sl   12:53   0:00 lightdm 
--session-child 12 19
root1271  0.0  0.4 138968 16544 ?Ss   12:53   0:00 
/usr/libexec/sssd/sssd_pac --logger=files --socket-activated
aduser  1279  0.5  0.2  17388 10136 ?Ss   12:53   0:00 
/lib/systemd/systemd --user
aduser  1292  0.6  0.1  29736  5824 ?Ss   12:53   0:00 
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile 
--systemd-activation --syslog-only
aduser  1294  0.0  0.1 241124  7680 ?Sl   12:53   0:00 
/usr/bin/gnome-keyring-daemon --daemonize --login
aduser  1298  0.1  0.2 240844  8672 ?Ssl  12:53   0:00 
/usr/libexec/gvfsd
aduser  1305  0.0  0.1 380884  7012 ?Sl   12:53   0:00 
/usr/libexec/gvfsd-fuse /run/user/1136602666/gvfs -f
aduser  1314  0.6  0.6 376912 27500 ?Ssl  12:53   0:00 
cinnamon-session --session cinnamon
aduser  1326  1.5  0.6 707460 26600 ?SNsl 12:53   0:00 
/usr/libexec/tracker-miner-fs-3
aduser  1372  0.0  0.2 325748 10224 ?Ssl  12:53   0:00 
/usr/libexec/gvfs-udisks2-volume-monitor

and when the workaround is present:

USER PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
...
root 873  0.4  2.5 153440 98936 ?S12:43   0:01 
/usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --logger=files
root 874  0.0  0.3  98068 14344 ?S12:43   0:00 
/usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --logger=files
root 885  0.0  0.3  70704 15060 ?Ss   12:43   0:00 
/usr/sbin/nmbd --foreground --no-process-group
root 973  0.0  0.4  78692 19632 ?Ss   12:43   0:00 
/usr/sbin/winbindd --foreground --no-process-group
root 981  0.0  0.2  78596 11108 ?S12:43   0:00 winbindd: 
domain child [PC000327]
root 982  0.0  0.4  79844 17164 ?S12:43   0:00 winbindd: 
domain child [DOMAIN]
root 986  0.0  0.7 105008 28736 ?Ss   12:43   0:00 
/usr/sbin/smbd --foreground --no-process-group
root1001  0.0  0.4  80464 16344 ?S12:43   0:00 winbindd: 
idmap child
root1004  0.0  0.5  97132 20376 ?S12:43   0:00 
/usr/lib/x86_64-linux-gnu/samba/samba-bgqd --ready-signal-fd=48 
--parent-watch-fd=12 --debuglevel=0 -F
root1010  0.0  0.2 249880  8900 ?Ssl  12:43   0:00 
/usr/libexec/accounts-daemon
root1013  0.0  0.2  57312  7968 ?Ss   12:43   0:00

[Desktop-packages] [Bug 1967127] Re: [FFe] update libarchive to 3.6.0

** Description changed:

- .
+ I request a Feature Freeze Exception to update libarchive from 3.5.2 to
+ 3.6.0 and build evince with libarchive 3.6.
+
+ This will allow us to drop 2 revert commits we added to evince to build with
the older libarchive.
+ https://salsa.debian.org/gnome-team/evince/-/commit/badb5b65b
+
+ Changes
+ ---
+ https://github.com/libarchive/libarchive/releases/tag/v3.6.0
+ https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0
+
+ Other Changes
+ -
+ 1. I am cherry-picking a security fix for CVE-2022-26280
+ 2. debian/rules was only running dh_auto_test if 'check' was set in
DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set. That
way we run the build tests by default.
+
+ I'm forwarding both those changes to Debian soon.
+
+ Build logs
+ --
+
https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13404994/+listing-archive-extra
+
+ https://buildd.debian.org/status/package.php?p=evince
+
+ Testing done
+
+ No errors in the install logs
+
+ Evince still works fine to open a variety of PDFs and a .cbz file I have.
+ File Roller still works fine to open a variety of compressed file types.

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

** Description changed:

I request a Feature Freeze Exception to update libarchive from 3.5.2 to
3.6.0 and build evince with libarchive 3.6.

This will allow us to drop 2 revert commits we added to evince to build with
the older libarchive.
https://salsa.debian.org/gnome-team/evince/-/commit/badb5b65b

Changes
---
https://github.com/libarchive/libarchive/releases/tag/v3.6.0
https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0

Other Changes
-
- 1. I am cherry-picking a security fix for CVE-2022-26280
- 2. debian/rules was only running dh_auto_test if 'check' was set in
DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set. That
way we run the build tests by default.
+ 1. libarchive: I am cherry-picking a security fix for CVE-2022-26280
+ 2. libarchive: debian/rules was only running dh_auto_test if 'check' was set
in DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set.
That way we run the build tests by default.

I'm forwarding both those changes to Debian soon.

Build logs
--

https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13404994/+listing-archive-extra

https://buildd.debian.org/status/package.php?p=evince

Testing done

No errors in the install logs

Evince still works fine to open a variety of PDFs and a .cbz file I have.
File Roller still works fine to open a variety of compressed file types.

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

Title:
[FFe] update libarchive to 3.6.0

Status in evince package in Ubuntu:
New
Status in libarchive package in Ubuntu:
New

Bug description:
I request a Feature Freeze Exception to update libarchive from 3.5.2
to 3.6.0 and build evince with libarchive 3.6.

This will allow us to drop 2 revert commits we added to evince to build with
the older libarchive.
https://salsa.debian.org/gnome-team/evince/-/commit/badb5b65b

Changes
---
https://github.com/libarchive/libarchive/releases/tag/v3.6.0
https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0

Other Changes
-
1. libarchive: I am cherry-picking a security fix for CVE-2022-26280
2. libarchive: debian/rules was only running dh_auto_test if 'check' was set
in DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set.
That way we run the build tests by default.

I'm forwarding both those changes to Debian soon.

Build logs
--

https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13404994/+listing-archive-extra

https://buildd.debian.org/status/package.php?p=evince

Testing done

No errors in the install logs

Evince still works fine to open a variety of PDFs and a .cbz file I have.
File Roller still works fine to open a variety of compressed file types.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1967127/+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 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts

2022-03-30 Thread WildWeasel

I don't understand why hirsute has been removed, I'm using it and just
hit this bug. Please restore the hirsute tag.

-- 
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/36812

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

Status in gnome-control-center:
  Unknown
Status in X.Org X server:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press  (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  For users being affected by this problem, the easiest solution for now is to 
add this PPA in your repositories:
  https://launchpad.net/~oded-geek/+archive/xorg-patches

  Practical summary of this bug for ubuntu developers (since reading 120 
comments is impractical for most):
  This problem is a really old (since 2004) issue of the xkb part of xorg; the 
main discussion was made upstream in freedesktop-bugs #865. There has been a 
patch from Ilya Murav'jov for upstream (#55), and attached here (#61).
  Upstream xorg has refused to apply the patch, mainly because it "explicitly 
contradicts the (xkb) spec"  (#84, #91).
  This patch has been reported to work for many people without any problems, 
and there is also a PPA by Oded Arbel (#95) where he maintains a patched 
version of the ubuntu xorg.
  The proper resolution of this bug would be to apply this patch to the 
upstream xorg, or at minimum to the official ubuntu xorg package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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 1966871] Re: Unable to play music in gnome but able to play in "speaker-test" after upgrade

2022-03-30 Thread Xavier Hsinyuan

Fixed after checking pipewire-media-session release note. Thanks for
your reply!

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1966871

Title:
  Unable to play music in gnome but able to play in "speaker-test" after
  upgrade

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  ==
  pulseaudio:
Installed：1:15.99.1+dfsg1-1ubuntu1
  pipewire:
Installed：0.3.48-1ubuntu1
  ==

  After upgrade to 22.04 dev branch, it seems that gnome the desktop
  environment and applications can't detect sound output devices. But
  "speaker-test" and "aplay" works fine with root privileges.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-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
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 29 15:01:27 2022
  InstallationDate: Installed on 2021-05-01 (332 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to jammy on 2022-01-23 (64 days ago)
  dmi.bios.date: 09/11/2020
  dmi.bios.release: 106.117
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0E07
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0E07:bd09/11/2020:br106.117:efr0.7:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:skuTM1701-16773:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.product.sku: TM1701-16773
  dmi.sys.vendor: Timi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966871/+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 1949291] Re: LibreOffice has started displaying a donation nag

With my LibreOffice Design Team Member hat on, I think it’s fine if
Debian and Ubuntu carry a distro patch like this to disable the infobar:
https://cgit.freedesktop.org/libreoffice/core/commit/?h=distro/mimo/mimo-7-2=adc2ecfaa9da2f26fa6ac77114e7f912efd791f4

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

Title:
  LibreOffice has started displaying a donation nag

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I just opened up a spreadsheet (technically a CSV file, but who's
  counting), to discover LibreOffice displaying an eye-catching blue
  "Your donations support our worldwide community." banner just below
  the toolbars and about a toolbar and a half tall.

  This irritating nag is apparently supposed to display every 90 to 180
  days with no in-application means to disable it permanently, and
  there's apparently also a "Help us make LibreOffice even better!"
  banner that can appear too.

  According to this blog post...

  https://www.remembertheusers.com/2019/11/0580-libreoffice-nag-
  notices.html

  ...it is not responsive to configuration overrides within the user
  profile and the only apparent solution that doesn't require patching
  the source and rebuilding is to create a file containing the following
  markup in `$BASEDIR/share/registry`
  (`/usr/lib/libreoffice/share/registry` as installed by the Ubuntu
  package):

  
  http://www.w3.org/2001/XMLSchema; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xmlns:oor="http://openoffice.org/2001/registry;>

http://openoffice.org/2004/installation; oor:name="Setup" 
oor:package="org.openoffice">
  

  0


  0

  

  

  Regardless of how it's achieved, I think it's tasteless, irritating,
  and probably doesn't give a very good image to any office customers
  Ubuntu may have downstream for random employees to be receiving nag
  banners like that in IT-installed software.

  Please consider patching it out or otherwise ensuring it never
  triggers in distro-provided builds of LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Oct 31 04:32:03 2021
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1949291/+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 1964541] Re: Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 (Wayland session)

2022-03-30 Thread Treviño

Take in mind that upgrading the shell you're also using libmutter-10
instead of libmutter-9, so the problem may be anywhere in both (more
likely in mutter).

So the only way to find out what may have changed this is using git
bisect over the various mutter versions (might be annoying, because you
need to keep shell in sync with that).

If the unconfined snap isn't affected, could be that mutter is now using
something that is blocked by the confinement?

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

Title:
  Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell
  42 (Wayland session)

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.

  syslog has the following:

  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.

  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1964541/+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 1966589] Re: Upgrader unable to contact snap store

Tested again - this time with TUI interface (do-release-upgrade) from a 
terminal and the upgrade finished with the error - "This upgrade has finished 
but there were errors.." 
During the upgrade I noticed that the snap store was not contacted.
After reboot I noticed that Firefox was still the deb version - opened Discover 
to apply updates and noticed (see screenshot) that758.4 MB were waiting to 
update. Comments 6 to 14 are from this upgrade.

Also note - running lsb_release - r shows 22.04 (wallpaper not updated)
and Prompt shows = Prompt=lts

I thought best to not file a new bug report as it seems to be same
result of snap store.



** Attachment added: "screen1.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1966589/+attachment/5574769/+files/screen1.jpg

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

Title:
  Upgrader unable to contact snap store

Status in firefox package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date
  27.03.2022)

  The upgrader was unable to connect to the snap store in order to
  install the firefox snap

  The upgrade was performed with GUI - do-release-upgrade -d -m desktop
  -f DistUpgradeViewKDE

  The error "could not install the upgrades" was received.
  I closed the error and then received th dialog box message "upgrade complete 
but there were errors during the upgrade process"

  After rebooting I received an upgrade notification and the Firefox
  snap was installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.7
  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
  CrashDB: ubuntu
  CurrentDesktop: LXQt
  Date: Sun Mar 27 13:08:26 2022
  InstallationDate: Installed on 2022-03-27 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kf  950 F pulseaudio
  BuildID: 20220322144853
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: LXQt
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 22.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  IpRoute:
   default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 
   192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 
metric 100
  Package: ubuntu-release-upgrader
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=98.0.2/20220322144853 (In use)
  RunningIncompatibleAddons: False
  Tags:  jammy
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.2
  dmi.board.name: 0Y7WYT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9

[Desktop-packages] [Bug 1967109] Re: Xubuntu Docs installed at /usr/share/xubuntu-docs/index.html is not accessible with firefox snap

** Changed in: xubuntu-default-settings (Ubuntu)
   Status: New => Triaged

** Changed in: firefox (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Xubuntu Docs installed at /usr/share/xubuntu-docs/index.html is not
  accessible with firefox snap

Status in firefox package in Ubuntu:
  Triaged
Status in xubuntu-default-settings package in Ubuntu:
  Triaged

Bug description:
  Xubuntu's documentation is stored at /usr/share/xubuntu-
  docs/index.html

  The firefox snap is not able to access this file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967109/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)

** Changed in: libreoffice (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  libreoffice help doesn't open in firefox (404 error on
  file:///tmp/lu417531j7po.tmp/NewHelp0.html)

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Ubuntu jammy live QA-test on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  Opened LibreOffice Writer as random apps in QA-test.
  Hit F1 to call help, and all I get is an error

  URL:  file:///tmp/lu417531j7po.tmp/NewHelp0.html

  ---
  File not found

  Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  Firefox opens as a snap; but it isn't accessing the data from
  LibreOffice.

  Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks-
  libreoffice-deb/27537

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465+canary3.3
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 17 04:46:33 2021
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+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 1966418] Re: [jammy regression] Evolution does not display message content anymore

2022-03-30 Thread Sebastien Bacher

the issue is in the library there is no need to add every client
software

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

** Changed in: evolution (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: epiphany-browser (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit/+bug/1966418/+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 1966589] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1966589/+attachment/5574768/+files/PulseList.txt

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

Title:
  Upgrader unable to contact snap store

Status in firefox package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date
  27.03.2022)

  The upgrader was unable to connect to the snap store in order to
  install the firefox snap

  The upgrade was performed with GUI - do-release-upgrade -d -m desktop
  -f DistUpgradeViewKDE

  The error "could not install the upgrades" was received.
  I closed the error and then received th dialog box message "upgrade complete 
but there were errors during the upgrade process"

  After rebooting I received an upgrade notification and the Firefox
  snap was installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.7
  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
  CrashDB: ubuntu
  CurrentDesktop: LXQt
  Date: Sun Mar 27 13:08:26 2022
  InstallationDate: Installed on 2022-03-27 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kf  950 F pulseaudio
  BuildID: 20220322144853
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: LXQt
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 22.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  IpRoute:
   default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 
   192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 
metric 100
  Package: ubuntu-release-upgrader
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=98.0.2/20220322144853 (In use)
  RunningIncompatibleAddons: False
  Tags:  jammy
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.2
  dmi.board.name: 0Y7WYT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] PciNetwork.txt

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1966589/+attachment/5574764/+files/PciNetwork.txt

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

Title:
  Upgrader unable to contact snap store

Status in firefox package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date
  27.03.2022)

  The upgrader was unable to connect to the snap store in order to
  install the firefox snap

  The upgrade was performed with GUI - do-release-upgrade -d -m desktop
  -f DistUpgradeViewKDE

  The error "could not install the upgrades" was received.
  I closed the error and then received th dialog box message "upgrade complete 
but there were errors during the upgrade process"

  After rebooting I received an upgrade notification and the Firefox
  snap was installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.7
  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
  CrashDB: ubuntu
  CurrentDesktop: LXQt
  Date: Sun Mar 27 13:08:26 2022
  InstallationDate: Installed on 2022-03-27 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kf  950 F pulseaudio
  BuildID: 20220322144853
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: LXQt
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 22.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  IpRoute:
   default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 
   192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 
metric 100
  Package: ubuntu-release-upgrader
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=98.0.2/20220322144853 (In use)
  RunningIncompatibleAddons: False
  Tags:  jammy
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.2
  dmi.board.name: 0Y7WYT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1966589/+attachment/5574765/+files/ProcCpuinfoMinimal.txt

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

Title:
  Upgrader unable to contact snap store

Status in firefox package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date
  27.03.2022)

  The upgrader was unable to connect to the snap store in order to
  install the firefox snap

  The upgrade was performed with GUI - do-release-upgrade -d -m desktop
  -f DistUpgradeViewKDE

  The error "could not install the upgrades" was received.
  I closed the error and then received th dialog box message "upgrade complete 
but there were errors during the upgrade process"

  After rebooting I received an upgrade notification and the Firefox
  snap was installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.7
  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
  CrashDB: ubuntu
  CurrentDesktop: LXQt
  Date: Sun Mar 27 13:08:26 2022
  InstallationDate: Installed on 2022-03-27 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kf  950 F pulseaudio
  BuildID: 20220322144853
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: LXQt
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 22.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  IpRoute:
   default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 
   192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 
metric 100
  Package: ubuntu-release-upgrader
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=98.0.2/20220322144853 (In use)
  RunningIncompatibleAddons: False
  Tags:  jammy
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.2
  dmi.board.name: 0Y7WYT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1966589/+attachment/5574766/+files/ProcEnviron.txt

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

Title:
  Upgrader unable to contact snap store

Status in firefox package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date
  27.03.2022)

  The upgrader was unable to connect to the snap store in order to
  install the firefox snap

  The upgrade was performed with GUI - do-release-upgrade -d -m desktop
  -f DistUpgradeViewKDE

  The error "could not install the upgrades" was received.
  I closed the error and then received th dialog box message "upgrade complete 
but there were errors during the upgrade process"

  After rebooting I received an upgrade notification and the Firefox
  snap was installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.7
  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
  CrashDB: ubuntu
  CurrentDesktop: LXQt
  Date: Sun Mar 27 13:08:26 2022
  InstallationDate: Installed on 2022-03-27 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kf  950 F pulseaudio
  BuildID: 20220322144853
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: LXQt
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 22.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  IpRoute:
   default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 
   192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 
metric 100
  Package: ubuntu-release-upgrader
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=98.0.2/20220322144853 (In use)
  RunningIncompatibleAddons: False
  Tags:  jammy
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.2
  dmi.board.name: 0Y7WYT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] Profile0Prefs.txt

apport information

** Attachment added: "Profile0Prefs.txt"
   
https://bugs.launchpad.net/bugs/1966589/+attachment/5574767/+files/Profile0Prefs.txt

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

Title:
  Upgrader unable to contact snap store

Status in firefox package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date
  27.03.2022)

  The upgrader was unable to connect to the snap store in order to
  install the firefox snap

  The upgrade was performed with GUI - do-release-upgrade -d -m desktop
  -f DistUpgradeViewKDE

  The error "could not install the upgrades" was received.
  I closed the error and then received th dialog box message "upgrade complete 
but there were errors during the upgrade process"

  After rebooting I received an upgrade notification and the Firefox
  snap was installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.7
  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
  CrashDB: ubuntu
  CurrentDesktop: LXQt
  Date: Sun Mar 27 13:08:26 2022
  InstallationDate: Installed on 2022-03-27 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kf  950 F pulseaudio
  BuildID: 20220322144853
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: LXQt
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 22.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  IpRoute:
   default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 
   192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 
metric 100
  Package: ubuntu-release-upgrader
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=98.0.2/20220322144853 (In use)
  RunningIncompatibleAddons: False
  Tags:  jammy
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.2
  dmi.board.name: 0Y7WYT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] Lspci.txt