date:20220418

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

Please update your system:

  sudo apt update
  sudo apt full-upgrade

and then ensure you have these debug symbols installed before getting a
stack trace from gdb:

https://launchpad.net/ubuntu/+archive/primary/+files/libmutter-10-0-dbgsym_42.0-3ubuntu2_amd64.ddeb

Alternatively just follow the instructions in
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

Please also run this command to gather more system info:

  apport-collect 1969351

** Summary changed:

- gnome-shell crashing after suspend or switching TTYs - libgbm.so.1
+ gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer()

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

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer()

Status in mutter package in Ubuntu:
  New

Bug description:
  When using Wayland on Ubuntu 22.04 gnome-shell is crashing anytime you
  leave the Desktop and return to the login screen.

  dmesg -
  [ 6522.928409] gnome-shell[20890]: segfault at 20 ip 0020 sp 
7ffe402baef8 error 14
  [ 6522.928414] Code: Unable to access opcode bytes at RIP 0xfff6.

  gdb -
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f4e2b0070d7 in gbm_surface_release_buffer () from 
/lib/x86_64-linux-gnu/libgbm.so.1

  (gdb) backtrace
  #0  0x7f93da12d0d7 in gbm_surface_release_buffer () at 
/lib/x86_64-linux-gnu/libgbm.so.1
  #1  0x7f93dc4e48ff in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #2  0x7f93dd1f8dfd in g_object_unref () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #3  0x7f93dc4edd40 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #4  0x7f93dd0d5698 in g_hash_table_foreach () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #5  0x7f93dc4f9fcc in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #6  0x7f93dc5141ae in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #7  0x7f93dc4fa03d in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #8  0x7f93dd0f1c24 in g_main_context_dispatch () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x7f93dd1466f8 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #10 0x7f93dd0f1293 in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7f93dc462209 in meta_context_run_main_loop () at 
/lib/x86_64-linux-gnu/libmutter-10.so.0
  #12 0x56280e1b6ed2 in  ()
  #13 0x7f93dc193d90 in __libc_start_call_main 
(main=main@entry=0x56280e1b6a30, argc=argc@entry=1, 
argv=argv@entry=0x7ffc82080608) at ../sysdeps/nptl/libc_start_call_main.h:58
  #14 0x7f93dc193e40 in __libc_start_main_impl (main=0x56280e1b6a30, 
argc=1, argv=0x7ffc82080608, init=, fini=, 
rtld_fini=, stack_end=0x7ffc820805f8) at ../csu/libc-start.c:392
  #15 0x56280e1b7155 in  ()

  Also Wayland shows my monitors backwards, left on the right, right on
  the left. Works fine in Xorg.

  If i try to rearrange the physical displays of my 2 monitors, I get kicked 
out when pressing apply. 
  dmesg -
  [ 7618.079350] traps: gnome-shell[25726] general protection fault 
ip:7f34373be0d7 sp:7ffcfb2a9538 error:0 in libgbm.so.1.0.0[7f34373b7000+8000]

  System:
Host: desktop Kernel: 5.17.0-1003-oem x86_64 bits: 64 compiler: gcc
  v: 11.2.0 Desktop: GNOME 42.0 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3
  Distro: Ubuntu 22.04 (Jammy Jellyfish)
  CPU:
Info: quad core model: Intel Core i5-7600K bits: 64 type: MCP
  arch: Kaby Lake rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 4401 high: 4404 min/max: 800/4400 cores: 1: 4401
  2: 4400 3: 4400 4: 4404 bogomips: 30399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel
  ports: active: HDMI-A-3 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:5912
Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
  vendor: Sapphire driver: amdgpu v: kernel pcie: speed: 2.5 GT/s lanes: 16
  ports: active: HDMI-A-5 empty: DP-3, DP-4, DVI-D-1, HDMI-A-4
  bus-ID: 01:00.0 chip-ID: 1002:67df
Device-3: Logitech HD Webcam C615 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-3:3 chip-ID: 046d:082c
Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: radeon
  gpu: amdgpu,i915 display-ID: 0
