[Desktop-packages] [Bug 2002061] Re: package texlive-latex-extra 2022.20220722-2 failed to install/upgrade: 该软件包现在的状态极为不妥； 建议您在卸载它之前再重新安装一次

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  package texlive-latex-extra 2022.20220722-2 failed to install/upgrade:
  该软件包现在的状态极为不妥； 建议您在卸载它之前再重新安装一次

Status in texlive-extra package in Ubuntu:
  New

Bug description:
  有 1 个软件包没有被完全安装或卸载。
  需要下载 0 B/14.3 MB 的归档。
  解压缩后会消耗 0 B 的额外空间。

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: texlive-latex-extra 2022.20220722-2
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Jan  5 18:44:39 2023
  DpkgTerminalLog:
   dpkg: 处理软件包 texlive-latex-extra (--remove)时出错：
该软件包现在的状态极为不妥；
   建议您在卸载它之前再重新安装一次
   dpkg: 出现过多错误，正在停止
  ErrorMessage: 该软件包现在的状态极为不妥； 建议您在卸载它之前再重新安装一次
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: texlive-extra
  Title: package texlive-latex-extra 2022.20220722-2 failed to install/upgrade: 
该软件包现在的状态极为不妥； 建议您在卸载它之前再重新安装一次
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/2002061/+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 2001922] Re: Xorg crash

[Daniel van Vugt]

Please tell us the contents of /var/crash/_usr_lib_xorg_Xorg.0.uploaded
as it will contain the unique ID of the Xorg crash.

** Tags added: amdgpu

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu 22.04.1 LTS installation crashes, but I was not able to
  figure out how to reproducibly trigger the crash. The last time it
  happened was with firefox and zoom running, the display suddenly went
  black and after a few seconds the X login screen appeared, my session
  gone.

  There are files in /var/crash/

  -rw-r--r-- 1 root whoopsie0 Jan  5 14:09 
_usr_lib_xorg_Xorg.0.upload
  -rw-r- 1 root whoopsie 12792518 Jan  5 14:09 
_usr_lib_xorg_Xorg.0.crash
  -rw--- 1 whoopsie whoopsie   37 Jan  5 14:09 
_usr_lib_xorg_Xorg.0.uploaded
  -rw-r--r-- 1 petr whoopsie0 Jan  5 14:13 
_usr_bin_xfsettingsd.1000.upload
  -rw-r- 1 petr whoopsie   516897 Jan  5 14:13 
_usr_bin_xfsettingsd.1000.crash
  -rw--- 1 whoopsie whoopsie   37 Jan  5 14:13 
_usr_bin_xfsettingsd.1000.uploaded
  -rw-r--r-- 1 petr whoopsie0 Jan  5 14:13 
_opt_zoom_zoom.1000.upload
  -rw-r- 1 petr whoopsie 46590288 Jan  5 14:13 _opt_zoom_zoom.1000.crash
  -rw--- 1 whoopsie whoopsie   37 Jan  5 14:13 
_opt_zoom_zoom.1000.uploaded

  
  and .xsession-errors.old ends with

  (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 
0x649, atom "_NET_WM_STATE_STAYS_ON_TOP")
  (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0
  Exiting due to channel error.
  Failed to parse arguments: Cannot open display: :0.0
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open 
display.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0
  Failed to parse arguments: Cannot open display: :0.0
  (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0
  (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0
  Failed to parse arguments: Cannot open display: :0.0
  (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0
  Failed to parse arguments: Cannot open display: :0.0
  Failed to parse arguments: Cannot open display: :0.0
  Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"
  Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"
  Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"
  Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"

  Is it safe and useful to upload the files from /var/crash/?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Jan  5 14:17:42 2023
  DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:3f96]
  InstallationDate: Installed on 2021-11-07 (424 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20YA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic 
root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago)
  dmi.bios.date: 09/23/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMCN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: ThinkBook 13s G3 ACN
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 

[Desktop-packages] [Bug 1783689] Re: [Dell XPS 15 9560] No sound from speakers

[Daniel van Vugt]

Zero speaker_outs sounds like the issue:

[4.273272] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3266: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[4.273274] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[4.273276] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[4.273277] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[4.273278] snd_hda_codec_realtek hdaudioC0D0:inputs:
[4.273280] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x18
[4.273282] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
[4.273283] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

** Summary changed:

- [HDA-Intel - HDA Intel PCH, playback] No sound at all
+ [Dell XPS 15 9560] No sound from speakers

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

** Tags added: jammy kinetic

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

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

Title:
  [Dell XPS 15 9560] No sound from speakers

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Speakers work from windows partition. Hear sounds when ubuntu log in
  page comes up. Once logged in cannot hear sound using alsa or
  pulseaudio. No reports of speaker problems or app complaints

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jon1974 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 25 22:26:23 2018
  InstallationDate: Installed on 2018-01-05 (201 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jon1974 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1783689/+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 2001914] Re: The gpu hangs and is not possible to work with GPU-envioronment

[Daniel van Vugt]

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

Sounds close enough to bug 1998950 that I think we should track it
there.

** This bug has been marked a duplicate of bug 1998950
   GPU hang on Alder Lake laptop

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

Title:
  The gpu hangs and is not possible to work with GPU-envioronment

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I open the terminal or just browsing, gnom sometimes freezes for
  a second, but sometimes  restart the machine is necessary. The log is:

  Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm]i915 :00:02.0: 
[drm] GPU HANG: ecode 12:0:
  Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] Resetting chip for 
stopped heartbeat on rcs0
  Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled
  Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC SLPC: enabled
  Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes
  Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 
last_user_time (2748010) is greater than comparison timestamp (2743419).  This 
most likely represents a buggy client sending inaccurate timestamps in messages 
such as _NET_ACTIVE_WINDOW.  Trying to work around...
  Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c 
appears to be one of the offending windows with a timestamp of 2748010.  
Working around...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  5 12:25:49 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-02 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  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/2001914/+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 1668317] Re: PCI/internal sound card not detected

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1783689
   [HDA-Intel - HDA Intel PCH, playback] No sound at all

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.1 on Dell XPS15 9650 dose not have sound after installing
  Graphics Drivers Nvidia375.39

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Feb 27 16:03:02 2017
  InstallationDate: Installed on 2017-02-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1668317/+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 1965750] Re: [jammy regression] No sound from onboard audio (playback / record)

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1783689
   [Dell XPS 15 9560] No sound from speakers

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

Title:
  [jammy regression] No sound from onboard audio (playback / record)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After updates I applied last friday, my onboard audio has ceased to
  function. No audio comes out the laptop speakers and no audio goes in
  the internal microphone (built in audio).

  If I connect my bluetooth headset (Bose NC700) the audio works, but
  only ever in mono. I cannot switch to the A2DP sink, it stays on HPF
  mono.

  I tried switching from pulseaudio to pipewire and pipewire-pulse, and
  I kind of made it work - the bluetooth headset works correctly, and
  the onboard audio works again after switching default inputs and
  outputs a number of times.

  I just want to stress my laptop's audio has worked fine for years in
  all versions of ubuntu including Jammy, but only up until Friday Jan
  the 18th 2022.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Mon Mar 21 11:48:25 2022
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (20 days ago)
  dmi.bios.date: 11/17/2019
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965750/+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 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound

[Daniel van Vugt]

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

Tracking in bug 1783689.

** This bug has been marked a duplicate of bug 1783689
   [Dell XPS 15 9560] No sound from speakers

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

Title:
  [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers
  but no sound

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Every now and then, after boot, I get no sounds at all coming from the
  speakers. Everything seems normal - the control center reports the
  output as active, and if I play anything with sound I can see the VU
  meter going back and forth. I've attached a screenshot showing as
  much.

  The internal microphone does not pick up any sounds either when this
  happens.

  If I connect my Bose NC700 bluetooth headset, I get sound out of it
  just fine, and the mike on it also works.

  Sometimes the internal sound will start working after a few times of
  switching back and forth internal audio / bluetooth headset.

  Restarting the systemd pipewire and pipewire-pulse user services
  doesn't help. Nor does killing & respawning wireplumber.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire-pulse 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: sway
  Date: Tue Jan  3 11:25:23 2023
  InstallationDate: Installed on 2023-01-03 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2000917/+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 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound

[Daniel van Vugt]

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

It looks like ALSA (the kernel) needs some tweaking because it is
reporting "speaker_outs=0"

Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0: 
autoconfig for ALC3266: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0:
speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0:
hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0:
mono: mono_out=0x0
Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0:
inputs:
Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0: 
 Headset Mic=0x18
Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0: 
 Headphone Mic=0x1a
Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0: 
 Internal Mic=0x12

** Summary changed:

- Pipewire correctly detects laptop sound & speakers but no sound
+ [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no 
sound

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

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

** No longer affects: pipewire (Ubuntu)

** Also affects: alsa-driver (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers
  but no sound

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Every now and then, after boot, I get no sounds at all coming from the
  speakers. Everything seems normal - the control center reports the
  output as active, and if I play anything with sound I can see the VU
  meter going back and forth. I've attached a screenshot showing as
  much.

  The internal microphone does not pick up any sounds either when this
  happens.

  If I connect my Bose NC700 bluetooth headset, I get sound out of it
  just fine, and the mike on it also works.

  Sometimes the internal sound will start working after a few times of
  switching back and forth internal audio / bluetooth headset.

  Restarting the systemd pipewire and pipewire-pulse user services
  doesn't help. Nor does killing & respawning wireplumber.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire-pulse 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: sway
  Date: Tue Jan  3 11:25:23 2023
  InstallationDate: Installed on 2023-01-03 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2000917/+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 2000835] Re: After resuming work, only the external screen works.

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1968040
   Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument 
invalide] [drmModeAtomicCommit: Invalid argument]

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

Title:
  After resuming work, only the external screen works.

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Work on two monitors - extended.
  After a certain period of time, the monitor automatically shuts down and 
locks the screen. Starting work turns on the external screen only. The built-in 
one is disabled. I can't see the window when entering the password. The only 
way is to switch to one monitor, then turn both back on. Sometimes the order of 
the displays is swapped (the main one becomes the external monitor)

  nvidia-driver-525 - current report
  nvidia-driver-525-open - not working

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-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  525.60.11  Wed Nov 23 
23:04:03 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  1 13:45:23 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   linux-apfs-rw/0+git20220214+ds-1, 5.15.0-53-generic, x86_64: installed
   linux-apfs-rw/0+git20220214+ds-1, 5.15.0-56-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] CoffeeLake-H GT2 [UHD Graphics 630] 
