date:20220422

** Changed in: xorg-server (Debian)
   Status: New => Fix Released

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

Title:
  BUG: triggered 'if (axnum >= dev->valuator->numAxes)'

Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg-server package in Debian:
  Fix Released

Bug description:
  I have a Surface Pro 3, and I'm using evdev to use it. While looking
  to tackle another issue (my trackpad suddenly stopped working), I
  noticed this in the xorg log:

  [  3479.176] (II) XINPUT: Adding extended input device "Microsoft Surface 
Type Cover" (type: KEYBOARD, id 8)
  [  3479.176] (**) Option "xkb_rules" "evdev"
  [  3479.176] (**) Option "xkb_model" "pc105"
  [  3479.176] (**) Option "xkb_layout" "us"
  [  3479.176] (WW) evdev: Microsoft Surface Type Cover: touchpads, tablets and 
touchscreens ignore relative axes.
  [  3479.176] (EE) BUG: triggered 'if (axnum >= dev->valuator->numAxes)'
  [  3479.176] (EE) BUG: ../../Xi/exevents.c:2086 in InitValuatorAxisStruct()
  [  3479.176] (EE) 
  [  3479.176] (EE) Backtrace:
  [  3479.176] (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7f8c9d098f76]
  [  3479.176] (EE) 1: /usr/bin/X (InitValuatorAxisStruct+0x67) [0x7f8c9d0280c7]
  [  3479.176] (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so 
(0x7f8c9476d000+0x51c2) [0x7f8c947721c2]
  [  3479.176] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so 
(0x7f8c9476d000+0x5406) [0x7f8c94772406]
  [  3479.176] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so 
(0x7f8c9476d000+0x7088) [0x7f8c94774088]
  [  3479.177] (EE) 5: /usr/bin/X (ActivateDevice+0x4a) [0x7f8c9cf2e50a]
  [  3479.177] (EE) 6: /usr/bin/X (0x7f8c9cee2000+0xa4d91) [0x7f8c9cf86d91]
  [  3479.177] (EE) 7: /usr/bin/X (0x7f8c9cee2000+0xbb8e9) [0x7f8c9cf9d8e9]
  [  3479.177] (EE) 8: /usr/bin/X (0x7f8c9cee2000+0xbbc28) [0x7f8c9cf9dc28]
  [  3479.177] (EE) 9: /usr/bin/X (WakeupHandler+0x6b) [0x7f8c9cf3e24b]
  [  3479.177] (EE) 10: /usr/bin/X (WaitForSomething+0x1c7) [0x7f8c9d096327]
  [  3479.177] (EE) 11: /usr/bin/X (0x7f8c9cee2000+0x57311) [0x7f8c9cf39311]
  [  3479.177] (EE) 12: /usr/bin/X (0x7f8c9cee2000+0x5b706) [0x7f8c9cf3d706]
  [  3479.177] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f8c9ac37ec5]
  [  3479.177] (EE) 14: /usr/bin/X (0x7f8c9cee2000+0x45a8e) [0x7f8c9cf27a8e]
  [  3479.177] (EE) 
  [  3479.177] (EE) BUG: triggered 'if (axnum >= dev->valuator->numAxes)'
  [  3479.177] (EE) BUG: ../../Xi/exevents.c:2119 in SetScrollValuator()
  [  3479.177] (EE) 
  [  3479.177] (EE) Backtrace:
  [  3479.177] (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7f8c9d098f76]
  [  3479.177] (EE) 1: /usr/bin/X (SetScrollValuator+0x76) [0x7f8c9d027ea6]
  [  3479.177] (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so 
(0x7f8c9476d000+0x51ee) [0x7f8c947721ee]
  [  3479.177] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so 
(0x7f8c9476d000+0x5406) [0x7f8c94772406]
  [  3479.177] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so 
(0x7f8c9476d000+0x7088) [0x7f8c94774088]
  [  3479.177] (EE) 5: /usr/bin/X (ActivateDevice+0x4a) [0x7f8c9cf2e50a]
  [  3479.177] (EE) 6: /usr/bin/X (0x7f8c9cee2000+0xa4d91) [0x7f8c9cf86d91]
  [  3479.177] (EE) 7: /usr/bin/X (0x7f8c9cee2000+0xbb8e9) [0x7f8c9cf9d8e9]
  [  3479.177] (EE) 8: /usr/bin/X (0x7f8c9cee2000+0xbbc28) [0x7f8c9cf9dc28]
  [  3479.177] (EE) 9: /usr/bin/X (WakeupHandler+0x6b) [0x7f8c9cf3e24b]
  [  3479.177] (EE) 10: /usr/bin/X (WaitForSomething+0x1c7) [0x7f8c9d096327]
  [  3479.177] (EE) 11: /usr/bin/X (0x7f8c9cee2000+0x57311) [0x7f8c9cf39311]
  [  3479.177] (EE) 12: /usr/bin/X (0x7f8c9cee2000+0x5b706) [0x7f8c9cf3d706]
  [  3479.177] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f8c9ac37ec5]
  [  3479.177] (EE) 14: /usr/bin/X (0x7f8c9cee2000+0x45a8e) [0x7f8c9cf27a8e]
  [  3479.177] (EE) 
  [  3479.178] (II) evdev: Microsoft Surface Type Cover: initialized for 
absolute axes.
  [  3479.178] (**) Microsoft Surface Type Cover: (accel) keeping acceleration 
scheme 1
  [  3479.178] (**) Microsoft Surface Type Cover: (accel) acceleration profile 0
  [  3479.178] (**) Microsoft Surface Type Cover: (accel) acceleration factor: 
2.000
  [  3479.178] (**) Microsoft Surface Type Cover: (accel) acceleration 
threshold: 4

  I have the similar lines in the beginning of the log also (with
  timestamp around 5), and I don't understand why all this is repeated
  here also.

  I suffer also from:
  https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/954426

  Trying to switch to console mode then come back doesn't trigger these
  lines.

  This report is only about this BUG behing logged into Xorg file. But
  it might be of interest of noting that I'm chasing an sudden issue
  with my typecover : the trackpad stopped working. For now, this is
  probably unrelated.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-04-22 Thread jeremyszu

Copied the finding from
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969142 since this
bug is created long time.

Pieces of log
```
 四 14 22:55:10 kernel: NVRM: GPU at PCI::01:00: 
GPU-581d669f-ec00-4588-ca5f-15ab24136974
 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics 
Exception: Shader Program Header 18 Error
 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics 
Exception: ESR 0x405840=0x8204
 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics 
Exception: ESR 0x405848=0x8000
 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=1270, Graphics 
Exception: ChID 0010, Class c597, Offset , Data 
```

For nvidia-driver, u-d-c, we need to follow
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html
to setup the parameters after some checks.

I appended the parameters:
options nvidia NVreg_TemporaryFilePath=/run
options nvidia NVreg_PreserveVideoMemoryAllocations=1

and then the problem solved.

Tried 510.60 as well and the problem is persistent.

** Tags added: jiayi wayland

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash

[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-04-22 Thread Yuan-Chen Cheng

** Tags added: oem-priority

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1

[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-04-22 Thread jeremyszu

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

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

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz:

[Desktop-packages] [Bug 1970011] [NEW] pulseaudio running but can't hear any sound

2022-04-22 Thread Samuel Siaw

Public bug reported:

...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.13
ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sat Apr 23 00:50:09 2022
InstallationDate: Installed on 2022-04-06 (16 days ago)
InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2021
dmi.bios.release: 4.14
dmi.bios.vendor: coreboot
dmi.bios.version: MrChromebox-4.14
dmi.board.name: Banon
dmi.board.vendor: GOOGLE
dmi.board.version: 1.0
dmi.chassis.type: 9
dmi.chassis.vendor: GOOGLE
dmi.ec.firmware.release: 0.0
dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku:
dmi.product.family: Intel_Strago
dmi.product.name: Banon
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2022-04-23T00:30:09.974603

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


** Tags: amd64 apport-bug focal

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

Title:
  pulseaudio running but can't hear any sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 23 00:50:09 2022
  InstallationDate: Installed on 2022-04-06 (16 days ago)
  InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2021
  dmi.bios.release: 4.14
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox-4.14
  dmi.board.name: Banon
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku:
  dmi.product.family: Intel_Strago
  dmi.product.name: Banon
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2022-04-23T00:30:09.974603

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1970011/+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 132448] Re: search-tool: deleted files are counted in filetype count

[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

** Changed in: tracker (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  search-tool: deleted files are counted in filetype count

Status in tracker package in Ubuntu:
  Expired

Bug description:
  Binary package hint: tracker

  Steps to reproduce:
  - create a file
  - search for this file
  - delete this file
  - search again for this file and notice that the file is not shown in the 
result window, but it is counted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/132448/+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 130937] Re: tracker-search-tool gets no response

[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

** Changed in: tracker (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  tracker-search-tool gets no response

Status in tracker package in Ubuntu:
  Expired

Bug description:
  Binary package hint: tracker

  Trackerd is still indexing my drive. I started tracker-search-tool and
  performed a search. It provided a number of results. Clicking on the
  emails and text categories worked, but when I clicked on "All Files" I
  got the following in the console:

  META_TILE_ERROR : Did not receive a reply. Possible causes include: the 
remote application did not send a reply, the message bus security policy 
blocked the reply, the reply timeout expired, or the network connection was 
broken.Did not receive a reply. Possible causes include: the remote application 
did not send a reply, the message bus security policy blocked the reply, the 
reply timeout expired, or the network connection was broken.
  META_TILE_ERROR : Did not receive a reply. Possible causes include: the 
remote application did not send a reply, the message bus security policy 
blocked the reply, the reply timeout expired, or the network connection was 
broken.Did not receive a reply. Possible causes include: the remote application 
did not send a reply, the message bus security policy blocked the reply, the 
reply timeout expired, or the network connection was broken.

  ** (tracker-search-tool:26050): CRITICAL **: set_snippet: assertion
  `error == NULL' failed

  and a dialogue box saying

  Did not receive a reply. Possible causes include: the remote
  application did not send a reply, the message bus security policy
  blocked the reply, the reply timeout expired, or the network
  connection was broken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/130937/+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 346575] Re: tracker-extract crashed with SIGSEGV in g_utf8_validate()

[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

** Changed in: tracker (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  tracker-extract crashed with SIGSEGV in g_utf8_validate()

Status in tracker package in Ubuntu:
  Expired

Bug description:
  Binary package hint: tracker

  same bug title reported fixed, but this is jaunty post-alpha6

  so we can't handle utf8, or apparently 90% of my documents or media
  without crashing. google desktop is sadly much more reliable.

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/lib/tracker/tracker-extract
  Package: tracker 0.6.91-1ubuntu1
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_GB.UTF-8
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   g_utf8_validate () from /usr/lib/libglib-2.0.so.0
   tracker_escape_metadata ()
   ?? ()
   ?? ()
   tracker_extract_get_metadata ()
  Title: tracker-extract crashed with SIGSEGV in g_utf8_validate()
  Uname: Linux 2.6.28-11-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/346575/+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 163544] Re: tracker search tool shows no results

[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

** Changed in: tracker (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  tracker search tool shows no results

Status in tracker package in Ubuntu:
  Expired

Bug description:
  See the attached screenshots. Same with any query string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/163544/+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 336422] Re: [jaunty] tracker-extract prevents unmounting of USB storage devices, crashed with signal 7 in tracker_extract_get_metadata() when media forcibly removed

[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

** Changed in: tracker (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [jaunty] tracker-extract prevents unmounting of USB storage devices,
  crashed with signal 7 in tracker_extract_get_metadata() when media
  forcibly removed

Status in tracker package in Ubuntu:
  Expired

Bug description:
  Binary package hint: tracker

  tracker-extract is being run against the files on removable storage,
  preventing timely removal of storage devices. When the devices are
  removed without unmounting, tracker-extract crashes.

  ProblemType: Crash
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/lib/tracker/tracker-extract
  NonfreeKernelModules: nvidia
  Package: tracker 0.6.90-1ubuntu2
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_AU.UTF-8
  Signal: 7
  SourcePackage: tracker
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   tracker_extract_get_metadata ()
   ?? () from /usr/lib/libdbus-glib-1.so.2
  Title: tracker-extract crashed with signal 7 in tracker_extract_get_metadata()
  Uname: Linux 2.6.28-8-generic x86_64
  UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev 
sambashare scanner vboxusers video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/336422/+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 1960817] Re: Network Manager sets powersave on by default, thus making many WiFi connections unreliable

[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Network Manager sets powersave on by default, thus making many WiFi
  connections unreliable

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  As the headline says. On the support fora that I frequent, many people
  report unstable and unreliable WiFi connections because of this. In
  those cases, when power management for the WiFi chipset is turned off,
  the connection immediately improves a lot.

  Therefore the default for WiFi power management should be "off", non
  "on".

  Workaround for those who don't want to wait for the fix:
  sudo sed -i 's/3/2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

  Reboot.

  When there's no such .conf file yet:
  sudo touch /etc/NetworkManager/conf.d/default-wifi-powersave-off.conf

  echo "[connection]" | sudo tee /etc/NetworkManager/conf.d/default-
  wifi-powersave-off.conf

  echo "wifi.powersave = 2" | sudo tee -a
  /etc/NetworkManager/conf.d/default-wifi-powersave-off.conf

  Reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1960817/+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 361598] Re: tracker-extract crashed with SIGSEGV in tracker_albumart_copy_to_local()

[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

** Changed in: tracker (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  tracker-extract crashed with SIGSEGV in
  tracker_albumart_copy_to_local()

Status in tracker package in Ubuntu:
  Expired

Bug description:
  Binary package hint: tracker

  Tracker crashed on indexing.

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/lib/tracker/tracker-extract
  NonfreeKernelModules: nvidia
  Package: tracker 0.6.93-0ubuntu1
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   tracker_albumart_copy_to_local ()
   tracker_process_albumart ()
   ?? ()
   ?? ()
   tracker_extract_get_metadata ()
  Title: tracker-extract crashed with SIGSEGV in 
tracker_albumart_copy_to_local()
  Uname: Linux 2.6.28-11-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev pulse pulse-access 
pulse-rt sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/361598/+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 1126537] Re: gnome-Tracker fills up my root with 27GB after kernel update

[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

** Changed in: tracker (Ubuntu)
Status: Incomplete => Expired

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

Title:
gnome-Tracker fills up my root with 27GB after kernel update

Status in tracker package in Ubuntu:
Expired

Bug description:
Top shows

814:44.76 tracker-miner-f

process now been running for 800 mins. after software-update installed
a new kernal.

This is the second time this has happened.

This is poorly documented software, no description of the metadata anywhere
or any justification for why this softare runs or
is needed. For all I know it could e malicious.

I do not like any software that keeps my disk continually busy for
three days without expaination.

I am going to find the line in the init scripts that kicks this off
and comment it out.

$ ubuntu_release
LSB Version:
core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu 11.10
Release: 11.10
Codename: oneiric

$ uname -a
Linux brucesalem-FQ582AA-ABA-SR5710F 3.0.0-31-generic #48-Ubuntu SMP Mon Feb
4 13:25:59 UTC 2013 i686 athlon i386 GNU/Linux

I challenge anyone to explain why this process should be running.

I am ssurely tempted to hange my window manager and possibly dump
Ubuntu and not use Gnome on any other Linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1126537/+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 1891270] Re: Iranian calendar shows in Azerbaijani language

2022-04-22 Thread esmaeelE

I check this bug on Ubuntu 20.04, 21.10, 22.04 and Xubuntu 22.10 
In first page of installer that we choose language of installer if I select 
Persian language final locale `fa_IR` will set after install complete.

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

Title:
  Iranian calendar shows in Azerbaijani language

Status in gnome-calendar package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Fix Committed

Bug description:
  I already installed Ubuntu 20.04.1 LTS  and set location on Iran during 
installation.
  After finishing installation successfully, I open the calendar by clicking at 
the top of the screen (where the clock is shown), I see the calendar with 
Azerbaijani names for month and weekdays.

  Such as "آقوست" for August and "جومعه آخشامی" for Thursday.

  But it should show in Iranian names such as "اوت" for August and
  "پنجشنبه" for Thursday.

  Description: Ubuntu 20.04.1 LTS
  Release: 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows

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

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

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

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

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

Title:
  Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging
  OpenGL app windows

Status in Mutter:
  Unknown
Status in metacity package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix

Bug description:
  Nvidia driver causes Xorg to use 100% CPU and shows high lag and
  stutter... but only when dragging glxgears/glxheads, or any window
  over them. Other apps do not exhibit the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 390.87-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Wed Oct 24 19:11:15 2018
  InstallationDate: Installed on 2018-05-26 (151 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1799679/+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 1970003] [NEW] Screen resolution and audio not recnognized by system

2022-04-22 Thread Jackson

Public bug reported:

Screen resolution and audio not recognized by system, the system does
not see the display or the audio output and defaults to an improper
screen resolution size with no audio output.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-108.122~18.04.1-generic 5.4.178
Uname: Linux 5.4.0-108-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
CasperVersion: 1.427
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Apr 23 04:26:46 2022
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-108-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation Device [10de:2504] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. Device [3842:3656]
LiveMediaBuild: Linux 18.04 - Release amd64
MachineType: Gigabyte Technology Co., Ltd. B560 DS3H AC-Y1
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt boot=casper quiet splash 
--
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2021
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F4
dmi.board.asset.tag: Default string
dmi.board.name: B560 DS3H AC-Y1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF4:bd06/18/2021:svnGigabyteTechnologyCo.,Ltd.:pnB560DS3HAC-Y1:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560DS3HAC-Y1:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: B560 MB
dmi.product.name: B560 DS3H AC-Y1
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1970003

Title:
  Screen resolution and audio not recnognized by system

Status in xorg package in Ubuntu:
  New

Bug description:
  Screen resolution and audio not recognized by system, the system does
  not see the display or the audio output and defaults to an improper
  screen resolution size with no audio output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-108.122~18.04.1-generic 5.4.178
  Uname: Linux 5.4.0-108-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  CasperVersion: 1.427
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Apr 23 04:26:46 2022
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-108-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:2504] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:3656]
  LiveMediaBuild: Linux 18.04 - Release amd64
  MachineType: Gigabyte Technology Co., Ltd. B560 DS3H AC-Y1
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt boot=casper quiet 
splash --
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B560 DS3H AC-Y1
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias:

[Desktop-packages] [Bug 1970002] [NEW] Unknown resilution configration error

2022-04-22 Thread Jackson

Public bug reported:

Display/audio not recognized at all.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-108.122~18.04.1-generic 5.4.178
Uname: Linux 5.4.0-108-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
CasperVersion: 1.427
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Apr 23 04:21:01 2022
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-108-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation Device [10de:2504] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. Device [3842:3656]
LiveMediaBuild: Linux 18.04 - Release amd64
MachineType: Gigabyte Technology Co., Ltd. B560 DS3H AC-Y1
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt boot=casper quiet splash 
--
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2021
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F4
dmi.board.asset.tag: Default string
dmi.board.name: B560 DS3H AC-Y1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF4:bd06/18/2021:svnGigabyteTechnologyCo.,Ltd.:pnB560DS3HAC-Y1:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560DS3HAC-Y1:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: B560 MB
dmi.product.name: B560 DS3H AC-Y1
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1970002

Title:
  Unknown resilution configration error

Status in xorg package in Ubuntu:
  New

Bug description:
  Display/audio not recognized at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-108.122~18.04.1-generic 5.4.178
  Uname: Linux 5.4.0-108-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  CasperVersion: 1.427
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Apr 23 04:21:01 2022
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-108-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:2504] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:3656]
  LiveMediaBuild: Linux 18.04 - Release amd64
  MachineType: Gigabyte Technology Co., Ltd. B560 DS3H AC-Y1
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt boot=casper quiet 
splash --
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B560 DS3H AC-Y1
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF4:bd06/18/2021:svnGigabyteTechnologyCo.,Ltd.:pnB560DS3HAC-Y1:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560DS3HAC-Y1:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B560 MB
  dmi.product.name: B560 DS3H AC-Y1
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2:

[Desktop-packages] [Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04

2022-04-22 Thread waffen

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

Sane problem here Ci5 10 + nVidia GTX 1650 +  driver 510.

In the login screen I can't see the gear, add line to the grub same
issue.

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

Title:
  wayland session not longer an option after recent update on Ubuntu
  22.04

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  After some recent update to Ubuntu 22.04 dev, X11 is selected by
  default and there is no longer the option to select the display
  protocol at login.

  It seems I am not the only affected:
  https://askubuntu.com/questions/1402671/ubuntu-no-gear-for-
  waylaland-x11

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-session 42.0-1ubuntu2
  Uname: Linux 5.17.3-051703-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 15 22:20:35 2022
  InstallationDate: Installed on 2022-02-02 (72 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+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 1954970] Re: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"

2022-04-22 Thread omriasta

This is happening to me as well, see the bug report here:
https://github.com/FreeRDP/FreeRDP/issues/7449

It appears to be an issue with any RD Gateway and related to OpenSSL 3
I tried the Flatpak method suggested and that works for me using the command 
line but would really like to be able to get back to using Remmina.

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

Title:
  remmina "Cannot connect to the RDP server ... via TLS. Check that the
  client and server support a common TLS version"

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

Bug description:
  Xubuntu Jammy (21.04)
  after upgrade
 libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1)
 libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1)
  Remmina can't connect to any RDP server (Win2008 R2) with error:
  "Cannot connect to the RDP server ... via TLS. Check that the client and 
server support a common TLS version"

  Rollback to Impish version of libs
 libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2
 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2
  makes it work normal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1954970/+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 1969853] Re: Bluetooth doesn't work but seems active

2022-04-22 Thread Diego Aparecido de Souza Pereira

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

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

Title:
  Bluetooth doesn't work but seems active

Status in bluez package in Ubuntu:
  New

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1969853/+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 1969853] [NEW] Bluetooth doesn't work but seems active

You have been subscribed to a public bug:

After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
stopped working via menu. Before I used versions 20.04 and 21.10, the
latter with kernel 5.13, and Bluetooth was recognized normally. The
bluetooth status in the terminal is this:

diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
   Docs: man:bluetoothd(8)
   Main PID: 1100 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 18808)
 Memory: 1.8M
CPU: 66ms
 CGroup: /system.slice/bluetooth.service
 └─1100 /usr/lib/bluetooth/bluetoothd

abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management interface 
1.21 initialized

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


** Tags: bot-comment
-- 
Bluetooth doesn't work but seems active
https://bugs.launchpad.net/bugs/1969853
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to bluez 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 1969999] [NEW] Looping music without no gui

2022-04-22 Thread Tuomas Lähteenmäki

Public bug reported:

rhythmbox 3.4.2 loop music without no gui.

OS Ubuntu 18.04 LTS.
5.4.0-109-generic #123~18.04.1-Ubuntu SMP Fri Apr 8 09:48:52 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux
rhytmbox version is 3.4.4
When you click playlist. Play song. Close the program in window x button. (From 
the x button right at the top. It's kill ui, but not stop music. Now is is 
looping your playlist. There is no icon for unhide the program. When you open 
program again and press play. You have seconds song playing. But you cannot 
stop first one.
You can only kill app for find top command rhythmbox id, but i cannot find task 
manager any rhythmbox apps.

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

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

Title:
  Looping music without no gui

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  rhythmbox 3.4.2 loop music without no gui.

  OS Ubuntu 18.04 LTS.
  5.4.0-109-generic #123~18.04.1-Ubuntu SMP Fri Apr 8 09:48:52 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux
  rhytmbox version is 3.4.4
  When you click playlist. Play song. Close the program in window x button. 
(From the x button right at the top. It's kill ui, but not stop music. Now is 
is looping your playlist. There is no icon for unhide the program. When you 
open program again and press play. You have seconds song playing. But you 
cannot stop first one.
  You can only kill app for find top command rhythmbox id, but i cannot find 
task manager any rhythmbox apps.

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

2022-04-22 Thread Erich Eickmeyer 

"Fix Released" isn't appropriate until it migrates from proposed.

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1967020] Re: WebKitWebProcess crashed with SIGSEGV

2022-04-22 Thread Gavin Graham

Evolution-3.44.0-1ubuntu1 in Jammy proposed fixes the issue.


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

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

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 1969140] Re: Window minimize animation flickers and appears in the wrong place

2022-04-22 Thread Anas Bushnaq

Changing the refresh rate on my display seems to have fixed this issue
for me.

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

Title:
  Window minimize animation flickers and appears in the wrong place

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Graphical glitches appears while minimizing or maximizing apps in x11
  session randomly, screencast below

  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
  Date: Thu Apr 14 17:07:49 2022
  DisplayManager: gdm3
  GsettingsChanges:

  InstallationDate: Installed on 2022-04-12 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  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/gnome-shell/+bug/1969140/+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 1969990] [NEW] Browser shows nothing readable

2022-04-22 Thread jpo

Public bug reported:

Opening the help browser shows nothing readable

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: yelp 42.1-1
ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
Uname: Linux 5.15.0-1005-raspi aarch64
ApportVersion: 2.20.11-0ubuntu82
Architecture: arm64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 22:17:43 2022
ImageMediaBuild: 20220419
SourcePackage: yelp
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Browser shows nothing readable

Status in yelp package in Ubuntu:
  New

Bug description:
  Opening the help browser shows nothing readable

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yelp 42.1-1
  ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
  Uname: Linux 5.15.0-1005-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 22:17:43 2022
  ImageMediaBuild: 20220419
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1969990/+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 1969990] Re: Browser shows nothing readable

2022-04-22 Thread jpo

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1969990/+attachment/5582625/+files/Screenshot%20from%202022-04-22%2022-23-40.png

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

Title:
  Browser shows nothing readable

Status in yelp package in Ubuntu:
  New

Bug description:
  Opening the help browser shows nothing readable

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yelp 42.1-1
  ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
  Uname: Linux 5.15.0-1005-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 22:17:43 2022
  ImageMediaBuild: 20220419
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1969990/+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 1969959] Re: Weird colors after startup (Ubuntu 22.04)

2022-04-22 Thread Damon Howe

the try ubuntu screen is fine.
after booted to desktop for a split second the screen colors are normal and 
then BAM i get an almost all white screen
i have tested with 2 systems and 2 video cards.

intel b660 + 12600k nvidia 3060 ti
amd x570 + 5600x nvidia 3060 ti
both systems have same behavior.
i am pretty sure this started happening with the ubuntu 22.04 daily after 
03-28-2022 but not 100% sure
i reported it over and over in the #ubuntu #ubuntu-next for 3 weeks and warned 
everyone repeatably.
i tried to get other people to verify with similar systems and while doing that 
i got silenced where i couldnt talk and i got kicked out #ubuntu-next.
they told me to report the bug but i first wanted to make sure it was happening 
on other peoples systems and i was in the process of that very thing when i got 
silenced.
it is very clear that there are some people there who dont like nvidia.

i would like to add that it is fine while using a nvidia 1060.

thanks

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

Title:
  Weird colors after startup (Ubuntu 22.04)

Status in xorg package in Ubuntu:
  New

Bug description:
  I started Ubuntu 22.04 from a live pen drive. Everything seems fine,
  the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
  appears. When hitting "Try Ubuntu", the screen turns black for a
  couple of seconds and then re-appears in yellow and brown colors,
  feels like a 4 color display (white, black, yellow and orange) and I
  can hardly see anything - sending this bug report from that live
  system right after starting it up.

  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
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:54:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 
00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7C56
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550-A PRO (MS-7C56)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C56
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  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/xorg/+bug/1969959/+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 109943] Re: Thunderbird: high CPU usage from progress bars

** Changed in: thunderbird
   Importance: High => Unknown

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

Title:
  Thunderbird: high CPU usage from progress bars

Status in Mozilla Thunderbird:
  In Progress
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: mozilla-thunderbird

  When sending a simple and short email with Thunderbird via SMTP the
  CPU is used intensively. This seems not to be necessary. If the
  sending failed and an corresponding error message dialog appears, the
  CPU is still being used. When pressing ok to close the error dialog
  the CPU is fine. This suggests it might be related specifically to the
  progress bar.  Such behavior is especially annoying on a laptop where
  you can hear the CPU usage because of a starting fan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/109943/+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 1965439] Re: software-properties-qt can no longer launch when called by pkexec

2022-04-22 Thread Erich Eickmeyer 

** Tags added: kubuntu ubuntustudio

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

Title:
  software-properties-qt can no longer launch when called by pkexec

Status in kubuntu-settings package in Ubuntu:
  In Progress
Status in policykit-1 package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  In Progress
Status in kubuntu-settings source package in Jammy:
  In Progress
Status in policykit-1 source package in Jammy:
  Confirmed
Status in software-properties source package in Jammy:
  Confirmed
Status in ubuntustudio-default-settings source package in Jammy:
  In Progress

Bug description:
  See description below. As the driver manager is done inside software-
  properties-qt, it's basically the same bug, but now it's affected by
  something we can't exactly get into the mechanism of: plasma-
  discover's "Software Sources" link.

  Steps to recrate:

  1) Open Plasma-discover
  2) Go to Settings
  3) Under click on "Software Sources"
  4) Attempt to enter password

  Expected: Software properties opens

  Actual: Pkexec keeps asking for password.

  --

  Earlier description:

  The driver manager for both Ubuntu Studio and Kubuntu can no longer
  launch due to some updated security measures in PolicyKit.

  The original behavior was that systemsettings would open
  /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-
  manger) via pkexec, which would then open software-settings-qt.
  Unfortunately, the new behavior does not act correctly to pkexec and
  pkexec does not see the user as available in the sudoers file.

  The only way around this was to pass "export DISPLAY=:0" inside the
  appropriate driver manager executable with the command "sudo software-
  properties-qt". The KCM itself needs to execute the driver-manager via
  xterm, which then prompts for a password. It's ugly, but it works.

  I will attach a debdiff for the kubuntu-settings package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntustudio-default-settings 22.04.19 [modified: 
usr/share/sddm/themes/ubuntustudio/theme.conf]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 17 12:19:44 2022
  InstallationDate: Installed on 2021-03-20 (361 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: ubuntustudio-default-settings
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago)
  modified.conffile..etc.skel..local.share.konsole.Profile: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1965439/+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 1969982] [NEW] Bluetooth sound card not detected - Bluetooth software blocked

2022-04-22 Thread RICARDO DA SILVA LISBOA

Public bug reported:

When I upgraded from ubuntu 21.10 to 22.04 the bluetooth stopped
working. I did a fresh install from scratch and bluetooth no longer
works.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ricardo3058 F pulseaudio
 /dev/snd/pcmC0D0p:   ricardo3058 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 15:37:34 2022
InstallationDate: Installed on 2022-04-22 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2017
dmi.bios.release: 1.11
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.11
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: T-Rex_SK
dmi.board.vendor: Acer
dmi.board.version: V1.11
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.11
dmi.ec.firmware.release: 1.8
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd08/11/2017:br1.11:efr1.8:svnAcer:pnAspireES1-572:pvrV1.11:rvnAcer:rnT-Rex_SK:rvrV1.11:cvnAcer:ct10:cvrV1.11:skuAspireES1-572_1085_V1.11:
dmi.product.family: SKL
dmi.product.name: Aspire ES1-572
dmi.product.sku: Aspire ES1-572_1085_V1.11
dmi.product.version: V1.11
dmi.sys.vendor: Acer

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

Title:
  Bluetooth sound card not detected - Bluetooth software blocked

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I upgraded from ubuntu 21.10 to 22.04 the bluetooth stopped
  working. I did a fresh install from scratch and bluetooth no longer
  works.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ricardo3058 F pulseaudio
   /dev/snd/pcmC0D0p:   ricardo3058 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:37:34 2022
  InstallationDate: Installed on 2022-04-22 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2017
  dmi.bios.release: 1.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: T-Rex_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd08/11/2017:br1.11:efr1.8:svnAcer:pnAspireES1-572:pvrV1.11:rvnAcer:rnT-Rex_SK:rvrV1.11:cvnAcer:ct10:cvrV1.11:skuAspireES1-572_1085_V1.11:
  dmi.product.family: SKL
  dmi.product.name: Aspire ES1-572
  dmi.product.sku: Aspire ES1-572_1085_V1.11
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1969982/+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 1969834] Re: artifacts (many short horizontal lines) on laptop with hybrid graphix

There is a strong suspicion that the problem is in the Plasma code. I
logged out and entered the working gnome - until I found artifacts.
Switched to Plasma - artifacts appear

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

Title:
  artifacts (many short horizontal lines) on laptop with hybrid graphix

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  artifacts (many short horizontal lines)
  see https://youtu.be/SQOOp0bd0LE
  artifacts only on display (screen capture is clear)
  i have laptop with hybrid graphix (intel nvidia)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.16.13-051613-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:  gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Apr 21 22:06:20 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:9a68] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb]
  InstallationDate: Installed on 2022-02-28 (52 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.16.13-051613-generic 
root=UUID=98fc789e-6997-4a4b-b741-da24a1b635ca ro quiet splash 
modprode.blacklist=nouveau snd_intel_dspcfg.dsp_driver=1 
snd_hda_intel.dmic_detect=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2022
  dmi.bios.release: 3.16
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E17L2IMS.310
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17L2
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.310:bd01/13/2022:br3.16:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3:
  dmi.product.family: GF
  dmi.product.name: Katana GF76 11UC
  dmi.product.sku: 17L2.3
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1969834/+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 1969834] Re: artifacts (many short horizontal lines) on laptop with hybrid graphix

I thought that this is possible due to warming up, but the temperature
is normal

hetman@katana-lin:~$ sensors
coretemp-isa-
Adapter: ISA adapter
Package id 0:  +45.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:+43.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:+41.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:+42.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:+41.0°C  (high = +100.0°C, crit = +100.0°C)
Core 4:+42.0°C  (high = +100.0°C, crit = +100.0°C)
Core 5:+39.0°C  (high = +100.0°C, crit = +100.0°C)

BAT1-acpi-0
Adapter: ACPI interface
in0:  12.92 V  
curr1: 0.00 A  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:+42.0°C  

nvme-pci-0200
Adapter: PCI adapter
Composite:+39.9°C  (low  = -20.1°C, high = +84.8°C)
   (crit = +89.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:+46.0°C  (crit = +100.0°C)


hetman@katana-lin:~$ nvidia-smi -q -d temperature

==NVSMI LOG==


Timestamp : Fri Apr 22 21:14:15 2022
Driver Version: 510.60.02
CUDA Version  : 11.6

Attached GPUs : 1
GPU :01:00.0
Temperature
GPU Current Temp  : 46 C
GPU Shutdown Temp : 100 C
GPU Slowdown Temp : 97 C
GPU Max Operating Temp: 87 C
GPU Target Temperature: N/A
Memory Current Temp   : N/A
Memory Max Operating Temp : N/A

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

Title:
  artifacts (many short horizontal lines) on laptop with hybrid graphix

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  artifacts (many short horizontal lines)
  see https://youtu.be/SQOOp0bd0LE
  artifacts only on display (screen capture is clear)
  i have laptop with hybrid graphix (intel nvidia)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.16.13-051613-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:  gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Apr 21 22:06:20 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:9a68] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb]
  InstallationDate: Installed on 2022-02-28 (52 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.16.13-051613-generic 
root=UUID=98fc789e-6997-4a4b-b741-da24a1b635ca ro quiet splash 
modprode.blacklist=nouveau snd_intel_dspcfg.dsp_driver=1 
snd_hda_intel.dmic_detect=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2022
  dmi.bios.release: 3.16
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E17L2IMS.310
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17L2
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.310:bd01/13/2022:br3.16:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3:
  dmi.product.family: GF
  dmi.product.name: Katana GF76 11UC
  dmi.product.sku: 17L2.3

[Desktop-packages] [Bug 1969977] [NEW] info (GNU texinfo) 6.7 segfaults in ubuntu 20.04.1

2022-04-22 Thread Cesar Rabak

Public bug reported:

The Standalone GNU Info documentation browser /info/ fails with a
segfault in a Ubuntu focal fossa recently updated system:

$  lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04

$ uname -a
Linux  5.13.0-40-generic #45~20.04.1-Ubuntu SMP Mon Apr 4 09:38:31 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

If I issue an info --version it works
 info --version
info (GNU texinfo) 6.7

Copyright (C) 2019 Free Software Foundation, Inc.
Licença GPLv3+: GNU GPL versão 3 ou superior 
Esse é um software livre: você é livre para alterá-lo e redistribuí-lo.
NÃO HÁ QUALQUER GARANTIA, na máxima extensão permitida em lei.

Display in Portuguese as machine is set to Brazilian locale

If issued with --help, it also prints 42 lines of information (in
Portuguese).

Any attempt to see documentation be it by asking a node, e.g. 'info
octave' or directly to a known info file, e.g. 'info -f
/usr/share/info/octave.info.gz' segfaults.

The message says the core dumped has been stored, but I still didn't
manage to find where to get a look with gdb.

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


** Tags: segfault

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

Title:
  info (GNU texinfo) 6.7 segfaults in ubuntu 20.04.1

Status in texinfo package in Ubuntu:
  New

Bug description:
  The Standalone GNU Info documentation browser /info/ fails with a
  segfault in a Ubuntu focal fossa recently updated system:

  $  lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  $ uname -a
  Linux  5.13.0-40-generic #45~20.04.1-Ubuntu SMP Mon Apr 4 09:38:31 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

  If I issue an info --version it works
   info --version
  info (GNU texinfo) 6.7

  Copyright (C) 2019 Free Software Foundation, Inc.
  Licença GPLv3+: GNU GPL versão 3 ou superior 

  Esse é um software livre: você é livre para alterá-lo e redistribuí-lo.
  NÃO HÁ QUALQUER GARANTIA, na máxima extensão permitida em lei.

  Display in Portuguese as machine is set to Brazilian locale

  If issued with --help, it also prints 42 lines of information (in
  Portuguese).

  Any attempt to see documentation be it by asking a node, e.g. 'info
  octave' or directly to a known info file, e.g. 'info -f
  /usr/share/info/octave.info.gz' segfaults.

  The message says the core dumped has been stored, but I still didn't
  manage to find where to get a look with gdb.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1969977/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2022-04-22 Thread Mario Limonciello

> The comment at
https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992
suggests that disabling the DynamicUser= setting makes the service work
again. Maybe that's worth a try, in order to get both problems solved?
(i.e. shipping an override config for fwupd)

> $cat /etc/systemd/system/fwupd-refresh.service.d/override.conf
> [Service]
> DynamicUser=no

The whole point of using DynamicUser in this case was so that fwupdmgr
didn't run as root when it reached out to the web to get data.  Yes,
certainly turning off DynamicUser in fwupd-refresh.service will solve
the problem, but that is then a different threat vector.

I think if turning off DynamicUser=1, then we probably need to also
create a new service account for that systemd service to use.

I'll open a new bug to move this discussion to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969976

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Released
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  Fix Released
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  rdkit was failing fast and giving up (that will be a different bug,

[Desktop-packages] [Bug 1969963] Re: Increasing the Terminal window height on 22.04 LTS using Alt + F8 + [Up|Down] is broken.

2022-04-22 Thread Paul White

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

** Tags added: jammy

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

Title:
  Increasing the Terminal window height on 22.04 LTS using Alt + F8 +
  [Up|Down] is broken.

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I experienced a bug on 22.04 LTS when resizing the height of the
  Terminal window using Alt + F8 + [Up|Down]. Increasing the height no
  longer works while decreasing the height still works. I tested other
  applications (e.g. Gedit, Firefox, Files) and I can still increase the
  window height.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1969963/+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 1969834] Re: artifacts (many short horizontal lines) on laptop with hybrid graphix

the error has not been fixed, it's just that the artifacts do not start
to appear immediately, but when the computer works a little

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

Title:
  artifacts (many short horizontal lines) on laptop with hybrid graphix

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  artifacts (many short horizontal lines)
  see https://youtu.be/SQOOp0bd0LE
  artifacts only on display (screen capture is clear)
  i have laptop with hybrid graphix (intel nvidia)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.16.13-051613-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:  gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Apr 21 22:06:20 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:9a68] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb]
  InstallationDate: Installed on 2022-02-28 (52 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.16.13-051613-generic 
root=UUID=98fc789e-6997-4a4b-b741-da24a1b635ca ro quiet splash 
modprode.blacklist=nouveau snd_intel_dspcfg.dsp_driver=1 
snd_hda_intel.dmic_detect=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2022
  dmi.bios.release: 3.16
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E17L2IMS.310
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17L2
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.310:bd01/13/2022:br3.16:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3:
  dmi.product.family: GF
  dmi.product.name: Katana GF76 11UC
  dmi.product.sku: 17L2.3
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1969834/+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 1969834] Re: artifacts (many short horizontal lines) on laptop with hybrid graphix

done.

this is very strange, but when I did the log, I noticed that the artifacts 
stopped appearing. And I was very surprised because. I did not reboot the 
laptop - it was woken up (23:48:37 suspend entry (deep)).
I recorded the video at about 21:27 and this period is in the log.
Perhaps the reinstallation of some libraries between 21:27 and 23:48, primarily 
Qt, had an effect (teamviewer did not want to start for me).

The bug has been fixed but I have no idea how.

** Attachment added: "log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1969834/+attachment/5582572/+files/journal.tar.gz

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

Title:
  artifacts (many short horizontal lines) on laptop with hybrid graphix

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  artifacts (many short horizontal lines)
  see https://youtu.be/SQOOp0bd0LE
  artifacts only on display (screen capture is clear)
  i have laptop with hybrid graphix (intel nvidia)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.16.13-051613-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:  gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Apr 21 22:06:20 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:9a68] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb]
  InstallationDate: Installed on 2022-02-28 (52 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.16.13-051613-generic 
root=UUID=98fc789e-6997-4a4b-b741-da24a1b635ca ro quiet splash 
modprode.blacklist=nouveau snd_intel_dspcfg.dsp_driver=1 
snd_hda_intel.dmic_detect=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2022
  dmi.bios.release: 3.16
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E17L2IMS.310
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17L2
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.310:bd01/13/2022:br3.16:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3:
  dmi.product.family: GF
  dmi.product.name: Katana GF76 11UC
  dmi.product.sku: 17L2.3
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1969834/+subscriptions

[Desktop-packages] [Bug 1969963] [NEW] Increasing the Terminal window height on 22.04 LTS using Alt + F8 + [Up|Down] is broken.

You have been subscribed to a public bug:

I experienced a bug on 22.04 LTS when resizing the height of the
Terminal window using Alt + F8 + [Up|Down]. Increasing the height no
longer works while decreasing the height still works. I tested other
applications (e.g. Gedit, Firefox, Files) and I can still increase the
window height.

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

-- 
Increasing the Terminal window height on 22.04 LTS using Alt + F8 + [Up|Down] 
is broken.
https://bugs.launchpad.net/bugs/1969963
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-terminal 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 1969974] [NEW] Problem with screencasting

2022-04-22 Thread Fateme Tamehri

Public bug reported:

I've just installed ubuntu 22.04; Screencasting (video recording)
doesn't work... every time I open the screen tools (those which you can
open with prtscr), and press the red button for screen recording, a red
thing appear top right of my screen and it will be disappeared
immediately! And then nothing happen :(

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
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 22:03:57 2022
DistUpgraded: 2022-04-22 18:01:56,000 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:828c]
InstallationDate: Installed on 2021-08-07 (257 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b5ae Chicony Electronics Co., Ltd HP HD Camera
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP EliteBook 840 G4
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=cfaddaca-a453-457a-bdb2-1acc1600816e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-04-22 (0 days ago)
dmi.bios.date: 04/11/2017
dmi.bios.release: 1.3
dmi.bios.vendor: HP
dmi.bios.version: P78 Ver. 01.03
dmi.board.name: 828C
dmi.board.vendor: HP
dmi.board.version: KBC Version 45.34
dmi.chassis.asset.tag: 5CG7242D5P
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 69.52
dmi.modalias: 
dmi:bvnHP:bvrP78Ver.01.03:bd04/11/2017:br1.3:efr69.52:svnHP:pnHPEliteBook840G4:pvr:rvnHP:rn828C:rvrKBCVersion45.34:cvnHP:ct10:cvr:skuX3V00AV:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP EliteBook 840 G4
dmi.product.sku: X3V00AV
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.14.1+22.04.20211217-0ubuntu2
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/1969974

Title:
  Problem with screencasting

Status in xorg package in Ubuntu:
  New

Bug description:
  I've just installed ubuntu 22.04; Screencasting (video recording)
  doesn't work... every time I open the screen tools (those which you
  can open with prtscr), and press the red button for screen recording,
  a red thing appear top right of my screen and it will be disappeared
  immediately! And then nothing happen :(

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 22:03:57 2022
  DistUpgraded: 2022-04-22 18:01:56,000 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:828c]
  InstallationDate: Installed on 2021-08-07 (257 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5ae Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID

[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

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

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

Status in mutter package in Ubuntu:
  Confirmed

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 1969959] [NEW] Weird colors after startup (Ubuntu 22.04)

2022-04-22 Thread Oliver Tacke

Public bug reported:

I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the
usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
appears. When hitting "Try Ubuntu", the screen turns black for a couple
of seconds and then re-appears in yellow and brown colors, feels like a
4 color display (white, black, yellow and orange) and I can hardly see
anything - sending this bug report from that live system right after
starting it up.

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
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.470
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 15:54:05 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 
[VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Micro-Star International Co., Ltd. MS-7C56
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
maybe-ubiquity quiet splash ---
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.40
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B550-A PRO (MS-7C56)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C56
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
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/1969959

Title:
  Weird colors after startup (Ubuntu 22.04)

Status in xorg package in Ubuntu:
  New

Bug description:
  I started Ubuntu 22.04 from a live pen drive. Everything seems fine,
  the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
  appears. When hitting "Try Ubuntu", the screen turns black for a
  couple of seconds and then re-appears in yellow and brown colors,
  feels like a 4 color display (white, black, yellow and orange) and I
  can hardly see anything - sending this bug report from that live
  system right after starting it up.

  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
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:54:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 
00 [VGA controller])
 Subsystem:

[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(

2022-04-22 Thread Evan Girardin

I still crash with this issue whenever I try to apply changes to any
display settings (e.g. refresh rate, multi-monitor positioning, etc.)

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

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 1854183] Re: when compiz have enabled gtk-window-decorator libreoffice-calc show transparent window

Launchpad has imported 20 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=126886.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2019-08-13T15:31:05+00:00 Gabriel Finkelstein wrote:

Description:
After opening a CSV in Calc (Text import) instead of opening the main Calc 
window, the space where the window is supposed to be, shows a "frozen" image of 
whatever was under the window before opening it. Calc menus and buttons still 
work, but nothing is visible. It'a a bit hard to explain, but the attached 
video is self explanatory.

The only error I get is:

(soffice:28076): Gtk-WARNING **: 12:06:36.708: infinite surface size not
supported

I'm using Ubuntu MATE 18.04
- This happens when using Compiz, but not when using Compton
- This happens in LO 6.2 & 6.3 but not in LO 6.1.5
- This happens when Calc's window starts maximized, but not when it starts 
unmaximized
- This happens when using libreoffice-gtk3 but not when using libreoffice-gtk2

Steps to Reproduce:
1. Enable Compiz
2. Open a CSV file with Calc
3. Click "OK" on the "Text import" window

Actual Results:
Whatever was on the screen stays frozen, as if it were a static image, and the 
Calc window were invisible. Moving the mouse around and clicking seems to open 
Calc menus.

Expected Results:
Calc's main window should open normally

Reproducible: Always

User Profile Reset: Yes

OpenGL enabled: Yes

Additional Info:
Version: 6.3.0.4
Build ID: 1:6.3.0-0ubuntu0.18.04.1~lo2
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: es-AR (en_US.UTF-8); UI-Language: en-US
Calc: threaded

Reply at: https://bugs.launchpad.net/compiz/+bug/1854183/comments/0

On 2019-08-13T15:32:04+00:00 Gabriel Finkelstein wrote:

Created attachment 153353
Reproducing the issue

Reply at: https://bugs.launchpad.net/compiz/+bug/1854183/comments/1

On 2019-09-08T16:40:35+00:00 JBF wrote:

Not reproducible with version 6.3.3.0+ built at home under Ubuntu/Gnome
18.04  x86-64 with GTK3 backend.

Best regards. JBF

Reply at: https://bugs.launchpad.net/compiz/+bug/1854183/comments/2

On 2019-09-12T08:43:19+00:00 timur wrote:

You write: 2. Open a CSV file with Calc
But in video you open via double click. Does it also happen with File-Open?
Does it happen with other CSV files or any other files?
How did you install LO 6.2 and 6.3, via PPA or debs? 
Seems like some integration issue.

Reply at: https://bugs.launchpad.net/compiz/+bug/1854183/comments/3

On 2019-09-12T16:41:38+00:00 Gabriel Finkelstein wrote:

(In reply to Timur from comment #3)
> You write: 2. Open a CSV file with Calc
> But in video you open via double click. Does it also happen with File-Open?
If I open Calc and then go to File > Open, the CSV opens correctly. BUT if I 
leave that file open and open a second file the same way, the issue happens 
again.

I can also reproduce the issue by opening the CSV through the CLI with the 
command:
libreoffice aaa.csv

Something else I just discovered: if Calc is already open with a blank
spreadsheet, and I open a CSV in the same way as the steps to reproduce,
it opens correctly.

> Does it happen with other CSV files or any other files?
It happens with any CSV file.
I have not seen it happen with any other formats. Although CSV is the only one 
I use that uses the text import feature.

> How did you install LO 6.2 and 6.3, via PPA or debs? 
Via PPA: https://launchpad.net/~libreoffice/+archive/ubuntu/ppa

I also experienced this issue when I had Ubuntu 16.04 + Gnome Flashback
+ Compiz.

I just tested on another machine with Ubuntu MATE 18.04 and a clean
Compiz profile, and the issue also happens there.

If it helps, this person also has the same issue (that's me in the
answer): https://askubuntu.com/questions/1140156/calc-shows-title-bar-
only-when-opening-csv-in-compiz/1141598

Reply at: https://bugs.launchpad.net/compiz/+bug/1854183/comments/4

On 2019-09-13T02:51:44+00:00 Qa-admin-q wrote:

[Automated Action] NeedInfo-To-Unconfirmed

Reply at: https://bugs.launchpad.net/compiz/+bug/1854183/comments/5

On 2019-11-24T17:25:09+00:00 Apiuano-lobugs wrote:

Not sure if related. Came here because of the "infinite surface size not
supported" warning.

I had the similar issues (cinnamon freezes but can move mouse) with a
personal python3 (3.6)

[Desktop-packages] [Bug 1854183] Re: when compiz have enabled gtk-window-decorator libreoffice-calc show transparent window

2022-04-22 Thread Thomas Mayer

** Package changed: libreoffice (Unity Linux) => libreoffice (Ubuntu)

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

Title:
  when compiz have enabled gtk-window-decorator libreoffice-calc show
  transparent window

Status in Compiz:
  New
Status in libreoffice package in Ubuntu:
  Unknown

Bug description:
  ubuntu 20.04 
  Compiz 0.9.14.0
  Libreoffice 6.3 from repo
  LIbreoffice 6.4 from document fundation

  Description:
  when compiz have enabled gtk-window-decorator, libreoffice apliction show 
transparent window

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1854183/+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 1969816] Re: Display dimming despite setting being turned off

2022-04-22 Thread Jacob Starr

I don't have the second setting, but the problem has seemed to resolve
itself overnight.

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

Title:
  Display dimming despite setting being turned off

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

Bug description:
  The display is dimming after a few seconds of "inactivity" despite
  turning off the setting to dim the display. This seems to occur on any
  power setting and a reboot did not solve the problem. This makes
  activities such as reading difficult as the display becomes harder to
  read and I have to interact with the computer more than necessary to
  keep the screen bright.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.14.0-1033.36-oem 5.14.21
  Uname: Linux 5.14.0-1033-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 21 09:56:56 2022
  DistUpgraded: 2022-04-21 09:33:57,457 DEBUG failed to SystemLock() (E:Could 
not get lock /var/lib/dpkg/lock. It is held by process 55177 (dpkg), W:Be aware 
that removing the lock file is not a solution and may break your system., 
E:Unable to lock the administration directory (/var/lib/dpkg/), is another 
process using it?)
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:9a78] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0a7d]
  InstallationDate: Installed on 2022-03-29 (23 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Dell Inc. Inspiron 14 5410
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1033-oem 
root=UUID=65a9ddc2-0f7d-4b2c-8228-d1f755668bf9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)
  dmi.bios.date: 02/15/2022
  dmi.bios.release: 2.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.7.1
  dmi.board.name: 0XPW9D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.7.1:bd02/15/2022:br2.7:svnDellInc.:pnInspiron145410:pvr:rvnDellInc.:rn0XPW9D:rvrA00:cvnDellInc.:ct10:cvr:sku0A7D:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 14 5410
  dmi.product.sku: 0A7D
  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/+source/gnome-control-center/+bug/1969816/+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 1854183] [NEW] when compiz have enabled gtk-window-decorator libreoffice-calc show transparent window

You have been subscribed to a public bug:

ubuntu 20.04 
Compiz 0.9.14.0
Libreoffice 6.3 from repo
LIbreoffice 6.4 from document fundation

Description:
when compiz have enabled gtk-window-decorator, libreoffice apliction show 
transparent window

** Affects: compiz
 Importance: Undecided
 Status: New

** Affects: libreoffice (Ubuntu)
 Importance: Unknown
 Status: Unknown


** Tags: gtk-window-decorator
-- 
when compiz have enabled gtk-window-decorator libreoffice-calc show transparent 
window
https://bugs.launchpad.net/bugs/1854183
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libreoffice 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 1968459] Re: IBus 1.5.26 does not enable on Xorg sesson

** Changed in: ibus
   Status: New => Fix Released

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

Title:
  IBus 1.5.26 does not enable on Xorg sesson

Status in ibus:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus package in Debian:
  Fix Released

Bug description:
  I tested newly installed Ubuntu 22.04 LTS dev.

  step to reproduce:
  1. boot
  2. select user
  3. session changes to Ubuntu on Xorg from Ubuntu
  4. enter password
  5. run gedit
  6. put Hankaku/Zenkaku key
  7. nothing to happen

  consideration：
  Run "ps ax |grep ibus" on terminal:
  $ ps ax |grep ibus
     5774 ?Ss 0:00 sh -c /usr/bin/ibus-daemon --panel disable $([[ 
$XDG_SESSION_TYPE == "x11" ]] && echo "--xim")
     5779 ?Sl 0:00 /usr/bin/ibus-daemon --panel disable
     5863 ?Sl 0:00 /usr/libexec/ibus-dconf
     5864 ?Sl 0:00 /usr/libexec/ibus-extension-gtk3
     5868 ?Sl 0:00 /usr/libexec/ibus-portal
     5965 ?Sl 0:00 /usr/lib/ibus-mozc/ibus-engine-mozc --ibus
     6831 pts/1R+ 0:00 grep --color=auto ibus
  It is strange.

  IBus 1.5.25 introduces systemd user unit files.
  /usr/lib/systemd/user/org.freedesktop.IBus.session.GNOME.service
  /usr/lib/systemd/user/org.freedesktop.IBus.session.generic.service
  above contains "ExecStart=sh -c '/usr/bin/ibus-daemon --panel disable $([[ 
$XDG_SESSION_TYPE == "x11" ]] && echo "--xim")"
  
https://github.com/ibus/ibus/blob/master/bus/services/org.freedesktop.IBus.session.GNOME.service.in#L21
  It may be bashism.
  I changed to "ExecStart=bash -c '/usr/bin/ibus-daemon --panel disable $([[ 
$XDG_SESSION_TYPE == "x11" ]] && echo "--xim")" and reboot then works as 
expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1968459/+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 1969910] Re: Firefox lost passwords, saved tabs, settings after upgrading to Ubuntu 22.04

2022-04-22 Thread Olivier Tilloy

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

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

Title:
  Firefox lost passwords, saved tabs, settings after upgrading to Ubuntu
  22.04

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Ubuntu 22.04 from Ubuntu 21.10, Firefox lost its
  all passwords, saved tabs, settings.

  I'm using KDE on Wayland; before the upgrade, was using KDE on X.

  Very annoying issue and seriously breaks productivity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969910/+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 1969946] [NEW] Steam crashes on some games after update to 22.04

2022-04-22 Thread amusicsite

Public bug reported:

Steam crashes on some games after update to 22.04 might be an nvidia
problem so included bug report

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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 15:32:55 2022
DisplayManager: gdm3
InstallationDate: Installed on 2020-06-02 (689 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

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


** Tags: amd64 apport-bug jammy

** Attachment added: "nvidia-bug-report.log.gz"
   
https://bugs.launchpad.net/bugs/1969946/+attachment/5582454/+files/nvidia-bug-report.log.gz

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

Title:
  Steam crashes on some games after update to 22.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steam crashes on some games after update to 22.04 might be an nvidia
  problem so included bug report

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:32:55 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-02 (689 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969946/+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 1967843] Re: cheese display corrupted under Ubuntu 22.04

2022-04-22 Thread Luís Louro

Also with Logitech C270. 640x480 provides good picture but you can't
take a photo.

$ cheese

(cheese:19369): Gdk-WARNING **: 15:21:08.634: Native Windows taller than 65535 
pixels are not supported
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed

(cheese:19369): cheese-WARNING **: 15:21:40.621: Output state was not
configured: ../gst-libs/gst/video/gstvideoencoder.c(2281):
gst_video_encoder_can_push_unlocked ():
/GstCameraBin:camerabin/GstEncodeBin:image-encodebin/GstJpegEnc:jpegenc0

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

Title:
  cheese display corrupted under  Ubuntu 22.04

Status in cheese package in Ubuntu:
  In Progress
Status in cheese source package in Jammy:
  In Progress

Bug description:
  The cheese application produces a corrupted display under Ubuntu 22.04
  with a Logitech C525 webcam. When started from the command line,
  cheese produces repeated warnings of the form...

  (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
  There may be a timestamping problem, or this computer is too slow.

  Adding /etc/modprobe.d/uvcvideo.conf

  with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue
  is not seen in either Ubuntu 21.10 or under Fedora-Workstation-
  Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both
  Wayland and X11 displays with the Nvidia drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  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-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 05:15:35 2022
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cheese 41.1-1build1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  Tags: wayland-session third-party-packages jammy gstreamer-error
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias:

[Desktop-packages] [Bug 1969767] Re: totem crashes when attempting to play mp4 files

2022-04-22 Thread Paul White

No I don't. The attached file shows the terminal output after successive
staring in a terminal.

** Attachment added: "totem_in_a_terminal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1969767/+attachment/5582438/+files/totem_in_a_terminal.txt

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

Title:
  totem crashes when attempting to play mp4 files

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  I can add and display a directory of .mp4 files in totem but when
  attempting to play any of them totem will crash. Any attempts to
  restart totem fail with the window not appearing at all.

  After several attempts to restart I can add an .mp4 file but any
  attempt to play it results in the described sequence repeating with
  sometimes the window not appearing, sometimes I can navigate to a
  local file and sometimes the above error is displayed as soon as
  totem's window is displayed.

  These reports have appeared on errors.ubuntu.com which relate to the
  most recent crashes:

  https://errors.ubuntu.com/oops/383cc642-c157-11ec-8afa-fa163e993415
  https://errors.ubuntu.com/oops/37f3e83a-c157-11ec-a3c9-fa163ef35206

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  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: Thu Apr 21 10:53:17 2022
  InstallationDate: Installed on 2022-04-02 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1969767/+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 1969936] [NEW] package firefox 99.0+build2-0ubuntu0.20.04.2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-04-22 Thread Abdullah Almubarak

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 99.0+build2-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  iabdull4h   1782 F pulseaudio
 /dev/snd/controlC0:  iabdull4h   1782 F pulseaudio
 /dev/snd/controlC1:  iabdull4h   1782 F pulseaudio
BuildID: 20220330194208
CasperMD5CheckResult: unknown
Channel: Unavailable
Date: Fri Apr 22 16:32:46 2022
ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
ForcedLayersAccel: False
InstallationDate: Installed on 2022-04-03 (18 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
IpRoute:
 default via 192.168.3.1 dev wlp5s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp5s0 scope link metric 1000 
 192.168.3.0/24 dev wlp5s0 proto kernel scope link src 192.168.3.16 metric 600
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2
 apt  2.4.5
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox 99.0+build2-0ubuntu0.20.04.2 failed to install/upgrade: 
new firefox package pre-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to jammy on 2022-04-22 (0 days ago)
dmi.bios.date: 07/08/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0807
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0807:bd07/08/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


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

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

Title:
  package firefox 99.0+build2-0ubuntu0.20.04.2 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 99.0+build2-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  iabdull4h   1782 F pulseaudio
   /dev/snd/controlC0:  iabdull4h   1782 F pulseaudio
   /dev/snd/controlC1:  iabdull4h   1782 F pulseaudio
  BuildID: 20220330194208
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Fri Apr 22 16:32:46 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-04-03 (18 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IpRoute:
   default via 192.168.3.1 dev wlp5s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp5s0 scope link metric 1000 
   192.168.3.0/24 dev wlp5s0 proto kernel scope link src 192.168.3.16 metric 600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 99.0+build2-0ubuntu0.20.04.2 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (0 days ago)
  dmi.bios.date: 07/08/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0807

[Desktop-packages] [Bug 1969910] Re: Firefox lost passwords, saved tabs, settings after upgrading to Ubuntu 22.04

2022-04-22 Thread TomaszChmielewski

The instructions helped, thanks a lot.

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

Title:
  Firefox lost passwords, saved tabs, settings after upgrading to Ubuntu
  22.04

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 22.04 from Ubuntu 21.10, Firefox lost its
  all passwords, saved tabs, settings.

  I'm using KDE on Wayland; before the upgrade, was using KDE on X.

  Very annoying issue and seriously breaks productivity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969910/+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 1784774] Re: snapd is not autofs aware and fails with nfs home dir

2022-04-22 Thread Andrew Conway

I never got it to work in 20.04, so I don't know whether your fix ever
made it in.

I have just installed Jammy Jellyfish (22.04), and can confirm snaps
don't work in it when using autofs and nfs mounted home directories.

The prior work around was just never use any snap applications, which
was OK as nothing important was in snaps prior to 22.04.

This is harder in 22.04 as firefox is distributed as a snap, and so
firefox doesn't work in 22.04 if you have autofs NFS home directories.

Work around is to use a different source for firefox,
https://ubuntuhandbook.org/index.php/2022/04/install-firefox-deb-
ubuntu-22-04/ but I don't know whether that will get security updates as
quickly, so this is a serious problem.

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

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

Title:
  snapd is not autofs aware and fails with nfs home dir

Status in snapd:
  Fix Released
Status in firefox package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Fix Released

Bug description:
  This is similar to bugs 1662552 and 1782873. In 1782873, jdstrand
  asked me to open a new bug for this specific issue.

  In 1662552, snapd fails for nfs mounted home directories as network
  permissions are not enabled. A work around was implemented that works
  if the mount is done via a /home mount at boot. However this does not
  work if people mount home directories via autofs. This is probably the
  fundamental problem for 1782873 although there may be other issues.

  [ Why use autofs? If some but not all of users want to use nfs homes.
  In particular, I have a local user on all my accounts that does not
  require the nfs server to be up or the kerberos server to be up, or
  kerberos working on the client machines, etc. It is very useful when
  something goes wrong. It means I mount /home/user rather than /home
  (for several users). ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1784774/+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 1969910] Re: Firefox lost passwords, saved tabs, settings after upgrading to Ubuntu 22.04

2022-04-22 Thread Olivier Tilloy

In Ubuntu 22.04, firefox was automatically transitioned to the snap
package, which is published by Mozilla.

The snap will attempt to import existing profiles if it was never run before. 
Could it be that you had installed/tried the firefox snap in the past, and thus 
had already an existing profile?
If so, deleting it and re-running the application should fix the problem:

rm -rf ~/snap/firefox
snap run firefox

If not, please attach the output of the following commands:

apt policy firefox

snap info firefox

snap connections firefox

Thanks!

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

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

Title:
  Firefox lost passwords, saved tabs, settings after upgrading to Ubuntu
  22.04

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 22.04 from Ubuntu 21.10, Firefox lost its
  all passwords, saved tabs, settings.

  I'm using KDE on Wayland; before the upgrade, was using KDE on X.

  Very annoying issue and seriously breaks productivity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969910/+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 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 enterprise wifi networks without CA_Certificate, like Eduroam

2022-04-22 Thread Ali Tolga Özbaş

22.04 stable version has been released yesterday, and it still doesn't
work on Ubuntu 22.04.

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

Title:
  Network manager cannot connect to WPA2/PEAP/MSCHAPv2 enterprise wifi
  networks without CA_Certificate, like Eduroam

Status in NetworkManager:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Triaged
Status in wpasupplicant package in Ubuntu:
  Triaged
Status in network-manager-applet source package in Trusty:
  Triaged
Status in wpasupplicant source package in Trusty:
  Triaged
Status in network-manager package in Debian:
  New
Status in Fedora:
  Fix Released
Status in Gentoo Linux:
  Fix Released
Status in network-manager package in openSUSE:
  Won't Fix

Bug description:
  HOW TO REPRODUCE:
  Connect to a MPA2/PEAP/MSCHAPv2 enterprise wifi network that doesn't use a CA 
Certificate, like Eduroam.

  RESULT:
  The computer doesn't connect, as the certificate verification fails.

  WORKAROUNDS:
  (http://askubuntu.com/questions/279762/cant-connect-to-wpa2-enterprise-peap)

  RELEASE NOTES TEXT:
  When connecting to MPA2/PEAP/MSCHAPv2 enterprise wifi networks that doesn't 
use a CA Certificate, like Eduroam, the connection fails 
(http://askubuntu.com/questions/279762/cant-connect-to-wpa2-enterprise-peap)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1104476/+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 1969934] [NEW] Update evolution-data-server to 3.44.1

2022-04-22 Thread Jeremy Bicha

Public bug reported:

Impact
--

Test Case
-

What Could Go Wrong
---

** Affects: evolution-data-server (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: jammy upgrade-software-version

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

Title:
  Update evolution-data-server to 3.44.1

Status in evolution-data-server package in Ubuntu:
  Triaged

Bug description:
  Impact
  --

  Test Case
  -

  What Could Go Wrong
  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1969934/+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 1850214] Re: gnome-shell crashed with SIGTRAP in g_logv("Settings schema 'org.gnome.desktop.privacy' does not contain a key named 'privacy-screen'") from glog() from g_settings

2022-04-22 Thread Treviño

Bah, recent mutter depends on newer gsettings schema, there's not really
much we can to avoid this.

Unless someone had wrong upgrades?

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

Title:
  gnome-shell crashed with SIGTRAP in g_logv("Settings schema
  'org.gnome.desktop.privacy' does not contain a key named 'privacy-
  screen'") from glog() from g_settings_schema_get_value() from
  g_settings_schema_get_value() from g_settings_schema_key_init() from
  g_settings_get_value() from g_settings_get_boolean()

Status in gnome-shell 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 
3.34.1-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/2b1107a85955c863c2829d7fe9671b0d20868308 
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/gnome-shell/+bug/1850214/+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

2022-04-22 Thread Jeremy Bicha

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

-- 
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 Released

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 1969925] [NEW] Save as Dialog from Firefox has save button greyed out if subfolder is opened

2022-04-22 Thread benste

Public bug reported:

Regression Bug

Steps to reproduce:

1. Download any Document and choose save as
2. pick a different folder than preselected
3. notice how the save button is active when clicking a folder (once)
4. double click to navigate into subfolder - notice how save icon is disabled

Expected behaviour - the file should be saved using the specified name
in that recently opened sub directory.

I've tried it with a PDF file, but i suspect this might be a bug...

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset wl nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 13:32:05 2022
GsettingsChanges:
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
 b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'initial-size' b'(1150, 540)'
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'278'
InstallationDate: Installed on 2018-09-15 (1314 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: nautilus
UpgradeStatus: Upgraded to jammy on 2022-04-22 (0 days ago)

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

Title:
  Save as Dialog from Firefox has save button greyed out if subfolder is
  opened

Status in nautilus package in Ubuntu:
  New

Bug description:
  Regression Bug

  Steps to reproduce:

  1. Download any Document and choose save as
  2. pick a different folder than preselected
  3. notice how the save button is active when clicking a folder (once)
  4. double click to navigate into subfolder - notice how save icon is disabled

  Expected behaviour - the file should be saved using the specified name
  in that recently opened sub directory.

  I've tried it with a PDF file, but i suspect this might be a bug...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset wl nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 13:32:05 2022
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1150, 540)'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'278'
  InstallationDate: Installed on 2018-09-15 (1314 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (0 days ago)

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

2022-04-22 Thread Matthew M. Dean

I'm still crashing with the exact same issue with 42.0-2ubuntu1. If i
blacklist amdgpu at boot time and use the Intel monitor there is no
crashing but obviously it isn't ideal.

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

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 1969622] Re: save file dialog doesn't allow saving to a directory without files

2022-04-22 Thread João Pedro Seara

Hello folks. Facing this issue as well, thank you very much for jumping
on it so quickly.

The workaround I found is to, instead of navigating to the inside of the
folder, just navigate to one level above, then click on the directory,
click on Save (this will make you enter the directory), and then click
on Save again.

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

Title:
  save file dialog doesn't allow saving to a directory without files

Status in GTK+:
  Unknown
Status in gtk4 package in Ubuntu:
  Fix Committed
Status in gtk4 source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  Ubuntu uses xdg-desktop-portal-gnome for the save dialog for snaps (like 
Firefox or Chromium). xdg-desktop-portal-gnome in Ubuntu 22.04 uses gtk4
  This issue also affects gnome-text-editor which uses gtk4 directly.

  Attempting to save a file to an empty folder won't work in many cases
  because the Save button is insensitive (unable to be clicked).

  Test Case
  -
  View this page with the Firefox or Chromium snaps.
  Press Ctrl+S to try to save this page.
  Navigate to a folder without any files in it. (It can have other folders in 
it.)
  The Save button should stay lit up.
  Save the file.

  Note that I wasn't able to reproduce the bug for bookmarked folders in
  the left sidebar so just navigate using the main view area.

  What Could Go Wrong
  
  This is a one-line bug fix from the stable gtk-4-6 branch targeted to 
directly fix this issue.

  Other Notes
  ---
  I do not believe we need to respin the Ubuntu 22.04 ISOs for this issue.
  I do request a 0-day SRU since this is a small high impact fix that affects 
the usability of the Firefox snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1969622/+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 1969118] Re: Certificate viewer shows extra bytes for RSA keys

2022-04-22 Thread Mikko Rantalainen

OK, I agree that this is not a security problem but UI issue only.

However, note that the UI says "Public key" and before that "Key
algorithm: RSA". As such, the public key should not have any extra bytes
at the start or at the end, just the public RSA 2048 bit key as is (as
desribed by "Key Algorithm" and "Key Size" fields immediately above).

Also note that the key displayed by gcr-viewer does not match key value
displayed by `openssl x509 -in ... -text`, Google Chrome, nor Firefox.
Is this also by design?

That said, I agree that gcr-viewer doesn't show the exponent separate
from the modulus either so maybe the easiest fix would be to change the
label "Public Key" to say "DER Encoded Public Key" to make it obvious
that user must decode the encoding of the key by themselves. When I'm
viewing PEM encoded key I sure didn't expect to see the public key as
DER encoded raw data.

A better fix would be to render modulus and exponent as separate fields
without any extra bytes. Of course, that would require different code
paths for e.g. RSA and x25519.

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

Title:
  Certificate viewer shows extra bytes for RSA keys

Status in gcr package in Ubuntu:
  Invalid

Bug description:
  When I view a x509 certificate using

  gcr-viewer .../path/to/certificate.pem

  and open the "Details" section and check the RSA public key
  information, the section that lists the public key renders extra 8
  bytes at the start and 5 bytes at the end which are not actually part
  of the key.

  I haven't tried if this happens with other file types except x509, or
  with encryption methods except RSA. The exact certificate I viewed can
  be downloaded from https://crt.sh/?d=6454583403 and the expected
  public key modulus should start with 00:b6:28:0b:44:... but the
  certificate viewer shows public key starting with bytes 30 82 01 0A 02
  82 01 01 00 B6 28 0B 44. Note the extra bytes 30 82 01 0A 02 82 01 01.
  The extra bytes seem to be static and do not change after re-lanching
  the viewer again. There are also extra bytes in the end of the
  displayed key.

  I'm marking this bug as a security vulnerability for now because

  (1) This tool is supposed to used to check encryption credentials, and
  (2) It's still unknown if this is some kind of 8 byte underflow/5 byte 
overflow or just a rendering problem. I'm not aware of the viewer writing extra 
bytes to any memory location so I would assume this is just a rendering issue.

  I'm fine with this issue being public so feel free to publish at your
  discretion.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gcr 3.28.0-1
  ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-lowlatency 5.4.174
  Uname: Linux 5.4.0-107-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Apr 14 15:47:18 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-01-05 (1194 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gcr
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1969118/+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 1969910] [NEW] Firefox lost passwords, saved tabs, settings after upgrading to Ubuntu 22.04

2022-04-22 Thread TomaszChmielewski

Public bug reported:

After upgrading to Ubuntu 22.04 from Ubuntu 21.10, Firefox lost its all
passwords, saved tabs, settings.

I'm using KDE on Wayland; before the upgrade, was using KDE on X.

Very annoying issue and seriously breaks productivity.

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

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

Title:
  Firefox lost passwords, saved tabs, settings after upgrading to Ubuntu
  22.04

Status in firefox package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 22.04 from Ubuntu 21.10, Firefox lost its
  all passwords, saved tabs, settings.

  I'm using KDE on Wayland; before the upgrade, was using KDE on X.

  Very annoying issue and seriously breaks productivity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969910/+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 1969622] Re: save file dialog doesn't allow saving to a directory without files

2022-04-22 Thread Brian Murray

Hello Jeremy, or anyone else affected,

Accepted gtk4 into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gtk4/4.6.2+ds-1ubuntu3
in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-jammy

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

Title:
  save file dialog doesn't allow saving to a directory without files

Status in GTK+:
  Unknown
Status in gtk4 package in Ubuntu:
  Fix Committed
Status in gtk4 source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  Ubuntu uses xdg-desktop-portal-gnome for the save dialog for snaps (like 
Firefox or Chromium). xdg-desktop-portal-gnome in Ubuntu 22.04 uses gtk4
  This issue also affects gnome-text-editor which uses gtk4 directly.

  Attempting to save a file to an empty folder won't work in many cases
  because the Save button is insensitive (unable to be clicked).

  Test Case
  -
  View this page with the Firefox or Chromium snaps.
  Press Ctrl+S to try to save this page.
  Navigate to a folder without any files in it. (It can have other folders in 
it.)
  The Save button should stay lit up.
  Save the file.

  Note that I wasn't able to reproduce the bug for bookmarked folders in
  the left sidebar so just navigate using the main view area.

  What Could Go Wrong
  
  This is a one-line bug fix from the stable gtk-4-6 branch targeted to 
directly fix this issue.

  Other Notes
  ---
  I do not believe we need to respin the Ubuntu 22.04 ISOs for this issue.
  I do request a 0-day SRU since this is a small high impact fix that affects 
the usability of the Firefox snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1969622/+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 1969815] Re: 22.04-machine rendered totally useless because of (portrait(?)) dual-screen (post-install)

2022-04-22 Thread Martin Wimpress 

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

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

** No longer affects: ubuntu-mate

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

Title:
  22.04-machine rendered totally useless because of (portrait(?)) dual-
  screen (post-install)

Status in marco package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower.
  Laptops went well as they are standard running wifi (note to self:
  next time upgrade one using a USB docking station+as many externally
  attached devices as possible should prove in a quite pleasurable end-
  user experience)

  For the tower: this is the dual-screen portrait system I have been
  opening up defects for months now. Same config too. Anyways, after I
  rebooted the overall booting process happened pretty well until TTY7
  tried kicking it and totally failed doing so hence rendered my system
  totally broken.

  The behavior of my screens is that they started blinking from blank to
  another type of blank for =<1 second each state. But during one of
  those states there seemed to be Wayland as I could just see the mouse
  cursor fly around when activated.

  Accessing other TTYs was also impossible as even though pressing
  CTRL+ALT+F2|F3|etc would indeed display a login prompt that within
  that same blinking instant that it had altered back to only that
  blinking cursor symbol(_) at the top-hand-left.

  That behavior held true for all TTYs.

  Pressing the power button did showed up the UM symbol alongside
  standard shutdown routine happened OK.

  Solution was: unplug one of the two monitor and automagically jammy's
  login screen popped up.

  If I replug that 2nd monitor while I am inside a working TTY7 session
  then the same (original) problem happens in which I cannot use any of
  the screens and when I re-unplug one of the two screens again I am re-
  back again at the jammy login having lost the current session that I
  had.

  Both of my screens are the same model and both use HDMI.

  I have attached my ~/.config/monitors.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1969815/+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 1969818] Re: Inconsistent Firefox screen resizing at session restore

2022-04-22 Thread Martin Wimpress 

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

** No longer affects: ubuntu-mate

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

Title:
  Inconsistent Firefox screen resizing at session restore

Status in firefox package in Ubuntu:
  New

Bug description:
  Prelude:
  I've have had this problem for MANY LTSes on both a Dell XPS13 laptop and 
tower and just now I can properly articulate it!1!

  Anyways see attached picture for those thousand words I cannot
  express.

  Context:
  So after my session relaunches(RE: bug #1969815) so does FF (as it's part of 
my start-up apps) but even though it's contour/top bar seems to fully take the 
whole space of the desktop as it should that it's content doesn't agree.

  Solution:
  Clicking on the Restore button will actually drag back the contour around the 
currently amount of content and then re-clicking on the same button (Which will 
now be labelled "Maximize window") will do it's function properly.

  PS:
  - I think that I have been having this problem only with Wayland;
  - No other software has given me such behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969818/+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 1969901] Re: network-manager fails to renew ipv6 address

2022-04-22 Thread Håkan Kvist

UPDATE, network-manager team applied this to the 1.10-trunk as well and it was 
included in:
1.10.8 (first tag)

See:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f

Unfortunately Ubuntu 18.04 includes a version that is slightly too old
to include this change: 1.10.6-2ubuntu1.1

** Description changed:

  We have experienced this issue on mixed ipv6/ipv4 corporate network on Ubuntu 
18.04.
  Unfortunately next LTS release is not yet an option for us.
  
  This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391
+ This was fixed in 1.12.0.
  
  Could you consider including the below patch on ubuntu 18.04?
  
  
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=17009ed91da8b3e0b10ee7e94d220be9bd3fa84c
  
  The patch can be applied with some adjustements on top of the version of
  network manager included in Bionic (pull-lp-source network-manager
  bionic). A function name has changed, changing the function name in the
  downloaded patch is enough to apply the patch.
  
  cat
  
../57ab9fd60fc9ec3ab7bc3fcef40b1f003d614162..17009ed91da8b3e0b10ee7e94d220be9bd3fa84c.patch
  |sed
  's|nm_dbus_object_clear_and_unexport|nm_exported_object_clear_and_unexport|g'
  > modified_patch.patch
  
  This has been tested on some devices and so far we have not seen any problems
  ipv4 only network (cable/wifi)
  ipv6/ipv4 mixed network (cable/wifi)

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

Title:
  network-manager fails to renew ipv6 address

Status in network-manager package in Ubuntu:
  New

Bug description:
  We have experienced this issue on mixed ipv6/ipv4 corporate network on Ubuntu 
18.04.
  Unfortunately next LTS release is not yet an option for us.

  This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391
  This was fixed in 1.12.0.

  Could you consider including the below patch on ubuntu 18.04?

  
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=17009ed91da8b3e0b10ee7e94d220be9bd3fa84c

  The patch can be applied with some adjustements on top of the version
  of network manager included in Bionic (pull-lp-source network-manager
  bionic). A function name has changed, changing the function name in
  the downloaded patch is enough to apply the patch.

  cat
  
../57ab9fd60fc9ec3ab7bc3fcef40b1f003d614162..17009ed91da8b3e0b10ee7e94d220be9bd3fa84c.patch
  |sed
  's|nm_dbus_object_clear_and_unexport|nm_exported_object_clear_and_unexport|g'
  > modified_patch.patch

  This has been tested on some devices and so far we have not seen any problems
  ipv4 only network (cable/wifi)
  ipv6/ipv4 mixed network (cable/wifi)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+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 1969637] Re: IBus lookup table appears bottom left of application (x11)

** Changed in: im-config (Debian)
   Status: Unknown => New

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

Title:
  IBus lookup table appears bottom left of application (x11)

Status in ibus:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New
Status in im-config package in Debian:
  New
Status in openSUSE:
  Unknown

Bug description:
  I know it is not im-config issue. I don't know what is root cause.

  how to reproduce:
  1. Install Ubuntu 22.04 LTS or apply newest update
  2. boot
  3. select a user
  4. select Ubuntu on Xorg
  5. input password
  6. login
  7. run gedit
  8. push Hankaku/Zenkaku key
  9. input any keys
  10. lookup table appears bottom left of application

  proposed fix:
  edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on 
/etc/default/im-config

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: im-config 0.50-2
  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: Thu Apr 21 00:13:10 2022
  InstallationDate: Installed on 2022-04-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  SourcePackage: im-config
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1969637/+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 1969901] [NEW] network-manager fails to renew ipv6 address

2022-04-22 Thread Håkan Kvist

Public bug reported:

We have experienced this issue on mixed ipv6/ipv4 corporate network on Ubuntu 
18.04.
Unfortunately next LTS release is not yet an option for us.

This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391

Could you consider including the below patch on ubuntu 18.04?

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=17009ed91da8b3e0b10ee7e94d220be9bd3fa84c

The patch can be applied with some adjustements on top of the version of
network manager included in Bionic (pull-lp-source network-manager
bionic). A function name has changed, changing the function name in the
downloaded patch is enough to apply the patch.

cat
../57ab9fd60fc9ec3ab7bc3fcef40b1f003d614162..17009ed91da8b3e0b10ee7e94d220be9bd3fa84c.patch
|sed
's|nm_dbus_object_clear_and_unexport|nm_exported_object_clear_and_unexport|g'
> modified_patch.patch

This has been tested on some devices and so far we have not seen any problems
ipv4 only network (cable/wifi)
ipv6/ipv4 mixed network (cable/wifi)

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  We have experienced this issue on mixed ipv6/ipv4 corporate network on Ubuntu 
18.04.
- Unfortunately next LTS release is not yet an option.
+ Unfortunately next LTS release is not yet an option for us.
  
  This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391
  
  Could you consider including the below patch on ubuntu 18.04?
  
  
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=17009ed91da8b3e0b10ee7e94d220be9bd3fa84c
  
- 
- The patch can be applied with some adjustements on top of the version of 
network manager included in Bionic (pull-lp-source network-manager bionic). A 
function name has changed, changing the function name in the downloaded patch 
is enough to apply the patch.
+ The patch can be applied with some adjustements on top of the version of
+ network manager included in Bionic (pull-lp-source network-manager
+ bionic). A function name has changed, changing the function name in the
+ downloaded patch is enough to apply the patch.
  
  cat
  
../57ab9fd60fc9ec3ab7bc3fcef40b1f003d614162..17009ed91da8b3e0b10ee7e94d220be9bd3fa84c.patch
  |sed
  's|nm_dbus_object_clear_and_unexport|nm_exported_object_clear_and_unexport|g'
  > modified_patch.patch
  
- 
  This has been tested on some devices and so far we have not seen any problems
  ipv4 only network (cable/wifi)
  ipv6/ipv4 mixed network (cable/wifi)

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

Title:
  network-manager fails to renew ipv6 address

Status in network-manager package in Ubuntu:
  New

Bug description:
  We have experienced this issue on mixed ipv6/ipv4 corporate network on Ubuntu 
18.04.
  Unfortunately next LTS release is not yet an option for us.

  This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391

  Could you consider including the below patch on ubuntu 18.04?

  
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=17009ed91da8b3e0b10ee7e94d220be9bd3fa84c

  The patch can be applied with some adjustements on top of the version
  of network manager included in Bionic (pull-lp-source network-manager
  bionic). A function name has changed, changing the function name in
  the downloaded patch is enough to apply the patch.

  cat
  
../57ab9fd60fc9ec3ab7bc3fcef40b1f003d614162..17009ed91da8b3e0b10ee7e94d220be9bd3fa84c.patch
  |sed
  's|nm_dbus_object_clear_and_unexport|nm_exported_object_clear_and_unexport|g'
  > modified_patch.patch

  This has been tested on some devices and so far we have not seen any problems
  ipv4 only network (cable/wifi)
  ipv6/ipv4 mixed network (cable/wifi)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+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 1969896] [NEW] Evince Document Viewer(42.0) does not remember last page in 22.04

2022-04-22 Thread bg

Public bug reported:

Just switched from Ubuntu 20.04 to 22.04 and realized that Document
Viewer no longer open on the last viewed page and doesn't remember the
side pane preference even after using the "Save Current Settings as
Default" option. Kindly advise

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 42.1-3
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-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 15:58:50 2022
InstallationDate: Installed on 2022-03-19 (34 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

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

Title:
  Evince Document Viewer(42.0) does not remember last page in 22.04

Status in evince package in Ubuntu:
  New

Bug description:
  Just switched from Ubuntu 20.04 to 22.04 and realized that Document
  Viewer no longer open on the last viewed page and doesn't remember the
  side pane preference even after using the "Save Current Settings as
  Default" option. Kindly advise

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.1-3
  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-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:58:50 2022
  InstallationDate: Installed on 2022-03-19 (34 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-04-22 Thread nfalse

I use the following method to bypass this bug，
1. create openssl.cnf for wpa_supplicant
- sudo cp /etc/ssl/openssl.cnf /etc/wpa_supplicant/
- motify /etc/wpa_supplicant/openssl.cnf
*** /etc/ssl/openssl.cnfFri Apr 22 14:54:42 2022
--- /etc/wpa_supplicant/openssl.cnf Fri Apr 22 14:55:22 2022
***
*** 52,57 
--- 52,64 
   
  [openssl_init]
  providers = provider_sect
+ ssl_conf = ssl_sect
+   
+ [ssl_sect]
+ system_default = system_default_sect
+   
+ [system_default_sect]
+ Options = UnsafeLegacyRenegotiation

  # List of providers to load
2. modify /usr/lib/systemd/system/wpa_supplicant.service
***
*** 8,13 
--- 8,14 
  [Service]
  Type=dbus
  BusName=fi.w1.wpa_supplicant1
+ Environment="OPENSSL_CONF=/etc/wpa_supplicant/openssl.cnf"
  ExecStart=/sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
  ExecReload=/bin/kill -HUP $MAINPID
3. restart wpa_supplicant
sudo systemctl daemon-reload
sudo systemctl restart wpa_supplicant.service

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

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

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])

Bug 1964037 mentions a similar stack trace so maybe that was the problem
all along.

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

Title:
  gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access
  memory at address [in stack])

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Desktop has some issues but it was not showable

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu1
  Uname: Linux 5.16.12-051612-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  7 12:12:08 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-04 (4 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f0d7aec5a7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 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/gnome-shell/+bug/1964120/+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(

Maybe it was a side effect of bug 1964037 / bug 1959888.

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

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(

It appears the crash reports suddenly stopped happening around 14 April.
Certainly the last affected version of gnome-shell is 42.0-1ubuntu1, but
that was replaced by 42.0-2ubuntu1 around 13 April.

So fixed already?

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

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

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

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 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error

2022-04-22 Thread Robin Sheat

https://github.com/NVIDIA/egl-wayland/issues/41#issuecomment-959550980

and

https://bugs.launchpad.net/egl-wayland/+bug/1968488

look related.

** Bug watch added: github.com/NVIDIA/egl-wayland/issues #41
   https://github.com/NVIDIA/egl-wayland/issues/41

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

Title:
  Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush
  Wayland connection | Gdk-Message: Error flushing display: Protocol
  error

Status in totem package in Ubuntu:
  New

Bug description:
  If I launch totem, it crashes pretty much immediately. I resolved this
  by deleting .config/totem. I had moved some video files that had been
  previously opened within it recently, so possibly it was trying to
  reference them (for thumbnails or whatever) and that broke it.

  robin@malik:~$ totem

  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush
  Wayland connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  
  (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland 
connection

  Gdk-Message: 18:00:17.844: Error flushing display: Protocol error
  robin@malik:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 18:00:39 2022
  InstallationDate: Installed on 2022-03-23 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+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 1969891] Re: Firefox snap can't be added to Dock favorites

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

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

Title:
  Firefox snap can't be added to Dock favorites

Status in firefox package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading from 21.10 to 22.04 the old Firefox was removed from
  my Dock favorites. I readded Firefox to my favorites which adds the
  Firefox icon to the favorites as expected.

  However, clicking on it will open the Firefox snap on the bottom of
  the Dock. So now I have 2 Firefox symbols in my Dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  Uname: Linux 5.17.0-4.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 08:49:32 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-05-31 (325 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969891/+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 1969266] Re: application windows frozen after screen blanking

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

Moving to bug 1969893 to make tracking clearer.

** This bug has been marked a duplicate of bug 1969893
   gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: 
window is null" from windowManager.js:1543:9

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

Title:
  application windows frozen after screen blanking

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

Bug description:
  When I want to use my computer after the screen has blanked, I often
  (about half of the time) find that the open applications are frozen.

  I can bring them back to life by restarting X or by cycling through
  the windows (ALT + TAB). Not a major bug certainly annoying as it is
  happening time and again.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 16 09:53:51 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-27 (19 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  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/gnome-shell/+bug/1969266/+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 1969893] Re: gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from windowManager.js:1543:9

Various crash reports as well as the upstream bug all suggest this is
Xorg-specific.

** Summary changed:

- gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: 
window is null" from windowManager.js:1543:9
+ gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: 
window is null" from _destroyWindow() [windowManager.js:1543:9]

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

Title:
  gnome-shell crashes with SIGSEGV just after logging "JS ERROR:
  TypeError: window is null" from _destroyWindow()
  [windowManager.js:1543:9]

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

Bug description:
  gnome-shell crashes with SIGSEGV just after logging:

  gnome-shell[3117]: JS ERROR: TypeError: window is null
  _destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9
  _initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16

  Examples:

  https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206
  https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206

  Tracking in:

  https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470
  ^^^ this is the second most common gnome-shell crash on errors.ubuntu.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1969893/+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 1969893] [NEW] gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9]

Public bug reported:

gnome-shell crashes with SIGSEGV just after logging:

gnome-shell[3117]: JS ERROR: TypeError: window is null
_destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9
_initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16

Examples:

https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206
https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206

Tracking in:

https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470
^^^ this is the second most common gnome-shell crash on errors.ubuntu.com

** Affects: gnome-shell
 Importance: Unknown
 Status: Unknown

** Affects: gnome-shell (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: jammy

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5330
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5330

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

** Tags added: jammy

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

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

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

Title:
  gnome-shell crashes with SIGSEGV just after logging "JS ERROR:
  TypeError: window is null" from _destroyWindow()
  [windowManager.js:1543:9]

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

Bug description:
  gnome-shell crashes with SIGSEGV just after logging:

  gnome-shell[3117]: JS ERROR: TypeError: window is null
  _destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9
  _initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16

  Examples:

  https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206
  https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206

  Tracking in:

  https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470
  ^^^ this is the second most common gnome-shell crash on errors.ubuntu.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1969893/+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 1850214] Re: gnome-shell crashed with SIGTRAP in g_logv("Settings schema 'org.gnome.desktop.privacy' does not contain a key named 'privacy-screen'") from glog() from g_settings

This looks like a catch-all bug where errors.ubuntu.com will bunch
unrelated crashes together because they have similar stack traces.

** Summary changed:

- gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from 
g_settings_schema_get_value() from g_settings_schema_key_init() from 
g_settings_get_value() from g_settings_get_boolean()
+ gnome-shell crashed with SIGTRAP in g_logv("Settings schema 
'org.gnome.desktop.privacy' does not contain a key named 'privacy-screen'") 
from glog() from g_settings_schema_get_value() from 
g_settings_schema_get_value() from g_settings_schema_key_init() from 
g_settings_get_value() from g_settings_get_boolean()

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

** Tags removed: eoan
** Tags added: jammy

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

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

Title:
  gnome-shell crashed with SIGTRAP in g_logv("Settings schema
  'org.gnome.desktop.privacy' does not contain a key named 'privacy-
  screen'") from glog() from g_settings_schema_get_value() from
  g_settings_schema_get_value() from g_settings_schema_key_init() from
  g_settings_get_value() from g_settings_get_boolean()

Status in gnome-shell 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 
3.34.1-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/2b1107a85955c863c2829d7fe9671b0d20868308 
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/gnome-shell/+bug/1850214/+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 1969890] [NEW] gnome-shell crashed with SIGTRAP in g_logv("Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-disable-extension'") from g_log() f

2022-04-22 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-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/2dd89d294fbe1add571e26db469810de64adb765 
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: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal groovy hirsute impish 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/1969890

Title:
  gnome-shell crashed with SIGTRAP in g_logv("Settings schema
  'org.gnome.mutter.wayland' does not contain a key named 'xwayland-
  disable-extension'") from g_log() from g_settings_schema_get_value()
  from g_settings_schema_get_value() from g_settings_schema_key_init()
  from g_settings_get_flags() from update_xwayland_disable_extensions()

Status in gnome-shell package in Ubuntu:
  New

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-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/2dd89d294fbe1add571e26db469810de64adb765 
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/gnome-shell/+bug/1969890/+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 1969890] Re: gnome-shell crashed with SIGTRAP in g_logv("Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-disable-extension'") from g_log() fro

This looks like a catch-all bug where errors.ubuntu.com will bunch
unrelated crashes together because they have similar stack traces.

** Summary changed:

- 
/usr/bin/gnome-shell:5:g_settings_schema_get_value:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_flags:update_xwayland_disable_extensions
+ gnome-shell crashed with SIGTRAP in g_logv("Settings schema 
'org.gnome.mutter.wayland' does not contain a key named 
'xwayland-disable-extension'") from g_log() from g_settings_schema_get_value() 
from g_settings_schema_get_value() from g_settings_schema_key_init() from 
g_settings_get_flags() from update_xwayland_disable_extensions()

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

Title:
  gnome-shell crashed with SIGTRAP in g_logv("Settings schema
  'org.gnome.mutter.wayland' does not contain a key named 'xwayland-
  disable-extension'") from g_log() from g_settings_schema_get_value()
  from g_settings_schema_get_value() from g_settings_schema_key_init()
  from g_settings_get_flags() from update_xwayland_disable_extensions()

Status in gnome-shell package in Ubuntu:
  New

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-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/2dd89d294fbe1add571e26db469810de64adb765 
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/gnome-shell/+bug/1969890/+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 1969891] [NEW] Firefox snap can't be added to Dock favorites

2022-04-22 Thread infowerk

Public bug reported:

After upgrading from 21.10 to 22.04 the old Firefox was removed from my
Dock favorites. I readded Firefox to my favorites which adds the Firefox
icon to the favorites as expected.

However, clicking on it will open the Firefox snap on the bottom of the
Dock. So now I have 2 Firefox symbols in my Dock.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
Uname: Linux 5.17.0-4.1-liquorix-amd64 x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 08:49:32 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2021-05-31 (325 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

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


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

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

Title:
  Firefox snap can't be added to Dock favorites

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading from 21.10 to 22.04 the old Firefox was removed from
  my Dock favorites. I readded Firefox to my favorites which adds the
  Firefox icon to the favorites as expected.

  However, clicking on it will open the Firefox snap on the bottom of
  the Dock. So now I have 2 Firefox symbols in my Dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  Uname: Linux 5.17.0-4.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 08:49:32 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-05-31 (325 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969891/+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 1927940] Re: [LINCPLUS P1, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all