[Desktop-packages] [Bug 1977507] Re: Cupsd crashes every other job since 2.3.1-9ubuntu1.2 security update
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/1977507 Title: Cupsd crashes every other job since 2.3.1-9ubuntu1.2 security update Status in cups package in Ubuntu: Expired Bug description: After yesterdays upgrade (apt log attached) cupsd has stared to crash again every other job. It is then restarted and the next job prints fine. This situation I recognize from the past. It's been like this for a while in the past. Back then I didn't know the upgrade that caused it as half the time it would print just fine. I tried filing a bug with "ubuntu-bug" on the fileserver, but the firefox that was started to let me file the bug wasn't able to get me logged into launchpad. (Works like a charm on my desktop google- chrome). These packages were upgraded yesterday: Start-Date: 2022-06-01 17:55:34 Commandline: apt-get dist-upgrade Requested-By: wolff (1000) Upgrade: libcups2:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), libkmod2:amd64 (27-1ubuntu2, 27-1ubuntu2.1), libcups2-dev:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), libcupsimage2-dev:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), cups-server-common:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), cups-common:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), apache2-data:amd64 (2.4.41-4ubuntu3.10, 2.4.41-4ubuntu3.11), kmod:amd64 (27-1ubuntu2, 27-1ubuntu2.1), cups-ppdc:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), apache2-bin:amd64 (2.4.41-4ubuntu3.10, 2.4.41-4ubuntu3, 2.3.1-9ubuntu1.2), apache2-bin:amd64 (2.4.41-4ubuntu3.10, 2.4.41-4ubuntu3.11), cups-bsd:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), cups-core-drivers:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), cups-daemon:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), libcupsimage2:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), apache2:amd64 (2.4.41-4ubuntu3.10, 2.4.41-4ubuntu3.11), cups:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), apache2-utils:amd64 (2.4.41-4ubuntu3.10, 2.4.41-4ubuntu3.11), cups-client:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), cups-ipp-utils:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2) End-Date: 2022-06-01 17:56:15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1977507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1975896] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1975896 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Expired Bug description: Errors were encountered while processing: /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri May 27 11:02:41 2022 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1975896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895762] Re: PH-B-500 Headphone makes bluetooth loop
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1895762 Title: PH-B-500 Headphone makes bluetooth loop Status in bluez package in Ubuntu: Expired Bug description: Hi there, I am using Ubuntu 18.04.4 LTS(Brazilian Portuguese, so, sorry if I translated wrong some label) in a Dell Inspiron 15 series 3000 and I am having some Bluetooth problems. I always suffer to synchronize my Cadenza PH-B Bluetooth Headphone. It Shows as PH-B-500 at the bluetooth devices list What happens is: 1. I turn on the headphone 2. I go to Settings → Bluetooth 3. The Notebook entire bluetooth enters a shutdown reinitialize loop 4. It only stops when I turn off the headphone But if I: 1. Keep the headphone off 2. go to Settings → Bluetooth 3. Click on the PH-B-500 on the list 4. Turn the headphone on and at the same time click on Conection at the PH-B-500 Bluetooth window it usually starts working fine. The headphone works perfectly on my Android cell phone so I don’t believe it is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1977679] Re: Firefox opens KML file in neverending loop if associated with "System Handler"
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1977679 Title: Firefox opens KML file in neverending loop if associated with "System Handler" Status in firefox package in Ubuntu: Expired Bug description: Found when trying open a KML export file from Google Timeline. It can be reproduced even with an empty KML file. Steps: * Create an empty file "test.kml" (run "$ touch test.kml") * Open the application "Files" * Right click on the test.kml and open it with Firefox * Open with "System Handler" and check the option "Do this automatically for files like this from now on" (see "Screenshot from 2022-06-05 11-13-23.png") Expected result: * No infinite opening Actual result: * Firefox starts opening the file again and again (see "Screenshot from 2022-06-05 11-04-35.png") Used SW: * Ubuntu 22.04 LTS * Firefox 101.0 * Files 42.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1977679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983768] Re: Resize: Filesystem enlargement depends of manual partition mounting
** Description changed: + Package: gnome-disk-utility 3.36.3 + This issue is for gnome-disks, for its Resize function. I've only evaluated this for EXT4 file systems. Works: 1) In a terminal, run $ lsblk 2) Open gnome-disks 3) Select a partition, and click on the "Mount selected" partition button. 4) Click on the "Additional partition options" button, and then on the "Resize..." entry to open the "Resize Volume" window. 5) In the "Resize Volume" window, enlarge the "Current size" and then click on the "Resize" button. 6) In the terminal, run $ lsblk again, and compare the SIZE of the partition with the previously output from lsblk 7) Result: Both the partition and the _file system_ will be enlarged. Does not work: * Run the above steps but skip step 3 (do not mount the partition). * Result: The partition will be enlarged, but not the _file system_ will not be enlarged. Solution: The Resize function should automatically resize the file system, regardless if the partition is mounted or not, like gparted. If it helps, the gparted log says that its using: $ resize2fs -p '/dev/sda2' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1983768 Title: Resize: Filesystem enlargement depends of manual partition mounting Status in gnome-disk-utility package in Ubuntu: New Bug description: Package: gnome-disk-utility 3.36.3 This issue is for gnome-disks, for its Resize function. I've only evaluated this for EXT4 file systems. Works: 1) In a terminal, run $ lsblk 2) Open gnome-disks 3) Select a partition, and click on the "Mount selected" partition button. 4) Click on the "Additional partition options" button, and then on the "Resize..." entry to open the "Resize Volume" window. 5) In the "Resize Volume" window, enlarge the "Current size" and then click on the "Resize" button. 6) In the terminal, run $ lsblk again, and compare the SIZE of the partition with the previously output from lsblk 7) Result: Both the partition and the _file system_ will be enlarged. Does not work: * Run the above steps but skip step 3 (do not mount the partition). * Result: The partition will be enlarged, but not the _file system_ will not be enlarged. Solution: The Resize function should automatically resize the file system, regardless if the partition is mounted or not, like gparted. If it helps, the gparted log says that its using: $ resize2fs -p '/dev/sda2' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1983768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983768] [NEW] Resize: Filesystem enlargement depends of manual partition mounting
Public bug reported: This issue is for gnome-disks, for its Resize function. I've only evaluated this for EXT4 file systems. Works: 1) In a terminal, run $ lsblk 2) Open gnome-disks 3) Select a partition, and click on the "Mount selected" partition button. 4) Click on the "Additional partition options" button, and then on the "Resize..." entry to open the "Resize Volume" window. 5) In the "Resize Volume" window, enlarge the "Current size" and then click on the "Resize" button. 6) In the terminal, run $ lsblk again, and compare the SIZE of the partition with the previously output from lsblk 7) Result: Both the partition and the _file system_ will be enlarged. Does not work: * Run the above steps but skip step 3 (do not mount the partition). * Result: The partition will be enlarged, but not the _file system_ will not be enlarged. Solution: The Resize function should automatically resize the file system, regardless if the partition is mounted or not, like gparted. If it helps, the gparted log says that its using: $ resize2fs -p '/dev/sda2' ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1983768 Title: Resize: Filesystem enlargement depends of manual partition mounting Status in gnome-disk-utility package in Ubuntu: New Bug description: This issue is for gnome-disks, for its Resize function. I've only evaluated this for EXT4 file systems. Works: 1) In a terminal, run $ lsblk 2) Open gnome-disks 3) Select a partition, and click on the "Mount selected" partition button. 4) Click on the "Additional partition options" button, and then on the "Resize..." entry to open the "Resize Volume" window. 5) In the "Resize Volume" window, enlarge the "Current size" and then click on the "Resize" button. 6) In the terminal, run $ lsblk again, and compare the SIZE of the partition with the previously output from lsblk 7) Result: Both the partition and the _file system_ will be enlarged. Does not work: * Run the above steps but skip step 3 (do not mount the partition). * Result: The partition will be enlarged, but not the _file system_ will not be enlarged. Solution: The Resize function should automatically resize the file system, regardless if the partition is mounted or not, like gparted. If it helps, the gparted log says that its using: $ resize2fs -p '/dev/sda2' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1983768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
I remember in previouse snap it is working, but withtout
vaapivideodecoder working. It is another problem, but the wayland is
sure working.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
sure, I already enable wayland.
chromium --enable-features=VaapiVideoDecoder
--disable-features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
[14225:14225:0807/073546.382350:ERROR:wayland_connection.cc(210)] Failed to
connect to Wayland display
[14225:14225:0807/073546.382387:ERROR:ozone_platform_wayland.cc(226)] Failed to
initialize Wayland platform
[14225:14225:0807/073546.382398:ERROR:env.cc(226)] The platform failed to
initialize. Exiting.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
So it works in Xorg (great to hear!) but not in Wayland for you?
It seems that you need one additional flag in Wayland, --ozone-
platform=wayland. I.e., can you please try
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
** Description changed:
To test the snap with VA-API changes,
-
- 0. If you have Nvidia GPU, you need Snapcraft >=7.1.1. Check `snap info
- snapcraft`. At the time of writing,
-
- sudo snap refresh --channel 7.x snapcraft
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-media-
samples
4. Enter about:media-internals in the address bar and note what the page
says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with newer
generations of Intel CPUs will have luck with this, but it's still an
uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProf
[Desktop-packages] [Bug 1983529] Re: No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4)
I am able to play sound with aplay when pipewire is not running, so I don't think it's a hardware/firmware issue. -- 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/1983529 Title: No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4) Status in alsa-driver package in Ubuntu: New Bug description: Not sure if it's relevant, but there are some errors in dmesg: $ sudo dmesg | grep audio [ 14.290226] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 14.440430] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 14.445129] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 14.445811] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 14.445861] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI codec failed [ 14.448966] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 15.467232] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, ret: -5 [ 15.467478] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1 [ 15.467479] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 15.467484] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 15.478062] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 15.478066] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.478068] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 15.478073] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 15.584074] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 15.584079] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.584080] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 15.591457] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.591461] sof-audio-pci-intel-tgl :00:1f.3: warn: topology ABI is more recent than kernel [ 15.624250] sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [ 15.643720] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 15.643726] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 15.643727] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 15.643728] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [ 15.643729] snd_hda_codec_realtek ehdaudio0D0:inputs: [ 15.643730] snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 Because of those ABI warnings, I tried building the latest mainline kernel from source, and the ABI warnings went away, but I still have no sound. $ sudo dmesg | grep audio # On latest upstream kernel [ 17.519958] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 17.804900] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 17.805661] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 17.806225] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 17.806265] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI codec failed [ 17.808071] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 21.844005] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, ret: -5 [ 21.844263] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1 [ 21.844264] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 21.844267] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 21.853970] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 21.853971] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.853979] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 21.961252] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 21.961255] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.967719] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.979145] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 21.979147] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 21.979148] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [
[Desktop-packages] [Bug 1983010] Re: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size
Launchpad has imported 2 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1783163. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-08-04T09:58:00+00:00 Vikram Vincent wrote: User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0 Steps to reproduce: use Firefox Beta and launch it from the terminal. While watching Netflix on Firefox, I get the following messages on my terminal: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present Sandbox: attempt to open unexpected file /sys/devices/system/cpu Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1983010/comments/5 On 2022-08-04T16:47:24+00:00 Gpascutto wrote: Just a warning, but unexpected, so we want to have a look at some point. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1983010/comments/9 ** Changed in: firefox Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1983010 Title: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: I use Firefox Beta and launch it from the terminal. While watching Netflix on Firefox, I get the following messages on my terminal: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present Sandbox: attempt to open unexpected file /sys/devices/system/cpu Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Jul 28 15:01:35 2022 InstallationDate: Installed on 2022-06-21 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1983010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983660] Re: Chromium seems to drive all data into swap, until choking
I checked, there seems to be no easy way to downgrade? And no other chromium in the *buntu pool (while the latter would probably not be very helpful anyway). If I could do anything further, just let me know. I don't like Firefox that much, and would love to go back, if possible. -- 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/1983660 Title: Chromium seems to drive all data into swap, until choking Status in chromium-browser package in Ubuntu: Incomplete Bug description: For the last day(s) my machine runs Chrome very very slow and sluggish until it stops reacting at all. I haven't done any changes except of the daily updates and snap refresh. What I found out, is that the memory space used is almost immediately the swap space. Same after cold boot: it starts pretty usual, but soon almost all memory data seem to be sent into swap space, despite of RAM being available. (See attachment, taken shortly before total non-reaction. CPU isn't very busy, RAM is aplenty.) Swappiness is okay at 60. I very much suspect Chrome, since when using Firefox, with my (in Chrome) usual sites, everything looks fine, it doesn't choke, and the swap space used is almost negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1983660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983453] Re: A locked screen does not blank after brief inactivity
All bug reports need to be assigned to a package for an Ubuntu developer to be made aware of a problem. Assigning to gnome-shell for now. ** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1983453 Title: A locked screen does not blank after brief inactivity Status in gnome-shell package in Ubuntu: New Bug description: Started happening immediately after an upgrade from 18.04 to 20.04. Previously, when locking the screen, in short absence of activity (1 minute?), the screen would go blank. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 3 10:11:52 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-02-18 (1991 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-08-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1983453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983453] [NEW] A locked screen does not blank after brief inactivity
You have been subscribed to a public bug: Started happening immediately after an upgrade from 18.04 to 20.04. Previously, when locking the screen, in short absence of activity (1 minute?), the screen would go blank. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 3 10:11:52 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-02-18 (1991 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-08-02 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- A locked screen does not blank after brief inactivity https://bugs.launchpad.net/bugs/1983453 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983638] Re: Ubuntu 22.10 Settings-sound-output-test does not work
After reboot on Settings>Sound I set all volumes to zero, Output Device is HDMI / DisplayPort2 - Built-in Audio but clicking on any 'Alert Sound' volume is NOT muted and seems at max. Sound from Firefox is muted, Playing a movie.MOV with totem sound is muted, sound from Aisleriot solitaire is NOT muted. sound comes from speakers connected to motherboard. my sound devices are: corrado@corrado-n4-kk-0718:~$ inxi -Axx Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 1-7:5 bus-ID: 00:1f.3 chip-ID: 046d:0990 chip-ID: 8086:a170 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo Sound Server-1: ALSA v: k5.15.0-27-generic running: yes Sound Server-2: PipeWire v: 0.3.56 running: yes corrado@corrado-n4-kk-0718:~$ -- 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/1983638 Title: Ubuntu 22.10 Settings-sound-output-test does not work Status in gnome-control-center package in Ubuntu: New Bug description: Open settings. select sound. System Volume and Volume for System Sounds are at maximum, Output Device is HDMI / DisplayPort2 - Built-in Audio click on Test and then on Left or Right speaker has no effect (no sound) but clicking on Alert Sound works fine. Playing a movie.MOV with totem sound is ok. On the same PC different partition I have Ubuntu 22.04 and problem does not occur. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:42.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 5 07:06:31 2022 InstallationDate: Installed on 2022-07-19 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 27867] Re: Background color is always white, top banner is never displayed in Firefox
Gulab.pk is one of the leading online plant nursery, provides wide range of indoor and outdoor Plants. Buy online | Fastest delivery. https://www.gulab.pk/ -- 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/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