[1025:133a]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] TU117M [GeForce GTX 1650 Mobile / 
Max-Q] [1025:1337]
  InstallationDate: Installed on 2020-04-05 (1000 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Acer Aspire A715-74G
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vg_ubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2020
  dmi.bios.release: 1.29
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.29
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Pidgey_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.29
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.29:bd04/09/2020:br1.29:efr1.27:svnAcer:pnAspireA715-74G:pvrV1.29:rvnCFL:rnPidgey_CFS:rvrV1.29:cvnAcer:ct10:cvrV1.29:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-74G
  dmi.product.sku: 
  dmi.product.version: V1.29
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: 

[Desktop-packages] [Bug 1999213] Re: Xorg crashed with SIGSEGV in ActivateGrabNoDelivery() from ActivatePassiveGrab() from CheckPassiveGrabsOnWindow() from CheckDeviceGrabs() from ProcessDeviceEvent()

[Daniel van Vugt]

** Tags added: rls-jj-incoming

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

Title:
  Xorg crashed with SIGSEGV in ActivateGrabNoDelivery() from
  ActivatePassiveGrab() from CheckPassiveGrabsOnWindow() from
  CheckDeviceGrabs() from ProcessDeviceEvent()

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:21.1.3-2ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/4bdcf11799f043b0a08bfd0a926e3751257425e8 
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/xorg-server/+bug/1999213/+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 2000649] Re: Xorg crashes or freezes

[Daniel van Vugt]

We are unable to track or help with crashes originating from PPAs.
Please try the regular Ubuntu version of Xorg and tell us if that
crashes.

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

Title:
  Xorg crashes or freezes

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Occasionally, (I wasn't able to reproduce it) xorg just hangs or
  crashes to the log screen. It happens about every two weeks,
  especially if I don't reboot often (However doesn't matter much, I
  think, because it also happens on "fresh" boot).

  I use bspwm (version from the jammy repository), on Lubuntu 22.04.1
  (fresh install, not upgrade from 22.04, nor 20.04).

  Freezes occur when I switch between desktops, just hangs and that's
  it, no response to the keyboard, however mouse is usually usable and
  screen keeps updating.

  Crashes occur when I switch between windows or desktops (I use
  shortcuts for this), xorg just goes black and prints my shortcut to
  the screen; waits for a few secs and opens login screen.

  I don't know why it is happening, before 22.04 I was using 16.04 never
  had any problems.

  I tried google it, use some intel video card in /etc/X11/xorg.conf.d
  directory, but it makes system unusable at all, just type is super
  slow and I gave up experimenting with different flags ...

  I really hope you can tell me something, because this bug is really
  annoying, especially when I have a lot of windows open and I have to
  open them all again and again. Thank you in advance and have a nice
  day!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop:
   
  Date: Wed Dec 28 23:59:36 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:5062]
  InstallationDate: Installed on 2022-12-24 (3 days ago)
  InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HMS6XX00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2022
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET69W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HMS6XX00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HMS6XX00
  dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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-server/+bug/2000649/+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 1985089] Re: Resizing two edge tiled windows is laggy

[Daniel van Vugt]

** Tags added: fixed-in-mutter-42.8 fixed-in-mutter-43.3

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

Title:
  Resizing two edge tiled windows is laggy

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Just to report an issue that other people have reported to GNOME and
  in Reddit, that seems to also affect Ubuntu 22.04.

  If you snap 2 windows side-by-side in Wayland and then try to resize
  them, it's very slow and uses a lot of memory.

  Check here for more details:
  - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246
  - 
https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1985089/+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 1988859] Re: Periodic black frames and stutter [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)]

[Daniel van Vugt]

Likely (the proper) fix committed to mesa in:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20397


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

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

Title:
  Periodic black frames and stutter [Failed to post KMS update:
  drmModeAddFB does not support format 'AR24' (0x34325241)]

Status in Mesa:
  New
Status in Mutter:
  New
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Every so often, the desktop will go black and then re appear on Ubuntu
  22.10 Wayland Session which should not be occurring (this does not
  happen on 22.04.) Note that only the cursor can be seen.

  Reporting this before release so that it can be patched for (at least)
  the RasPi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8
  Uname: Linux 5.19.0-1001-raspi aarch64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 16:10:37 2022
  DisplayManager: gdm3
  ImageMediaBuild: 20220826
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1988859/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD

[Joshua Peisach]

Fix released for nautilus 1:43.0-1ubuntu2.1

nautilus (1:43.0-1ubuntu2.1) kinetic-security; urgency=medium

  * SECURITY UPDATE: crash via invalid zip file
- debian/patches/CVE-2022-37290.patch: fix crash when copying an
  invalid file in src/nautilus-dbus-manager.c,
  src/nautilus-file-operations.c.
- CVE-2022-37290

 -- Marc Deslauriers   Tue, 03 Jan 2023
12:27:45 -0500

** Changed in: nautilus (Ubuntu Kinetic)
   Status: New => Fix Released

** Changed in: nautilus (Ubuntu Lunar)
   Status: New => Fix Released

** Changed in: nautilus (Ubuntu Jammy)
   Status: New => Fix Released

** Changed in: nautilus (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  CVE-2022-37290: Pasted zip archive/invalid file causes NPD

Status in caja package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Fix Released
Status in nemo package in Ubuntu:
  Fix Committed
Status in caja source package in Focal:
  New
Status in nautilus source package in Focal:
  Fix Released
Status in nemo source package in Focal:
  New
Status in caja source package in Jammy:
  New
Status in nautilus source package in Jammy:
  Fix Released
Status in nemo source package in Jammy:
  New
Status in caja source package in Kinetic:
  New
Status in nautilus source package in Kinetic:
  Fix Released
Status in nemo source package in Kinetic:
  New
Status in caja source package in Lunar:
  New
Status in nautilus source package in Lunar:
  Fix Released
Status in nemo source package in Lunar:
  Fix Committed

Bug description:
  A bug for the triage/patching of CVE-2022-37290.

  In get_basename() and g_file_get_basename(), when the file name cannot
  be parsed, NULL is returned; Nautilus does not check this and this
  results in a NPD and a crash.

  The issue on GNOME GitLab explains this pretty well:
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376

  And the code in question is also in Nemo and Caja.

  History of the code: The faulty code was introduced in Nautilus 2.20,
  before Nemo and Caja were forked; these file managers have the same
  issue and same code in the function.

  The simplest POC I found was running this via DBus, which I'm not 100%
  sure if I've altered correctly for Nemo and Caja, but regardless for
  Nautilus this results in a crash.

  ```
  Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed
  Nov 27 20:38:32 Joshua-2210Test kernel: [  825.449866] pool-org.gnome.[5439]: 
segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in 
libglib-2.0.so.0.7400.0[7f3058c03000+8f000]
  Nov 27 20:38:32 Joshua-2210Test kernel: [  825.449878] Code: 0f 85 bc fe ff 
ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 
89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 
00 0f b6 42 01 48 8d
  ```

  Attached is the poc.py, made by Wu Chunming.

  ** Nemo **
  Upstream, version 5.6.0:
  (more advanced/verbose) upstream patch: 
https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005
  possible further problems: 
https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 27 20:41:20 2022
  GsettingsChanges:

  InstallationDate: Installed on 2022-09-18 (70 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 2000937] Re: DING settings values shown untranslated

[Gunnar Hjalmarsson]

@Sebastien: I figured it out. Actually you already fixed it for jammy,
but...

https://salsa.debian.org/gnome-team/gnome-control-
center/-/commit/1e46adfc

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: gnome-control-center (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  DING settings values shown untranslated

Status in Ubuntu Translations:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 22.10 ; Gnome 43.0

  Hello,
  There is a translation problem (missing?) in gnome-control-center.
  See image attached.
  Regards,
  Roxfr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/2000937/+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 1699942] Re: network-manager fails to deprecate addresses

[Nick Rosbrook]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu)
   Status: Won't Fix => Incomplete

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

Title:
  network-manager fails to deprecate addresses

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  network manager does not properly deprecate autoconfigured temporary IP 
addresses when ValidLifetime for a prefix is 0 in router advertisements. This 
behaviour is non-compliant with RFC 4861 § 6.3.4, which reads:
  If the prefix is already present in the host's Prefix List as
  the result of a previously received advertisement, reset its
  invalidation timer to the Valid Lifetime value in the Prefix
  Information option.  If the new Lifetime value is zero, time-out
  the prefix immediately.

  The hosts instead continued to use temporary addresses configured
  until they reached their timeout, rather than immediately dropping the
  addresses. It further appears that it is generating new temporary
  addresses when the previous ones expire, but I have not been
  monitoring hosts closely enough to tell for sure---I will update on
  this when I have further information.

  This problem was discovered on Ubuntu Studio 16.04.2; it is not
  present on Ubuntu Server (which uses Debian networking scripts).

  Additional Info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