Monitor-1: HDMI-A-3 model: Asus VG23A res: 1920x1080 dpi: 91
  diag: 618mm (24.3")
Monitor-2: HDMI-A-5 model: Samsung res: 1920x1080 dpi: 44
  diag: 1271mm (50.1")
OpenGL: renderer: AMD Radeon RX 580 Series (polaris10 LLVM 14.0.0 DRM
  3.44

[Desktop-packages] [Bug 1969351] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer()

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

Actually it looks like:

https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4

in which case we may not need any more info.

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer()

Status in mutter package in Ubuntu:
  New

Bug description:
  When using Wayland on Ubuntu 22.04 gnome-shell is crashing anytime you
  leave the Desktop and return to the login screen.

  dmesg -
  [ 6522.928409] gnome-shell[20890]: segfault at 20 ip 0020 sp 
7ffe402baef8 error 14
  [ 6522.928414] Code: Unable to access opcode bytes at RIP 0xfff6.

  gdb -
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f4e2b0070d7 in gbm_surface_release_buffer () from 
/lib/x86_64-linux-gnu/libgbm.so.1

  (gdb) backtrace
  #0  0x7f93da12d0d7 in gbm_surface_release_buffer () at 
/lib/x86_64-linux-gnu/libgbm.so.1
  #1  0x7f93dc4e48ff in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #2  0x7f93dd1f8dfd in g_object_unref () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #3  0x7f93dc4edd40 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #4  0x7f93dd0d5698 in g_hash_table_foreach () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #5  0x7f93dc4f9fcc in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #6  0x7f93dc5141ae in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #7  0x7f93dc4fa03d in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #8  0x7f93dd0f1c24 in g_main_context_dispatch () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x7f93dd1466f8 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #10 0x7f93dd0f1293 in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7f93dc462209 in meta_context_run_main_loop () at 
/lib/x86_64-linux-gnu/libmutter-10.so.0
  #12 0x56280e1b6ed2 in  ()
  #13 0x7f93dc193d90 in __libc_start_call_main 
(main=main@entry=0x56280e1b6a30, argc=argc@entry=1, 
argv=argv@entry=0x7ffc82080608) at ../sysdeps/nptl/libc_start_call_main.h:58
  #14 0x7f93dc193e40 in __libc_start_main_impl (main=0x56280e1b6a30, 
argc=1, argv=0x7ffc82080608, init=, fini=, 
rtld_fini=, stack_end=0x7ffc820805f8) at ../csu/libc-start.c:392
  #15 0x56280e1b7155 in  ()

  Also Wayland shows my monitors backwards, left on the right, right on
  the left. Works fine in Xorg.

  If i try to rearrange the physical displays of my 2 monitors, I get kicked 
out when pressing apply. 
  dmesg -
  [ 7618.079350] traps: gnome-shell[25726] general protection fault 
ip:7f34373be0d7 sp:7ffcfb2a9538 error:0 in libgbm.so.1.0.0[7f34373b7000+8000]

  System:
Host: desktop Kernel: 5.17.0-1003-oem x86_64 bits: 64 compiler: gcc
  v: 11.2.0 Desktop: GNOME 42.0 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3
  Distro: Ubuntu 22.04 (Jammy Jellyfish)
  CPU:
Info: quad core model: Intel Core i5-7600K bits: 64 type: MCP
  arch: Kaby Lake rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 4401 high: 4404 min/max: 800/4400 cores: 1: 4401
  2: 4400 3: 4400 4: 4404 bogomips: 30399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel
  ports: active: HDMI-A-3 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:5912
Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
  vendor: Sapphire driver: amdgpu v: kernel pcie: speed: 2.5 GT/s lanes: 16
  ports: active: HDMI-A-5 empty: DP-3, DP-4, DVI-D-1, HDMI-A-4
  bus-ID: 01:00.0 chip-ID: 1002:67df
Device-3: Logitech HD Webcam C615 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-3:3 chip-ID: 046d:082c
Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: radeon
  gpu: amdgpu,i915 display-ID: 0
Monitor-1: HDMI-A-3 model: Asus VG23A res: 1920x1080 dpi: 91
  diag: 618mm (24.3")
Monitor-2: HDMI-A-5 model: Samsung res: 1920x1080 dpi: 44
  diag: 1271mm (50.1")
OpenGL: renderer: AMD Radeon RX 580 Series (polaris10 LLVM 14.0.0 DRM
  3.44 5.17.0-1003-oem)
  v: 4.6 Mesa 22.1.0-devel direct render: Yes

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

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

** Changed in: webkit2gtk (Ubuntu)
   Status: New => Confirmed

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

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 1969351] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer()

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

We can use bug 1969422 to track it now.

** This bug has been marked a duplicate of bug 1969422
   gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from 
meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from 
g_set_object()

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer()

Status in mutter package in Ubuntu:
  New

Bug description:
  When using Wayland on Ubuntu 22.04 gnome-shell is crashing anytime you
  leave the Desktop and return to the login screen.

  dmesg -
  [ 6522.928409] gnome-shell[20890]: segfault at 20 ip 0020 sp 
7ffe402baef8 error 14
  [ 6522.928414] Code: Unable to access opcode bytes at RIP 0xfff6.

  gdb -
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f4e2b0070d7 in gbm_surface_release_buffer () from 
/lib/x86_64-linux-gnu/libgbm.so.1

  (gdb) backtrace
  #0  0x7f93da12d0d7 in gbm_surface_release_buffer () at 
/lib/x86_64-linux-gnu/libgbm.so.1
  #1  0x7f93dc4e48ff in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #2  0x7f93dd1f8dfd in g_object_unref () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #3  0x7f93dc4edd40 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #4  0x7f93dd0d5698 in g_hash_table_foreach () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #5  0x7f93dc4f9fcc in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #6  0x7f93dc5141ae in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #7  0x7f93dc4fa03d in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #8  0x7f93dd0f1c24 in g_main_context_dispatch () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x7f93dd1466f8 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #10 0x7f93dd0f1293 in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7f93dc462209 in meta_context_run_main_loop () at 
/lib/x86_64-linux-gnu/libmutter-10.so.0
  #12 0x56280e1b6ed2 in  ()
  #13 0x7f93dc193d90 in __libc_start_call_main 
(main=main@entry=0x56280e1b6a30, argc=argc@entry=1, 
argv=argv@entry=0x7ffc82080608) at ../sysdeps/nptl/libc_start_call_main.h:58
  #14 0x7f93dc193e40 in __libc_start_main_impl (main=0x56280e1b6a30, 
argc=1, argv=0x7ffc82080608, init=, fini=, 
rtld_fini=, stack_end=0x7ffc820805f8) at ../csu/libc-start.c:392
  #15 0x56280e1b7155 in  ()

  Also Wayland shows my monitors backwards, left on the right, right on
  the left. Works fine in Xorg.

  If i try to rearrange the physical displays of my 2 monitors, I get kicked 
out when pressing apply. 
  dmesg -
  [ 7618.079350] traps: gnome-shell[25726] general protection fault 
ip:7f34373be0d7 sp:7ffcfb2a9538 error:0 in libgbm.so.1.0.0[7f34373b7000+8000]

  System:
Host: desktop Kernel: 5.17.0-1003-oem x86_64 bits: 64 compiler: gcc
  v: 11.2.0 Desktop: GNOME 42.0 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3
  Distro: Ubuntu 22.04 (Jammy Jellyfish)
  CPU:
Info: quad core model: Intel Core i5-7600K bits: 64 type: MCP
  arch: Kaby Lake rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 4401 high: 4404 min/max: 800/4400 cores: 1: 4401
  2: 4400 3: 4400 4: 4404 bogomips: 30399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel
  ports: active: HDMI-A-3 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:5912
Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
  vendor: Sapphire driver: amdgpu v: kernel pcie: speed: 2.5 GT/s lanes: 16
  ports: active: HDMI-A-5 empty: DP-3, DP-4, DVI-D-1, HDMI-A-4
  bus-ID: 01:00.0 chip-ID: 1002:67df
Device-3: Logitech HD Webcam C615 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-3:3 chip-ID: 046d:082c
Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: radeon
  gpu: amdgpu,i915 display-ID: 0
Monitor-1: HDMI-A-3 model: Asus VG23A res: 1920x1080 dpi: 91
  diag: 618mm (24.3")
Monitor-2: HDMI-A-5 model: Samsung res: 1920x1080 dpi: 44
  diag: 1271mm (50.1")
OpenGL: renderer: AMD Radeon RX 580 Series (polaris10 LLVM 14.0.0 DRM
  3.44 5.17.0-1003-oem)
  v: 4.6 Mesa 22.1.0-devel direct render: Yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969351/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(

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

** Changed in: mutter (Ubuntu)
   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/1969422

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969422/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(

** Summary changed:

- 
/usr/bin/gnome-shell:11:gbm_surface_release_buffer:meta_drm_buffer_gbm_finalize:g_object_unref:g_object_unref:g_set_object
+ gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from 
meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from 
g_set_object()

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Tags added: triple-buffering

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

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969422/+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 1969422] [NEW] gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_objec

2022-04-18 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

** Affects: mutter (Ubuntu)
 Importance: High
 Assignee: Daniel van Vugt (vanvugt)
 Status: Confirmed


** Tags: jammy triple-buffering

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969422/+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 1969307] Re: Firefox Snap launcher keeps disappearing

** Package changed: gnome-session (Ubuntu) => unity (Ubuntu)

** Summary changed:

- Firefox Snap launcher keeps disappearing
+ Firefox Snap launcher keeps disappearing from Unity launcher

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

Title:
  Firefox Snap launcher keeps disappearing from Unity launcher

Status in unity package in Ubuntu:
  New

Bug description:
  I have the Firefox Snap launcher pinned on Unity's side
  launcher/panel, but it keeps disappearing.

  I believe it happens after every Firefox update.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: unity-session 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Apr 17 12:24:25 2022
  InstallationDate: Installed on 2022-02-06 (69 days ago)
  InstallationMedia: Ubuntu Unity 22.04
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1969307/+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 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time

Bug 1969097 sounds like it might explain it.

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

Title:
  System fallback to gdm login screen when hot-plugging a external
  monitor in 1st time

Status in OEM Priority Project:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  [Steps to reproduce]
  1. Install Jammy daily build
  2. dist-upgrade to verify https://bugs.launchpad.net/mutter/+bug/1964037
  3. reboot with no attach monitor
  4. attach monitor after booting

  [Expect result]
  external monitor works directly

  [Actual result]
  system go back to gdm login screen

  [Additional information]
  1. the external port is connecting to dGPU.
  2. happens on wayland only
  3. Only back to login screen in 1st attach, 2nd, 3rd, etc.. works good

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 14 21:22:47 2022
  InstallationDate: Installed on 2022-04-13 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969121/+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 1969406] Re: Problem with right click on an app in dock

Please check bug 1967121 to see if it's the same issue.

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Incomplete

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

Title:
  Problem with right click on an app in dock

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

Bug description:
  I'am on Ubuntu 22.04 (developpement branch).
  When I right click on an app in the dock, a little window opens. It's normal. 
But, when I click in this windows to close the applacation windows, the window 
moves down and it makes me click on "Show details". It's pretty annoying 
because I can't close windows with this feature.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 15:41:38 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   anbox-ashmem/1: added
   anbox-binder/1: added
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81b3]
  InstallationDate: Installed on 2022-04-13 (6 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 
(20220412)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=4082b1cb-5861-4f76-b7d1-278936a44624 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.name: 81B3
  dmi.board.vendor: HP
  dmi.board.version: 00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd11/03/2017:br4.6:svnHP:pn:pvr:rvnHP:rn81B3:rvr00:cvnHP:ct3:cvr:sku:
  dmi.product.family: 103C_53316J
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1969406/+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 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10

Reopened from bug 1968395.

** Changed in: chromium-browser (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Wayland Screensharing broken in Ubuntu 21.10

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in pipewire package in Ubuntu:
  Invalid
Status in xdg-desktop-portal package in Ubuntu:
  Invalid
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released

Bug description:
  Freshly installed Ubuntu 21.10, screen sharing does not work with any
  browser, tested the following options:

  - Firefox snap
  - Firefox deb
  - Chromium snap
  - Chromium flatpak

  Steps to reproduce:

  1. Go to 
https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006
  2. Select to share the whole desktop in the xdg-desktop-portal
  3. Notice the orange screen share indicator in Gnome-Shell but actually 
nothing is shared in the browser.

  This should be handled high priority since this is a critical feature
  during the pandemic.

  Filed against ubuntu-meta since I don't know exactly which package to
  blame, whether it's pipewire, xdg-desktop portal or some problem
  directely with mutter / gnome-shell, please reassign accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+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 1968999] Re: [jammy] Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead.

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

** No longer affects: gdm3 (Ubuntu)

** Tags added: wayland-session xwayland

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

Title:
  [jammy] Option "-listen" for file descriptors is deprecated. Please
  use "-listenfd" instead.

Status in mutter package in Ubuntu:
  New

Bug description:
  Hi,

  I see this warning message in the logs:

  root@vougeot:~# journalctl | grep -e -listen
  Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: (WW) Option "-listen" 
for file descriptors is deprecated
  Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: Please use "-listenfd" 
instead.
  Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: (WW) Option "-listen" 
for file descriptors is deprecated
  Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: Please use "-listenfd" 
instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  Uname: Linux 5.17.3-051703-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Apr 14 09:42:34 2022
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 42.0-3ubuntu1
  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/mutter/+bug/1968999/+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 1968395] Re: [impish] Wayland is with the black screen when I share it

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

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 1950040, 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.


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

** This bug has been marked a duplicate of bug 1950040
   Wayland Screensharing broken in Ubuntu 21.10

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

Title:
  [impish] Wayland is with the black screen when I share it

Status in chromium package in Ubuntu:
  Incomplete

Bug description:
  Wayland is with the black screen when I share it.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.16.0-051600-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  9 01:40:22 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-20 (19 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  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/chromium/+bug/1968395/+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 1969097] Re: connecting interfaces with a udev rule triggers return to gdm login screen

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

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

Title:
  connecting interfaces with a udev rule triggers return to gdm login
  screen

Status in snapd:
  Invalid
Status in gdm3 package in Ubuntu:
  Fix Committed

Bug description:
  As part of our udev backend we do something like:
  $ sudo udevadm control --reload-rules ; sudo udevadm trigger 
--subsystem-nomatch=input

  On 22.04 after boot this will trigger the gdm screen to reappear. It
  looks almost like the user is logged out except that the session is
  still running but the user is put on the VT of gdm.

  This was also observed on arch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1969097/+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 1969097] [NEW] connecting interfaces with a udev rule triggers return to gdm login screen

You have been subscribed to a public bug:

As part of our udev backend we do something like:
$ sudo udevadm control --reload-rules ; sudo udevadm trigger 
--subsystem-nomatch=input

On 22.04 after boot this will trigger the gdm screen to reappear. It
looks almost like the user is logged out except that the session is
still running but the user is put on the VT of gdm.

This was also observed on arch.

** Affects: snapd
 Importance: Undecided
 Status: Invalid

** Affects: gdm3 (Ubuntu)
 Importance: Critical
 Status: Fix Committed


** Tags: patch
-- 
connecting interfaces with a udev rule triggers return to gdm login screen
https://bugs.launchpad.net/bugs/1969097
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gdm3 in Ubuntu.

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

[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide]

Alright let's mention both translations to help with text searches.

** Summary changed:

- Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument 
invalide]
+ Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument 
invalide] [drmModeAtomicCommit: Invalid argument]

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

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

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

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+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 1969289] Re: Secondary display does not work

