[Desktop-packages] [Bug 1983605] Re: exim4 autopkgtest failure on ppc64el with libx11 1.8
Reassigning since it fails even without libx11 1.8 ** Package changed: libx11 (Ubuntu) => exim4 (Ubuntu) ** Summary changed: - exim4 autopkgtest failure on ppc64el with libx11 1.8 + exim4 autopkgtest failure on ppc64el ** Description changed: I'm just filing a tracker bug for this issue but am not working on it myself. - exim4's autopkgtest fails with the new libx11 on kinetic on the ppc64el - architecture. + exim4's autopkgtest fails on the ppc64el architecture. https://autopkgtest.ubuntu.com/packages/e/exim4/kinetic/ppc64el This test doesn't fail on Debian. Ubuntu's ppc64el is slightly different than Debian's (we enable -O3 for instance only on that architecture by default). https://ci.debian.net/packages/e/exim4/testing/ppc64el/ - - This issue is blocking other packages from migrating out of kinetic- - proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1983605 Title: exim4 autopkgtest failure on ppc64el Status in exim4 package in Ubuntu: New Bug description: I'm just filing a tracker bug for this issue but am not working on it myself. exim4's autopkgtest fails on the ppc64el architecture. https://autopkgtest.ubuntu.com/packages/e/exim4/kinetic/ppc64el This test doesn't fail on Debian. Ubuntu's ppc64el is slightly different than Debian's (we enable -O3 for instance only on that architecture by default). https://ci.debian.net/packages/e/exim4/testing/ppc64el/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1983605/+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
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454
chrome://flags/#ozone-platform-hint , not work.
[30855:30855:0806/092525.830999:ERROR:wayland_connection.cc(210)] Failed to
connect to Wayland display
[30855:30855:0806/092525.831041:ERROR:ozone_platform_wayland.cc(226)] Failed to
initialize Wayland platform
[30855:30855:0806/092525.831051: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,
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`
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
Wao, perfecter build.
It is the first time my Nvidia/intel CPU, get a snap chromium support
video decoder.
I need not manually maintain my native chromium environment.
Thanks for your hardwarking.
--
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,
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`
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 1983502] Re: [snap] seccomp denials for syscall=314 on amd64
There are quite a few "pending" crash reports and one from the day I opened this bug so I'd say yes, it's failing to submit them: sdeziel@sdeziel-lemur:~/snap/thunderbird/common/.thunderbird/Crash Reports/pending$ ls -ltr | tail -rw--- 1 sdeziel sdeziel 2088424 May 27 14:04 5f6acf74-091e-649d-d405-8f515d115c43.dmp -rw--- 1 sdeziel sdeziel 11518 May 27 14:04 5f6acf74-091e-649d-d405-8f515d115c43.extra -rw--- 1 sdeziel sdeziel 1790080 Jun 2 12:07 36f475a4-a06d-805a-f37c-3537f767db0d.dmp -rw--- 1 sdeziel sdeziel 12510 Jun 2 12:07 36f475a4-a06d-805a-f37c-3537f767db0d.extra -rw--- 1 sdeziel sdeziel 1752936 Jun 30 09:27 42252ef9-1b81-6337-f078-a16915f5a550.dmp -rw--- 1 sdeziel sdeziel8111 Jun 30 09:27 42252ef9-1b81-6337-f078-a16915f5a550.extra -rw-rw-r-- 1 sdeziel sdeziel 344429 Jul 26 13:34 44fcac7c-c079-c1c2-d25b-a421fdc9b60b.dmp -rw--- 1 sdeziel sdeziel9526 Jul 26 13:34 44fcac7c-c079-c1c2-d25b-a421fdc9b60b.extra -rw--- 1 sdeziel sdeziel 1667280 Aug 3 12:02 09575f30-efa8-4267-8875-7c78e787f556.dmp -rw--- 1 sdeziel sdeziel 11198 Aug 3 12:02 09575f30-efa8-4267-8875-7c78e787f556.extra -- 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/1983502 Title: [snap] seccomp denials for syscall=314 on amd64 Status in thunderbird package in Ubuntu: New Bug description: $ snap list thunderbird Name VersionRev Tracking Publisher Notes thunderbird 102.1.0-2 237 latest/stable canonical✓ - During normal operation, the following is logged: Aug 03 12:07:58 foo kernel: audit: type=1326 audit(1659542878.718:511): auid=1000 uid=1000 gid=1000 ses=9 subj=? pid=154377 comm="thunderbird-bin" exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7e4137c4473d code=0x5 And something similar when the crash reporter executes: Aug 03 12:02:04 foo kernel: audit: type=1326 audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=? pid=150188 comm="crashreporter" exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e syscall=314 compat=0 ip=0x7e5f095e773d code=0x5 # Additional information: $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 $ uname -a Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983502/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
I found a fix for the speakers and several other issues. I submitted the patch to the alsa-devel mailing list, where it was applied by one of the sound subsystem maintainers. It will now slowly travel towards mainline. https://mailman.alsa-project.org/pipermail/alsa- devel/2022-July/204315.html As I'm more familiar with Arch Linux than Ubuntu I opted to run a patched kernel on Arch. I uploaded the patches I currently use to https://github.com/PJungkamp/yoga9-linux. If you stick with Ubuntu and are familiar with patching Ubuntu/Debian kernels you can try to apply those yourself. -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1965094] Re: "Additional Drivers" application crashes on startup
The traceback is really in UbuntuDrivers/detect.py which is part of ubuntu-drivers-common. Looking at the code it hasn't changed with the latest version of ubuntu-drivers-common (1:0.9.6.1) so this still needs fixing. ** Information type changed from Private to Public ** Tags added: rls-jj-incoming ** Package changed: software-properties (Ubuntu) => ubuntu-drivers- common (Ubuntu) -- 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/1965094 Title: "Additional Drivers" application crashes on startup Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Click on "Show applications" in the dock * Click on "Additional Drivers" Expected: It is possible to see and install additional drivers Actual: Application "software-properties-gtk" crashes Background: I installed 22.04 daily build from scratch on my new Samsung laptop just a few days ago and I have almost no custom settings. Output from screenfetch: ./+o+- [...] y- -yy+ OS: Ubuntu 22.04 jammy ://+//-yyo Kernel: x86_64 Linux 5.15.0-22-generic .++ .:/++/-.+sss/` Uptime: 1d 9h 37m .:++o: //:--:/- Packages: 1810 o:+o+:++.`..```.-/oo+/ Shell: bash 5.1.16 .:+o:+o/. `+sssoo+/Resolution: 3840x1080 .++/+:+oo+o:` /sssooo. DE: GNOME 41.4 /+++//+:`oo+o /::--:. WM: Mutter \+/+o+++`o++o ++. WM Theme: Adwaita .++.o+++oo+:` /dddhhh. GTK Theme: Yaru-dark [GTK2/3] .+.o+oo:. `odd+Icon Theme: Yaru \+.++o+o``-.:ohdh+ Font: Ubuntu 11 `:o+++ `oyo++os: Disk: 21G / 1,2T (2%) .o:`.syhhh/.oo++o` CPU: 11th Gen Intel Core i7-1165G7 @ 8x 4,7GHz [40.0°C] /osyyo++ooo+++/ GPU: Iris Xe Graphics ` +oo+++o\: RAM: 2627MiB / 15725MiB `oo++. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 08:34:57 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-14 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4 Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4'] PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1965094/+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 1965094] Re: "Additional Drivers" application crashes on startup
Here's an errors bucket for the crash w/ thousands of duplicates: https://errors.ubuntu.com/problem/789caa74268274fffeac8967a2dd4735c91866be ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1965094 Title: "Additional Drivers" application crashes on startup Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Click on "Show applications" in the dock * Click on "Additional Drivers" Expected: It is possible to see and install additional drivers Actual: Application "software-properties-gtk" crashes Background: I installed 22.04 daily build from scratch on my new Samsung laptop just a few days ago and I have almost no custom settings. Output from screenfetch: ./+o+- [...] y- -yy+ OS: Ubuntu 22.04 jammy ://+//-yyo Kernel: x86_64 Linux 5.15.0-22-generic .++ .:/++/-.+sss/` Uptime: 1d 9h 37m .:++o: //:--:/- Packages: 1810 o:+o+:++.`..```.-/oo+/ Shell: bash 5.1.16 .:+o:+o/. `+sssoo+/Resolution: 3840x1080 .++/+:+oo+o:` /sssooo. DE: GNOME 41.4 /+++//+:`oo+o /::--:. WM: Mutter \+/+o+++`o++o ++. WM Theme: Adwaita .++.o+++oo+:` /dddhhh. GTK Theme: Yaru-dark [GTK2/3] .+.o+oo:. `odd+Icon Theme: Yaru \+.++o+o``-.:ohdh+ Font: Ubuntu 11 `:o+++ `oyo++os: Disk: 21G / 1,2T (2%) .o:`.syhhh/.oo++o` CPU: 11th Gen Intel Core i7-1165G7 @ 8x 4,7GHz [40.0°C] /osyyo++ooo+++/ GPU: Iris Xe Graphics ` +oo+++o\: RAM: 2627MiB / 15725MiB `oo++. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 08:34:57 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-14 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4 Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4'] PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1965094/+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
My apologies, Li, I didn't realize that Snapcraft 7.1.1 had to reach the
builder, not the installer machine; as such, your test still suffered
the lack of LIBVA_DRIVERS_PATH.
I uploaded a rebuilt snap (from hwacc-debug, with vainfo) to
candidate/hwacc and made sure that the snapcraft changes made their way
in. May you please install — or refresh — it and try it again?
--
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,
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`
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 1983490] Re: Auto-hide taskbar does not work quite right
*** This bug is a duplicate of bug 1983130 *** https://bugs.launchpad.net/bugs/1983130 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1983490 Title: Auto-hide taskbar does not work quite right Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: In Gnome on the latest version of Ubuntu Jammy Jellyfish, the auto- hide taskbar feature is broken. The task bar will disappear even when there is no overlapping window and the only way to bring it back appears to be to move a window down into that region of the display and back away from it and then it will re-appear, until it disappears again on it own. Sorry don't have the time to help with debug of this, but wanted you to know. Also I submitted a ubuntu-bug on this bug for some reason it gathered all my info and then failed to ask me what the specific problem was. So you might want to x-ref this bug report with that filing to get all the details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1983490/+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 1981863] Re: gnome calendar does not sync with google calendar
I don't know what happened, but gnome calendar syncing again with google :-o Maybe the update of libgnutls30? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: Incomplete Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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 1809975] Re: Please implement Microsoft "Your Phone" support for Chat Accounts
Please see comment #13 which advises that the Thunderbird developers won't be implementing this request so have closed their issue with a status of "RESOLVED WONTFIX". I'm closing the Ubuntu task (as Invalid but should also be Won't Fix) as it's not something that Ubuntu developers will be implementing as a patch to all or any future Thunderbird releases. ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Invalid -- 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/1809975 Title: Please implement Microsoft "Your Phone" support for Chat Accounts Status in Mozilla Thunderbird: Won't Fix Status in thunderbird package in Ubuntu: Invalid Bug description: I would love to see support for Microsoft Accounts "Your Phone/Companion" feature in Thunderbird's "Chat Accounts" tool. This would allow me to synchronize my text messages and notifications with my Android device. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thunderbird 1:60.2.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-12.13-lowlatency 4.18.17 Uname: Linux 4.18.0-12-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeb6811 F pulseaudio /dev/snd/controlC2: jeb6811 F pulseaudio /dev/snd/controlC0: jeb6811 F pulseaudio BuildID: 20181011091051 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Dec 28 08:22:33 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-08-17 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src 192.168.86.239 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818 PrefSources: prefs.js Prefs: extensions.lastAppVersion: "60.2.1" (prefs.js) network.cookie.prefsMigrated: true (prefs.js) network.predictor.cleaned-up: true (prefs.js) places.database.lastMaintenance: 1544627000 (prefs.js) places.history.expiration.transient_current_max_pages: 104858 (prefs.js) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=60.2.1/20181011091051 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to cosmic on 2018-10-19 (69 days ago) dmi.bios.date: 09/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A880G+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A880G+ dmi.product.sku: To Be Filled By O.E.M. dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1809975/+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 1974449] Re: No filepicker in Firefox with enforced AppArmor profile
Fixed in the beta branches (bionic and focal) with
https://bazaar.launchpad.net/~mozillateam/firefox/firefox-
beta.bionic/revision/1463 and
https://bazaar.launchpad.net/~mozillateam/firefox/firefox-
beta.focal/revision/1463.
** Changed in: firefox (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Changed in: firefox (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
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/1974449
Title:
No filepicker in Firefox with enforced AppArmor profile
Status in firefox package in Ubuntu:
Invalid
Status in firefox source package in Bionic:
Fix Committed
Status in firefox source package in Focal:
Fix Committed
Bug description:
# System
Ubuntu 22.04 LTS (Jammy Jellyfish) {kubuntu-ppa/backports/ubuntu jammy main |
mozillateam/ppa/ubuntu/ jammy main}
Package: firefox
Version: 100.0.1+build1-0ubuntu0.22.04.1~mt1
---
# Description
I’m using Firefox stand-alone package (not the mainline Ubuntu Snap version)
under KDE (native KDE filepicker) with enforced `usr.bin.firefox AppArmor`
profile (included in `firefox` package) and when I try to open a file, save a
screenshot or print to file, no filepicker shown.
---
# Error message
Can't open portal file chooser:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy
prevents this sender from sending this message to this recipient;
type="method_call", […] interface="org.freedesktop.portal.FileChooser"
member="OpenFile" […] destination="org.freedesktop.portal.Desktop" […])
---
# Suggested fix
Please see commit:
https://github.com/snapcore/snapd/pull/8793/files/ec7f01e8c15bf9303cfb30354470d2a7b3783f25
# Fix result
Implementing the part for `org.freedesktop.portal.Desktop` from the above
commit resolves the filepicker issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1974449/+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 1974449] Re: No filepicker in Firefox with enforced AppArmor profile
** Branch linked: lp:~mozillateam/firefox/firefox-beta.bionic
** Branch linked: lp:~mozillateam/firefox/firefox-beta.focal
--
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/1974449
Title:
No filepicker in Firefox with enforced AppArmor profile
Status in firefox package in Ubuntu:
Invalid
Status in firefox source package in Bionic:
Fix Committed
Status in firefox source package in Focal:
Fix Committed
Bug description:
# System
Ubuntu 22.04 LTS (Jammy Jellyfish) {kubuntu-ppa/backports/ubuntu jammy main |
mozillateam/ppa/ubuntu/ jammy main}
Package: firefox
Version: 100.0.1+build1-0ubuntu0.22.04.1~mt1
---
# Description
I’m using Firefox stand-alone package (not the mainline Ubuntu Snap version)
under KDE (native KDE filepicker) with enforced `usr.bin.firefox AppArmor`
profile (included in `firefox` package) and when I try to open a file, save a
screenshot or print to file, no filepicker shown.
---
# Error message
Can't open portal file chooser:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy
prevents this sender from sending this message to this recipient;
type="method_call", […] interface="org.freedesktop.portal.FileChooser"
member="OpenFile" […] destination="org.freedesktop.portal.Desktop" […])
---
# Suggested fix
Please see commit:
https://github.com/snapcore/snapd/pull/8793/files/ec7f01e8c15bf9303cfb30354470d2a7b3783f25
# Fix result
Implementing the part for `org.freedesktop.portal.Desktop` from the above
commit resolves the filepicker issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1974449/+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 1979412] Re: Chromium crashes when downloading
** Package changed: chromium (Ubuntu) => chromium-browser (Ubuntu) ** Tags added: snap ** Summary changed: - Chromium crashes when downloading + [snap] Chromium crashes when downloading ** Tags added: jammy -- 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/1979412 Title: [snap] Chromium crashes when downloading Status in chromium-browser package in Ubuntu: New Bug description: For a couple of weeks, I observe random crashes of Chromium when you click on a link that starts a non-HTML download (e.g. PDF or an MS Excel file). After restarting Chromium and restoring the tabs, a second click on the link starts the download without problems, probably because this issue is not 100% reproducible in the first place. Observed with Chromium 102.0.5005.115 (officiel build) snap (64-Bit) on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1979412/+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 1979412] [NEW] Chromium crashes when downloading
You have been subscribed to a public bug: For a couple of weeks, I observe random crashes of Chromium when you click on a link that starts a non-HTML download (e.g. PDF or an MS Excel file). After restarting Chromium and restoring the tabs, a second click on the link starts the download without problems, probably because this issue is not 100% reproducible in the first place. Observed with Chromium 102.0.5005.115 (officiel build) snap (64-Bit) on Ubuntu 22.04 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- Chromium crashes when downloading https://bugs.launchpad.net/bugs/1979412 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser 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 1974449] Re: No filepicker in Firefox with enforced AppArmor profile
Even though the reporter wasn't using an officially-supported package,
the problem is actually valid for officially-supported packages of
firefox on bionic and focal, so I'm going to update the apparmor
profiles for those to address the issue.
** Also affects: firefox (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: firefox (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: firefox (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: firefox (Ubuntu Bionic)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: firefox (Ubuntu Focal)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: firefox (Ubuntu Focal)
Status: New => Confirmed
** Changed in: firefox (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: firefox (Ubuntu Focal)
Importance: Undecided => Medium
--
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/1974449
Title:
No filepicker in Firefox with enforced AppArmor profile
Status in firefox package in Ubuntu:
Invalid
Status in firefox source package in Bionic:
Confirmed
Status in firefox source package in Focal:
Confirmed
Bug description:
# System
Ubuntu 22.04 LTS (Jammy Jellyfish) {kubuntu-ppa/backports/ubuntu jammy main |
mozillateam/ppa/ubuntu/ jammy main}
Package: firefox
Version: 100.0.1+build1-0ubuntu0.22.04.1~mt1
---
# Description
I’m using Firefox stand-alone package (not the mainline Ubuntu Snap version)
under KDE (native KDE filepicker) with enforced `usr.bin.firefox AppArmor`
profile (included in `firefox` package) and when I try to open a file, save a
screenshot or print to file, no filepicker shown.
---
# Error message
Can't open portal file chooser:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy
prevents this sender from sending this message to this recipient;
type="method_call", […] interface="org.freedesktop.portal.FileChooser"
member="OpenFile" […] destination="org.freedesktop.portal.Desktop" […])
---
# Suggested fix
Please see commit:
https://github.com/snapcore/snapd/pull/8793/files/ec7f01e8c15bf9303cfb30354470d2a7b3783f25
# Fix result
Implementing the part for `org.freedesktop.portal.Desktop` from the above
commit resolves the filepicker issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1974449/+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 1855793] Re: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on
Also have this issue again in 22.04.1 LTS version. -- 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/1855793 Title: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden and I will then be forced to turn the Wi-Fi off and then back on again, which is annoying. And even then, the Wi-Fi becomes unusually slow afterwards. Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855793/+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 1983196] Re: Cheese Internal data stream error
*** This bug is a duplicate of bug 1983181 *** https://bugs.launchpad.net/bugs/1983181 ** This bug has been marked a duplicate of bug 1983181 Cheese Internal data stream error -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1983196 Title: Cheese Internal data stream error Status in cheese package in Ubuntu: New Bug description: Starting cheese i have a message: corrado@corrado-n4-kk-0718:~$ cheese (cheese:11193): Gdk-WARNING **: 08:46:12.388: Native Windows taller than 65535 pixels are not supported and after many seconds: (cheese:11193): cheese-WARNING **: 08:47:17.731: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) NOTE: to create this bug report i removed the apport package hook provided by cheese and located in /usr/share/apport/package-hooks/source_cheese.py. becaause the hook creates a bug against linux instead cheese. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: cheese 41.1-2 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: Sun Jul 31 08:47:35 2022 InstallationDate: Installed on 2022-07-19 (12 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-07-19 (12 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) Package: cheese 41.1-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: wayland-session kinetic Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1983196/+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
This is pretty much what I think. Can't vouch for it, of course. But the choking up to no reaction only happened yesterday. As usual, in the beginning I expected some tab to require lot of CPU time. Therefore, I use the widget shown in the image relatively frequently. And sometimes I close a demanding tab. So this belongs to my almost staple diet. Yesterday, again, I wanted to find out if I had en extremely demanding tab, when I noticed, to my surprise, that the CPU was hoovering around 2-5 percent. That was the first time I noticed. Closed Chrome, opened Chrome again, same. Logged off, logged in, same. Cold boot, same. Attached you'll find the image of the resources with Firefox, only running application, after some 5 hours of running, some 20 tabs, the same that I use daily on Chrome. And it looks similar to what it used to look throughout the last years, using Chrome. And it looks like what one expects. ** Attachment added: "Normal resource use, as earlier and here with Firefox" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1983660/+attachment/5607144/+files/Screenshot_20220805_160001.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/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 1100326] Re: Location requested by websites should be able to use GPS/mobile positioning
** Changed in: firefox (Ubuntu) Status: Confirmed => 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/1100326 Title: Location requested by websites should be able to use GPS/mobile positioning Status in Chromium Browser: Fix Committed Status in Mozilla Firefox: Fix Released Status in GeoClue: Won't Fix Status in WebKit: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Fix Released Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-providers package in Ubuntu: Invalid Bug description: It would be nice if location requested by websites could use location found from GPS or GSM/CDMA positioning. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1100326/+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 1981186] Re: Thunderbird 102 : keeps an empty window even if all calendar alarms closed
That sounds like an upstream regression. Would you mind filing a bug at https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird, and sharing the link to it here? -- 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/1981186 Title: Thunderbird 102 : keeps an empty window even if all calendar alarms closed Status in thunderbird package in Ubuntu: New Bug description: Since Thunderbird 102 (deb version on Ubuntu 22.10), a new bug appeared on calendar : when a window opens with many alarm reminders, after having reported or closed all of them, it remains an empty window with "0 reminder" title, instead of closing the floating window as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981186/+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 1945741] Re: [upstream] PDF attachment opens in Firefox instead of the built-in viewer when opened from the compose window
** Changed in: thunderbird (Ubuntu)
Status: Confirmed => Fix Released
--
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/1945741
Title:
[upstream] PDF attachment opens in Firefox instead of the built-in
viewer when opened from the compose window
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Fix Released
Bug description:
In Thunderbird 78, you could double click on an attachment you've just
attached when composing an email. This was very useful, so that you
could double check that you attached the correct file. In Thunderbird
91, this doesn't seem to work. When you double click on the
attachment, nothing happens.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: thunderbird 1:91.1.1+build2-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alistair 2076 F pulseaudio
BuildID: 20210916142849
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Oct 1 08:44:34 2021
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-07-14 (443 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 172.30.3.254 dev wlp0s20f3 proto dhcp metric 600
10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2
169.254.0.0/16 dev wg0 scope link metric 1000
172.30.0.0/22 dev wlp0s20f3 proto kernel scope link src 172.30.0.92 metric
600
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:359
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=91.1.1/20210916142849 (In use)
RebootRequiredPkgs: Error: path contained symlinks.
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to impish on 2021-09-24 (6 days ago)
dmi.bios.date: 06/21/2021
dmi.bios.release: 1.19
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET29W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias:
dmi:bvnLENOVO:bvrN2WET29W(1.19):bd06/21/2021:br1.19:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1945741/+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 1981163] Re: In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince
This sounds very much like bug #1945741, which was an upstream bug (https://bugzilla.mozilla.org/show_bug.cgi?id=1734428), but was marked as fixed 9 months ago. So it's probably a slightly different variation of that bug. Would you mind filing a new bug report at https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird, mentioning that other upstream bug, and sharing the link to it here? ** Bug watch added: Mozilla Bugzilla #1734428 https://bugzilla.mozilla.org/show_bug.cgi?id=1734428 -- 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/1981163 Title: In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince Status in thunderbird package in Ubuntu: New Bug description: In Thunderbird on Ubuntu Gnome, I set Evince as default program to open pdf files from Thunderbird. In received messages, and those saved on "Sent" folder, it works perfectly. But in the "Compose" window: if I add a pdf file to the message, and double-click on it to open and verify it, Thunderbird always uses Firefox to show it. In case Firefox is not installed (has been removed), I have an error message telling there is not associated application for pdf files and to go to Preferences - where Evince is already and still defined as default. It happens since many months and bug is still present in Thunderbird 102 / Ubuntu 22.10 beta. It's not the same as bug 234349 as here, it's not an URL file but directly a pdf joined in a mail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/+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 1983717] [NEW] Monitor layout hotkey does not show single display options
Public bug reported: 0) More detailed description: The default hotkey to switch which monitor to display the desktop on (Super+P) only shows two options: Mirror and Join Displays. There is no option "External Only" or "Built-in Only". This computer is configured with an AMD graphics card plugged into two external monitors, running Ubuntu 22.04 in the Wayland session. 1) lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 2) apt-cache policy gnome-shell gnome-shell: Installed: 42.2-0ubuntu0.2 Candidate: 42.2-0ubuntu0.2 Version table: *** 42.2-0ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) Expected to happen: Meta+P hotkey showing all four possibilities for display configurations (Mirror, Join Displays, External Only, Built-in Only). 4) What happened instead: Only two options appear on screen while pressing Meta+P: "Mirror" and "Join Displays". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 5 09:17:19 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (95 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1983717 Title: Monitor layout hotkey does not show single display options Status in gnome-shell package in Ubuntu: New Bug description: 0) More detailed description: The default hotkey to switch which monitor to display the desktop on (Super+P) only shows two options: Mirror and Join Displays. There is no option "External Only" or "Built-in Only". This computer is configured with an AMD graphics card plugged into two external monitors, running Ubuntu 22.04 in the Wayland session. 1) lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) apt-cache policy gnome-shell gnome-shell: Installed: 42.2-0ubuntu0.2 Candidate: 42.2-0ubuntu0.2 Version table: *** 42.2-0ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) Expected to happen: Meta+P hotkey showing all four possibilities for display configurations (Mirror, Join Displays, External Only, Built-in Only). 4) What happened instead: Only two options appear on screen while pressing Meta+P: "Mirror" and "Join Displays". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 5 09:17:19 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (95 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1983717/+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
That confirms that your chromium snap was updated 2 days ago. Would you say that the problem started happening 2 days ago? -- 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 1983660] Re: Chromium seems to drive all data into swap, until choking
name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 2 days ago, at 17:42 CEST channels: latest/stable:104.0.5112.79 2022-08-03 (2051) 148MB - latest/candidate: 104.0.5112.79 2022-08-03 (2051) 148MB - latest/beta: 104.0.5112.79 2022-08-02 (2051) 148MB - latest/edge: 105.0.5195.19 2022-08-04 (2052) 148MB - installed: 104.0.5112.79(2051) 148MB - -- 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 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
** Also affects: gnome-control-center (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in gnome-control-center package in Ubuntu: New Status in gnome-control-center source package in Jammy: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983645/+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 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
The attachment "gnome-control-center_42.2-1ubuntu3.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in gnome-control-center package in Ubuntu: New Status in gnome-control-center source package in Jammy: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983645/+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
##
snap info chromium
name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: Canonical✓
store-url: https://snapcraft.io/chromium
contact:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license: unset
description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
commands:
- chromium.chromedriver
- chromium
snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/candidate/hwacc
refresh-date: today at 18:55 CST
channels:
latest/stable:104.0.5112.79 2022-08-03 (2051) 148MB -
latest/candidate: 104.0.5112.79 2022-08-03 (2051) 148MB -
latest/beta: 104.0.5112.79 2022-08-02 (2051) 148MB -
latest/edge: 105.0.5195.19 2022-08-04 (2052) 148MB -
###
snap run --shell chromium
env | grep LIBVA
LIBVA_DRIVER_NAME=iHD
vainfo
bash: vainfo: command not found <<== ???
--
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,
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`
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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
ACK on the debdiff in comment #5, I am currently building it (with a slight change to add the bug number to the changelog) and will release it as a security update next week. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: In Progress Status in gdk-pixbuf source package in Focal: New Bug description: [Impact] * A buffer overwrite exists in gdk-pixbuf's thumbnailer. * The GIF loader runs out of memory with specifically crafted files with bad frame data (and images with its sizes) over the integer limit. * After gdk-pixbuf-thum runs out of memory, other apps can and on low RAM systems like my old iMac, the system can completely run out of memory. * Or, in other ways, bad gif files in other applications can open the door for exploits. * Any app using gdk-pixbuf is affected, mainly file managers and image viewers. [Test Plan] * Take the POC's - they can be found in the issue in the GNOME repo * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: - Nautilus, GNOME's file manager - Nemo, Cinnamon's file manager - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes - PCManFM, LXDE's file manager which straight up crashes - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app still usable, no memory issues) - Eye of GNOME (eog) triggers the segfault in syslog - Eye of MATE (eom) segfaults * If you or the system couldn't tell something is wrong, cat /var/log/syslog and enjoy the segfaults or out of memory warnings or even kernel spam. [Where problems could occur] * The patch itself is simple, but since gdk-pixbuf is often used with GTK apps a mistake here could be problematic. * It is possible, and has happened in the past (which has been patched) that other bad GIFs can cause other crashes. * That patch is essentially overflow checks - changes with GLib (GNOME's, not to be confused with glibc) and the functions used in not only the patch but all of gdk-pixbuf can cause problems * Other failures to properly handle GIFs and broken or intentionally tampered GIFs can continue and always will open the door for security holes for other bugs * Again, overall a simple patch but as long as the GIFs remain handled properly, and no changes to the GLib functions are made and to other apps that use gdk-pixbuf (and assuming are not affected by the change and still work), the patch does not have much regression potential. [Other Info] * Besides Buffer overwrite/overflow issues, as aforementioned out of memory errors can happen. * Files attached are examples or crashes * Again, all apps using gdk-pixbuf are affected * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/ * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 * https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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
Can you share the output of `snap info chromium` ? Chromium was recently (2 days ago) updated to a new major version (104), so maybe that's a functional regression that wasn't present in 103 ? -- 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 1816497] Re: [snap] vaapi chromium no video hardware decoding
** Changed in: chromium-browser (Ubuntu)
Assignee: Olivier Tilloy (osomon) => Nathan Teodosio (nteodosio)
--
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,
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`
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
If you updated Snapcraft as indicated, at least the LIBVA path should be
right, so could you please `snap run --shell chromium` and tell us the
output of `env | grep LIBVA` and `vainfo`?
And thank you for your perseverance testing this.
--
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,
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`
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 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_3_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607137/+files/scenario_3_installer.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 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 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_2_appstream.txt" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607136/+files/scenario_2_appstream.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 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 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_2_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607135/+files/scenario_2_installer.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 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 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file
Okay, I've gone down the rabbit hole with this one. It's possible this is 2 separate issues. I tested 3 scenarios: Scenario 1 - Performed a clean Ubuntu Server install (interactive), and installed ubuntu-desktop-minimal post-deployment. After rebooting, the 50appstream config is present, and I installed snap-store and gnome-software. Neither snap-store nor gnome-software showed any .deb packages. Only snaps. I tried re-installing appstream and forcing a refresh of the cache, but still no .deb packages shown. Nothing I have tried in this install has been able to fix the issue. Scenario 2 - I performed a clean install using our automated install image (/var/log/installer contents attached) WITHOUT our appstream config reinstall script that I shared previously. After deployment, ubuntu-desktop-minimal is already installed, and 50appstream config is MISSING (see attachment). Both snap-store and gnome-software only show snaps. No .deb packages. Next, I ran the appstream re-install script I shared previously and rebooted the machine. After the reboot, gnome-software correctly shows .deb packages. However, snap-store is still only showing snaps!!! Scenario 3 - I performed a clean install using our automated install image (/var/log/installer contents attached), this time including our appstream config reinstall script. After the deployment, 50appstream config is PRESENT. Both snap-store and gnome-software work correctly and show both snaps and .deb packages. The varying behaviour between all 3 has completely blown my mind. I really don't know what is the cause of the issue, and potentially this is even 2 separate issues, since in Scenario 1, neither snap-store nor gnome-software work correctly. ** Attachment added: "installer logs for Scenario 1" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607134/+files/scenario_1_installer.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 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 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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
My t460p, Nvida, Intel GPU. Insalled with
sudo snap install --channel candidate/hwacc chromium
LIBVA_MESSAGING_LEVEL=2 chromium
--disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
```
Gtk-Message: 19:02:47.866: Failed to load module "canberra-gtk-module"
Gtk-Message: 19:02:47.868: Failed to load module "canberra-gtk-module"
WARNING: Kernel has no file descriptor comparison support: Operation not
permitted
[21291:21389:0805/190251.215417:ERROR:udev_watcher.cc(98)] Failed to begin udev
enumeration.
Warning: vkCreateInstance: Found no drivers!
Error: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
at CheckVkSuccessImpl
(../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
at CreateVkInstance
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:383)
at Initialize
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:269)
at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:199)
at operator()
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458)
```
There is no libva loading information. There is no video decoder. The
version is not work in my hardware.
--
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,
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`
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
** 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/beta snapcraft
+ 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,
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
VAProfileH264ConstrainedBasel
[Desktop-packages] [Bug 1983660] Re: Chromium seems to drive all data into swap, until choking
No. Chrom(ium) from snap, with snap refresh whenever possible (last two days ago). kubuntu. I myself was surprised, and checked with kernel initially. Nothing. In principle only running Chrome on the Desktop. And when I close it, close to choking, the swap space is being almost freed immediately (well, whatever you expect at that swappiness). I made sure, that after cold re-boot I opened nothing but Chrome. I concede, that I have, what others call, unusually many open tabs, between 25 and 30. Though until recently (?) this never happend. Since I tun a relatively low-powered, fanless CPU I was used to lagging because of high CPU loads. Therefore I was surprised yesterday that the CPU loads (e.g. top) were low at high swap use. Therefore I had expected a kernel problem, until I started Firefox, with my around 20 tabs, and everything was very much back to normal: high CPU loads, medium RAM usage, close to zero swap use. -- 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 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
patch for kinetic ** Patch added: "gnome-control-center_42.2-1ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983645/+attachment/5607123/+files/gnome-control-center_42.2-1ubuntu3.debdiff -- 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/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in gnome-control-center package in Ubuntu: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983645/+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] [NEW] Chromium seems to drive all data into swap, until choking
Public bug reported: 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. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Unusual use of swap space" https://bugs.launchpad.net/bugs/1983660/+attachment/5607125/+files/Screenshot_20220804_161916.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/1983660 Title: Chromium seems to drive all data into swap, until choking Status in chromium-browser package in Ubuntu: New 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 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
patch for jammy ** Patch added: "gnome-control-center_41.7-0ubuntu0.22.04.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983645/+attachment/5607124/+files/gnome-control-center_41.7-0ubuntu0.22.04.4.debdiff ** Changed in: gnome-control-center (Ubuntu) Assignee: Dirk Su (dirksu) => (unassigned) -- 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/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in gnome-control-center package in Ubuntu: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983645/+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
That's unexpected, indeed. Are we talking about chrome, or chromium? Do you have other potentially memory-hungry programs running alongside when that happens? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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 1983502] Re: [snap] seccomp denials for syscall=314 on amd64
Is the crash reporter failing to submit crash reports? If so, it might be a similar issue to https://bugzilla.mozilla.org/show_bug.cgi?id=1732720, which was fixed by staging libcurl4 in the snap. ** Bug watch added: Mozilla Bugzilla #1732720 https://bugzilla.mozilla.org/show_bug.cgi?id=1732720 -- 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/1983502 Title: [snap] seccomp denials for syscall=314 on amd64 Status in thunderbird package in Ubuntu: New Bug description: $ snap list thunderbird Name VersionRev Tracking Publisher Notes thunderbird 102.1.0-2 237 latest/stable canonical✓ - During normal operation, the following is logged: Aug 03 12:07:58 foo kernel: audit: type=1326 audit(1659542878.718:511): auid=1000 uid=1000 gid=1000 ses=9 subj=? pid=154377 comm="thunderbird-bin" exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7e4137c4473d code=0x5 And something similar when the crash reporter executes: Aug 03 12:02:04 foo kernel: audit: type=1326 audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=? pid=150188 comm="crashreporter" exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e syscall=314 compat=0 ip=0x7e5f095e773d code=0x5 # Additional information: $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 $ uname -a Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983502/+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 1875015] Re: Displaylink is extremely slow in Xorg sessions
Installed a package from a PPA won't break the package upgrade. As Timo uploads the package to Unstable. If everything goes smoothly, the next version of xserver-xorg-video-amdgpu will contain the patches and that version will overwrite mine from the PPA. In short, an "apt upgrade" will overwrite it and point to current version from ubuntu-archive. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1983645] [NEW] Can't find 5G option in Network Mode under Mobile Network
Public bug reported: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Assignee: Dirk Su (dirksu) Status: New ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Dirk Su (dirksu) -- 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/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in gnome-control-center package in Ubuntu: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983645/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
Hi Joshua and Pedro, Have you reported the side effects of the fix to those projects you mentioned? If yes could you add the bug reports here? thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: In Progress Status in gdk-pixbuf source package in Focal: New Bug description: [Impact] * A buffer overwrite exists in gdk-pixbuf's thumbnailer. * The GIF loader runs out of memory with specifically crafted files with bad frame data (and images with its sizes) over the integer limit. * After gdk-pixbuf-thum runs out of memory, other apps can and on low RAM systems like my old iMac, the system can completely run out of memory. * Or, in other ways, bad gif files in other applications can open the door for exploits. * Any app using gdk-pixbuf is affected, mainly file managers and image viewers. [Test Plan] * Take the POC's - they can be found in the issue in the GNOME repo * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: - Nautilus, GNOME's file manager - Nemo, Cinnamon's file manager - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes - PCManFM, LXDE's file manager which straight up crashes - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app still usable, no memory issues) - Eye of GNOME (eog) triggers the segfault in syslog - Eye of MATE (eom) segfaults * If you or the system couldn't tell something is wrong, cat /var/log/syslog and enjoy the segfaults or out of memory warnings or even kernel spam. [Where problems could occur] * The patch itself is simple, but since gdk-pixbuf is often used with GTK apps a mistake here could be problematic. * It is possible, and has happened in the past (which has been patched) that other bad GIFs can cause other crashes. * That patch is essentially overflow checks - changes with GLib (GNOME's, not to be confused with glibc) and the functions used in not only the patch but all of gdk-pixbuf can cause problems * Other failures to properly handle GIFs and broken or intentionally tampered GIFs can continue and always will open the door for security holes for other bugs * Again, overall a simple patch but as long as the GIFs remain handled properly, and no changes to the GLib functions are made and to other apps that use gdk-pixbuf (and assuming are not affected by the change and still work), the patch does not have much regression potential. [Other Info] * Besides Buffer overwrite/overflow issues, as aforementioned out of memory errors can happen. * Files attached are examples or crashes * Again, all apps using gdk-pixbuf are affected * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/ * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 * https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1982584] Re: wacom invisible cursor on startup, xorg 22.04
Same here with $ lsusb | grep -i wacom Bus 003 Device 009: ID 056a:033e Wacom Co., Ltd CTH-690 [Intuos Art (M)] $ xinput | grep -i wacom ⎜ ↳ Wacom Intuos PT M 2 Pen stylusid=14 [slave pointer (2)] ⎜ ↳ Wacom Intuos PT M 2 Pad pad id=15 [slave pointer (2)] ⎜ ↳ Wacom Intuos PT M 2 Finger touch id=16 [slave pointer (2)] For me the workaround is to unplug/plug the usb cord of the Wacom tablet then go to Wacom settings screen. After that the cursor is shown and functioning as expected. It's a bit of a hassle to do this after every boot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1982584 Title: wacom invisible cursor on startup, xorg 22.04 Status in mutter package in Ubuntu: Confirmed Bug description: With a Wacom One attached, the mouse cursor doesn't show. The mouse cursor can be made to show if, after logging in using the keyboard, you type the super-key, type "zoom", and arrow key over to zoom, and activate the zoom functionality with the enter key. Then the mouse cursor appears once your view is zoomed in, and you can deactivate the zoom and go about everything as normal with the mouse cursor working normally again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 06:45:04 2022 InstallationDate: Installed on 2022-01-30 (172 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-05-16 (66 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1982584/+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 1966348] Re: seahorse crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1963837 *** https://bugs.launchpad.net/bugs/1963837 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: seahorse (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1966348 Title: seahorse crashed with SIGSEGV in g_main_context_dispatch() Status in seahorse package in Ubuntu: Confirmed Bug description: Just booted up. And this message showed. Reporting the error as its occuring on 22.04 beta build. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: seahorse 41.0-2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:21:06 2022 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2022-03-06 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) ProcCmdline: /usr/bin/seahorse --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_AU:en LANG=en_AU.UTF-8 SegvAnalysis: Segfault happened at: 0x7f0d0d6cc73e:movl $0x1,0xa8(%rax) PC (0x7f0d0d6cc73e) ok source "$0x1" ok destination "0xa8(%rax)" (0x56433f045fcb) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: seahorse StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: seahorse crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1966348/+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