[Bram Stolk]

My current theory is that we broke video input for non Intel platforms.

On my machine with AMD GPU, I get:

ERROR:gpu_memory_buffer_support_x11.cc(134)] Can't create buffer -- gbm
device is missing

$ inxi -G
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
driver: amdgpu v: kernel
  Device-2: Logitech QuickCam Vision Pro type: USB
driver: snd-usb-audio,uvcvideo
  Display: server: X.Org v: 1.22.1.3 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu
resolution: 3840x2160~120Hz
  OpenGL: renderer: llvmpipe (LLVM 13.0.1 256 bits) v: 4.5 Mesa 22.0.5

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

Title:
  Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  With the latest version of Chromium in the stable channel
  (108.0.5359.94), I can access the webcam and the microphone in Google
  Meet and Jitsi (using a framatalk.org instance).

  However, with version 107.0.5304.121-hwacc (from
  latest/candidate/hwacc branch), the same test does not work.

  The only difference between the two in `snap connections chromium` is

  content   chromium:va-driver-non-free -
  -

  Test:

  1. Install Chromium from the given channel
  2. Go to https://framatalk.org/ and click on "Create a room"
  3. Accept the permissions to access Microphone and Camera

  Expected result:

  Image from camera is displayed on screen

  Actual result:

  The webcam is turned on (the LED turns on), but no image is captured,
  and after a few seconds, an error message is displayed ("We are unable
  to access your camera").

  In the settings, I can see the camera name ("UVC Camera (046d:0802)").

  Attached are two logs:

  - One retrieved by launching Chromium with `chromium 
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a 
room".
  - One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


  Configuration information
  =

  - Desktop with AMD GPU RX580
  - Ubuntu 20.04 (kernel 5.15.0-56-generic)
  - Webcam: 046d:0802 Logitech, Inc. Webcam C200
  - Headset: 046d:0a38 Logitech, Inc. Headset H340

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+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 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

[Bram Stolk]

@ikepanhc Which GPU do you have? Intel, AMD or nVidia?

$ sudo apt install inxi
$ inxi -G

Thanks.

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

Title:
  Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  With the latest version of Chromium in the stable channel
  (108.0.5359.94), I can access the webcam and the microphone in Google
  Meet and Jitsi (using a framatalk.org instance).

  However, with version 107.0.5304.121-hwacc (from
  latest/candidate/hwacc branch), the same test does not work.

  The only difference between the two in `snap connections chromium` is

  content   chromium:va-driver-non-free -
  -

  Test:

  1. Install Chromium from the given channel
  2. Go to https://framatalk.org/ and click on "Create a room"
  3. Accept the permissions to access Microphone and Camera

  Expected result:

  Image from camera is displayed on screen

  Actual result:

  The webcam is turned on (the LED turns on), but no image is captured,
  and after a few seconds, an error message is displayed ("We are unable
  to access your camera").

  In the settings, I can see the camera name ("UVC Camera (046d:0802)").

  Attached are two logs:

  - One retrieved by launching Chromium with `chromium 
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a 
room".
  - One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


  Configuration information
  =

  - Desktop with AMD GPU RX580
  - Ubuntu 20.04 (kernel 5.15.0-56-generic)
  - Webcam: 046d:0802 Logitech, Inc. Webcam C200
  - Headset: 046d:0a38 Logitech, Inc. Headset H340

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+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 1995766] Re: X server segfault when starting youtube videos

[clepsdyrae]

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

Thanks -- great to know. Do you know if the fix will be brought into
22.04 ?

And thanks for the help on it.

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

Title:
  X server segfault when starting youtube videos

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

Bug description:
  This is an intermittent bug; happens perhaps 1-3 times a week. Always
  when just starting to play a youtube videos (I haven't seen it playing
  videos on other sites, or locally, but the sample size is skewed.) I'm
  using Nvidia drivers with a 6GB 1060 GTX running three monitors.
  Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around
  5 or 6% usage. System RAM is 16GB, also not stressed (10-15%).

  Stack trace in Xorg.0.log.old is always the same:

  [  1890.850] (EE) 
  [  1890.850] (EE) Backtrace:
  [  1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9]
  [  1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) 
[0x7f40d5da5520]
  [  1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) 
[0x558c41efb1e9]
  [  1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) 
[0x558c41efcc85]
  [  1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) 
[0x558c41efd183]
  [  1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) 
[0x558c41efe183]
  [  1890.853] (EE) 6: /usr/lib/xorg/Xorg 
(InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d]
  [  1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) 
[0x558c42006e4c]
  [  1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) 
[0x558c4121]
  [  1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) 
[0x558c4200011e]
  [  1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60]
  [  1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) 
[0x558c4205fee8]
  [  1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) 
[0x558c41ef0257]
  [  1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524]
  [  1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_init_first+0x90) [0x7f40d5d8cd90]
  [  1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0x80) [0x7f40d5d8ce40]
  [  1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5]
  [  1890.855] (EE) 
  [  1890.855] (EE) Segmentation fault at address 0x7ffec8965000
  [  1890.855] (EE) 
  Fatal server error:
  [  1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-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  470.141.03  Thu Jun 30 
18:45:31 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Nov  5 10:27:18 2022
  DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 
1060 6GB] [1462:3281]
  InstallationDate: Installed on 2020-04-27 (921 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=8M mtrr_chunk_size=32M quiet splash 
nomodeset vt.handoff=7
  

[Desktop-packages] [Bug 1985089] Re: Resizing two edge tiled windows is laggy

[xalt7x]

@vanvugt
As it was merged, can we expect this fix to land for 22.04?
Patches apply to Mutter 42.5 without issues.
I've just needed to slightly adapt an additional patch ("tiling: Remove 
unnecessary update_edge_constraints()") which needs to be applied after 
"tiling: Skip the resize effect for tiled windows during user grabs"


** Patch added: "tiling: Remove unnecessary update_edge_constraints()."
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1985089/+attachment/5639395/+files/tiling--02--Remove-unnecessary-update_edge_constraints--42.5.diff

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

Title:
  Resizing two edge tiled windows is laggy

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Just to report an issue that other people have reported to GNOME and
  in Reddit, that seems to also affect Ubuntu 22.04.

  If you snap 2 windows side-by-side in Wayland and then try to resize
  them, it's very slow and uses a lot of memory.

  Check here for more details:
  - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246
  - 
https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1985089/+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 2000649] Re: Xorg crashes or freezes

[andrey]

Hi! Thank you for taking your time investigating this issue! I don't
really know, what you meant in 2), but here is the link with my ID
pasted:
https://errors.ubuntu.com/user/1757d7b8546457ecd92b2fa0f587fd8a5833d146a4408883990f1450bc67160d0e631ce4aaed7a0594917c05bf044ffcc90c3d5fe9db89d304988fc5f45f705e

About crashes there ... I don't think that's related to the issue. At
least, according to journalctl, it's not like some program causes the
xorg to crash. It's more like, I am working and everything is good and
then I switch windows or desktops (I am using bspwm always, so I don't
really know if that's even the bug of xserver or bspwm).

I have one crash file of conky in /var/crash, but again it happened
__after__ xorg server died (according to journalctl). I did what you
said, although I don't think that's the problem. Here is the id of the
bug: e62b4bd4-8d29-11ed-9cd9-fa163e993415 (found in file uploaded, if
that's what you meant, because there wasn't any new bug generated on
this site)

One key note to mention here is that I use xserver from this PPA
https://launchpad.net/~nrbrtx/+archive/ubuntu/xorg-hotkeys, because
otherwise I have problems with using "ctrl + shift" in bspwm. Probably
it can be related.

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

Title:
  Xorg crashes or freezes

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Occasionally, (I wasn't able to reproduce it) xorg just hangs or
  crashes to the log screen. It happens about every two weeks,
  especially if I don't reboot often (However doesn't matter much, I
  think, because it also happens on "fresh" boot).

  I use bspwm (version from the jammy repository), on Lubuntu 22.04.1
  (fresh install, not upgrade from 22.04, nor 20.04).

  Freezes occur when I switch between desktops, just hangs and that's
  it, no response to the keyboard, however mouse is usually usable and
  screen keeps updating.

  Crashes occur when I switch between windows or desktops (I use
  shortcuts for this), xorg just goes black and prints my shortcut to
  the screen; waits for a few secs and opens login screen.

  I don't know why it is happening, before 22.04 I was using 16.04 never
  had any problems.

  I tried google it, use some intel video card in /etc/X11/xorg.conf.d
  directory, but it makes system unusable at all, just type is super
  slow and I gave up experimenting with different flags ...

  I really hope you can tell me something, because this bug is really
  annoying, especially when I have a lot of windows open and I have to
  open them all again and again. Thank you in advance and have a nice
  day!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop:
   
  Date: Wed Dec 28 23:59:36 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:5062]
  InstallationDate: Installed on 2022-12-24 (3 days ago)
  InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HMS6XX00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2022
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET69W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HMS6XX00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HMS6XX00
  dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  

