[Touch-packages] [Bug 1900057] Re: ThinkPad T400 sleeps immediately after login
Does the same problem happen if you select 'Ubuntu on Wayland' from the login screen? ** Summary changed: - booting interrupted + ThinkPad T400 sleeps immediately after login ** Package changed: xorg (Ubuntu) => gnome-shell (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/1900057 Title: ThinkPad T400 sleeps immediately after login Status in gnome-shell package in Ubuntu: New Bug description: After pressing power button (and after upgrade to focal), PC starts up normally. After I enter authentication, though, it shuts down, apparently into sleep mode/suspend/hibernate. Pressing powerbutton again brings up normal desktop and normal use right away. Possibly this is a bug against kernel or gdm3. Ubuntu 20.04.1 LTS xorg: Geïnstalleerd: 1:7.7+19ubuntu14 Kandidaat: 1:7.7+19ubuntu14 Versietabel: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status gdm3: Geïnstalleerd: 3.36.3-0ubuntu0.20.04.1 Kandidaat: 3.36.3-0ubuntu0.20.04.1 Versietabel: *** 3.36.3-0ubuntu0.20.04.1 500 500 http://nl.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 00:10:04 2020 DistUpgraded: 2020-10-12 20:07:01,643 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (Bestand of map bestaat niet) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-11-30 (320 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic root=UUID=21af2411-3a11-46c1-9554-cb8ffbfdbd89 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-10-12 (3 days ago) dmi.bios.date: 04/22/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET66WW (2.16 ) dmi.board.name: 6474B84 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET66WW(2.16):bd04/22/2009:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900057/+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 1899953] Re: Crackling audio on Raspberry Pi Desktop
Dave, can you please report the issue to the developers: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues and then tell us the issue ID? -- 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/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: New Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899953/+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 1899971] Re: Problematic dependency on python3-apport causes all Python invocations to install apport hook
** Tags added: focal -- 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/1899971 Title: Problematic dependency on python3-apport causes all Python invocations to install apport hook Status in xorg package in Ubuntu: New Bug description: This would be no big deal if python3-apport just sat there until it was used (which it would never be on my system, since I removed apport). However, whenever python3-apport is installed, it unconditionally sets itself as sys.excepthook in Python3. The decision to have xserver-xorg depend on python3-apport basically means that every user who runs an X server will get this exception hook in Python whether they want it or not. And having python3-apport as the Python exception hook is not exactly harmless; it can still cause issues. My relatively minor but annoying issue is that I see deprecation warnings every time I get an error traceback, because python3-apport uses some deprecated code. I can imagine worse issues should there be an error in python3-apport; it could cause massive headaches and confusion for users who have no idea what's causing it. I'm not sure there is any point to have this dependency in the xserver-xorg package; it doesn't seem like those scripts will ever be run unless apport is installed and detects a crash, and apport already depends on python3-apport. I made a nice equivs package to allow myself to uninstall it, and as far as I can tell X and its applications still run fine. This is for Fossa, package version 1:7.7+19ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1899971/+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 1899962] Re: Wrong audio output device selected on Raspberry Pi Desktop
** Tags added: groovy raspi -- 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/1899962 Title: Wrong audio output device selected on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: New Bug description: On each boot, an incorrect audio output device is selected, at least when HDMI audio output is in use (still need to test the TV/aux output; will update the bug when done). Specifically, the settings application lists "Multichannel Output - Built-in Audio" as the selected output device. However, for audio to play through the connected HDMI device, "Analog Output - Built-in Audio" must be selected instead. Unfortunately, this setting will be lost on subsequent boots. A workaround is to remove the following lines from /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif However, removal of these lines will (as the comment suggests) result in hot-plugged USB devices *not* being automatically selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899962/+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 1899953] Re: Crackling audio on Raspberry Pi Desktop
I will assume this is groovy. ** Tags added: groovy ** Tags added: raspi -- 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/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: New Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899953/+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 1164317] Re: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
This bug is closed and has been for a few years. Please open a new bug by running: ubuntu-bug pulseaudio -- 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/1164317 Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all Status in pulseaudio package in Ubuntu: Expired Bug description: no audio coming out while using any of the players (both audio and video - rhythm box, banshee, movie player) in use in ubuntu ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghavan 1862 F pulseaudio /dev/snd/pcmC0D1p: raghavan 1862 F...m pulseaudio Date: Thu Apr 4 12:03:53 2013 InstallationDate: Installed on 2013-01-15 (78 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghavan 1862 F pulseaudio /dev/snd/pcmC0D1p: raghavan 1862 F...m pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5G41T-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1164317/+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 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
Removed NVIDIA card, re-ran full install with no problems. Reinstalled card, then installed NVIDIA/CUDA from ubuntu repos and all is fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails when "Install Third-Party Drivers" is selected Status in GLibC: New Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: In Progress Status in glibc package in Ubuntu: Invalid Status in apt source package in Bionic: Triaged Status in glibc source package in Bionic: Invalid Status in apt source package in Focal: Triaged Status in glibc source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+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.
Same issue, running ubuntu 20.04.1 with 5.4.0-51-generic kernel. I have an ASUS Zephyrus M GU502GW-AH76 -- 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 1900068] [NEW] Upgrade to zeitgeist-1.0.3
Public bug reported: Please do upgrade zeitgeist from current 1.0.2 to 1.0.3. It is required for GNOME Activity Journal to work. GNOME Activity Journal has been ported to GTK3. It will be available in GNOME repos shortly. For more details: https://discourse.gnome.org/t/zeitgeist-gnome-activity-journal-1-0/4521 ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Attachment added: "GNOME Activity Journal - new version based on zeitgeist 1.0.3" https://bugs.launchpad.net/bugs/1900068/+attachment/5422747/+files/multi-view-new.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1900068 Title: Upgrade to zeitgeist-1.0.3 Status in zeitgeist package in Ubuntu: New Bug description: Please do upgrade zeitgeist from current 1.0.2 to 1.0.3. It is required for GNOME Activity Journal to work. GNOME Activity Journal has been ported to GTK3. It will be available in GNOME repos shortly. For more details: https://discourse.gnome.org/t/zeitgeist-gnome-activity- journal-1-0/4521 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1900068/+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 1900068] Re: Upgrade to zeitgeist-1.0.3
** Attachment added: "GNOME Activity Journal - GTK3 version based on zeitgeist 1.0.3" https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1900068/+attachment/5422748/+files/about-new.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1900068 Title: Upgrade to zeitgeist-1.0.3 Status in zeitgeist package in Ubuntu: New Bug description: Please do upgrade zeitgeist from current 1.0.2 to 1.0.3. It is required for GNOME Activity Journal to work. GNOME Activity Journal has been ported to GTK3. It will be available in GNOME repos shortly. For more details: https://discourse.gnome.org/t/zeitgeist-gnome-activity- journal-1-0/4521 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1900068/+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 1900057] [NEW] booting interrupted
Public bug reported: After pressing power button (and after upgrade to focal), PC starts up normally. After I enter authentication, though, it shuts down, apparently into sleep mode/suspend/hibernate. Pressing powerbutton again brings up normal desktop and normal use right away. Possibly this is a bug against kernel or gdm3. Ubuntu 20.04.1 LTS xorg: Geïnstalleerd: 1:7.7+19ubuntu14 Kandidaat: 1:7.7+19ubuntu14 Versietabel: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status gdm3: Geïnstalleerd: 3.36.3-0ubuntu0.20.04.1 Kandidaat: 3.36.3-0ubuntu0.20.04.1 Versietabel: *** 3.36.3-0ubuntu0.20.04.1 500 500 http://nl.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 00:10:04 2020 DistUpgraded: 2020-10-12 20:07:01,643 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (Bestand of map bestaat niet) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-11-30 (320 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic root=UUID=21af2411-3a11-46c1-9554-cb8ffbfdbd89 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-10-12 (3 days ago) dmi.bios.date: 04/22/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET66WW (2.16 ) dmi.board.name: 6474B84 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET66WW(2.16):bd04/22/2009:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- 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/1900057 Title: booting interrupted Status in xorg package in Ubuntu: New Bug description: After pressing power button (and after upgrade to focal), PC starts up normally. After I enter authentication, though, it shuts down, apparently into sleep mode/suspend/hibernate. Pressing powerbutton again brings up normal desktop and normal use right away. Possibly this is a bug against kernel or gdm3. Ubuntu 20.04.1 LTS xorg: Geïnstalleerd: 1:7.7+19ubuntu14 Kandidaat: 1:7.7+19ubuntu14 Versietabel: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status gdm3: Geïnstalleerd: 3.36.3-0ubuntu0.20.04.1 Kandidaat: 3.36.3-0ubuntu0.20.04.1 Versietabel: *** 3.36.3-0ubuntu0.20.04.1 500 500 http://nl.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main
[Touch-packages] [Bug 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''
Hello Hui, or anyone else affected, Accepted alsa-lib into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.2.3.2-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: alsa-lib (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: Fix Committed Bug description: [Impact] Recently the ucm added some amixer settings, like this one: cset "name='rt711 ADC 23 Mux' 'MIC2'" This setting is needed for Dell soundwire audio machines, and only this setting is set correctly, the headset-mic could work. And we already backported this ucm to focal. But the alsa-lib ctl parse doesn't support the enum value in the '' yet, so this amixer setting can't be set correctly under current focal and groovy, we need to backport a patch from alsa-lib master branch. [Fix] Backport a patch from upstream, this patch is not in the groovy yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this patch. [Test Case] On the Dell soundwire audio machine, run alsactl init, then check if the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set correctly, it means the alsalib enum ctl parse support both "" and '' now. [Regression Risk] This could introduce failure on setting enum amixer settings, users will experience the failure of audio device like the speaker can't output sound, the mic can't record sound. But this possibility is very low since we have tested this SRU on many LENOVO and Dell machines (with and without soundwire audio), all worked as fine as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+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 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers
FIX IS to add these lines to /etc/modprobe.d/alsa-config.conf options snd-hda-intel model=clevo-p950 options snd-hda-intel probe_mask=0x1 the cause appears to be NVIDIA drivers I am using the same ones https://pov.es/linux/ubuntu-ubuntu-20-4-installing-nvidia-drivers- breaks-built-in-audio-on-laptop/?print=print mesaboogie in the mintlinux official IRC chat found this technical writeup... The problem did appear to happen after I changed to NVIDIA from the default... why NVIDIA breaks sound i have no idea lol -- 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/1898603 Title: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound output is detected as "headphones" instead of Speakers when this laptop doesn't even have any headphones connected at all... reverting to a prior kernel fixes the problem and then the output is correctly Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and the Mint Linux support chat said I should file a bug for this because this kernel broke something. See attached detailed log reports for more info... Thanks team!!! Best Regards, -Avery Tarasov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chr0meice2 2656 F pulseaudio /dev/snd/controlC0: chr0meice2 2656 F pulseaudio /dev/snd/pcmC0D0c: chr0meice2 2656 F...m pulseaudio /dev/snd/pcmC0D0p: chr0meice2 2656 F...m pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-10-05 (0 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 NonfreeKernelModules: nvidia_modeset nvidia Package: alsa-driver (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: ulyana Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898603/+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 1899797] Re: dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121
as you indicated this is tied to your kernel version, i'm marking systemd as invalid. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1899797 Title: dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: This morning i've got a kernel update. After that I could not send mails using thunderbird contacting my mail provider kontent.com. The last working system was: Linux server 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I tried 4.15.0-118 and 4.15.0-121 but using these I could not resolve: smtp.kontent.com - but I could resolve www.google.de. So it seems that using the newer kernels 118 and 121 I can not resolve some but not all addresses. I returned to kernel 4.15.0-117 and everything works fine again. systemd-resolve --status Global DNS Servers: 172.30.30.1<--- this is an local router next to my "server" DNS Domain: ami.intranet DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp0s25) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.30.30.1 DNS Domain: ~. ami.intranet andreas@server:~$ host smtp.kontent.com smtp.kontent.com has address 81.88.40.61 doning the same with a newer kernel results in a "SERVERFAIL 2 error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899797/+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 1898878] Re: Ubuntu slow boot
*** This bug is a duplicate of bug 1898869 *** https://bugs.launchpad.net/bugs/1898869 ** This bug has been marked a duplicate of bug 1898869 System slow on booting -- 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/1898878 Title: Ubuntu slow boot Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: My PC takes about 2 minutes till Desktop, it's just slow. I am attaching logs in hope of seeing if there is a bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-lowlatency 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 Uname: Linux 5.4.0-48-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lyubo 2186 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 7 17:00:19 2020 InstallationDate: Installed on 2020-02-08 (242 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 1bbb:0195 T & A Mobile Phones Mobilebroadband Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality init=/lib/systemd/systemd-bootchart vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-20 (169 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898878/+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 1899146] Re: systemd-resolve has no --verbose or --debug flag
** Also affects: systemd via https://github.com/systemd/systemd/issues/17330 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1899146 Title: systemd-resolve has no --verbose or --debug flag Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: I understand that systemd-resolve is the tool to test queries through systemd-resolved. When investigation resolution issues (if it resolves fine with dig @server domain.to.test but not with systemd-resolved), you can use systemd-resolve --status to view the active configuration with the link related parameters, OR use systemd-resolve domain.to.test to test the resolution (but you have no details, just either a result, or a simple "not found"). It would really help a lot to have either a --verbose or a --debug flag, to see which server is queried, why, which domains are actually sent in the query (based on the search domains), was the cache used (something like the dig output would already be better). Thanks! Ubuntu version: Ubuntu 18.04.5 LTS Systemd version: 237-3ubuntu10.42 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1899146/+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 1898421] Re: Suspend - takes 30 seconds to fully suspend
This isn't a problem with systemd, it looks like this is a problem either with your kernel drivers and/or actual hardware, e.g.: [ 1135.331004] amdgpu :02:00.0: refused to change power state from D0 to D3hot [ 1135.331007] xhci_hcd :02:00.4: refused to change power state from D0 to D3hot ** Package changed: systemd (Ubuntu) => linux (Ubuntu) -- 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/1898421 Title: Suspend - takes 30 seconds to fully suspend Status in linux package in Ubuntu: New Bug description: Using `systemctl suspend` or suspending through the power menu takes 30 seconds for the system to fully suspend. Expected: The system suspends in under 2 seconds (e.g. check Arch Linux) Actual: The system takes 30 seconds to suspend (31.44 seconds using a stopwatch) Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal DMESG: [ 8521.093270] PM: suspend entry (deep) [ 8521.104938] Filesystems sync: 0.011 seconds [ 8521.182123] Freezing user space processes ... (elapsed 0.004 seconds) done. [ 8521.187004] OOM killer disabled. [ 8521.187005] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 8521.188754] printk: Suspending console(s) (use no_console_suspend to debug) [ 8521.219072] sd 1:0:0:0: [sda] Synchronizing SCSI cache [ 8521.219621] sd 1:0:0:0: [sda] Stopping disk [ 8521.958776] ACPI: Preparing to enter system sleep state S3 [ 8521.960793] PM: Saving platform NVS memory [ 8521.961025] Disabling non-boot CPUs ... [ 8521.961558] IRQ 26: no longer affine to CPU1 [ 8521.962593] smpboot: CPU 1 is now offline [ 8521.964649] IRQ 18: no longer affine to CPU2 [ 8521.965669] smpboot: CPU 2 is now offline [ 8521.967970] IRQ 27: no longer affine to CPU3 [ 8521.968991] smpboot: CPU 3 is now offline [ 8521.970958] ACPI: Low-level resume complete [ 8521.970958] PM: Restoring platform NVS memory [ 8521.976827] Enabling non-boot CPUs ... [ 8521.976893] x86: Booting SMP configuration: [ 8521.976894] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 8521.983510] CPU1 is up [ 8521.983545] smpboot: Booting Node 0 Processor 2 APIC 0x3 [ 8521.990199] CPU2 is up [ 8521.990234] smpboot: Booting Node 0 Processor 3 APIC 0x1 [ 8521.996937] CPU3 is up [ 8521.999566] ACPI: Waking up from system sleep state S3 [ 8522.039068] usb usb3: root hub lost power or was reset [ 8522.039085] usb usb4: root hub lost power or was reset [ 8522.039093] usb usb5: root hub lost power or was reset [ 8522.039149] usb usb6: root hub lost power or was reset [ 8522.039172] usb usb7: root hub lost power or was reset [ 8522.039207] usb usb8: root hub lost power or was reset [ 8522.046933] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 8522.053105] [drm] PCIE GART of 1024M enabled (table at 0x00162000). [ 8522.053201] radeon :01:00.0: WB enabled [ 8522.053204] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x2d5e699f [ 8522.053207] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x6b3686a1 [ 8522.053999] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0x556b4497 [ 8522.054407] sd 1:0:0:0: [sda] Starting disk [ 8522.070310] [drm] ring test on 0 succeeded in 2 usecs [ 8522.070320] [drm] ring test on 3 succeeded in 6 usecs [ 8522.139382] mt7601u 1-5:1.0: Error: MCU response pre-completed! [ 8522.167009] mt7601u 1-5:1.0: EEPROM ver:0c fae:00 [ 8522.246061] [drm] ring test on 5 succeeded in 2 usecs [ 8522.246069] [drm] UVD initialized successfully. [ 8522.246206] [drm] ib test on ring 0 succeeded in 0 usecs [ 8522.246333] [drm] ib test on ring 3 succeeded in 0 usecs [ 8522.372750] ata1: SATA link down (SStatus 0 SControl 300) [ 8522.420793] ata4: SATA link down (SStatus 0 SControl 300) [ 8522.420965] ata5: SATA link down (SStatus 0 SControl 300) [ 8522.420984] ata6: SATA link down (SStatus 0 SControl 300) [ 8522.421015] ata3: SATA link down (SStatus 0 SControl 300) [ 8522.534422] usb 4-2: reset low-speed USB device number 3 using uhci_hcd [ 8522.586417] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8522.589674] ata2.00: configured for UDMA/133 [ 8522.589762] ata2.00: Enabling discard_zeroes_data [ 8522.910492] [drm] ib test on ring 5 succeeded [ 8523.114411] usb 4-1: reset low-speed USB device number 2 using uhci_hcd [ 8523.467722] OOM killer enabled. [ 8523.467723] Restarting tasks ... [ 8523.469565] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469623] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469671] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469723] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469769] pci
[Touch-packages] [Bug 1164317] Re: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
Just upgraded fro 18.04 to 20.04.1 LTS. After upgrade, no sound. In settings no choice for my sound card. -- 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/1164317 Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all Status in pulseaudio package in Ubuntu: Expired Bug description: no audio coming out while using any of the players (both audio and video - rhythm box, banshee, movie player) in use in ubuntu ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghavan 1862 F pulseaudio /dev/snd/pcmC0D1p: raghavan 1862 F...m pulseaudio Date: Thu Apr 4 12:03:53 2013 InstallationDate: Installed on 2013-01-15 (78 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghavan 1862 F pulseaudio /dev/snd/pcmC0D1p: raghavan 1862 F...m pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5G41T-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1164317/+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 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers
Hi Daniel, someone in mint linux support chat, mesaboogie, firmly believes this can be fixed by adding "snd-hda-intel options model=" to the correct value in my /etc/modprobe.d/alsa-config.conf we tried setting to p950-clevo and rebooting but no luck. any other ideas? Any idea why my sound works perfectly in the live CD every single time, yet in the same exact version of the that same kernel the sound is broken now? I have not done anything unusual with my system install -- 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/1898603 Title: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound output is detected as "headphones" instead of Speakers when this laptop doesn't even have any headphones connected at all... reverting to a prior kernel fixes the problem and then the output is correctly Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and the Mint Linux support chat said I should file a bug for this because this kernel broke something. See attached detailed log reports for more info... Thanks team!!! Best Regards, -Avery Tarasov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chr0meice2 2656 F pulseaudio /dev/snd/controlC0: chr0meice2 2656 F pulseaudio /dev/snd/pcmC0D0c: chr0meice2 2656 F...m pulseaudio /dev/snd/pcmC0D0p: chr0meice2 2656 F...m pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-10-05 (0 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 NonfreeKernelModules: nvidia_modeset nvidia Package: alsa-driver (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: ulyana Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898603/+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 1898447] Re: HDMI sound output disappears after sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1898447 Title: HDMI sound output disappears after sleep Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am using an Nvidia graphics card with HDMI output. The sound output choice for HDMI is missing from either pavucontrol or the GNOME settings sound settings after waking the computer up from sleep. Running `pacmd list-cards` does show the HDMI sound output listed. I can bring the output back as a choice if I run `pulseaudio -k`, but I will lose the choice to select this output if I put the computer to sleep, leaving me only with the S/PDIF output from my motherboard. I didnt see this issue prior to what I suspect was an `apt upgrade`. Description: Ubuntu 20.04.1 LTS Release: 20.04 Kernel: 5.4.0-48-generic Desktop Environment: GNOME 3.36.3 pulseaudio: Installed: 1:13.99.1-1ubuntu3.6 Candidate: 1:13.99.1-1ubuntu3.6 Version table: *** 1:13.99.1-1ubuntu3.6 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages Hardware Info: CPU: AMD Ryzen 9 3950x GPU: Nvidia RTX 2080ti (Driver 450.66 ) Motherboard: Gigabyte X570 AORUS MASTER --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: umayr 4915 F pulseaudio /dev/snd/pcmC0D3p: umayr 4915 F...m pulseaudio /dev/snd/controlC1: umayr 4915 F pulseaudio /dev/snd/controlC2: umayr 4915 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-12 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER 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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898447/+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 1898729] Re: shim can end up being removed
** Also affects: apt (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Focal) Importance: Undecided Status: New ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1898729 Title: shim can end up being removed Status in apt package in Ubuntu: New Status in shim package in Ubuntu: New Status in apt source package in Focal: New Status in shim source package in Focal: New Status in apt source package in Groovy: New Status in shim source package in Groovy: New Bug description: I just did a set of package updates in focal that ended up with shim shim-signed mokutil being autoremoved. I rebooted without noticing, and had to manually recover the system thereafter. :( Julian says there was a period of time where these were marked auto. I suppose that I installed during this window, and now some dependency change meant that as far as apt was concerned they weren't required any more. Can we please consider never proposing these packages for autoremoval? apt has NeverAutoRemove for this which could be used, or some other appropriate method. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel ModemManager[1308]: Caught signal, shutting down... Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: Unexpected error
[Touch-packages] [Bug 882878] Re: With IPv6 disabled, openssh will not forward X connections
Still broken in bionic in 2020! -- 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/882878 Title: With IPv6 disabled, openssh will not forward X connections Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Status in openssh package in openSUSE: Fix Released Bug description: If you disable IPv6 in /etc/sysctl.conf sshd will not forward X11. It logs the failue in /var/log/auth.log Oct 27 18:49:26 uscps002 sshd[14722]: Accepted password for root from 172.20.10.50 port 60322 ssh2 Oct 27 18:49:26 uscps002 sshd[14722]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 27 18:49:27 uscps002 sshd[14722]: error: Failed to allocate internet-domain X11 display socket. Aparently the compiled sshd version will not try an ipv4 localhost if an ipv6 localhost does not exist. Placing the following line in /etc/ssh/sshd_config fixes the issue X11UseLocalHost no root@uscps002:/var/log# lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 root@uscps002:/var/log# root@uscps002:/var/log# uname -a Linux uscps002 3.0.0-12-server #20-Ubuntu SMP Fri Oct 7 16:36:30 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/882878/+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 1899745] Re: [SRU] alsa-utils: let alsactl support _boot section defined in ucm
** Changed in: alsa-utils (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1899745 Title: [SRU] alsa-utils: let alsactl support _boot section defined in ucm Status in HWE Next: New Status in alsa-utils package in Ubuntu: Fix Released Status in alsa-utils source package in Focal: In Progress Bug description: This patchset was backported from mainline alsa-utils 1.2.3, and groovy already integrated alsa-utils 1.2.3, there is no need to SRU this patchset to groovy, so only for focal. [Impact] We enabled 2 Dell soundwire audio machines, these machines depend on ucm to make the audio work, and in the ucm, the _boot section defined some amixers values for the 1st booting, these amixer values should be set to audio driver at the 1st booting, otherwise the whole audio doesn't work. [Fix] Backport some patches from mainline v1.2.3, these patches make the alsactl support _boot section in the ucm, then the systemd will call alsactl init after booting, the alsactl init will setting all amixers defined in the _boot section of ucm. [Test Case] On the Dell soundwire audio machines, After booting up, run 'amixer contents | less' to check all amixer values defined in the _boot section of ucm, all values read from driver are same as the ones in the ucm, test speaker/microphone/headset, all work well. [Regression Risk] This could introduce failure on runing 'alsactl init' for some machines, then the amixers will not be initialized correctly, users will experience all audio can't work like speaker doesn't output sound or microphone can't record sound. But this regression possibility is very low, since We have tested it both on soundwire machines and non-soundwire machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899745/+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 1880193] Re: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.
** Changed in: autofs (Ubuntu) Status: Incomplete => Invalid ** Changed in: autofs (Ubuntu Focal) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu Focal) Status: Incomplete => Invalid -- 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/1880193 Title: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting. Status in autofs package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in autofs source package in Focal: Invalid Status in systemd source package in Focal: Invalid Bug description: autofs has a periodic error on mounting shares in Ubuntu 20.04 (it happens about 1 time out of 5): "Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting. Aborted (core dumped)" `autofs.service` restart (or `automount` app restart) fixes this issue. However if some of home dirs (like `Desktop` or `Documents`) are mounted by `autofs`, user can't login into Ubuntu Desktop Environment (PC freezes on login with black screen). Since this error can prevent user log in, it might be considered as critical bug. It happens both in `autofs` systemd service and by direct execution of `automount` app (`automount -f -d` command). May be it's an underlying error in `systemd` library (I found the line, mentioned in error, in its source codes). This issue has place in Ubuntu 20.04 (it works correctly in Ubuntu 18.04): > lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Packages versions: > apt-cache policy autofs systemd autofs: Installed: 5.1.6-2 Candidate: 5.1.6-2 Version table: *** 5.1.6-2 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1. Ubuntu 20.04 clean install 2. `apt install realmd sssd sssd-tools libnss-sss libpam-sss adcli samba-common-bin` 3. `realm join DOMAIN.NAME` 4. Enable makehomedir by command: `pam-auth-update` 5. `apt install cifs-utils` 6. `apt install autofs` 7. Add next line inside [domain/DOMAIN.EXT] section into /etc/sssd/sssd.conf: `krb5_ccname_template = FILE:%d/krb5cc_%U` 8. Reboot 9. Login as domain user and try to open directory, mounted by `autofs` (in my configuration shares are provided by AD). 10. `autofs.service` stops with the error above about 1 time out of 5 (not always). Found workaround: Add `Restart=always` into `[Service]` section in `/lib/systemd/system/autofs.service` file (in other words configure auto-restart on failures for autofs service). Attachments: 1. Full log of `automount -f -d` command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1880193/+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 1897744] Re: VerifyHostKeyDNS not working due to missing trust-ad flag
** Description changed: [impact] without trust-ad resolv.conf option, glibc will strip AD from systemd- resolved responses. one thing this will prevent working is ssh VerifyHostKeyDNS [test case] - setup a target system to ssh into, and create a SSHFP DNS record for its - public key. on a different source system, setup dns to enable DNSSEC, - and attempt to ssh to the target system using the VerifyHostKeyDNS=yes - option. - - setup of the SSHFP is out of scope for this bug, but e.g.: - https://en.wikipedia.org/wiki/SSHFP_record - https://tools.ietf.org/html/rfc4255 + see + https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1898590/comments/7 [regression potential] regressions would likely involve DNS lookup failures, probably if DNSSEC is enabled but possibly even without, and likely when the application requesting the dns lookup processes the response AD. [scope] this is needed only in focal. glibc first stripped the AD in version 2.31, so this is not needed in bionic or earlier. this was added upstream in commit a742f9828ea which was included in v246, so this is fixed already in groovy. [original description] Hi, 1) Description: Ubuntu 20.04.1 LTS Release: 20.04 2) systemd:245.4-4ubuntu3.2 3) I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp. 4) I still get the security question Matching host key fingerprint found in DNS. Are you sure you want to continue connecting (yes/no/[fingerprint])? The issue is known and fixed in systemd v246. https://github.com/systemd/systemd/pull/16072 Best regards Daniel -- 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/1897744 Title: VerifyHostKeyDNS not working due to missing trust-ad flag Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Bug description: [impact] without trust-ad resolv.conf option, glibc will strip AD from systemd- resolved responses. one thing this will prevent working is ssh VerifyHostKeyDNS [test case] see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1898590/comments/7 [regression potential] regressions would likely involve DNS lookup failures, probably if DNSSEC is enabled but possibly even without, and likely when the application requesting the dns lookup processes the response AD. [scope] this is needed only in focal. glibc first stripped the AD in version 2.31, so this is not needed in bionic or earlier. this was added upstream in commit a742f9828ea which was included in v246, so this is fixed already in groovy. [original description] Hi, 1) Description: Ubuntu 20.04.1 LTS Release: 20.04 2) systemd:245.4-4ubuntu3.2 3) I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp. 4) I still get the security question Matching host key fingerprint found in DNS. Are you sure you want to continue connecting (yes/no/[fingerprint])? The issue is known and fixed in systemd v246. https://github.com/systemd/systemd/pull/16072 Best regards Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897744/+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 1899878] Re: Python's test_ssl fails starting from Ubuntu 20.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1899878 Title: Python's test_ssl fails starting from Ubuntu 20.04 Status in openssl package in Ubuntu: Confirmed Bug description: Please take a look at https://bugs.python.org/issue41561. Developers who work on Python think that the issue is due to a change in Ubuntu 20.04 that is best described by https://bugs.python.org/issue41561#msg378089: "It sounds like a Debian/Ubuntu patch is breaking an assumption. Did somebody report the bug with Debian/Ubuntu maintainers of OpenSSL already? Fedora also configures OpenSSL with minimum protocol version of TLS 1.2. The distribution does it in a slightly different way that makes the restriction discoverable and that is compatible with Python's test suite." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1899878/+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 1899971] [NEW] Problematic dependency on python3-apport causes all Python invocations to install apport hook
Public bug reported: This would be no big deal if python3-apport just sat there until it was used (which it would never be on my system, since I removed apport). However, whenever python3-apport is installed, it unconditionally sets itself as sys.excepthook in Python3. The decision to have xserver-xorg depend on python3-apport basically means that every user who runs an X server will get this exception hook in Python whether they want it or not. And having python3-apport as the Python exception hook is not exactly harmless; it can still cause issues. My relatively minor but annoying issue is that I see deprecation warnings every time I get an error traceback, because python3-apport uses some deprecated code. I can imagine worse issues should there be an error in python3-apport; it could cause massive headaches and confusion for users who have no idea what's causing it. I'm not sure there is any point to have this dependency in the xserver- xorg package; it doesn't seem like those scripts will ever be run unless apport is installed and detects a crash, and apport already depends on python3-apport. I made a nice equivs package to allow myself to uninstall it, and as far as I can tell X and its applications still run fine. This is for Fossa, package version 1:7.7+19ubuntu. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1899971 Title: Problematic dependency on python3-apport causes all Python invocations to install apport hook Status in xorg package in Ubuntu: New Bug description: This would be no big deal if python3-apport just sat there until it was used (which it would never be on my system, since I removed apport). However, whenever python3-apport is installed, it unconditionally sets itself as sys.excepthook in Python3. The decision to have xserver-xorg depend on python3-apport basically means that every user who runs an X server will get this exception hook in Python whether they want it or not. And having python3-apport as the Python exception hook is not exactly harmless; it can still cause issues. My relatively minor but annoying issue is that I see deprecation warnings every time I get an error traceback, because python3-apport uses some deprecated code. I can imagine worse issues should there be an error in python3-apport; it could cause massive headaches and confusion for users who have no idea what's causing it. I'm not sure there is any point to have this dependency in the xserver-xorg package; it doesn't seem like those scripts will ever be run unless apport is installed and detects a crash, and apport already depends on python3-apport. I made a nice equivs package to allow myself to uninstall it, and as far as I can tell X and its applications still run fine. This is for Fossa, package version 1:7.7+19ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1899971/+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 1899962] [NEW] Wrong audio output device selected on Raspberry Pi Desktop
Public bug reported: On each boot, an incorrect audio output device is selected, at least when HDMI audio output is in use (still need to test the TV/aux output; will update the bug when done). Specifically, the settings application lists "Multichannel Output - Built-in Audio" as the selected output device. However, for audio to play through the connected HDMI device, "Analog Output - Built-in Audio" must be selected instead. Unfortunately, this setting will be lost on subsequent boots. A workaround is to remove the following lines from /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif However, removal of these lines will (as the comment suggests) result in hot-plugged USB devices *not* being automatically selected. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1899962 Title: Wrong audio output device selected on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: New Bug description: On each boot, an incorrect audio output device is selected, at least when HDMI audio output is in use (still need to test the TV/aux output; will update the bug when done). Specifically, the settings application lists "Multichannel Output - Built-in Audio" as the selected output device. However, for audio to play through the connected HDMI device, "Analog Output - Built-in Audio" must be selected instead. Unfortunately, this setting will be lost on subsequent boots. A workaround is to remove the following lines from /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif However, removal of these lines will (as the comment suggests) result in hot-plugged USB devices *not* being automatically selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899962/+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 1880193] Re: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.
Hello Michael, thanks for the followup and for filing the bug in the first place. For the moment I'm changing the status of this report to Incomplete across the packages/series it targets. If this specific issue can't be reproduced anymore please set the statuses to Invalid (I'd prefer it to Fix Released as we didn't identify what actually fixed it), and go ahead filing a new bug for the remaining issues you're facing. On the other hand if you still think this should be investigated please comment back with your findings, change the bug status back to New and we'll look at it again. Thanks! ** Changed in: autofs (Ubuntu) Status: Triaged => Incomplete ** Changed in: autofs (Ubuntu Focal) Status: Triaged => Incomplete ** Changed in: systemd (Ubuntu) Status: Triaged => Incomplete ** Changed in: systemd (Ubuntu Focal) Status: Triaged => Incomplete -- 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/1880193 Title: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting. Status in autofs package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in autofs source package in Focal: Incomplete Status in systemd source package in Focal: Incomplete Bug description: autofs has a periodic error on mounting shares in Ubuntu 20.04 (it happens about 1 time out of 5): "Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting. Aborted (core dumped)" `autofs.service` restart (or `automount` app restart) fixes this issue. However if some of home dirs (like `Desktop` or `Documents`) are mounted by `autofs`, user can't login into Ubuntu Desktop Environment (PC freezes on login with black screen). Since this error can prevent user log in, it might be considered as critical bug. It happens both in `autofs` systemd service and by direct execution of `automount` app (`automount -f -d` command). May be it's an underlying error in `systemd` library (I found the line, mentioned in error, in its source codes). This issue has place in Ubuntu 20.04 (it works correctly in Ubuntu 18.04): > lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Packages versions: > apt-cache policy autofs systemd autofs: Installed: 5.1.6-2 Candidate: 5.1.6-2 Version table: *** 5.1.6-2 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1. Ubuntu 20.04 clean install 2. `apt install realmd sssd sssd-tools libnss-sss libpam-sss adcli samba-common-bin` 3. `realm join DOMAIN.NAME` 4. Enable makehomedir by command: `pam-auth-update` 5. `apt install cifs-utils` 6. `apt install autofs` 7. Add next line inside [domain/DOMAIN.EXT] section into /etc/sssd/sssd.conf: `krb5_ccname_template = FILE:%d/krb5cc_%U` 8. Reboot 9. Login as domain user and try to open directory, mounted by `autofs` (in my configuration shares are provided by AD). 10. `autofs.service` stops with the error above about 1 time out of 5 (not always). Found workaround: Add `Restart=always` into `[Service]` section in `/lib/systemd/system/autofs.service` file (in other words configure auto-restart on failures for autofs service). Attachments: 1. Full log of `automount -f -d` command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1880193/+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 1899953] [NEW] Crackling audio on Raspberry Pi Desktop
Public bug reported: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: New Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899953/+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 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15
** Changed in: zlib (Ubuntu Focal) Status: New => In Progress ** Changed in: zlib (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1899621 Title: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15 Status in Release Notes for Ubuntu: New Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: In Progress Status in zlib source package in Focal: In Progress Status in zlib source package in Groovy: In Progress Bug description: Description: zlib: inflateSyncPoint() returns an incorrect result on z15 Symptom: Certain rsync builds fail with "error in rsync protocol data stream" on z15. Problem: inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. Solution: Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. [Impact] * Certain rsync builds fail with "error in rsync protocol data stream" on z15. * On ubuntu, rsync normally uses zstd or lz4. But when rsync is forced to use non-default zlib compression (-z flag) it uses inflateSyncPoint() API. This can also happen when rsync on the the other end doesn't support zstd & lz4. * inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. * Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. * Above makes rsync to succeed, when zlib uses hardware compression. [Test Case] Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 [Regression Potential] * inflateSyncPoint API is rarely used. Scanning codesearch, there is a lot of false positives due to embedded copies of zlib in all the things. I do see that both rsync and backuppc-rsync use it. It used during a safety check to ensure that algorithm is not at a sync point (or that cannot be determined). Nonetheless, returning error is a safer implementation for this API call. [Other Info] * This is a regression introduced by adding & enabling zlib hw acceleration by default on z15; and discovering using rsync that one API is implemented incorrectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899621/+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 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15
** Description changed: Description: zlib: inflateSyncPoint() returns an incorrect result on z15 Symptom: Certain rsync builds fail with "error in rsync protocol data -stream" on z15. + stream" on z15. Problem: inflateSyncPoint() does not take into account the hardware -compression state and returns an incorrect result. + compression state and returns an incorrect result. Solution: Make inflateSyncPoint() fail if the hardware compression is on. -The hardware does not provide enough information in order to -implement this function. + The hardware does not provide enough information in order to + implement this function. + + + [Impact] + + * Certain rsync builds fail with "error in rsync protocol data stream" + on z15. + + * rsync with non-default zlib compression (-z flag) uses + inflateSyncPoint() API. + + * inflateSyncPoint() does not take into account the hardware + compression state and returns an incorrect result. + + * Make inflateSyncPoint() fail if the hardware compression is on. The + hardware does not provide enough information in order to implement this + function. + + * Above makes rsync to succeed, when zlib uses hardware compression. + + [Test Case] + Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 + + [Regression Potential] + + * inflateSyncPoint API is rarely used. Scanning codesearch, there is a + lot of false positives due to embedded copies of zlib in all the things. + I do see that both rsync and backuppc-rsync use it. It used during a + safety check to ensure that algorithm is not at a sync point (or that + cannot be determined). Nonetheless, returning error is a safer + implementation for this API call. + + [Other Info] + + * This is a regression introduced by adding & enabling zlib hw acceleration by default on z15; and discovering using rsync that one API is implemented incorrectly. ** Description changed: Description: zlib: inflateSyncPoint() returns an incorrect result on z15 Symptom: Certain rsync builds fail with "error in rsync protocol data stream" on z15. Problem: inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. Solution: Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. + [Impact] - [Impact] - - * Certain rsync builds fail with "error in rsync protocol data stream" + * Certain rsync builds fail with "error in rsync protocol data stream" on z15. - * rsync with non-default zlib compression (-z flag) uses - inflateSyncPoint() API. + * On ubuntu, rsync normally uses zstd or lz4. But when rsync is forced + to use non-default zlib compression (-z flag) it uses inflateSyncPoint() + API. This can also happen when rsync on the the other end doesn't + support zstd & lz4. - * inflateSyncPoint() does not take into account the hardware + * inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. - * Make inflateSyncPoint() fail if the hardware compression is on. The + * Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. - * Above makes rsync to succeed, when zlib uses hardware compression. + * Above makes rsync to succeed, when zlib uses hardware compression. [Test Case] Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 [Regression Potential] - * inflateSyncPoint API is rarely used. Scanning codesearch, there is a + * inflateSyncPoint API is rarely used. Scanning codesearch, there is a lot of false positives due to embedded copies of zlib in all the things. I do see that both rsync and backuppc-rsync use it. It used during a safety check to ensure that algorithm is not at a sync point (or that cannot be determined). Nonetheless, returning error is a safer implementation for this API call. [Other Info] - - * This is a regression introduced by adding & enabling zlib hw acceleration by default on z15; and discovering using rsync that one API is implemented incorrectly. + + * This is a regression introduced by adding & enabling zlib hw + acceleration by default on z15; and discovering using rsync that one API + is implemented incorrectly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1899621 Title: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15 Status in Release Notes for Ubuntu: New Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Status in
[Touch-packages] [Bug 1899780] Re: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow
** Tags added: lxqt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1899780 Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow Status in software-properties package in Ubuntu: New Bug description: :~$ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 :~$ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.98.9.2 Candidate: 0.98.9.2 Table version: *** 0.98.9.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main i386 Packages 100 /var/lib/dpkg/status 0.98.9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Oct 14 14:49:36 2020 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1899780/+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 1899349] Re: Jack_control in jackd2 1.9.14 will not accept char parameters
This bug was fixed in the package jackd2 - 1.9.14-0ubuntu3.1 --- jackd2 (1.9.14-0ubuntu3.1) groovy; urgency=medium * debian/patches/git_dbus_bytes.patch: - Fix jack_control handling of dbus bytes, thanks Len (lp: #1899349) -- Sebastien Bacher Wed, 14 Oct 2020 09:59:30 +0200 ** Changed in: jackd2 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1899349 Title: Jack_control in jackd2 1.9.14 will not accept char parameters Status in jackd2 package in Ubuntu: Fix Released Bug description: trying to set self-connect-mode (for example): $ jack_control eps self-connect-mode e gives: --- engine param set "self-connect-mode" -> "e" Traceback (most recent call last): File "/usr/bin/jack_control", line 400, in main() File "/usr/bin/jack_control", line 283, in main configure_iface.SetParameterValue(['engine', param], python_type_to_jackdbus_type(value, type_char)) File "/usr/bin/jack_control", line 46, in python_type_to_jackdbus_type return dbus.Byte(value); TypeError: Expected a bytes or str of length 1, or an int in the range 0-255 This bug has been fixed upstream in commit ba28ffa @@ -43,7 +43,7 @@ def python_type_to_jackdbus_type(value, type_char): if type_char == "b": return bool_convert(value); elif type_char == "y": -return dbus.Byte(value); +return dbus.Byte(ord(value)); elif type_char == "i": return dbus.Int32(value) elif type_char == "u": To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1899349/+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 1899907] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1899907 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Processing triggers for initramfs-tools (0.136ubuntu6.3) ... update-initramfs: Generating /boot/initrd.img-5.4.0-51-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-51-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-121.123-generic 4.15.18 Uname: Linux 4.15.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 15 10:18:16 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-04-15 (1643 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1899907/+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 1899907] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: Processing triggers for initramfs-tools (0.136ubuntu6.3) ... update-initramfs: Generating /boot/initrd.img-5.4.0-51-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-51-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-121.123-generic 4.15.18 Uname: Linux 4.15.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 15 10:18:16 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-04-15 (1643 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-15 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1899907 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Processing triggers for initramfs-tools (0.136ubuntu6.3) ... update-initramfs: Generating /boot/initrd.img-5.4.0-51-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-51-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-121.123-generic 4.15.18 Uname: Linux 4.15.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 15 10:18:16 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-04-15 (1643 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1899907/+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 1899889] Re: In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the end
** Package changed: dash (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1899889 Title: In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the end of the last page. Status in gnome-shell package in Ubuntu: New Bug description: Upon installing a new application the list in "show applications" is not updated and just added at the end (last page). The list is also not sorted. When first installing Ubuntu 20.10, I could get the list updated by logging in and out, but after installing about 10 applications that stopped working. The Dash is version 0.5.10.2-7 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dash 0.5.10.2-7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 09:29:12 2020 InstallationDate: Installed on 2020-10-01 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923) RebootRequiredPkgs: linux-image-5.8.0-23-generic linux-base SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899889/+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 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
In the meantime I'm on 5.4.0-51-generic #56, but it's still happening. Google more about the error, there are some indications that it could be a faulty/bad firmware problem: https://www.kernel.org/doc/html/v5.4/sound/hd-audio/notes.html#codec- probing-problem -- 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/1894881 Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: kernel 5.4.0-47-generic #51 upgraded today to this new kernel sound is now totally broken kern.org and syslog are filling with those messages every second, in loop, with no end to it : Sep 8 19:42:34 orion kernel: [ 147.398030] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 8 19:42:35 orion kernel: [ 148.410043] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 8 19:42:36 orion kernel: [ 149.413955] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 8 19:42:37 orion kernel: [ 150.421890] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 8 19:42:38 orion kernel: [ 151.453799] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:39 orion kernel: [ 152.461793] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:41 orion kernel: [ 153.473734] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:42 orion kernel: [ 154.477653] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:43 orion kernel: [ 155.481576] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:44 orion kernel: [ 156.489620] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:45 orion kernel: [ 157.497553] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:46 orion kernel: [ 158.509530] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:47 orion kernel: [ 159.513471] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Because of this, machine has become very slow and response time is awful Login into the machine, even trying to launch a simple program can take up to 30 seconds of wait before anything happens. Sound was working fine with previous kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gf 1758 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 19:42:19 2020 InstallationDate: Installed on 2020-08-29 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894881/+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 1899889] [NEW] In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the e
Public bug reported: Upon installing a new application the list in "show applications" is not updated and just added at the end (last page). The list is also not sorted. When first installing Ubuntu 20.10, I could get the list updated by logging in and out, but after installing about 10 applications that stopped working. The Dash is version 0.5.10.2-7 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dash 0.5.10.2-7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 09:29:12 2020 InstallationDate: Installed on 2020-10-01 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923) RebootRequiredPkgs: linux-image-5.8.0-23-generic linux-base SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1899889 Title: In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the end of the last page. Status in dash package in Ubuntu: New Bug description: Upon installing a new application the list in "show applications" is not updated and just added at the end (last page). The list is also not sorted. When first installing Ubuntu 20.10, I could get the list updated by logging in and out, but after installing about 10 applications that stopped working. The Dash is version 0.5.10.2-7 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dash 0.5.10.2-7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 09:29:12 2020 InstallationDate: Installed on 2020-10-01 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923) RebootRequiredPkgs: linux-image-5.8.0-23-generic linux-base SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1899889/+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 1899764] Re: [Realtek ALC257][Lenovo T14 Gen1] Internal mic or headset mic not detected
After further investigations, the problem could come from the computer itself. I finished my distro / kernel tests with a windows installation, and I discovered that the mic is still unavailable... Sorry for the inconvenience, I think you can close this ticket. I am going to bring in the on-site support to fix the problem on window, before going further on the linux side. -- 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/1899764 Title: [Realtek ALC257][Lenovo T14 Gen1] Internal mic or headset mic not detected Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hello, I've received a brand new Lenovo T14 Gen 1 (Intel), that suffers of some incompatibilities with Ubuntu. The internal mic is not detected (only analog input is displayed). And when a headset is plug, only the output works. I've tried lots of alsa-base.conf snd-hda-intel overrides without success. Tested on U18 and U20. > uname -a Linux julien-ThinkPad-T14-Gen-1 5.9.0-050900-generic #202010112230 SMP Sun Oct 11 22:34:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (tried with stock kernel and kernel-oem too) > arecord -l Liste des Périphériques Matériels CAPTURE carte 0: PCH [HDA Intel PCH], périphérique 0: ALC257 Analog [ALC257 Analog] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 2: ALC257 Alt Analog [ALC257 Alt Analog] Sous-périphériques: 2/2 Sous-périphérique #0: subdevice #0 Sous-périphérique #1: subdevice #1 > cat /proc/asound/card0/codec\#0 https://gist.github.com/julienlafont-tabmo/4ba9311bbb1d3d918532279d7578ba28 > hdajackretask (default configuration) - Internal speaker Ox14 - Black headphone, Right Side, 0x21 - All others: not connected > alsa-info http://alsa-project.org/db/?f=a5af631628bef97a85cace2574b7c6694037130a > alba-base.conf settings tried without success: options snd-hda-intel model=laptop-dmic -- options snd-hda-intel dmic_detect=0 options snd-hda-intel index=0 model=laptop-dmic -- options snd-hda-intel dmic_detect=0 options snd-hda-intel index=1 model=laptop-dmic -- options snd-hda-intel model=auto -- options snd-hda-intel model=headset-mic Do you have some idea to make the mic working? Bests, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1899764/+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