[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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
[Touch-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 Ubuntu Touch seeded 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:
[Touch-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
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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:
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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:
[Touch-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:
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to systemd 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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:
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 115774] Re: graceful full disk handling. syslog.0 and kern.log.0 grow huge
Still happening on 20.04. I think we should limit this bug to : - Create a mechanism that would prevent rsyslogd to fillup disk. - This would make log turn as soon as there is only XX GB left -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/115774 Title: graceful full disk handling. syslog.0 and kern.log.0 grow huge Status in rsyslog package in Ubuntu: Confirmed Bug description: These two log files recently grew to over 1 Gb each. I only noticed when I booted up and X failed to start, giving a warming about not being able to write to /tmp. I later discovered that this error was due to lack of partition space and that /var/log had become bloated. I deleted syslog.0 and kern.log.0 and all is well. This bug may be related to Bug #71870. My kernel is 2.6.20-15-generic Version is Kubuntu 7.04 My hard drive is partitioned thus: hda1 - WinXP (ntfs) - 10 Gb hda5 - windows user files (ntfs) - 30 Gb hda6 - / (ext3) - 7 Gb hda7 - swap - 2 Gb hda8 - user space (fat32) - 2 Gb hda9 - /home (ext3) - 25 Gb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/115774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop
I m stil wondering if this issue is really related to the systemd bug, current bionic systemd is 237-3ubuntu10.39 and the issue with systemd has been seen since 243 https://github.com/systemd/systemd/issues/14322 So are we sure to target the right issue here ? ** Bug watch added: github.com/systemd/systemd/issues #14322 https://github.com/systemd/systemd/issues/14322 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in systemd package in Ubuntu: Fix Released 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 Conclusion : - Fix is realeased in 20.04 - Fix will never be released ( AFAIK ) in 18.04 --- 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/systemd/+bug/1864057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 : + 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 + + + Conclusion : + + - Fix is realeased in 20.04 + - Fix will never be released ( AFAIK ) in 18.04 --- 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 Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in systemd package in Ubuntu: Fix Released 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 Conclusion : - Fix is realeased in 20.04 - Fix will never be released ( AFAIK ) in 18.04 --- 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
[Touch-packages] [Bug 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop
Thanks timo , I understand this would be never patched in 18.04 ? Can you publish a "workaround" so our clients on 18.04 could avoid it ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in systemd package in Ubuntu: Fix Released 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: 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/systemd/+bug/1864057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1285444] Re: Login Successful, Desktop Never Loads
Are you sure it relates to the bug ? If your problem is related to gnome-shell it is a different bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1285444 Title: Login Successful, Desktop Never Loads Status in at-spi2-core package in Ubuntu: Triaged Bug description: Here is what I encounter 1. Boot computer, boot proceeds normally 2. Reach standard Ubuntu login screen, nothing seems to be amiss 3. Enter user name and password 4. Login disappears, just see the pink "Ubuntu 14.04" background The desktop never loads, not even after ~30 minutes. The launcher never appears, and the Desktop background never changes to the user- configured background. Other features: * Cursor works fine, it can be moved around the screen * No error messages pop up * ALT+F1 etc. can be used to switch to different TTYs; all files on the system appear to be intact * Print screen button works (I will upload a screen shot when I get a chance to copy it onto a USB drive) * Hitting power button pops up a window prompting the user to decide whether to shut down * CTRL+ALT+DELETE prompts the user to log out * Desktop does not load on any user accounts, including the guest account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997020] Re: apport-collect does not work on headless servers
Yes we need some kind of API key that would be given to apport-collect to be authenticated to launchpad automatically without any browser launched This REALLY need when we have a client that cannot start a graphic session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/997020 Title: apport-collect does not work on headless servers Status in apport package in Ubuntu: Triaged Bug description: It is essential that apport-collect works on a headless/non-X installs in order to report bugs. In this case, apport-collect tries to use a text-based browser to attempt to login to Launchpad. I tried lynx, links2, elinks and w3m. With elinks I get the following message: "Your Page Was Stale" after selecting "continue". This bug is related to #556927, #645024 and #683337. As these only concern the functioning of w3m, I would here like to raise the issue that a proper installation must make sure that a compatible text-based browser is installed and set as default. WORKAROUND: Execute the following: sudo apt-get install w3m sudo update-alternatives --set www-browser /usr/bin/w3m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/997020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782679] Re: systemd-resolved can't resolve at all, need to add nameservers to resolve.conf
We seem to hit the same problem here. Can you post you NetworkManager.conf file ? if it was not upgraded correctly that could be the issue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1782679 Title: systemd-resolved can't resolve at all, need to add nameservers to resolve.conf Status in systemd package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 (upgraded from 17.10) on a machine with both ethernet and wifi interfaces. When I boot, my ethernet connection enp0s31f6 is brought up by Network Manager and given three nameserver addresses via DHCP, 10.1.13.10, 10.1.141.10, 10.1.13.36. Running nmcli shows the three nameservers under "DNS configuration". Running "systemd-resolve --status" shows them under a "Link 2 (enp0s31f6)" section. I can do a "ip route get to X" and ping each one successfully. No other connection is active. testuser ☼ systemd-resolve --status Global DNS Domain: orgsdomain.net DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp4s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp0s31f6) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.1.13.10 10.1.141.10 10.1.13.36 DNS Domain: orgsdomain.net However, when I actually try to resolve a name, even the name of one of the nameservers, dig claims that "connection timed out: no servers could be reached". testuser ☼ dig dcpdc001.orgsdomain.net +nocookie ; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> dcpdc001.orgsdomain.net +nocookie ;; global options: +cmd ;; connection timed out; no servers could be reached Note that this name should resolve to 10.1.13.10, the first nameserver. The "+nocookie" option is there to work around an issue with Windows DNS servers. But other than that, the servers themselves work fine if I tell dig where to look: testuser ☼ dig dcpdc001.orgsdomain.net +nocookie @10.1.13.10 ; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> dcpdc001.orgsdomain.net +nocookie @10.1.13.10 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61294 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4000 ;; QUESTION SECTION: ;dcpdc001.orgsdomain.net. IN A ;; ANSWER SECTION: dcpdc001.orgsdomain.net. 3600IN A 10.1.13.10 ;; Query time: 2 msec ;; SERVER: 10.1.13.10#53(10.1.13.10) ;; WHEN: Fri Jul 20 10:56:27 AEST 2018 ;; MSG SIZE rcvd: 65 I have configured resolvconf to use dynamic updates. /etc/resolv.conf points to /run/resolvconf/resolv.conf. This file contains only (non- comments): nameserver 127.0.0.53 search orgsdomain If I add "nameserver 10.1.13.10" to this file manually, suddenly dig can resolve again (without the @...), and anything else that needs to resolve names can do so. Removing the nameserver breaks that again. I don't know much about the servers. They're part of a Windows-based network, but since I can use them if I edit resolv.conf or give dig the address, I don't think they're the issue (except in the sense that maybe they require a feature that systemd-resolved doesn't support?). I increased the logging level of systemd-resolved to "debug" and "journalctl -f -u systemd-resolved" shows this during a failed query: Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Got DNS stub UDP query packet for id 19836 Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Looking up RR for dcpdc001.orgsdomain.net IN A. Jul 20 10:33:23 heerij-ubuntu
[Touch-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
Shall the WPA package be updated in 16.04 ? I guess the impact is so limited that it's possible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in ubiquity source package in Xenial: Confirmed Status in wpa source package in Xenial: Confirmed Bug description: * Steps to reproduce: 1. Install image 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
This affects the entire Ekimia product line also ( intel 8285 M.2 ) We will apply the patch for WPA -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in ubiquity source package in Xenial: Confirmed Status in wpa source package in Xenial: Confirmed Bug description: * Steps to reproduce: 1. Install image 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1181106] Re: Failed to change profile to A2DP
WIth latest Update of Bluez 5.37-0ubuntu5 , the issue is fixed here. I can reconnect in a2dp mode with a paired headset -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1181106 Title: Failed to change profile to A2DP Status in Bluez Utilities: New Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: Fix Released Bug description: I upgraded to 13.04 recently and my A2DP profile, which had been working great under 12.10 is suddenly gone. Neither my blueman applet nor the built-in bluetooth manager applet can connect my external bluetooth speaker to the A2DP profile. They can connect to the bluetooth device itself just fine. Steps I'm using: * using blueman, I can connect to the external bluetooth speaker and view the device in the devices listing * I can connect the device to the Audio sink and I get a message saying it is now connected and will "show in the PulseAudio mixer" * After connecting the external speaker to the audio sink, I can also see the device in the "Play sound through" listing in the Sound system control panel, but the icon has a circle with a line through it. * but if I right-click the device and choose "Audio Profile" from the context menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I get an error message stating "failed to change profile to a2dp" I've already added "Enable=Socket" in /etc/bluetooth/audio.conf, without that I can't pair my headset. Now I can pair it, but I can't activate the A2DP profile. When I try to activate it, I see this message in my syslog : pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no transport I tried the kernel 3.9.0 because of a sound problem with my soundcard, this kernel fixed my soundcard problem, but A2DP still doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1181106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 566381] Re: Lag when using module-loopback
Same on 16.04 ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/566381
Title:
Lag when using module-loopback
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
Binary package hint: pulseaudio
Using
pactl load-module module-loopback
I can route the mic input through output. However, the audio that comes out
is about half a second behind the audio coming in. This is okay for some
things, but for others, like musical instruments, game consoles, etc., the lag
makes it pretty much unusable for these uses.
Back in alsa this used to work fine without lag.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelModules: nls_iso8859_1 nls_cp437 btrfs zlib_deflate crc32c
libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs
reiserfs pata_jmicron acpiphp michael_mic arc4 hidp rfcomm binfmt_misc sco
bridge stp bnep l2cap vboxnetadp vboxnetflt dm_crypt snd_hda_codec_idt
snd_hda_codec_intelhdmi snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss
snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi vboxdrv
snd_rawmidi joydev snd_seq_midi_event lp snd_seq snd_timer snd_seq_device
lib80211_crypt_tkip snd parport soundcore wl dell_wmi btusb psmouse dell_laptop
dcdbas ricoh_mmc snd_page_alloc lib80211 sdhci_pci sdhci led_class serio_raw
bluetooth dm_raid45 xor fbcon tileblit font bitblit softcursor vga16fb vgastate
usbhid hid i915 drm_kms_helper ohci1394 drm i2c_algo_bit ieee1394 sky2
intel_agp ahci video output
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: matthew 10508 F pulseaudio
/dev/snd/pcmC0D0c: matthew 10508 F...m pulseaudio
/dev/snd/pcmC0D0p: matthew 10508 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 21'
Mixer name : 'SigmaTel STAC9228'
Components : 'HDA:14f12c06,14f1000f,0010
HDA:10951392,1028022f,0010 HDA:83847616,1028022f,00100402'
Controls : 23
Simple ctrls : 12
Date: Sun Apr 18 21:42:33 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: pulseaudio
dmi.bios.date: 03/10/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd03/10/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/566381/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631763] Re: Ubuntu needs a GPU accelerated browser
Really good news for firefox VP9+EME is really a great choice for publishers. But still software decoded ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1631763 Title: Ubuntu needs a GPU accelerated browser Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: We all know the Web support of an operating system is becoming more and more important for users. The situation right now in terms of browser Performance and power consumption of GNU/Linux is not really in a good shape compared to the 2 other competitors : Windows and Mac OSX. Windows 10 : Microsoft has shown how its integrated browser is more efficient and less hungry on power consumption than other browsers. Mac OSX: Safari is also showing a great power consumption and integrated features. SO this bug is to track progress for an integrated browser for Ubuntu ( can be firefox, chromium, something else ) that would out of the box : - Use GPU for video decoding - Use GPU for Web 3D rendering like webGL - integrate as much as possible EME HTML5 for DRM support (like firefox 49 for netflix) Please suggest other features in the comments -- Chromium -- For chromium we track progress on https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201 -- Firefox -- Firefox video decode progress should be tracked here : https://bugzilla.mozilla.org/show_bug.cgi?id=563206 Firefox overlay support here https://bugzilla.mozilla.org/show_bug.cgi?id=495727 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1631763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1062447] Re: Please add UOA support for Exchange/Evolution
Still a problem in 16.04 . Can someone detail why GOA cannot be used as is by UOA ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1062447 Title: Please add UOA support for Exchange/Evolution Status in Online Accounts: Account plugins: Confirmed Status in evolution-data-server package in Ubuntu: Fix Released Bug description: Ubuntu Online Accounts does not yet support Exchange accounts (through Evolution). This is probably a blocker for those who use the support in GNOME Online Accounts (where it is supported). See bug 1040193 for the general issue. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1062447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631763] Re: Ubuntu needs a GPU accelerated browser
** Description changed: We all know the Web support of an operating system is becoming more and more important for users. The situation right now in terms of browser Performance and power consumption of GNU/Linux is not really in a good shape compared to the 2 other competitors : Windows and Mac OSX. Windows 10 : Microsoft has shown how its integrated browser is more efficient and less hungry on power consumption than other browsers. Mac OSX: Safari is also showing a great power consumption and integrated features. SO this bug is to track progress for an integrated browser for Ubuntu ( can be firefox, chromium, something else ) that would out of the box : - Use GPU for video decoding - Use GPU for Web 3D rendering like webGL - integrate as much as possible EME HTML5 for DRM support (like firefox 49 for netflix) Please suggest other features in the comments + -- Chromium -- - For chromium we track progress on lp:#1424201 + For chromium we track progress on + https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1424201 + + -- Firefox -- + + Firefox video decode progress should be tracked here : + https://bugzilla.mozilla.org/show_bug.cgi?id=563206 + + Firefox overlay support here + https://bugzilla.mozilla.org/show_bug.cgi?id=495727 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1631763 Title: Ubuntu needs a GPU accelerated browser Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: We all know the Web support of an operating system is becoming more and more important for users. The situation right now in terms of browser Performance and power consumption of GNU/Linux is not really in a good shape compared to the 2 other competitors : Windows and Mac OSX. Windows 10 : Microsoft has shown how its integrated browser is more efficient and less hungry on power consumption than other browsers. Mac OSX: Safari is also showing a great power consumption and integrated features. SO this bug is to track progress for an integrated browser for Ubuntu ( can be firefox, chromium, something else ) that would out of the box : - Use GPU for video decoding - Use GPU for Web 3D rendering like webGL - integrate as much as possible EME HTML5 for DRM support (like firefox 49 for netflix) Please suggest other features in the comments -- Chromium -- For chromium we track progress on https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201 -- Firefox -- Firefox video decode progress should be tracked here : https://bugzilla.mozilla.org/show_bug.cgi?id=563206 Firefox overlay support here https://bugzilla.mozilla.org/show_bug.cgi?id=495727 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1631763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631763] Re: Ubuntu needs a GPU accelerated browser
Can we confirm there is no progress on this ? ** Description changed: We all know the Web support of an operating system is becoming more and more important for users. The situation right now in terms of browser Performance and power consumption of GNU/Linux is not really in a good shape compared to the 2 other competitors : Windows and Mac OSX. Windows 10 : Microsoft has shown how its integrated browser is more efficient and less hungry on power consumption than other browsers. Mac OSX: Safari is also showing a great power consumption and integrated features. + SO this bug is to track progress for an integrated browser for Ubuntu ( + can be firefox, chromium, something else ) that would out of the box : - SO this bug is to track progress for an integrated browser for Ubuntu ( can be firefox, chromium, something else ) that would out of the box : - - - - Use GPU for video decoding + - Use GPU for video decoding - Use GPU for Web 3D rendering like webGL - integrate as much as possible EME HTML5 for DRM support (like firefox 49 for netflix) + Please suggest other features in the comments - Please suggest other features in the comments + + For chromium we track progress on lp:#1424201 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1631763 Title: Ubuntu needs a GPU accelerated browser Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: We all know the Web support of an operating system is becoming more and more important for users. The situation right now in terms of browser Performance and power consumption of GNU/Linux is not really in a good shape compared to the 2 other competitors : Windows and Mac OSX. Windows 10 : Microsoft has shown how its integrated browser is more efficient and less hungry on power consumption than other browsers. Mac OSX: Safari is also showing a great power consumption and integrated features. SO this bug is to track progress for an integrated browser for Ubuntu ( can be firefox, chromium, something else ) that would out of the box : - Use GPU for video decoding - Use GPU for Web 3D rendering like webGL - integrate as much as possible EME HTML5 for DRM support (like firefox 49 for netflix) Please suggest other features in the comments For chromium we track progress on lp:#1424201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1631763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
