[Desktop-packages] [Bug 1981349] Re: wslu prevents from opening files and folders on some situations
We really need to fix this , some more clients had the same problem after installing Gimp ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1981349 Title: wslu prevents from opening files and folders on some situations Status in wslu package in Ubuntu: Confirmed Bug description: With wslu installed, files and locations can't be opened from Gnome Activities View neither on Wayland session nor on Xorg one. The same happens when I try to go to a location from Places Status Indicator extension.In fact, I filed a bug some time ago against this extension, but that bug was expired. Now I found the reason for that bug so I create a bug report against the proper package. The bug report against Places Status Indicator is this one: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1970181 I realized the cause of the bug in Places Status Indicator when I saw this thread: https://answers.launchpad.net/ubuntu/+question/701579 Once I removed wslu from my system (on two different pc's) the problem with the extension has gone and I can open files and folders from Activities view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1981349/+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 1722603] Re: No automatic driver install for Apple facetime camera ( experimental working driver available)
** Description changed: - the facetime camera does not work on Ubuntu 17.10 out of the box. + the integrated facetime camera does not work on Ubuntu 22.04 out of the + box. the current workaround is outlined here: https://github.com/patjak/bcwc_pcie/wiki/Get-Started#additional-notes - would it be possible to have something simpler to follow or perhaps be built in? - --- + would it be possible to have this driver supported by ubuntu-drivers ? + + + Manual Dkms Solution : + + git clone https://github.com/ekimiateam/facetimehd + git clone https://github.com/patjak/facetimehd-firmware + make -C facetimehd-firmware/ deb + cp facetimehd-firmware/debian/*.deb . + cd facetimehd/ + dpkg-buildpackage -us -uc + cd .. + sudo apt install ./facetimehd*.deb + + - + ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: peter 1906 F pulseaudio - /dev/snd/controlC1: peter 1906 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: peter 1906 F pulseaudio + /dev/snd/controlC1: peter 1906 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-04-05 (553 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) MachineType: Apple Inc. MacBookPro12,1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=540e40c6-4d83-4c9e-8dfe-18c9ab5e2234 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: - linux-restricted-modules-4.13.0-12-generic N/A - linux-backports-modules-4.13.0-12-generic N/A - linux-firmware 1.169 + linux-restricted-modules-4.13.0-12-generic N/A + linux-backports-modules-4.13.0-12-generic N/A + linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-09 (1 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- 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/1722603 Title: No automatic driver install for Apple facetime camera ( experimental working driver available) Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Status in linux source package in Artful: Won't Fix Status in ubuntu-drivers-common source package in Artful: New Bug description: the integrated facetime camera does not work on Ubuntu 22.04 out of the box. the current workaround is outlined here: https://github.com/patjak/bcwc_pcie/wiki/Get-Started#additional-notes would it be possible to have this driver supported by ubuntu-drivers ? Manual Dkms Solution : git clone https://github.com/ekimiateam/facetimehd git clone https://github.com/patjak/facetimehd-firmware make -C facetimehd-firmware/ deb cp facetimehd-firmware/debian/*.deb . cd facetimehd/ dpkg-buildpackage -us -uc cd .. sudo apt install ./facetimehd*.deb - ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1906 F pulseaudio /dev/snd/controlC1: peter 1906 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-04-05 (553 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) MachineType: Apple Inc. MacBookPro12,1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=540e40c6-4d83-4c9e-8dfe-18c9ab5e2234 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A
[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
** Description changed: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when most browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS January 2024: - Quickest answer : Install firefox Flatpak https://flathub.org/fr/apps/org.mozilla.firefox - activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true + activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true - - Snap : still not ready + - Snap : Test in Progress - deb from mozilla : not tested. August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when most browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS January 2024: - Quickest answer : Install firefox Flatpak https://flathub.org/fr/apps/org.mozilla.firefox activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true - Snap : Test in Progress - deb from mozilla : not tested. August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1424201] Re: Web browsers lacking hardware-accelerated video decoding
** Description changed: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. - We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS + We will close this bug when most browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS + + January 2024: + + - Quickest answer : Install firefox Flatpak, activate VAAPI with the + flag media.ffmpeg.vaapi.enabled=true + + - Snap : still not ready + - deb from mozilla : not tested. August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works --> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. + -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. ** Description changed: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when most browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS January 2024: - - Quickest answer : Install firefox Flatpak, activate VAAPI with the - flag media.ffmpeg.vaapi.enabled=true + - Quickest answer : Install firefox Flatpak https://flathub.org/fr/apps/org.mozilla.firefox + activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true - - Snap : still not ready + - Snap : still not ready - deb from mozilla : not tested. August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when most browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS January 2024: - Quickest answer : Install firefox Flatpak https://flathub.org/fr/apps/org.mozilla.firefox activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true - Snap : still not ready - deb from mozilla : not tested. August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when
[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
Vaapi in Flatpak Firefox works OOTB now ( Just a flag away) so definitely the best solution. -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
Hi, Very interesting bug on how Canonical destroy the Ubuntu community just "because the don't care" I guess we should stop wasting our customers and time to fix ubuntu pro and move to something else. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+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 1987792] Re: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers
Hi that was a client Laptop and I don't have access to it anymore -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1987792 Title: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers Status in mesa package in Ubuntu: Incomplete Bug description: Sony laptop with AMD RV710 Try to play a DVD with Vaapi mesa drivers installed ALl players crash , example with VLC ( Works great without VAAPI ) libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 [7fd5d8085d50] main generic debug: using glconv module "glconv_vaapi_drm" [7fd5d8001610] main vout display debug: using vout display module "gl" [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4028010] main video output debug: original format sz 720x576, of (0,0), vsz 720x576, 4cc VAOP, sar 16:15, msk r0x0 g0x0 b0x0 [7fd5d4029610] main spu text debug: removing module "freetype" [7fd5d4072b40] main spu text debug: looking for text renderer module matching "any": 2 candidates [7fd5d4072b40] freetype spu text debug: Building font databases. [5601ed37aed0] qt interface debug: Logical video size: 768x576 [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4072b40] freetype spu text debug: Took -23713 microseconds [7fd5d4072b40] main spu text debug: using text renderer module "freetype" [7fd5d409d080] main generic debug: looking for hw decoder module matching "vaapi": 3 candidates [7fd5d409d080] main generic debug: using hw decoder module "vaapi" [7fd5d004efb0] avcodec decoder: Using Mesa Gallium driver 22.0.5 for AMD RV710 (DRM 2.50.0 / 5.15.0-46-generic, LLVM 13.0.1) for hardware decoding [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld chosen by get_format(). [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld requires hwaccel initialisation. [mpeg2video @ 0x7fd5d4087d80] Using deprecated struct vaapi_context in decode. [mpeg2video @ 0x7fd5d4087d80] Using user-supplied decoder context: 0x15/0x16. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 0, 40 bytes) is 0x17. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 1, 288 bytes) is 0x18. [mpeg2video @ 0x7fd5d4087d80] Slice 0 param buffer (48 bytes) is 0x19. [mpeg2video @ 0x7fd5d4087d80] Slice 0 data buffer (176 bytes) is 0x1a. [mpeg2video @ 0x7fd5d4087d80] Slice 1 param buffer (48 bytes) is 0x1b. [mpeg2video @ 0x7fd5d4087d80] Slice 1 data buffer (175 bytes) is 0x1c. [mpeg2video @ 0x7fd5d4087d80] Slice 2 param buffer (48 bytes) is 0x1d. [mpeg2video @ 0x7fd5d4087d80] Slice 2 data buffer (175 bytes) is 0x1e. [mpeg2video @ 0x7fd5d4087d80] Slice 3 param buffer (48 bytes) is 0x1f. [mpeg2video @ 0x7fd5d4087d80] Slice 3 data buffer (175 bytes) is 0x20. [mpeg2video @ 0x7fd5d4087d80] Slice 4 param buffer (48 bytes) is 0x21. [mpeg2video @ 0x7fd5d4087d80] Slice 4 data buffer (175 bytes) is 0x22. [mpeg2video @ 0x7fd5d4087d80] Slice 5 param buffer (48 bytes) is 0x23. [mpeg2video @ 0x7fd5d4087d80] Slice 5 data buffer (175 bytes) is 0x24. [mpeg2video @ 0x7fd5d4087d80] Slice 6 param buffer (48 bytes) is 0x25. [mpeg2video @ 0x7fd5d4087d80] Slice 6 data buffer (175 bytes) is 0x26. [mpeg2video @ 0x7fd5d4087d80] Slice 7 param buffer (48 bytes) is 0x27. [mpeg2video @ 0x7fd5d4087d80] Slice 7 data buffer (175 bytes) is 0x28. [mpeg2video @ 0x7fd5d4087d80] Slice 8 param buffer (48 bytes) is 0x29. [mpeg2video @ 0x7fd5d4087d80] Slice 8 data buffer (175 bytes) is 0x2a. [mpeg2video @ 0x7fd5d4087d80] Slice 9 param buffer (48 bytes) is 0x2b. [mpeg2video @ 0x7fd5d4087d80] Slice 9 data buffer (175 bytes) is 0x2c. [mpeg2video @ 0x7fd5d4087d80] Slice 10 param buffer (48 bytes) is 0x2d. [mpeg2video @ 0x7fd5d4087d80] Slice 10 data buffer (175 bytes) is 0x2e. [mpeg2video @ 0x7fd5d4087d80] Slice 11 param buffer (48 bytes) is 0x2f. [mpeg2video @ 0x7fd5d4087d80] Slice 11 data buffer (175 bytes) is 0x30. [mpeg2video @ 0x7fd5d4087d80] Slice 12 param buffer (48 bytes) is 0x31. [mpeg2video @ 0x7fd5d4087d80] Slice 12 data buffer (175 bytes) is 0x32. [mpeg2video @ 0x7fd5d4087d80] Slice 13 param buffer (48 bytes) is 0x33. [mpeg2video @ 0x7fd5d4087d80] Slice 13 data buffer (175 bytes) is 0x34. [mpeg2video @ 0x7fd5d4087d80] Slice 14 param buffer (48 bytes) is 0x35. [mpeg2video @ 0x7fd5d4087d80] Slice 14 data buffer (175 bytes) is 0x36. [mpeg2video @ 0x7fd5d4087d80] Slice 15 param buffer (48 bytes) is 0x37. [mpeg2video @ 0x7fd5d4087d80] Slice 15 data buffer (571 bytes) is 0x38. [mpeg2video @ 0x7fd5d4087d80] Slice 16 param buffer (48 bytes) is 0x39.
[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
Yes this bug was supposed to solve it , But I don't think it did https://mzl.la/3W6JpMQ -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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
Don't wanna be rude , but don't expect this to work solid one day. I've been asking this to google and canonical for almost 10 years We've worked hours of test and stuff , this is going nowhere. Let's help firefox , time is precious -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: To test the snap with VA-API changes, 1. Install the Chromium snap, sudo snap install --channel candidate/hwacc chromium 2. Start Chromium, snap run chromium 3. Open a video, e.g. one from https://github.com/chthomos/video- media-samples. 4. Enter about:media-internals in the address bar, click the corresponding box (if the video is playing, it will have the "(kPlay)" identifier) and note if the page says VaapiVideoDecoder for kVideoDecoderName. You can alternatively check with intel_gpu_top (from intel-gpu-tools package) that the video engine bars are non zero during playback. --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 2002332] [NEW] [22.04] Cannot see thumbnail in MTP of PTP mode in Nautilus
Public bug reported: Usage of USB to see / copy photos from an Android phone is still useful in 2023 With Ubuntu 22.04 up to date : - Connect your Android phone ( Android 10 lineageos here ) - Choose MTP : open nautilus and browse -> No thumbnail for your pictures - Choose PTP : open nautilus and browse -> No thumbnail for your pictures - Choose PTP : open Shotwell and browse -> Some thumbnails appears Without thumbnails , it is almost impossible to choose what to copy. ** Affects: libmtp (Ubuntu) Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/2002332 Title: [22.04] Cannot see thumbnail in MTP of PTP mode in Nautilus Status in libmtp package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: Usage of USB to see / copy photos from an Android phone is still useful in 2023 With Ubuntu 22.04 up to date : - Connect your Android phone ( Android 10 lineageos here ) - Choose MTP : open nautilus and browse -> No thumbnail for your pictures - Choose PTP : open nautilus and browse -> No thumbnail for your pictures - Choose PTP : open Shotwell and browse -> Some thumbnails appears Without thumbnails , it is almost impossible to choose what to copy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/2002332/+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 1981349] Re: wslu prevents from opening files and folders on some situations
it s because wslu provides www-browser ( like firefox or epiphany ) and gimp-help needs a browser Kind of crazy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1981349 Title: wslu prevents from opening files and folders on some situations Status in wslu package in Ubuntu: Confirmed Bug description: With wslu installed, files and locations can't be opened from Gnome Activities View neither on Wayland session nor on Xorg one. The same happens when I try to go to a location from Places Status Indicator extension.In fact, I filed a bug some time ago against this extension, but that bug was expired. Now I found the reason for that bug so I create a bug report against the proper package. The bug report against Places Status Indicator is this one: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1970181 I realized the cause of the bug in Places Status Indicator when I saw this thread: https://answers.launchpad.net/ubuntu/+question/701579 Once I removed wslu from my system (on two different pc's) the problem with the extension has gone and I can open files and folders from Activities view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1981349/+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 1981349] Re: wslu prevents from opening files and folders on some situations
Really important problem : - WSLU is getting installed automatically as it satisfies www-browser ( which is kind of weird ) - Some gnome extension like DING fail to work , so you cannot open folders from your desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1981349 Title: wslu prevents from opening files and folders on some situations Status in wslu package in Ubuntu: Confirmed Bug description: With wslu installed, files and locations can't be opened from Gnome Activities View on a Wayland session or on a Xorg one. The same happens when I try to go to a location on Places Status Indicator.In fact, I filed a bug some time ago against this extension, but that bug was expired. Now I found the reason and then I create a bug report against the proper package. The bug report against Places Status Indicator is this one: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1970181 And I realized the cause of the bug against the extension when I saw this thread: https://answers.launchpad.net/ubuntu/+question/701579 Once I removed wslu from my system (on two different pc's) the problem with the extension has gone and I can open files and folders from Activities view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1981349/+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 1991809] [NEW] App search based on mime type returns nothing
Public bug reported: When trying to open a file which has no apps associated in nautilus like a .epub You have the button " look for compatible apps" which is great however , gnome-software returns no apps for "application/epub+zip" mime type althou calibre and others can handle them is this a problem with appsstream ? I think THIS IS a very important feature .. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-software 41.5-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 5 16:34:08 2022 InstalledPlugins: gnome-software-plugin-flatpak 41.5-2ubuntu2 gnome-software-plugin-snap41.5-2ubuntu2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1991809 Title: App search based on mime type returns nothing Status in gnome-software package in Ubuntu: New Bug description: When trying to open a file which has no apps associated in nautilus like a .epub You have the button " look for compatible apps" which is great however , gnome-software returns no apps for "application/epub+zip" mime type althou calibre and others can handle them is this a problem with appsstream ? I think THIS IS a very important feature .. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-software 41.5-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 5 16:34:08 2022 InstalledPlugins: gnome-software-plugin-flatpak 41.5-2ubuntu2 gnome-software-plugin-snap41.5-2ubuntu2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1991809/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952934] Re: [essx8336] Intel HDA Sound Card not detected on Ubuntu 20.04
** Description changed: - the intel sound card is not detected and only "dummy output" is - available + [Solution ] + + The complete recipe based on 5.19 is here + https://github.com/thesofproject/linux/wiki/ES8336-support + + Hope that 6.0 mainline will work ... + + [Original bug report ] + + + the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel Also tried without success : - - Booted the 5.4 + - Booted the 5.4 - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1952934 Title: [essx8336] Intel HDA Sound Card not detected on Ubuntu 20.04 Status in Linux: New Status in alsa-driver package in Ubuntu: Confirmed Bug description: [Solution ] The complete recipe based on 5.19 is here https://github.com/thesofproject/linux/wiki/ES8336-support Hope that 6.0 mainline will work ... [Original bug report ] the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel Also tried without success : - Booted the 5.4 - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1987792] [NEW] Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers
Public bug reported: Sony laptop with AMD RV710 Try to play a DVD with Vaapi mesa drivers installed ALl players crash , example with VLC ( Works great without VAAPI ) libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 [7fd5d8085d50] main generic debug: using glconv module "glconv_vaapi_drm" [7fd5d8001610] main vout display debug: using vout display module "gl" [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4028010] main video output debug: original format sz 720x576, of (0,0), vsz 720x576, 4cc VAOP, sar 16:15, msk r0x0 g0x0 b0x0 [7fd5d4029610] main spu text debug: removing module "freetype" [7fd5d4072b40] main spu text debug: looking for text renderer module matching "any": 2 candidates [7fd5d4072b40] freetype spu text debug: Building font databases. [5601ed37aed0] qt interface debug: Logical video size: 768x576 [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4072b40] freetype spu text debug: Took -23713 microseconds [7fd5d4072b40] main spu text debug: using text renderer module "freetype" [7fd5d409d080] main generic debug: looking for hw decoder module matching "vaapi": 3 candidates [7fd5d409d080] main generic debug: using hw decoder module "vaapi" [7fd5d004efb0] avcodec decoder: Using Mesa Gallium driver 22.0.5 for AMD RV710 (DRM 2.50.0 / 5.15.0-46-generic, LLVM 13.0.1) for hardware decoding [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld chosen by get_format(). [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld requires hwaccel initialisation. [mpeg2video @ 0x7fd5d4087d80] Using deprecated struct vaapi_context in decode. [mpeg2video @ 0x7fd5d4087d80] Using user-supplied decoder context: 0x15/0x16. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 0, 40 bytes) is 0x17. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 1, 288 bytes) is 0x18. [mpeg2video @ 0x7fd5d4087d80] Slice 0 param buffer (48 bytes) is 0x19. [mpeg2video @ 0x7fd5d4087d80] Slice 0 data buffer (176 bytes) is 0x1a. [mpeg2video @ 0x7fd5d4087d80] Slice 1 param buffer (48 bytes) is 0x1b. [mpeg2video @ 0x7fd5d4087d80] Slice 1 data buffer (175 bytes) is 0x1c. [mpeg2video @ 0x7fd5d4087d80] Slice 2 param buffer (48 bytes) is 0x1d. [mpeg2video @ 0x7fd5d4087d80] Slice 2 data buffer (175 bytes) is 0x1e. [mpeg2video @ 0x7fd5d4087d80] Slice 3 param buffer (48 bytes) is 0x1f. [mpeg2video @ 0x7fd5d4087d80] Slice 3 data buffer (175 bytes) is 0x20. [mpeg2video @ 0x7fd5d4087d80] Slice 4 param buffer (48 bytes) is 0x21. [mpeg2video @ 0x7fd5d4087d80] Slice 4 data buffer (175 bytes) is 0x22. [mpeg2video @ 0x7fd5d4087d80] Slice 5 param buffer (48 bytes) is 0x23. [mpeg2video @ 0x7fd5d4087d80] Slice 5 data buffer (175 bytes) is 0x24. [mpeg2video @ 0x7fd5d4087d80] Slice 6 param buffer (48 bytes) is 0x25. [mpeg2video @ 0x7fd5d4087d80] Slice 6 data buffer (175 bytes) is 0x26. [mpeg2video @ 0x7fd5d4087d80] Slice 7 param buffer (48 bytes) is 0x27. [mpeg2video @ 0x7fd5d4087d80] Slice 7 data buffer (175 bytes) is 0x28. [mpeg2video @ 0x7fd5d4087d80] Slice 8 param buffer (48 bytes) is 0x29. [mpeg2video @ 0x7fd5d4087d80] Slice 8 data buffer (175 bytes) is 0x2a. [mpeg2video @ 0x7fd5d4087d80] Slice 9 param buffer (48 bytes) is 0x2b. [mpeg2video @ 0x7fd5d4087d80] Slice 9 data buffer (175 bytes) is 0x2c. [mpeg2video @ 0x7fd5d4087d80] Slice 10 param buffer (48 bytes) is 0x2d. [mpeg2video @ 0x7fd5d4087d80] Slice 10 data buffer (175 bytes) is 0x2e. [mpeg2video @ 0x7fd5d4087d80] Slice 11 param buffer (48 bytes) is 0x2f. [mpeg2video @ 0x7fd5d4087d80] Slice 11 data buffer (175 bytes) is 0x30. [mpeg2video @ 0x7fd5d4087d80] Slice 12 param buffer (48 bytes) is 0x31. [mpeg2video @ 0x7fd5d4087d80] Slice 12 data buffer (175 bytes) is 0x32. [mpeg2video @ 0x7fd5d4087d80] Slice 13 param buffer (48 bytes) is 0x33. [mpeg2video @ 0x7fd5d4087d80] Slice 13 data buffer (175 bytes) is 0x34. [mpeg2video @ 0x7fd5d4087d80] Slice 14 param buffer (48 bytes) is 0x35. [mpeg2video @ 0x7fd5d4087d80] Slice 14 data buffer (175 bytes) is 0x36. [mpeg2video @ 0x7fd5d4087d80] Slice 15 param buffer (48 bytes) is 0x37. [mpeg2video @ 0x7fd5d4087d80] Slice 15 data buffer (571 bytes) is 0x38. [mpeg2video @ 0x7fd5d4087d80] Slice 16 param buffer (48 bytes) is 0x39. [mpeg2video @ 0x7fd5d4087d80] Slice 16 data buffer (7664 bytes) is 0x3a. [mpeg2video @ 0x7fd5d4087d80] Slice 17 param buffer (48 bytes) is 0x3b. [mpeg2video @ 0x7fd5d4087d80] Slice 17 data buffer (1387 bytes) is 0x3c. [mpeg2video @ 0x7fd5d4087d80] Slice 18 param buffer (48 bytes) is 0x3d. [mpeg2video @ 0x7fd5d4087d80] Slice 18 data buffer (7428 bytes) is 0x3e. [mpeg2video @ 0x7fd5d4087d80] Slice 19 param buffer (48 bytes) is 0x3f. [mpeg2video @ 0x7fd5d4087d80] Slice 19 data
[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
** Description changed: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS August 2022 : - * Ubuntu 22.04 :Launch firefox snap on Intel Tiger lake -> Check with + * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) - -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding - works + -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works +-> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1424201] Re: Web browsers lacking hardware-accelerated video decoding
** Description changed: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS Auhust 2022 : * Ubuntu 22.04 :Launch firefox snap on Intel Tiger lake -> Check with - intel_gpu_top that no codec are GPU decoded ( either VPA , H264 , H265 - or AV1 ) + intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) + +-> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding + works * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. Ubuntu now will integrate this patch on Snap chromium stable soon , more info here https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. ** Description changed: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS - Auhust 2022 : + August 2022 : * Ubuntu 22.04 :Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) --> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding + -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works * In july 2020, things are getting better : - Chromium : - A patch is used on most distro packages. Ubuntu now will integrate this - patch on Snap chromium stable soon , more info here + A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS August 2022 : * Ubuntu 22.04 :Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1424201] Re: Web browsers lacking hardware-accelerated video decoding
** Description changed: - This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux - browsers. + This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. + We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS - In 2015 I opened this bug , no easy solution was available and battery - drained when playing video in browser was crazy. + Auhust 2022 : - In july 2020, things are getting better : + * Ubuntu 22.04 :Launch firefox snap on Intel Tiger lake -> Check with + intel_gpu_top that no codec are GPU decoded ( either VPA , H264 , H265 + or AV1 ) + + * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. Ubuntu now will integrate this patch on Snap chromium stable soon , more info here https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497 - - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 - We shall close this bug when both browsers will have Va-api decoding - available in Stable. + * In 2015 I opened this bug , no easy solution was available and battery + drained when playing video in browser was crazy. -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS Auhust 2022 : * Ubuntu 22.04 :Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VPA , H264 , H265 or AV1 ) * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. Ubuntu now will integrate this patch on Snap chromium stable soon , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
[Workaround] Use Extension manager to install gnome extensions https://flathub.org/apps/details/com.mattjakeman.ExtensionManager ** Description changed: (initially reported at https://forum.snapcraft.io/t/chrome-gnome-shell- does-not-work-with-chromium-snap/3377) See attached screenshot. + + [Workaround] + Use Extension manager to install gnome extensions + https://flathub.org/apps/details/com.mattjakeman.ExtensionManager -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] Use Extension manager to install gnome extensions https://flathub.org/apps/details/com.mattjakeman.ExtensionManager To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952934] Re: [essx8336] Intel HDA Sound Card not detected on Ubuntu 20.04
So I finally had more info on the Sof-driver by running latest jammy build This is a Everest essx8336 CHip and works is in progress for 5.18 support , will wait for september 2022 ! ** Summary changed: - Intel HDA Sound Card not detected on Ubuntu 20.04 + [essx8336] Intel HDA Sound Card not detected on Ubuntu 20.04 ** Bug watch added: github.com/thesofproject/linux/issues #3248 https://github.com/thesofproject/linux/issues/3248 ** Also affects: sound-2.6 via https://github.com/thesofproject/linux/issues/3248 Importance: Unknown Status: Unknown ** Also affects: linux via https://github.com/thesofproject/linux/issues/3248 Importance: Unknown Status: Unknown ** No longer affects: sound-2.6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1952934 Title: [essx8336] Intel HDA Sound Card not detected on Ubuntu 20.04 Status in Linux: Unknown Status in alsa-driver package in Ubuntu: Confirmed Bug description: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel Also tried without success : - Booted the 5.4 - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1952934/+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 1962836] Re: [NJ50_70CU, Realtek ALC256, Speaker, Internal] No sounds after Resume
Alsa info after suspend http://alsa- project.org/db/?f=5616145ad14337953bcf0df255cc83693c829e2d -- 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/1962836 Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] No sounds after Resume Status in alsa-driver package in Ubuntu: New Bug description: How to reproduce : - With internal speakers - play sound - suspend laptop - Resume - Play sound : no sound but the meter moves and the sound card is selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2268 F pulseaudio /dev/snd/pcmC0D0c: oem2268 F...m pulseaudio /dev/snd/pcmC0D0p: oem2268 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 12:12:49 2022 InstallationDate: Installed on 2022-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 7.18 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.18I dmi.board.asset.tag: Tag 12345 dmi.board.name: NJ50_70CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.12 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.18I:bd10/24/2019:br7.18:efr7.12:svnNotebook:pnNJ50_70CU:pvrNotApplicable:rvnNotebook:rnNJ50_70CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NJ50_70CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-03T11:48:35.145684 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1962836/+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 1962836] [NEW] [NJ50_70CU, Realtek ALC256, Speaker, Internal] No sounds after Resume
Public bug reported: How to reproduce : - With internal speakers - play sound - suspend laptop - Resume - Play sound : no sound but the meter moves and the sound card is selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2268 F pulseaudio /dev/snd/pcmC0D0c: oem2268 F...m pulseaudio /dev/snd/pcmC0D0p: oem2268 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 12:12:49 2022 InstallationDate: Installed on 2022-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 7.18 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.18I dmi.board.asset.tag: Tag 12345 dmi.board.name: NJ50_70CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.12 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.18I:bd10/24/2019:br7.18:efr7.12:svnNotebook:pnNJ50_70CU:pvrNotApplicable:rvnNotebook:rnNJ50_70CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NJ50_70CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-03T11:48:35.145684 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1962836 Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] No sounds after Resume Status in alsa-driver package in Ubuntu: New Bug description: How to reproduce : - With internal speakers - play sound - suspend laptop - Resume - Play sound : no sound but the meter moves and the sound card is selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2268 F pulseaudio /dev/snd/pcmC0D0c: oem2268 F...m pulseaudio /dev/snd/pcmC0D0p: oem2268 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 12:12:49 2022 InstallationDate: Installed on 2022-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 7.18 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.18I dmi.board.asset.tag: Tag 12345 dmi.board.name: NJ50_70CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.12 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.18I:bd10/24/2019:br7.18:efr7.12:svnNotebook:pnNJ50_70CU:pvrNotApplicable:rvnNotebook:rnNJ50_70CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NJ50_70CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-03T11:48:35.145684 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1962836/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1871011] Re: USB scanning and printing broken on focal by ippusbxd (was: hpmud and ippusbxd conflict)
@Robert : you misunderstood , the problem is not the version of the HPLIP , but the conflict with ippusbxd on USB device claiming. Auto configure usb printers is nice but we can live on 20.04 without it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1871011 Title: USB scanning and printing broken on focal by ippusbxd (was: hpmud and ippusbxd conflict) Status in HPLIP: Invalid Status in hplip package in Ubuntu: Expired Status in ippusbxd package in Ubuntu: Confirmed Bug description: SOLUTION : sudo apt remove ippusbxd Initial report - On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3. Previously there was a libmtp (udev) bug erroneously detecting HP printers as mtp devices. This was fixed. Now, I can try to scan-- from both simple-scan and hp-scan, hplip errors out: Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/2: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=3 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=3, altset=0, index=9 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=3 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/4/1: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=0, index=11 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/cc/0: Device or resource busy Printer/scanner is an Officejet 4635. Scanning previously worked just fine a few months ago. Regression? To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1871011/+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 1871011] Re: USB scanning broken on focal by ippusbxd (was: hpmud and ippusbxd conflict)
We had several clients with HP printers that faced this problem. This should really be fixed on LTS 20.04 as there is no simple workaround for the user If ippusbxd is non functionnal I guess it should be removed on next 20.04.4 ** Summary changed: - USB scanning broken on focal by ippusbxd (was: hpmud and ippusbxd conflict) + USB scanning and printing broken on focal by ippusbxd (was: hpmud and ippusbxd conflict) ** Description changed: + SOLUTION : sudo apt remove ippusbxd + + Initial report - + On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3. Previously there was a libmtp (udev) bug erroneously detecting HP printers as mtp devices. This was fixed. Now, I can try to scan-- from both simple-scan and hp-scan, hplip errors out: - Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/2: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=3 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=3, altset=0, index=9 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=3 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/4/1: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=0, index=11 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/cc/0: Device or resource busy Printer/scanner is an Officejet 4635. Scanning previously worked just fine a few months ago. Regression? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1871011 Title: USB scanning and printing broken on focal by ippusbxd (was: hpmud and ippusbxd conflict) Status in HPLIP: Invalid Status in hplip package in Ubuntu: Expired Status in ippusbxd package in Ubuntu: Confirmed Bug description: SOLUTION : sudo apt remove ippusbxd Initial report - On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3. Previously there was a libmtp (udev) bug erroneously detecting HP printers as mtp devices. This was fixed. Now, I can try to scan-- from both simple-scan and hp-scan, hplip errors out: Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/2: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=3 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=3, altset=0, index=9 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=3 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/4/1: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=0, index=11 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/cc/0: Device or resource busy Printer/scanner is an Officejet 4635. Scanning previously worked just fine a few months ago. Regression? To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1871011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952934] Re: Intel HDA Sound Card not detected on Ubuntu 20.04
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+attachment/5551088/+files/dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1952934 Title: Intel HDA Sound Card not detected on Ubuntu 20.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel Also tried without success : - Booted the 5.4 - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952934] Re: Intel HDA Sound Card not detected on Ubuntu 20.04
Reinstalled a fresh 20.04.3 : dmesg attached 6.196452] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [6.196478] snd_hda_intel :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [6.224933] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [6.224960] sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [6.224980] sof-audio-pci :00:1f.3: enabling device ( -> 0002) [6.225234] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [6.225336] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [6.231868] sof-audio-pci :00:1f.3: use msi interrupt mode [6.245453] sof-audio-pci :00:1f.3: hda codecs found, mask 4 [6.245456] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [6.245462] sof-audio-pci :00:1f.3: DMICs detected in NHLT tables: 2 [6.332979] sof-audio-pci :00:1f.3: Firmware info: version 1:6:0-18fab [6.332986] sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:18:0 [6.346627] sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:18:0 [6.371269] sof-audio-pci :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1952934 Title: Intel HDA Sound Card not detected on Ubuntu 20.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel Also tried without success : - Booted the 5.4 - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952934] Re: Intel HDA Sound Card not detected on Ubuntu 20.04
Thnaks hui , dmesg attached , I thought apport-collect would attach it actually ** Changed in: alsa-driver (Ubuntu) Assignee: I-Cat (i-cat) => (unassigned) ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+attachment/5546430/+files/dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1952934 Title: Intel HDA Sound Card not detected on Ubuntu 20.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel Also tried without success : - Booted the 5.4 - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952934] Re: Intel HDA Sound Card not detected on Ubuntu 20.04
@I-cat : the media dir is correct and it is not the issue here. Please don't change the status or assigned like that. ** Changed in: alsa-driver (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1952934 Title: Intel HDA Sound Card not detected on Ubuntu 20.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel Also tried without success : - Booted the 5.4 - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952934] Re: Intel HDA Sound Card not detected on Ubuntu 20.04
** Description changed: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel + + Also tried without success : + + - Booted the 5.4 + - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: oem2217 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1952934 Title: Intel HDA Sound Card not detected on Ubuntu 20.04 Status in alsa-driver package in Ubuntu: New Bug description: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel Also tried without success : - Booted the 5.4 - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952934] [NEW] Intel HDA Sound Card not detected on Ubuntu 20.04
Public bug reported: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1952934 Title: Intel HDA Sound Card not detected on Ubuntu 20.04 Status in alsa-driver package in Ubuntu: New Bug description: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+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 1950484] [NEW] Adding an admin user a Gnome Control Center should set the right groups
Public bug reported: Currently when installing Ubuntu , the default admin belongs to several essential groups : adm cdrom sudo dip plugdev lpadmin lxd sambashare But when adding a user from GCC , the new admin user will only belong to : sudo This leads that the second admin cannot add printers and so on... This is observed on a clean 20.04.3 install ** Affects: gnome-control-center (Ubuntu) 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/1950484 Title: Adding an admin user a Gnome Control Center should set the right groups Status in gnome-control-center package in Ubuntu: New Bug description: Currently when installing Ubuntu , the default admin belongs to several essential groups : adm cdrom sudo dip plugdev lpadmin lxd sambashare But when adding a user from GCC , the new admin user will only belong to : sudo This leads that the second admin cannot add printers and so on... This is observed on a clean 20.04.3 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1950484/+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 1949958] Re: External output Jack produce low volume garbled sound with alc293 on Ubuntu 20.04.3
** Summary changed: - External Jack produce garbled sound with alc293 + External output Jack produce low volume garbled sound with alc293 on Ubuntu 20.04.3 ** Description changed: - External Jack produce garbled sound + External Jack produce low volume garbled sound We tried alc293-dell1 and alc293-dell , but it does not change anything It seems it was working with some older 5.11 kernel + + But We tested a live Ubuntu 20.04.3 with the same fail results. + + It seems the card have recorded some settings ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.12 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip Date: Fri Nov 5 12:06:01 2021 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: pulseaudio 1:13.99.1-1ubuntu3.12 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: focal Uname: Linux 5.11.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1949958 Title: External output Jack produce low volume garbled sound with alc293 on Ubuntu 20.04.3 Status in pulseaudio package in Ubuntu: New Bug description: External Jack produce low volume garbled sound We tried alc293-dell1 and alc293-dell , but it does not change anything It seems it was working with some older 5.11 kernel But We tested a live Ubuntu 20.04.3 with the same fail results. It seems the card have recorded some settings ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.12 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip Date: Fri Nov 5 12:06:01 2021 InstallationDate: Installed on 2020-10-13
[Desktop-packages] [Bug 1949958] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1949958/+attachment/5538406/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1949958 Title: External Jack produce garbled sound with alc293 Status in pulseaudio package in Ubuntu: New Bug description: External Jack produce garbled sound We tried alc293-dell1 and alc293-dell , but it does not change anything It seems it was working with some older 5.11 kernel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.12 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip Date: Fri Nov 5 12:06:01 2021 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: pulseaudio 1:13.99.1-1ubuntu3.12 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: focal Uname: Linux 5.11.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1949958/+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 1949958] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1949958/+attachment/5538410/+files/ProcCpuinfoMinimal.txt ** Summary changed: - External Jack produce garbled sound + External Jack produce garbled sound with alc293 ** Description changed: External Jack produce garbled sound + + We tried alc293-dell1 and alc293-dell , but it does not change anything + + It seems it was working with some older 5.11 kernel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.12 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: pandora3069 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip Date: Fri Nov 5 12:06:01 2021 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=fr_FR.UTF-8 + SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: pandora3069 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: pulseaudio 1:13.99.1-1ubuntu3.12 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: focal Uname: Linux 5.11.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1949958 Title: External Jack produce garbled sound with alc293 Status in pulseaudio package in Ubuntu: New Bug description: External Jack produce garbled sound We tried alc293-dell1 and alc293-dell , but it does not change anything It seems it was working with some older 5.11 kernel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.12 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069
[Desktop-packages] [Bug 1949958] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1949958/+attachment/5538407/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1949958 Title: External Jack produce garbled sound with alc293 Status in pulseaudio package in Ubuntu: New Bug description: External Jack produce garbled sound We tried alc293-dell1 and alc293-dell , but it does not change anything It seems it was working with some older 5.11 kernel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.12 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip Date: Fri Nov 5 12:06:01 2021 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: pulseaudio 1:13.99.1-1ubuntu3.12 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: focal Uname: Linux 5.11.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1949958/+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 1949958] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1949958/+attachment/5538408/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1949958 Title: External Jack produce garbled sound with alc293 Status in pulseaudio package in Ubuntu: New Bug description: External Jack produce garbled sound We tried alc293-dell1 and alc293-dell , but it does not change anything It seems it was working with some older 5.11 kernel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.12 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip Date: Fri Nov 5 12:06:01 2021 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: pulseaudio 1:13.99.1-1ubuntu3.12 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: focal Uname: Linux 5.11.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1949958/+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 1949958] [NEW] External Jack produce garbled sound with alc293
Public bug reported: External Jack produce garbled sound We tried alc293-dell1 and alc293-dell , but it does not change anything It seems it was working with some older 5.11 kernel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.12 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip Date: Fri Nov 5 12:06:01 2021 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: pulseaudio 1:13.99.1-1ubuntu3.12 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: focal Uname: Linux 5.11.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected focal ** Tags added: apport-collected ** Description changed: External Jack produce garbled sound ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.12 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip Date: Fri Nov 5 12:06:01 2021 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias:
[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
Could we track the firefox deb OOTB support ? IMO FF deb still does not use the GPU OOTB to decode video. -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. Ubuntu now will integrate this patch on Snap chromium stable soon , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 We shall close this bug when both browsers will have Va-api decoding available in Stable. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1945047] Re: Gdm does not start anymore on 20.04
Thanks that is the way droid repo that broke . I fixed it by restoring the ubuntu repo version. -- 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/1945047 Title: Gdm does not start anymore on 20.04 Status in mutter package in Ubuntu: Invalid Bug description: After a reboot GDM3 does not start anymore . I could install lightdm and see that login to gnome ( Ubuntu session ) either on XOrg or wayland mode does not work as well. I don't think any of my ppa can generate this problem. XFCE works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.4 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Sep 25 12:31:28 2021 InstallationDate: Installed on 2020-08-13 (407 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2021-09-25T12:11:41.629180 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-13 (407 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: gdm3 3.36.3-0ubuntu0.20.04.4 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Tags: third-party-packages focal Uname: Linux 5.11.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2021-09-25T12:11:41.629180 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1945047/+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 1945047] Re: Gdm does not start anymore on 20.04
Thanks Daniel , Will try to remove waydroid , which was not working anyway -- 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/1945047 Title: Gdm does not start anymore on 20.04 Status in mutter package in Ubuntu: Invalid Bug description: After a reboot GDM3 does not start anymore . I could install lightdm and see that login to gnome ( Ubuntu session ) either on XOrg or wayland mode does not work as well. I don't think any of my ppa can generate this problem. XFCE works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.4 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Sep 25 12:31:28 2021 InstallationDate: Installed on 2020-08-13 (407 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2021-09-25T12:11:41.629180 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-13 (407 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: gdm3 3.36.3-0ubuntu0.20.04.4 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Tags: third-party-packages focal Uname: Linux 5.11.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2021-09-25T12:11:41.629180 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1945047/+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 1945047] [NEW] Gdm does not start anymore on 20.04
Public bug reported: After a reboot GDM3 does not start anymore . I could install lightdm and see that login to gnome ( Ubuntu session ) either on XOrg or wayland mode does not work as well. I don't think any of my ppa can generate this problem. XFCE works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.4 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Sep 25 12:31:28 2021 InstallationDate: Installed on 2020-08-13 (407 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2021-09-25T12:11:41.629180 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-13 (407 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: gdm3 3.36.3-0ubuntu0.20.04.4 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Tags: third-party-packages focal Uname: Linux 5.11.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2021-09-25T12:11:41.629180 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected focal third-party-packages ** Tags added: apport-collected ** Description changed: After a reboot GDM3 does not start anymore . I could install lightdm and see that login to gnome ( Ubuntu session ) either on XOrg or wayland mode does not work as well. I don't think any of my ppa can generate this problem. XFCE works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.4 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Sep 25 12:31:28 2021 InstallationDate: Installed on 2020-08-13 (407 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2021-09-25T12:11:41.629180 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.20 + Architecture: amd64 + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-08-13 (407 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + Package: gdm3 3.36.3-0ubuntu0.20.04.4 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=fr_FR + TERM=xterm-256color + PATH=(custom, no user) + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 + Tags: third-party-packages focal + Uname: Linux 5.11.0-36-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + modified.conffile..etc.gdm3.custom.conf: [modified] + mtime.conffile..etc.gdm3.custom.conf: 2021-09-25T12:11:41.629180 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1945047 Title: Gdm does not start anymore on 20.04 Status in gdm3 package in Ubuntu: New Bug description: After a reboot GDM3 does not start anymore . I could install lightdm and see that login to gnome ( Ubuntu session ) either on XOrg or wayland mode does not work as well. I don't think any of my ppa can generate this problem. XFCE works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.4 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Sep 25 12:31:28 2021 InstallationDate: Installed on 2020-08-13 (407 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2021-09-25T12:11:41.629180 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-13 (407 days ago)
[Desktop-packages] [Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
*** This bug is a duplicate of bug 1901470 *** https://bugs.launchpad.net/bugs/1901470 Just tested on a SAMSUNG S34J550WQR on Focal and everything works great in 21:9 OOTB -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Incomplete Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+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 1939010] [NEW] Cannot manually switch to laptop speakers if headphones are plugged
Public bug reported: In a lot of scenari , one would like to plug its "one jack" headet to use the microphone , but would like to output sound to speakers Ubuntu 20.04 , kernel 5.11 , after plugging the headphone , it become the only option on the sound panel , laptop speakers are not available to be selected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem3009 F pulseaudio /dev/snd/pcmC0D0c: oem3009 F...m pulseaudio /dev/snd/pcmC0D0p: oem3009 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 5 12:55:31 2021 InstallationDate: Installed on 2021-04-29 (97 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2019 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL40_50CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd09/14/2019:br7.6:efr7.1:svnNotebook:pnNL40_50CU:pvrNotApplicable:rvnNotebook:rnNL40_50CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL40_50CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1939010 Title: Cannot manually switch to laptop speakers if headphones are plugged Status in alsa-driver package in Ubuntu: New Bug description: In a lot of scenari , one would like to plug its "one jack" headet to use the microphone , but would like to output sound to speakers Ubuntu 20.04 , kernel 5.11 , after plugging the headphone , it become the only option on the sound panel , laptop speakers are not available to be selected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem3009 F pulseaudio /dev/snd/pcmC0D0c: oem3009 F...m pulseaudio /dev/snd/pcmC0D0p: oem3009 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 5 12:55:31 2021 InstallationDate: Installed on 2021-04-29 (97 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2019 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL40_50CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd09/14/2019:br7.6:efr7.1:svnNotebook:pnNL40_50CU:pvrNotApplicable:rvnNotebook:rnNL40_50CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL40_50CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1939010/+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 964705] Re: System policy prevents modification of network settings for all users
Still happening in Ubuntu 20.04 focal , We need to find some workaround for this , any other mobile or desktop OS can do this ! -- 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/964705 Title: System policy prevents modification of network settings for all users Status in NetworkManager: Invalid Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Debian: Fix Released Status in network-manager package in openSUSE: Fix Released Bug description: This seems like a regression? The screen shot is at http://thesii.org/Screenshot.jpg The nearest link I can find is from the forum area at http://ubuntuforums.org/showthread.php?p=1146 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Sun Mar 25 19:36:45 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120323) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/964705/+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 1077982] Re: A Guest cannot connect easily to a new Wifi network without admin password
This is still happening on 20.04 today -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1077982 Title: A Guest cannot connect easily to a new Wifi network without admin password Status in OEM Priority Project: Invalid Status in network-manager-applet package in Ubuntu: Confirmed Bug description: When a guest is using its guest session and wants to join a new Wifi network, the administrative rights GUI is shown and the guest just cancel. this is because (I guess) by default a new network should be available to all users and thus stored in a way that needs admin rights. A workaround : add manually the Wifi network and uncheck the "available to all users" note : adding the OEM project because It was a blocking issue for testing an Asus Ubuntu computer presented in a shop. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1077982/+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 1102354] Re: Impossible for non-administrator users to connect to new wireless networks
Still happening in 20.04 focal , We need to find some workaround for this , any other mobile or desktop OS can do this ! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1102354 Title: Impossible for non-administrator users to connect to new wireless networks Status in network-manager-applet package in Ubuntu: Confirmed Bug description: I have configured a laptop for a non tech-savvy member of my familiy, and therefore not given his user any administrative rights. It is impossible for him to connect to a new wireless networks, since that requires administrative priviledges. This makes the laptop more or less useless for him. I believe the root cause is that it by default tries to save the network connection and make it avaiable for all users, which requires administrative priviledges. Since it is a non-administrator user that is trying to connec to the network it should not try to add it for all users. Problem has been reproduced on several machines running Ubuntu 12.10, it can easily be triggered: 1. ( Create a user with a standard account ) 2. Log in as a normal users 3. Try to connect to a wireless network - you will now be asked for the password of the administrator account, which the user of course doesn't have. Note, the bug in step 3 will only trigger if another user hasn't previously connected to that network, because then it would already be stored in the system global network settings :~$ lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 :~$ apt-cache policy network-manager network-manager: Installed: 0.9.6.0-0ubuntu7 Candidate: 0.9.6.0-0ubuntu7 Version table: *** 0.9.6.0-0ubuntu7 0 500 http://se.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1102354/+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 1756006] Re: Support suspend-then-hibernate
** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #583 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/583 ** Also affects: gnome-settings-daemon via https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/583 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756006 Title: Support suspend-then-hibernate Status in GNOME Settings Daemon: Unknown Status in gnome-settings-daemon package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Triaged Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1756006/+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 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
Please give a little help here , all my clients have this bug, and no one at canonical can help to confirm it ? That is not serious ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Invalid Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+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 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
Anyone with a 21:9 monitor could apport this ? ** Changed in: xorg-server (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Confirmed Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+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 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
@Dale Sch. (d2o17o717tds) : I don't have this 21:9 monitor right now , could you create a new bug and I'll mark this one as dusplicate , thanks we need to get rid of this -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Incomplete Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+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 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
** Changed in: xorg-server (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: New Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+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
Sorry to use this bug report as a forum but IMO it is useless to spend more time on chromium. Ubuntu & users should define a Blink-based open source browser like Brave that could be supported nicely upstream unlike whats google is doing by removing sync API access with google services -- 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: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --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 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
Thanks for all the valuable info about this problem. I'm not sure I understand if the observed behaviour is the one expected ? On of my client had his Ryzen 2200g workstation broken ( initramfs prompt ) after a 5.8 update , going back to 5.4 worked - Virtualbox module still does not build on 5.8 - Broadcom Wifi module neither Then I don't think 5.8 was ready to be deployed ? Should we force remove linux-hwe package from workstations for now ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
For once I'll make some noise : It's been months , we are using chromium snap and Vaapi support is still not really there on the stable branch, what's wrong ? Migrating to snap has been painful to some users and the point for canonical was to free some time to polish things , which I totally understand , but then , if we still lack behind mac and windows in terms of features like battery life , is this worth the hassle ? Simple question : does canonical run automatic vaapi test ( amd , nvidia , intel ) on each snap release to be sure support is here ? -- 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: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --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 1905555] Re: Xserver crash at start , black screen , 20.04 , Intel HD620
I did it in a Root console as said on #4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/190 Title: Xserver crash at start , black screen , 20.04 , Intel HD620 Status in xorg-server package in Ubuntu: Incomplete Bug description: Xserver crash at start , black screen , 20.04 , Intel HD630 Just happened since yesterday updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 25 12:48:16 2020 DistUpgraded: 2020-09-19 18:32:29,160 DEBUG pid is: 29157 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 (Whiskey Lake) [1558:1325] InstallationDate: Installed on 2019-03-04 (632 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash i8042.reset vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-09-19 (66 days ago) dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/190/+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 1905555] Re: Xserver crash at start , black screen , 20.04 , Intel HD620
the client is on 20.04 ? 'I've tried everything in a root console and get ERROR: Cannot update /var/crash/_usr_lib_xorg_Xorg.121.crash: [Errno 13] Permission denied: '/var/crash/_usr_lib_xorg_Xorg.121.crash' and the crash is not visible on errors.ubuntu.com Why the hell is it so difficult to report crash on 20.04 ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/190 Title: Xserver crash at start , black screen , 20.04 , Intel HD620 Status in xorg-server package in Ubuntu: Incomplete Bug description: Xserver crash at start , black screen , 20.04 , Intel HD630 Just happened since yesterday updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 25 12:48:16 2020 DistUpgraded: 2020-09-19 18:32:29,160 DEBUG pid is: 29157 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 (Whiskey Lake) [1558:1325] InstallationDate: Installed on 2019-03-04 (632 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash i8042.reset vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-09-19 (66 days ago) dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/190/+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 1905555] Re: Xserver crash at start , black screen , 20.04 , Intel HD620
the crash dump ** Attachment added: "_usr_lib_xorg_Xorg.121.crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/190/+attachment/5437868/+files/_usr_lib_xorg_Xorg.121.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/190 Title: Xserver crash at start , black screen , 20.04 , Intel HD620 Status in xorg package in Ubuntu: New Bug description: Xserver crash at start , black screen , 20.04 , Intel HD630 Just happened since yesterday updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 25 12:48:16 2020 DistUpgraded: 2020-09-19 18:32:29,160 DEBUG pid is: 29157 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 (Whiskey Lake) [1558:1325] InstallationDate: Installed on 2019-03-04 (632 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash i8042.reset vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-09-19 (66 days ago) dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/190/+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 1905555] [NEW] Xserver crash at start , black screen , 20.04 , Intel HD620
Public bug reported: Xserver crash at start , black screen , 20.04 , Intel HD630 Just happened since yesterday updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 25 12:48:16 2020 DistUpgraded: 2020-09-19 18:32:29,160 DEBUG pid is: 29157 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 (Whiskey Lake) [1558:1325] InstallationDate: Installed on 2019-03-04 (632 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash i8042.reset vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-09-19 (66 days ago) dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Summary changed: - Xserver crash at start , black screen , 20.04 , Intel HD630 + Xserver crash at start , black screen , 20.04 , Intel HD620 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/190 Title: Xserver crash at start , black screen , 20.04 , Intel HD620 Status in xorg package in Ubuntu: New Bug description: Xserver crash at start , black screen , 20.04 , Intel HD630 Just happened since yesterday updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 25 12:48:16 2020 DistUpgraded: 2020-09-19 18:32:29,160 DEBUG pid is: 29157 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 (Whiskey Lake) [1558:1325] InstallationDate: Installed on 2019-03-04 (632 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash i8042.reset vt.handoff=7 SourcePackage:
[Desktop-packages] [Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
Could some people confirm this Bug ? It's quite annoying -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Incomplete Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+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 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
** Changed in: xorg-server (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Incomplete Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+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 1897917] [NEW] Ubuntu 20.04 does not boot to GDM forever spining wheel
Public bug reported: On a basic Intel laptop : once every 2 boot , the spining whell runs forever and GDM does not show ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-common 2:1.20.8-2ubuntu2.4 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: CasperMD5CheckResult: skip Date: Wed Sep 30 17:29:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: tuxedo_keyboard, 2.0.0, 5.4.0-47-generic, x86_64: installed tuxedo_keyboard, 2.0.0, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics [1558:40c1] InstallationDate: Installed on 2020-08-13 (48 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook NL40_50CU PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=13c54f9c-8969-4e49-822c-24d6f69ac07d ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL40_50CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.09:bd09/14/2019:svnNotebook:pnNL40_50CU:pvrNotApplicable:rvnNotebook:rnNL40_50CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL40_50CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Summary changed: - Ubuntu 20.04 does not boot to GDM forver spining + Ubuntu 20.04 does not boot to GDM forever spining wheel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1897917 Title: Ubuntu 20.04 does not boot to GDM forever spining wheel Status in xorg-server package in Ubuntu: New Bug description: On a basic Intel laptop : once every 2 boot , the spining whell runs forever and GDM does not show ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-common 2:1.20.8-2ubuntu2.4 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: CasperMD5CheckResult: skip Date: Wed Sep 30 17:29:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: tuxedo_keyboard, 2.0.0, 5.4.0-47-generic, x86_64: installed tuxedo_keyboard, 2.0.0, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics [1558:40c1] InstallationDate: Installed on 2020-08-13 (48 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook NL40_50CU PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=13c54f9c-8969-4e49-822c-24d6f69ac07d ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2019 dmi.bios.vendor: INSYDE Corp.
[Desktop-packages] [Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
Client is using 2:1.20.8-2ubuntu2.4 on 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Incomplete Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+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 1894441] [NEW] nvidia 7050 glitch on Nouveau and Xubuntu 20.04
Public bug reported: nvidia 7050 glitch on Nouveau and Xubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sun Sep 6 19:02:23 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C73 [GeForce 7050 / nForce 610i] [10de:07e3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Packard Bell B.V. C73 [GeForce 7050 / nForce 610i] [1631:e038] InstallationDate: Installed on 2020-09-06 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 001 Device 002: ID 0846:4260 NetGear, Inc. WG111v3 54 Mbps Wireless [realtek RTL8187B] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/8p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtl8187, 480M MachineType: Packard Bell BV IMEDIA D9378 AIO ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=b807077b-46c6-4253-9a39-2be7f9e84214 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: PBDV10.P17 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MCP73VT-PM dmi.board.vendor: Packard Bell BV dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell BV dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrPBDV10.P17:bd04/08/2008:svnPackardBellBV:pnIMEDIAD9378AIO:pvrPB80139602:rvnPackardBellBV:rnMCP73VT-PM:rvr1.0:cvnPackardBellBV:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: IMEDIA D9378 AIO dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: PB80139602 dmi.sys.vendor: Packard Bell BV version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1894441 Title: nvidia 7050 glitch on Nouveau and Xubuntu 20.04 Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: nvidia 7050 glitch on Nouveau and Xubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sun Sep 6 19:02:23 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C73 [GeForce 7050 / nForce 610i] [10de:07e3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Packard Bell B.V. C73 [GeForce 7050 / nForce 610i] [1631:e038] InstallationDate: Installed on 2020-09-06 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 001 Device 002: ID 0846:4260 NetGear, Inc. WG111v3 54 Mbps Wireless [realtek RTL8187B] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/8p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtl8187, 480M MachineType: Packard Bell BV IMEDIA D9378 AIO ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=b807077b-46c6-4253-9a39-2be7f9e84214 ro
[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
** Description changed: - The chromium team has done a great job to totally disable hardware - decoding on Linux. + This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux + browsers. - Even ignoring the GPU blacklist does not enable GPU decoding. + In 2015 I opened this bug , no easy solution was available and battery + drained when playing video in browser was crazy. - How ever the patch is quite simple and it's already working using this - PPA ( using libVA ) : + In july 2020, things are getting better : - https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev + - Chromium : - the corresponding patch is here : + A patch is used on most distro packages. Ubuntu now will integrate this + patch on Snap chromium stable soon , more info here + https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497 - http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- - browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff - that would be great if we could have this patch indefault Ubuntu - chromium build, this situation is really sad right now, google use linux - to make chromeOS so chromebook are really good at playing videos but - GNU/Linux chromium is slow at doing it. + - Firefox : + + Firefox team has done a great job and now Va-api decoding in Wayland is + possible and X11 is possible in nightly ! + + Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 + + We shall close this bug when both browsers will have Va-api decoding + available in Stable. -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. Ubuntu now will integrate this patch on Snap chromium stable soon , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 We shall close this bug when both browsers will have Va-api decoding available in Stable. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
@vita-cell : Same here on 20.04 , no OSK in oem-config :-( , did you open a new bug ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-settings-daemon source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+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
Failure report : - distro version : Ubuntu 20.04 - GPU Hardware used : Intel pentium 5000 so HD630 ? - Codec used : VP9 On youtube , H264 on vimeo video is totally scrambled on H264/VP9 or even does not start on vimeo. Netflix and bitmovin DRM test Works great, which means that Widevine does not use GPU. ** Description changed: News : - - Candidate Chromium 81 Snap with vaapi enabled can be installed with : + - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium - - Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals + Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in + about:media-internals Widevine DRM streams will have DecryptingVideoDecoder - - Please report success/failure with + Please report success/failure with - distro version - - GPU Hardware used - - Codec used - + - GPU Hardware used + - Codec used --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: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --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 1863258] Re: [Snap] Install the widevine binary upon request in Chromium
For some reason , chromium 81 installed automatically the widevine component now , and only a restart of chromium is need to have Widevine working. THis could be because in snap mode it can write on its own lib directory. ** Description changed: Use case : - Start a video on netflix.com ( with chrome/ubuntu user agent ) - Get a mysterious Netflix Error saying your browser is not supported - Start Firefox and watch your video Solution : - Detects when browsing a website that may need widevine ( see how firefox team did ) - ask user if he wants this non-free binary plugin - Run some script like https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 that would copy the widevine plugin in snap user directory - Notes : - - Widevine versions and binary url from mozilla - https://hg.mozilla.org/releases/mozilla- - beta/file/default/toolkit/content/gmp-sources/widevinecdm.json + To test if Widevine Works : https://bitmovin.com/demos/drm + + + - Widevine versions and binary url from mozilla https://hg.mozilla.org/releases/mozilla-beta/file/default/toolkit/content/gmp-sources/widevinecdm.json -- 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/1863258 Title: [Snap] Install the widevine binary upon request in Chromium Status in chromium-browser package in Ubuntu: New Bug description: Use case : - Start a video on netflix.com ( with chrome/ubuntu user agent ) - Get a mysterious Netflix Error saying your browser is not supported - Start Firefox and watch your video Solution : - Detects when browsing a website that may need widevine ( see how firefox team did ) - ask user if he wants this non-free binary plugin - Run some script like https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 that would copy the widevine plugin in snap user directory Notes : To test if Widevine Works : https://bitmovin.com/demos/drm - Widevine versions and binary url from mozilla https://hg.mozilla.org/releases/mozilla-beta/file/default/toolkit/content/gmp-sources/widevinecdm.json To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863258/+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: News : - - Beta Chromium 80 Snap with vaapi enabled : + - Candidate Chromium 81 Snap with vaapi enabled can be installed with : - https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- - source-enable- - vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap + sudo snap install --channel=candidate/vaapi chromium - Install it with --devmode + + Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals + + Widevine DRM streams will have DecryptingVideoDecoder + + + Please report success/failure with + + - distro version + - GPU Hardware used + - Codec used --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: News : - Candidate Chromium 81 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --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
@nicolas :that s because of https://bugs.launchpad.net/libva/+bug/1698287 I guess -- 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: News : - Beta Chromium 80 Snap with vaapi enabled : https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- source-enable- vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap Install it with --devmode --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 1868117] Re: [snap] Adapt chromium user agent to avoid "not supported browser"
You are offtopic here , the same problems happens in 18.04 with the repo version of chromium. it is just that we try to focus on snap, but we shall backport this use agent patch on repo version -- 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/1868117 Title: [snap] Adapt chromium user agent to avoid "not supported browser" Status in chromium-browser package in Ubuntu: Triaged Bug description: Currently some websites like netflix.com and web.whatsapp.com does not recognize chromium Ubuntu as chrome because of the different user agent. We need to find a way like vivaldi to avoid such problems for casual users. Current snap chromium UA : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868117/+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 1433774] Re: When double clicking an executable bash script in file manager, it opens in gedit rather than executing
IN our Setup script we do : gsettings set org.gnome.nautilus.preferences executable-text-activation ask So the user can decide if he wants to execute it . This should be the default behaviour. if security risk is too high, then we should create a default "script executor" that would warn the user harder like on Windows 10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1433774 Title: When double clicking an executable bash script in file manager, it opens in gedit rather than executing Status in nautilus package in Ubuntu: Triaged Bug description: Download https://www.torproject.org/dist/torbrowser/4.0.4/tor-browser- linux64-4.0.4_en-US.tar.xz and extract it to a folder. Navigate to that folder in the GNOME file manager. Double click "start-tor-browser". Expected result: The script executes and launches the browser. Actual result: The script opens in gedit. Even when right clicking it, "Run" is not listed as an option anywhere. It's not even an option under "Open With... -> Other Application". The only way to run it is from a terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.7 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 18 16:00:48 2015 GsettingsChanges: InstallationDate: Installed on 2015-03-06 (12 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1433774/+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 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job
Several clients told us this problem as Well in 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1073669 Title: Bluetooth won't stay disabled after reboot due to early upstart job Status in rfkill package in Ubuntu: Confirmed Bug description: Using a Dell XPS 13 with Ubuntu 12.04. In order to restore RF interfaces to their previous state between boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill- store.conf (run while shutting down) and rfkill-restore.conf (run when starting up). However, while rfkill-restore.conf starts on the Upstart local-filesystems signal, there is a high probability that the RF kill switches in /sys/class/rfkill/ still won't yet be populated (i.e. every time on the Dell XPS 13). This results in behavior like the following: 1. Disable bluetooth via applet. 2. Reboot. 3. Login. 4. Observe bluetooth is re-enabled! Bluetooth should have stayed disabled, but since the kill switches weren't present when rfkill-restore was run, the kill switch states were not restored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+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
Test on 20.04 on Pentium N5000 : - Chromium show "unknown libva error" from the start. - VAAPI is not used -- 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: News : - Beta Chromium 80 Snap with vaapi enabled : https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- source-enable- vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap Install it with --devmode --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: + News : + + - Beta Chromium 80 Snap with vaapi enabled : + + https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- + source-enable- + vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap + + Install it with --devmode + + + --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` + 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: News : - Beta Chromium 80 Snap with vaapi enabled : https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- source-enable- vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap Install it with --devmode --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 1863258] Re: [Snap] Install the widevine binary upon request in Chromium
Brave have implented their own Widevine module downloader : https://github.com/brave/brave-browser/pull/3300/files -- 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/1863258 Title: [Snap] Install the widevine binary upon request in Chromium Status in chromium-browser package in Ubuntu: New Bug description: Use case : - Start a video on netflix.com ( with chrome/ubuntu user agent ) - Get a mysterious Netflix Error saying your browser is not supported - Start Firefox and watch your video Solution : - Detects when browsing a website that may need widevine ( see how firefox team did ) - ask user if he wants this non-free binary plugin - Run some script like https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 that would copy the widevine plugin in snap user directory Notes : - Widevine versions and binary url from mozilla https://hg.mozilla.org/releases/mozilla- beta/file/default/toolkit/content/gmp-sources/widevinecdm.json To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863258/+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 1863258] Re: [Snap] Install the widevine binary upon request in Chromium snap
** Summary changed: - Install the widevine binary upon request in Chromium snap + [Snap] Install the widevine binary upon request in Chromium snap ** Summary changed: - [Snap] Install the widevine binary upon request in Chromium snap + [Snap] Install the widevine binary upon request in Chromium -- 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/1863258 Title: [Snap] Install the widevine binary upon request in Chromium Status in chromium-browser package in Ubuntu: New Bug description: Use case : - Start a video on netflix.com ( with chrome/ubuntu user agent ) - Get a mysterious Netflix Error saying your browser is not supported - Start Firefox and watch your video Solution : - Detects when browsing a website that may need widevine ( see how firefox team did ) - ask user if he wants this non-free binary plugin - Run some script like https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 that would copy the widevine plugin in snap user directory Notes : - Widevine versions and binary url from mozilla https://hg.mozilla.org/releases/mozilla- beta/file/default/toolkit/content/gmp-sources/widevinecdm.json To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863258/+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 1872390] Re: 193% CPU usage while using webex with chromium
You would use chrome://media-internals/ To know if a video is gpudecoded ( MOjo) or soft (vpx or ffmpeg) But all default version are soft. -- 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/1872390 Title: 193% CPU usage while using webex with chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: 193% CPU usage while using webex with chromium. The process seems associated with audio. When the process was killed. The voice was muted. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEaeIgAQEBASAbAQOAKxh46tr1pFVSnycOUFS/7gCBwAEBAQEBAQEBAQEBAQEBZiFWqlEAHjBGjzMAsuwQAAAe/QAyTB5TDgAKICAgICAg/ABWWDIwNwogICAgICAg/wBIOExNUVMwMTg1ODUKAbQCAxthIwkHB4MBAABnAwwAIACALUOQhALiAA+MCtCKIOAtEBA+lgCgWgAAKQ== modes: 1366x768 1920x1080 1920x1080 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGr+1hAAAaAQSlIhN4Alklk1hZkykmUFQBAQEBAQEBAQEBAQEBAQEBeDeAtHA4LkBsMKoAWMEQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU2SEFOMDYuMSAKANo= modes: 1920x1080 Date: Mon Apr 13 11:01:39 2020 Desktop-Session: 'gnome' '/etc/xdg/xdg-gnome:/etc/xdg' '/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2018-04-29 (714 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Load-Avg-1min: 6.54 Load-Processes-Running-Percent: 0.3% MachineType: ASUSTeK COMPUTER INC. FX503VD ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=8d5334b6-ef1c-42d3-880c-f5d4c937cba2 ro quiet splash tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait mds=full,nosmt quiet splash tpm_tis.interrupts=0 acpi_osi=Linux acpi_backlight=vendor i915.preliminary_hw_support=1 idle=nomwait mds=full,nosmt vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2019-12-20 (114 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.308:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1872390/+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 1866721] Re: [Snap] Unable to use microphone in chrome
I'm not use this is fixed on the snapstore side ? See the default permissions when I "reinstall" chromium snap stable (81) on my 18.04 ** Summary changed: - Unable to use microphone in chrome + [Snap] Unable to use microphone in chrome -- 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/1866721 Title: [Snap] Unable to use microphone in chrome Status in chromium-browser package in Ubuntu: In Progress Bug description: Running Ubuntu 19.10 and the chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 package I am unable to use my microphone with sites that support it, such as discord. I can hear audio from websites like Youtube, but sites that want to use my microphone fail to do so, even though I give permission. I've tested with Hubs by Mozilla, Discord and https://www.onlinemictest.com/ All three properly prompt for permission, but then act as if I refused to give it when choose "allow". If I start chrome from the command line, when this happens I see this in the output [73233:73233:0309/165624.013771:ERROR:pulse_util.cc(300)] pa_operation is nullptr. The https://www.onlinemictest.com/ reports "Microphone not authorized. Please check your media permissions settings." My microphone works fine in Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866721/+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 1866721] Re: [Snap] Unable to use microphone in chrome
** Attachment added: "Capture d’écran de 2020-04-23 09-07-32.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866721/+attachment/5358338/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202020-04-23%2009-07-32.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/1866721 Title: [Snap] Unable to use microphone in chrome Status in chromium-browser package in Ubuntu: In Progress Bug description: Running Ubuntu 19.10 and the chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 package I am unable to use my microphone with sites that support it, such as discord. I can hear audio from websites like Youtube, but sites that want to use my microphone fail to do so, even though I give permission. I've tested with Hubs by Mozilla, Discord and https://www.onlinemictest.com/ All three properly prompt for permission, but then act as if I refused to give it when choose "allow". If I start chrome from the command line, when this happens I see this in the output [73233:73233:0309/165624.013771:ERROR:pulse_util.cc(300)] pa_operation is nullptr. The https://www.onlinemictest.com/ reports "Microphone not authorized. Please check your media permissions settings." My microphone works fine in Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866721/+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 1872390] Re: 193% CPU usage while using webex with chromium
Neither chromium nor chrome on linux are gpu video decoding capable. You have to use Brave for this ( with limitations) I guess Webex use Webrtc ( So may be VP8 ) Check the last section of chrome://gpu/ to know what decoding is supported. -- 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/1872390 Title: 193% CPU usage while using webex with chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: 193% CPU usage while using webex with chromium. The process seems associated with audio. When the process was killed. The voice was muted. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEaeIgAQEBASAbAQOAKxh46tr1pFVSnycOUFS/7gCBwAEBAQEBAQEBAQEBAQEBZiFWqlEAHjBGjzMAsuwQAAAe/QAyTB5TDgAKICAgICAg/ABWWDIwNwogICAgICAg/wBIOExNUVMwMTg1ODUKAbQCAxthIwkHB4MBAABnAwwAIACALUOQhALiAA+MCtCKIOAtEBA+lgCgWgAAKQ== modes: 1366x768 1920x1080 1920x1080 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGr+1hAAAaAQSlIhN4Alklk1hZkykmUFQBAQEBAQEBAQEBAQEBAQEBeDeAtHA4LkBsMKoAWMEQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU2SEFOMDYuMSAKANo= modes: 1920x1080 Date: Mon Apr 13 11:01:39 2020 Desktop-Session: 'gnome' '/etc/xdg/xdg-gnome:/etc/xdg' '/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2018-04-29 (714 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Load-Avg-1min: 6.54 Load-Processes-Running-Percent: 0.3% MachineType: ASUSTeK COMPUTER INC. FX503VD ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=8d5334b6-ef1c-42d3-880c-f5d4c937cba2 ro quiet splash tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait mds=full,nosmt quiet splash tpm_tis.interrupts=0 acpi_osi=Linux acpi_backlight=vendor i915.preliminary_hw_support=1 idle=nomwait mds=full,nosmt vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2019-12-20 (114 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.308:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1872390/+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 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
Confirmed on 81 -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Triaged Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths.  tracking:candidate installed: 62.0.3202.94 (123) 246MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+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
Here is my few tests from yesterday : Platform : pentium Kabylake mobile - YouTube VP90 1080p : MojoVideoDecoder - 15% CPU - 8-10W battery - Netflix H264 720p ? ( https://bit.ly/3apopqR) : DecryptingVideoDecoder - 20% CPU - 12-15W battery I'm then looking for info about DecryptingVideoDecoder when Widevine is used , how is video decoded. Bacause when looking to compare LinuxLaptops with MacBooks on "Netflix battery time" -- 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: 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 1868117] [NEW] Adapt chromium user agent to avoid "not supported browser"
Public bug reported: Currently some websites like netflix.com and web.whatsapp.com does not recognize chromium Ubuntu as chrome because of the different user agent. We need to find a way like vivaldi to avoid such problems for casual users. Current snap chromium UA : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1868117 Title: Adapt chromium user agent to avoid "not supported browser" Status in chromium-browser package in Ubuntu: New Bug description: Currently some websites like netflix.com and web.whatsapp.com does not recognize chromium Ubuntu as chrome because of the different user agent. We need to find a way like vivaldi to avoid such problems for casual users. Current snap chromium UA : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868117/+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 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
As I said earlier I totally agree with the comment above : Manual whitelisting from the snap team will always be a blocker for such a widely adopted use of an important browser. That will push people to use chrome which IMO a failure on the libre software side. -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+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 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop
** Description changed: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 + + + Notes : + Possible Root cause : + + [ 9.014] (EE) modeset(0): drmSetMaster failed: Permission denied + [ 9.014] (EE) + Fatal server error: + [ 9.014] (EE) AddScreen/ScreenInit failed for driver 0 + [ 9.014] (EE) + + + It seems related to systemd : + + https://github.com/systemd/systemd/issues/13943 + + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: Incomplete Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 Notes : Possible Root cause : [ 9.014] (EE) modeset(0): drmSetMaster failed: Permission denied [ 9.014] (EE) Fatal server error: [ 9.014] (EE) AddScreen/ScreenInit failed for driver 0 [ 9.014] (EE) It seems related to systemd : https://github.com/systemd/systemd/issues/13943 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron:
[Desktop-packages] [Bug 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop
@Daniel : similar issue here on arch https://bbs.archlinux.org/viewtopic.php?id=250892 Says fixed with systemd 244 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: Incomplete Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+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 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop
Thanks daniel /var/crash is empty Whoopsie did not report any crash so far on errors.ubuntu.com For years we disabled apport to reduce end-user interaction, is this why ? I Will try to find more logs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: Incomplete Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+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 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop
@Timo : did you mean "Run 'dmesg > dmesg.txt' when booting *with nomodeset and attach it here." ? Because We never boot with nomodeset -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: Incomplete Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+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 1864057] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1864057/+attachment/5329826/+files/XorgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: New Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+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 1864057] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1864057/+attachment/5329821/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: New Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+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 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop
apport information ** Tags added: apport-collected ubuntu ** Description changed: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encouter that since kernel 5.3 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + DistUpgraded: Fresh install + DistroCodename: bionic + DistroRelease: Ubuntu 18.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes + GraphicsCard: + Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) +Subsystem: CLEVO/KAPOK Computer Device [1558:1325] + InstallationDate: Installed on 2019-03-04 (353 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd + Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. + Bus 001 Device 004: ID 8087:0025 Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Notebook N150ZU + Package: xorg-server (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=en_AG.utf8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 + Tags: bionic ubuntu + Uname: Linux 5.3.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 10/19/2018 + dmi.bios.vendor: INSYDE Corp. + dmi.bios.version: 1.07.01 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: N150ZU + dmi.board.vendor: Notebook + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: No Enclosure + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: + dmi.product.family: Not Applicable + dmi.product.name: N150ZU + dmi.product.sku: Not Applicable + dmi.product.version: Not Applicable + dmi.sys.vendor: Notebook + version.compiz: compiz N/A + version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 + version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 + version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 + version.xserver-xorg-core: xserver-xorg-core N/A + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A + version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A + version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1864057/+attachment/5329817/+files/BootLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: New Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True
[Desktop-packages] [Bug 1864057] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1864057/+attachment/5329824/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: New Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+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 1864057] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1864057/+attachment/5329818/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: New Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+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 1864057] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1864057/+attachment/5329819/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: New Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+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 1864057] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1864057/+attachment/5329827/+files/XorgLogOld.txt ** Description changed: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - - it seems user encouter that since kernel 5.3 - --- + - it seems user encounter that since kernel 5.3 + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) -Subsystem: CLEVO/KAPOK Computer Device [1558:1325] + Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) + Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd - Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. - Bus 001 Device 004: ID 8087:0025 Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd + Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. + Bus 001 Device 004: ID 8087:0025 Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=en_AG.utf8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=en_AG.utf8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: - + _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: New Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType:
[Desktop-packages] [Bug 1864057] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1864057/+attachment/5329823/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: New Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+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 1864057] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1864057/+attachment/5329820/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: New Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+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 1864057] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1864057/+attachment/5329822/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: New Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+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 1864057] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1864057/+attachment/5329825/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: New Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+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 1864057] [NEW] Xorg Server terminated with error (1) on Intel/18.04 Laptop
Public bug reported: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic ubuntu ** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in xorg-server package in Ubuntu: New Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook