[Desktop-packages] [Bug 1990886] Re: Security updates missing after 91.11.0

[Rico Tzschichholz]

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-36319

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-36318

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-36314

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-2505

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-38472

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-38473

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-38477

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-38476

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-38478

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3033

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3032

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3034

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-36059

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

Title:
  Security updates missing after 91.11.0

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  Upstream released Thunderbird 91.11.0 on June 28, 2022.
  It's now at 91.13.1 from September 19, 2022. The release notes say:
  "By popular demand, Thunderbird 91.13.1 contains important security updates 
that shipped in Thunderbird 102.2.1. Users are encouraged to update as soon as 
possible."
  Source: https://www.thunderbird.net/en-US/thunderbird/91.13.1/releasenotes/

  Ubuntu 22.04 Jammy (but also the other supported LTS) still has Thunderbird 
91.11.0 (1:91.11.0+build2-0ubuntu0.22.04.1) without the security fixes after 
91.11.0.
  The package should be updated to 91.13.1.

  Given that it has been three months without security updates, there
  seems to be some general friction with following upstream.

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


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

[Desktop-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu

[Baker]

my wpa_supplicant version is 2.9
but, it is not working for me.

iphone se3, ios 15.7
it is not connected. infinite loading.

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1753509] Re: avahi-daemon adds/installs every printer on network

[Walt DeMoss]

I have had the same problem since 20.04.  Now on 22.04.  for me it is
solved by using deny-interfaces in the avahi-daemon.conf file.  I just
eliminate the interfaces that are adding the printers I don't need.
Here I have denied my wifi usb dongle and my ZeroTier network
connection.


** Attachment added: "Selection_052.bmp"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1753509/+attachment/5620161/+files/Selection_052.bmp

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

Title:
  avahi-daemon adds/installs every printer on network

Status in cups package in Ubuntu:
  Triaged

Bug description:
  When connected to a network, avahi-daemon adds & installs all printer
  on a network without being prompted.  This is not desired behaviour.
  Discovery of the printers is good, but not automatic installation &
  addition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  5 09:29:05 2018
  InstallationDate: Installed on 2017-09-29 (157 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1989744] Re: KB/Mouse use causing short system freezes. Happens after resume

[Daniel van Vugt]

OK, stay in hybrid mode.

The next thing to try is to select 'Ubuntu on Wayland' on the login
screen. And then check the Settings app to ensure Wayland is in use.
Does that exhibit the same bug?

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

Title:
  KB/Mouse use causing short system freezes. Happens after resume

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Summary:
  My laptop gets into a an odd state after resuming from sleep where, depending 
on user activity,
  the entire system freezes every 20 seconds for about 1/2 second.

  This does not happen after every resume. After upgrading to 22.04 was much 
less 
  frequent than it was with 21.10. It seems that after some recent update it is 
happening
  more frequently again. Maybe one every 4 suspend/resume cycles.

  Normal operation can be restored by rebooting or sometimes suspending
  and waking.

  The triggering event is complex:
  * The pointer or pointer and keyboard must be actively used
  * Just typing with no mouse use will not cause it to happen.
  * Just moving the mouse pointer around but keeping it inside the same GUI 
element(a 
textarea for example) will not cause it
  * Typing for more than 20 seconds and then moving the mouse one pixel will 
cause it.
  * Moving the mouse around constantly for over 20 seconds will cause it to 
happen only 
if: a key on the keyboard was hit OR the pointer moved over a new GUI 
element(window 
border, button, even frames in a web page)
  * It is not application specific. 

  
  The following is usually logged(not always though) when the freeze happens:
  ==> ~/.local/share/xorg/Xorg.1.log <==
  [1214998.964] (II) event5  - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some 
input events have been lost.

  ==> /var/log/syslog <==
  Sep 15 08:23:51 krug /usr/libexec/gdm-x-session[3264]: (II) event5  - TPPS/2 
Elan TrackPoint: SYN_DROPPED event - some input events have been lost.

  Sep 15 08:50:34 krug /usr/libexec/gdm-x-session[3264]: (II) event5  - TPPS/2 
Elan TrackPoint: SYN_DROPPED event - some input events have been lost.
  Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer 
event4 trackpoint: scheduled expiry is in the past (-317ms), your system is too 
slow
  Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer 
event4 trackpoint: scheduled expiry is in the past (-301ms), your system is too 
slow
  Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer 
event4 trackpoint: scheduled expiry is in the past (-288ms), your system is too 
slow
  Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer 
event4 trackpoint: scheduled expiry is in the past (-278ms), your system is too 
slow
  Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) WARNING: log rate 