[Desktop-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

[Gunnar Hjalmarsson]

I have accomplished the steps in the test plan:

* for jammy with language-selector-[common,gnome] 0.219.1

* for kinetic with language-selector-[common,gnome] 0.219.22.10.1

and can verify the expected improvement. (The kinetic verification was
made on Xubuntu 22.10 where fonts-noto-core is installed by default for
all users. The configuration tweak has the same effect on Xubuntu as on
Ubuntu, though.)

** Tags removed: verification-needed verification-needed-jammy 
verification-needed-kinetic
** Tags added: verification-done verification-done-jammy 
verification-done-kinetic

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

Title:
  [System Fonts] Replace default sinhala font from LKLUG to Noto

Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Won't Fix
Status in language-selector source package in Jammy:
  Fix Committed
Status in language-selector source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

  The current default font for Sinhala (LKLUG) is unmaintained and comes
  with issues. Noto offers Sinhala fonts with significantly higher
  quality.

  fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of
  changing that, the proposed change makes fontconfig give Noto Sans
  Sinhala respective Noto Serif Sinhala higher precedence than LKLUG,
  and that — together with installation of fonts-noto-core — seems to be
  sufficient to achieve the desired result.

  [ Test Plan ]

  * Install language-selector-[common,gnome] from
  [jammy,kinetic]-proposed.

  * Open Language Support and install the Sinhala language.

  * Open a terminal window and run this command:

    fc-match -a | grep -E 'LKLUG|Sinhala'

  * Confirm that Noto Sans Sinhala is listed before LKLUG.

  * Close Firefox and re-open it.

  * Visit e.g. https://si.wikipedia.org and confirm the
    improvement. (Also I (Gunnar), who don't speak Sinhala,
    notice a remarkable difference.)

  [ Where problems could occur ]

  No real problem in sight. Some Sinhala speaking users with fonts-noto-
  core installed will indeed see a surprise change when it starts to
  render Sinhala via Noto fonts instead of LKLUG. But that surprise
  ought to make them happy. :)

  Please note Robie Basak's warning about the changed font metrics in
  comment #7, though.

  [ Original description ]

  **What's the problem?**

  Currently ubuntu comes with LKLUG font for sinhala (si). it's not
  clear. e.g. we cannot recognize vowel signs and read websites using
  that font. We can change it manually but such changes do not apply to
  some applications or application types e.g. snap apps etc.

  LKLUG (last active: 2012) no one maintain it now.
  https://web.archive.org/web/202200*/http://www.lug.lk/
  http://www.lug.lk/fonts/lklug

  **What expected to happen?**

  We would like to see Noto serif sinhala as the default font for sinhala 
language
  https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala
  [Highlighs: clear (readable), thin, takes less space than sans sinhala]

  If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala 
https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala
  [Highlighs: clear (readable), thick, takes more space than serif sinhala]

  **Additional details**

  Screenshots (see the difference: LKLUG/Noto)

  LKLUG
  https://i.ibb.co/nbHM5Mw/lklug.jpg

  Noto Sinhala
  https://i.ibb.co/k9dbtYb/noto.jpg

  If you need more examples or clarifications, please add a comment

  Random posts
  1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g
  2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with 
some apps)
  3. 
https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/

  Also, some developers already have designed tools, scripts for that problem 
however many people do not try to find these scripts and switch to other OS
  1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache)
  2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79
  3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer

  Please review details, screenshots and posts. This is not a personal
  opinion and atleast, i expect to see this change in the next interim
  or LTS release.

  Furthermore, please let me know if i can help to speed-up this
  replacement process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2000551/+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 2000551] Please test proposed package

[Robie Basak]

Hello Aurora, or anyone else affected,

Accepted language-selector into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/language-
selector/0.219.1 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.

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

Title:
  [System Fonts] Replace default sinhala font from LKLUG to Noto

Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Won't Fix
Status in language-selector source package in Jammy:
  Fix Committed
Status in language-selector source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

  The current default font for Sinhala (LKLUG) is unmaintained and comes
  with issues. Noto offers Sinhala fonts with significantly higher
  quality.

  fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of
  changing that, the proposed change makes fontconfig give Noto Sans
  Sinhala respective Noto Serif Sinhala higher precedence than LKLUG,
  and that — together with installation of fonts-noto-core — seems to be
  sufficient to achieve the desired result.

  [ Test Plan ]

  * Install language-selector-[common,gnome] from
  [jammy,kinetic]-proposed.

  * Open Language Support and install the Sinhala language.

  * Open a terminal window and run this command:

    fc-match -a | grep -E 'LKLUG|Sinhala'

  * Confirm that Noto Sans Sinhala is listed before LKLUG.

  * Close Firefox and re-open it.

  * Visit e.g. https://si.wikipedia.org and confirm the
    improvement. (Also I (Gunnar), who don't speak Sinhala,
    notice a remarkable difference.)

  [ Where problems could occur ]

  No real problem in sight. Some Sinhala speaking users with fonts-noto-
  core installed will indeed see a surprise change when it starts to
  render Sinhala via Noto fonts instead of LKLUG. But that surprise
  ought to make them happy. :)

  Please note Robie Basak's warning about the changed font metrics in
  comment #7, though.

  [ Original description ]

  **What's the problem?**

  Currently ubuntu comes with LKLUG font for sinhala (si). it's not
  clear. e.g. we cannot recognize vowel signs and read websites using
  that font. We can change it manually but such changes do not apply to
  some applications or application types e.g. snap apps etc.

  LKLUG (last active: 2012) no one maintain it now.
  https://web.archive.org/web/202200*/http://www.lug.lk/
  http://www.lug.lk/fonts/lklug

  **What expected to happen?**

  We would like to see Noto serif sinhala as the default font for sinhala 
language
  https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala
  [Highlighs: clear (readable), thin, takes less space than sans sinhala]

  If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala 
https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala
  [Highlighs: clear (readable), thick, takes more space than serif sinhala]

  **Additional details**

  Screenshots (see the difference: LKLUG/Noto)

  LKLUG
  https://i.ibb.co/nbHM5Mw/lklug.jpg

  Noto Sinhala
  https://i.ibb.co/k9dbtYb/noto.jpg

  If you need more examples or clarifications, please add a comment

  Random posts
  1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g
  2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with 
some apps)
  3. 
https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/

  Also, some developers already have designed tools, scripts for that problem 
however many people do not try to find these scripts and switch to other OS
  1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache)
  2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79
  3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer

  Please review 

[Desktop-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

[Robie Basak]

Hello Aurora, or anyone else affected,

Accepted language-selector into kinetic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/language-
selector/0.219.22.10.1 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-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. 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: language-selector (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-kinetic

** Changed in: language-selector (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  [System Fonts] Replace default sinhala font from LKLUG to Noto

Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Won't Fix
Status in language-selector source package in Jammy:
  Fix Committed
Status in language-selector source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

  The current default font for Sinhala (LKLUG) is unmaintained and comes
  with issues. Noto offers Sinhala fonts with significantly higher
  quality.

  fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of
  changing that, the proposed change makes fontconfig give Noto Sans
  Sinhala respective Noto Serif Sinhala higher precedence than LKLUG,
  and that — together with installation of fonts-noto-core — seems to be
  sufficient to achieve the desired result.

  [ Test Plan ]

  * Install language-selector-[common,gnome] from
  [jammy,kinetic]-proposed.

  * Open Language Support and install the Sinhala language.

  * Open a terminal window and run this command:

    fc-match -a | grep -E 'LKLUG|Sinhala'

  * Confirm that Noto Sans Sinhala is listed before LKLUG.

  * Close Firefox and re-open it.

  * Visit e.g. https://si.wikipedia.org and confirm the
    improvement. (Also I (Gunnar), who don't speak Sinhala,
    notice a remarkable difference.)

  [ Where problems could occur ]

  No real problem in sight. Some Sinhala speaking users with fonts-noto-
  core installed will indeed see a surprise change when it starts to
  render Sinhala via Noto fonts instead of LKLUG. But that surprise
  ought to make them happy. :)

  Please note Robie Basak's warning about the changed font metrics in
  comment #7, though.

  [ Original description ]

  **What's the problem?**

  Currently ubuntu comes with LKLUG font for sinhala (si). it's not
  clear. e.g. we cannot recognize vowel signs and read websites using
  that font. We can change it manually but such changes do not apply to
  some applications or application types e.g. snap apps etc.

  LKLUG (last active: 2012) no one maintain it now.
  https://web.archive.org/web/202200*/http://www.lug.lk/
  http://www.lug.lk/fonts/lklug

  **What expected to happen?**

  We would like to see Noto serif sinhala as the default font for sinhala 
language
  https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala
  [Highlighs: clear (readable), thin, takes less space than sans sinhala]

  If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala 
https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala
  [Highlighs: clear (readable), thick, takes more space than serif sinhala]

  **Additional details**

  Screenshots (see the difference: LKLUG/Noto)

  LKLUG
  https://i.ibb.co/nbHM5Mw/lklug.jpg

  Noto Sinhala
  https://i.ibb.co/k9dbtYb/noto.jpg

  If you need more examples or clarifications, please add a comment

  Random posts
  1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g
  2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with 
some apps)
  3. 
https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/

  Also, some developers already have designed tools, scripts for that problem 
however many 

[Desktop-packages] [Bug 1971712] Re: Add support for Intel DG2

[Sebastian Heiden]

It seems like there is no more force-probe required for oem-6.1, works
fine out-of-the-box now.

When is the 22.2 mesa from ppa:canonical-x/x-staging going to be
released, currently using the linux-oem-6.1 kernel together with the
23.0 mesa from the Intel Arc package sources.

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

Title:
  Add support for Intel DG2

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
  firmare: updates to i915 DMC, GuC

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 2000835] Re: After resuming work, only the external screen works.

[Adrian Feliks]

I am attaching the logs.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000835/+attachment/5639364/+files/journal.txt

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

Title:
  After resuming work, only the external screen works.

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Work on two monitors - extended.
  After a certain period of time, the monitor automatically shuts down and 
