[Touch-packages] [Bug 1834817] Re: Faulty screen lock toggle and erratic dock auto hide
It appears you are reporting two separate issues. Please pick one for this bug to be about and then open a new bug for the other. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1834817 Title: Faulty screen lock toggle and erratic dock auto hide Status in gnome-shell package in Ubuntu: Incomplete Bug description: Fresh install 18.04.2.Screen locks after 30 minutes despite toggle ON/OFF in settings or terminal command "gsettings set org.gnome.desktop.lockdown disable-lock-screen 'false' or 'true'" Dock set to auto hide does not return properly when mouse over. Dock set to 'Bottom'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 14:18:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkCentre M6258 [17aa:3048] Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller [17aa:3048] InstallationDate: Installed on 2019-06-30 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 7360PU5 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT77AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NONE dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT77AUS:bd05/07/2012:svnLENOVO:pn7360PU5:pvrThinkCentre:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.family: NONE dmi.product.name: 7360PU5 dmi.product.sku: NONE dmi.product.version: ThinkCentre dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834817/+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 1834817] [NEW] Faulty screen lock toggle and erratic dock auto hide
Public bug reported: Fresh install 18.04.2.Screen locks after 30 minutes despite toggle ON/OFF in settings or terminal command "gsettings set org.gnome.desktop.lockdown disable-lock-screen 'false' or 'true'" Dock set to auto hide does not return properly when mouse over. Dock set to 'Bottom'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 14:18:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkCentre M6258 [17aa:3048] Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller [17aa:3048] InstallationDate: Installed on 2019-06-30 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 7360PU5 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT77AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NONE dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT77AUS:bd05/07/2012:svnLENOVO:pn7360PU5:pvrThinkCentre:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.family: NONE dmi.product.name: 7360PU5 dmi.product.sku: NONE dmi.product.version: ThinkCentre dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1834817 Title: Faulty screen lock toggle and erratic dock auto hide Status in xorg package in Ubuntu: New Bug description: Fresh install 18.04.2.Screen locks after 30 minutes despite toggle ON/OFF in settings or terminal command "gsettings set org.gnome.desktop.lockdown disable-lock-screen 'false' or 'true'" Dock set to auto hide does not return properly when mouse over. Dock set to 'Bottom'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 14:18:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkCentre M6258 [17aa:3048] Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller [17aa:3048] InstallationDate: Installed on 2019-06-30 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 7360PU5 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT77AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NONE dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT77AUS:bd05/07/2012:svnLENOVO:pn7360PU5:pvrThinkCentre:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.family: NONE dmi.product.name:
[Touch-packages] [Bug 1827181] Re: 18.04 - Need to purge and reload alsa and pulseaudio to get sound
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1827181 Title: 18.04 - Need to purge and reload alsa and pulseaudio to get sound Status in pulseaudio package in Ubuntu: Expired Bug description: When I start my computer (running Ubuntu 18.04.2 LTS), there is no sound from the speakers plugged into the line-out jack. In order to get sound, I need to run the following sequence of commands: sudo apt-get update && sudo apt-get upgrade sudo apt-get remove --purge alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio pavucontrol sudo alsa force-reload reboot sudo apt-get install pavucontrol pulseaudio --start My system is dual-boot with Windows 10, but it doesn't seem to need me to boot Windows 10 in order to lose the settings in Ubuntu. This problem started on 19 March 2019 when I was trying to record some audio with audacity and I've just found the above fix to get things running, but sadly the problem reverts when I shutdown. Related packages: pulseaudio: Installed: 1:11.1-1ubuntu7.2 Candidate: 1:11.1-1ubuntu7.2 Version table: *** 1:11.1-1ubuntu7.2 500 500 http://nz.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://nz.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status pavucontrol: Installed: 3.0-4 Candidate: 3.0-4 Version table: *** 3.0-4 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827181/+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 1834784] Re: Xorg freeze
When the problem happens does the mouse pointer freeze too? Only if the mouse pointer freezes is it the Xorg process that's frozen. ** Tags added: amdgpu ** Summary changed: - Xorg freeze + [amdgpu[ Xorg freeze ** Summary changed: - [amdgpu[ Xorg freeze + [amdgpu] Xorg freeze ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1834784 Title: [amdgpu] Xorg freeze Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I can't provide much in the way of detail as the freezes are seemingly random. They happen with different software being used. Release: Ubuntu 18.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 30 17:40:47 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Nitro+ Radeon RX 580 4GB [1da2:e366] InstallationDate: Installed on 2019-06-30 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=71fe103c-b7c8-4fbd-970d-39d7569306ab ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4011 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.:bvr4011:bd04/19/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.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1834784/+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 1834782] Re: ASUS Zenbook UX433FN: sound stops working after a couple of seconds
If the problem started only a month ago then it wouldn't be pulseaudio because that hardly ever changes. Most likely it is the kernel, which gets updated more frequently. Can you please try some older (or newer) kernel versions from here: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D and tell us if any are able to avoid the bug? ** No longer affects: alsa-driver (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete ** Changed in: linux-hwe (Ubuntu) Status: New => Incomplete ** Changed in: linux-hwe-edge (Ubuntu) Status: New => Incomplete -- 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/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in linux-firmware package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1834782/+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 1834761] Re: monitor refresh rates higher than 120 Hz not detected/cannot be set
Yes, it seems to be an issue either with the amdgpu graphics driver, or with the monitor's own detection data that the supported modes are limited to [ 3.773] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [ 3.773] (II) AMDGPU(0): Modeline "2560x1440"x60.0 241.70 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (88.9 kHz eP) [ 3.773] (II) AMDGPU(0): Modeline "2560x1440"x120.0 497.75 2560 2608 2640 2720 1440 1443 1448 1525 +hsync -vsync (183.0 kHz e) [ 3.773] (II) AMDGPU(0): Modeline "2560x1440"x50.0 201.42 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (74.1 kHz e) [ 3.773] (II) AMDGPU(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e) [ 3.773] (II) AMDGPU(0): Modeline "1920x1080"x144.0 325.04 1920 1944 1976 2056 1080 1084 1089 1098 +hsync -vsync (158.1 kHz e) and lower... ** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Summary changed: - monitor refresh rates higher than 120 Hz not detected/cannot be set + [amdgpu] monitor refresh rates higher than 120 Hz not detected/cannot be set -- 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/1834761 Title: [amdgpu] monitor refresh rates higher than 120 Hz not detected/cannot be set Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: using this monitor: https://www.pixiogaming.com/px329 and this video card: https://www.gigabyte.com/us/Graphics-Card/GV-RX580GAMING-4GD-rev-10-11 I am unable to set any refresh rates higher than 120 Hz. The video card and the monitor both support 144 Hz and 165 Hz yet those refresh rates are not available as options to choose in the settings app. I've tried a couple of online guides using xrandr to add and set a custom display resolution/refresh rate but I can't get it to go any higher than 120 Hz. I have the exact same hardware running macOS Mojave 10.14.4 and it allows me to set the refresh rate to 144 Hz and 165 Hz. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 29 18:13:05 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 470/480/570/580] [1458:22fd] InstallationDate: Installed on 2019-06-28 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=8d1eef58-5823-4ca0-abb0-d2c79b140e40 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd01/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
[Touch-packages] [Bug 1834731] Re: System hung while booting
It appears your system is having some disk trouble which may be related: [8.507702] systemd-journald[282]: Received request to flush runtime journal from PID 1 [9.786399] systemd-journald[282]: File /var/log/journal/a99c9c8a58fcb89719f7d37e51877f86/system.journal corrupted or uncleanly shut down, renaming and replacing. Also it sounds like starting some network interfaces is taking a long time: A start job is running for Raise network interfaces (31s / 5min 16s) So please try booting without your USB wifi dongle plugged in. If that doesn't fix the problem then please run this command after a fresh reboot: journalctl -b0 > curboot.txt and attach the file 'curboot.txt'. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1834731 Title: System hung while booting Status in Ubuntu: Incomplete Bug description: Booting is not happening properly. Either it will display few options like Ubnut, Advance Ubuntu or it is getting hung. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18 Uname: Linux 4.15.0-53-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jun 29 11:54:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-51-generic, i686: installed rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-53-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04ab] InstallationDate: Installed on 2013-05-06 (2244 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: Dell Inc. Vostro 460 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-53-generic root=UUID=37e1c2cf-5770-4b8c-af11-1fdfc29f5133 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/21/2011:svnDellInc.:pnVostro460:pvr:rvnDellInc.:rn0Y2MRG:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 460 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jun 29 11:52:13 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Entry Keyboard KEYBOARD, id 8 inputUSB Optical MouseMOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1834731/+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 1834794] Re: Uses too much memory (6Gbyte process)
Thanks for that. I've never seen pulseaudio do this before. 1. Do you have any ideas as to what apps might have been using pulseaudio recently? 2. Is the problem regular? Does it return after a reboot? 3. Does the same problem exist in Ubuntu 19.04 if you boot that from USB? (http://releases.ubuntu.com/19.04/) We use a newer version of PulseAudio in all Ubuntu releases from 18.10 onward so I am wondering if this is a bug that was fixed already. -- 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/1834794 Title: Uses too much memory (6Gbyte process) Status in pulseaudio package in Ubuntu: Incomplete Bug description: So, my pulseaudio process is 6Gbyte large, 3.5Gb of that resident in memory. version: 1:11.1-1ubuntu7.2 OS: Ubuntu 18.04.2 LTS System uptime: 11 days Desktop: GNOME pmap output: $ pmap 25499 25499: /usr/bin/pulseaudio --start --log-target=syslog 55e3bb805000 84K r-x-- pulseaudio 55e3bba1a000 4K r pulseaudio 55e3bba1b000 4K rw--- pulseaudio 55e3bd1b9000132K rw--- [ anon ] 55e3bd1da000 3671036K rw--- [ anon ] 7f705c00 65536K rw-s- memfd:pulseaudio (deleted) 7f706000 65536K rw-s- memfd:pulseaudio (deleted) 7f706400 65536K rw-s- memfd:pulseaudio (deleted) 7f706800 65536K rw-s- memfd:pulseaudio (deleted) 7f706c00 65536K rw-s- memfd:pulseaudio (deleted) 7f707000 65536K rw-s- memfd:pulseaudio (deleted) 7f707400 65536K rw-s- memfd:pulseaudio (deleted) 7f707800 65536K rw-s- memfd:pulseaudio (deleted) 7f707c00 65536K rw-s- memfd:pulseaudio (deleted) 7f708000 65536K rw-s- memfd:pulseaudio (deleted) 7f708400 65536K rw-s- memfd:pulseaudio (deleted) 7f708800 65536K rw-s- memfd:pulseaudio (deleted) 7f70bc00 65536K rw-s- memfd:pulseaudio (deleted) 7f70c000 65536K rw-s- memfd:pulseaudio (deleted) 7f70c400 65536K rw-s- memfd:pulseaudio (deleted) 7f70c800 65536K rw-s- memfd:pulseaudio (deleted) 7f70ec00 65536K rw-s- memfd:pulseaudio (deleted) 7f70f000 65536K rw-s- memfd:pulseaudio (deleted) 7f70f400 65536K rw-s- memfd:pulseaudio (deleted) 7f70f800 65536K rw-s- memfd:pulseaudio (deleted) 7f70fc00 65536K rw-s- memfd:pulseaudio (deleted) 7f71 65536K rw-s- memfd:pulseaudio (deleted) 7f710400 65536K rw-s- memfd:pulseaudio (deleted) 7f710800 65536K rw-s- memfd:pulseaudio (deleted) 7f710c00 65536K rw-s- memfd:pulseaudio (deleted) 7f711000 65536K rw-s- memfd:pulseaudio (deleted) 7f711400 65536K rw-s- memfd:pulseaudio (deleted) 7f711800 65536K rw-s- memfd:pulseaudio (deleted) 7f711c00172K rw--- [ anon ] 7f711c02b000 65364K - [ anon ] 7f7120957000 24K r-x-- libuuid.so.1.3.0 7f712095d000 2044K - libuuid.so.1.3.0 7f7120b5c000 4K r libuuid.so.1.3.0 7f7120b5d000 4K rw--- libuuid.so.1.3.0 7f7120b5e000 28K r-x-- libSM.so.6.0.1 7f7120b65000 2044K - libSM.so.6.0.1 7f7120d64000 4K r libSM.so.6.0.1 7f7120d65000 4K rw--- libSM.so.6.0.1 7f7120d66000 92K r-x-- libICE.so.6.3.0 7f7120d7d000 2044K - libICE.so.6.3.0 7f7120f7c000 4K r libICE.so.6.3.0 7f7120f7d000 4K rw--- libICE.so.6.3.0 7f7120f7e000 12K rw--- [ anon ] 7f7120f81000 8K r-x-- module-x11-xsmp.so 7f7120f83000 2048K - module-x11-xsmp.so 7f7121183000 4K r module-x11-xsmp.so 7f7121184000 4K rw--- module-x11-xsmp.so 7f7121185000 68K r-x-- libXext.so.6.4.0 7f7121196000 2044K - libXext.so.6.4.0 7f7121395000 4K r libXext.so.6.4.0 7f7121396000 4K rw--- libXext.so.6.4.0 7f7121397000 20K r-x-- libXtst.so.6.1.0 7f712139c000 2044K - libXtst.so.6.1.0 7f712159b000 4K r libXtst.so.6.1.0 7f712159c000 4K rw--- libXtst.so.6.1.0 7f712159d000 8K r-x-- module-x11-cork-request.so 7f712159f000 2044K - module-x11-cork-request.so 7f712179e000 4K r module-x11-cork-request.so 7f712179f000 4K rw--- module-x11-cork-request.so 7f71217a 8K r-x-- module-x11-bell.so 7f71217a2000 2044K - module-x11-bell.so 7f71219a1000 4K r module-x11-bell.so 7f71219a2000 4K rw--- module-x11-bell.so 7f71219a3000 12K r-x-- module-x11-publish.so 7f71219a6000 2044K - module-x11-publish.so 7f7121ba5000 4K r module-x11-publish.so 7f7121ba6000 4K rw--- module-x11-publish.so 7f7121ba7000 8K r-x-- libcli.so 7f7121ba9000 2044K
[Touch-packages] [Bug 1834666] Re: X didn't use hardware acceleration for your system
This is a strange one. It appears you have an Intel GPU (I assume because the CPU is model i7-8700). And the Linux kernel can find it on the bus: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller]) but the kernel is also failing to load a driver for it, so there are no /dev/dri* files for X to use. ** Summary changed: - X didn't use hardware acceleration for your system + Intel GPU present but i915 not loaded. Stuck in low resolution. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1834666 Title: Intel GPU present but i915 not loaded. Stuck in low resolution. Status in linux package in Ubuntu: New Bug description: Your system is providing 3D via software rendering rather than hardware rendering. This is a compatibility mode which should display 3D graphics properly but the performance may be very poor. If the problem you're reporting is related to graphics performance, your real question may be why X didn't use hardware acceleration for your system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None CurrentDesktop: KDE Date: Fri Jun 28 16:28:41 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=4e297ab3-b0cc-4dcf-ac56-953597c77fa0 ro Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: Default string dmi.board.name: TUF B360-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd03/23/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB360-PLUSGAMING:rvrRev1.xx: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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834666/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
Yes, there is a power optimization in the 19.04. please close that optimization by editing the /etc/modprobe.d/alsa- base.conf add options snd-hda-intel power_save=0 then reboot. -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in alsa-driver package in Ubuntu: New Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833793/+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 1834794] Re: Uses too much memory (6Gbyte process)
Thanks for the reply. It is 3.7G byte mapped hardware memory, not just virtual. Here's the output you asked: $ cat status Name: pulseaudio Umask: 0022 State: S (sleeping) Tgid: 25499 Ngid: 0 Pid:25499 PPid: 1 TracerPid: 0 Uid:1000100010001000 Gid:1000100010001000 FDSize: 128 Groups: 4 24 27 30 46 116 126 129 131 1000 1001 64055 NStgid: 25499 NSpid: 25499 NSpgid: 25498 NSsid: 25498 VmPeak: 7469272 kB VmSize: 7207128 kB VmLck: 0 kB VmPin: 0 kB VmHWM: 3694032 kB VmRSS: 3694032 kB RssAnon: 3672980 kB RssFile:9136 kB RssShmem: 11916 kB VmData: 3688908 kB VmStk: 132 kB VmExe:84 kB VmLib: 14096 kB VmPTE: 7792 kB VmSwap:0 kB HugetlbPages: 0 kB CoreDumping:0 Threads:3 SigQ: 0/95728 SigPnd: ShdPnd: SigBlk: SigIgn: 00381000 SigCgt: 000180004a43 CapInh: CapPrm: CapEff: CapBnd: 003f CapAmb: NoNewPrivs: 0 Seccomp:0 Speculation_Store_Bypass: thread vulnerable Cpus_allowed: f Cpus_allowed_list: 0-3 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0001 Mems_allowed_list: 0 voluntary_ctxt_switches:64080270 nonvoluntary_ctxt_switches: 3402344 -- 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/1834794 Title: Uses too much memory (6Gbyte process) Status in pulseaudio package in Ubuntu: Incomplete Bug description: So, my pulseaudio process is 6Gbyte large, 3.5Gb of that resident in memory. version: 1:11.1-1ubuntu7.2 OS: Ubuntu 18.04.2 LTS System uptime: 11 days Desktop: GNOME pmap output: $ pmap 25499 25499: /usr/bin/pulseaudio --start --log-target=syslog 55e3bb805000 84K r-x-- pulseaudio 55e3bba1a000 4K r pulseaudio 55e3bba1b000 4K rw--- pulseaudio 55e3bd1b9000132K rw--- [ anon ] 55e3bd1da000 3671036K rw--- [ anon ] 7f705c00 65536K rw-s- memfd:pulseaudio (deleted) 7f706000 65536K rw-s- memfd:pulseaudio (deleted) 7f706400 65536K rw-s- memfd:pulseaudio (deleted) 7f706800 65536K rw-s- memfd:pulseaudio (deleted) 7f706c00 65536K rw-s- memfd:pulseaudio (deleted) 7f707000 65536K rw-s- memfd:pulseaudio (deleted) 7f707400 65536K rw-s- memfd:pulseaudio (deleted) 7f707800 65536K rw-s- memfd:pulseaudio (deleted) 7f707c00 65536K rw-s- memfd:pulseaudio (deleted) 7f708000 65536K rw-s- memfd:pulseaudio (deleted) 7f708400 65536K rw-s- memfd:pulseaudio (deleted) 7f708800 65536K rw-s- memfd:pulseaudio (deleted) 7f70bc00 65536K rw-s- memfd:pulseaudio (deleted) 7f70c000 65536K rw-s- memfd:pulseaudio (deleted) 7f70c400 65536K rw-s- memfd:pulseaudio (deleted) 7f70c800 65536K rw-s- memfd:pulseaudio (deleted) 7f70ec00 65536K rw-s- memfd:pulseaudio (deleted) 7f70f000 65536K rw-s- memfd:pulseaudio (deleted) 7f70f400 65536K rw-s- memfd:pulseaudio (deleted) 7f70f800 65536K rw-s- memfd:pulseaudio (deleted) 7f70fc00 65536K rw-s- memfd:pulseaudio (deleted) 7f71 65536K rw-s- memfd:pulseaudio (deleted) 7f710400 65536K rw-s- memfd:pulseaudio (deleted) 7f710800 65536K rw-s- memfd:pulseaudio (deleted) 7f710c00 65536K rw-s- memfd:pulseaudio (deleted) 7f711000 65536K rw-s- memfd:pulseaudio (deleted) 7f711400 65536K rw-s- memfd:pulseaudio (deleted) 7f711800 65536K rw-s- memfd:pulseaudio (deleted) 7f711c00172K rw--- [ anon ] 7f711c02b000 65364K - [ anon ] 7f7120957000 24K r-x-- libuuid.so.1.3.0 7f712095d000 2044K - libuuid.so.1.3.0 7f7120b5c000 4K r libuuid.so.1.3.0 7f7120b5d000 4K rw--- libuuid.so.1.3.0 7f7120b5e000 28K r-x-- libSM.so.6.0.1 7f7120b65000 2044K - libSM.so.6.0.1 7f7120d64000 4K r libSM.so.6.0.1 7f7120d65000 4K rw--- libSM.so.6.0.1 7f7120d66000 92K r-x-- libICE.so.6.3.0 7f7120d7d000 2044K - libICE.so.6.3.0 7f7120f7c000 4K r libICE.so.6.3.0 7f7120f7d000 4K rw--- libICE.so.6.3.0 7f7120f7e000 12K rw--- [ anon ] 7f7120f81000 8K r-x-- module-x11-xsmp.so 7f7120f83000 2048K - module-x11-xsmp.so 7f7121183000 4K r module-x11-xsmp.so
[Touch-packages] [Bug 1834794] Re: Uses too much memory (6Gbyte process)
Thanks for the bug report. 'pmap' displays virtual memory (address space), which is mostly not real memory. Please attach a copy of your /proc/PID/status file. The important field that affects machine performance is VmRSS, and VmData tells you the amount of regular memory allocations. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1834794 Title: Uses too much memory (6Gbyte process) Status in pulseaudio package in Ubuntu: Incomplete Bug description: So, my pulseaudio process is 6Gbyte large, 3.5Gb of that resident in memory. version: 1:11.1-1ubuntu7.2 OS: Ubuntu 18.04.2 LTS System uptime: 11 days Desktop: GNOME pmap output: $ pmap 25499 25499: /usr/bin/pulseaudio --start --log-target=syslog 55e3bb805000 84K r-x-- pulseaudio 55e3bba1a000 4K r pulseaudio 55e3bba1b000 4K rw--- pulseaudio 55e3bd1b9000132K rw--- [ anon ] 55e3bd1da000 3671036K rw--- [ anon ] 7f705c00 65536K rw-s- memfd:pulseaudio (deleted) 7f706000 65536K rw-s- memfd:pulseaudio (deleted) 7f706400 65536K rw-s- memfd:pulseaudio (deleted) 7f706800 65536K rw-s- memfd:pulseaudio (deleted) 7f706c00 65536K rw-s- memfd:pulseaudio (deleted) 7f707000 65536K rw-s- memfd:pulseaudio (deleted) 7f707400 65536K rw-s- memfd:pulseaudio (deleted) 7f707800 65536K rw-s- memfd:pulseaudio (deleted) 7f707c00 65536K rw-s- memfd:pulseaudio (deleted) 7f708000 65536K rw-s- memfd:pulseaudio (deleted) 7f708400 65536K rw-s- memfd:pulseaudio (deleted) 7f708800 65536K rw-s- memfd:pulseaudio (deleted) 7f70bc00 65536K rw-s- memfd:pulseaudio (deleted) 7f70c000 65536K rw-s- memfd:pulseaudio (deleted) 7f70c400 65536K rw-s- memfd:pulseaudio (deleted) 7f70c800 65536K rw-s- memfd:pulseaudio (deleted) 7f70ec00 65536K rw-s- memfd:pulseaudio (deleted) 7f70f000 65536K rw-s- memfd:pulseaudio (deleted) 7f70f400 65536K rw-s- memfd:pulseaudio (deleted) 7f70f800 65536K rw-s- memfd:pulseaudio (deleted) 7f70fc00 65536K rw-s- memfd:pulseaudio (deleted) 7f71 65536K rw-s- memfd:pulseaudio (deleted) 7f710400 65536K rw-s- memfd:pulseaudio (deleted) 7f710800 65536K rw-s- memfd:pulseaudio (deleted) 7f710c00 65536K rw-s- memfd:pulseaudio (deleted) 7f711000 65536K rw-s- memfd:pulseaudio (deleted) 7f711400 65536K rw-s- memfd:pulseaudio (deleted) 7f711800 65536K rw-s- memfd:pulseaudio (deleted) 7f711c00172K rw--- [ anon ] 7f711c02b000 65364K - [ anon ] 7f7120957000 24K r-x-- libuuid.so.1.3.0 7f712095d000 2044K - libuuid.so.1.3.0 7f7120b5c000 4K r libuuid.so.1.3.0 7f7120b5d000 4K rw--- libuuid.so.1.3.0 7f7120b5e000 28K r-x-- libSM.so.6.0.1 7f7120b65000 2044K - libSM.so.6.0.1 7f7120d64000 4K r libSM.so.6.0.1 7f7120d65000 4K rw--- libSM.so.6.0.1 7f7120d66000 92K r-x-- libICE.so.6.3.0 7f7120d7d000 2044K - libICE.so.6.3.0 7f7120f7c000 4K r libICE.so.6.3.0 7f7120f7d000 4K rw--- libICE.so.6.3.0 7f7120f7e000 12K rw--- [ anon ] 7f7120f81000 8K r-x-- module-x11-xsmp.so 7f7120f83000 2048K - module-x11-xsmp.so 7f7121183000 4K r module-x11-xsmp.so 7f7121184000 4K rw--- module-x11-xsmp.so 7f7121185000 68K r-x-- libXext.so.6.4.0 7f7121196000 2044K - libXext.so.6.4.0 7f7121395000 4K r libXext.so.6.4.0 7f7121396000 4K rw--- libXext.so.6.4.0 7f7121397000 20K r-x-- libXtst.so.6.1.0 7f712139c000 2044K - libXtst.so.6.1.0 7f712159b000 4K r libXtst.so.6.1.0 7f712159c000 4K rw--- libXtst.so.6.1.0 7f712159d000 8K r-x-- module-x11-cork-request.so 7f712159f000 2044K - module-x11-cork-request.so 7f712179e000 4K r module-x11-cork-request.so 7f712179f000 4K rw--- module-x11-cork-request.so 7f71217a 8K r-x-- module-x11-bell.so 7f71217a2000 2044K - module-x11-bell.so 7f71219a1000 4K r module-x11-bell.so 7f71219a2000 4K rw--- module-x11-bell.so 7f71219a3000 12K r-x-- module-x11-publish.so 7f71219a6000 2044K - module-x11-publish.so 7f7121ba5000 4K r module-x11-publish.so 7f7121ba6000 4K rw--- module-x11-publish.so 7f7121ba7000 8K r-x-- libcli.so 7f7121ba9000 2044K - libcli.so 7f7121da8000 4K r libcli.so 7f7121da9000 4K rw---
[Touch-packages] [Bug 1834795] [NEW] xubuntu ethernet does not reconnect unless computer restarted, after power off/on modem or manually off/on "enable networking"
Public bug reported: Xubuntu 19.04, 64bit, encrypted drive, using a desktop computer with ethernet to connect. Connects fine. Use openvpn also (from terminal). When the modem is turned off and on, or when the modem remains on but the ethernet connection is disabled (by unticking) and then ticking again "enable networking" in the applet taskbar, the connection does not re-establish. This is irregardless of the vpn, which even if i turn off, will not affect the lack of reconnection. If i ping bing.com, after trying to reconnect, I get back one response, but no multiple responses. ping bing.com PING bing.com (204.79.197.200) 56(84) bytes of data. This is slightly different to no connection being present, as then I would not even get back a single ping: "ping: bing.com: Temporary failure in name resolution" The only way to get a connection back is by restarting the system. And then it works fine. This is not an issue for ubuntu mate 19.04. The reconnection works fine, with no restart required. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: ethernet linux network-manager -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1834795 Title: xubuntu ethernet does not reconnect unless computer restarted, after power off/on modem or manually off/on "enable networking" Status in network-manager package in Ubuntu: New Bug description: Xubuntu 19.04, 64bit, encrypted drive, using a desktop computer with ethernet to connect. Connects fine. Use openvpn also (from terminal). When the modem is turned off and on, or when the modem remains on but the ethernet connection is disabled (by unticking) and then ticking again "enable networking" in the applet taskbar, the connection does not re-establish. This is irregardless of the vpn, which even if i turn off, will not affect the lack of reconnection. If i ping bing.com, after trying to reconnect, I get back one response, but no multiple responses. ping bing.com PING bing.com (204.79.197.200) 56(84) bytes of data. This is slightly different to no connection being present, as then I would not even get back a single ping: "ping: bing.com: Temporary failure in name resolution" The only way to get a connection back is by restarting the system. And then it works fine. This is not an issue for ubuntu mate 19.04. The reconnection works fine, with no restart required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1834795/+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 1834794] Re: Uses too much memory (6Gbyte process)
Running with 'pmap -x' gives this info: $ pmap -x 25499 25499: /usr/bin/pulseaudio --start --log-target=syslog Address Kbytes RSS Dirty Mode Mapping 55e3bb805000 84 84 0 r-x-- pulseaudio 55e3bb805000 0 0 0 r-x-- pulseaudio 55e3bba1a000 4 4 4 r pulseaudio 55e3bba1a000 0 0 0 r pulseaudio 55e3bba1b000 4 4 4 rw--- pulseaudio 55e3bba1b000 0 0 0 rw--- pulseaudio 55e3bd1b9000 132 132 132 rw--- [ anon ] 55e3bd1b9000 0 0 0 rw--- [ anon ] 55e3bd1da000 3671036 3671036 3671036 rw--- [ anon ] 55e3bd1da000 0 0 0 rw--- [ anon ] ... -- 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/1834794 Title: Uses too much memory (6Gbyte process) Status in pulseaudio package in Ubuntu: New Bug description: So, my pulseaudio process is 6Gbyte large, 3.5Gb of that resident in memory. version: 1:11.1-1ubuntu7.2 OS: Ubuntu 18.04.2 LTS System uptime: 11 days Desktop: GNOME pmap output: $ pmap 25499 25499: /usr/bin/pulseaudio --start --log-target=syslog 55e3bb805000 84K r-x-- pulseaudio 55e3bba1a000 4K r pulseaudio 55e3bba1b000 4K rw--- pulseaudio 55e3bd1b9000132K rw--- [ anon ] 55e3bd1da000 3671036K rw--- [ anon ] 7f705c00 65536K rw-s- memfd:pulseaudio (deleted) 7f706000 65536K rw-s- memfd:pulseaudio (deleted) 7f706400 65536K rw-s- memfd:pulseaudio (deleted) 7f706800 65536K rw-s- memfd:pulseaudio (deleted) 7f706c00 65536K rw-s- memfd:pulseaudio (deleted) 7f707000 65536K rw-s- memfd:pulseaudio (deleted) 7f707400 65536K rw-s- memfd:pulseaudio (deleted) 7f707800 65536K rw-s- memfd:pulseaudio (deleted) 7f707c00 65536K rw-s- memfd:pulseaudio (deleted) 7f708000 65536K rw-s- memfd:pulseaudio (deleted) 7f708400 65536K rw-s- memfd:pulseaudio (deleted) 7f708800 65536K rw-s- memfd:pulseaudio (deleted) 7f70bc00 65536K rw-s- memfd:pulseaudio (deleted) 7f70c000 65536K rw-s- memfd:pulseaudio (deleted) 7f70c400 65536K rw-s- memfd:pulseaudio (deleted) 7f70c800 65536K rw-s- memfd:pulseaudio (deleted) 7f70ec00 65536K rw-s- memfd:pulseaudio (deleted) 7f70f000 65536K rw-s- memfd:pulseaudio (deleted) 7f70f400 65536K rw-s- memfd:pulseaudio (deleted) 7f70f800 65536K rw-s- memfd:pulseaudio (deleted) 7f70fc00 65536K rw-s- memfd:pulseaudio (deleted) 7f71 65536K rw-s- memfd:pulseaudio (deleted) 7f710400 65536K rw-s- memfd:pulseaudio (deleted) 7f710800 65536K rw-s- memfd:pulseaudio (deleted) 7f710c00 65536K rw-s- memfd:pulseaudio (deleted) 7f711000 65536K rw-s- memfd:pulseaudio (deleted) 7f711400 65536K rw-s- memfd:pulseaudio (deleted) 7f711800 65536K rw-s- memfd:pulseaudio (deleted) 7f711c00172K rw--- [ anon ] 7f711c02b000 65364K - [ anon ] 7f7120957000 24K r-x-- libuuid.so.1.3.0 7f712095d000 2044K - libuuid.so.1.3.0 7f7120b5c000 4K r libuuid.so.1.3.0 7f7120b5d000 4K rw--- libuuid.so.1.3.0 7f7120b5e000 28K r-x-- libSM.so.6.0.1 7f7120b65000 2044K - libSM.so.6.0.1 7f7120d64000 4K r libSM.so.6.0.1 7f7120d65000 4K rw--- libSM.so.6.0.1 7f7120d66000 92K r-x-- libICE.so.6.3.0 7f7120d7d000 2044K - libICE.so.6.3.0 7f7120f7c000 4K r libICE.so.6.3.0 7f7120f7d000 4K rw--- libICE.so.6.3.0 7f7120f7e000 12K rw--- [ anon ] 7f7120f81000 8K r-x-- module-x11-xsmp.so 7f7120f83000 2048K - module-x11-xsmp.so 7f7121183000 4K r module-x11-xsmp.so 7f7121184000 4K rw--- module-x11-xsmp.so 7f7121185000 68K r-x-- libXext.so.6.4.0 7f7121196000 2044K - libXext.so.6.4.0 7f7121395000 4K r libXext.so.6.4.0 7f7121396000 4K rw--- libXext.so.6.4.0 7f7121397000 20K r-x-- libXtst.so.6.1.0 7f712139c000 2044K - libXtst.so.6.1.0 7f712159b000 4K r libXtst.so.6.1.0 7f712159c000 4K rw--- libXtst.so.6.1.0 7f712159d000 8K r-x-- module-x11-cork-request.so 7f712159f000 2044K - module-x11-cork-request.so 7f712179e000 4K r module-x11-cork-request.so 7f712179f000 4K rw--- module-x11-cork-request.so 7f71217a 8K r-x-- module-x11-bell.so 7f71217a2000 2044K - module-x11-bell.so 7f71219a1000 4K r module-x11-bell.so 7f71219a2000 4K rw--- module-x11-bell.so
[Touch-packages] [Bug 1834794] [NEW] Uses too much memory (6Gbyte process)
Public bug reported: So, my pulseaudio process is 6Gbyte large, 3.5Gb of that resident in memory. version: 1:11.1-1ubuntu7.2 OS: Ubuntu 18.04.2 LTS System uptime: 11 days Desktop: GNOME pmap output: $ pmap 25499 25499: /usr/bin/pulseaudio --start --log-target=syslog 55e3bb805000 84K r-x-- pulseaudio 55e3bba1a000 4K r pulseaudio 55e3bba1b000 4K rw--- pulseaudio 55e3bd1b9000132K rw--- [ anon ] 55e3bd1da000 3671036K rw--- [ anon ] 7f705c00 65536K rw-s- memfd:pulseaudio (deleted) 7f706000 65536K rw-s- memfd:pulseaudio (deleted) 7f706400 65536K rw-s- memfd:pulseaudio (deleted) 7f706800 65536K rw-s- memfd:pulseaudio (deleted) 7f706c00 65536K rw-s- memfd:pulseaudio (deleted) 7f707000 65536K rw-s- memfd:pulseaudio (deleted) 7f707400 65536K rw-s- memfd:pulseaudio (deleted) 7f707800 65536K rw-s- memfd:pulseaudio (deleted) 7f707c00 65536K rw-s- memfd:pulseaudio (deleted) 7f708000 65536K rw-s- memfd:pulseaudio (deleted) 7f708400 65536K rw-s- memfd:pulseaudio (deleted) 7f708800 65536K rw-s- memfd:pulseaudio (deleted) 7f70bc00 65536K rw-s- memfd:pulseaudio (deleted) 7f70c000 65536K rw-s- memfd:pulseaudio (deleted) 7f70c400 65536K rw-s- memfd:pulseaudio (deleted) 7f70c800 65536K rw-s- memfd:pulseaudio (deleted) 7f70ec00 65536K rw-s- memfd:pulseaudio (deleted) 7f70f000 65536K rw-s- memfd:pulseaudio (deleted) 7f70f400 65536K rw-s- memfd:pulseaudio (deleted) 7f70f800 65536K rw-s- memfd:pulseaudio (deleted) 7f70fc00 65536K rw-s- memfd:pulseaudio (deleted) 7f71 65536K rw-s- memfd:pulseaudio (deleted) 7f710400 65536K rw-s- memfd:pulseaudio (deleted) 7f710800 65536K rw-s- memfd:pulseaudio (deleted) 7f710c00 65536K rw-s- memfd:pulseaudio (deleted) 7f711000 65536K rw-s- memfd:pulseaudio (deleted) 7f711400 65536K rw-s- memfd:pulseaudio (deleted) 7f711800 65536K rw-s- memfd:pulseaudio (deleted) 7f711c00172K rw--- [ anon ] 7f711c02b000 65364K - [ anon ] 7f7120957000 24K r-x-- libuuid.so.1.3.0 7f712095d000 2044K - libuuid.so.1.3.0 7f7120b5c000 4K r libuuid.so.1.3.0 7f7120b5d000 4K rw--- libuuid.so.1.3.0 7f7120b5e000 28K r-x-- libSM.so.6.0.1 7f7120b65000 2044K - libSM.so.6.0.1 7f7120d64000 4K r libSM.so.6.0.1 7f7120d65000 4K rw--- libSM.so.6.0.1 7f7120d66000 92K r-x-- libICE.so.6.3.0 7f7120d7d000 2044K - libICE.so.6.3.0 7f7120f7c000 4K r libICE.so.6.3.0 7f7120f7d000 4K rw--- libICE.so.6.3.0 7f7120f7e000 12K rw--- [ anon ] 7f7120f81000 8K r-x-- module-x11-xsmp.so 7f7120f83000 2048K - module-x11-xsmp.so 7f7121183000 4K r module-x11-xsmp.so 7f7121184000 4K rw--- module-x11-xsmp.so 7f7121185000 68K r-x-- libXext.so.6.4.0 7f7121196000 2044K - libXext.so.6.4.0 7f7121395000 4K r libXext.so.6.4.0 7f7121396000 4K rw--- libXext.so.6.4.0 7f7121397000 20K r-x-- libXtst.so.6.1.0 7f712139c000 2044K - libXtst.so.6.1.0 7f712159b000 4K r libXtst.so.6.1.0 7f712159c000 4K rw--- libXtst.so.6.1.0 7f712159d000 8K r-x-- module-x11-cork-request.so 7f712159f000 2044K - module-x11-cork-request.so 7f712179e000 4K r module-x11-cork-request.so 7f712179f000 4K rw--- module-x11-cork-request.so 7f71217a 8K r-x-- module-x11-bell.so 7f71217a2000 2044K - module-x11-bell.so 7f71219a1000 4K r module-x11-bell.so 7f71219a2000 4K rw--- module-x11-bell.so 7f71219a3000 12K r-x-- module-x11-publish.so 7f71219a6000 2044K - module-x11-publish.so 7f7121ba5000 4K r module-x11-publish.so 7f7121ba6000 4K rw--- module-x11-publish.so 7f7121ba7000 8K r-x-- libcli.so 7f7121ba9000 2044K - libcli.so 7f7121da8000 4K r libcli.so 7f7121da9000 4K rw--- libcli.so 7f7121daa000 8K r-x-- libprotocol-cli.so 7f7121dac000 2044K - libprotocol-cli.so 7f7121fab000 4K r libprotocol-cli.so 7f7121fac000 4K rw--- libprotocol-cli.so 7f7121fad000 8K r-x-- module-cli-protocol-unix.so 7f7121faf000 2044K - module-cli-protocol-unix.so 7f71221ae000 4K r module-cli-protocol-unix.so 7f71221af000 4K rw--- module-cli-protocol-unix.so 7f71221b 24K r-x-- module-filter-apply.so 7f71221b6000 2044K - module-filter-apply.so 7f71223b5000 4K r module-filter-apply.so 7f71223b6000 4K rw--- module-filter-apply.so 7f71223b7000 12K r-x-- module-filter-heuristics.so 7f71223ba000 2044K - module-filter-heuristics.so 7f71225b9000 4K r
[Touch-packages] [Bug 1391779] Re: curl not build with metalink support
As a workaround now you may install and use the curl-metalink snap for downloading Metalinks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1391779 Title: curl not build with metalink support Status in curl package in Ubuntu: Triaged Status in curl package in Debian: New Bug description: The manpage for curl talks about having support for the --metalink flag but trying to use it in Ubuntu 14.04 fails with the following warning: Warning: --metalink option is ignored because the binary is built without the Warning: Metalink support. Can we get curl built with metalink support please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1391779/+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 1413283] Re: "Set as default" is absent from "Open with.." context menu
** Changed in: hundredpapercuts Status: New => Confirmed ** Changed in: hundredpapercuts Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1413283 Title: "Set as default" is absent from "Open with.." context menu Status in One Hundred Papercuts: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Question http://askubuntu.com/questions/90214/how-to-set-default- program gets 35k+ views. I suspect much of it is because there is no intuitive way to set a file association. See the comment under accepted answer: Right-click -> open with -> other application DOES NOT show "Set as default"... Right-click -> Properties -> Open With DOES show "Set as default" I was looking for "Set as default" in "Open with.." menu myself . To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1413283/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
It literally doesn't go away, only reliable way is playing something 24/7 just to get Ubuntu to shut the f*** up. -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in alsa-driver package in Ubuntu: New Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833793/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
Is this some kind of new power optimization to constantly reinitialize my sound card? -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in alsa-driver package in Ubuntu: New Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833793/+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 1834784] [NEW] Xorg freeze
Public bug reported: I can't provide much in the way of detail as the freezes are seemingly random. They happen with different software being used. Release: Ubuntu 18.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 30 17:40:47 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Nitro+ Radeon RX 580 4GB [1da2:e366] InstallationDate: Installed on 2019-06-30 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=71fe103c-b7c8-4fbd-970d-39d7569306ab ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4011 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.:bvr4011:bd04/19/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.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1834784 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I can't provide much in the way of detail as the freezes are seemingly random. They happen with different software being used. Release: Ubuntu 18.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 30 17:40:47 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Nitro+ Radeon RX 580 4GB [1da2:e366] InstallationDate: Installed on 2019-06-30 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=71fe103c-b7c8-4fbd-970d-39d7569306ab ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4011 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
[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
Mortimer, it's still available at the Google cache: https://webcache.googleusercontent.com/search?https://webcache.googleusercontent.com/search?q=cache:Ulh1YXwMuK8J:https://dev.getsol.us/T5224 It appears that the fix there addresses the same file and the same line in that file. However, the lines are simply being deleted there & it breaks Bluetooth so I wouldn't go that route (though at the time I did due to not knowing any better). They are also placing it at a different location, /etc/udev/rules.d/, and I don't know the significance of that. And to address what others are saying, yes, hand editing a system file (and one, at that, which is headed by the comment line "# do not edit this file, it will be overwritten on update") is not an optimal solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+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 1827498] Re: Geoclue 2 very high memory usage
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: geoclue (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to geoclue in Ubuntu. https://bugs.launchpad.net/bugs/1827498 Title: Geoclue 2 very high memory usage Status in geoclue package in Ubuntu: Confirmed Bug description: After geoclue 2 running at high CPU for some minutes I found CPU usage had dropped to zero but geoclue was still hogging a whopping 11GB of memory (the PC has 16GB). I stopped the geoclue service to recover the memory. Kubuntu 18.04 $ apt-cache policy geoclue-2.0 geoclue-2.0: Installed: 2.4.7-1ubuntu1 Candidate: 2.4.7-1ubuntu1 Version table: *** 2.4.7-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Happy to provide other info on request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue/+bug/1827498/+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 1834782] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1834782/+attachment/5274267/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in alsa-driver package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-hwe package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834782/+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 1834782] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1834782/+attachment/5274268/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in alsa-driver package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-hwe package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834782/+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 1834782] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1834782/+attachment/5274266/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in alsa-driver package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-hwe package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834782/+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 1834782] Re: ASUS Zenbook UX433FN: sound stops working after a couple of seconds
apport information ** Tags added: apport-collected bionic third-party-packages wayland- session ** Description changed: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: mmm 28065 F pulseaudio + CurrentDesktop: KDE + CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted + Dependencies: + + DistroRelease: KDE neon 18.04 + InstallationDate: Installed on 2012-12-23 (2380 days ago) + InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) + Package: pulseaudio + PackageArchitecture: all + ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 + Tags: bionic wayland-session third-party-packages wayland-session + Uname: Linux 4.18.0-25-generic x86_64 + UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm libvirtd lpadmin netdev plugdev sudo video + _MarkForUpload: True + dmi.bios.date: 04/24/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: UX433FN.306 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: UX433FN + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: ZenBook + dmi.product.name: ZenBook UX433FN_UX433FN + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1834782/+attachment/5274265/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in alsa-driver package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-hwe package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor:
[Touch-packages] [Bug 1834782] Re: ASUS Zenbook UX433FN: sound stops working after a couple of seconds
I am not sure if this is a kernel/FW issue, as the soundcard is recognized and the sound playes at first. On the other hand there were not changes/updates to alsa,pulseaudio and the sound used to work ok before. These problems started to appear cca a month ago(?) but usually "some trick" made it work again (I didn't identify exactly what), like ++volume key after the sound stoped working, this does not help anymore. -- 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/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in alsa-driver package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-hwe package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834782/+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 1834782] [NEW] ASUS Zenbook UX433FN: sound stops working after a couple of seconds
Public bug reported: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-edge (Ubuntu) Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic third-party-packages wayland-session ** Also affects: linux-hwe-edge (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Also affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in alsa-driver package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-hwe package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session
[Touch-packages] [Bug 1807709] Re: dbus always crashes at session start (on wayland)
Same here, Ubuntu 19.04, not on wayland. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1807709 Title: dbus always crashes at session start (on wayland) Status in dbus package in Ubuntu: Confirmed Bug description: When you login in ubuntu 18.10 using gnome shell and wayland, dbus always crashes and you are welcomed with a dialog to report the crash. Looking into the file `/var/crash/_usr_bin_dbus-daemon.1000.crash` one can see that there is antoher bug, previoulsy reported as #1591548 (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1591548) So may be the bug report is never sent, either ? /var/crash/_usr_bin_dbus-daemon.1000.crash content is: ProblemType: Crash Architecture: amd64 Date: Sun Dec 9 11:16:22 2018 DistroRelease: Ubuntu 18.10 ExecutablePath: /usr/bin/dbus-daemon ExecutableTimestamp: 1536206167 ProcCmdline: /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only ProcCwd: /home/solstice ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcMaps: 55c9bfc7a000-55c9bfc83000 r--p 08:07 787824 /usr/bin/dbus-daemon 55c9bfc83000-55c9bfca5000 r-xp 9000 08:07 787824 /usr/bin/dbus-daemon 55c9bfca5000-55c9bfcb3000 r--p 0002b000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb3000-55c9bfcb5000 r--p 00038000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb5000-55c9bfcb6000 rw-p 0003a000 08:07 787824 /usr/bin/dbus-daemon 55c9c1bd8000-55c9c1f1e000 rw-p 00:00 0 [heap] 7eff0278c000-7eff02792000 r--p 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff02792000-7eff027bd000 r-xp 6000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027bd000-7eff027cc000 r--p 00031000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cc000-7eff027cf000 r--p 0003f000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cf000-7eff027d rw-p 00042000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027d-7eff027d1000 rw-p 00:00 0 7eff027d1000-7eff027d4000 r--p 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027d4000-7eff027db000 r-xp 3000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027db000-7eff027de000 r--p a000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027de000-7eff027df000 r--p c000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027df000-7eff027e rw-p d000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027e-7eff027e6000 rw-p 00:00 0 7eff027e6000-7eff027ea000 r--p 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ea000-7eff027f8000 r-xp 4000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027f8000-7eff027fd000 r--p 00012000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fd000-7eff027fe000 r--p 00016000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fe000-7eff027ff000 rw-p 00017000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ff000-7eff02801000 rw-p 00:00 0 7eff02801000-7eff02803000 r--p 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff02803000-7eff0280b000 r-xp 2000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280b000-7eff0280d000 r--p a000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280d000-7eff0280e000 r--p b000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280e000-7eff0280f000 rw-p c000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280f000-7eff02811000 r--p 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02811000-7eff02817000 r-xp 2000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02817000-7eff02818000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02818000-7eff02819000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02819000-7eff0281a000 rw-p 9000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff0281a000-7eff0281f000 rw-p 00:00 0
[Touch-packages] [Bug 1807709] Re: dbus always crashes at session start (on wayland)
Here's crash report. Ubuntu 19.04, not on wayland. ** Attachment added: "Crash report" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1807709/+attachment/5274264/+files/_usr_bin_dbus-daemon.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1807709 Title: dbus always crashes at session start (on wayland) Status in dbus package in Ubuntu: Confirmed Bug description: When you login in ubuntu 18.10 using gnome shell and wayland, dbus always crashes and you are welcomed with a dialog to report the crash. Looking into the file `/var/crash/_usr_bin_dbus-daemon.1000.crash` one can see that there is antoher bug, previoulsy reported as #1591548 (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1591548) So may be the bug report is never sent, either ? /var/crash/_usr_bin_dbus-daemon.1000.crash content is: ProblemType: Crash Architecture: amd64 Date: Sun Dec 9 11:16:22 2018 DistroRelease: Ubuntu 18.10 ExecutablePath: /usr/bin/dbus-daemon ExecutableTimestamp: 1536206167 ProcCmdline: /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only ProcCwd: /home/solstice ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcMaps: 55c9bfc7a000-55c9bfc83000 r--p 08:07 787824 /usr/bin/dbus-daemon 55c9bfc83000-55c9bfca5000 r-xp 9000 08:07 787824 /usr/bin/dbus-daemon 55c9bfca5000-55c9bfcb3000 r--p 0002b000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb3000-55c9bfcb5000 r--p 00038000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb5000-55c9bfcb6000 rw-p 0003a000 08:07 787824 /usr/bin/dbus-daemon 55c9c1bd8000-55c9c1f1e000 rw-p 00:00 0 [heap] 7eff0278c000-7eff02792000 r--p 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff02792000-7eff027bd000 r-xp 6000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027bd000-7eff027cc000 r--p 00031000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cc000-7eff027cf000 r--p 0003f000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cf000-7eff027d rw-p 00042000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027d-7eff027d1000 rw-p 00:00 0 7eff027d1000-7eff027d4000 r--p 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027d4000-7eff027db000 r-xp 3000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027db000-7eff027de000 r--p a000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027de000-7eff027df000 r--p c000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027df000-7eff027e rw-p d000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027e-7eff027e6000 rw-p 00:00 0 7eff027e6000-7eff027ea000 r--p 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ea000-7eff027f8000 r-xp 4000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027f8000-7eff027fd000 r--p 00012000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fd000-7eff027fe000 r--p 00016000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fe000-7eff027ff000 rw-p 00017000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ff000-7eff02801000 rw-p 00:00 0 7eff02801000-7eff02803000 r--p 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff02803000-7eff0280b000 r-xp 2000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280b000-7eff0280d000 r--p a000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280d000-7eff0280e000 r--p b000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280e000-7eff0280f000 rw-p c000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280f000-7eff02811000 r--p 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02811000-7eff02817000 r-xp 2000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02817000-7eff02818000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02818000-7eff02819000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so
[Touch-packages] [Bug 1834780] Re: apport should have python3-launchpad in required dependencies
$ apport-collect 1834780 ERROR: The python3-launchpadlib package is not installed. This functionality is not available. ** Summary changed: - apport should have python3-launchpad in required dependencies + apport should have python3-launchpadlib in required dependencies ** Description changed: When asked to report apt-collect , apport is not installed on my system and I was told "apt install apport", so I did and the installation went ok. - Problem: - apport then fails on missing dependency python3-launchpad + Problem: + apport then fails on missing dependency python3-launchpadlib - Workaround: - manually install it through apt. + Workaround: + manually install it through apt. - Solution: - apport should have python3-launchpad in required dependencies. + Solution: + apport should have python3-launchpadlib in required dependencies. ** Tags added: apport-collected bionic third-party-packages wayland- session ** Description changed: When asked to report apt-collect , apport is not installed on my system and I was told "apt install apport", so I did and the installation went ok. Problem: apport then fails on missing dependency python3-launchpadlib Workaround: manually install it through apt. Solution: apport should have python3-launchpadlib in required dependencies. + --- + ProblemType: Bug + ApportLog: + + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + CurrentDesktop: KDE + DistroRelease: KDE neon 18.04 + InstallationDate: Installed on 2012-12-23 (2380 days ago) + InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) + Package: apport 2.20.9-0ubuntu7.6 [origin: Ubuntu] + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8 + Tags: third-party-packages bionic wayland-session + Uname: Linux 5.0.0-20-generic x86_64 + UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm libvirtd lpadmin netdev plugdev sudo video + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1834780 Title: apport should have python3-launchpadlib in required dependencies Status in apport package in Ubuntu: New Bug description: When asked to report apt-collect , apport is not installed on my system and I was told "apt install apport", so I did and the installation went ok. Problem: apport then fails on missing dependency python3-launchpadlib Workaround: manually install it through apt. Solution: apport should have python3-launchpadlib in required dependencies. --- ProblemType: Bug ApportLog: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: apport 2.20.9-0ubuntu7.6 [origin: Ubuntu] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-20-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1834780/+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 1834780] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1834780/+attachment/5274261/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1834780 Title: apport should have python3-launchpadlib in required dependencies Status in apport package in Ubuntu: New Bug description: When asked to report apt-collect , apport is not installed on my system and I was told "apt install apport", so I did and the installation went ok. Problem: apport then fails on missing dependency python3-launchpadlib Workaround: manually install it through apt. Solution: apport should have python3-launchpadlib in required dependencies. --- ProblemType: Bug ApportLog: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: apport 2.20.9-0ubuntu7.6 [origin: Ubuntu] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-20-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1834780/+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 1834780] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1834780/+attachment/5274263/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1834780 Title: apport should have python3-launchpadlib in required dependencies Status in apport package in Ubuntu: New Bug description: When asked to report apt-collect , apport is not installed on my system and I was told "apt install apport", so I did and the installation went ok. Problem: apport then fails on missing dependency python3-launchpadlib Workaround: manually install it through apt. Solution: apport should have python3-launchpadlib in required dependencies. --- ProblemType: Bug ApportLog: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: apport 2.20.9-0ubuntu7.6 [origin: Ubuntu] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-20-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1834780/+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 1834780] [NEW] apport should have python3-launchpadlib in required dependencies
Public bug reported: When asked to report apt-collect , apport is not installed on my system and I was told "apt install apport", so I did and the installation went ok. Problem: apport then fails on missing dependency python3-launchpadlib Workaround: manually install it through apt. Solution: apport should have python3-launchpadlib in required dependencies. --- ProblemType: Bug ApportLog: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: apport 2.20.9-0ubuntu7.6 [origin: Ubuntu] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-20-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1834780 Title: apport should have python3-launchpadlib in required dependencies Status in apport package in Ubuntu: New Bug description: When asked to report apt-collect , apport is not installed on my system and I was told "apt install apport", so I did and the installation went ok. Problem: apport then fails on missing dependency python3-launchpadlib Workaround: manually install it through apt. Solution: apport should have python3-launchpadlib in required dependencies. --- ProblemType: Bug ApportLog: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: apport 2.20.9-0ubuntu7.6 [origin: Ubuntu] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-20-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1834780/+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 1834780] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1834780/+attachment/5274262/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1834780 Title: apport should have python3-launchpadlib in required dependencies Status in apport package in Ubuntu: New Bug description: When asked to report apt-collect , apport is not installed on my system and I was told "apt install apport", so I did and the installation went ok. Problem: apport then fails on missing dependency python3-launchpadlib Workaround: manually install it through apt. Solution: apport should have python3-launchpadlib in required dependencies. --- ProblemType: Bug ApportLog: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: apport 2.20.9-0ubuntu7.6 [origin: Ubuntu] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-20-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1834780/+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 1834780] Re: apport should have python3-launchpadlib in required dependencies
Uploaded apport-collect, please note the dependencies info is after I needed to manually install the launchpadlib :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1834780 Title: apport should have python3-launchpadlib in required dependencies Status in apport package in Ubuntu: New Bug description: When asked to report apt-collect , apport is not installed on my system and I was told "apt install apport", so I did and the installation went ok. Problem: apport then fails on missing dependency python3-launchpadlib Workaround: manually install it through apt. Solution: apport should have python3-launchpadlib in required dependencies. --- ProblemType: Bug ApportLog: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: apport 2.20.9-0ubuntu7.6 [origin: Ubuntu] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-20-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1834780/+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 1834494] Re: latest bzip2 reports crc errors incorrectly
** Changed in: bzip2 (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1834494 Title: latest bzip2 reports crc errors incorrectly Status in bzip2: New Status in bzip2 package in Ubuntu: Confirmed Status in bzip2 source package in Xenial: New Status in bzip2 source package in Bionic: New Status in bzip2 source package in Cosmic: New Status in bzip2 source package in Disco: New Status in bzip2 package in Debian: Confirmed Bug description: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. To manage notifications about this bug go to: https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1834494] Re: latest bzip2 reports crc errors incorrectly
Filled respective bug in Debian as well as per https://bugs.debian.org/931278 ** Bug watch added: Debian Bug tracker #931278 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931278 ** Also affects: bzip2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931278 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1834494 Title: latest bzip2 reports crc errors incorrectly Status in bzip2: New Status in bzip2 package in Ubuntu: Confirmed Status in bzip2 source package in Xenial: New Status in bzip2 source package in Bionic: New Status in bzip2 source package in Cosmic: New Status in bzip2 source package in Disco: New Status in bzip2 package in Debian: Unknown Bug description: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. To manage notifications about this bug go to: https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1810683] Re: Suspend does not work in the login screen
Does anybody care about lightdm bugs? I'm still seeing this issue but I haven't found a way to debug it. Is there some environment variable or some other method that can make all g_debug() messages visible from lightdm? Currently no log seems to contain any of the g_debug() messages in the lightdm source code. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1810683 Title: Suspend does not work in the login screen Status in lightdm package in Ubuntu: New Bug description: After booting the system and login screen is displayed top right gear- icon contains option to Suspend. However, selecting that action has no results at all (no error message, nothing in any file under /var/log or journalctl). I would like to get the suspend action to work similar to older Ubuntu versions (this system used to run Ubuntu 16.04 LTS and I did a fresh install of 18.04.1 LTS). I have removed package gdm3 and installed lightdm instead because I like the lightdm interface better for our use case. Looking at the source code in liblightdm-gobject/power.c suggests that lightdm_get_can_suspend() returns true because I get the suspend option. However, selecting the option does nothing so I would guess that lightdm_suspend() is called but somehow none of the g_debug() log messages never appear anywhere so I cannot debug the problem any further. (The above is just a guess because I didn't have enough time to read the source well enough to figure out if this is the codepath I'm trying to activate.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Jan 6 22:23:20 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1810683/+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 1832882] Re: libcurl-gnutls segfaults spotify client
Can confirm the segfault. Actually snap package is not a solution, it has a different behaviour with media keys (not working without an explicit mapping) that's why the deb package is preferrable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832882 Title: libcurl-gnutls segfaults spotify client Status in curl package in Ubuntu: Fix Released Status in curl source package in Disco: Confirmed Bug description: The latest release of Spotify client segfaults in libcurl-gnutls as can be read in this thread on spotify support forum: https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479 According to one participant the work-around is to install debian packages libgnutls30_3.6.8-1_amd64.deb and libcurl3-gnutls_7.64.0-3_amd64.deb Ubuntu 19.04 version of the packages: libgnutls30 3.6.5-2ubuntu1.1 libcurl3-gnutls 7.64.0-2ubuntu1.1 As the bug can be resolved by installing debian packages, I assume Ubuntu's version of the packages is at fault and should be upgraded to match debian's level as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+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 1832882] Re: libcurl-gnutls segfaults spotify client
Pardon my ignorance about the Launchpad bug metadata states, but: is there going to be an update for Ubuntu Disco fixing this issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832882 Title: libcurl-gnutls segfaults spotify client Status in curl package in Ubuntu: Fix Released Status in curl source package in Disco: Confirmed Bug description: The latest release of Spotify client segfaults in libcurl-gnutls as can be read in this thread on spotify support forum: https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479 According to one participant the work-around is to install debian packages libgnutls30_3.6.8-1_amd64.deb and libcurl3-gnutls_7.64.0-3_amd64.deb Ubuntu 19.04 version of the packages: libgnutls30 3.6.5-2ubuntu1.1 libcurl3-gnutls 7.64.0-2ubuntu1.1 As the bug can be resolved by installing debian packages, I assume Ubuntu's version of the packages is at fault and should be upgraded to match debian's level as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+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