Thanks for the bug report.

There doesn't seem to be any secondary display plugged in according to
the attached files. Please try a different monitor cable.


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

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

** Tags added: multimonitor

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

Title:
  Secondary display does not work

Status in Ubuntu:
  Incomplete

Bug description:
  Secondary display does not work

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 16 20:29:43 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06fd]
  InstallationDate: Installed on 2022-04-14 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=3b34bc2c-2f64-49d2-9734-d6ff9a9d3b14 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2016
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.12.00
  dmi.board.name: 0X1DP8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.12.00:bd09/06/2016:br1.12:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0X1DP8:rvrA00:cvnDellInc.:ct9:cvr:sku06FD:
  dmi.product.name: Inspiron 13-7359
  dmi.product.sku: 06FD
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  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 this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1969289/+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 1969414] [NEW] Fierfox opens with missing title bar and unable to mouse click in the app

2022-04-18 Thread Centaur5

Public bug reported:

Installed the alpha a month ago and didn't experience many issues until
a few days ago. Upon opening firefox, it resumed my previous session,
not as full screen per usual, but I couldn't click tabs or any buttons
in the app. When I try to click a new tab, it thinks I'm interacting
with the website various pixels away (about an inch of screen space.)
Kept hoping that daily updates would fix it but I had to start using
opera. When I tried to drag firefox to full screen, it just pulled a tab
into a new window but I'm unable to switch windows in the dock, I have
to use keyboard shortcuts.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 18 21:11:26 2022
InstallationDate: Installed on 2021-07-14 (278 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Snap.Changes: no changes found
SourcePackage: firefox
UpgradeStatus: Upgraded to jammy on 2022-03-18 (31 days ago)

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

Title:
  Fierfox opens with missing title bar and unable to mouse click in the
  app

Status in firefox package in Ubuntu:
  New

Bug description:
  Installed the alpha a month ago and didn't experience many issues
  until a few days ago. Upon opening firefox, it resumed my previous
  session, not as full screen per usual, but I couldn't click tabs or
  any buttons in the app. When I try to click a new tab, it thinks I'm
  interacting with the website various pixels away (about an inch of
  screen space.) Kept hoping that daily updates would fix it but I had
  to start using opera. When I tried to drag firefox to full screen, it
  just pulled a tab into a new window but I'm unable to switch windows
  in the dock, I have to use keyboard shortcuts.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 21:11:26 2022
  InstallationDate: Installed on 2021-07-14 (278 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969414/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]

Missing the GAMMA_LUT property on this OLED panel still feels like an
i915 kernel bug to me. Not something Intel would intentionally omit.
Please try the latest DRM kernel here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

The upstream mutter bug report also mentioned that a newer kernel solved
it for them.

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

Title:
  Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
  KMS update: CRTC property (GAMMA_LUT) not found]

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Screen can't turn back on by clicking keyboard after screen off by meta + l 
key.
  Try to do VT switch can make the screen back, some error poped when I try to 
wake up screen.

  gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not 
found
  gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not 
found
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  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')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-03-31 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  Tags: wayland-session jammy third-party-packages
  Uname: Linux 5.15.0-23-generic x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  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:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time

If there's no crash then please try Ctrl+Alt+F2. I think I saw a similar
issue last week where the login screen appeared but I was not logged
out. Logging in again returned me to my session but Ctrl+Alt+F2 should
achieve the same.

Sounds like gdm3 might be restarting the login screen (another gnome-
shell instance) too soon and forcing a VT switch away from the user
session.

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

Title:
  System fallback to gdm login screen when hot-plugging a external
  monitor in 1st time

Status in OEM Priority Project:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  [Steps to reproduce]
  1. Install Jammy daily build
  2. dist-upgrade to verify https://bugs.launchpad.net/mutter/+bug/1964037
  3. reboot with no attach monitor
  4. attach monitor after booting

  [Expect result]
  external monitor works directly

  [Actual result]
  system go back to gdm login screen

  [Additional information]
  1. the external port is connecting to dGPU.
  2. happens on wayland only
  3. Only back to login screen in 1st attach, 2nd, 3rd, etc.. works good

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 14 21:22:47 2022
  InstallationDate: Installed on 2022-04-13 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969121/+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 1969387] Re: Wayland stopped working.

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

** This bug has been marked a duplicate of bug 1969243
   gdm 42.0-1ubuntu4 no longer shows Wayland option

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

Title:
  Wayland stopped working.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After install 3 finger swipe worked to switch Workspaces, now it no
  longer works. It seems Wayland stopped working and I'm forced to use
  X11. How can I get Wayland back?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 22:57:49 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-11 (7 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1969387/+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 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time

2022-04-18 Thread jeremyszu

Hi Michael,

do you mean the patch to disable wayland on nVidia?

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

Title:
  System fallback to gdm login screen when hot-plugging a external
  monitor in 1st time

Status in OEM Priority Project:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  [Steps to reproduce]
  1. Install Jammy daily build
  2. dist-upgrade to verify https://bugs.launchpad.net/mutter/+bug/1964037
  3. reboot with no attach monitor
  4. attach monitor after booting

  [Expect result]
  external monitor works directly

  [Actual result]
  system go back to gdm login screen

  [Additional information]
  1. the external port is connecting to dGPU.
  2. happens on wayland only
  3. Only back to login screen in 1st attach, 2nd, 3rd, etc.. works good

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 14 21:22:47 2022
  InstallationDate: Installed on 2022-04-13 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969121/+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 1969406] [NEW] Problem with right click on an app in dock

2022-04-18 Thread Thibaut Dupuy

Public bug reported:

I'am on Ubuntu 22.04 (developpement branch).
When I right click on an app in the dock, a little window opens. It's normal. 
But, when I click in this windows to close the applacation windows, the window 
moves down and it makes me click on "Show details". It's pretty annoying 
because I can't close windows with this feature.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 18 15:41:38 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 anbox-ashmem/1: added
 anbox-binder/1: added
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81b3]
InstallationDate: Installed on 2022-04-13 (6 days ago)
InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220412)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=4082b1cb-5861-4f76-b7d1-278936a44624 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2017
dmi.bios.release: 4.6
dmi.bios.vendor: AMI
dmi.bios.version: F.30
dmi.board.name: 81B3
dmi.board.vendor: HP
dmi.board.version: 00
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd11/03/2017:br4.6:svnHP:pn:pvr:rvnHP:rn81B3:rvr00:cvnHP:ct3:cvr:sku:
dmi.product.family: 103C_53316J
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
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

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


** Tags: amd64 apport-bug jammy ubuntu

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

Title:
  Problem with right click on an app in dock

Status in xorg package in Ubuntu:
  New

Bug description:
  I'am on Ubuntu 22.04 (developpement branch).
  When I right click on an app in the dock, a little window opens. It's normal. 
But, when I click in this windows to close the applacation windows, the window 
moves down and it makes me click on "Show details". It's pretty annoying 
because I can't close windows with this feature.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 15:41:38 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   anbox-ashmem/1: added
   anbox-binder/1: added
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81b3]
  InstallationDate: Installed on 2022-04-13 (6 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 
(20220412)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=4082b1cb-5861-4f76-b7d1-278936a44624 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.name: 81B3
  dmi.board.vendor: HP
  dmi.board.version: 00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd11/03/2017:br4.6:svnHP:pn:pvr:rvnHP:rn81B3:rvr00:cvnHP:ct3:cvr:sku:
  dmi.product.family: 103C_53316J
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  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

[Desktop-packages] [Bug 1969396] Re: gnome-control-center compose key setting does not set compose key

Was able to force the Compose key to work by running the following
command:

gsettings set org.gnome.desktop.input-sources xkb-options
"['altwin:menu', 'compose:ralt', 'lv3:none']"

seems impossible to get to this configuration via the UI.

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

Title:
  gnome-control-center compose key setting does not set compose key

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

Bug description:
  I noticed after upgrade from impish to jammy that my compose key is
  not working correctly.

  Going into gnome-control-center -> Keyboard, I see that 'Alternate
  Characters Key' and 'Compose Key' are both set to Right Alt.

  Setting Alternate Characters Key to None, and moving the Compose Key
  setting around between different options (and then back to Right Alt),
  the behavior of the Right Alt key is still AltGr and not Compose.
  From xev:

  KeyPress event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617),
  state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617),
  state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 16:01:10 2022
  InstallationDate: Installed on 2019-12-23 (847 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+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 1969396] Re: gnome-control-center compose key setting does not set compose key

