[Touch-packages] [Bug 1881715] Re: package libopencv-dnn-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/opencv4/opencv2/dnn/all_layers.hpp', which is also in package
libopencv-dev 4.1.1-2-gd5a58aa75 Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Changed in: opencv (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1881715 Title: package libopencv-dnn-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/opencv4/opencv2/dnn/all_layers.hpp', which is also in package libopencv-dev 4.1.1-2-gd5a58aa75 Status in opencv package in Ubuntu: Invalid Bug description: Didn't know what exactly happened. I'm using the system mostly for ML purposes with Nvidia drivers and ML frameworks. Upgraded from 18.04 to 20.04 today and ran into some errors with libopencv. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libopencv-dnn-dev (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 2 08:58:20 2020 ErrorMessage: trying to overwrite '/usr/include/opencv4/opencv2/dnn/all_layers.hpp', which is also in package libopencv-dev 4.1.1-2-gd5a58aa75 InstallationDate: Installed on 2018-07-07 (695 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 2.0.2ubuntu0.1 SourcePackage: opencv Title: package libopencv-dnn-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/opencv4/opencv2/dnn/all_layers.hpp', which is also in package libopencv-dev 4.1.1-2-gd5a58aa75 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1881715/+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 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.
For more information, this bug causes the headset to be not detected when plugged into the combo headset port. In addition, the other microphone jack does not work also. I tried mapping pins in HDAjackretask in these are my findings: Mapping 0x19 to Microphone and 0x21 to Headphone will allow the microphone from the combo jackk to work. The headphones are also detected when plugged in, however, no sound is being output to the headphones. -- 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/1877640 Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.4 LTS dual boot with Windows 10. On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, tried even 5.7-rc4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corsarstl 1728 F pulseaudio /dev/snd/pcmC0D0p: corsarstl 1728 F...m pulseaudio /dev/snd/controlC1: corsarstl 1728 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:25:27 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio /dev/snd/controlC1: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502GV.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502GV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus M dmi.product.name: Zephyrus M GU502GV_GU502GV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877640/+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 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.
Having the exact same issue running on Manjaro! Many other people have reported the same issue on this particular laptop. I've filed a bug report on bugzilla but have not received any help yet. Anyone else have any ideas on what we can do to solve this issue? -- 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/1877640 Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.4 LTS dual boot with Windows 10. On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, tried even 5.7-rc4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corsarstl 1728 F pulseaudio /dev/snd/pcmC0D0p: corsarstl 1728 F...m pulseaudio /dev/snd/controlC1: corsarstl 1728 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:25:27 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio /dev/snd/controlC1: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502GV.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502GV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus M dmi.product.name: Zephyrus M GU502GV_GU502GV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877640/+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 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => 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/1877640 Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.4 LTS dual boot with Windows 10. On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, tried even 5.7-rc4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corsarstl 1728 F pulseaudio /dev/snd/pcmC0D0p: corsarstl 1728 F...m pulseaudio /dev/snd/controlC1: corsarstl 1728 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:25:27 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio /dev/snd/controlC1: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502GV.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502GV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus M dmi.product.name: Zephyrus M GU502GV_GU502GV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877640/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3
Keeping im-config out of launching and configuring IBus was reported in comment #20 to be one way to get rid of the issue. Through im-config 0.45-1 we do just that, i.e. for GNOME desktops we leave the launch and configuration of IBus to GNOME. ** Changed in: im-config (Ubuntu) Status: New => Fix Released ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: ibus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1882415 Title: Graphical artifact in top-right corner, owned by ibus-ui-gtk3 Status in im-config package in Ubuntu: Fix Released Bug description: Ubuntu 20.04, Gnome 3.36.2, Nvidia Small gray line in top-right corner. More precisely, it happens to be in the corner in 1920x1080 resolution. Not present in smaller resolutions. In panning mode it's fixed to panel, not screen. Present on the panel and on fullscreen windows but not in overview. Not clickable (prevents me from clicking button underneath it). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2014-11-12 (2037 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 Tags: focal Uname: Linux 5.4.0-37-lowlatency x86_64 UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1882415/+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 1890913] Re: init is using 100% of processor
** Tags added: block-proposed ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- 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/1890913 Title: init is using 100% of processor Status in systemd package in Ubuntu: New Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890913/+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 1869759] Re: [amdgpu] Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled
I meant amdgpu not mesa. -- 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/1869759 Title: [amdgpu] Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Textures are glitched (almost like they are cut up and repeated) when mipmapping or trilinear/bilinear filtering is enabled. Workaround is to disable both. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 12:03:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:134f] InstallationDate: Installed on 2019-11-04 (147 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-43 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=a44eb2b0-d036-44b7-9c90-d0a427ecd008 ro quiet splash resume=/dev/nvme0n1p5 resume_offset=15261696 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Grumpy_PK dmi.board.vendor: PK dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-43 dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 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+git20190815-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/linux/+bug/1869759/+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 1869759] Re: [amdgpu] Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled
I believe it is related to this mesa issue, though the type of corruption is different,(https://gitlab.freedesktop.org/mesa/mesa/-/issues/1399) because running with AMD_DEBUG=nodma resolves the corruption. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1399 https://gitlab.freedesktop.org/mesa/mesa/-/issues/1399 ** Attachment added: "Screenshot from 2020-08-08 13-49-25-2.png" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1869759/+attachment/5400024/+files/Screenshot%20from%202020-08-08%2013-49-25-2.png -- 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/1869759 Title: [amdgpu] Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Textures are glitched (almost like they are cut up and repeated) when mipmapping or trilinear/bilinear filtering is enabled. Workaround is to disable both. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 12:03:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:134f] InstallationDate: Installed on 2019-11-04 (147 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-43 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=a44eb2b0-d036-44b7-9c90-d0a427ecd008 ro quiet splash resume=/dev/nvme0n1p5 resume_offset=15261696 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Grumpy_PK dmi.board.vendor: PK dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-43 dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 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+git20190815-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/linux/+bug/1869759/+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 1890913] Re: init is using 100% of processor
Here is a screenshot of htop. ** Attachment added: "htop" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890913/+attachment/5400023/+files/%D9%86%D9%85%D8%A7%DA%AF%D8%B1%D9%81%D8%AA%20%D8%A7%D8%B2%202020-08-08%2022-17-22.png -- 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/1890913 Title: init is using 100% of processor Status in systemd package in Ubuntu: New Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890913/+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 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
@zack You could wait until the logrotate happen and restart rsyslog or you could simply do manual restart using 'systemctl restart rsyslog' and then look in /var/log/syslog. What triggers the error is at rsyslog startup from what I have notice during my test. - Eric -- 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/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Focal: Fix Committed Bug description: [Impact] At the moment rsyslog cannot have access /dev/console due to a mismatch permission/ownership between '/dev/console' and the Privilege Drop User and Group 'syslog' in rsyslog. [Test Case] * Deploy focal/20.04LTS (tested in gcloud instance) * Install rsyslog * systemctl restart rsyslog OR systemctl restart rsyslog * Inspect /var/log/syslog for the following error: syslog:Aug 4 14:37:56 rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] [Regression potential] https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/comments/4 [Other information] Other bug: https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 [Original description] The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following: syslog:Aug 3 15:16:58 rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2] [1] - Bionic/18.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root syslog 5, 1 Aug 3 15:17 /dev/console [2] - Focal/20.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root tty 5, 1 Aug 3 17:19 /dev/console # /etc/rsyslog.conf $PrivDropToUser syslog $PrivDropToGroup syslog ** As a debug exercise I did the following: - Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options. - Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group. Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]). Other bug: https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+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 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
@zack You could wait until the logrotate happen that will then restart rsyslog itself or you could simply do a manual restart using 'systemctl restart rsyslog' and then look in /var/log/syslog. What triggers the error is at rsyslog startup from what I have notice during my test. - Eric -- 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/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Focal: Fix Committed Bug description: [Impact] At the moment rsyslog cannot have access /dev/console due to a mismatch permission/ownership between '/dev/console' and the Privilege Drop User and Group 'syslog' in rsyslog. [Test Case] * Deploy focal/20.04LTS (tested in gcloud instance) * Install rsyslog * systemctl restart rsyslog OR systemctl restart rsyslog * Inspect /var/log/syslog for the following error: syslog:Aug 4 14:37:56 rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] [Regression potential] https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/comments/4 [Other information] Other bug: https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 [Original description] The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following: syslog:Aug 3 15:16:58 rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2] [1] - Bionic/18.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root syslog 5, 1 Aug 3 15:17 /dev/console [2] - Focal/20.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root tty 5, 1 Aug 3 17:19 /dev/console # /etc/rsyslog.conf $PrivDropToUser syslog $PrivDropToGroup syslog ** As a debug exercise I did the following: - Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options. - Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group. Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]). Other bug: https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+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 1890913] [NEW] init is using 100% of processor
Public bug reported: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy package-from-proposed third-party-packages -- 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/1890913 Title: init is using 100% of processor Status in systemd package in Ubuntu: New Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku:
[Touch-packages] [Bug 1890911] [NEW] package whoopsie 0.2.69ubuntu0.1 failed to install/upgrade: new whoopsie package pre-removal script subprocess returned error exit status 1
Public bug reported: trying to upgrade from 18.10 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: whoopsie 0.2.69ubuntu0.1 ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 8 12:01:52 2020 ErrorMessage: new whoopsie package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2016-08-07 (1462 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie Title: package whoopsie 0.2.69ubuntu0.1 failed to install/upgrade: new whoopsie package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-08-08 (0 days ago) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package autoreport-false focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1890911 Title: package whoopsie 0.2.69ubuntu0.1 failed to install/upgrade: new whoopsie package pre-removal script subprocess returned error exit status 1 Status in whoopsie package in Ubuntu: New Bug description: trying to upgrade from 18.10 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: whoopsie 0.2.69ubuntu0.1 ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 8 12:01:52 2020 ErrorMessage: new whoopsie package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2016-08-07 (1462 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie Title: package whoopsie 0.2.69ubuntu0.1 failed to install/upgrade: new whoopsie package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-08-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1890911/+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 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
For your reference: Bug #1890905 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in ibus: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change intentionally requires a change to apparmor to add a unix rule for communicating with the new ibus address. This is in xenial- proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to ensure that the apparmor abstraction is updated and policy recompiled before ibus is restarted. This was omitted from the initial im-config upload which resulted in bug #1588197. Test cases ensuring this is working properly are included above under 'Extended test case'. = SRU apparmor =
[Touch-packages] [Bug 1877238] Re: package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: попытка перезаписать общий «/usr/share/
*** This bug is a duplicate of bug 1881502 *** https://bugs.launchpad.net/bugs/1881502 ** This bug has been marked a duplicate of bug 1881502 package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from other instances of package libegl-mesa0:armhf -- 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/1877238 Title: package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: попытка перезаписать общий «/usr/share/glvnd/egl_vendor.d/50_mesa.json», который отличается от других экземпляров пакета libegl-mesa0:armhf Status in mesa package in Ubuntu: New Bug description: - ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] Uname: Linux 4.9.140-tegra aarch64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: arm64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 7 09:53:41 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: попытка перезаписать общий «/usr/share/glvnd/egl_vendor.d/50_mesa.json», который отличается от других экземпляров пакета libegl-mesa0:armhf GraphicsCard: ProcKernelCmdLine: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,2 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff78 core_edp_mv=1075 core_edp_ma=4000 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 quiet Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: mesa Title: package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: попытка перезаписать общий «/usr/share/glvnd/egl_vendor.d/50_mesa.json», который отличается от других экземпляров пакета libegl-mesa0:armhf UpgradeStatus: No upgrade log present (probably fresh install) version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1877238/+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 1881502] Re: package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to overwrite shared '/usr/share/
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1881502 Title: package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from other instances of package libegl-mesa0:armhf Status in mesa package in Ubuntu: Confirmed Bug description: Errors created when trying to install TeamViewer on Jetson Nano ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] Uname: Linux 4.9.140-tegra aarch64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: arm64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 31 14:35:15 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: trying to overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from other instances of package libegl-mesa0:armhf GraphicsCard: ProcKernelCmdLine: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,0 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff78 core_edp_mv=1125 core_edp_ma=4000 tegra_fbmem=0x14@0x92cb4000 is_hdmi_initialised=1 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 quiet Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: mesa Title: package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from other instances of package libegl-mesa0:armhf UpgradeStatus: No upgrade log present (probably fresh install) version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1881502/+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 1890903] [NEW] systemd-resolved.service still breaks (now 20.04, since as least 16)
Public bug reported: There are still occurrences of this service breaking down. At some moment the service just stops working correctly and is not able to recover. I can reset the service by restarting it: systemctl restart systemd-resolved.service I've also tried to set the caching off, but it still fails on me occasionally (on 18.04 as well). There is a local DNS in the network, I would like to directly use that in stead of: nameserver 127.0.0.53 Example: geus@desk-02:~$ ssh smb-01 ssh: Could not resolve hostname smb-01: Temporary failure in name resolution ... root@desk-02:/home/geus# systemctl restart systemd-resolved.service root@desk-02:/home/geus# nslookup smb-01 Server: 127.0.0.53 Address:127.0.0.53#53 Non-authoritative answer: Name: smb-01.lan Address: 192.168.178.39 ... geus@desk-02:~$ ssh smb-01 geus@smb-01's password: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat Aug 8 17:03:50 2020 InstallationDate: Installed on 2020-05-31 (69 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890903 Title: systemd-resolved.service still breaks (now 20.04, since as least 16) Status in systemd package in Ubuntu: New Bug description: There are still occurrences of this service breaking down. At some moment the service just stops working correctly and is not able to recover. I can reset the service by restarting it: systemctl restart systemd-resolved.service I've also tried to set the caching off, but it still fails on me occasionally (on 18.04 as well). There is a local DNS in the network, I would like to directly use that in stead of: nameserver 127.0.0.53 Example: geus@desk-02:~$ ssh smb-01 ssh: Could not resolve hostname smb-01: Temporary failure in name resolution ... root@desk-02:/home/geus# systemctl restart systemd-resolved.service root@desk-02:/home/geus# nslookup smb-01 Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: smb-01.lan Address: 192.168.178.39 ... geus@desk-02:~$ ssh smb-01 geus@smb-01's password: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat Aug 8 17:03:50 2020 InstallationDate: Installed on 2020-05-31 (69 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1
[Touch-packages] [Bug 1890892] [NEW] WSL openssh-server incorrect permissions .ssh
Public bug reported: Using Ubuntu Windows Subsystem for Linux (WSL) $ uname -srvmpio Linux 4.4.0-19041-Microsoft #1-Microsoft Fri Dec 06 14:06:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux (Prestep required to add port for access to windows firewall) .ssh directory was set as 777 when 755 (minimum) is required for operation of authentication keys when trying to ssh -i /path-to-key/key user@domain. Generally poor housekeeping. <3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.3 ProcVersionSignature: Microsoft 4.4.0-19041.1-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Aug 8 08:44:02 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 127: Error getting authority: Error initializing authority: Could not connect: No such file or directory SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1890892 Title: WSL openssh-server incorrect permissions .ssh Status in openssh package in Ubuntu: New Bug description: Using Ubuntu Windows Subsystem for Linux (WSL) $ uname -srvmpio Linux 4.4.0-19041-Microsoft #1-Microsoft Fri Dec 06 14:06:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux (Prestep required to add port for access to windows firewall) .ssh directory was set as 777 when 755 (minimum) is required for operation of authentication keys when trying to ssh -i /path-to-key/key user@domain. Generally poor housekeeping. <3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.3 ProcVersionSignature: Microsoft 4.4.0-19041.1-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Aug 8 08:44:02 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 127: Error getting authority: Error initializing authority: Could not connect: No such file or directory SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1890892/+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 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
http://h20195.www2.hp.com/v2/GetDocument.aspx?docname=4AA7-6280ENW this document by HP (note 11) acknowledge that mic is not functional due to missing snd-sof-pci driver -- 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/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Hi all, It works for me on Asus Vivobook after have applied firmware linux- firmware_1.183.2_all.deb on Ubuntu 20 on kernel 5.4.0-42-generic . Don't know how. dmesg | grep firmware [0.139854] Spectre V2 : Enabling Restricted Speculation for firmware calls [3.107460] iwlwifi :01:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2 [3.107485] iwlwifi :01:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2 [3.112097] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm [3.188788] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [3.193324] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [3.195221] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi [3.197148] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware monitor. [4.801750] Bluetooth: hci0: Waiting for firmware download to complete -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1890891] [NEW] dock
Public bug reported: when no one program is pinned and no one open dock stop working normally. When I open program it appear only 10 sec later as well for closing. restarting with alt + f2 is solving problem until all programs again unpinned and closed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 16:08:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=bfd431bb-2152-4fc0-98a1-a1e23b252397 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H V2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd12/02/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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 -- 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/1890891 Title: dock Status in xorg package in Ubuntu: New Bug description: when no one program is pinned and no one open dock stop working normally. When I open program it appear only 10 sec later as well for closing. restarting with alt + f2 is solving problem until all programs again unpinned and closed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 16:08:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=bfd431bb-2152-4fc0-98a1-a1e23b252397 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H V2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3
[Touch-packages] [Bug 1890836] Re: udev rule read but "RUN" command is not executed
Bug report to improve debugging output:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890890
--
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/1890836
Title:
udev rule read but "RUN" command is not executed
Status in systemd package in Ubuntu:
Invalid
Bug description:
The following was introduced as
"/etc/udev/rules.d/99-harvest_camera.rules":
ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D",
RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh"
When the device is attached, it gets mounted but the harvest_camera.sh
script does not execute. The udev_log=debug parameter is set in
/etc/udev/udev.conf. Verbosity was also maximized by running "udevadm
control --log-priority=debug". After running "udevadm monitor
--environment --udev", the drive was attached. The output shows a
device being created (/dev/sda1) and the UUID in the rule matches.
But the script simply never executes. The /var/log/syslog file shows:
"
Reading rules file: /etc/udev/rules.d/99-harvest_camera.rules
Successfully forked off 'n/a' as PID 2201.
1-2.3: Worker [2201] is forced for rocessing SEQNUM=7973.
"
So the logs make it look as though the script was executed. The
script is simply a stub that does a "touch /tmp/IhaveExecuted" and a
call to zenity to give a popup announcement. But none of that happens
(no popup and no new file in /tmp/). With maximum verbosity, there is
no way to further diagnose this. Deeper detail is needed that shows
which matching criteria in the rules is being tried and what the
result is.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836/+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 1890890] [NEW] more debugging verbosity for udev rules needed
Public bug reported: I wrote a udev rule that would not trigger when expected. I spent 2 days working on it, trying to understand what the problem was. I finally figured it out -- it was a matching problem: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836 The most verbose output possible is with the log level set to "debug". This level of logging does not show users what criteria is being checked and what the result is. So users are working in the dark. We have to guess what udev is doing. And we're bad at it, because if we could guess correctly we probably would have written the rule correctly in the first place. Consider procmail. This is an application where users write rules that contain matching criteria. When Procmail doesn't work as expected, the logs show in detail what criteria matches and what does not. This is what udev needs. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1890890 Title: more debugging verbosity for udev rules needed Status in systemd package in Ubuntu: New Bug description: I wrote a udev rule that would not trigger when expected. I spent 2 days working on it, trying to understand what the problem was. I finally figured it out -- it was a matching problem: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836 The most verbose output possible is with the log level set to "debug". This level of logging does not show users what criteria is being checked and what the result is. So users are working in the dark. We have to guess what udev is doing. And we're bad at it, because if we could guess correctly we probably would have written the rule correctly in the first place. Consider procmail. This is an application where users write rules that contain matching criteria. When Procmail doesn't work as expected, the logs show in detail what criteria matches and what does not. This is what udev needs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890890/+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 1890836] Re: udev rule read but "RUN" command is not executed
PEBKAC
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Bill Yikes (yik3s)
--
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/1890836
Title:
udev rule read but "RUN" command is not executed
Status in systemd package in Ubuntu:
Invalid
Bug description:
The following was introduced as
"/etc/udev/rules.d/99-harvest_camera.rules":
ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D",
RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh"
When the device is attached, it gets mounted but the harvest_camera.sh
script does not execute. The udev_log=debug parameter is set in
/etc/udev/udev.conf. Verbosity was also maximized by running "udevadm
control --log-priority=debug". After running "udevadm monitor
--environment --udev", the drive was attached. The output shows a
device being created (/dev/sda1) and the UUID in the rule matches.
But the script simply never executes. The /var/log/syslog file shows:
"
Reading rules file: /etc/udev/rules.d/99-harvest_camera.rules
Successfully forked off 'n/a' as PID 2201.
1-2.3: Worker [2201] is forced for rocessing SEQNUM=7973.
"
So the logs make it look as though the script was executed. The
script is simply a stub that does a "touch /tmp/IhaveExecuted" and a
call to zenity to give a popup announcement. But none of that happens
(no popup and no new file in /tmp/). With maximum verbosity, there is
no way to further diagnose this. Deeper detail is needed that shows
which matching criteria in the rules is being tried and what the
result is.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836/+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 1890836] Re: udev rule read but "RUN" command is not executed
It turns out the problem arises out of cargo cult programming on my
part. The bang in KERNEL=="sd*[!0-9]" is what I copied out of
stackexchange, and it's exactly what prevents the mount from matching.
I suspected that early on, but ruled it out because when the device
first connects it must connect as /dev/sda (as the partition table must
be read before there can be an sda1). Now I'm figuring the sda gets
replaced with sda1 before it reaches my custom rule.
In any case, the bug is not as I reported. I'm sorry this turned out to
be a non-bug and I'm sorry I wasted your time Mr. Streetman. This can
be closed.
I may open a new bug report to improve the debug output, because we
shouldn't have to work in the dark and guess about what the matching
criteria is doing.
--
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/1890836
Title:
udev rule read but "RUN" command is not executed
Status in systemd package in Ubuntu:
Invalid
Bug description:
The following was introduced as
"/etc/udev/rules.d/99-harvest_camera.rules":
ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D",
RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh"
When the device is attached, it gets mounted but the harvest_camera.sh
script does not execute. The udev_log=debug parameter is set in
/etc/udev/udev.conf. Verbosity was also maximized by running "udevadm
control --log-priority=debug". After running "udevadm monitor
--environment --udev", the drive was attached. The output shows a
device being created (/dev/sda1) and the UUID in the rule matches.
But the script simply never executes. The /var/log/syslog file shows:
"
Reading rules file: /etc/udev/rules.d/99-harvest_camera.rules
Successfully forked off 'n/a' as PID 2201.
1-2.3: Worker [2201] is forced for rocessing SEQNUM=7973.
"
So the logs make it look as though the script was executed. The
script is simply a stub that does a "touch /tmp/IhaveExecuted" and a
call to zenity to give a popup announcement. But none of that happens
(no popup and no new file in /tmp/). With maximum verbosity, there is
no way to further diagnose this. Deeper detail is needed that shows
which matching criteria in the rules is being tried and what the
result is.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836/+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 1890041] Re: Apport does not work without Chrome
Sorry, I misunderstood. arcturus ~ > grep chromium ~/.local/share/applications/* /home/ralph/.local/share/applications/chromium-browser-2.desktop:Exec=chromium-browser --incognito /home/ralph/.local/share/applications/chromium-browser-2.desktop:Exec=chromium-browser /home/ralph/.local/share/applications/chromium-browser-2.desktop:Exec=chromium-browser --temp-profile /home/ralph/.local/share/applications/chromium-browser-2.desktop:Icon=chromium-browser /home/ralph/.local/share/applications/chromium-browser-2.desktop:X-AppInstall-Package=chromium-browser /home/ralph/.local/share/applications/Chromium.desktop:Exec=/snap/chromium/current/bin/chromium.launcher /home/ralph/.local/share/applications/Chromium.desktop:Icon=chromium-browser -- 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/1890041 Title: Apport does not work without Chrome Status in apport package in Ubuntu: Incomplete Bug description: I cannot recall Apport ever working for me, but this time it fails because I don't have chromium installed on my machine. I use Firefox instead. Besides, on the second screen, "I don't know" should realy be called "My bug is not listed". Error message: arcturus ~ > apport-bug 1276 /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) non-network local connections being added to access control list sudo: chromium-browser: command not found Further information: Kubuntu 20.04.1 LTS apport: Installed: 2.20.11-0ubuntu27.4 Candidate: 2.20.11-0ubuntu27.4 Version table: *** 2.20.11-0ubuntu27.4 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890041/+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 1888120] Re: Headphones detected like Speakers and Volume Problem
In Windows and in some games, you have got the option to select the sound output. For example, you can select headphones (auriculares in spanish) and the sound is lower to not damage your ears. The other option is to select speakers (altavoces in spanish), and in that case the sound is higher. I don't know if Ubuntu has got the same option in the kernel or if in Linux, maybe in Linux speakers and headphones are the same, and the output volume you obtain it's equal and indifferent. If it is, you can close the bug. Thank you. -- 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/1888120 Title: Headphones detected like Speakers and Volume Problem Status in pulseaudio package in Ubuntu: Incomplete Bug description: I bought a Kyus Headphones, this model exactly: https://www.pccomponentes.com/krom-kyus-auriculares-gaming and when I go to Settings/Sound in Ubuntu 20.04 LTS, I can watch Speakers - USB Audio Device, not Headphones. In Windows if the system detect the headphones like speakers, the sound is louder and upset, I think that Ubuntu should have a similar problem. Another problem is the control volume. When I change the volume using a key combination to up volume and down volume. If I up the volume when I have got 0 level, the volume doesn't ear in the two first steps that I pulsed UP volume. Other problem is, that if I press up volume it change a lot with only one press of up volume. This generate the situation of volume too low and when press up, the volume is too high. Thanks for your time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888120/+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 1890869] Re: [Clevo N350TW with Intel Corporation Cannon Lake PCH cAVS] no sound from speakers and headphones
** Attachment added: "alsamixer.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1890869/+attachment/5399761/+files/alsamixer.png -- 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/1890869 Title: [Clevo N350TW with Intel Corporation Cannon Lake PCH cAVS] no sound from speakers and headphones Status in alsa-driver package in Ubuntu: New Bug description: First I must say you, my English is not very good. I'm from Germany and I learned English in school, but this was in 1986. * My notebook: Product Name: SCHENKER_DOCK_15_SDO15L18_SDO15E19; Board Name: Clevo N350TW; Dual-boot: "Linux Mint 20 Ulyana (based on Ubuntu 20.04)" and "Windows 10 1909"; Architecture: x86_64; Kernel release: 5.4.0-40; Audio device: Intel Corporation Cannon Lake PCH cAVS [8086:a348] (rev 10); Subsystem: CLEVO/KAPOK Computer Cannon Lake PCH cAVS [1558:0351]; * Here is the problem: When I boot Linux, the notebook have no sound from speakers and headphones. When I click the speaker-icon in tray, I can only see "Dummy-Output". Sometimes I hear a crack from the speakers. Only when I connect the notebook and the TV with a HDMI-cable, I have sound on TV. When I now click the speaker-icon, I see "HDMI-3". This problem was also with the Live-CD and also with "Linux Mint 19.3 Tricia (based on Ubuntu 18.04)". If I boot "Windows", there are no problems with sound. * Here the ALSA-info file: http://alsa-project.org/db/?f=47ee648ea6d6f98dcd1284b5d9800aa6b7240e33 * Can someone please help me to solve this problem? My Linux skills are average (learning by doing). Thanks in advance for your assistance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1890869/+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 1890869] Re: [Clevo N350TW with Intel Corporation Cannon Lake PCH cAVS] no sound from speakers and headphones
** Attachment added: "pactl list sinks" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1890869/+attachment/5399760/+files/pactl%20list%20sinks -- 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/1890869 Title: [Clevo N350TW with Intel Corporation Cannon Lake PCH cAVS] no sound from speakers and headphones Status in alsa-driver package in Ubuntu: New Bug description: First I must say you, my English is not very good. I'm from Germany and I learned English in school, but this was in 1986. * My notebook: Product Name: SCHENKER_DOCK_15_SDO15L18_SDO15E19; Board Name: Clevo N350TW; Dual-boot: "Linux Mint 20 Ulyana (based on Ubuntu 20.04)" and "Windows 10 1909"; Architecture: x86_64; Kernel release: 5.4.0-40; Audio device: Intel Corporation Cannon Lake PCH cAVS [8086:a348] (rev 10); Subsystem: CLEVO/KAPOK Computer Cannon Lake PCH cAVS [1558:0351]; * Here is the problem: When I boot Linux, the notebook have no sound from speakers and headphones. When I click the speaker-icon in tray, I can only see "Dummy-Output". Sometimes I hear a crack from the speakers. Only when I connect the notebook and the TV with a HDMI-cable, I have sound on TV. When I now click the speaker-icon, I see "HDMI-3". This problem was also with the Live-CD and also with "Linux Mint 19.3 Tricia (based on Ubuntu 18.04)". If I boot "Windows", there are no problems with sound. * Here the ALSA-info file: http://alsa-project.org/db/?f=47ee648ea6d6f98dcd1284b5d9800aa6b7240e33 * Can someone please help me to solve this problem? My Linux skills are average (learning by doing). Thanks in advance for your assistance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1890869/+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 1890869] [NEW] [Clevo N350TW with Intel Corporation Cannon Lake PCH cAVS] no sound from speakers and headphones
Public bug reported: First I must say you, my English is not very good. I'm from Germany and I learned English in school, but this was in 1986. * My notebook: Product Name: SCHENKER_DOCK_15_SDO15L18_SDO15E19; Board Name: Clevo N350TW; Dual-boot: "Linux Mint 20 Ulyana (based on Ubuntu 20.04)" and "Windows 10 1909"; Architecture: x86_64; Kernel release: 5.4.0-40; Audio device: Intel Corporation Cannon Lake PCH cAVS [8086:a348] (rev 10); Subsystem: CLEVO/KAPOK Computer Cannon Lake PCH cAVS [1558:0351]; * Here is the problem: When I boot Linux, the notebook have no sound from speakers and headphones. When I click the speaker-icon in tray, I can only see "Dummy-Output". Sometimes I hear a crack from the speakers. Only when I connect the notebook and the TV with a HDMI-cable, I have sound on TV. When I now click the speaker-icon, I see "HDMI-3". This problem was also with the Live-CD and also with "Linux Mint 19.3 Tricia (based on Ubuntu 18.04)". If I boot "Windows", there are no problems with sound. * Here the ALSA-info file: http://alsa-project.org/db/?f=47ee648ea6d6f98dcd1284b5d9800aa6b7240e33 * Can someone please help me to solve this problem? My Linux skills are average (learning by doing). Thanks in advance for your assistance! ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: clevo n350tw ** Attachment added: "alsa-info-txt" https://bugs.launchpad.net/bugs/1890869/+attachment/5399759/+files/alsa-info-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/1890869 Title: [Clevo N350TW with Intel Corporation Cannon Lake PCH cAVS] no sound from speakers and headphones Status in alsa-driver package in Ubuntu: New Bug description: First I must say you, my English is not very good. I'm from Germany and I learned English in school, but this was in 1986. * My notebook: Product Name: SCHENKER_DOCK_15_SDO15L18_SDO15E19; Board Name: Clevo N350TW; Dual-boot: "Linux Mint 20 Ulyana (based on Ubuntu 20.04)" and "Windows 10 1909"; Architecture: x86_64; Kernel release: 5.4.0-40; Audio device: Intel Corporation Cannon Lake PCH cAVS [8086:a348] (rev 10); Subsystem: CLEVO/KAPOK Computer Cannon Lake PCH cAVS [1558:0351]; * Here is the problem: When I boot Linux, the notebook have no sound from speakers and headphones. When I click the speaker-icon in tray, I can only see "Dummy-Output". Sometimes I hear a crack from the speakers. Only when I connect the notebook and the TV with a HDMI-cable, I have sound on TV. When I now click the speaker-icon, I see "HDMI-3". This problem was also with the Live-CD and also with "Linux Mint 19.3 Tricia (based on Ubuntu 18.04)". If I boot "Windows", there are no problems with sound. * Here the ALSA-info file: http://alsa-project.org/db/?f=47ee648ea6d6f98dcd1284b5d9800aa6b7240e33 * Can someone please help me to solve this problem? My Linux skills are average (learning by doing). Thanks in advance for your assistance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1890869/+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