locks the screen. Starting work turns on the external screen only. The built-in 
one is disabled. I can't see the window when entering the password. The only 
way is to switch to one monitor, then turn both back on. Sometimes the order of 
the displays is swapped (the main one becomes the external monitor)

  nvidia-driver-525 - current report
  nvidia-driver-525-open - not working

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-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  525.60.11  Wed Nov 23 
23:04:03 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  1 13:45:23 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   linux-apfs-rw/0+git20220214+ds-1, 5.15.0-53-generic, x86_64: installed
   linux-apfs-rw/0+git20220214+ds-1, 5.15.0-56-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] CoffeeLake-H GT2 [UHD Graphics 630] 
[1025:133a]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] TU117M [GeForce GTX 1650 Mobile / 
Max-Q] [1025:1337]
  InstallationDate: Installed on 2020-04-05 (1000 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Acer Aspire A715-74G
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vg_ubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2020
  dmi.bios.release: 1.29
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.29
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Pidgey_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.29
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.29:bd04/09/2020:br1.29:efr1.27:svnAcer:pnAspireA715-74G:pvrV1.29:rvnCFL:rnPidgey_CFS:rvrV1.29:cvnAcer:ct10:cvrV1.29:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-74G
  dmi.product.sku: 
  dmi.product.version: V1.29
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/mutter/+bug/2000835/+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 1971712] Re: Add support for Intel DG2

[Timo Aaltonen]

oem-6.1 is now in jammy-proposed

** Package changed: linux-oem-6.0 (Ubuntu) => linux-oem-6.1 (Ubuntu)

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

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

Title:
  Add support for Intel DG2

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
  firmare: updates to i915 DMC, GuC

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 2001971] [NEW] Slow execution during boot and log contains many errors

[Islam]

Public bug reported:

The service gpu-manager.service takes 10.44 seconds during boot time and
it's log contains the below errors:

log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /opt/amdgpu-pro/bin/amdgpu-pro-px
Looking for nvidia modules in /lib/modules/5.19.0-26-generic/kernel
Looking for nvidia modules in /lib/modules/5.19.0-26-generic/updates/dkms
Looking for amdgpu modules in /lib/modules/5.19.0-26-generic/kernel
Looking for amdgpu modules in /lib/modules/5.19.0-26-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is amdgpu versioned? no
Is amdgpu pro stack? no
Is nouveau loaded? yes
Is nouveau blacklisted? no
Is nvidia kernel module available? no
Is amdgpu kernel module available? no
Vendor/Device Id: 8086:9a49
BusID "PCI:0@0:2:0"
Is boot vga? yes
Vendor/Device Id: 10de:1f9c
BusID "PCI:89@0:0:0"
can't open /sys/bus/pci/devices/:59:00.0/boot_vga
Is boot vga? no
can't open /sys/bus/pci/devices/:59:00.0/boot_vga
Chassis type: "10"
Laptop detected
can't access /etc/u-d-c-nvidia-runtimepm-override file
can't open /sys/module/nvidia/version
Warning: cannot check the NVIDIA driver major version
Support for runtimepm not detected.
You can override this check at your own risk by creating the 
/etc/u-d-c-nvidia-runtimepm-override file.
Is nvidia runtime pm supported for "0x1f9c"? yes
Trying to create new file: /run/nvidia_runtimepm_supported
Checking power status in /proc/driver/nvidia/gpus/:59:00.0/power
Error while opening /proc/driver/nvidia/gpus/:59:00.0/power
Is nvidia runtime pm enabled for "0x1f9c"? no
Skipping "/dev/dri/card1", driven by "i915"
Skipping "/dev/dri/card1", driven by "i915"
Skipping "/dev/dri/card1", driven by "i915"
Found "/dev/dri/card1", driven by "i915"
output 0:
card1-eDP-1
output 1:
card1-HDMI-A-2
Number of connected outputs for /dev/dri/card1: 2
can't access /etc/prime-discrete
No prime-settings found. Assuming prime is not set to ON (ONDEMAND could be on).
Does it require offloading? no
last cards number = 2
Has amd? no
Has intel? yes
Has nvidia? yes
How many cards? 2
Loading nvidia with "no" parameters
Has the system changed? No
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't open /sys/module/nvidia/version
can't access /run/u-d-c-nvidia-drm-was-loaded file

[Desktop-packages] [Bug 1998537] Re: Holding Cttrl+S generates too many 'save page' dialogues

[Paul White]

I can confirm this issue when running the snap version of Firefox in
both the jammy and kinetic releases of Ubuntu. I don't see this bug when
running the .deb version of Firefox in Ubuntu 20.04.

** Tags added: snap

** Summary changed:

- Holding Cttrl+S generates too many 'save page' dialogues
+ [snap] Holding down Ctrl+S generates too many 'save page' dialogs

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

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

Title:
  [snap] Holding down Ctrl+S generates too many 'save page' dialogs

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Opening any page and holding Ctrl+S on the firefox snap package begins
  to spam-generate save dialogues. These do not stop being generated for
  several seconds after Ctrl+S is released. These dialogues slow down
  the system to the point that interacting with both them, and the
  system as a whole, feels laggy. The compositor also attempts to assign
  them each shadows, and as a result, on Mutter with Wayland, a they are
  surrounded by a thick black halo (see attachment).

  I'm running Ubuntu 22.04.1 on Gnome 42.5 with Wayland. Firefox is
  version 107.0.1 although this bug has been present on every version of
  Firefox I've used on this system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1998537/+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 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment

[Alberto Milone]

** Changed in: ubuntu-drivers-common (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

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

Title:
  UnboundLocalError: local variable 'version' referenced before
  assignment

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

Bug description:
  Hello, we received a drive-by complaint about the ubuntu-drivers
  autoinstall tool:

  < Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command
  < Fhazal> this error appear when i try to auto install recommended driver
  < Fhazal> https://pastebin.com/ydZVFT24

  The contents of the pastebin:

  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
  return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
  command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
  UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in 
nvidia_desktop_pre_installation_hook
  with_nvidia_kms = version >= 470
  UnboundLocalError: local variable 'version' referenced before assignment

  
  Skimming the version on my system it sure feels plausible:

  def nvidia_desktop_pre_installation_hook(to_install):
  '''Applies changes that need to happen before installing the NVIDIA 
drivers'''
  with_nvidia_kms = False

  # Enable KMS if nvidia >= 470
  for package_name in to_install:
  if package_name.startswith('nvidia-driver-'):
  try:
  version = int(package_name.split('-')[-1])
  except ValueError:
  pass
  finally:
  with_nvidia_kms = version >= 470

  if with_nvidia_kms:
  set_nvidia_kms(1)


  If there was an exception splitting, indexing, or converting to an
  int, that 'version' variable may not have a value.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1993019/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD

[Joshua Peisach]

Fix in version 5.6.1, sitting in proposed

** Changed in: nemo (Ubuntu Lunar)
   Status: New => Fix Committed

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

Title:
  CVE-2022-37290: Pasted zip archive/invalid file causes NPD

Status in caja package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New
Status in nemo package in Ubuntu:
  Fix Committed
Status in caja source package in Focal:
  New
Status in nautilus source package in Focal:
  New
Status in nemo source package in Focal:
  New
Status in caja source package in Jammy:
  New
Status in nautilus source package in Jammy:
  New
Status in nemo source package in Jammy:
  New
Status in caja source package in Kinetic:
  New
Status in nautilus source package in Kinetic:
  New
Status in nemo source package in Kinetic:
  New
Status in caja source package in Lunar:
  New
Status in nautilus source package in Lunar:
  New
Status in nemo source package in Lunar:
  Fix Committed

Bug description:
  A bug for the triage/patching of CVE-2022-37290.

  In get_basename() and g_file_get_basename(), when the file name cannot
  be parsed, NULL is returned; Nautilus does not check this and this
  results in a NPD and a crash.

  The issue on GNOME GitLab explains this pretty well:
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376

  And the code in question is also in Nemo and Caja.

  History of the code: The faulty code was introduced in Nautilus 2.20,
  before Nemo and Caja were forked; these file managers have the same
  issue and same code in the function.

  The simplest POC I found was running this via DBus, which I'm not 100%
  sure if I've altered correctly for Nemo and Caja, but regardless for
  Nautilus this results in a crash.

  ```
  Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed
  Nov 27 20:38:32 Joshua-2210Test kernel: [  825.449866] pool-org.gnome.[5439]: 
segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in 
libglib-2.0.so.0.7400.0[7f3058c03000+8f000]
  Nov 27 20:38:32 Joshua-2210Test kernel: [  825.449878] Code: 0f 85 bc fe ff 
ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 
89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 
00 0f b6 42 01 48 8d
  ```

  Attached is the poc.py, made by Wu Chunming.

  ** Nemo **
  Upstream, version 5.6.0:
  (more advanced/verbose) upstream patch: 
https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005
  possible further problems: 
https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 27 20:41:20 2022
  GsettingsChanges:

  InstallationDate: Installed on 2022-09-18 (70 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 2001904] Re: URLs fail to launch in Firefox

[Dave Jones]

Adding a trivial test PDF

** Attachment added: "test_pdf.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2001904/+attachment/5639334/+files/test_pdf.pdf

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

Title:
  URLs fail to launch in Firefox

Status in evince package in Ubuntu:
  New

Bug description:
  Opening a PDF under evince, then clicking an https: link within the
  PDF fails to open the link in Firefox. On the command line, evince
  reports:

  $ evince test.pdf
  env: ‘/snap/bin/firefox’: Permission denied

  In dmesg, the following message appears each time the link is clicked:

  [ 1366.891145] audit: type=1400 audit(1672910889.559:286):
  apparmor="DENIED" operation="exec" profile="/usr/bin/evince"
  name="/usr/bin/snap" pid=14698 comm="env" requested_mask="x"
  denied_mask="x" fsuid=1000 ouid=0

  This may be related to (or a regression of?) LP: #964510 as it's
  clearly aa related, but I don't think it's a direct duplicate given
  the audit log is rather different.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2001904/+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 2001921] Re: Update to 108.0.1