The output is:

$ gsettings get org.gnome.desktop.input-sources xkb-options
['lv3:ralt_alt', 'grp:alts_toggle', 'altwin:menu', 'compose:ralt']
$

not sure what 'ralt_alt' means as opposed to 'ralt', but this is at
least consistent with the fact that the key is stuck as AltGr instead of
Compose.

If I select 'Right Alt' for 'Alternate Characters Key', the gsettings
value changes to 'lv3:ralt_switch'.  If I select any other option, it
shows 'ralt_alt', and the UI shows 'Alternate Characters Key': 'None'.

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => New

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

Title:
  gnome-control-center compose key setting does not set compose key

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

Bug description:
  I noticed after upgrade from impish to jammy that my compose key is
  not working correctly.

  Going into gnome-control-center -> Keyboard, I see that 'Alternate
  Characters Key' and 'Compose Key' are both set to Right Alt.

  Setting Alternate Characters Key to None, and moving the Compose Key
  setting around between different options (and then back to Right Alt),
  the behavior of the Right Alt key is still AltGr and not Compose.
  From xev:

  KeyPress event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617),
  state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617),
  state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 16:01:10 2022
  InstallationDate: Installed on 2019-12-23 (847 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+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 1969396] Re: gnome-control-center compose key setting does not set compose key

2022-04-18 Thread Gunnar Hjalmarsson

Hi Steve,

Can you please let us know the output of this command:

gsettings get org.gnome.desktop.input-sources xkb-options

when your settings combo gives you the reported xev output for Right
Alt.

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-control-center compose key setting does not set compose key

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

Bug description:
  I noticed after upgrade from impish to jammy that my compose key is
  not working correctly.

  Going into gnome-control-center -> Keyboard, I see that 'Alternate
  Characters Key' and 'Compose Key' are both set to Right Alt.

  Setting Alternate Characters Key to None, and moving the Compose Key
  setting around between different options (and then back to Right Alt),
  the behavior of the Right Alt key is still AltGr and not Compose.
  From xev:

  KeyPress event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617),
  state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617),
  state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 16:01:10 2022
  InstallationDate: Installed on 2019-12-23 (847 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+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 1969396] [NEW] gnome-control-center compose key setting does not set compose key

Public bug reported:

I noticed after upgrade from impish to jammy that my compose key is not
working correctly.

Going into gnome-control-center -> Keyboard, I see that 'Alternate
Characters Key' and 'Compose Key' are both set to Right Alt.

Setting Alternate Characters Key to None, and moving the Compose Key
setting around between different options (and then back to Right Alt),
the behavior of the Right Alt key is still AltGr and not Compose.  From
xev:

KeyPress event, serial 37, synthetic NO, window 0x401,
root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617),
state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes: 
XmbLookupString gives 0 bytes: 
XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x401,
root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617),
state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes: 
XFilterEvent returns: False

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.4-1ubuntu12
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 18 16:01:10 2022
InstallationDate: Installed on 2019-12-23 (847 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago)

** Affects: gnome-control-center (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apport-bug jammy rls-jj-incoming

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => High

** Tags added: rls-jj-incoming

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

Title:
  gnome-control-center compose key setting does not set compose key

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

Bug description:
  I noticed after upgrade from impish to jammy that my compose key is
  not working correctly.

  Going into gnome-control-center -> Keyboard, I see that 'Alternate
  Characters Key' and 'Compose Key' are both set to Right Alt.

  Setting Alternate Characters Key to None, and moving the Compose Key
  setting around between different options (and then back to Right Alt),
  the behavior of the Right Alt key is still AltGr and not Compose.
  From xev:

  KeyPress event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617),
  state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617),
  state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 16:01:10 2022
  InstallationDate: Installed on 2019-12-23 (847 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+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 1948533] Re: any dns defined in network-manager doesnt go in openvpn tunnel (leaks on gnome/mate/xubuntu only in 21.10)

2022-04-18 Thread iMac

We have noticed this as well.  Using VPN we use a special resolver to
handle private IP space, and now, looking into this further it does look
like the network-manager is ignoring the dns= specified in the system-
connections (set via the network manager settings gui).

My settings below, noting X.X.X.x is where my DNS resolver IP address
would normally be and X.com I placed in any domain search field.

A quick check from the command line shows the server is reachable, and
responding properly, just not receiving any requests.

[ipv4]
dns=X.X.X.X;
dns-search=
ignore-auto-dns=true
method=auto

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto

It doesn't appear there are any overrides, and netplan shows
NetworkManager should be controlling everything. nmcli confirms the DNS
is set

$ nmcli conn show "MyVPNConnectionName" | grep dns
connection.mdns:-1 (default)
ipv4.dns:   X.X.X.X
ipv4.dns-search:--
ipv4.dns-options:   --
ipv4.dns-priority:  0
ipv4.ignore-auto-dns:   yes
ipv6.dns:   --
ipv6.dns-search:--
ipv6.dns-options:   --
ipv6.dns-priority:  0
ipv6.ignore-auto-dns:   no


$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

$ netplan  get
network:
  version: 2
  renderer: NetworkManager

$ cat /etc/resolv.conf | grep -v "#"

nameserver 127.0.0.53
options edns0 trust-ad
search X.com

In the nmcli, I did notice that tun0, spawned as a seperate connection
has no DNS defined


$ nmcli conn show "tun0" | grep -i dns
connection.mdns:-1 (default)
ipv4.dns:   --
ipv4.dns-search:--
ipv4.dns-options:   --
ipv4.dns-priority:  100
ipv4.ignore-auto-dns:   no
ipv6.dns:   --
ipv6.dns-search:--
ipv6.dns-options:   --
ipv6.dns-priority:  100
ipv6.ignore-auto-dns:   no


I also see the DNS for the actual wired or wireless connection in use is 
defined, and so must be superseding the OpenVPN defined setting. 

It does seem like a priority issue, whereby the VPN connection should
have priority.  In my case both the VPN and the default WiFi connection
have priority "0"

$ nmcli conn show "MyVPNConnectionName" | grep priority
connection.autoconnect-priority:0
ipv4.dns-priority:  0
ipv6.dns-priority:  0
 
So it seems I would need to change the relative priority to solve this problem. 
 Lower value is higher priority.  

Network Manager should be setting the default connection to 100, and the
VPN to 50, per some Network Manager defaults.

https://access.redhat.com/documentation/en-
us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/configuring-
the-order-of-dns-servers_configuring-and-managing-networking

This document also suggests if they are the same (mine are both 0) the
one with active default route with the lowest metric should win.

In my case, the tun0 would win, but it is not where the DNS is defined.
It would be nice to see what changed in 20.04, but clearly my guess
would be that

a) Default Connection (wifi/wired) used to be dns priority 100 lost to the VPN 
conenction because dns priority was tied, and vpn default gateway metric was 
lower, or 
b) because vpn dns priority was lower

Either way, something does not seem right with current nm defaults for
connections and their dns.priorities

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

Title:
  any dns defined in network-manager doesnt go in openvpn tunnel (leaks
  on gnome/mate/xubuntu only in 21.10)

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  in all linux including ubuntu up to version 21.04, when dns is set to not 
automatic in network manager and one dns is set manually (exemple 1.1.1.1) when 
openvpn is used the dns is going through the vpn tunnel.
  On ubuntu 21.10 (I tested ubuntu, ubuntu mate and xubuntu)I can affirm the 
dns in this case is not going trough the vpn.it is leaking.I have used ubuntu 
for years this is first time this problem occurs (21.10).(and it s not just a 
question of packages because on my arch linux installs I never had such 
problem, so it must be a config problem.

  (when using packages stubby or dnscrypt-proxy (to encrypt dns queries)
  and dns 127.0.0.1 is set in network-manager the dns does goes trough
  the vpn (but stubby service needs to be sometimes reloded, it is less
  reliable that it used to be with previous versions of ubuntu)

  (I cannot speculate where

[Desktop-packages] [Bug 1969387] Re: Wayland stopped working.

2022-04-18 Thread pbuzas

Never mind, installing latest updates fixed my problem.

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

Title:
  Wayland stopped working.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After install 3 finger swipe worked to switch Workspaces, now it no
  longer works. It seems Wayland stopped working and I'm forced to use
  X11. How can I get Wayland back?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 22:57:49 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-11 (7 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1969387/+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 1969387] [NEW] Wayland stopped working.

2022-04-18 Thread pbuzas

Public bug reported:

After install 3 finger swipe worked to switch Workspaces, now it no
longer works. It seems Wayland stopped working and I'm forced to use
X11. How can I get Wayland back?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 18 22:57:49 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-04-11 (7 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Wayland stopped working.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After install 3 finger swipe worked to switch Workspaces, now it no
  longer works. It seems Wayland stopped working and I'm forced to use
  X11. How can I get Wayland back?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 22:57:49 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-11 (7 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1969387/+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 1969386] [NEW] software-properties-gtk Livepatch toggle is grayed out

Public bug reported:

After an upgrade from impish to jammy, update-manager rightly notifies
me that livepatch should be available:

  The software on this computer is up to date.
  Tip: You can use Livepatch to keep your computer more secure between restarts.

However, when I click on the 'Settings & Livepatch' button to launch
software-properties-gtk, after attaching a UA subscription to this
machine (which I hadn't done previously), the Livepatch toggle is grayed
out.

ua status says:

$ ua status
SERVICE   ENTITLED  STATUSDESCRIPTION
cc-ealyes   n/a   Common Criteria EAL2 Provisioning Packages
cis   yes   n/a   Security compliance and audit tools
esm-infra yes   n/a   UA Infra: Extended Security Maintenance (ESM)
fips  yes   n/a   NIST-certified core packages
fips-updates  yes   n/a   NIST-certified core packages with priority 
security updates
livepatch yes   n/a   Canonical Livepatch service

Enable services with: ua enable 

 Account: steve.langa...@canonical.com
Subscription: steve.langa...@canonical.com
$

Running 'sudo ua enable livepatch' reports:

Livepatch is not available for Ubuntu 22.04 (Jammy Jellyfish).

So perhaps this is an issue of update-manager only checking that we're
on an LTS, rather than checking that the livepatch service is available
from the server?  But, that also means connectivity issues could result
in the user never being prompted to enable livepatch.

When is livepatch going to be available for 22.04 LTS?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: software-properties-gtk 0.99.22
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 18 10:08:47 2022
InstallationDate: Installed on 2019-12-23 (846 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  software-properties-gtk Livepatch toggle is grayed out

Status in software-properties package in Ubuntu:
  New

Bug description:
  After an upgrade from impish to jammy, update-manager rightly notifies
  me that livepatch should be available:

The software on this computer is up to date.
Tip: You can use Livepatch to keep your computer more secure between 
restarts.

  However, when I click on the 'Settings & Livepatch' button to launch
  software-properties-gtk, after attaching a UA subscription to this
  machine (which I hadn't done previously), the Livepatch toggle is
  grayed out.

  ua status says:

  $ ua status
  SERVICE   ENTITLED  STATUSDESCRIPTION
  cc-ealyes   n/a   Common Criteria EAL2 Provisioning Packages
  cis   yes   n/a   Security compliance and audit tools
  esm-infra yes   n/a   UA Infra: Extended Security Maintenance 
(ESM)
  fips  yes   n/a   NIST-certified core packages
  fips-updates  yes   n/a   NIST-certified core packages with priority 
security updates
  livepatch yes   n/a   Canonical Livepatch service

  Enable services with: ua enable 

   Account: steve.langa...@canonical.com
  Subscription: steve.langa...@canonical.com
  $

  Running 'sudo ua enable livepatch' reports:

  Livepatch is not available for Ubuntu 22.04 (Jammy Jellyfish).

  So perhaps this is an issue of update-manager only checking that we're
  on an LTS, rather than checking that the livepatch service is
  available from the server?  But, that also means connectivity issues
  could result in the user never being prompted to enable livepatch.

  When is livepatch going to be available for 22.04 LTS?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.22
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 10:08:47 2022
  InstallationDate: Installed on 2019-12-23 (846 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version

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

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

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

Title:
  Unity7 crashes on Jammy with 22.04's gnome-session version

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Unity7 seems to crash on 22.04 when logging in after installing Ubuntu
  (it works fine in the live session). I then tried installing the 21.10
  gnome-session package on 22.04 and Unity7 then worked perfectly fine.
  Also, XDG_CURRENT_DESKTOP is set to GNOME instead of
  "Unity:7;Unity:ubuntu" with the Jammy version, which is really
  unexpected and might be causing these issues.

  seb128 and 3vin1o: Neither I nor Khurshid are sure about what has
  changed between the two packages, and I think this is a critical bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+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 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version

2022-04-18 Thread Khurshid Alam

This is happenning bcz of wrong XDG_CURRENT_DESKTOP (as in Gnome vs
Unity7:Unity:Ubuntu). Ubuntu-settings sets themes deopending on that
value.

@3v1n0 Can you please look into it ?

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

Title:
  Unity7 crashes on Jammy with 22.04's gnome-session version

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Unity7 seems to crash on 22.04 when logging in after installing Ubuntu
  (it works fine in the live session). I then tried installing the 21.10
  gnome-session package on 22.04 and Unity7 then worked perfectly fine.
  Also, XDG_CURRENT_DESKTOP is set to GNOME instead of
  "Unity:7;Unity:ubuntu" with the Jammy version, which is really
  unexpected and might be causing these issues.

  seb128 and 3vin1o: Neither I nor Khurshid are sure about what has
  changed between the two packages, and I think this is a critical bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+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 1968552] Re: Opening web link from evince doesn't work, "env: ‘/snap/bin/firefox’: Permission denied"

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

** Changed in: evince (Ubuntu)
   Status: New => Confirmed

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

Title:
  Opening web link from evince doesn't work, "env: ‘/snap/bin/firefox’:
  Permission denied"

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Jammy Jellyfish 22.04. When opening a PDF document with an external
  link in it, clicking the link doesn't do anything. However, stderr
  says "env: ‘/snap/bin/firefox’: Permission denied"

  How to reproduce:

  Open example PDF file. Click link.
  Expected: firefox opens link.
  Actual result: nothing; stderr says:

  env: ‘/snap/bin/firefox’: Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1968552/+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 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time

2022-04-18 Thread Michael Aaron Murphy

Fixed 2 days ago in updated gdm package.

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

Title:
  System fallback to gdm login screen when hot-plugging a external
  monitor in 1st time

Status in OEM Priority Project:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  [Steps to reproduce]
  1. Install Jammy daily build
  2. dist-upgrade to verify https://bugs.launchpad.net/mutter/+bug/1964037
  3. reboot with no attach monitor
  4. attach monitor after booting

  [Expect result]
  external monitor works directly

  [Actual result]
  system go back to gdm login screen

  [Additional information]
  1. the external port is connecting to dGPU.
  2. happens on wayland only
  3. Only back to login screen in 1st attach, 2nd, 3rd, etc.. works good

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 14 21:22:47 2022
  InstallationDate: Installed on 2022-04-13 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969121/+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 1969244] Re: ubuntu dock's right click menu switches position when the dock is hidden

2022-04-18 Thread Treviño

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

Please, check if this happens also with version 72~ubuntu5

** This bug has been marked a duplicate of bug 1967121
   Contextual menus are glitching when auto-hide is enabled (right click + 
windows selector)

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

Title:
  ubuntu dock's right click menu switches position when the dock is
  hidden

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

Bug description:
  Description: 
  When ubuntu-dock is set to autohide and in hidden state (happens on panel and 
dock mode) 
  When you go to right-click an icon to access its menu, the dock hides again 
and the menu stays open but when you click it the menu updates its position to 
be closer to the dock, leading to miss clicks and a worse user experience. 

  What should happen: 
  The dock should stay visible while you interact with the menu. 

  Replicate it: 
  Set your dock to autohide and then, trigger the autohide (like maximizing a 
window), reach for one of the icons and right-click it.

  
  Hardware info: 
  Asus Vivobook 14 Ryzen 5 3500U & Radeon Graphics. Ubuntu 22.04 Beta 
(15/04/2022)

  
  Package version (output of apt-cache policy): 

  apt-cache policy gnome-shell-extension-ubuntu-dock

  gnome-shell-extension-ubuntu-dock:
Instalados: 72~ubuntu4
Candidato:  72~ubuntu5
Tabla de versión:
   72~ubuntu5 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
   *** 72~ubuntu4 100
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1969244/+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 1969303] Re: "No package to remove" error when attempting to uninstall

2022-04-18 Thread Ken VanDine

Link to upstream bug https://gitlab.gnome.org/GNOME/gnome-
software/-/issues/1720

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

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Unknown
Status in snap-store-desktop:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of ubuntu 22.04, ubuntu-store won't uninstall any
  application

  If you want to uninstall a sottware, tthere is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1969303/+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 1969303] Re: "No package to remove" error when attempting to uninstall

2022-04-18 Thread Ken VanDine

I've also reproduced the same issue with the gnome-software 41.5 deb in
Jammy, output is slightly different:

14:26:55:0535 Gs  uninstall org.gnome.Cheese.desktop
14:26:55:0535 Gs  Chaining cancellation from 0x55d1dbee0fa0 to 0x55d1dc090820
14:26:55:0536 Gs  running remove on plugin=packagekit with dedupe-flags=7 with 
refine-flags=require-setup-action,require-origin with interactive=True with 
timeout=60 on apps 
system/package/manual:ubuntu-jammy-main/org.gnome.Cheese.desktop/*, elapsed 
time since creation 1ms
14:26:55:0538 Gs  Disconnecting cancellable 0x55d1dbee0fa0


** Also affects: gnome-software (Ubuntu)
   Importance: Undecided
   Status: New

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

** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #1720
   https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1720

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Unknown
Status in snap-store-desktop:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of ubuntu 22.04, ubuntu-store won't uninstall any
  application

  If you want to uninstall a sottware, tthere is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1969303/+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 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version

2022-04-18 Thread Rudra Saraswat

** Description changed:

  Unity7 seems to crash on 22.04 when logging in after installing Ubuntu
  (it works fine in the live session). I then tried installing the 21.10
  gnome-session package on 22.04 and Unity7 then worked perfectly fine.
+ Also, XDG_CURRENT_DESKTOP is set to GNOME instead of
+ "Unity:7;Unity:ubuntu" with the Jammy version, which is really
+ unexpected and might be causing these issues.
  
- seb128: Neither I nor Khurshid are sure about what has changed between
- the two packages, and I think this is a critical bug.
+ seb128 and 3vin1o: Neither I nor Khurshid are sure about what has
+ changed between the two packages, and I think this is a critical bug.

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

Title:
  Unity7 crashes on Jammy with 22.04's gnome-session version

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Unity7 seems to crash on 22.04 when logging in after installing Ubuntu
  (it works fine in the live session). I then tried installing the 21.10
  gnome-session package on 22.04 and Unity7 then worked perfectly fine.
  Also, XDG_CURRENT_DESKTOP is set to GNOME instead of
  "Unity:7;Unity:ubuntu" with the Jammy version, which is really
  unexpected and might be causing these issues.

  seb128 and 3vin1o: Neither I nor Khurshid are sure about what has
  changed between the two packages, and I think this is a critical bug.

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


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

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

2022-04-18 Thread Nick Rosbrook

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

** This bug has been marked a duplicate of bug 1962036
   dbus was stopped during today's jammy update, breaking desktop

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

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

Status in gvfs package in Ubuntu:
  Confirmed

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

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

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


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

[Desktop-packages] [Bug 1969351] Re: gnome-shell crashing after suspend or switching TTYs - libgbm.so.1

2022-04-18 Thread Brian Murray

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

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

Title:
  gnome-shell crashing after suspend or switching TTYs - libgbm.so.1

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When using Wayland on Ubuntu 22.04 gnome-shell is crashing anytime you
  leave the Desktop and return to the login screen.

  dmesg -
  [ 6522.928409] gnome-shell[20890]: segfault at 20 ip 0020 sp 
7ffe402baef8 error 14
  [ 6522.928414] Code: Unable to access opcode bytes at RIP 0xfff6.

  gdb -
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f4e2b0070d7 in gbm_surface_release_buffer () from 
/lib/x86_64-linux-gnu/libgbm.so.1

  (gdb) backtrace
  #0  0x7f93da12d0d7 in gbm_surface_release_buffer () at 
/lib/x86_64-linux-gnu/libgbm.so.1
  #1  0x7f93dc4e48ff in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #2  0x7f93dd1f8dfd in g_object_unref () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #3  0x7f93dc4edd40 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #4  0x7f93dd0d5698 in g_hash_table_foreach () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #5  0x7f93dc4f9fcc in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #6  0x7f93dc5141ae in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #7  0x7f93dc4fa03d in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #8  0x7f93dd0f1c24 in g_main_context_dispatch () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x7f93dd1466f8 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #10 0x7f93dd0f1293 in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7f93dc462209 in meta_context_run_main_loop () at 
/lib/x86_64-linux-gnu/libmutter-10.so.0
  #12 0x56280e1b6ed2 in  ()
  #13 0x7f93dc193d90 in __libc_start_call_main 
(main=main@entry=0x56280e1b6a30, argc=argc@entry=1, 
argv=argv@entry=0x7ffc82080608) at ../sysdeps/nptl/libc_start_call_main.h:58
  #14 0x7f93dc193e40 in __libc_start_main_impl (main=0x56280e1b6a30, 
argc=1, argv=0x7ffc82080608, init=, fini=, 
rtld_fini=, stack_end=0x7ffc820805f8) at ../csu/libc-start.c:392
  #15 0x56280e1b7155 in  ()

  Also Wayland shows my monitors backwards, left on the right, right on
  the left. Works fine in Xorg.

  If i try to rearrange the physical displays of my 2 monitors, I get kicked 
out when pressing apply. 
  dmesg -
  [ 7618.079350] traps: gnome-shell[25726] general protection fault 
ip:7f34373be0d7 sp:7ffcfb2a9538 error:0 in libgbm.so.1.0.0[7f34373b7000+8000]

  System:
Host: desktop Kernel: 5.17.0-1003-oem x86_64 bits: 64 compiler: gcc
  v: 11.2.0 Desktop: GNOME 42.0 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3
  Distro: Ubuntu 22.04 (Jammy Jellyfish)
  CPU:
Info: quad core model: Intel Core i5-7600K bits: 64 type: MCP
  arch: Kaby Lake rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 4401 high: 4404 min/max: 800/4400 cores: 1: 4401
  2: 4400 3: 4400 4: 4404 bogomips: 30399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel
  ports: active: HDMI-A-3 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:5912
Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
  vendor: Sapphire driver: amdgpu v: kernel pcie: speed: 2.5 GT/s lanes: 16
  ports: active: HDMI-A-5 empty: DP-3, DP-4, DVI-D-1, HDMI-A-4
  bus-ID: 01:00.0 chip-ID: 1002:67df
Device-3: Logitech HD Webcam C615 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-3:3 chip-ID: 046d:082c
Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: radeon
  gpu: amdgpu,i915 display-ID: 0
Monitor-1: HDMI-A-3 model: Asus VG23A res: 1920x1080 dpi: 91
  diag: 618mm (24.3")
Monitor-2: HDMI-A-5 model: Samsung res: 1920x1080 dpi: 44
  diag: 1271mm (50.1")
OpenGL: renderer: AMD Radeon RX 580 Series (polaris10 LLVM 14.0.0 DRM
  3.44 5.17.0-1003-oem)
  v: 4.6 Mesa 22.1.0-devel direct render: Yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969351/+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 1969351] [NEW] gnome-shell crashing after suspend or switching TTYs - libgbm.so.1

You have been subscribed to a public bug:

When using Wayland on Ubuntu 22.04 gnome-shell is crashing anytime you
leave the Desktop and return to the login screen.

dmesg -
[ 6522.928409] gnome-shell[20890]: segfault at 20 ip 0020 sp 
7ffe402baef8 error 14
[ 6522.928414] Code: Unable to access opcode bytes at RIP 0xfff6.

gdb -
Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x7f4e2b0070d7 in gbm_surface_release_buffer () from 
/lib/x86_64-linux-gnu/libgbm.so.1

(gdb) backtrace
#0  0x7f93da12d0d7 in gbm_surface_release_buffer () at 
/lib/x86_64-linux-gnu/libgbm.so.1
#1  0x7f93dc4e48ff in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#2  0x7f93dd1f8dfd in g_object_unref () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3  0x7f93dc4edd40 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#4  0x7f93dd0d5698 in g_hash_table_foreach () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f93dc4f9fcc in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#6  0x7f93dc5141ae in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#7  0x7f93dc4fa03d in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#8  0x7f93dd0f1c24 in g_main_context_dispatch () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f93dd1466f8 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f93dd0f1293 in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f93dc462209 in meta_context_run_main_loop () at 
/lib/x86_64-linux-gnu/libmutter-10.so.0
#12 0x56280e1b6ed2 in  ()
#13 0x7f93dc193d90 in __libc_start_call_main 
(main=main@entry=0x56280e1b6a30, argc=argc@entry=1, 
argv=argv@entry=0x7ffc82080608) at ../sysdeps/nptl/libc_start_call_main.h:58
#14 0x7f93dc193e40 in __libc_start_main_impl (main=0x56280e1b6a30, argc=1, 
argv=0x7ffc82080608, init=, fini=, 
rtld_fini=, stack_end=0x7ffc820805f8) at ../csu/libc-start.c:392
#15 0x56280e1b7155 in  ()

Also Wayland shows my monitors backwards, left on the right, right on
the left. Works fine in Xorg.

If i try to rearrange the physical displays of my 2 monitors, I get kicked out 
when pressing apply. 
dmesg -
[ 7618.079350] traps: gnome-shell[25726] general protection fault 
ip:7f34373be0d7 sp:7ffcfb2a9538 error:0 in libgbm.so.1.0.0[7f34373b7000+8000]

System:
  Host: desktop Kernel: 5.17.0-1003-oem x86_64 bits: 64 compiler: gcc
v: 11.2.0 Desktop: GNOME 42.0 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3
Distro: Ubuntu 22.04 (Jammy Jellyfish)
CPU:
  Info: quad core model: Intel Core i5-7600K bits: 64 type: MCP
arch: Kaby Lake rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 4401 high: 4404 min/max: 800/4400 cores: 1: 4401
2: 4400 3: 4400 4: 4404 bogomips: 30399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel
ports: active: HDMI-A-3 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:5912
  Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: Sapphire driver: amdgpu v: kernel pcie: speed: 2.5 GT/s lanes: 16
ports: active: HDMI-A-5 empty: DP-3, DP-4, DVI-D-1, HDMI-A-4
bus-ID: 01:00.0 chip-ID: 1002:67df
  Device-3: Logitech HD Webcam C615 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-3:3 chip-ID: 046d:082c
  Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
compositor: gnome-shell driver: X: loaded: modesetting unloaded: radeon
gpu: amdgpu,i915 display-ID: 0
  Monitor-1: HDMI-A-3 model: Asus VG23A res: 1920x1080 dpi: 91
diag: 618mm (24.3")
  Monitor-2: HDMI-A-5 model: Samsung res: 1920x1080 dpi: 44
diag: 1271mm (50.1")
  OpenGL: renderer: AMD Radeon RX 580 Series (polaris10 LLVM 14.0.0 DRM
3.44 5.17.0-1003-oem)
v: 4.6 Mesa 22.1.0-devel direct render: Yes

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


** Tags: bot-comment
-- 
gnome-shell crashing after suspend or switching TTYs - libgbm.so.1
https://bugs.launchpad.net/bugs/1969351
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

2022-04-18 Thread Bernard Stafford

Apparmor audit message.

** Attachment added: "Apparmor audit message"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+attachment/5581262/+files/Apparmor%20audit%20message

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

Title:
  apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
  `/usr/sbin/cups-browsed` to change its nice value.

  $ sudo dmesg | grep apparmor
  [541870.509461] audit: type=1400 audit(1600898428.089:60): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=62030 comm="cups-browsed" capability=23  capname="sys_nice"
  [628298.779668] audit: type=1400 audit(1600984854.115:61): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=66850 comm="cups-browsed" capability=23  capname="sys_nice"
  [714667.424963] audit: type=1400 audit(1601071220.527:62): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=76828 comm="cups-browsed" capability=23  capname="sys_nice"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+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 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

2022-04-18 Thread Bernard Stafford

I have 33 denied messages that increase in number every time I reboot.

** Attachment added: "Apparmor rsys log d"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+attachment/5581261/+files/Apparmor%20rsys%20log%20d

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

Title:
  apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
  `/usr/sbin/cups-browsed` to change its nice value.

  $ sudo dmesg | grep apparmor
  [541870.509461] audit: type=1400 audit(1600898428.089:60): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=62030 comm="cups-browsed" capability=23  capname="sys_nice"
  [628298.779668] audit: type=1400 audit(1600984854.115:61): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=66850 comm="cups-browsed" capability=23  capname="sys_nice"
  [714667.424963] audit: type=1400 audit(1601071220.527:62): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=76828 comm="cups-browsed" capability=23  capname="sys_nice"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+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 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

2022-04-18 Thread Bernard Stafford

** Attachment added: "Apparmor kernal log"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+attachment/5581260/+files/Apparmor%20kernal%20log

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

Title:
  apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
  `/usr/sbin/cups-browsed` to change its nice value.

  $ sudo dmesg | grep apparmor
  [541870.509461] audit: type=1400 audit(1600898428.089:60): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=62030 comm="cups-browsed" capability=23  capname="sys_nice"
  [628298.779668] audit: type=1400 audit(1600984854.115:61): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=66850 comm="cups-browsed" capability=23  capname="sys_nice"
  [714667.424963] audit: type=1400 audit(1601071220.527:62): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=76828 comm="cups-browsed" capability=23  capname="sys_nice"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+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 1969357] [NEW] Unity7 crashes on Jammy with 22.04's gnome-session version

2022-04-18 Thread Rudra Saraswat

Public bug reported:

Unity7 seems to crash on 22.04 when logging in after installing Ubuntu
(it works fine in the live session). I then tried installing the 21.10
gnome-session package on 22.04 and Unity7 then worked perfectly fine.

seb128: Neither I nor Khurshid are sure about what has changed between
the two packages, and I think this is a critical bug.

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


** Tags: jammy

** Tags added: jammy

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

Title:
  Unity7 crashes on Jammy with 22.04's gnome-session version

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Unity7 seems to crash on 22.04 when logging in after installing Ubuntu
  (it works fine in the live session). I then tried installing the 21.10
  gnome-session package on 22.04 and Unity7 then worked perfectly fine.

  seb128: Neither I nor Khurshid are sure about what has changed between
  the two packages, and I think this is a critical bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+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 1969314] Re: xdg-user-dirs-gtk-update not display panel

** Package changed: ubuntu => xdg-user-dirs-gtk (Ubuntu)

** Tags added: jammy

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

Title:
  xdg-user-dirs-gtk-update not display panel

Status in xdg-user-dirs-gtk package in Ubuntu:
  New

Bug description:
  Hi,

  I installed jammy-desktop-amd64.iso 2022-04-16 version by selecting Japanese.
  ubuntu-20.04, after installing the English version, I added a Japanese 
environment,
  but it has easier.

  However, the setting panel does not appear even if I execute the command
  to change the Japanese directory name of the HOME directory.

  LANG=C xdg-user-dirs-gtk-update

  As for the execution result, both Japanese and English direcotres
  remained.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs-gtk/+bug/1969314/+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 1969314] [NEW] xdg-user-dirs-gtk-update not display panel

You have been subscribed to a public bug:

Hi,

I installed jammy-desktop-amd64.iso 2022-04-16 version by selecting Japanese.
ubuntu-20.04, after installing the English version, I added a Japanese 
environment,
but it has easier.

However, the setting panel does not appear even if I execute the command
to change the Japanese directory name of the HOME directory.

LANG=C xdg-user-dirs-gtk-update

As for the execution result, both Japanese and English direcotres
remained.

** Affects: xdg-user-dirs-gtk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
xdg-user-dirs-gtk-update not display panel
https://bugs.launchpad.net/bugs/1969314
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xdg-user-dirs-gtk in Ubuntu.

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

[Desktop-packages] [Bug 1969149] Re: Unable to remove DEB packages in Ubuntu Software

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

** This bug is no longer a duplicate of bug 1969335
Unable to remove DEB packages in Ubuntu Software
** This bug has been marked a duplicate of bug 1969303
   no package to remove

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

Title:
  Unable to remove DEB packages in Ubuntu Software

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:

  When trying to remove DEB packages it shows "Cannot remove:
  no packages to remove"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1969149/+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 1966178] Re: Screen-privacy couldn't work

2022-04-18 Thread Bin Li

Tested on 5.17.0-1003-oem kernel, this privacy item could be showed.

But it couldn't sync with 'Fn + D', if it is disabled, click the 'Fn +
D', it changed enabled, and changed back to disabled quickly. Looks like
it's a kind of bug.

Tested my own build image based on 5.15.0-27-generic with upstream
patches, it works perfectly. So the new issue might be related kernel
side.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/comments/3

Tested kernel are here.
https://people.canonical.com/~binli/5.15.0-27.28binli1/

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

Title:
  Screen-privacy couldn't work

Status in OEM Priority Project:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  On ThinkPad X13 it supports 'Privacy Guard', but on jammy the g-c-c
  couldn't control it.

  From the GUI, I click 'Restrict Viewing Angle' on and off, there are
  no change at screen.

  From Fn+D, it could let screen change, and the GUI could follow the
  changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966178/+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 1966178] Re: Screen-privacy couldn't work

2022-04-18 Thread Bin Li

** Changed in: oem-priority
   Status: New => Fix Released

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

Title:
  Screen-privacy couldn't work

Status in OEM Priority Project:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  On ThinkPad X13 it supports 'Privacy Guard', but on jammy the g-c-c
  couldn't control it.

  From the GUI, I click 'Restrict Viewing Angle' on and off, there are
  no change at screen.

  From Fn+D, it could let screen change, and the GUI could follow the
  changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966178/+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 1969265] Re: Ubuntu 22.04 after Update to latest gdm3 jammy 42.0-1ubuntu4 arm64, I does not logon to Wayland Session anymore

2022-04-18 Thread JF Lim

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

After today's update of gdm3 to gdm3/jammy,now 42.0-1ubuntu6 arm64, on
gdm3 greeter screen now have optio of ubuntu, ubuntu on Xorg, gnome and
gnome on xorg.  Select "ubuntu" results in correct Wayland session.

Thank for resolving the bug.

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

Title:
  Ubuntu 22.04 after Update to latest gdm3 jammy 42.0-1ubuntu4 arm64, I
  does not logon to Wayland Session anymore

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After the latest Ubuntu 22.04 (Jammy) updates (Suspected gdm3
  42.0-1ubuntu4 arm64), it does not logon to Wayland session anymore.

  On gmd3 logon greeter screen only "ubuntu" and "gnome" desktop are
  available.  Before update it had "ubuntu", "ubuntu on Xorg", "gnome"
  and "gnome on xorg" option.

  Selecting "ubuntu" or "gnome", the logon session is in X11 and NOT
  Wayland.

  Previously before update, logon with "ubuntu" or "gnome" result in
  Wayland session.

  Additional Info:
  $ journalctl -b

  Apr 16 12:00:27 armbian systemd[3679]: Started Application launched by 
gnome-session-binary.
  Apr 16 12:00:27 armbian systemd[3679]: Started GNOME Session Manager 
(session: ubuntu).
  Apr 16 12:00:27 armbian systemd[3679]: Reached target GNOME Session Manager 
is ready.
  Apr 16 12:00:27 armbian systemd[3679]: Starting GNOME Shell on Wayland...
  Apr 16 12:00:27 armbian systemd[3679]: Starting GNOME Shell on X11...
  Apr 16 12:00:27 armbian systemd[3679]: org.gnome.Shell@wayland.service: 
Skipped due to 'exec-condition'.
  Apr 16 12:00:27 armbian systemd[3679]: Condition check resulted in GNOME 
Shell on Wayland being skipped.
  Apr 16 12:00:27 armbian systemd[3679]: Started Application launched by 
gnome-session-binary.
  Apr 16 12:00:27 armbian systemd[3679]: Started Application launched by 
gnome-session-binary.
  Apr 16 12:00:27 armbian gnome-shell[3902]: Running GNOME Shell (using mutter 
42.0) as a X11 window and compositing manager

  Wayland Session Stop Working after these updates:

  jfl@armbian:~$ apt list --upgradable
  Listing... Done
  gdm3/jammy 42.0-1ubuntu4 arm64 [upgradable from: 42.0-1ubuntu2]
  gir1.2-gdm-1.0/jammy 42.0-1ubuntu4 arm64 [upgradable from: 42.0-1ubuntu2]
  libgdm1/jammy 42.0-1ubuntu4 arm64 [upgradable from: 42.0-1ubuntu2]
  linux-dtb-edge-meson64/jammy 22.05.0-trunk.0038 arm64 [upgradable from: 
22.05.0-trunk]
  vivaldi-stable/stable 5.2.2623.39-1 arm64 [upgradable from: 5.2.2623.36-1]
  jfl@armbian:~$ sudo apt update
  Hit:1 https://ryanfortner.github.io/box64-debs/debian ./ InRelease
 
  Hit:2 http://ports.ubuntu.com jammy InRelease 
 
  Hit:4 http://ports.ubuntu.com jammy-security InRelease
 
  Hit:5 http://deb.volian.org/volian scar InRelease   
  Hit:3 http://sg-mirror.bret.dk/armbian/apt jammy InRelease
 
  Hit:6 http://ports.ubuntu.com jammy-updates InRelease   
  Hit:7 http://ports.ubuntu.com jammy-backports InRelease
  Ign:8 https://repo.vivaldi.com/stable/deb stable InRelease
  Hit:9 https://repo.vivaldi.com/stable/deb stable Release
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  5 packages can be upgraded. Run 'apt list --upgradable' to see them.
  jfl@armbian:~$ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
libjavascriptcoregtk-4.1-0 libsoup-3.0-0 libsoup-3.0-common
libwebkit2gtk-4.1-0
  Use 'sudo apt autoremove' to remove them.
  The following packages have been kept back:
linux-dtb-edge-meson64
  The following packages will be upgraded:
gdm3 gir1.2-gdm-1.0 libgdm1 vivaldi-stable
  4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
  Need to get 83.4 MB of archives.
  After this operation, 3,072 B of additional disk space will be used.
  Do you want to continue? [Y/n] Y

  
  Second Additional Info:
  Added a Second User.
  Logon to Second User: Ubuntu Session
  Still Logon as X11 Session.

  Reboot.

  On Start up Logon to Second User: Ubuntu Session
  System logon as X11 Session

  Switch User and Logon to First User: Ubuntu Session
  Now it logon to Wayland Session for First User.

  Strange

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  Uname: Linux 5.15.34-flippy-71+o aarch64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 16 15:40:31 2022
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell

[Desktop-packages] [Bug 1962021] Re: Make the deb package install the firefox snap

2022-04-18 Thread Alkis Georgopoulos

The commands to install firefox.deb from the PPA are:

sudo -i
add-apt-repository --yes ppa:mozillateam/ppa
echo 'Package: *
Pin: release o=LP-PPA-mozillateam
Pin-Priority: 1001' >/etc/apt/preferences.d/60local
apt install firefox firefox-locale-en

If you need more locales like `firefox-locale-el` add them to the last
command.

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

Title:
  Make the deb package install the firefox snap

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Canonical and Mozilla are working together to make the firefox snap
  the only supported package in Ubuntu, thus deprecating the deb package
  in the archive.

  This bug tracks the transformation of the firefox package in the
  archive into a transitional package that installs the snap, much like
  was done for chromium-browser in Ubuntu 19.10.

  There are a number of known problems and regressions with the snap
  compared to the deb (see
  https://bugzilla.mozilla.org/show_bug.cgi?id=snap and
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bugs?field.tag=snap),
  those are actively being worked on and will be addressed in due time,
  please refrain from using this bug to point them out. Instead, file
  separate bugs in the upstream bug tracker
  (https://bugzilla.mozilla.org/enter_bug.cgi), making sure to specify
  this is about the snap package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962021/+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 1962800] Re: It goes into black screen for more than 20 seconds when increase default resolution to max available 1360 * 768 for ubuntu 22.04 daily build desktop in ESXi

2022-04-18 Thread vmware-gos-Yuhua

Any comments for this issue ?

** Package changed: ubuntu => screen-resolution-extra (Ubuntu)

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

Title:
It goes into black screen for more than 20 seconds when increase
default resolution to max available 1360 * 768 for ubuntu 22.04 daily
build desktop in ESXi

Status in screen-resolution-extra package in Ubuntu:
Confirmed

Bug description:
Summary:
-
It goes into black screen for about 20 seconds when increase Guest OS default
resolution to max available resolution 1360 * 768 for ubuntu 22.04 daily build
desktop in ESXi. After about 20 seconds later, it restore to previous screen
resolution.

Reproduce:
-
1. create VM with default settings(video memory 4MB)and install guest OS with
ubuntu 22.04 daily build 27-Feb-2022 images in ESXi

2. we login system after finish installation and rebooting VM

3. Select Virtual Machine -> Settings -> Display, select the max available
resolution 1360 * 768
and click "Apply button".

The screen get black for about 20 seconds and then restore to
previous screen resolution.

Expected Results:
-
For step 3, we expect the max available resolution 1360 * 768 screen
resolution works well.
If the default video memory 4MB is not enough to support 1360 * 768 and it
needs to restore previous resolution, it seems long to stay black for 20
seconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1962800/+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 1962800] [NEW] It goes into black screen for more than 20 seconds when increase default resolution to max available 1360 * 768 for ubuntu 22.04 daily build desktop in ESXi

You have been subscribed to a public bug:

Summary:
-
It goes into black screen for about 20 seconds when increase Guest OS default 
resolution to max available resolution 1360 * 768 for ubuntu 22.04 daily build 
desktop in ESXi.  After about 20 seconds later, it restore to previous screen 
resolution.

Reproduce:
-
1. create VM with default settings(video memory 4MB)and install guest OS with 
ubuntu 22.04 daily build 27-Feb-2022 images in ESXi

2. we login system after finish installation and rebooting VM

3. Select Virtual Machine -> Settings -> Display, select the max available 
resolution 1360 * 768
   and click "Apply button".

   The screen get black for about 20 seconds and then restore to
previous screen resolution.


Expected Results:
-
For step 3, we expect the max available resolution 1360 * 768 screen resolution 
works well.  
If the default video memory 4MB is not enough to support 1360 * 768 and it 
needs to restore previous resolution, it seems long to stay black for 20 
seconds.

** Affects: screen-resolution-extra (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: bot-comment
-- 
It goes into black screen for more than 20 seconds when increase default 
resolution to max available 1360 * 768  for ubuntu 22.04 daily build  desktop 
in ESXi
https://bugs.launchpad.net/bugs/1962800
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to screen-resolution-extra in Ubuntu.

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

[Desktop-packages] [Bug 1969335] Re: Unable to remove DEB packages in Ubuntu Software

** Tags added: jammy

** Package changed: gnome-software (Ubuntu) => snap-store-desktop

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

Title:
   Unable to remove DEB packages in Ubuntu Software

Status in snap-store-desktop:
  New

Bug description:
  Using Ubuntu 22.04 beta and when trying to remove any DEB package (using 
Ubuntu Software) it shows (a Telegram example) "Cannot remove "Telegram 
Desktop":
  no packages to remove.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store-desktop/+bug/1969335/+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 1969151] Re: Files does not open DEB packages installer

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

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

Title:
  Files does not open DEB packages installer

Status in nautilus package in Ubuntu:
  New

Bug description:
  When trying to install DEB packages the "Compressed File Manager" is opened 
instead of the "Program Installation"
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-04-16 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Package: nautilus 1:42.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-04-16 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Package: nautilus 1:42.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-04-16 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Package: nautilus 1:42.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-04-16 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Package: nautilus 1:42.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-04-16 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Package: nautilus 1:42.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6
  --- 
  ProblemType: Bug

[Desktop-packages] [Bug 1969149] Re: Unable to remove DEB packages in Ubuntu Software