[Touch-packages] [Bug 1774342] Re: /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable
*** This bug is a duplicate of bug 1894172 *** https://bugs.launchpad.net/bugs/1894172 ** This bug has been marked a duplicate of bug 1894172 isc-dhcp-server using wrong env variable for INTERFACES -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1774342 Title: /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable Status in isc-dhcp package in Ubuntu: New Bug description: package: isc-dhcp-server /etc/default/isc-dhcp-server define the variables INTERFACESv4 and INTERFACESv6 for define listening network interface, but /lib/systemd/system/isc-dhcp-server.service and /lib/systemd/system /isc-dhcp-server6.service use the variable INTERFACES (exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES'). This causes the service to listen on all interfaces. The correct way would be for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACESv4' .. for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf $CONFIG_FILE $INTERFACESv6' . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1774342/+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 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
** Also affects: ayatana-indicator-power (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" Status in Ubuntu MATE: New Status in ayatana-indicator-power package in Ubuntu: New Status in indicator-power package in Ubuntu: Confirmed Status in mate-indicator-applet package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Click on the battery indicator. 2. Click "Show Percentage on Menu Bar" to enable it. 3. Do it again to disable it. 4. Battery indicator disappears Output from dmesg: [ 613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000] [ 749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000] [ 775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000] [ 816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000] [ 841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+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 1893170] Re: [Ubuntu 20.10] zlib: DFLTCC compression level switching issues
** Changed in: ubuntu-z-systems Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1893170 Title: [Ubuntu 20.10] zlib: DFLTCC compression level switching issues Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: New Status in zlib source package in Focal: New Status in zlib source package in Groovy: New Bug description: Description: zlib: DFLTCC compression level switching issues Symptom: Switching compression levels corrupts data Problem: Hardware and software compression states become desynchronized. Solution: Improve compression state synchronization. Since zlib project does not accept patches at the moment, the fix has been integrated into the DFLTCC pull request: https://github.com/madler/zlib/pull/410 The commitid is 992a7afc3edfa511dff0650d1c545b11bf64e655. Reproduction: Not possible with popular command line tools. The issues were discovered using example_call_fuzzer from: https://github.com/iii-i/zlib-ng/tree/fuzz/test/fuzz/ This needs also be applied against 20.04 ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893170/+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 1894454] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: nvidia ** Summary changed: - Xorg freeze + [nvidia] Screen freeze ** 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/1894454 Title: [nvidia] Screen freeze Status in Ubuntu: Incomplete Bug description: Ubuntu 20.04 freezes randomly ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 01:22:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.66, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: NVIDIA Corporation GM107GL [Quadro K620] [10de:13bb] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K620] [10de:1098] InstallationDate: Installed on 2020-04-26 (133 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision Tower 3620 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=5abcce6c-0eb6-4ef4-bf1b-0a62c2924a2d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.15.0 dmi.board.name: 0MWYPT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.15.0:bd03/25/2020:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision Tower 3620 dmi.product.sku: 06B7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1894454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchp
[Touch-packages] [Bug 1894432] Re: corrupted screen on Chrome when returning from sleep
I think this might be related to bug 1855757. If so then a similar fix may be needed in Chrome, OR it might be another bug in Mutter (gnome- shell). ** Package changed: xorg (Ubuntu) => chromium-browser (Ubuntu) ** Summary changed: - corrupted screen on Chrome when returning from sleep + [nvidia] Corrupted screen on Chrome when returning from sleep ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags added: nvidia -- 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/1894432 Title: [nvidia] Corrupted screen on Chrome when returning from sleep Status in chromium-browser package in Ubuntu: New Bug description: Problem just started happening within the last few days. No major system changes that I can think of other than some 'live-patches' being reported as updated... Only appears to happen in Chrome (so maybe I should report it there?) as other application don't seem to display the same glitchiness. Appears I have to stop all instances of chrome to clear it (or of course, restart the machine) Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 6 08:41:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-42-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 440.100, 5.4.0-45-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics [1043:150f] Subsystem: ASUSTeK Computer Inc. GP108BM [GeForce MX250] [1043:150f] InstallationDate: Installed on 2020-06-17 (80 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX434FLC_UX434FL ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ac571274-cc68-46ff-b340-4ca15d7a7289 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434FLC.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434FLC 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.:bvrUX434FLC.303:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434FLC_UX434FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434FLC_UX434FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-vi
[Touch-packages] [Bug 1893170] Re: [Ubuntu 20.10] zlib: DFLTCC compression level switching issues
Hi I've updated the patch to the latest version and uploaded the package to my PPA as version 1.2.11.dfsg-2ubuntu2~ppa2 which should appear here soon: https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=zlib. Can you test this on your hardware and let me know how it goes? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1893170 Title: [Ubuntu 20.10] zlib: DFLTCC compression level switching issues Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Status in zlib source package in Focal: New Status in zlib source package in Groovy: New Bug description: Description: zlib: DFLTCC compression level switching issues Symptom: Switching compression levels corrupts data Problem: Hardware and software compression states become desynchronized. Solution: Improve compression state synchronization. Since zlib project does not accept patches at the moment, the fix has been integrated into the DFLTCC pull request: https://github.com/madler/zlib/pull/410 The commitid is 992a7afc3edfa511dff0650d1c545b11bf64e655. Reproduction: Not possible with popular command line tools. The issues were discovered using example_call_fuzzer from: https://github.com/iii-i/zlib-ng/tree/fuzz/test/fuzz/ This needs also be applied against 20.04 ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893170/+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 1894400] Re: Establishing connection to PulseAudio. Please wait...
On the affected machine, please: 1. Check for any crashes in /var/crash/ 2. Reproduce the problem again and verify there is a pulseaudio process running while the problem is occuring. 3. Reboot, reproduce the problem again and while it is happening run: journalctl -b0 > journal.txt and attach the resulting text file here. ** 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/1894400 Title: Establishing connection to PulseAudio. Please wait... Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sometimes when i start up firefox in the morning i can't hear any audio. Or sometimes a page that wants to play audio will freeze, waiting. When these happen i'll launch pavucontrol next and it'll say "Establishing connection to PulseAudio. Please wait..." and just keep waiting. i look for the pulseaudio process, it's there as usual. Even so i just launch an additional pulseaudio process, and then pavucontrol is immediately all happy. Firefox might also immediately become all happy, or less often i'll also need to restart firefox before i can play audio. i usually shut off my computer at night. Starting it up each morning, manifestations as described above might be separated by a couple weeks, or might happen a couple times within a week. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 [modified: usr/share/pulseaudio/alsa-mixer/paths/steelseries-arctis-7-output-mono.conf] ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 5 16:45:50 2020 ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894400/+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 1894338] Re: Earphones Volume Control doesn't work
Please be careful to only report one problem per bug report. The second issue you mention is bug 1583801. ** Description changed: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 - (dual-boot with Windows 10, Secure Boot enabled) I have two issues with - them (possibly should report a new bug for the second one?) + (dual-boot with Windows 10, Secure Boot enabled) - 1) Trying to set the volume from my earphones' controls doesn't work, no + Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? - - 2) Every time I boot or reboot my system and leave the earphones on, - without unplugging them, i.e. when Ubuntu boots with the headphone plug - already occupied, I don't get any sound from my headphones, no matter - how much up and down I turn the volume (from my laptop sound controls), - i.e. the sound bar moves up and down and I hear no sound. I have to - unplug and re-plug my earphones and only then does Ubuntu recognize them - and ask me to select "Headset/Headset with mic/Mic". How can I fix it, - so that I don't have to replug every time I boot? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: jason 3523 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=el_GR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=el_GR.UTF-8 + SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. ** Summary changed: - Earphones Volume Control doesn't work + [Samsung Earphones Tuned by AKG] Volume control buttons don't work -- 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/1894338 Title: [Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in pulseaudio package in Ubuntu: Incomplete Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.
[Touch-packages] [Bug 1893728] Re: Ubuntu CVE Tracker krb5 1.17-6ubuntu4 CVE-2018-20217 false positive
This was fixed in the https://launchpad.net/ubuntu-cve-tracker in commit https://git.launchpad.net/ubuntu-cve- tracker/commit/?id=6d3a00335ca58346a10a09ad3c94046820490f8f ** No longer affects: krb5 (Ubuntu) ** No longer affects: krb5 (Ubuntu Bionic) ** Changed in: krb5 (Ubuntu Focal) Status: New => Invalid ** Also affects: ubuntu-cve-tracker Importance: Undecided Status: New ** Changed in: ubuntu-cve-tracker Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1893728 Title: Ubuntu CVE Tracker krb5 1.17-6ubuntu4 CVE-2018-20217 false positive Status in Ubuntu CVE Tracker: Fix Released Status in krb5 source package in Focal: Invalid Bug description: Information in shows that krb5 versions before 1.17 are vulnerable to CVE-2018-20217. https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-20217.html Based on Debian bug report, this is already fixed in 1.16.2 version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917387 Ubuntu 20.04 LTS (Focal Fossa) includes version krb5 1.17.6: https://launchpad.net/ubuntu/focal/+source/krb5 Ubuntu CVE Tracker page shows that Ubuntu 20.04 LTS (Focal Fossa) doesn't have a package where CVE-2018-20217 is fixed. https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-20217.html Steps to reproduce: This was found when examining AWS Elastic Container Registry Vulnerability scanning results for a Docker image based on latest Ubuntu 20.04: Here is the complete line from the report: krb5:1.17-6ubuntu4 MEDIUM A Reachable Assertion issue was discovered in the KDC in MIT Kerberos 5 (aka krb5) before 1.17. If an attacker can obtain a krbtgt ticket using an older encryption type (single-DES, triple-DES, or RC4), the attacker can crash the KDC by making an S4U2Self request. It can be seen from the scan that the Docker image included krb5 bversion 1.17-6. Expected: No vulnerability finding. Actual: krb5 bversion 1.17-6ubuntu4 is reported as vulnerable to CVE-2018-20217. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cve-tracker/+bug/1893728/+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 1894338] Re: [Samsung Earphones Tuned by AKG] Volume control buttons don't work
First we need to check if the problem has already been solved in a later release. Please try booting these from USB: http://cdimage.ubuntu.com/daily-live/current/ https://releases.ubuntu.com/20.04/ and tell us if the same problem occurs in a live session of 20.04 or 20.10. ** 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/1894338 Title: [Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in pulseaudio package in Ubuntu: Incomplete Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894338/+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 1894347] Re: Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell
** Package changed: gnome-shell (Ubuntu) => ubuntu-meta (Ubuntu) ** No longer affects: ubuntu-wallpapers (Ubuntu) ** Changed in: ubuntu-meta (Ubuntu) Status: Incomplete => Triaged ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Low ** Tags added: focal groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1894347 Title: Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Try to remove just "ubuntu-wallpapers" in Synaptic. It will mark for removal "gnome-shell", "ubuntu-desktop", "ubuntu-artwork" and 3 other packages. It should remove only "ubuntu-wallpapers" and "ubuntu-wallpapers-bionic". Experiments with "depends" have to stop now! I don't want to remove gnome-shell just because of wallpapers! Who made this change? Fire him!!! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['disable-force-q...@kingodz.gmail.com', 'temperature@xtranophilist', 'freon@UshakovVasilii_Github.yahoo.com', 'systemmoni...@gnome-shell-extensions.gcampax.github.com']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-06-30 (1527 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: ubuntu-wallpapers PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-115-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1894347/+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 1894347] [NEW] Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell
You have been subscribed to a public bug: Try to remove just "ubuntu-wallpapers" in Synaptic. It will mark for removal "gnome-shell", "ubuntu-desktop", "ubuntu-artwork" and 3 other packages. It should remove only "ubuntu-wallpapers" and "ubuntu-wallpapers-bionic". Experiments with "depends" have to stop now! I don't want to remove gnome-shell just because of wallpapers! Who made this change? Fire him!!! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['disable-force-q...@kingodz.gmail.com', 'temperature@xtranophilist', 'freon@UshakovVasilii_Github.yahoo.com', 'systemmoni...@gnome-shell-extensions.gcampax.github.com']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-06-30 (1527 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: ubuntu-wallpapers PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-115-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: ubuntu-wallpapers (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-collected bionic packaging third-party-packages -- Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell https://bugs.launchpad.net/bugs/1894347 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. -- 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 1894234] Re: Bluetooth not working with Gnome in Groovy (20.10)
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1894234 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: gnome-bluetooth (Ubuntu) => bluez (Ubuntu) ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1894234 Title: Bluetooth not working with Gnome in Groovy (20.10) Status in bluez package in Ubuntu: Incomplete Bug description: Having plugged in a USB bluetooth dongle, the gnome-bluetooth settiogs report that I have no bluetooth adapter, and I should plug one in. At the same time, I can see the bluetooth adapter with hciconfig, and in fact, I can pair with remote bluetooth devices using a 3rd party bluetooth manager (blueman). Obviously this is not ideal, as it is not fully integrated with gnome, sound devices are not fully available etc.. I'm not sure what else I can provide, but:- # hciconfig -a hci0: Type: Primary Bus: USB BD Address: 24:4B:FE:3A:21:65 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:1117 acl:0 sco:0 events:72 errors:0 TX bytes:4973 acl:0 sco:0 commands:72 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'morpheous' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0xb LMP Version: 5.1 (0xa) Subversion: 0x8761 Manufacturer: Realtek Semiconductor Corporation (93) root@morpheous:~# When I got to settings, it tells me I have no bluetooth devices plugged in! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1894234/+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 1888352] Re: use builtin dump_acpi_tables.py in hookutils
the oem-getlogs file using the apport 2.20.11-0ubuntu27.9 from the proposed channel. I am going to find uefi expert to double check ** Attachment added: "oemlogs-f1-test-20200907111510+0800.apport.gz" https://bugs.launchpad.net/oem-priority/+bug/1888352/+attachment/5408229/+files/oemlogs-f1-test-20200907111510+0800.apport.gz -- 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/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+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 1894234] [NEW] Bluetooth not working with Gnome in Groovy (20.10)
You have been subscribed to a public bug: Having plugged in a USB bluetooth dongle, the gnome-bluetooth settiogs report that I have no bluetooth adapter, and I should plug one in. At the same time, I can see the bluetooth adapter with hciconfig, and in fact, I can pair with remote bluetooth devices using a 3rd party bluetooth manager (blueman). Obviously this is not ideal, as it is not fully integrated with gnome, sound devices are not fully available etc.. I'm not sure what else I can provide, but:- # hciconfig -a hci0: Type: Primary Bus: USB BD Address: 24:4B:FE:3A:21:65 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:1117 acl:0 sco:0 events:72 errors:0 TX bytes:4973 acl:0 sco:0 commands:72 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'morpheous' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0xb LMP Version: 5.1 (0xa) Subversion: 0x8761 Manufacturer: Realtek Semiconductor Corporation (93) root@morpheous:~# When I got to settings, it tells me I have no bluetooth devices plugged in! ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth gnome groovy -- Bluetooth not working with Gnome in Groovy (20.10) https://bugs.launchpad.net/bugs/1894234 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. -- 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 1876637] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1876637 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1876637 Title: [Lenovo V330-15IKB] Volume jumps to max automatically Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: alsa-driver was selected automatically. I don't know if that's the problem. I'm newbie. I just want to understand when it will be triggered (if it's a feature) so I can avoid increasing the volume to the max accidentally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mert 1026 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 02:57:08 2020 InstallationDate: Installed on 2020-05-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulseAudioLog: May 03 12:18:43 V330 dbus-daemon[841]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=1000 pid=1026 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [81AX, Intel Kabylake HDMI, Digital Out, HDMI] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN49WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6SCN49WW:bd02/18/2020:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876637/+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 1894097] Re: Unable to switch from HSP to A2DP on BOSE blutoot headphones
Reminiscent of bug 1845046, and bug 1879010. ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894097 Title: Unable to switch from HSP to A2DP on BOSE blutoot headphones Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I have a Bose NC 700 pair of headphones. The device works correctly with Android and Windows (al be it more cumbersome and confusing in Windows). Device: Firmware 1.5.1-9303+d287f23 GUID: 5c097385-cd87-d8dd-bab9-4c726a0ac560 I am available to test. Problem 1: I am required to click on the "connect" toggle button for the Bluetooth audio device about 20 - 30 times to make it connect. This is also true for other speakers as for example JBL Bluetooth speakers. Problem 2: BOSE Headset/Gnome BT Audio configuration. I am unable to switch between HSP/DSP mode to A2DP Sink. The device remains connected as a communication device and not as an audio device. I remain stuck with mono sound. Though the gnome control panel indicates that I have indeed switched to A2DP Sink. However, when I click "test" I only get the mono test and the sound is absolutely unusable. Because there is a microphone on the headphones, Gnome control panel and the underlying Bluetooth service refuse to change from HSP/DSP. Clearly this is not by design. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 13:45:22 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-04 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894097/+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 1888352] Re: use builtin dump_acpi_tables.py in hookutils
** Changed in: oem-priority Status: Confirmed => In Progress -- 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/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+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 1789758] Re: bluetooth headphones a2dp profile does not function after suspend, only HSP
There are two problems in your logs that might be relevant: 1. Timeouts: [1666806.664899] Bluetooth: hci0: command 0x200c tx timeout [1666808.680839] Bluetooth: hci0: command 0x0401 tx timeout 2. BlueZ crashed: [1666867.068257] bluetoothd[9515]: segfault at 0 ip 556e0bc36576 sp 7fff1afb5c40 error 4 in bluetoothd[556e0bbcd000+f3000] But since this bug is a couple of years old already, please tell us if you still experience it. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => 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/1789758 Title: bluetooth headphones a2dp profile does not function after suspend, only HSP Status in pulseaudio package in Ubuntu: Incomplete Bug description: 1) lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 2) $ apt-cache policy bluez bluez: Installed: 5.48-0ubuntu3.1 Candidate: 5.48-0ubuntu3.1 Version table: *** 5.48-0ubuntu3.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.48-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) bluetooth headphones stay working in a2dp mode even after suspend 4) bluetooth headphones connect but no sound will come out of a2dp mode, only in HSP profile ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 29 18:07:26 2018 InstallationDate: Installed on 2018-05-26 (95 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180525) InterestingModules: rfcomm bnep btusb bluetooth ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9e84ffd4-d629-4dcd-a6c4-6648d1a34665 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0041.2015.0316.1442 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87971-406 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0041.2015.0316.1442:bd03/16/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-406:cvn:ct3:cvr: dmi.product.family: To be filled by O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: 48:51:B7:07:93:F5 ACL MTU: 1021:5 SCO MTU: 96:5 DOWN RX bytes:5617087 acl:790 sco:22622 events:634625 errors:0 TX bytes:540631745 acl:632348 sco:22584 commands:537 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1789758/+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 1876637] Re: [Lenovo V330-15IKB] Volume jumps to max automatically
See also bug 1894075. ** Summary changed: - I use the buttons on the keyboard to adjust sound (F1 mute, F2 decrease, F3 increase). More often than not, I push two to four times until the sound gets to the level I want. Sometimes it gets automatic after I press, and takes it all the way up, or all the way down. I'm not sure if this is a feature or bug but I can't figure out when it will be triggered, thus I end up pumping the music at very loud, uncomfortable levels until I get back my control from panic and decrease the volume to somewhere acceptable. There are times it automatically goes to complete silent from there which is still annoying although not as much as the first one. [81AX, Intel Kabylake HDMI, Digital Out, HDMI] volume slider problem + [Lenovo V330-15IKB] Volume jumps to max automatically ** Also affects: linux (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/1876637 Title: [Lenovo V330-15IKB] Volume jumps to max automatically Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: alsa-driver was selected automatically. I don't know if that's the problem. I'm newbie. I just want to understand when it will be triggered (if it's a feature) so I can avoid increasing the volume to the max accidentally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mert 1026 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 02:57:08 2020 InstallationDate: Installed on 2020-05-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulseAudioLog: May 03 12:18:43 V330 dbus-daemon[841]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=1000 pid=1026 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [81AX, Intel Kabylake HDMI, Digital Out, HDMI] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN49WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6SCN49WW:bd02/18/2020:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876637/+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 1894075] Re: [Lenovo V330-15IKB] sound is absent ubuntu 20.04
See also bug 1876637. ** Summary changed: - sound is absent ubuntu 20.04 + [Lenovo V330-15IKB] sound is absent ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894075 Title: [Lenovo V330-15IKB] sound is absent ubuntu 20.04 Status in pulseaudio package in Ubuntu: New Bug description: Could You help me with sound restore in Ubuntu 20.04 LTS after upgrade from Ubuntu 19.10? Sincerely N.E. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsystemd0:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:123:2243292:2020-09-02 17:38:34.836466312 +0300:2020-09-02 17:38:35.836466312 +0300:/var/crash/_usr_lib_firefox_crashreporter.1000.crash 640:0:123:81354:2020-09-02 14:42:34.015875816 +0300:2020-09-02 14:42:35.015875816 +0300:/var/crash/systemd.0.crash 640:0:123:81374:2020-09-02 14:42:33.987879276 +0300:2020-09-02 14:42:34.987879276 +0300:/var/crash/libsystemd0:amd64.0.crash 640:0:123:81374:2020-09-02 14:42:35.003877338 +0300:2020-09-02 14:42:34.991878838 +0300:/var/crash/systemd-timesyncd.0.crash Date: Wed Sep 2 14:42:34 2020 DpkgTerminalLog: dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 is already installed and configured ErrorMessage: package libsystemd0:amd64 is already installed and configured InstallationDate: Installed on 2019-09-27 (341 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dpkg Title: package libsystemd0:amd64 245.4-4ubuntu3.2 failed to install/upgrade: package libsystemd0:amd64 is already installed and configured UpgradeStatus: Upgraded to focal on 2020-06-19 (75 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolae1554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-01 (368 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190709) Package: pulseaudio 1:13.99.1-1ubuntu3.5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal wayland-session Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6SCN35WW:bd06/21/2018:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894075/+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 1805077] Re: [ASUS X555YI] the audio pause and repeat for a very short of time randomly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1805077 Title: [ASUS X555YI] the audio pause and repeat for a very short of time randomly Status in pulseaudio package in Ubuntu: Confirmed Bug description: the audio pause and repeat for a very short of time randomly when I use web browser to play music and use smplayer play video this bug happens randomly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 13716 F pulseaudio /dev/snd/controlC0: widon 13716 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI 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/pulseaudio/+bug/1805077/+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 1805077] Re: [ASUS X555YI] the audio pause and repeat for a very short of time randomly
I am a new Linux user, and I face the same problem in Ubuntu 20.04 A short (about a second or less) repeated sound occurs at random times, in the browser, in VLC or even the system sounds, and it's actually annoying. I tried Fedora 32 but the same issue there but less likely to happens, and I tried OpenSUSE Leap 15.2 and it never happened. My search led me to an Arch article explaining the situation: "The newer implementation of the PulseAudio sound server uses timer-based audio scheduling instead of the traditional, interrupt-driven approach. Timer-based scheduling may expose issues in some ALSA drivers. On the other hand, other drivers might be glitchy without it on, so check to see what works on your system." See https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches,_skips_or_crackling I tried the proposed solutions but it Don't work. -- 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/1805077 Title: [ASUS X555YI] the audio pause and repeat for a very short of time randomly Status in pulseaudio package in Ubuntu: Confirmed Bug description: the audio pause and repeat for a very short of time randomly when I use web browser to play music and use smplayer play video this bug happens randomly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 13716 F pulseaudio /dev/snd/controlC0: widon 13716 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI 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/pulseaudio/+bug/1805077/+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 1894454] [NEW] Xorg freeze
Public bug reported: Ubuntu 20.04 freezes randomly ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 01:22:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.66, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: NVIDIA Corporation GM107GL [Quadro K620] [10de:13bb] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K620] [10de:1098] InstallationDate: Installed on 2020-04-26 (133 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision Tower 3620 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=5abcce6c-0eb6-4ef4-bf1b-0a62c2924a2d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.15.0 dmi.board.name: 0MWYPT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.15.0:bd03/25/2020:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision Tower 3620 dmi.product.sku: 06B7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze possible-manual-nvidia-install 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/1894454 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.04 freezes randomly ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Bir dizin: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 01:22:46 2020 DistUpgraded: Fresh install DistroCodename:
[Touch-packages] [Bug 1894452] [NEW] shutdown delay because of cups
Public bug reported: Both my desktop and laptop running 20.10 have a 90 second delay shutting down (power off or restart). Getting message; A stop job is Running for Make remote CUPS printers available locally After 90 seconds the shutdown continues to completion. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: cups 2.3.3-2ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Sep 6 18:10:20 2020 InstallationDate: Installed on 2020-08-28 (9 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) KernLog: Lpstat: device for ENVY_4500: hp:/net/ENVY_4500_series?ip=192.168.1.131 MachineType: CLEVO CO. W35_37ET Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ENVY_4500.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ENVY_4500.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: W35_37ET dmi.board.vendor: CLEVO CO. dmi.board.version: N/A dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: CLEVO CO. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: W35_37ET dmi.product.sku: To be filled by O.E.M. dmi.product.version: N/A dmi.sys.vendor: CLEVO CO. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1894452 Title: shutdown delay because of cups Status in cups package in Ubuntu: New Bug description: Both my desktop and laptop running 20.10 have a 90 second delay shutting down (power off or restart). Getting message; A stop job is Running for Make remote CUPS printers available locally After 90 seconds the shutdown continues to completion. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: cups 2.3.3-2ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Sep 6 18:10:20 2020 InstallationDate: Installed on 2020-08-28 (9 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) KernLog: Lpstat: device for ENVY_4500: hp:/net/ENVY_4500_series?ip=192.168.1.131 MachineType: CLEVO CO. W35_37ET Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ENVY_4500.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ENVY_4500.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: W35_37ET dmi.board.vendor: CLEVO CO. dmi.board.version: N/A dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: CLEVO CO. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: W35_37ET dmi.product.sku: To be filled by O.E.M. dmi.product.version: N/A dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1894452/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@
[Touch-packages] [Bug 1894432] [NEW] corrupted screen on Chrome when returning from sleep
Public bug reported: Problem just started happening within the last few days. No major system changes that I can think of other than some 'live-patches' being reported as updated... Only appears to happen in Chrome (so maybe I should report it there?) as other application don't seem to display the same glitchiness. Appears I have to stop all instances of chrome to clear it (or of course, restart the machine) Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 6 08:41:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-42-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 440.100, 5.4.0-45-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics [1043:150f] Subsystem: ASUSTeK Computer Inc. GP108BM [GeForce MX250] [1043:150f] InstallationDate: Installed on 2020-06-17 (80 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX434FLC_UX434FL ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ac571274-cc68-46ff-b340-4ca15d7a7289 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434FLC.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434FLC 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.:bvrUX434FLC.303:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434FLC_UX434FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434FLC_UX434FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "example of corrupted screen display in chrome" https://bugs.launchpad.net/bugs/1894432/+attachment/5408085/+files/graphics_glitch.png -- 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/1894432 Title: corrupted screen on Chrome when returning from sleep Status in xorg package in Ubuntu: New Bug description: Problem just started happening within the last few days. No major system changes that I can think of other than some 'live-patches' being reported as updated... Only appears to happen in Chrome (so maybe I should report it there?) as other application don'
[Touch-packages] [Bug 1257076] Re: Slow app startup time
I have this same issue. Apps like settings or firefox take upto 10 seconds to launch the first time after boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart-app-launch in Ubuntu. https://bugs.launchpad.net/bugs/1257076 Title: Slow app startup time Status in Ubuntu Application Launcher: Fix Released Status in unity-mir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Status in upstart-app-launch package in Ubuntu: Fix Released Bug description: Since upgrading to trusty, applications have been taking longer and longer to load. While on the one hand, there is feature work and investigation to do, see: https://blueprints.launchpad.net/ubuntu/+spec/appdev-1311-sdk-apps- performance on the other hand, this is a regression and should be handled via a bug report for that reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1257076/+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 1894423] Re: ubuntu-bug remains on "detecting data from the system" - cancel button doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- 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/1894423 Title: ubuntu-bug remains on "detecting data from the system" - cancel button doesn't work Status in apport package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 version: 2020.08.20+git968d4a4 steps: - terminal: ubuntu-bug - display (X.org) - the dialog "retrieving the informationn about the problem in progress" appear and it stay as is for minutes. I need to close the previous window "Apport" to close it. Lenovo thikcpad e495. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.8 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportLog: ERROR: apport (pid 2845) Sun Sep 6 09:45:36 2020: called for pid 828, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2845) Sun Sep 6 09:45:36 2020: executable: /usr/sbin/gdm3 (command line "/usr/sbin/gdm3") ERROR: apport (pid 2845) Sun Sep 6 09:45:36 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 2845) Sun Sep 6 09:45:36 2020: wrote report /var/crash/_usr_sbin_gdm3.0.crash ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:0:125:500320:2020-09-06 09:50:47.521485567 +0200:2020-09-06 09:55:24.662612942 +0200:/var/crash/_usr_sbin_gdm3.0.crash 600:120:125:37:2020-09-06 09:55:30.745127080 +0200:2020-09-06 09:55:30.745127080 +0200:/var/crash/_usr_sbin_gdm3.0.uploaded 644:0:125:0:2020-09-06 09:55:24.662612942 +0200:2020-09-06 09:55:24.662612942 +0200:/var/crash/_usr_sbin_gdm3.0.upload CurrentDesktop: ubuntu:GNOME Date: Sun Sep 6 10:27:09 2020 ExecutablePath: /usr/bin/apport-bug InstallationDate: Installed on 2020-09-03 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterpreterPath: /usr/bin/dash PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=it_IT.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1894423/+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 1894423] [NEW] ubuntu-bug remains on "detecting data from the system" - cancel button doesn't work
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 version: 2020.08.20+git968d4a4 steps: - terminal: ubuntu-bug - display (X.org) - the dialog "retrieving the informationn about the problem in progress" appear and it stay as is for minutes. I need to close the previous window "Apport" to close it. Lenovo thikcpad e495. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.8 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportLog: ERROR: apport (pid 2845) Sun Sep 6 09:45:36 2020: called for pid 828, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2845) Sun Sep 6 09:45:36 2020: executable: /usr/sbin/gdm3 (command line "/usr/sbin/gdm3") ERROR: apport (pid 2845) Sun Sep 6 09:45:36 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 2845) Sun Sep 6 09:45:36 2020: wrote report /var/crash/_usr_sbin_gdm3.0.crash ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:0:125:500320:2020-09-06 09:50:47.521485567 +0200:2020-09-06 09:55:24.662612942 +0200:/var/crash/_usr_sbin_gdm3.0.crash 600:120:125:37:2020-09-06 09:55:30.745127080 +0200:2020-09-06 09:55:30.745127080 +0200:/var/crash/_usr_sbin_gdm3.0.uploaded 644:0:125:0:2020-09-06 09:55:24.662612942 +0200:2020-09-06 09:55:24.662612942 +0200:/var/crash/_usr_sbin_gdm3.0.upload CurrentDesktop: ubuntu:GNOME Date: Sun Sep 6 10:27:09 2020 ExecutablePath: /usr/bin/apport-bug InstallationDate: Installed on 2020-09-03 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterpreterPath: /usr/bin/dash PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=it_IT.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal third-party-packages -- 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/1894423 Title: ubuntu-bug remains on "detecting data from the system" - cancel button doesn't work Status in apport package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 version: 2020.08.20+git968d4a4 steps: - terminal: ubuntu-bug - display (X.org) - the dialog "retrieving the informationn about the problem in progress" appear and it stay as is for minutes. I need to close the previous window "Apport" to close it. Lenovo thikcpad e495. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.8 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportLog: ERROR: apport (pid 2845) Sun Sep 6 09:45:36 2020: called for pid 828, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2845) Sun Sep 6 09:45:36 2020: executable: /usr/sbin/gdm3 (command line "/usr/sbin/gdm3") ERROR: apport (pid 2845) Sun Sep 6 09:45:36 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 2845) Sun Sep 6 09:45:36 2020: wrote report /var/crash/_usr_sbin_gdm3.0.crash ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:0:125:500320:2020-09-06 09:50:47.521485567 +0200:2020-09-06 09:55:24.662612942 +0200:/var/crash/_usr_sbin_gdm3.0.crash 600:120:125:37:2020-09-06 09:55:30.745127080 +0200:2020-09-06 09:55:30.745127080 +0200:/var/crash/_usr_sbin_gdm3.0.uploaded 644:0:125:0:2020-09-06 09:55:24.662612942 +0200:2020-09-06 09:55:24.662612942 +0200:/var/crash/_usr_sbin_gdm3.0.upload CurrentDesktop: ubuntu:GNOME Date: Sun Sep 6 10:27:09 2020 ExecutablePath: /usr/bin/apport-bug InstallationDate: Installed on 2020-09-03 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterpreterPath: /usr/bin/dash PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=it_IT.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1894423/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
I am suffering from this problem. Output from 'sudo service whoospie status': ** Attachment added: "whoopsiestatus.txt" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+attachment/5408046/+files/whoopsiestatus.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/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Proces
[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
It seems this bug affects almost everyone who wants to use earbuds with Linux? How come this issue is still nox fixed after such a long time? -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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