[Nishit Majithia]

Package Information:
  https://launchpad.net/ubuntu/+source/firefox/108.0.1+build1-0ubuntu0.20.04.1
  https://launchpad.net/ubuntu/+source/firefox/108.0.1+build1-0ubuntu0.18.04.1

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

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

Title:
  Update to 108.0.1

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  https://www.mozilla.org/en-US/firefox/108.0.1/releasenotes/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2001921/+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 2001922] [NEW] Xorg crash

[pd]

Public bug reported:

My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure
out how to reproducibly trigger the crash. The last time it happened was
with firefox and zoom running, the display suddenly went black and after
a few seconds the X login screen appeared, my session gone.

There are files in /var/crash/

-rw-r--r-- 1 root whoopsie0 Jan  5 14:09 _usr_lib_xorg_Xorg.0.upload
-rw-r- 1 root whoopsie 12792518 Jan  5 14:09 _usr_lib_xorg_Xorg.0.crash
-rw--- 1 whoopsie whoopsie   37 Jan  5 14:09 
_usr_lib_xorg_Xorg.0.uploaded
-rw-r--r-- 1 petr whoopsie0 Jan  5 14:13 
_usr_bin_xfsettingsd.1000.upload
-rw-r- 1 petr whoopsie   516897 Jan  5 14:13 
_usr_bin_xfsettingsd.1000.crash
-rw--- 1 whoopsie whoopsie   37 Jan  5 14:13 
_usr_bin_xfsettingsd.1000.uploaded
-rw-r--r-- 1 petr whoopsie0 Jan  5 14:13 _opt_zoom_zoom.1000.upload
-rw-r- 1 petr whoopsie 46590288 Jan  5 14:13 _opt_zoom_zoom.1000.crash
-rw--- 1 whoopsie whoopsie   37 Jan  5 14:13 
_opt_zoom_zoom.1000.uploaded


and .xsession-errors.old ends with

(xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 
0x649, atom "_NET_WM_STATE_STAYS_ON_TOP")
(xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0
Exiting due to channel error.
Failed to parse arguments: Cannot open display: :0.0
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
(xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
(xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0
Failed to parse arguments: Cannot open display: :0.0
(xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0
(xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0
Failed to parse arguments: Cannot open display: :0.0
(xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0
Failed to parse arguments: Cannot open display: :0.0
Failed to parse arguments: Cannot open display: :0.0
Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"
Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"
Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"
Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"

Is it safe and useful to upload the files from /var/crash/?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Jan  5 14:17:42 2023
DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed
 virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Cezanne [17aa:3f96]
InstallationDate: Installed on 2021-11-07 (424 days ago)
InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20YA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic 
root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago)
dmi.bios.date: 09/23/2021
dmi.bios.release: 1.27
dmi.bios.vendor: LENOVO
dmi.bios.version: GMCN27WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: ThinkBook 13s G3 ACN
dmi.ec.firmware.release: 1.19
dmi.modalias: 
dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN:
dmi.product.family: ThinkBook 13s G3 ACN
dmi.product.name: 20YA
dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN
dmi.product.version: ThinkBook 13s G3 ACN
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1

[Desktop-packages] [Bug 2001921] [NEW] Update to 108.0.1

[Nishit Majithia]

Public bug reported:

https://www.mozilla.org/en-US/firefox/108.0.1/releasenotes/

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

Title:
  Update to 108.0.1

Status in firefox package in Ubuntu:
  New

Bug description:
  https://www.mozilla.org/en-US/firefox/108.0.1/releasenotes/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2001921/+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 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

[Gunnar Hjalmarsson]

Ok, Robie, you win. :) I have uploaded to the kinetic unapproved queue
too. Hopefully the version string (0.219.22.10.1) makes sense.

** Changed in: language-selector (Ubuntu Kinetic)
   Importance: Undecided => Wishlist

** Changed in: language-selector (Ubuntu Kinetic)
   Status: Won't Fix => In Progress

** Changed in: language-selector (Ubuntu Kinetic)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Description changed:

  [ Impact ]
  
  The current default font for Sinhala (LKLUG) is unmaintained and comes
  with issues. Noto offers Sinhala fonts with significantly higher
  quality.
  
  fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of
  changing that, the proposed change makes fontconfig give Noto Sans
  Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and
  that — together with installation of fonts-noto-core — seems to be
  sufficient to achieve the desired result.
  
  [ Test Plan ]
  
- * Install language-selector-[common,gnome] from jammy-proposed.
+ * Install language-selector-[common,gnome] from
+ [jammy,kinetic]-proposed.
  
  * Open Language Support and install the Sinhala language.
  
  * Open a terminal window and run this command:
  
    fc-match -a | grep -E 'LKLUG|Sinhala'
  
  * Confirm that Noto Sans Sinhala is listed before LKLUG.
  
  * Close Firefox and re-open it.
  
  * Visit e.g. https://si.wikipedia.org and confirm the
-   improvement. (Also I (Gunnar), who don't speak Sinhala,
-   notice a remarkable difference.)
+   improvement. (Also I (Gunnar), who don't speak Sinhala,
+   notice a remarkable difference.)
  
  [ Where problems could occur ]
  
  No real problem in sight. Some Sinhala speaking users with fonts-noto-
  core installed will indeed see a surprise change when it starts to
  render Sinhala via Noto fonts instead of LKLUG. But that surprise ought
  to make them happy. :)
  
  Please note Robie Basak's warning about the changed font metrics in
  comment #7, though.
  
  [ Original description ]
  
  **What's the problem?**
  
  Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear.
  e.g. we cannot recognize vowel signs and read websites using that font.
  We can change it manually but such changes do not apply to some
  applications or application types e.g. snap apps etc.
  
  LKLUG (last active: 2012) no one maintain it now.
  https://web.archive.org/web/202200*/http://www.lug.lk/
  http://www.lug.lk/fonts/lklug
  
  **What expected to happen?**
  
  We would like to see Noto serif sinhala as the default font for sinhala 
language
  https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala
  [Highlighs: clear (readable), thin, takes less space than sans sinhala]
  
  If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala 
https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala
  [Highlighs: clear (readable), thick, takes more space than serif sinhala]
  
  **Additional details**
  
  Screenshots (see the difference: LKLUG/Noto)
  
  LKLUG
  https://i.ibb.co/nbHM5Mw/lklug.jpg
  
  Noto Sinhala
  https://i.ibb.co/k9dbtYb/noto.jpg
  
  If you need more examples or clarifications, please add a comment
  
  Random posts
  1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g
  2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with 
some apps)
  3. 
https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/
  
  Also, some developers already have designed tools, scripts for that problem 
however many people do not try to find these scripts and switch to other OS
  1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache)
  2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79
  3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer
  
  Please review details, screenshots and posts. This is not a personal
  opinion and atleast, i expect to see this change in the next interim or
  LTS release.
  
  Furthermore, please let me know if i can help to speed-up this
  replacement process

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

Title:
  [System Fonts] Replace default sinhala font from LKLUG to Noto

Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Won't Fix
Status in language-selector source package in Jammy:
  In Progress
Status in language-selector source package in Kinetic:
  In Progress

Bug description:
  [ Impact ]

  The current default font for Sinhala (LKLUG) is unmaintained and comes
  with issues. Noto offers Sinhala fonts with significantly higher
  quality.

  fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of
  changing that, the proposed change makes fontconfig give Noto Sans
  Sinhala respective Noto Serif Sinhala higher precedence than 

[Desktop-packages] [Bug 1983794] Re: Evolution not deleting autosave files

[Christoph Petzold]

For me

  sudo apt remove libcanberra-gtk3-module

solved the problem.

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

Title:
  Evolution not deleting autosave files

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Invalid
Status in libcanberra package in Ubuntu:
  Triaged

Bug description:
  Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
  was installed with the distribution on a new system and received
  settings imported from an earlier version on another computer.

  When composing an email, if the process takes long enough an autosave
  file is created as ~/.local/share/evolution/.evolution-
  composer.autosave-xx ("xx" is a random 6 character string).
  When the email is successfully sent, the autosave file SHOULD be
  deleted. It's not. When evolution is shut down and restarted I'm asked
  if I want to recover an unfinished email. Answering No to this will
  delete the autosave file, but otherwise it persists and the recovery
  query recurs the next time I open evolution.

  Other people are having the same issue, see
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
  people aren't dealing with it, perhaps considering it a distro-
  specific bug.

  On a system used by many people this is a potential security issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

[Robie Basak]

Thank you for the updates! It looks like you responded appropriately to
all of my points, but I'd like to clarify one thing about version
numbers and Kinetic.

> If a user with an updated jammy (including this fix) upgrades to
kinetic, they will still have version 0.219.1 of the language-selector-*
packages, since the version string in kinetic is lower. So no
regression.

If you're not intending to fix Kinetic, then we'll need to use a
different package version for Jammy. We generally avoid the version
situation you describe, since that makes it difficult to reliably issue
an update for users for the package in Kinetic. Consider if a security
update were then required, for example. It would be possible to fix, but
only if someone were to notice the unusual situation first. And it's
confusing for Kinetic users to be on a different package version
depending on whether or not they upgraded from Jammy or not. That
situation means there are more combinations of interactions with other
packages that might lead to different behaviours and different bugs. So
we avoid it.

Using a "compliant" version for the Jammy SRU, the original point about
regressions on upgrade still stands, but see
https://wiki.ubuntu.com/StableReleaseUpdates#Newer_Releases for
instructions and policy for this situation. It may still acceptable if
you insist on not updating Kinetic. But we will want to adjust the
version string for Jammy.

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

Title:
  [System Fonts] Replace default sinhala font from LKLUG to Noto

Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Won't Fix
Status in language-selector source package in Jammy:
  In Progress
Status in language-selector source package in Kinetic:
  Won't Fix

Bug description:
  [ Impact ]

  The current default font for Sinhala (LKLUG) is unmaintained and comes
  with issues. Noto offers Sinhala fonts with significantly higher
  quality.

  fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of
  changing that, the proposed change makes fontconfig give Noto Sans
  Sinhala respective Noto Serif Sinhala higher precedence than LKLUG,
  and that — together with installation of fonts-noto-core — seems to be
  sufficient to achieve the desired result.

  [ Test Plan ]

  * Install language-selector-[common,gnome] from jammy-proposed.

  * Open Language Support and install the Sinhala language.

  * Open a terminal window and run this command:

    fc-match -a | grep -E 'LKLUG|Sinhala'

  * Confirm that Noto Sans Sinhala is listed before LKLUG.

  * Close Firefox and re-open it.

  * Visit e.g. https://si.wikipedia.org and confirm the
improvement. (Also I (Gunnar), who don't speak Sinhala,
notice a remarkable difference.)

  [ Where problems could occur ]

  No real problem in sight. Some Sinhala speaking users with fonts-noto-
  core installed will indeed see a surprise change when it starts to
  render Sinhala via Noto fonts instead of LKLUG. But that surprise
  ought to make them happy. :)

  Please note Robie Basak's warning about the changed font metrics in
  comment #7, though.

  [ Original description ]

  **What's the problem?**

  Currently ubuntu comes with LKLUG font for sinhala (si). it's not
  clear. e.g. we cannot recognize vowel signs and read websites using
  that font. We can change it manually but such changes do not apply to
  some applications or application types e.g. snap apps etc.

  LKLUG (last active: 2012) no one maintain it now.
  https://web.archive.org/web/202200*/http://www.lug.lk/
  http://www.lug.lk/fonts/lklug

  **What expected to happen?**

  We would like to see Noto serif sinhala as the default font for sinhala 