limit exceeded (5 msgs per 360ms). Discarding future messages.

  System Information:

  Lenovo Thinkpad P15
  Model: 20YQ-003WUS 
  OS: Ubuntu 22.04.1 LTS
  Kernel: 5.15.0-46-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-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  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 15 10:13:26 2022
  DistUpgraded: 2022-06-30 16:37:37,968 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed
   virtualbox/6.1.34, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-H GT1 [UHD Graphics] [17aa:22d8]
   NVIDIA Corporation GA107GLM [RTX A2000 Mobile] [10de:25b8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo GA107GLM [RTX A2000 Mobile] [17aa:22d8]
  InstallationDate: Installed on 2022-03-03 (195 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: LENOVO 

[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed

[Qinling Wang]

>From build guild:
  use VaapiVideoDecoder:
--enable-features=VaapiVideoDecoder,\
VaapiVideoEncoder,UseChromeOSDirectVideoDecoder

  use legacy VDA:
--enable-features=VaapiVideoDecoder, VaapiVideoEncoder \
--disable-features=UseChromeOSDirectVideoDecoder

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

Title:
  VA error: resource allocation failed

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  https://github.com/intel/media-driver/issues/1498

  ---

  When I play a H264/AAC video with HW decoding enabled on Alderlake
  12600k, using Wayland I get the error:

  vaCreateSurfaces (import mode) failed, VA error: resource allocation
  failed

  After which, chromium will proceed to play the video without HW
  acceleration using ffmpeg.

  This is both with using the pre-built snap from channel beta/hwacc and
  a snap built from source.

  (NOTE: HW decoding does work with same browser on X11 desktop, using
  VDAVideoDecoder.)

  To get more information on this VA error, I built the snap with debug
  versions of gmmlib and media-driver (latest git) using the latest git
  from valib as well.

  The log output from chromium now mentions why the allocation fails:

  [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
  [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] 
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
  [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
  [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
  [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
  [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder

  Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
  modifier."

  I am on wayland, and use these chromium flags:

  export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
  features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
  features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
  --disable-gpu-driver-bug-workaround --ozone-platform=wayland"

  The video that fails: the 1080p/60 version downloaded from here:
  https://github.com/chthomos/video-media-samples/

  I will figure out which is the "unsupported modifier" and report back,
  here.

  Note: currently gmmlib and media-driver have failing debug builds, but I have 
created pull requests to both:
  https://github.com/intel/media-driver/pull/1491
  https://github.com/intel/gmmlib/pull/97

  CPU: 12600k

  GPU: Intel Alderlake_s (Gen12)

  Snap built with: core20

  Host OS: Ubuntu Kinetic

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


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

[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed

[Qinling Wang]

Thank you for letting me know 104.0.5112.101-1 does work on your
Alderlake.

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

Title:
  VA error: resource allocation failed

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  https://github.com/intel/media-driver/issues/1498

  ---

  When I play a H264/AAC video with HW decoding enabled on Alderlake
  12600k, using Wayland I get the error:

  vaCreateSurfaces (import mode) failed, VA error: resource allocation
  failed

  After which, chromium will proceed to play the video without HW
  acceleration using ffmpeg.

  This is both with using the pre-built snap from channel beta/hwacc and
  a snap built from source.

  (NOTE: HW decoding does work with same browser on X11 desktop, using
  VDAVideoDecoder.)

  To get more information on this VA error, I built the snap with debug
  versions of gmmlib and media-driver (latest git) using the latest git
  from valib as well.

  The log output from chromium now mentions why the allocation fails:

  [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
  [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] 
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
  [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
  [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
  [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
  [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder

  Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
  modifier."

  I am on wayland, and use these chromium flags:

  export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
  features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
  features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
  --disable-gpu-driver-bug-workaround --ozone-platform=wayland"

  The video that fails: the 1080p/60 version downloaded from here:
  https://github.com/chthomos/video-media-samples/

  I will figure out which is the "unsupported modifier" and report back,
  here.

  Note: currently gmmlib and media-driver have failing debug builds, but I have 
created pull requests to both:
  https://github.com/intel/media-driver/pull/1491
  https://github.com/intel/gmmlib/pull/97

  CPU: 12600k

  GPU: Intel Alderlake_s (Gen12)

  Snap built with: core20

  Host OS: Ubuntu Kinetic

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


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

[Desktop-packages] [Bug 1968907] Re: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed

[Erik Thorne]

I believe I'm experiencing something similar. I saw what looked like an
X session reboot which was unexpected. Here's the output from the
relevant part of journalctl -b --priority=3 output

Sep 29 15:11:34 delirium gdm-x-session[1750]: GLib: Source ID 2 was not found 
when attempting to remove it
Sep 29 15:11:36 delirium systemd[288465]: Failed to start Service for snap 
application snapd-desktop-integration.snapd-desktop-integration.
Sep 29 15:11:49 delirium gnome-session-binary[289310]: GLib-GIO-CRITICAL: 
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Sep 29 15:11:49 delirium gnome-session-binary[289310]: GLib-GIO-CRITICAL: 
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Sep 29 15:12:01 delirium gdm-password][289613]: gkr-pam: unable to locate 
daemon control file
Sep 29 15:12:02 delirium systemd[289626]: Failed to start Service for snap 
application snapd-desktop-integration.snapd-desktop-integration.
Sep 29 15:12:26 delirium gnome-session-binary[289310]: GLib-CRITICAL: 
g_hash_table_foreach_remove_or_steal: assertion 'version == 
hash_table->version' failed
Sep 29 15:12:27 delirium gdm-launch-environment][288414]: GLib-GObject: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed


and some machine information

 >  hostnamectl
 Static hostname: delirium
   Icon name: computer-laptop
 Chassis: laptop
  Machine ID: dc5d74e4a48c4fbb863a6976e32b
 Boot ID: 85559914113641b5983b8204aa86021c
Operating System: Ubuntu 22.04.1 LTS  
  Kernel: Linux 5.15.0-48-generic
Architecture: x86-64
 Hardware Vendor: Lenovo
  Hardware Model: ThinkPad P15 Gen 2i

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

Title:
  GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error
  == NULL' failed

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I see the following errors in the system logs:

  # journalctl | grep gnome-session-binary
  Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: 
GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' 
failed
  Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: 
GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' 
failed
  Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: 
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
  Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: 
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-session-bin 42.0-1ubuntu2
  Uname: Linux 5.17.2-051702-generic x86_64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Apr 13 19:48:49 2022
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed

[Bram Stolk]

The deb does indeed vaapi hw decode for me on Alderlake.

$ LIBVA_TRACE=$HOME/va.log  /usr/bin/chromium-browser-unstable --enable-
logging=stderr   ~/Downloads/*mp4


** Attachment added: "va trace"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620150/+files/va.log.222000.thd-0x00032256

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

Title:
  VA error: resource allocation failed

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  https://github.com/intel/media-driver/issues/1498

  ---

  When I play a H264/AAC video with HW decoding enabled on Alderlake
  12600k, using Wayland I get the error:

  vaCreateSurfaces (import mode) failed, VA error: resource allocation
  failed

  After which, chromium will proceed to play the video without HW
  acceleration using ffmpeg.

  This is both with using the pre-built snap from channel beta/hwacc and
  a snap built from source.

  (NOTE: HW decoding does work with same browser on X11 desktop, using
  VDAVideoDecoder.)

  To get more information on this VA error, I built the snap with debug
  versions of gmmlib and media-driver (latest git) using the latest git
  from valib as well.

  The log output from chromium now mentions why the allocation fails:

  [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
  [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] 
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
  [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
  [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
  [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
  [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder

  Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
  modifier."

  I am on wayland, and use these chromium flags:

  export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
  features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
  features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
  --disable-gpu-driver-bug-workaround --ozone-platform=wayland"

  The video that fails: the 1080p/60 version downloaded from here:
  https://github.com/chthomos/video-media-samples/

  I will figure out which is the "unsupported modifier" and report back,
  here.

  Note: currently gmmlib and media-driver have failing debug builds, but I have 
created pull requests to both:
  https://github.com/intel/media-driver/pull/1491
  https://github.com/intel/gmmlib/pull/97

  CPU: 12600k

  GPU: Intel Alderlake_s (Gen12)

  Snap built with: core20

  Host OS: Ubuntu Kinetic

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


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

[Desktop-packages] [Bug 1991022] Re: [FFe] Socket activation

[Graham Inggs]

Thanks Utkarsh, I agree this looks good, FFe granted.


** Changed in: speech-dispatcher (Ubuntu)
   Status: New => Triaged

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

Title:
  [FFe] Socket activation

Status in speech-dispatcher package in Ubuntu:
  Triaged

Bug description:
  [Description]

  Systemd socket activation for Speech Dispatcher.

    - Creates the speech-dispatcher.socket;
    - Modifies the server so that it can detect it was automatically launched 
by that socket activation; and
    - Modifies the Autotools files accordingly.

  [Rationale]

  It's relevance is described in [1], of which I quote the essential
  parts [my notes in brackets]:

  > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle 
it inside of the sandbox, so that each application has its own "private" 
instance of Speech Dispatcher running. This works more or less, but it has the 
downside that speech dispatcher cannot coordinate simultaneous messages from 
multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same 
time, the text reading overlaps.
  >
  > In order to solve this issue, I would really like to give sandboxed apps 
access to the Speech Dispatcher instance of the host.

  And then,

  > The only issue I see is having it auto launch. I think it would
  probably be a good step forward for speech-dispatcher to be auto
  launched by a systemd socket like other daemons already do on demand.
  That way the host speech-dispatcher with it's configuration would be
  used by all snaps,

  [Additional information]

  The changes are already merged upstream[2], but still not released.

  I have built and installed the package in Kinetic and verified that
  spd-say still causes the dispatcher spawn and emits sound. Upstream
  test can also confirm this.

  [1]: https://github.com/brailcom/speechd/issues/335
  [2]: https://github.com/brailcom/speechd/pull/763

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


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

[Desktop-packages] [Bug 1991022] Re: [FFe] Socket activation

[Utkarsh Gupta]

Hi Nathan,

Thank you for filing the FFe bug. The bug is well documented and
supported via attached logs and diff. Whilst this looks good for FFe,
please wait for an ACK from the actual Release team member. Thanks! \o/

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

Title:
  [FFe] Socket activation

Status in speech-dispatcher package in Ubuntu:
  Triaged

Bug description:
  [Description]

  Systemd socket activation for Speech Dispatcher.

    - Creates the speech-dispatcher.socket;
    - Modifies the server so that it can detect it was automatically launched 
by that socket activation; and
    - Modifies the Autotools files accordingly.

  [Rationale]

  It's relevance is described in [1], of which I quote the essential
  parts [my notes in brackets]:

  > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle 
it inside of the sandbox, so that each application has its own "private" 
instance of Speech Dispatcher running. This works more or less, but it has the 
downside that speech dispatcher cannot coordinate simultaneous messages from 
multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same 
time, the text reading overlaps.
  >
  > In order to solve this issue, I would really like to give sandboxed apps 
access to the Speech Dispatcher instance of the host.

  And then,

  > The only issue I see is having it auto launch. I think it would
  probably be a good step forward for speech-dispatcher to be auto
  launched by a systemd socket like other daemons already do on demand.
  That way the host speech-dispatcher with it's configuration would be
  used by all snaps,

  [Additional information]

  The changes are already merged upstream[2], but still not released.

  I have built and installed the package in Kinetic and verified that
  spd-say still causes the dispatcher spawn and emits sound. Upstream
  test can also confirm this.

  [1]: https://github.com/brailcom/speechd/issues/335
  [2]: https://github.com/brailcom/speechd/pull/763

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


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

[Desktop-packages] [Bug 1991263] Re: duplicate appindicators

[Treviño]

** Description changed:

+ [ Impact ]
+ 
  I'm seeing duplicate appindicators for snaps built with core22, like
  mattermost-desktop and discord.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 22.10
+ [ Test case ]
+ 
+ From shell point of view:
+  - Lock / unlock your desktop multiple times
+ 
+ With applications (both cases must be fixed):
+  1) Electron apps
+ - Install ferdium (https://github.com/ferdium/)
+ - Open it in guest mode, go to settings
+ - Toggle the "Always Show Ferdium in System Tray" option multiple times
+ - Once disabled indicators should go away and be added again
+ 
+  2) KDE Status Notification apps
+ - Download Telegram desktop (snap install telegram-desktop)
+ - Run it with:
+   XDG_CURRENT_DESKTOP=KDE Telegram
+   or
+   XDG_CURRENT_DESKTOP=KDE telegram-desktop
+ - Disable notificationn area icon and enable it again
+ - The icon should be hidden and shown again accordingly
+ 
+ [ Regression potential ]
+ 
+  - Icon could not show at all or with the wrong content
+  - Icon updates may lead to more CPU usage
+  - Updated to icon could not be properly visible
+ 
+ 
+ ProblemType: BugDistroRelease: Ubuntu 22.10
  Package: gnome-shell-extension-appindicator 42-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 29 09:46:07 2022
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (863 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- RebootRequiredPkgs: Error: path contained symlinks.
- SourcePackage: gnome-shell-extension-appindicator
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ RebootRequiredPkgs: Error: path contained symlinks.SourcePackage: 
gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (29 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

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

Title:
  duplicate appindicators

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Jammy:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Kinetic:
  Confirmed

Bug description:
  [ Impact ]

  I'm seeing duplicate appindicators for snaps built with core22, like
  mattermost-desktop and discord.

  [ Test case ]

  From shell point of view:
   - Lock / unlock your desktop multiple times

  With applications (both cases must be fixed):
   1) Electron apps
  - Install ferdium (https://github.com/ferdium/)
  - Open it in guest mode, go to settings
  - Toggle the "Always Show Ferdium in System Tray" option multiple times
  - Once disabled indicators should go away and be added again

   2) KDE Status Notification apps
  - Download Telegram desktop (snap install telegram-desktop)
  - Run it with:
XDG_CURRENT_DESKTOP=KDE Telegram
or
XDG_CURRENT_DESKTOP=KDE telegram-desktop
  - Disable notificationn area icon and enable it again
  - The icon should be hidden and shown again accordingly

  [ Regression potential ]

   - Icon could not show at all or with the wrong content
   - Icon updates may lead to more CPU usage
   - Updated to icon could not be properly visible

  
  ProblemType: BugDistroRelease: Ubuntu 22.10
  Package: gnome-shell-extension-appindicator 42-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 29 09:46:07 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   

[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed

[Bram Stolk]

@helainewang I can confirm that your .deb file indeed plays with HW
decoding on my Alderlake machine, but not via VAAPI.

If I pass:
```
--enable-logging=stderr
--enable-features=VaapiVideoDecoder,VaapiVideoEncoder
--disable-features=UseChromeOSDirectVideoDecoder
```

Then the decoding is in sofware, with the following error from chromium:

```
[188746:188746:0929/141918.619668:ERROR:vaapi_wrapper.cc(2128)] vaCreateContext 
failed, VA error: unknown libva error
[188746:188746:0929/141918.619871:ERROR:vaapi_video_decode_accelerator.cc(726)] 
Failed to create Context
```

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

Title:
  VA error: resource allocation failed

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  https://github.com/intel/media-driver/issues/1498

  ---

  When I play a H264/AAC video with HW decoding enabled on Alderlake
  12600k, using Wayland I get the error:

  vaCreateSurfaces (import mode) failed, VA error: resource allocation
  failed

  After which, chromium will proceed to play the video without HW
  acceleration using ffmpeg.

  This is both with using the pre-built snap from channel beta/hwacc and
  a snap built from source.

  (NOTE: HW decoding does work with same browser on X11 desktop, using
  VDAVideoDecoder.)

  To get more information on this VA error, I built the snap with debug
  versions of gmmlib and media-driver (latest git) using the latest git
  from valib as well.

  The log output from chromium now mentions why the allocation fails:

  [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
  [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] 
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
  [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
  [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
  [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
  [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder

  Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
  modifier."

  I am on wayland, and use these chromium flags:

  export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
  features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
  features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
  --disable-gpu-driver-bug-workaround --ozone-platform=wayland"

  The video that fails: the 1080p/60 version downloaded from here:
  https://github.com/chthomos/video-media-samples/

  I will figure out which is the "unsupported modifier" and report back,
  here.

  Note: currently gmmlib and media-driver have failing debug builds, but I have 
created pull requests to both:
  https://github.com/intel/media-driver/pull/1491
  https://github.com/intel/gmmlib/pull/97

  CPU: 12600k

  GPU: Intel Alderlake_s (Gen12)

  Snap built with: core20

  Host OS: Ubuntu Kinetic

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


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

[Desktop-packages] [Bug 1877038]

[Dschubert]

Folks, while it's great to see there is a lot of interest in this,
please don't post "+1" comments. We know that this is important (it is a
P1, after all) and people are actively working on it. It will be done as
soon as it's done, and posting more comments isn't accelerating that
process.

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

Title:
  [upstream] Firefox lacks FIDO2 support with Yubikeys

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

Bug description:
  Ubuntu LTS versions affected.

  "Passwordless" authentications with Yubikeys using Firefox don't work
  with FIDO2.

  Tested both with the yubikey software packages from the
  bionic/universe repo and those from the vendor https://www.yubico.com/

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


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

[Desktop-packages] [Bug 1877038]

[Drew-dani]

Any updates on the estimated completion date on this P1 item? This bug
has been open for 4 years (since 2/25/2019) and impacting customers from
raising the security bar to migrate to FIDO2 security keys; ultimately
driving millions of users AWAY from using Firefox. Google Chrome,
Microsoft Edge, and Safari support FIDO2 for years now. Also, U2F is a
deprecated API and major security token providers only sell FIDO2
tokens. Currently, Firefox only supports U2F on Mac and Linux, and with
that, this is a critical security blocker.

On a different note, can someone from Mozilla provide a knowledge
transfer so that we understand the blocker and the remaining work? Is
there a feature branch we can test FIDO2 in Firefox on Mac and Linux?
I'm curious to know the current state of the FIDO2 support in Firefox.
Thanks.

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

Title:
  [upstream] Firefox lacks FIDO2 support with Yubikeys

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

Bug description:
  Ubuntu LTS versions affected.

  "Passwordless" authentications with Yubikeys using Firefox don't work
  with FIDO2.

  Tested both with the yubikey software packages from the
  bionic/universe repo and those from the vendor https://www.yubico.com/

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


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

[Desktop-packages] [Bug 1877038]

[purtpelhcs]

Currently Microsoft doesn't support FIDO2 keys while using firefox on linux or 
MacOS.
(see 
https://learn.microsoft.com/en-us/azure/active-directory/authentication/fido2-compatibility)
Just for my understanding: Would resolving this bug result in MS being able to 
support FIDO on linux/MacOS?

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

Title:
  [upstream] Firefox lacks FIDO2 support with Yubikeys

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

Bug description:
  Ubuntu LTS versions affected.

  "Passwordless" authentications with Yubikeys using Firefox don't work
  with FIDO2.

  Tested both with the yubikey software packages from the
  bionic/universe repo and those from the vendor https://www.yubico.com/

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


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

[Desktop-packages] [Bug 1877038]

[Neumaif02-k]

(In reply to Christian from comment #29)
> Just for my understanding: Would resolving this bug result in MS being able 
> to support FIDO on linux/MacOS?
It would, at least if MS allows the User Agent of Firefox for Mac/Linux to see 
this feature (otherwise you would have to switch your user agent) like they 
didn't do with Safari.

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

Title:
  [upstream] Firefox lacks FIDO2 support with Yubikeys

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

Bug description:
  Ubuntu LTS versions affected.

  "Passwordless" authentications with Yubikeys using Firefox don't work
  with FIDO2.

  Tested both with the yubikey software packages from the
  bionic/universe repo and those from the vendor https://www.yubico.com/

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


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

[Desktop-packages] [Bug 1877038]

[Paul Schreiber]

+1 would like to see this. We ran into this problem with Microsoft +
Firefox on Linux yesterday.

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

Title:
  [upstream] Firefox lacks FIDO2 support with Yubikeys

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

Bug description:
  Ubuntu LTS versions affected.

  "Passwordless" authentications with Yubikeys using Firefox don't work
  with FIDO2.

  Tested both with the yubikey software packages from the
  bionic/universe repo and those from the vendor https://www.yubico.com/

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


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

[Desktop-packages] [Bug 1991333] [NEW] Night light is not available in gnome-control-center despite being enabled in quick settings

[Nicolás Abel Carbone]

Public bug reported:

In the gnome-control-center, under Monitors->Night light, there is a
banner saying that night light is not available and "that may be the
result of the graphics driver or that you are using remote desktop"
(loosely translated from Spanish, see screenshot). None of that is true
and Night light worked fine before updating to 22.10 beta.

Moreover, night light was setup to activate at dusk before updating and
that seems to be working. It can even be toggled using the quick
settings.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-control-center 1:43.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 29 18:17:51 2022
InstallationDate: Installed on 2022-02-02 (239 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago)

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


** Tags: amd64 apport-bug kinetic third-party-packages wayland-session

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1991333/+attachment/5620139/+files/Captura%20desde%202022-09-29%2018-19-32.png

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

Title:
  Night light is not available in gnome-control-center despite being
  enabled in quick settings

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

Bug description:
  In the gnome-control-center, under Monitors->Night light, there is a
  banner saying that night light is not available and "that may be the
  result of the graphics driver or that you are using remote desktop"
  (loosely translated from Spanish, see screenshot). None of that is
  true and Night light worked fine before updating to 22.10 beta.

  Moreover, night light was setup to activate at dusk before updating
  and that seems to be working. It can even be toggled using the quick
  settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 29 18:17:51 2022
  InstallationDate: Installed on 2022-02-02 (239 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago)

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


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

[Desktop-packages] [Bug 1991293] Re: sane-backends 1.1.1-5 FTBFS

[Bug Watch Updater]

** Changed in: sane-backends
   Status: Unknown => New

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

Title:
  sane-backends 1.1.1-5 FTBFS

Status in sane-backends:
  New
Status in sane-backends package in Ubuntu:
  Fix Committed
Status in sane-backends package in Debian:
  Confirmed

Bug description:
  FTBFS[1]:

  --->
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::Pixel’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::RawPixel’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::PixelFormat’)
  <---

  Since this happens in testsuite/, my suggested workaround is to simply
  disable the offending call, responsible for a diagnostic message.

  [1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic-
  amd64.sane-backends_1.1.1-5_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1991293/+subscriptions


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

[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'

[Chris Iverach-Brereton]

I was about to file a new bug report about this issue.

It appears the ubuntu-drivers-common package is missing a dependency on
alsa-utils (which provides the aplay command).

The problem can be fixed by running

```
sudo apt-get install alsa-utils
```

but ideally the ubuntu-drivers-common package should be modified to:

1) depend on alsa-utils
2) have better exception-handling for situations where `aplay` isn't installed
3) ideally both

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

Title:
  Traceback during 'ubuntu-drivers list'

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

Bug description:
  ubuntu@doubletusk:~$ sudo ubuntu-drivers list
  ERROR:root:could not open aplay -l
  Traceback (most recent call last):
File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in 
detect
  aplay = subprocess.Popen(
File "/usr/lib/python3.8/subprocess.py", line 858, in __init__
  self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child
  raise child_exception_type(errno_num, err_msg, err_filename)
  FileNotFoundError: [Errno 2] No such file or directory: 'aplay'
  nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server)
  nvidia-driver-470, (kernel modules provided by nvidia-dkms-470)
  nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server)
  nvidia-driver-465, (kernel modules provided by nvidia-dkms-465)
  nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server)
  nvidia-driver-460, (kernel modules provided by nvidia-dkms-460)
  ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common
  ubuntu-drivers-common:
Installed: 1:0.9.0~0.20.04.1
Candidate: 1:0.9.0~0.20.04.1
Version table:
   *** 1:0.9.0~0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.8.6.5~0.20.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   1:0.8.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  ubuntu@doubletusk:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

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


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

[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'

[Launchpad Bug Tracker]

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

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

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

Title:
  Traceback during 'ubuntu-drivers list'

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

Bug description:
  ubuntu@doubletusk:~$ sudo ubuntu-drivers list
  ERROR:root:could not open aplay -l
  Traceback (most recent call last):
File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in 
detect
  aplay = subprocess.Popen(
File "/usr/lib/python3.8/subprocess.py", line 858, in __init__
  self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child
  raise child_exception_type(errno_num, err_msg, err_filename)
  FileNotFoundError: [Errno 2] No such file or directory: 'aplay'
  nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server)
  nvidia-driver-470, (kernel modules provided by nvidia-dkms-470)
  nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server)
  nvidia-driver-465, (kernel modules provided by nvidia-dkms-465)
  nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server)
  nvidia-driver-460, (kernel modules provided by nvidia-dkms-460)
  ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common
  ubuntu-drivers-common:
Installed: 1:0.9.0~0.20.04.1
Candidate: 1:0.9.0~0.20.04.1
Version table:
   *** 1:0.9.0~0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.8.6.5~0.20.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   1:0.8.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  ubuntu@doubletusk:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

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


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

[Desktop-packages] [Bug 1991293] Re: sane-backends 1.1.1-5 FTBFS

[Gunnar Hjalmarsson]

The issue has been reported upstream, but they don't seem to have
addressed it yet.

Sponsored to the kinetic unapproved queue. Thanks!

** Changed in: sane-backends (Ubuntu)
   Status: New => Fix Committed

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

Title:
  sane-backends 1.1.1-5 FTBFS

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  Fix Committed
Status in sane-backends package in Debian:
  Confirmed

Bug description:
  FTBFS[1]:

  --->
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::Pixel’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::RawPixel’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::PixelFormat’)
  <---

  Since this happens in testsuite/, my suggested workaround is to simply
  disable the offending call, responsible for a diagnostic message.

  [1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic-
  amd64.sane-backends_1.1.1-5_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1991293/+subscriptions


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

[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed

[Qinling Wang]

Validated HW decoding working fine with chromium-browser-
unstable_104.0.5112.101-1_amd64.deb as the attached picture. Tested on
Wayland.

** Attachment removed: "HW decoding working with Chromium Browser"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620117/+files/HW-Decording-working.png

** Attachment added: "HW decoding working with Chromium Browser"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620118/+files/HW-Decording-working.png

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

Title:
  VA error: resource allocation failed

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  https://github.com/intel/media-driver/issues/1498

  ---

  When I play a H264/AAC video with HW decoding enabled on Alderlake
  12600k, using Wayland I get the error:

  vaCreateSurfaces (import mode) failed, VA error: resource allocation
  failed

  After which, chromium will proceed to play the video without HW
  acceleration using ffmpeg.

  This is both with using the pre-built snap from channel beta/hwacc and
  a snap built from source.

  (NOTE: HW decoding does work with same browser on X11 desktop, using
  VDAVideoDecoder.)

  To get more information on this VA error, I built the snap with debug
  versions of gmmlib and media-driver (latest git) using the latest git
  from valib as well.

  The log output from chromium now mentions why the allocation fails:

  [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
  [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] 
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
  [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
  [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
  [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
  [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder

  Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
  modifier."

  I am on wayland, and use these chromium flags:

  export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
  features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
  features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
  --disable-gpu-driver-bug-workaround --ozone-platform=wayland"

  The video that fails: the 1080p/60 version downloaded from here:
  https://github.com/chthomos/video-media-samples/

  I will figure out which is the "unsupported modifier" and report back,
  here.

  Note: currently gmmlib and media-driver have failing debug builds, but I have 
created pull requests to both:
  https://github.com/intel/media-driver/pull/1491
  https://github.com/intel/gmmlib/pull/97

  CPU: 12600k

  GPU: Intel Alderlake_s (Gen12)

  Snap built with: core20

  Host OS: Ubuntu Kinetic

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


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

[Desktop-packages] [Bug 1991263] Re: duplicate appindicators

[Ken VanDine]

** Changed in: gnome-shell-extension-appindicator (Ubuntu Jammy)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

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

Title:
  duplicate appindicators

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Jammy:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Kinetic:
  Confirmed

Bug description:
  I'm seeing duplicate appindicators for snaps built with core22, like
  mattermost-desktop and discord.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell-extension-appindicator 42-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 29 09:46:07 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (863 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (29 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

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


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

[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed

[Qinling Wang]

** Attachment added: "HW decoding working with Chromium Browser"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620117/+files/HW-Decording-working.png

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

Title:
  VA error: resource allocation failed

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  https://github.com/intel/media-driver/issues/1498

  ---

  When I play a H264/AAC video with HW decoding enabled on Alderlake
  12600k, using Wayland I get the error:

  vaCreateSurfaces (import mode) failed, VA error: resource allocation
  failed

  After which, chromium will proceed to play the video without HW
  acceleration using ffmpeg.

  This is both with using the pre-built snap from channel beta/hwacc and
  a snap built from source.

  (NOTE: HW decoding does work with same browser on X11 desktop, using
  VDAVideoDecoder.)

  To get more information on this VA error, I built the snap with debug
  versions of gmmlib and media-driver (latest git) using the latest git
  from valib as well.

  The log output from chromium now mentions why the allocation fails:

  [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
  [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] 
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
  [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
  [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
  [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
  [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder

  Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
  modifier."

  I am on wayland, and use these chromium flags:

  export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
  features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
  features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
  --disable-gpu-driver-bug-workaround --ozone-platform=wayland"

  The video that fails: the 1080p/60 version downloaded from here:
  https://github.com/chthomos/video-media-samples/

  I will figure out which is the "unsupported modifier" and report back,
  here.

  Note: currently gmmlib and media-driver have failing debug builds, but I have 
created pull requests to both:
  https://github.com/intel/media-driver/pull/1491
  https://github.com/intel/gmmlib/pull/97

  CPU: 12600k

  GPU: Intel Alderlake_s (Gen12)

  Snap built with: core20

  Host OS: Ubuntu Kinetic

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


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

[Desktop-packages] [Bug 1845362] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()

[Sean Davis]

This appears to be fixed in gnome-font-viewer 43.0-1 on the Xubuntu
22.10 beta.

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

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

Title:
  gnome-font-viewer crashed with signal 5 in _XEventsQueued()

Status in gnome-font-viewer package in Ubuntu:
  Fix Released
Status in gnome-font-viewer package in Debian:
  New

Bug description:
  Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of
  application during ISO testing of a live-session.

  Application will crash if there is an attempt to close it or scroll
  through fonts. On one occasion my laptop was rendered unusable when
  Firefox was launched while trying to report the crash to Launchpad.

  After the bug report has been sent gnome-font-viewer will freeze when
  automatically restarted. No fonts are displayed.

  Work around
  ---
  gnome-font-viewer appears to start correctly when started from the command 
line of my Ubuntu 20.04 installation. Then subsequent attempts to start the 
program succeed when started from the dock or the Application Overview.

  I have found that this work around wasn't necessary when using Xubuntu
  20.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.416
  CurrentDesktop: XFCE
  Date: Wed Sep 25 17:34:17 2019
  ExecutablePath: /usr/bin/gnome-font-viewer
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  ProcCmdline: gnome-font-viewer
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-font-viewer
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 1991325] [NEW] xeyes app only tracks mouse pointer when its in a window

[Paul Pierce]

Public bug reported:

The xeyes app only tracks the mouse pointer when the pointer is in a
window on the workspace in which the xeyes app was started. When you set
xeyes to be visible on all workspaces, there is no tracking when viewing
any other workspace than the original one. I am seeing several other
mouse hover problems and differences from before the upgrade. I recently
let the system upgrade itself from 20.x LTS to 22.x LTS.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: x11-apps 7.7+8build2
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 29 12:16:52 2022
DistUpgraded: 2022-09-03 12:03:40,568 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExecutablePath: /usr/bin/xeyes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 5100] 
[1002:67c7] (prog-if 00 [VGA controller])
   Subsystem: Dell Ellesmere [Radeon Pro WX 5100] [1028:0b0d]
InstallationDate: Installed on 2021-06-18 (467 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Gigabyte Technology Co., Ltd. TRX40 AORUS PRO WIFI
ProcEnviron:
 LD_LIBRARY_PATH=
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-48-generic 
root=UUID=e478506b-beb8-4fa5-8d81-b0740312bf39 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: x11-apps
UpgradeStatus: Upgraded to jammy on 2022-09-03 (26 days ago)
dmi.bios.date: 04/12/2021
dmi.bios.release: 5.15
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: FBi
dmi.board.asset.tag: Default string
dmi.board.name: TRX40 AORUS PRO WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFBi:bd04/12/2021:br5.15:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: TRX40 AORUS PRO WIFI
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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

** Affects: x11-apps (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  xeyes app only tracks mouse pointer when its in a window

Status in x11-apps package in Ubuntu:
  New

Bug description:
  The xeyes app only tracks the mouse pointer when the pointer is in a
  window on the workspace in which the xeyes app was started. When you
  set xeyes to be visible on all workspaces, there is no tracking when
  viewing any other workspace than the original one. I am seeing several
  other mouse hover problems and differences from before the upgrade. I
  recently let the system upgrade itself from 20.x LTS to 22.x LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: x11-apps 7.7+8build2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 29 12:16:52 2022
  DistUpgraded: 2022-09-03 12:03:40,568 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/xeyes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 5100] 
[1002:67c7] (prog-if 00 [VGA controller])
 Subsystem: 

[Desktop-packages] [Bug 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all

[Bug Watch Updater]

** Bug watch added: Linux Kernel Bug Tracker #205755
   https://bugzilla.kernel.org/show_bug.cgi?id=205755

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Desktop-packages] [Bug 1958019]

[soyer]

(In reply to Marko from comment #694)
> Thanks for the tip Gergo!
> I disable the sound power management with the tlp.service and set the
> i2c-register with a own customboot.service after the tlp.service is started.
> It works for now :o)
> 
> /root/bass-speaker-on.sh
> #!/usr/bin/env bash
> /usr/sbin/i2cset -y 3 0x48 0x2 0
> 
> /etc/systemd/system/customboot.service
> [Unit]
> Description=Custom Bootup Script
> After=tlp.service
> [Service]
> ExecStart=/root/bass-speaker-on.sh
> [Install]
> WantedBy=default.target
> 
> /etc/tlp.conf
> SOUND_POWER_SAVE_ON_AC=0
> SOUND_POWER_SAVE_ON_BAT=0
> SOUND_POWER_SAVE_CONTROLLER=N

One thing to protect your speakers. It's a 6W amplifier so the default gain may 
be too much. I didn't dump the registers in windows yet, but in the limited 
sound on c940 issue ( https://bugzilla.kernel.org/show_bug.cgi?id=205755 ) they 
write about 11 dB for a 2W bass speaker.
I think that's a different amplifier, so the register values may not match.
Please add
i2cset -y 3 0x48 0x3 0x00
to your script until the windows dump is done.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Desktop-packages] [Bug 1958019]

[dr.tikkel]

Thanks for the tip Gergo!
I disable the sound power management with the tlp.service and set the 
i2c-register with a own customboot.service after the tlp.service is started.
It works for now :o)

/root/bass-speaker-on.sh
#!/usr/bin/env bash
/usr/sbin/i2cset -y 3 0x48 0x2 0

/etc/systemd/system/customboot.service
[Unit]
Description=Custom Bootup Script
After=tlp.service
[Service]
ExecStart=/root/bass-speaker-on.sh
[Install]
WantedBy=default.target

/etc/tlp.conf
SOUND_POWER_SAVE_ON_AC=0
SOUND_POWER_SAVE_ON_BAT=0
SOUND_POWER_SAVE_CONTROLLER=N

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Desktop-packages] [Bug 1958019]

[soyer]

(In reply to Marko from comment #691)
> (In reply to Gergo K from comment #689)
> > The TAS2563 works without the firmware (tuning file).
> > Documentation:
> > https://www.ti.com/product/TAS2553
> > 
> > However there is an android driver with firmware loading support.
> > https://git.ti.com/cgit/tas256xsw-android/tas2563-android-driver/
> > Or a mainline RFC:
> > https://lkml.org/lkml/2020/6/9/800
> > 
> > 
> > The bass speakers can be enabled with:
> > i2cset 3 0x4c 0x2 0
> > i2cset 3 0x4d 0x2 0
> > 
> > they are listening on 0x48 too, so in one turn:
> > i2cset 3 0x48 0x2 0
> > 
> > I don't know how safe it is to use it this way.
> > 
> > They have to be enabled after suspend, and if you plug in-out the headphone
> > (only if auto mute is enabled).
> 
> OK, that works! But what can I do to make this register (3 0x38 0x02 0) set
> automatically?
> Does that have something to do with the power settings under
> /sys/bus/i2c/devices/i2c-3/device/power/*?

I think you can run it with systemd after resume/hibernate/boot while I
write a driver for it.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Desktop-packages] [Bug 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/430690

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

Title:
  Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

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

Bug description:
  1) lsb_release -rd

  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04
  (Kubuntu Jammy live session in QEMU VM)

  2) apt-cache policy ubuntu-release-upgrader-core
  ubuntu-release-upgrader-core:
    Installed: 1:22.04.6

  3) expected

  (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.)

  * Firefox icon on panel to be intact.
  * Clicked icon launches browser.
  * Icon tooltip/mouse hover to describe application.

  4) happened instead

  * Icon is missing/replaced with a generic icon
  * Icon click produces error notification "Plasma Workspace - 
preferred://browser"
  * Icon tooltip/mouse hover appears, though is blank.

  Additional info:
  * firefox is still installed, works as expected.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-07 (2 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: ubuntu-release-upgrader (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1991293] Re: sane-backends 1.1.1-5 FTBFS

[Bug Watch Updater]

** Changed in: sane-backends (Debian)
   Status: Unknown => Confirmed

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

Title:
  sane-backends 1.1.1-5 FTBFS

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  New
Status in sane-backends package in Debian:
  Confirmed

Bug description:
  FTBFS[1]:

  --->
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::Pixel’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::RawPixel’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::PixelFormat’)
  <---

  Since this happens in testsuite/, my suggested workaround is to simply
  disable the offending call, responsible for a diagnostic message.

  [1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic-
  amd64.sane-backends_1.1.1-5_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1991293/+subscriptions


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

[Desktop-packages] [Bug 1991293] Re: sane-backends 1.1.1-5 FTBFS

[Gunnar Hjalmarsson]

** Bug watch added: Debian Bug tracker #1013034
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013034

** Also affects: sane-backends (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013034
   Importance: Unknown
   Status: Unknown

** Bug watch added: gitlab.com/sane-project/backends/-/issues #597
   https://gitlab.com/sane-project/backends/-/issues/597

** Also affects: sane-backends via
   https://gitlab.com/sane-project/backends/-/issues/597
   Importance: Unknown
   Status: Unknown

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

Title:
  sane-backends 1.1.1-5 FTBFS

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  New
Status in sane-backends package in Debian:
  Unknown

Bug description:
  FTBFS[1]:

  --->
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::Pixel’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::RawPixel’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::PixelFormat’)
  <---

  Since this happens in testsuite/, my suggested workaround is to simply
  disable the offending call, responsible for a diagnostic message.

  [1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic-
  amd64.sane-backends_1.1.1-5_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1991293/+subscriptions


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

Re: [Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed

[Nathan Teodosio]

> ** Attachment added: "chromium-browser-unstable_104.0.5112.101-1_amd64"
> 
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620071/+files/chromium-browser-unstable_104.0.5112.101-1_amd64.deb
>  

Thanks Qinling.

Playback is software accelerated as verified in about:media-internals 
(kDecoderName is FfmpegVideoDecoder).

Tested on Wayland. Execution log is attached.

--->
% vainfo
libva info: VA-API version 1.15.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.15 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.4.3 ()
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
  VAProfileVP8Version0_3  : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile2: VAEntrypointVLD
<---

** Attachment added: "log"
   https://bugs.launchpad.net/bugs/1990010/+attachment/5620076/+files/log

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

Title:
  VA error: resource allocation failed

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  https://github.com/intel/media-driver/issues/1498

  ---

  When I play a H264/AAC video with HW decoding enabled on Alderlake
  12600k, using Wayland I get the error:

  vaCreateSurfaces (import mode) failed, VA error: resource allocation
  failed

  After which, chromium will proceed to play the video without HW
  acceleration using ffmpeg.

  This is both with using the pre-built snap from channel beta/hwacc and
  a snap built from source.

  (NOTE: HW decoding does work with same browser on X11 desktop, using
  VDAVideoDecoder.)

  To get more information on this VA error, I built the snap with debug
  versions of gmmlib and media-driver (latest git) using the latest git
  from valib as well.

  The log output from chromium now mentions why the allocation fails:

  [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
  [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] 
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
  [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
  [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
  [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
  [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder

  Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
  modifier."

  I am on wayland, and use these chromium flags:

  export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
  features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
  features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
  --disable-gpu-driver-bug-workaround --ozone-platform=wayland"

  The video that fails: the 1080p/60 version downloaded from here:
  https://github.com/chthomos/video-media-samples/

  I will figure out which is the "unsupported modifier" and report back,
  here.

  Note: currently gmmlib and media-driver have failing debug 

[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed

[Qinling Wang]

Could you please test the attached chromium-browser-
unstable_104.0.5112.101-1_amd64.deb? Thank you!

** Attachment added: "chromium-browser-unstable_104.0.5112.101-1_amd64"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620071/+files/chromium-browser-unstable_104.0.5112.101-1_amd64.deb

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

Title:
  VA error: resource allocation failed

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  https://github.com/intel/media-driver/issues/1498

  ---

  When I play a H264/AAC video with HW decoding enabled on Alderlake
  12600k, using Wayland I get the error:

  vaCreateSurfaces (import mode) failed, VA error: resource allocation
  failed

  After which, chromium will proceed to play the video without HW
  acceleration using ffmpeg.

  This is both with using the pre-built snap from channel beta/hwacc and
  a snap built from source.

  (NOTE: HW decoding does work with same browser on X11 desktop, using
  VDAVideoDecoder.)

  To get more information on this VA error, I built the snap with debug
  versions of gmmlib and media-driver (latest git) using the latest git
  from valib as well.

  The log output from chromium now mentions why the allocation fails:

  [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
  [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] 
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
  [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
  [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
  [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
  [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder

  Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
  modifier."

  I am on wayland, and use these chromium flags:

  export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
  features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
  features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
  --disable-gpu-driver-bug-workaround --ozone-platform=wayland"

  The video that fails: the 1080p/60 version downloaded from here:
  https://github.com/chthomos/video-media-samples/

  I will figure out which is the "unsupported modifier" and report back,
  here.

  Note: currently gmmlib and media-driver have failing debug builds, but I have 
created pull requests to both:
  https://github.com/intel/media-driver/pull/1491
  https://github.com/intel/gmmlib/pull/97

  CPU: 12600k

  GPU: Intel Alderlake_s (Gen12)

  Snap built with: core20

  Host OS: Ubuntu Kinetic

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


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

[Desktop-packages] [Bug 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf

[Lorenzo Natali]

I applied the same solution found here 
https://bugs.chromium.org/p/chromium/issues/detail?id=1315684#c17 using 
dconf-editor to turn to false org/gnome/desktop/sound/input-feedkback-sounds 
and this worked for me, 
The other solutions (installing portal, disabling hardware acceleration) didn't 
worked, but this seems to work.

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

Title:
  Brave & Chrome browsers freezes on download and print to pdf

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Whenever any file is downloaded, the browser will freeze. Download
  files, from any page does not work. Same issue with Firefox.

  Similarly, the browser will freeze when a page is printed to pdf.

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


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

[Desktop-packages] [Bug 1991293] [NEW] sane-backends 1.1.1-5 FTBFS

[Nathan Teodosio]

Public bug reported:

FTBFS[1]:

--->
minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::Pixel’)
minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::RawPixel’)
minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::PixelFormat’)
<---

Since this happens in testsuite/, my suggested workaround is to simply
disable the offending call, responsible for a diagnostic message.

[1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic-
amd64.sane-backends_1.1.1-5_BUILDING.txt.gz

** Affects: sane-backends (Ubuntu)
 Importance: High
 Assignee: Nathan Teodosio (nteodosio)
 Status: New


** Tags: patch

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

Title:
  sane-backends 1.1.1-5 FTBFS

Status in sane-backends package in Ubuntu:
  New

Bug description:
  FTBFS[1]:

  --->
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::Pixel’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::RawPixel’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::PixelFormat’)
  <---

  Since this happens in testsuite/, my suggested workaround is to simply
  disable the offending call, responsible for a diagnostic message.

  [1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic-
  amd64.sane-backends_1.1.1-5_BUILDING.txt.gz

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


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

[Desktop-packages] [Bug 1991293] Re: sane-backends 1.1.1-5 FTBFS

[Nathan Teodosio]

To-do is to submit a proper fix upstream, which likely involves
overloading the << operator for the offending types.

** Patch added: "sane-backends.diff"
   
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1991293/+attachment/5620060/+files/sane-backends.diff

** Changed in: sane-backends (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

** Changed in: sane-backends (Ubuntu)
   Importance: Undecided => High

** Tags added: patch

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

Title:
  sane-backends 1.1.1-5 FTBFS

Status in sane-backends package in Ubuntu:
  New

Bug description:
  FTBFS[1]:

  --->
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const std::vector’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::Pixel’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::RawPixel’)
  minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are 
‘std::basic_ostream’ and ‘const genesys::PixelFormat’)
  <---

  Since this happens in testsuite/, my suggested workaround is to simply
  disable the offending call, responsible for a diagnostic message.

  [1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic-
  amd64.sane-backends_1.1.1-5_BUILDING.txt.gz

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


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

[Desktop-packages] [Bug 1990986] Re: With iwd, doesn't connect to WPA2 Enterprise network (e.g. eduroam)

[Alexander Browne]

Reopening as suggested on the Ubuntu forum, so this issue can be looked
at before iwd becomes default.


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

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

Title:
  With iwd, doesn't connect to WPA2 Enterprise network (e.g. eduroam)

Status in iwd package in Ubuntu:
  New

Bug description:
  I believe my Kinetic system installed iwd with updates today, and now
  I am unable to my University's WPA2 Enterprise network eduroam. There
  is a no graphical error message, it just never connects. I tried
  forgetting the network and re-adding, and again there's no error, but
  no connection is established. Looking in the Logs app, I see messages
  like "Failed to add new connection: (5) 802.1x connections must have
  IWD provisioning files".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: iwd 1.30-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 27 09:32:38 2022
  InstallationDate: Installed on 2022-08-25 (32 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220825)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: iwd
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1989508] Re: hp-plugin unable to load plugin.conf

[Launchpad Bug Tracker]

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

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

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

Title:
  hp-plugin unable to load plugin.conf

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in hplip package in Fedora:
  Confirmed

Bug description:
  Linux hp-plugin fails on Fedora 35 with the error:

  error: Plugin download failed with error code = 8
  error:  file does not match its checksum. File may have been corrupted or 
altered

  When running "hp-plugin -l debug" the reason turns out to be that
  http://hplip.sourceforge.net/plugin.conf does not exist:

  hp-plugin[540794]: debug: wget returned: 0
  hp-plugin[540794]: debug: --2022-09-13 23:23:02--  
http://hplip.sf.net/plugin.conf
  Resolving hplip.sf.net (hplip.sf.net)... 204.68.111.100
  Connecting to hplip.sf.net (hplip.sf.net)|204.68.111.100|:80... connected.
  HTTP request sent, awaiting response... 301 Moved Permanently
  Location: http://hplip.sourceforge.net/plugin.conf [following]
  --2022-09-13 23:23:02--  http://hplip.sourceforge.net/plugin.conf
  Resolving hplip.sourceforge.net (hplip.sourceforge.net)... 204.68.111.100
  Reusing existing connection to hplip.sf.net:80.
  HTTP request sent, awaiting response... 404 Not Found
  2022-09-13 23:23:02 ERROR 404: Not Found.

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


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

[Desktop-packages] [Bug 1989508] Re: hp-plugin unable to load plugin.conf

[Rai Biason Toffoletto]

I can confirm I'm encountering the same problem with hplip 3.21.12 on
ubuntu 22.04.1. Tryed even to get the newest version from SF, but the
same error. Running hp-plugin -i -g shows me a series of 301s and then a
404 fail on the mentioned config file.

Wouldn't it be better to move this configuration file to
openprinting.org instead of trusting SF? apparently the plugins are
being downloaded from there, so it makes sense to keep it in the same
server!?

Also... any plans in porting the plugin/hplip to python3? or is it be
done?

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

Title:
  hp-plugin unable to load plugin.conf

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in hplip package in Fedora:
  Confirmed

Bug description:
  Linux hp-plugin fails on Fedora 35 with the error:

  error: Plugin download failed with error code = 8
  error:  file does not match its checksum. File may have been corrupted or 
altered

  When running "hp-plugin -l debug" the reason turns out to be that
  http://hplip.sourceforge.net/plugin.conf does not exist:

  hp-plugin[540794]: debug: wget returned: 0
  hp-plugin[540794]: debug: --2022-09-13 23:23:02--  
http://hplip.sf.net/plugin.conf
  Resolving hplip.sf.net (hplip.sf.net)... 204.68.111.100
  Connecting to hplip.sf.net (hplip.sf.net)|204.68.111.100|:80... connected.
  HTTP request sent, awaiting response... 301 Moved Permanently
  Location: http://hplip.sourceforge.net/plugin.conf [following]
  --2022-09-13 23:23:02--  http://hplip.sourceforge.net/plugin.conf
  Resolving hplip.sourceforge.net (hplip.sourceforge.net)... 204.68.111.100
  Reusing existing connection to hplip.sf.net:80.
  HTTP request sent, awaiting response... 404 Not Found
  2022-09-13 23:23:02 ERROR 404: Not Found.

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


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

[Desktop-packages] [Bug 1990705] Re: Doesn't autoconnect to wifi using iwd

[Daniel van Vugt]

Sounds like an explanation/fix for bug 1990891?

** Tags added: kinetic

** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1091
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1091

** Also affects: network-manager via
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1091
   Importance: Unknown
   Status: Unknown

** Changed in: iwd (Ubuntu)
 Assignee: (unassigned) => Heather Ellsworth (hellsworth)

** Changed in: iwd (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
   Doesn't autoconnect to wifi using iwd

Status in NetworkManager:
  Unknown
Status in iwd package in Ubuntu:
  In Progress

Bug description:
  If you create your wireless connection with wpa_supplicant, then the
  /etc/NetworkManager/system-connections/.network lists the
  "interface-name". But then when you install iwd, it becomes the
  handler of wireless networks and changes the network interface name
  without updating the name (or removing it) from the .network file.

  The upstream bug is
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1091

  Filed the launchpad bug in iwd because an iwd post-install script will
  be the proposed solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1990705/+subscriptions


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

[Desktop-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless

[Daniel van Vugt]

Fix in bug 1990705?

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

Title:
  after today's Kinetic updates, WiFi no longer working, so laptop
  basically useless

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  ThinkPad X1 Carbon 6th Gen
  WiFi was working fine.
  Installed today's batch of Kinetic updates.
  Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad 
USB dongle and plug into my router to be able to submit this bug report).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 17:09:25 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-16 (1137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 
100 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 
metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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


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

[Desktop-packages] [Bug 1186702] Re: WebDAV: LibreOffice does not handle vnd.sun.star.webdav protocol out-of-the-box

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Confirmed => Fix Released

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

Title:
  WebDAV: LibreOffice does not handle vnd.sun.star.webdav protocol out-
  of-the-box

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Libreoffice is able to open documents located on a WebDAV server if provided 
with an URL starting with the vnd.sun.star.webdav protocol.
  (for instance: vnd.sun.star.webdav://example.com/webdav/my-document.odt )

  Unfortunately, after installing Libreoffice on Ubuntu these URL aren't still 
handled correctly.
  Whether you click on a link in your browser or you try to open the URL from 
the command line with xdg-open vnd.sun.star.webdav://... you get a message 
saying that this protocol is unknown.

  What I expected was that LibreOffice would start and would open the
  document.

  A workaround is to create a Desktop file with the following informations:
  [Desktop Entry]
  Name=WebDav LibreOffice
  Exec=/usr/bin/libreoffice %u
  Type=Application
  Terminal=false
  Categories=System;
  MimeType=x-scheme-handler/vnd.sun.star.webdav;

  and then to copy it in /usr/share/applications
  Afterwards you have to run sudo update-desktop-database so that Ubuntu will 
take the new protocol into account.

  A more definitive solution would be to modify the libreoffice-base
  Desktop file that comes with libreoffice (also located in
  /usr/share/applications) to add the MimeType properties described
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Sun Jun  2 11:51:56 2013
  InstallationDate: Installed on 2013-05-12 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release i386 
(20130424)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1186702/+subscriptions


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

[Desktop-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless

[Daniel van Vugt]

You can't uninstall wpasupplicant because that removes ubuntu-desktop.
Removing /etc/NetworkManager/conf.d/iwd.conf works though.

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

Title:
  after today's Kinetic updates, WiFi no longer working, so laptop
  basically useless

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  ThinkPad X1 Carbon 6th Gen
  WiFi was working fine.
  Installed today's batch of Kinetic updates.
  Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad 
USB dongle and plug into my router to be able to submit this bug report).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 17:09:25 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-16 (1137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 
100 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 
metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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


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

[Desktop-packages] [Bug 1186702]

[Samuel-mehrbrodt-6]

This has been fixed with 1bc454a2c0cb0dd69512d69ddd2123a44814197e .

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

Title:
  WebDAV: LibreOffice does not handle vnd.sun.star.webdav protocol out-
  of-the-box

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Libreoffice is able to open documents located on a WebDAV server if provided 
with an URL starting with the vnd.sun.star.webdav protocol.
  (for instance: vnd.sun.star.webdav://example.com/webdav/my-document.odt )

  Unfortunately, after installing Libreoffice on Ubuntu these URL aren't still 
handled correctly.
  Whether you click on a link in your browser or you try to open the URL from 
the command line with xdg-open vnd.sun.star.webdav://... you get a message 
saying that this protocol is unknown.

  What I expected was that LibreOffice would start and would open the
  document.

  A workaround is to create a Desktop file with the following informations:
  [Desktop Entry]
  Name=WebDav LibreOffice
  Exec=/usr/bin/libreoffice %u
  Type=Application
  Terminal=false
  Categories=System;
  MimeType=x-scheme-handler/vnd.sun.star.webdav;

  and then to copy it in /usr/share/applications
  Afterwards you have to run sudo update-desktop-database so that Ubuntu will 
take the new protocol into account.

  A more definitive solution would be to modify the libreoffice-base
  Desktop file that comes with libreoffice (also located in
  /usr/share/applications) to add the MimeType properties described
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Sun Jun  2 11:51:56 2013
  InstallationDate: Installed on 2013-05-12 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release i386 
(20130424)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1186702/+subscriptions


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

[Desktop-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless

[Daniel van Vugt]

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  after today's Kinetic updates, WiFi no longer working, so laptop
  basically useless

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  ThinkPad X1 Carbon 6th Gen
  WiFi was working fine.
  Installed today's batch of Kinetic updates.
  Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad 
USB dongle and plug into my router to be able to submit this bug report).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 17:09:25 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-16 (1137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 
100 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 
metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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


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

[Desktop-packages] [Bug 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

[Simon Iremonger]

Thunderbird in Ubuntu is now lagging-behind on Security, Debian have released 
102.3.0 as an LTS update, ubuntu version is some versions behind in 91.x ..
https://www.ubuntuupdates.org/ppa/ubuntu_mozilla_security  would suggest 
102.2.2 at least started to be prepared?
Hope this nudge helps =).

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

Title:
  Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in thunderbird source package in Focal:
  Fix Released
Status in thunderbird source package in Hirsute:
  Fix Released

Bug description:
  Similarly to bug #1895643, which was about upgrading thunderbird from
  68 to 78 in all supported Ubuntu releases, this bug is to track the
  update from thunderbird 78 to 91 in hirsute, focal and bionic.

  The rationale is that series 78 will soon be out of support (the last
  release, 78.14.0, was made public on September 7, 2021).

  Thunderbird follows the Firefox ESR release cycle, and the
  next/current series is 91 (already available in impish and jammy).

  User-facing announcement: https://discourse.ubuntu.com/t/thunderbird-
  lts-update-78-to-91/25391.

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


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

[Desktop-packages] [Bug 1967109] Re: Xubuntu Docs installed at /usr/share/xubuntu-docs/index.html is not accessible with firefox snap

[Sean Davis]

** Changed in: snapd
   Status: In Progress => 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/1967109

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

Status in snapd:
  Fix Released
Status in firefox package in Ubuntu:
  Invalid
Status in xubuntu-docs package in Ubuntu:
  Fix Released

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

  The firefox snap is not able to access this file.

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


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

[Desktop-packages] [Bug 1968764] Re: Google Login Window not rendering when adding Google Account

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Google Login Window not rendering when adding Google Account

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  When attempting to add a Google account through settings, the login
  window doesn't render correctly.

  It appears to load but only shows a stock background color.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 11:08:57 2022
  InstallationDate: Installed on 2020-12-18 (480 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago)

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


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

[Desktop-packages] [Bug 1991263] [NEW] duplicate appindicators

[Ken VanDine]

Public bug reported:

I'm seeing duplicate appindicators for snaps built with core22, like
mattermost-desktop and discord.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell-extension-appindicator 42-3ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 29 09:46:07 2022
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
InstallationDate: Installed on 2020-05-18 (863 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-shell-extension-appindicator
UpgradeStatus: Upgraded to kinetic on 2022-08-30 (29 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

** Affects: gnome-shell-extension-appindicator (Ubuntu)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Confirmed

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

** Affects: gnome-shell-extension-appindicator (Ubuntu Kinetic)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Confirmed


** Tags: amd64 apport-bug kinetic third-party-packages wayland-session

** Attachment added: "unknown.png"
   
https://bugs.launchpad.net/bugs/1991263/+attachment/5620013/+files/unknown.png

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

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

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Also affects: gnome-shell-extension-appindicator (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell-extension-appindicator (Ubuntu Kinetic)
   Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Confirmed

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

Title:
  duplicate appindicators

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Jammy:
  New
Status in gnome-shell-extension-appindicator source package in Kinetic:
  Confirmed

Bug description:
  I'm seeing duplicate appindicators for snaps built with core22, like
  mattermost-desktop and discord.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell-extension-appindicator 42-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 29 09:46:07 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (863 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (29 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

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


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

[Desktop-packages] [Bug 1991117] Re: 13.3.0-3build1 fails to build from source

[Sebastien Bacher]

Thanks, the tags are fine like that. I've added a small description of
the change to the changelog instead of "Added" and uploaded

** Changed in: xserver-xorg-video-vmware (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  13.3.0-3build1 fails to build from source

Status in xserver-xorg-video-vmware package in Ubuntu:
  Fix Committed

Bug description:
  [Log]
  
https://launchpadlibrarian.net/625441992/buildlog_ubuntu-kinetic-amd64.xserver-xorg-video-vmware_1%3A13.3.0-3build1_BUILDING.txt.gz

  [Error]
  ../../vmwgfx/vmwgfx_tex_video.c: In function ‘stop_video’:
  ../../vmwgfx/vmwgfx_tex_video.c:240:20: error: the comparison will always 
evaluate as ‘true’ for the address of ‘yuv’ will never be NULL [-Werror=address]
240 |if (priv->yuv[i]) {
|^~~~
  ../../vmwgfx/vmwgfx_tex_video.c:125:24: note: ‘yuv’ declared here
125 | struct xa_surface *yuv[2][3];
|^~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+subscriptions


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

[Desktop-packages] [Bug 1989744] Re: KB/Mouse use causing short system freezes. Happens after resume

[Erik Meitner]

My laptop can only run in discrete and hybrid mode(auto-switch on
demand).

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

Title:
  KB/Mouse use causing short system freezes. Happens after resume

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Summary:
  My laptop gets into a an odd state after resuming from sleep where, depending 
on user activity,
  the entire system freezes every 20 seconds for about 1/2 second.

  This does not happen after every resume. After upgrading to 22.04 was much 
less 
  frequent than it was with 21.10. It seems that after some recent update it is 
happening
  more frequently again. Maybe one every 4 suspend/resume cycles.

  Normal operation can be restored by rebooting or sometimes suspending
  and waking.

  The triggering event is complex:
  * The pointer or pointer and keyboard must be actively used
  * Just typing with no mouse use will not cause it to happen.
  * Just moving the mouse pointer around but keeping it inside the same GUI 
element(a 
textarea for example) will not cause it
  * Typing for more than 20 seconds and then moving the mouse one pixel will 
cause it.
  * Moving the mouse around constantly for over 20 seconds will cause it to 
happen only 
if: a key on the keyboard was hit OR the pointer moved over a new GUI 
element(window 
border, button, even frames in a web page)
  * It is not application specific. 

  
  The following is usually logged(not always though) when the freeze happens:
  ==> ~/.local/share/xorg/Xorg.1.log <==
  [1214998.964] (II) event5  - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some 
input events have been lost.

  ==> /var/log/syslog <==
  Sep 15 08:23:51 krug /usr/libexec/gdm-x-session[3264]: (II) event5  - TPPS/2 
Elan TrackPoint: SYN_DROPPED event - some input events have been lost.

  Sep 15 08:50:34 krug /usr/libexec/gdm-x-session[3264]: (II) event5  - TPPS/2 
Elan TrackPoint: SYN_DROPPED event - some input events have been lost.
  Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer 
event4 trackpoint: scheduled expiry is in the past (-317ms), your system is too 
slow
  Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer 
event4 trackpoint: scheduled expiry is in the past (-301ms), your system is too 
slow
  Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer 
event4 trackpoint: scheduled expiry is in the past (-288ms), your system is too 
slow
  Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer 
event4 trackpoint: scheduled expiry is in the past (-278ms), your system is too 
slow
  Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) WARNING: log rate 
limit exceeded (5 msgs per 360ms). Discarding future messages.

  System Information:

  Lenovo Thinkpad P15
  Model: 20YQ-003WUS 
  OS: Ubuntu 22.04.1 LTS
  Kernel: 5.15.0-46-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-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  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 15 10:13:26 2022
  DistUpgraded: 2022-06-30 16:37:37,968 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed
   virtualbox/6.1.34, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-H GT1 [UHD Graphics] [17aa:22d8]
   NVIDIA Corporation GA107GLM [RTX A2000 Mobile] [10de:25b8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo GA107GLM [RTX A2000 Mobile] [17aa:22d8]
  InstallationDate: Installed on 2022-03-03 (195 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: LENOVO 20YQ003WUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   

[Desktop-packages] [Bug 1979116] Re: no USB-key any more in the sidebar of the save-dialog

[Rudolph]

So, what should I do or what will you do now?

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

Title:
  no USB-key any more in the sidebar of the save-dialog

Status in libreoffice package in Ubuntu:
  New

Bug description:
  If I want to save a new document, then in the save-dialog there's no USB-key 
any more in the sidebar (so, on the left side), no matter if in the Options (in 
"LibreOffice" in "General") "Use LibreOffice dialogs" is checked or unchecked.
  But the USB-key still appears in the file-manager of the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-44.49-generic 5.13.19
  Uname: Linux 5.13.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Sat Jun 18 12:05:53 2022
  InstallationDate: Installed on 2022-02-06 (131 days ago)
  InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1991253] [NEW] Fix test failure in abseil 0~20210324.2-4

[Nathan Teodosio]

Public bug reported:

Abseil is failing to build in Kinetic because of a segmentation fault in
test phase[1].

I'm forwarding a fix from upstream.

[1]: https://launchpadlibrarian.net/625442454/buildlog_ubuntu-kinetic-
amd64.abseil_0~20210324.2-4_BUILDING.txt.gz

** Affects: abseil (Ubuntu)
 Importance: High
 Assignee: Nathan Teodosio (nteodosio)
 Status: New


** Tags: patch

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

Title:
  Fix test failure in abseil 0~20210324.2-4

Status in abseil package in Ubuntu:
  New

Bug description:
  Abseil is failing to build in Kinetic because of a segmentation fault
  in test phase[1].

  I'm forwarding a fix from upstream.

  [1]: https://launchpadlibrarian.net/625442454/buildlog_ubuntu-kinetic-
  amd64.abseil_0~20210324.2-4_BUILDING.txt.gz

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


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

[Desktop-packages] [Bug 1991117] Re: 13.3.0-3build1 fails to build from source

[Nathan Teodosio]

Thanks for your review, Sebastien.

I attach the patch with the cherry-pick.

> Also please tag the patches you add

Added more tags in this one, please do let me know if I still left a
relevant field out.

PS: I sent mail to this bug but it didn't arrive (at least yet). So
disregard echos of this message.

** Patch added: "xorg-vmware3.diff"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+attachment/5620009/+files/xorg-vmware3.diff

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

Title:
  13.3.0-3build1 fails to build from source

Status in xserver-xorg-video-vmware package in Ubuntu:
  Incomplete

Bug description:
  [Log]
  
https://launchpadlibrarian.net/625441992/buildlog_ubuntu-kinetic-amd64.xserver-xorg-video-vmware_1%3A13.3.0-3build1_BUILDING.txt.gz

  [Error]
  ../../vmwgfx/vmwgfx_tex_video.c: In function ‘stop_video’:
  ../../vmwgfx/vmwgfx_tex_video.c:240:20: error: the comparison will always 
evaluate as ‘true’ for the address of ‘yuv’ will never be NULL [-Werror=address]
240 |if (priv->yuv[i]) {
|^~~~
  ../../vmwgfx/vmwgfx_tex_video.c:125:24: note: ‘yuv’ declared here
125 | struct xa_surface *yuv[2][3];
|^~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+subscriptions


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

[Desktop-packages] [Bug 1980839] Re: thunderbird -compose returns error since the 102 snap update?

[Markus Teubert]

Same Problem here with Thunderbird 102.3.1 (Ubuntu 22.04.).

The same error message ("Thunderbird is already running, but is not
responding. To use Thunderbird, you must first close the existing
Thunderbird process, restart your device, or use a different profile.")
comes, when i try to use the feature "send to" with right click on a
file.

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

Title:
  thunderbird -compose returns error since the 102 snap update?

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After updating to the latest thunderbird 102.0.1 snap on Ubuntu 20.04,
  it is no longer possible to open mailto links from the firefox snap in
  thunderbird. When clicking a mailto link in the firefox 102.0.1 snap,
  thunderbird returns the following error message: "Thunderbird is
  already running, but is not responding. To use Thunderbird, you must
  first close the existing Thunderbird process, restart your device, or
  use a different profile." The issue appears related to the thunderbird
  update as there was no issue opening links in the previous 91 version.

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


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

[Desktop-packages] [Bug 1991022] Re: [FFe] Socket activation

[Graham Inggs]

** Summary changed:

- Feature freeze exception: Socket activation
+ [FFe] Socket activation

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

Title:
  [FFe] Socket activation

Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  [Description]

  Systemd socket activation for Speech Dispatcher.

    - Creates the speech-dispatcher.socket;
    - Modifies the server so that it can detect it was automatically launched 
by that socket activation; and
    - Modifies the Autotools files accordingly.

  [Rationale]

  It's relevance is described in [1], of which I quote the essential
  parts [my notes in brackets]:

  > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle 
it inside of the sandbox, so that each application has its own "private" 
instance of Speech Dispatcher running. This works more or less, but it has the 
downside that speech dispatcher cannot coordinate simultaneous messages from 
multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same 
time, the text reading overlaps.
  >
  > In order to solve this issue, I would really like to give sandboxed apps 
access to the Speech Dispatcher instance of the host.

  And then,

  > The only issue I see is having it auto launch. I think it would
  probably be a good step forward for speech-dispatcher to be auto
  launched by a systemd socket like other daemons already do on demand.
  That way the host speech-dispatcher with it's configuration would be
  used by all snaps,

  [Additional information]

  The changes are already merged upstream[2], but still not released.

  I have built and installed the package in Kinetic and verified that
  spd-say still causes the dispatcher spawn and emits sound. Upstream
  test can also confirm this.

  [1]: https://github.com/brailcom/speechd/issues/335
  [2]: https://github.com/brailcom/speechd/pull/763

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


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

[Desktop-packages] [Bug 1781810] Re: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it

[kenn]

Hi @ALinuxUser. I frequently encountered that bug with transparent
theme. For two days I switched to Yaru-Light and I haven't encountered
the bug yet.

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

Title:
  Plank dock is not showing an indicator when a certain application is
  open anymore and when an application that is open is clicked on the
  dock, a new instance of it is opened

Status in BAMF:
  Expired
Status in Plank:
  Expired
Status in bamf package in Ubuntu:
  Expired
Status in plank package in Ubuntu:
  Expired

Bug description:
  Plank version: 0.11.4
  Distribution: Ubuntu MATE 18.04
  DE: MATE Desktop
  Window manager: Marco
  Video card: Intel HD Graphics 4000
  Plank comes installed with the system by default

  When i used Ubuntu MATE 16.04 it didn't happen. I had an indicator that the 
application i was clicking on was open and when i clicked it, it would be 
restored if it was minimized and it will be minimized if it was maximized or 
just being shown on the screen but on this version, even if the application is 
minimized or maximized, when i click on its icon, first of all, i can't see 
that 
  "application open" indicator below its icon anymore(Only below the Plank 
icon) and second of all, Plank will open a new instance of that same 
application. I recorded a video showing you what i am talking about. And also, 
sometimes when i click on the icons on the dock, i won't have that visual 
feedback, that "little jump" of the icon i click. That's very important as well 
otherwise, i think nothing happened. That's all. I really like Plank and it is 
a great application. Thanks for it. Best wishes

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


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

[Desktop-packages] [Bug 1952934] Re: [essx8336] Intel HDA Sound Card not detected on Ubuntu 20.04

[Michel-Ekimia]

** Description changed:

- the intel sound card is not detected and only "dummy output" is
- available
+ [Solution ]
+ 
+ The complete recipe based on 5.19 is here
+ https://github.com/thesofproject/linux/wiki/ES8336-support
+ 
+ Hope that 6.0 mainline will work ...
+ 
+ [Original bug report ]
+ 
+ 
+ the intel sound card is not detected and only "dummy output" is available
  
  I've tested on kernel 5.15 but it s the same on default 5.11 kernel
  
  Also tried without success :
  
- - Booted the 5.4 
+ - Booted the 5.4
  - added snd_intel_dspcfg.dsp_driver=1 boot param
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.15.6-051506-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem2217 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed Dec  1 17:35:25 2021
  InstallationDate: Installed on 2021-11-19 (12 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2021
  dmi.bios.release: 85.176
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: TN1V5.03_PCS
  dmi.board.asset.tag: Board Asset Tag
  dmi.board.name: WN1
  dmi.board.vendor: IP3
  dmi.board.version: V20
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PCSpecialist
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M:
  dmi.product.family: Notebook
  dmi.product.name: TN1-156M
  dmi.product.sku: TN1-156M
  dmi.product.version: V10
  dmi.sys.vendor: PCSpecialist
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418

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

Title:
  [essx8336] Intel HDA Sound Card not detected on Ubuntu 20.04

Status in Linux:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  [Solution ]

  The complete recipe based on 5.19 is here
  https://github.com/thesofproject/linux/wiki/ES8336-support

  Hope that 6.0 mainline will work ...

  [Original bug report ]

  
  the intel sound card is not detected and only "dummy output" is available

  I've tested on kernel 5.15 but it s the same on default 5.11 kernel

  Also tried without success :

  - Booted the 5.4
  - added snd_intel_dspcfg.dsp_driver=1 boot param

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.15.6-051506-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem2217 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed Dec  1 17:35:25 2021
  InstallationDate: Installed on 2021-11-19 (12 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2021
  dmi.bios.release: 85.176
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: TN1V5.03_PCS
  dmi.board.asset.tag: Board Asset Tag
  dmi.board.name: WN1
  dmi.board.vendor: IP3
  dmi.board.version: V20
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PCSpecialist
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M:
  dmi.product.family: Notebook
  dmi.product.name: TN1-156M
  dmi.product.sku: TN1-156M
  dmi.product.version: V10
  dmi.sys.vendor: PCSpecialist
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1990040] Re: Bass speakers not enabled on Lenovo Yoga 7 Gen 7 (14ARB7)

[Saverio Miroddi]

Interestingly, somebody found a workaround; see
https://github.com/PJungkamp/yoga9-linux/issues/8.

** Bug watch added: github.com/PJungkamp/yoga9-linux/issues #8
   https://github.com/PJungkamp/yoga9-linux/issues/8

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

Title:
  Bass speakers not enabled on Lenovo Yoga 7 Gen 7 (14ARB7)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Lenovo Yoga 7 Gen 7 (14ARB7) has 4 speakers - 2 trebles and 2
  basses.

  The treble speakers work, but the bass ones don't.

  I think this is very similar to
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165,
  but that patch does not solve the problem, I suppose because the
  chipset is not the same (ALC245 on this machine vs ALC295 on that.

  This report has been sent from a system with Pipewire (and kernel
  6.0), but this can be ignored, as the problem reproduces the same way
  on a system without Pipewire (kernel 6.0 is needed because of keyboard
  issues).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  Uname: Linux 6.0.0-06rc3-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  saverio2016 F wireplumber
   /dev/snd/controlC0:  saverio2016 F wireplumber
   /dev/snd/seq:saverio2014 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Sun Sep 18 00:08:29 2022
  InstallationDate: Installed on 2022-09-15 (2 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" 
(20220910)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2022
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: K5CN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76463 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 7 14ARB7
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrK5CN27WW:bd05/08/2022:br1.27:efr1.27:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7:
  dmi.product.family: Yoga 7 14ARB7
  dmi.product.name: 82QF
  dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7
  dmi.product.version: Yoga 7 14ARB7
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.default.apport: 2022-09-15T11:39:08.571662
  mtime.conffile..etc.pulse.default.pa: 2022-09-15T11:39:08.207685

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


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

[Desktop-packages] [Bug 1991117] Re: 13.3.0-3build1 fails to build from source

[Sebastien Bacher]

Thanks for the work Nathan.

Checking upstream is it seems they fixed it differently in
https://gitlab.freedesktop.org/xorg/driver/xf86-video-
vmware/-/commit/77b8183b ... maybe it's better to cherrypick the
'official' solution?

Also please tag the patches you add (https://dep-
team.pages.debian.net/deps/dep3/), it helps understanding why we have
them later on and try to forward fixes to Debian (in that case the
package is in sync and there is no reason the fix shouldn't land in
Debian, which would benefit them and us by not having to merge again
later)

** Changed in: xserver-xorg-video-vmware (Ubuntu)
   Importance: Undecided => High

** Changed in: xserver-xorg-video-vmware (Ubuntu)
   Status: New => Incomplete

** Changed in: xserver-xorg-video-vmware (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

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

Title:
  13.3.0-3build1 fails to build from source

Status in xserver-xorg-video-vmware package in Ubuntu:
  Incomplete

Bug description:
  [Log]
  
https://launchpadlibrarian.net/625441992/buildlog_ubuntu-kinetic-amd64.xserver-xorg-video-vmware_1%3A13.3.0-3build1_BUILDING.txt.gz

  [Error]
  ../../vmwgfx/vmwgfx_tex_video.c: In function ‘stop_video’:
  ../../vmwgfx/vmwgfx_tex_video.c:240:20: error: the comparison will always 
evaluate as ‘true’ for the address of ‘yuv’ will never be NULL [-Werror=address]
240 |if (priv->yuv[i]) {
|^~~~
  ../../vmwgfx/vmwgfx_tex_video.c:125:24: note: ‘yuv’ declared here
125 | struct xa_surface *yuv[2][3];
|^~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+subscriptions


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

[Desktop-packages] [Bug 1991100] Re: 2.3.3.4+dfsg-1ubuntu5 fails to build from source

[Sebastien Bacher]

Thanks Nathan, for reference Debian also fixed that issue in a recent
upload, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016219 which
means it's not a delta we will need to carry next cycle once me merge.

** Bug watch added: Debian Bug tracker #1016219
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016219

** Changed in: clucene-core (Ubuntu)
   Importance: Undecided => High

** Changed in: clucene-core (Ubuntu)
   Status: New => Fix Committed

** Changed in: clucene-core (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

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

Title:
  2.3.3.4+dfsg-1ubuntu5 fails to build from source

Status in clucene-core package in Ubuntu:
  Fix Committed

Bug description:
  Log: https://launchpadlibrarian.net/625441502/buildlog_ubuntu-kinetic-
  amd64.clucene-core_2.3.3.4+dfsg-1ubuntu5_BUILDING.txt.gz

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


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