[Touch-packages] [Bug 1975872] [NEW] Screen flickering on external monitor (laptop)
Public bug reported: External screen flickers on and off (image is present and then signal is lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh installation. Details: - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make that HDMI work with NVIDIA GTX 960M in my laptop). - Nothing was installed after installing the OS - i connected to the Internet while installing the system and marked the option to download the updates. - I had that issue on Windows 10 - I fixed it by installing a latest Intel GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers installed by Windows - they were the latest Intel drivers. - Internal screen works fine. - If I mirror external and internal monitor, external isn't flickering, but internal monitor's resolution is lower that external's one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 26 22:34:16 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d] InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. GL552VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=be9d6e78-64ad-42f3-883b-15903e52b776 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: GL dmi.product.name: GL552VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/1975872 Title: Screen flickering on external monitor (laptop) Status in xorg package in Ubuntu: New Bug description: External screen flickers on and off (image is present and then signal is lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh installation. Details: - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make that HDMI work with NVIDIA GTX 960M in my laptop). - Nothing was installed after installing the OS - i connected to the Internet while installing the system and marked the option to download the updates. - I had that issue on Windows 10 - I fixed it by installing a latest Intel GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers installed by Windows - they were the latest Intel drivers. - Internal screen works fine. - If I mirror external and internal monitor, external isn't flickering, but internal monitor's resolution is lower that external's one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13]
[Touch-packages] [Bug 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
I struggled with this issue for a while until I discovered thar the issue is with the color profile as described in this question https://askubuntu.com/questions/1404516/screen-turns-yellow-even-using- the-live-option-ubuntu-22-04. The way to solve it for me was to add a new color profile in Setting/Color tab -> Add profile for a display. "Standard Space - sRGB" works just right for my Dell XPS 9560 laptop. The issue must be with how the default color profiles are generated for a screen. I have an external monitor and there were no issue with colors there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Problem has NOT been fixed for my setup: - Kernel: 5.4.0-65-generic (also tried 5.11.0-051100-generic) - OS: Lubuntu 20.04.2 LTS - Machine: OptiPlex 9020 - Headset: Sony WH-XB900N -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895665] Re: PulseAudio automatically switches from HDMI 2 after display sleep
It seems that it depends on connected monitor. In my case monitor goes to power saving mode after laptop suspend or in few minutes after system lock. So ubuntu switches to analog device after resume/unlock. But its not so critical, because device can be easily changed with tray icon. And for HDMI 2 selecting I also had to open sound settings window. Btw, maybe try to set priority=99 for hdmi-output-1.conf? -- 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/1895665 Title: PulseAudio automatically switches from HDMI 2 after display sleep Status in pulseaudio package in Ubuntu: New Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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
Re: [Touch-packages] [Bug 1895665] Re: PulseAudio automatically switches from HDMI 2 after display sleep
Right. I just tested: Selected digital device. Selected HDMI 2 for digital device. Disconnected HDMI 2 from laptop (digital device automatically switched to HDMI 1, sound automatically switched to internal analog audio). Connected HDMI 2 to laptop (digital device automatically switched to HDMI 2 - this resolves the main part of the issue, but sound still left on internal analog audio). On Wed, Sep 16, 2020 at 12:30 PM Hui Wang <1895...@bugs.launchpad.net> wrote: > Do you mean even did the change of #2, the output device still changes > to internal analog audio after sleep? Before sleep, you select the hdmi- > output-2 manually? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1895665 > > Title: > PulseAudio automatically switches from HDMI 2 after display sleep > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > I have an Nvidia based video card that has an HDMI output + a > DisplayPort output. > DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI > output is listed as "Digital Stereo (HDMI 2)". > > I prefer to use "Digital Stereo (HDMI 2)". > But after each display sleep (screen lock for example) audio is switched > to built in audio > > 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 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu27.8 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: XFCE > Date: Tue Sep 15 14:56:58 2020 > InstallationDate: Installed on 2020-06-20 (86 days ago) > InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > SourcePackage: pulseaudio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/11/2019 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.11.1 > dmi.board.name: 0CNDTP > dmi.board.vendor: Dell Inc. > dmi.board.version: A01 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: > dmi.product.family: GSeries > dmi.product.name: G5 5590 > dmi.product.sku: 08EA > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+subscriptions > -- 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/1895665 Title: PulseAudio automatically switches from HDMI 2 after display sleep Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1895665] Re: PulseAudio automatically switches from HDMI 2 after display sleep
After #2 it prefers HDMI 2 when its connected, thanks @hui.wang. But seems that anyway it prefers internal analog audio instead of digital audio. Will observe more to understand new behavior after reboots, suspends and locks. -- 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/1895665 Title: PulseAudio automatically switches from HDMI 2 after display sleep Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1895665] [NEW] PulseAudio automatically switches from HDMI 2 after display sleep
Public bug reported: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot_2020-09-15_15-49-17.jpg" https://bugs.launchpad.net/bugs/1895665/+attachment/5411015/+files/screenshot_2020-09-15_15-49-17.jpg -- 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/1895665 Title: PulseAudio automatically switches from HDMI 2 after display sleep Status in pulseaudio package in Ubuntu: New Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 #lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal #uname -r 5.4.0-37-generic #pulseaudio --version pulseaudio 13.99.1 [B4:86:55:E1:8B:07] Name: FlyPods Lite Alias: FlyPods Lite [rw] Address: B4:86:55:E1:8B:07 Icon: audio-card Class: 0x2c0404 Paired: 1 Trusted: 1 [rw] Blocked: 0 [rw] Connected: 1 UUIDs: [AudioSource, AudioSink, AVRemoteControl, Handsfree, PnPInformation] bt-device -s B4:86:55:E1:8B:07 Discovering services... [RECORD:0x1] SrvClassIDList: "AudioSink" ProtocolDescList: "L2CAP", 0x19 "AVDTP", 0x103 BTProfileDescList: "AdvAudio", 0x103 SrvName: "Advanced Audio" ProviderName: "MtView" [RECORD:0x10002] SrvClassIDList: "Handsfree", "Audio" ProtocolDescList: "L2CAP" "RFCOMM", Channel: 1 BTProfileDescList: "Handsfree", 0x107 SrvName: "Hands-Free unit " [RECORD:0x10001] SrvClassIDList: "AVRemote", "VideoConf" ProtocolDescList: "L2CAP", 0x17 "AVCTP", 0x102 BTProfileDescList: "AVRemote", 0x105 SrvName: "MVIEW " ProviderName: "MVIEW " [RECORD:0x10003] SrvClassIDList: "AudioSource" ProtocolDescList: "L2CAP", 0x19 "AVDTP", 0x103 BTProfileDescList: "AdvAudio", 0x103 SrvName: "Advanced Audio" ProviderName: "MtView" -- 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/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 1794169] Re: AWS ubuntu became unreachable after ssh login
information attached and status changed. i'm using linux-image-4.15.0-1021-aws. based on https://packages.ubuntu.com/bionic/linux-image-4.15.0-1021-aws it maintained my Ubuntu Core. Also i'm not 100% sure that issue in the kernel. -- 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/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1794169] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1794169/+attachment/5193230/+files/UdevDb.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1794169] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1794169/+attachment/5193228/+files/ProcModules.txt -- 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/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1794169] SystemdDelta.txt
apport information ** Attachment added: "SystemdDelta.txt" https://bugs.launchpad.net/bugs/1794169/+attachment/5193229/+files/SystemdDelta.txt -- 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/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1794169] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1794169/+attachment/5193227/+files/ProcInterrupts.txt -- 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/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1794169] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1794169/+attachment/5193226/+files/ProcCpuinfoMinimal.txt -- 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/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1794169] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1794169/+attachment/5193223/+files/Dependencies.txt -- 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/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1794169] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1794169/+attachment/5193222/+files/CurrentDmesg.txt -- 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/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1794169] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1794169/+attachment/5193225/+files/ProcCpuinfo.txt -- 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/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1794169] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1794169/+attachment/5193224/+files/Lspci.txt -- 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/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1794169] Re: AWS ubuntu became unreachable after ssh login
apport information ** Tags added: apport-collected ec2-images ** Description changed: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. + --- + ProblemType: Bug + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.3 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + CRDA: N/A + DistroRelease: Ubuntu 18.04 + Ec2AMI: ami-91caece9 + Ec2AMIManifest: (unknown) + Ec2AvailabilityZone: us-west-2b + Ec2InstanceType: m5.xlarge + Ec2Kernel: unavailable + Ec2Ramdisk: unavailable + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: Amazon EC2 m5.xlarge + Package: systemd 237-3ubuntu10.3 + PackageArchitecture: amd64 + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 + ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-1021-aws N/A + linux-backports-modules-4.15.0-1021-aws N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic ec2-images + Uname: Linux 4.15.0-1021-aws x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: docker + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 10/16/2017 + dmi.bios.vendor: Amazon EC2 + dmi.bios.version: 1.0 + dmi.board.asset.tag: i-02cfe7fcd8a997085 + dmi.board.vendor: Amazon EC2 + dmi.chassis.asset.tag: Amazon EC2 + dmi.chassis.type: 1 + dmi.chassis.vendor: Amazon EC2 + dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: + dmi.product.name: m5.xlarge + dmi.sys.vendor: Amazon EC2 ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1794169/+attachment/5193221/+files/AudioDevicesInUse.txt -- 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/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins.
[Touch-packages] [Bug 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster
@Jacopo Yes, sometimes. Even restarting audacity or arecord does the trick. What really annoying is the noise level. And, yes I've tried everything under Windows 10 and sound records perfectly. The problem is that I hate too use Windows :) Oh, I've updated linux kernel to 4.18 and the problem is still there. -- 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/1764965 Title: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recording applications (audacity, arecord, gnome-sound-recorder) record extremely slowly (at what seems to be 0,1x speed), which means that at playback the sound is played at a very high pitch and much faster than the original. To help you understand the issue, I've attached an archive containing two files recorded at the same time, one with arecord -f cd and the other with a stand-alone Olympus recorder. A video of Audacity's behavior when trying to record is also available: https://youtu.be/Fe20eQNvZVA Look at the seconds hand of the xclock and how much it is moving before Audacity is done recording one second of audio. Things I've already tried: * Purging and reinstalling Audacity * Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki * Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 audacity as suggested on AskUbuntu * Reinstalling Ubuntu on a new hard disk * Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 daily and Xubuntu 17.10.1, 18.04) The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard. The problem can be reproduced as follows: * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've tested with) * Install audacity via the terminal * Start recording, microphone is connected to the rear microphone jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacopo 2417 F pulseaudio /dev/snd/controlC0: jacopo 2417 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 18 09:35:50 2018 InstallationDate: Installed on 2018-03-03 (45 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. 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/alsa-driver/+bug/1764965/+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 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster
Nope, tried again with arecord and it's recording slowly again. The same situation with audacity, sometimes it works and sometimes not. -- 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/1764965 Title: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recording applications (audacity, arecord, gnome-sound-recorder) record extremely slowly (at what seems to be 0,1x speed), which means that at playback the sound is played at a very high pitch and much faster than the original. To help you understand the issue, I've attached an archive containing two files recorded at the same time, one with arecord -f cd and the other with a stand-alone Olympus recorder. A video of Audacity's behavior when trying to record is also available: https://youtu.be/Fe20eQNvZVA Look at the seconds hand of the xclock and how much it is moving before Audacity is done recording one second of audio. Things I've already tried: * Purging and reinstalling Audacity * Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki * Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 audacity as suggested on AskUbuntu * Reinstalling Ubuntu on a new hard disk * Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 daily and Xubuntu 17.10.1, 18.04) The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard. The problem can be reproduced as follows: * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've tested with) * Install audacity via the terminal * Start recording, microphone is connected to the rear microphone jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacopo 2417 F pulseaudio /dev/snd/controlC0: jacopo 2417 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 18 09:35:50 2018 InstallationDate: Installed on 2018-03-03 (45 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. 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/alsa-driver/+bug/1764965/+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 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster
I've also tried command line tool for sound recording - arecord. And it works, somehow, but sound is very noisy and staticky. -- 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/1764965 Title: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recording applications (audacity, arecord, gnome-sound-recorder) record extremely slowly (at what seems to be 0,1x speed), which means that at playback the sound is played at a very high pitch and much faster than the original. To help you understand the issue, I've attached an archive containing two files recorded at the same time, one with arecord -f cd and the other with a stand-alone Olympus recorder. A video of Audacity's behavior when trying to record is also available: https://youtu.be/Fe20eQNvZVA Look at the seconds hand of the xclock and how much it is moving before Audacity is done recording one second of audio. Things I've already tried: * Purging and reinstalling Audacity * Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki * Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 audacity as suggested on AskUbuntu * Reinstalling Ubuntu on a new hard disk * Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 daily and Xubuntu 17.10.1, 18.04) The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard. The problem can be reproduced as follows: * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've tested with) * Install audacity via the terminal * Start recording, microphone is connected to the rear microphone jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacopo 2417 F pulseaudio /dev/snd/controlC0: jacopo 2417 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 18 09:35:50 2018 InstallationDate: Installed on 2018-03-03 (45 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. 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/alsa-driver/+bug/1764965/+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 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster
I have the same problem and my board is MSI X370 Pro Carbon, (same ALC1220 Chipset). Tried Kubuntu 18.04 and Ubuntu 18.04. Recording with audacity also slow to the extreme. I changed sample rate in audacity to 51 or 52 Hz as a temporary workaround, but the sound is very noisy. -- 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/1764965 Title: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recording applications (audacity, arecord, gnome-sound-recorder) record extremely slowly (at what seems to be 0,1x speed), which means that at playback the sound is played at a very high pitch and much faster than the original. To help you understand the issue, I've attached an archive containing two files recorded at the same time, one with arecord -f cd and the other with a stand-alone Olympus recorder. A video of Audacity's behavior when trying to record is also available: https://youtu.be/Fe20eQNvZVA Look at the seconds hand of the xclock and how much it is moving before Audacity is done recording one second of audio. Things I've already tried: * Purging and reinstalling Audacity * Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki * Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 audacity as suggested on AskUbuntu * Reinstalling Ubuntu on a new hard disk * Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 daily and Xubuntu 17.10.1, 18.04) The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard. The problem can be reproduced as follows: * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've tested with) * Install audacity via the terminal * Start recording, microphone is connected to the rear microphone jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacopo 2417 F pulseaudio /dev/snd/controlC0: jacopo 2417 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 18 09:35:50 2018 InstallationDate: Installed on 2018-03-03 (45 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. 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/alsa-driver/+bug/1764965/+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 1698541] Re: [MacBookAir4, 2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] Underruns, dropouts or crackling sound
I solved it by switching from stereo to mono sound in headphones. But I am still researching this issue, is it problem in hardware chip or a program bug. -- 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/1698541 Title: [MacBookAir4,2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Invalid Bug description: I use next version of ubuntu x86_64 Description: Ubuntu 16.04.2 LTS Release: 16.04 kernel 4.2.8-040208-lowlatency alsa-base 1.0.25+dfsg-0ubuntu5 alsa-utils 1.1.0-0ubuntu5 gstreamer1.0-alsa:amd64 1.8.3-1ubuntu0.2 Sound from speakers works fine (tested on wav and mp3 files). Problem appears when I plug headphones, I hear audio crackling and noises during sound play. But when I tried listen to music from flash player (like youtube , online radio ...) sound works good without any problems in headphones. I tried to add different options in /etc/modprobe.d/alsa-base.conf and changing configuration /etc/pulse/default.pa, but it didn't help. Also I loaded ubuntu with kernels 4.8.0-54-generic, 4.8.0-53-generic but it isn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.2.8-040208-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ash1911 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 17 15:21:52 2017 InstallationDate: Installed on 2017-06-05 (12 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Green Headphone Out, UNKNOWN Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [MacBookAir4,2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B14.1510261805 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B14.1510261805:bd10/26/2015:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-17T15:11:50.985356 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1698541/+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 1698541] Re: [MacBookAir4, 2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] Underruns, dropouts or crackling sound
** Changed in: alsa-driver (Ubuntu) Assignee: (unassigned) => Andrii (comachada) ** Changed in: alsa-driver (Ubuntu) Status: New => In Progress ** Changed in: alsa-driver (Ubuntu) Status: In Progress => Invalid -- 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/1698541 Title: [MacBookAir4,2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Invalid Bug description: I use next version of ubuntu x86_64 Description: Ubuntu 16.04.2 LTS Release: 16.04 kernel 4.2.8-040208-lowlatency alsa-base 1.0.25+dfsg-0ubuntu5 alsa-utils 1.1.0-0ubuntu5 gstreamer1.0-alsa:amd64 1.8.3-1ubuntu0.2 Sound from speakers works fine (tested on wav and mp3 files). Problem appears when I plug headphones, I hear audio crackling and noises during sound play. But when I tried listen to music from flash player (like youtube , online radio ...) sound works good without any problems in headphones. I tried to add different options in /etc/modprobe.d/alsa-base.conf and changing configuration /etc/pulse/default.pa, but it didn't help. Also I loaded ubuntu with kernels 4.8.0-54-generic, 4.8.0-53-generic but it isn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.2.8-040208-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ash1911 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 17 15:21:52 2017 InstallationDate: Installed on 2017-06-05 (12 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Green Headphone Out, UNKNOWN Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [MacBookAir4,2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B14.1510261805 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B14.1510261805:bd10/26/2015:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-17T15:11:50.985356 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1698541/+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 1698541] [NEW] [MacBookAir4, 2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] Underruns, dropouts or crackling sound
Public bug reported: I use next version of ubuntu x86_64 Description:Ubuntu 16.04.2 LTS Release:16.04 kernel 4.2.8-040208-lowlatency alsa-base 1.0.25+dfsg-0ubuntu5 alsa-utils 1.1.0-0ubuntu5 gstreamer1.0-alsa:amd64 1.8.3-1ubuntu0.2 Sound from speakers works fine (tested on wav and mp3 files). Problem appears when I plug headphones, I hear audio crackling and noises during sound play. But when I tried listen to music from flash player (like youtube , online radio ...) sound works good without any problems in headphones. I tried to add different options in /etc/modprobe.d/alsa-base.conf and changing configuration /etc/pulse/default.pa, but it didn't help. Also I loaded ubuntu with kernels 4.8.0-54-generic, 4.8.0-53-generic but it isn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.2.8-040208-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ash1911 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 17 15:21:52 2017 InstallationDate: Installed on 2017-06-05 (12 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Green Headphone Out, UNKNOWN Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [MacBookAir4,2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B14.1510261805 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B14.1510261805:bd10/26/2015:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-17T15:11:50.985356 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1698541 Title: [MacBookAir4,2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: I use next version of ubuntu x86_64 Description: Ubuntu 16.04.2 LTS Release: 16.04 kernel 4.2.8-040208-lowlatency alsa-base 1.0.25+dfsg-0ubuntu5 alsa-utils 1.1.0-0ubuntu5 gstreamer1.0-alsa:amd64 1.8.3-1ubuntu0.2 Sound from speakers works fine (tested on wav and mp3 files). Problem appears when I plug headphones, I hear audio crackling and noises during sound play. But when I tried listen to music from flash player (like youtube , online radio ...) sound works good without any problems in headphones. I tried to add different options in /etc/modprobe.d/alsa-base.conf and changing configuration /etc/pulse/default.pa, but it didn't help. Also I loaded ubuntu with kernels 4.8.0-54-generic, 4.8.0-53-generic but it isn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.2.8-040208-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ash1911 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 17 15:21:52 2017 InstallationDate: Installed on 2017-06-05 (12 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Green Headphone Out, UNKNOWN Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [MacBookAir4,2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B14.1510261805
[Touch-packages] [Bug 1509562] Re: no icons for menu, folders, directories, files
For those who uses standalone window manager instead of gnome/kde/etc but wants icons back there's a workaround: you have to define environment variable XDG_CURRENT_DESKTOP=gnome. Don't know if other values work as well. Source: https://bbs.archlinux.org/viewtopic.php?id=160206 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1509562 Title: no icons for menu, folders, directories, files Status in dolphin package in Ubuntu: Confirmed Status in kate package in Ubuntu: Confirmed Status in kdepim package in Ubuntu: Confirmed Status in konsole package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: no icons for menu, folders, directories, files I am using Xubuntu 15.10 as the Guest in Virtualbox 5.0.8 r103449. This happened after a recent Xubuntu update. Info: $ apt-cache policy dolphin dolphin: Installed: 4:15.08.2-0ubuntu1 Candidate: 4:15.08.2-0ubuntu1 Version table: *** 4:15.08.2-0ubuntu1 0 500 http://mirror.cogentco.com/pub/linux/ubuntu/ wily/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dolphin 4:15.08.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 23 17:35:08 2015 InstallationDate: Installed on 2015-06-01 (144 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150521) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dolphin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1509562/+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 1463475] [NEW] package libffi6:i386 3.1~rc1+r3.0.13-12 failed to install/upgrade: package libffi6:i386 is already installed and configured
Public bug reported: not known ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libffi6:i386 3.1~rc1+r3.0.13-12 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Tue Jun 9 10:45:48 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libffi6:i386:3.1~rc1+r3.0.13-12:package libffi6:i386 is already installed and configured ErrorMessage: package libffi6:i386 is already installed and configured InstallationDate: Installed on 2015-06-09 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: i386 SourcePackage: libffi Title: package libffi6:i386 3.1~rc1+r3.0.13-12 failed to install/upgrade: package libffi6:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libffi (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1463475 Title: package libffi6:i386 3.1~rc1+r3.0.13-12 failed to install/upgrade: package libffi6:i386 is already installed and configured Status in libffi package in Ubuntu: New Bug description: not known ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libffi6:i386 3.1~rc1+r3.0.13-12 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Tue Jun 9 10:45:48 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libffi6:i386:3.1~rc1+r3.0.13-12:package libffi6:i386 is already installed and configured ErrorMessage: package libffi6:i386 is already installed and configured InstallationDate: Installed on 2015-06-09 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: i386 SourcePackage: libffi Title: package libffi6:i386 3.1~rc1+r3.0.13-12 failed to install/upgrade: package libffi6:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1463475/+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