language
  https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala
  [Highlighs: clear (readable), thin, takes less space than sans sinhala]

  If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala 
https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala
  [Highlighs: clear (readable), thick, takes more space than serif sinhala]

  **Additional details**

  Screenshots (see the difference: LKLUG/Noto)

  LKLUG
  https://i.ibb.co/nbHM5Mw/lklug.jpg

  Noto Sinhala
  https://i.ibb.co/k9dbtYb/noto.jpg

  If you need more examples or clarifications, please add a comment

  Random posts
  1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g
  2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with 
some apps)
  3. 
https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/

  Also, some developers already have designed tools, scripts for that problem 
however many people do not try to find these scripts and switch to other OS
  1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache)
  2. 

[Desktop-packages] [Bug 2001890] Re: Network Manager cannot using the 'add' button for openvpn

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Network Manager cannot using the 'add' button for openvpn

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi everyone,

  This issue is related to network-manager with an openvpn connection on
  Ubuntu 22.10.

  I am using a openvpn connection with as connection type "Password with
  Certificate (TLS)".

  After upgrading my laptop from ubuntu 22.04 to ubuntu 22.10, I am no longer 
able to save the TLS certificate password
  for my user only.
  If I select the "for my user only" option, I cannot save the profile (i.e. 
button is disabled).

  The only option I currently have is to never save the password, which
  does work.

  This issue only popped up after the upgrade to 22.10. Not touching the VPN 
connection makes network-manager ask for
  the password.

  Have a look at the screenshot below for further information.

  Any help would be appreciated.

  Thank you in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2001890/+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 2001914] [NEW] The gpu hangs and is not possible to work with GPU-envioronment

[Tsvetomir]

Public bug reported:

When I open the terminal or just browsing, gnom sometimes freezes for a
second, but sometimes  restart the machine is necessary. The log is:

Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm]i915 :00:02.0: [drm] 
GPU HANG: ecode 12:0:
Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] Resetting chip for 
stopped heartbeat on rcs0
Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled
Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC SLPC: enabled
Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes
Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: last_user_time 
(2748010) is greater than comparison timestamp (2743419).  This most likely 
represents a buggy client sending inaccurate timestamps in messages such as 
_NET_ACTIVE_WINDOW.  Trying to work around...
Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c 
appears to be one of the offending windows with a timestamp of 2748010.  
Working around...

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan  5 12:25:49 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-01-02 (2 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  The gpu hangs and is not possible to work with GPU-envioronment

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I open the terminal or just browsing, gnom sometimes freezes for
  a second, but sometimes  restart the machine is necessary. The log is:

  Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm]i915 :00:02.0: 
[drm] GPU HANG: ecode 12:0:
  Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] Resetting chip for 
stopped heartbeat on rcs0
  Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled
  Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC SLPC: enabled
  Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes
  Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 
last_user_time (2748010) is greater than comparison timestamp (2743419).  This 
most likely represents a buggy client sending inaccurate timestamps in messages 
such as _NET_ACTIVE_WINDOW.  Trying to work around...
  Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c 
appears to be one of the offending windows with a timestamp of 2748010.  
Working around...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  5 12:25:49 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-02 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  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/2001914/+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 2001911] [NEW] [SRU] libreoffice 7.4.4 for kinetic

[Rico Tzschichholz]

Public bug reported:

[Impact]

 * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line:
 https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release

 * Version 7.4.2 is currently released in kinetic and 7.4.3 in 
kinetic-proposed. For a list of fixed bugs compared to 7.4.3 see the list of 
bugs fixed in the release candidates of 7.4.4 (that's a total of ? bugs):
 https://wiki.documentfoundation.org/Releases/7.4.4/RC1#List_of_fixed_bugs
 https://wiki.documentfoundation.org/Releases/7.4.4/RC2#List_of_fixed_bugs

 * Given the nature of the project, the complexity of the codebase and
the high level of quality assurance upstream, it is preferable to SRU a
minor release rather than cherry-pick selected bug fixes.

[Testing]

 * Upstream testing. Bugs fixed upstream typically include
unit/regression tests, and the release itself is extensively exercised
(both in an automated manner and manually).

  * A recent set of upstream's automated jenkins testing can be found here:
https://ci.libreoffice.org/job/gerrit_74/1542/

  * More information about the upstream QA testing can be found here:
* Automated tests
  https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
* Automated UI tests
  https://wiki.documentfoundation.org/Development/UITests
* Regression tests
  https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
* Feature tests
  https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

 * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
* [amd64] ...
* [arm64] ...
* [armhf] ...
* [ppc64el] ...
* [s390x] ...
 * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

[Regression Potential]

 * A minor release with a total of ? bug fixes always carries the
potential for introducing regressions, even though it is a bugfix-only
release, meaning that no new features were added, and no existing
features were removed.

 * A combination of autopkgtests and careful smoke testing as described
above should provide reasonable confidence that no regressions sneaked
in.

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

** Affects: libreoffice (Ubuntu Kinetic)
 Importance: High
 Assignee: Rico Tzschichholz (ricotz)
 Status: New

** Also affects: libreoffice (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: libreoffice (Ubuntu Kinetic)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

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

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

Title:
  [SRU] libreoffice 7.4.4 for kinetic

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice source package in Kinetic:
  New

Bug description:
  [Impact]

   * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release

   * Version 7.4.2 is currently released in kinetic and 7.4.3 in 
kinetic-proposed. For a list of fixed bugs compared to 7.4.3 see the list of 
bugs fixed in the release candidates of 7.4.4 (that's a total of ? bugs):
   https://wiki.documentfoundation.org/Releases/7.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.4.4/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_74/1542/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] ...
  * [arm64] ...
  * [armhf] ...
  * [ppc64el] ...
  * [s390x] ...
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 

[Desktop-packages] [Bug 2001910] Re: Libreoffice Impress crashes when exiting presentation with high-dpi scaling in GNOME

[peterfrank]

Additional info: the bug occurs on both Wayland and Xorg sessions on my
Ubuntu 22.04 installation.

(Before I upgraded Ubuntu, I also experienced the problem on 20.04, with
all recent versions of LibreOffice including both official Ubuntu
versions and more updated PPA versions, but only in Xorg sessions not
Wayland sessions.)

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

Title:
  Libreoffice Impress crashes when exiting presentation with high-dpi
  scaling in GNOME

Status in libreoffice package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.04.01, LibreOffice Impress (version
  1:7.3.7-0ubuntu0.22.04.1) crashes when exiting the presentation mode,
  if I enable 200% scaling in GNOME settings on my high-dpi screen. The
  application window disappears silently instead of returning to the
  editing mode. The error message is (if Impress is started from a
  terminal):

  
  X-Error: BadDrawable (invalid Pixmap or Window parameter)
Major opcode: 62 (X_CopyArea)
Resource ID:  0x1202be7
Serial No:59699 (59699)
  These errors are reported asynchronously,
  set environment variable SAL_SYNCHRONIZE to 1 to help debugging
  Unspecified Application Error
  

  The crash occurs reliably every time. The crash does not happen if I
  do not use scaling in GNOME display settings, or if I turn off the
  "hardware acceleration" option in Impress --> Tools --> Options -->
  LibreOffice --> View --> Graphics Output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001910/+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 2001910] [NEW] Libreoffice Impress crashes when exiting presentation with high-dpi scaling in GNOME

[peterfrank]

Public bug reported:

On Ubuntu 22.04.01, LibreOffice Impress (version
1:7.3.7-0ubuntu0.22.04.1) crashes when exiting the presentation mode, if
I enable 200% scaling in GNOME settings on my high-dpi screen. The
application window disappears silently instead of returning to the
editing mode. The error message is (if Impress is started from a
terminal):


X-Error: BadDrawable (invalid Pixmap or Window parameter)
Major opcode: 62 (X_CopyArea)
Resource ID:  0x1202be7
Serial No:59699 (59699)
These errors are reported asynchronously,
set environment variable SAL_SYNCHRONIZE to 1 to help debugging
Unspecified Application Error


The crash occurs reliably every time. The crash does not happen if I do
not use scaling in GNOME display settings, or if I turn off the
"hardware acceleration" option in Impress --> Tools --> Options -->
LibreOffice --> View --> Graphics Output.

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

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

Title:
  Libreoffice Impress crashes when exiting presentation with high-dpi
  scaling in GNOME

Status in libreoffice package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.04.01, LibreOffice Impress (version
  1:7.3.7-0ubuntu0.22.04.1) crashes when exiting the presentation mode,
  if I enable 200% scaling in GNOME settings on my high-dpi screen. The
  application window disappears silently instead of returning to the
  editing mode. The error message is (if Impress is started from a
  terminal):

  
  X-Error: BadDrawable (invalid Pixmap or Window parameter)
Major opcode: 62 (X_CopyArea)
Resource ID:  0x1202be7
Serial No:59699 (59699)
  These errors are reported asynchronously,
  set environment variable SAL_SYNCHRONIZE to 1 to help debugging
  Unspecified Application Error
  

  The crash occurs reliably every time. The crash does not happen if I
  do not use scaling in GNOME display settings, or if I turn off the
  "hardware acceleration" option in Impress --> Tools --> Options -->
  LibreOffice --> View --> Graphics Output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001910/+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 2001904] [NEW] URLs fail to launch in Firefox

[Dave Jones]

Public bug reported:

Opening a PDF under evince, then clicking an https: link within the PDF
fails to open the link in Firefox. On the command line, evince reports:

$ evince test.pdf
env: ‘/snap/bin/firefox’: Permission denied

In dmesg, the following message appears each time the link is clicked:

[ 1366.891145] audit: type=1400 audit(1672910889.559:286):
apparmor="DENIED" operation="exec" profile="/usr/bin/evince"
name="/usr/bin/snap" pid=14698 comm="env" requested_mask="x"
denied_mask="x" fsuid=1000 ouid=0

This may be related to (or a regression of?) LP: #964510 as it's clearly
aa related, but I don't think it's a direct duplicate given the audit
log is rather different.

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

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

Title:
  URLs fail to launch in Firefox

Status in evince package in Ubuntu:
  New

Bug description:
  Opening a PDF under evince, then clicking an https: link within the
  PDF fails to open the link in Firefox. On the command line, evince
  reports:

  $ evince test.pdf
  env: ‘/snap/bin/firefox’: Permission denied

  In dmesg, the following message appears each time the link is clicked:

  [ 1366.891145] audit: type=1400 audit(1672910889.559:286):
  apparmor="DENIED" operation="exec" profile="/usr/bin/evince"
  name="/usr/bin/snap" pid=14698 comm="env" requested_mask="x"
  denied_mask="x" fsuid=1000 ouid=0

  This may be related to (or a regression of?) LP: #964510 as it's
  clearly aa related, but I don't think it's a direct duplicate given
  the audit log is rather different.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2001904/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end

[Daniel van Vugt]

Yeah kinetic doesn't have this bug so we can probably fix jammy via the
backport without knowing which commits are most important.

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Gnome-shell is crashing on older gen Intel hw due to a memory leak.

  [Fix]
  An upstream commit that fixes the memleak in the crocus driver (which is only 
used on Intel 4th gen chips and older)

  [Test case]
  Either test this on an old Intel or see if there's a dent in the reported 
crashes.

  [Where things could go wrong]
  Mainly if this would not fix the crashes.

  --
  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/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
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/mesa/+bug/1972977/+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 1999213] Re: Xorg crashed with SIGSEGV in ActivateGrabNoDelivery() from ActivatePassiveGrab() from CheckPassiveGrabsOnWindow() from CheckDeviceGrabs() from ProcessDeviceEvent()

[Bug Watch Updater]

** Changed in: xorg-server
   Status: Unknown => 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/1999213

Title:
  Xorg crashed with SIGSEGV in ActivateGrabNoDelivery() from
  ActivatePassiveGrab() from CheckPassiveGrabsOnWindow() from
  CheckDeviceGrabs() from ProcessDeviceEvent()

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:21.1.3-2ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/4bdcf11799f043b0a08bfd0a926e3751257425e8 
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/xorg-server/+bug/1999213/+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 2001594] Re: Mutter crashes on xdg_activation.activate request

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => New

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

Title:
  Mutter crashes on xdg_activation.activate request

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Please allow users to upgrade Mutter because of bug. See
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2486

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2001594/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end

[Timo Aaltonen]

or, just accept the current upload and revisit it again with the 22.2
backport if needed, but in any case I don't think this bug should block
either one from getting into updates

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Gnome-shell is crashing on older gen Intel hw due to a memory leak.

  [Fix]
  An upstream commit that fixes the memleak in the crocus driver (which is only 
used on Intel 4th gen chips and older)

  [Test case]
  Either test this on an old Intel or see if there's a dent in the reported 
crashes.

  [Where things could go wrong]
  Mainly if this would not fix the crashes.

  --
  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/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
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/mesa/+bug/1972977/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end

[Timo Aaltonen]

but it is in 22.2.x which we need in proposed asap anyway, so I'll drop
this from the current upload so that it can be fast-tracked through, as
#1998893 is even more urgent.

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Gnome-shell is crashing on older gen Intel hw due to a memory leak.

  [Fix]
  An upstream commit that fixes the memleak in the crocus driver (which is only 
used on Intel 4th gen chips and older)

  [Test case]
  Either test this on an old Intel or see if there's a dent in the reported 
crashes.

  [Where things could go wrong]
  Mainly if this would not fix the crashes.

  --
  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/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
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/mesa/+bug/1972977/+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 2001890] Re: Network Manager cannot using the 'add' button for openvpn

[Luca Bei]

As you can see in the screenshot I am using the following settings and I
cannot click the 'add' button.

** Attachment added: "Screenshot2.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2001890/+attachment/5639245/+files/Screenshot2.png

** Description changed:

  Hi everyone,
  
- After upgrading my laptop to ubuntu 22.10 I cannot add an openvpn in the
- network settings.
+ This issue is related to network-manager with an openvpn connection on
+ Ubuntu 22.10.
+ 
+ I am using a openvpn connection with as connection type "Password with
+ Certificate (TLS)".
+ 
+ After upgrading my laptop from ubuntu 22.04 to ubuntu 22.10, I am no longer 
able to save the TLS certificate password
+ for my user only.
+ If I select the "for my user only" option, I cannot save the profile (i.e. 
button is disabled).
+ 
+ The only option I currently have is to never save the password, which
+ does work.
+ 
+ This issue only popped up after the upgrade to 22.10. Not touching the VPN 
connection makes network-manager ask for
+ the password.
  
  Have a look at the screenshot below for further information.
  
+ Any help would be appreciated.
+ 
  Thank you in advance!

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

Title:
  Network Manager cannot using the 'add' button for openvpn

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi everyone,

  This issue is related to network-manager with an openvpn connection on
  Ubuntu 22.10.

  I am using a openvpn connection with as connection type "Password with
  Certificate (TLS)".

  After upgrading my laptop from ubuntu 22.04 to ubuntu 22.10, I am no longer 
able to save the TLS certificate password
  for my user only.
  If I select the "for my user only" option, I cannot save the profile (i.e. 
button is disabled).

  The only option I currently have is to never save the password, which
  does work.

  This issue only popped up after the upgrade to 22.10. Not touching the VPN 
connection makes network-manager ask for
  the password.

  Have a look at the screenshot below for further information.

  Any help would be appreciated.

  Thank you in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2001890/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end

[Daniel van Vugt]

Tested jammy with crocus on an i5-4300U, both 22.0.5-0ubuntu0.1 and
22.0.5-0ubuntu0.2

gnome-shell's RSS grows but seems to plateau similarly with both.

Based on upstream's comments, I started counting i915.gem instances in
/proc/PID/smaps and found that both 22.0.5-0ubuntu0.1 and
22.0.5-0ubuntu0.2 seem to leak them equally. Never reached the point of
crashing but the evidence is that mesa 22.0.5-0ubuntu0.2 makes gnome-
shell leak almost as much as 22.0.5-0ubuntu0.1 ... That said, I expect
most graphics leaks to be hardware independent and the fault of gnome-
shell/mutter, not mesa.

Looking at the upstream fix again I realize it's not fixing all the
leaks that's important here, but avoiding crashes when they occur. And
for that we are missing the correct patch:

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17615/diffs

It's not in mesa_22.0.5-0ubuntu0.2.diff.gz


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

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Gnome-shell is crashing on older gen Intel hw due to a memory leak.

  [Fix]
  An upstream commit that fixes the memleak in the crocus driver (which is only 
used on Intel 4th gen chips and older)

  [Test case]
  Either test this on an old Intel or see if there's a dent in the reported 
crashes.

  [Where things could go wrong]
  Mainly if this would not fix the crashes.

  --
  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/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
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/mesa/+bug/1972977/+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