[Touch-packages] [Bug 1874887] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1874887 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Confirmed Bug description: this was generated by a report ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:amd64: Configure NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.chromium.rules 70-snap.subtitle-edit.rules 70-snap.core.rules 70-snap.minetest.rules 70-snap.mc-installer.rules Date: Fri Apr 24 10:09:35 2020 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-04-17 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: ASUSTeK COMPUTER INC. N56VV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=185a0301-89b3-4798-b58b-80794b55d1b7 ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VV.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VV 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.:bvrN56VV.201:bd06/05/2013:svnASUSTeKCOMPUTERINC.:pnN56VV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N56VV dmi.product.sku: ASUS-NotebookSKU 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/systemd/+bug/1874887/+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 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module
For both tests I used the kmod package from my test ppa, since it is still in the unapproved upload queue. Firstly, I installed 4.15.0-99-generic from -updates, and booted my EFI based KVM machine with VGA=std. The screen was garbled, as the framebuffer used was efifb. I then installed 4.15.0-100-generic from -proposed, and rebooted, keeping the same settings. The screen was perfect and readable. The issue was fixed. I looked at lsmod, and bochs-drm was loaded. $ lsmod | grep bochs_drm bochs_drm 20480 1 ttm 106496 1 bochs_drm drm_kms_helper172032 1 bochs_drm drm 401408 4 drm_kms_helper,bochs_drm,ttm Dmesg shows: [1.082068] checking generic (c000 12c000) vs hw (c000 100) [1.082069] fb: switching to bochsdrmfb from EFI VGA [1.082468] Console: switching to colour dummy device 80x25 [1.083148] [drm] Found bochs VGA, ID 0xb0c5. [1.083151] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000. [1.083386] [TTM] Zone kernel: Available graphics memory: 4026194 kiB [1.083389] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [1.083390] [TTM] Initializing pool allocator [1.083394] [TTM] Initializing DMA pool allocator [1.085265] fbcon: bochsdrmfb (fb0) is primary device [1.087421] Console: switching to colour frame buffer device 128x48 [1.091589] bochs-drm :00:01.0: fb0: bochsdrmfb frame buffer device [1.108664] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on minor 0 Attached is a screenshot showing a good screen. I am happy to mark this as verified for the linux package. ** Attachment added: "screenshot of vga=std with 4.15.0-100-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872863/+attachment/5365529/+files/Screenshot%20from%202020-05-03%2013-25-59.png ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1872863 Title: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Bionic: In Progress Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device, as the efifb driver yields an unreadable garbled screen. See the attached image. The correct framebuffer driver to use in this situation is bochs-drm, and modprobing it from a HWE kernel fixes the issues. bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in LP #1378648 due to bochs-drm causing problems in a PowerKVM machine. This problem appears to be fixed now, and bochs-drm has been re-enabled for Disco and up, in LP #1795857 and has been proven safe. This has also come up again in LP #1823152, as well as chatter on LP #1795857 to get this enabled on Bionic. The customer which is experiencing this issue cannot switch to VGA=qxl as a workaround, and must use VGA=std, hence I suggest we re-enable bochs-drm for Bionic. [Fix] I noticed on Focal, if you boot, the framebuffer is initially efifb: [ 0.603716] efifb: probing for efifb [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1 [ 0.603736] efifb: scrolling: redraw [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 0.604462] Console: switching to colour frame buffer device 100x37 [ 0.605829] fb0: EFI VGA frame buffer device This soon changes to bochs-drm about a second later: [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xc000 -> 0xc0ff [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xc1c8c000 -> 0xc1c8cfff [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100) [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA [ 0.939085] Console: switching to colour dummy device 80x25 [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5. [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000. [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB [ 0.942081] [TTM] Initializing pool allocator [ 0.942089] [TTM] Initializing DMA pool allocator [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 GB/10.0 GiB) [ 0.944019]
[Touch-packages] [Bug 1876219] Re: iris driver for old cpu
Thanks! Mine is gen6 so the problem is with the default choice of graphics driver, do you happen to know which source package I should file bug or feature request to? Thanks again! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1876219 Title: iris driver for old cpu Status in mesa package in Ubuntu: New Bug description: I am not completely sure where I should file the bug. I am using Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the default graphics driver, which results in crashes in multiple apps including guvcview and calibre. Setting MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but is it true that iris does not support older generations of Intel CPUs? If it is the case would it be possible to revert to i965 in those circumstances? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1876219/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
This is not a bug, but lack of support for headsets that only have the HFP (Handsfree) profile and no HSP (Headset) profile. Many current headsets only support HFP, and these won't work since pulseway doesn't support HFP only. I find this ridiculous since there are a number of projects on git that have patched versions of pusleaudio to support HFP only headsets, so I wonder why this is not merging to the mainline of pulseaudio. With everyone on their headsets doing teleconferencing during the lockdown, this limitation of pulseway has been exemplified. Please have a look at it. -- 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 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/ubuntu/+source/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
[Touch-packages] [Bug 1867537] Re: 10-link-restrictions.conf missing - removed by postinst
Problem persist in Ubuntu 20.04 LTS stable release: root@fpglinux:/var/cache# lsb_release -d Description:Ubuntu 20.04 LTS root@fpglinux:/var/cache# apt policy procps procps: Instalados: 2:3.3.16-1ubuntu2 Candidato: 2:3.3.16-1ubuntu2 Tabla de versión: *** 2:3.3.16-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@fpglinux:/var/cache# debsums -ac procps debsums: missing file /etc/sysctl.d/10-link-restrictions.conf (from procps package) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1867537 Title: 10-link-restrictions.conf missing - removed by postinst Status in procps package in Ubuntu: Confirmed Bug description: The file "10-link-restrictions.conf" is listed in DEBIAN/conffiles in the binary deb package, and the file is present/installed, but it is removed by the "postinst" script resulting in "debsums" flagging it as a missing config file: root@beluga:~# lsb_release -d Description: Ubuntu Focal Fossa (development branch) root@beluga:~# apt policy procps procps: Installed: 2:3.3.16-1ubuntu2 Candidate: 2:3.3.16-1ubuntu2 Version table: *** 2:3.3.16-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@beluga:~# debsums -ac procps debsums: missing file /etc/sysctl.d/10-link-restrictions.conf (from procps package) This is not an issue in 18.04: manager@brigante:~$ lsb_release -d Description: Ubuntu 18.04.4 LTS manager@brigante:~$ apt policy procps procps: Installed: 2:3.3.12-3ubuntu1.2 Candidate: 2:3.3.12-3ubuntu1.2 Version table: *** 2:3.3.12-3ubuntu1.2 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:3.3.12-3ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2:3.3.12-3ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages manager@brigante:~$ debsums -ac procps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1867537/+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 1876484] Re: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Speaker, Internal] No sound at all
Please rm ~/.config/pulse/*; then reboot and retest. -- 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/1876484 Title: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hi, I have a problem with the sound. It doesn't work, it did work only once. When I did add Bluetooth speakers to it. https://i.imgur.com/2cyJwVJ.png - here speaker But now it recognizes speakers and built-in speakers, but no sound at all. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 2 19:23:55 2020 InstallationDate: Installed on 2020-04-27 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: AMI dmi.bios.version: F.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8519 dmi.board.vendor: HP dmi.board.version: 11.72 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.40:bd11/27/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn8519:rvr11.72:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df0xxx dmi.product.sku: 4UU78EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876484/+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 1867537] Re: 10-link-restrictions.conf missing - removed by postinst
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: procps (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1867537 Title: 10-link-restrictions.conf missing - removed by postinst Status in procps package in Ubuntu: Confirmed Bug description: The file "10-link-restrictions.conf" is listed in DEBIAN/conffiles in the binary deb package, and the file is present/installed, but it is removed by the "postinst" script resulting in "debsums" flagging it as a missing config file: root@beluga:~# lsb_release -d Description: Ubuntu Focal Fossa (development branch) root@beluga:~# apt policy procps procps: Installed: 2:3.3.16-1ubuntu2 Candidate: 2:3.3.16-1ubuntu2 Version table: *** 2:3.3.16-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@beluga:~# debsums -ac procps debsums: missing file /etc/sysctl.d/10-link-restrictions.conf (from procps package) This is not an issue in 18.04: manager@brigante:~$ lsb_release -d Description: Ubuntu 18.04.4 LTS manager@brigante:~$ apt policy procps procps: Installed: 2:3.3.12-3ubuntu1.2 Candidate: 2:3.3.12-3ubuntu1.2 Version table: *** 2:3.3.12-3ubuntu1.2 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:3.3.12-3ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2:3.3.12-3ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages manager@brigante:~$ debsums -ac procps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1867537/+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 1876475] Re: lxc can't assign ipv4 address from lxc-container config file
Yes, different versions of different distros will have different behavior as to what they do with pre-existing network config. Point is, it's racy and unreliable, the only way to get guaranteed behavior is to make sure that nothing else attempts to manage the network when you've already pre-configured it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1876475 Title: lxc can't assign ipv4 address from lxc-container config file Status in lxc package in Ubuntu: Invalid Bug description: I created and ran lxc-container with network config - others lxc-config on host system are the same like that (ipv4. addresses is different): __ # Template used to create this container: /usr/share/lxc/templates/lxc-ubuntu # Parameters passed to the template: # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware this has security implications) # Common configuration lxc.include = /usr/share/lxc/config/ubuntu.common.conf lxc.apparmor.profile = unconfined lxc.start.auto = 1 # Container specific configuration lxc.rootfs.path = dir:/var/lib/lxc/video/rootfs lxc.uts.name = video lxc.arch = amd64 # Network configuration lxc.net.0.type = veth lxc.net.0.flags = up lxc.net.0.link = lxcbr0 lxc.net.0.hwaddr = 4a:49:43:49:79:bf lxc.net.0.ipv4.address = 10.0.3.10/24 lxc.net.0.ipv4.gateway = 10.0.3.1 When container started - i can't see ip 10.0.3.10, it is not assigned after start: NAME STATE AUTOSTART GROUPS IPV4 IPV6 UNPRIVILEGED x RUNNING 1 - 10.0.3.2 -false y RUNNING 1 - 10.0.3.3 -false x1 RUNNING 1 - 10.0.3.7 -false x2 RUNNING 1 - 10.0.3.5 -false z3 RUNNING 1 - 10.0.3.4 -false z1 RUNNING 1 - 10.0.3.6 -false video RUNNING 0 - --false <-!!! Example (inside container "z1"): root@z1:/# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Example (inside problem container "video"): root@video:/# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal x,y,x1-3,z3,z1 - ubuntu 18 lts video - Ubuntu 20 LTS, host system ubuntu 20 lts. Host system: root@node:/var/lib/lxc/video# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal BUT! When I restarts all host-system, "video" container assigns ipv4 address after it. And if I stop the "video" container again (lxc-stop) and start the "video" container again (lxc-start -d -n video) - it losts ipv4 address and can't assign it again (from cli). root@node:/home/alex# dpkg -l | grep lxc ii liblxc-common 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools (common tools) ii liblxc1 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools (library) ii lxc 1:4.0.2-0ubuntu1 all Transitional package - lxc -> lxc-utils ii lxc-templates 3.0.4-3ubuntu1 amd64Linux Containers userspace tools (templates) ii lxc-utils 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools rc lxctl 0.3.1+debian-4 all Utility to manage LXC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxc 1:4.0.2-0ubuntu1 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 CasperMD5CheckResult: skip Date: Sat May 2 18:21:44 2020 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: lxc UpgradeStatus: Upgraded to focal on 2020-05-02 (0 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc.conf: lxc.network.link = lxcbr0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1876475/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1876534] [NEW] ThinkPad P72 - Very serious issues with external monitors on Thunderbolt dock
Public bug reported: I'm running Ubuntu 20.04 LTS on a ThinkPad P72 with a Quadro P5200. I recently purchased the ThinkPad Workstation Dock Gen2 and have been having issues with external displays on it. There are a multitude of issues with this. Sometimes you can plug in displays and both will show up fine after running xrandr --auto. Sometimes only one will appear and the other will stay black. There is a chance for any of these things to happen after making a display configuration change: - Nothing (displays work fine) - One display stays black - All displays including laptop internal display freeze, which is recoverable only by physically disconnecting the displays from the dock - Displays flicker on and off rapidly before every one goes dark including the laptop's internal display, requiring a hard reset. I have tried: - Upgrading to a newer kernel version (5.6.7) via mainline - Upgrading all system firmware, including dock, to latest via Lenovo Vantage in Windows dual boot - Downgrading the dock firmware from 3166 to 3164 - despite suggestions by people in this thread in the Lenovo community https://forums.lenovo.com/t5/Ubuntu/Thinkpad-P1-Gen2-amp-Thunderbolt-3-Workstation-Dock-amp-Linux-Ubuntu-Monitor-s-black/m-p/4575709?page=3 - this did not work - Downgrading the NVIDIA driver version to both 435 and 390 - neither worked ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun May 3 00:37:27 2020 DistUpgraded: 2020-03-04 19:48:20,592 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-28-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-28-generic, x86_64: installed wireguard, 1.0.20200413, 5.4.0-28-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2269] NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269] InstallationDate: Installed on 2019-10-19 (196 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20MCS08200 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=on default_hugepagesz=1G hugepagesz=1G hugepages=32 transparent_hugepage=never vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-03-04 (59 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2CET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MCS08200 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: 00040 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2CET50W(1.33):bd01/15/2020:svnLENOVO:pn20MCS08200:pvrThinkPadP72:rvnLENOVO:rn20MCS08200:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P72 dmi.product.name: 20MCS08200 dmi.product.sku: LENOVO_MT_20MC_BU_Think_FM_ThinkPad P72 dmi.product.version: ThinkPad P72 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Touch-packages] [Bug 1876533] [NEW] ThinkPad P72 - Display freezes when moving mouse pointer
Public bug reported: I'm running Ubuntu 20.04 LTS on a ThinkPad P72 with a Quadro P5200. Whenever I have Discrete graphics enabled in the BIOS, or set the prime- select profile to NVIDIA, the display will freeze and the mouse pointer will drift for a few seconds. This makes the system nearly unusable. However, the issue can be fixed by simply attaching a new display and running xrandr --auto. This video illustrates the issue: https://www.youtube.com/watch?v=OOQxK_4xII0 I have tried with a newer kernel version and with older versions of the NVIDIA driver (390, 435). Nothing works. For this reason I believe the issue to probably reside in the kernel or X. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun May 3 00:27:29 2020 DistUpgraded: 2020-03-04 19:48:20,592 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-28-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-28-generic, x86_64: installed wireguard, 1.0.20200413, 5.4.0-28-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2269] NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269] InstallationDate: Installed on 2019-10-19 (196 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20MCS08200 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=on default_hugepagesz=1G hugepagesz=1G hugepages=32 transparent_hugepage=never vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-03-04 (59 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2CET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MCS08200 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: 00040 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2CET50W(1.33):bd01/15/2020:svnLENOVO:pn20MCS08200:pvrThinkPadP72:rvnLENOVO:rn20MCS08200:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P72 dmi.product.name: 20MCS08200 dmi.product.sku: LENOVO_MT_20MC_BU_Think_FM_ThinkPad P72 dmi.product.version: ThinkPad P72 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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 false-gpu-hang focal freeze possible-manual-nvidia-install ubuntu ** Description changed: I'm running Ubuntu 20.04 LTS on a ThinkPad P72 with a Quadro P5200. Whenever I have Discrete graphics enabled in the BIOS, or set the prime- select profile to NVIDIA, the display will freeze and the mouse pointer will drift for a few seconds. This makes the system nearly unusable. + + However, the issue can be fixed by simply attaching a new display and + running xrandr --auto. This video illustrates the issue:
[Touch-packages] [Bug 1442649] Re: nautilus trash doesn't include btrfs and zfs subvolumes
** Changed in: glib Status: Unknown => Fix Released ** Changed in: gvfs Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1442649 Title: nautilus trash doesn't include btrfs and zfs subvolumes Status in GLib: Fix Released Status in gvfs: New Status in glib2.0 package in Ubuntu: Triaged Status in gvfs package in Ubuntu: Triaged Bug description: Files in `/path/to/subvolume/.Trash-1000` aren't listed in the global trash. Comment by bug triage team: comment 4 has a spot-on analysis of where this issue is coming from, an inconsistency between trash handling in gvfs and glib/gio. The problem has been around for quite a while. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1442649/+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 1876475] Re: lxc can't assign ipv4 address from lxc-container config file
LXC always does the same thing, it preconfigures your network namespace. Now if the OS you're running in the container runs its own network configuration tool, that pre-made configuration will likely get reset or mangled. If you want to use those config keys, you need to make sure you're not running software in your container which will reset that pre-made configuration. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1876475 Title: lxc can't assign ipv4 address from lxc-container config file Status in lxc package in Ubuntu: Invalid Bug description: I created and ran lxc-container with network config - others lxc-config on host system are the same like that (ipv4. addresses is different): __ # Template used to create this container: /usr/share/lxc/templates/lxc-ubuntu # Parameters passed to the template: # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware this has security implications) # Common configuration lxc.include = /usr/share/lxc/config/ubuntu.common.conf lxc.apparmor.profile = unconfined lxc.start.auto = 1 # Container specific configuration lxc.rootfs.path = dir:/var/lib/lxc/video/rootfs lxc.uts.name = video lxc.arch = amd64 # Network configuration lxc.net.0.type = veth lxc.net.0.flags = up lxc.net.0.link = lxcbr0 lxc.net.0.hwaddr = 4a:49:43:49:79:bf lxc.net.0.ipv4.address = 10.0.3.10/24 lxc.net.0.ipv4.gateway = 10.0.3.1 When container started - i can't see ip 10.0.3.10, it is not assigned after start: NAME STATE AUTOSTART GROUPS IPV4 IPV6 UNPRIVILEGED x RUNNING 1 - 10.0.3.2 -false y RUNNING 1 - 10.0.3.3 -false x1 RUNNING 1 - 10.0.3.7 -false x2 RUNNING 1 - 10.0.3.5 -false z3 RUNNING 1 - 10.0.3.4 -false z1 RUNNING 1 - 10.0.3.6 -false video RUNNING 0 - --false <-!!! Example (inside container "z1"): root@z1:/# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Example (inside problem container "video"): root@video:/# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal x,y,x1-3,z3,z1 - ubuntu 18 lts video - Ubuntu 20 LTS, host system ubuntu 20 lts. Host system: root@node:/var/lib/lxc/video# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal BUT! When I restarts all host-system, "video" container assigns ipv4 address after it. And if I stop the "video" container again (lxc-stop) and start the "video" container again (lxc-start -d -n video) - it losts ipv4 address and can't assign it again (from cli). root@node:/home/alex# dpkg -l | grep lxc ii liblxc-common 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools (common tools) ii liblxc1 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools (library) ii lxc 1:4.0.2-0ubuntu1 all Transitional package - lxc -> lxc-utils ii lxc-templates 3.0.4-3ubuntu1 amd64Linux Containers userspace tools (templates) ii lxc-utils 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools rc lxctl 0.3.1+debian-4 all Utility to manage LXC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxc 1:4.0.2-0ubuntu1 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 CasperMD5CheckResult: skip Date: Sat May 2 18:21:44 2020 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: lxc UpgradeStatus: Upgraded to focal on 2020-05-02 (0 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc.conf: lxc.network.link = lxcbr0 To manage notifications about
[Touch-packages] [Bug 1876531] [NEW] Dynamic desktop background when TearFree is true
Public bug reported: In my 20-intel.conf file in either /etc/X11/xorg.conf.d/ or /usr/share/X11/xorg.conf.d/ when I set Option TearFree to true, the pixel on my desktop go wild, see attachment (dynamic because those stripes vary from boot to boot). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 00:34:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:16a1] InstallationDate: Installed on 2020-04-30 (2 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 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 13d3:56dc IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX392FA_UX392FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=cbcf9a35-a5f8-429f-adad-ad8f21bff5df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX392FA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX392FA 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.:bvrUX392FA.301:bd07/17/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX392FA_UX392FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX392FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX392FA_UX392FA 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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 resolution ubuntu ** Attachment added: "Screenshot from 2020-05-03 00-00-01.png" https://bugs.launchpad.net/bugs/1876531/+attachment/5365443/+files/Screenshot%20from%202020-05-03%2000-00-01.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/1876531 Title: Dynamic desktop background when TearFree is true Status in xorg package in Ubuntu: New Bug description: In my 20-intel.conf file in either /etc/X11/xorg.conf.d/ or /usr/share/X11/xorg.conf.d/ when I set Option TearFree to true, the pixel on my desktop go wild, see attachment (dynamic because those stripes vary from boot to boot). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 00:34:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:16a1] InstallationDate: Installed on 2020-04-30 (2 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 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 13d3:56dc IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002
[Touch-packages] [Bug 1876530] [NEW] Screen scales to grandma very unfriendly mode
Public bug reported: When fractional scaling is active and set to 125% (I only tested this with 125%) and then the switch for fractional scaling is deactivated again, the screen scales well beyond the standard (and selected) 100%. Feels like 50% or less. This issue is removed when rebooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 00:35:53 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:16a1] InstallationDate: Installed on 2020-04-30 (2 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 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 13d3:56dc IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX392FA_UX392FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=cbcf9a35-a5f8-429f-adad-ad8f21bff5df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX392FA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX392FA 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.:bvrUX392FA.301:bd07/17/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX392FA_UX392FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX392FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX392FA_UX392FA 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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 -- 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/1876530 Title: Screen scales to grandma very unfriendly mode Status in xorg package in Ubuntu: New Bug description: When fractional scaling is active and set to 125% (I only tested this with 125%) and then the switch for fractional scaling is deactivated again, the screen scales well beyond the standard (and selected) 100%. Feels like 50% or less. This issue is removed when rebooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 00:35:53 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:16a1] InstallationDate: Installed on 2020-04-30 (2 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 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 13d3:56dc IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX392FA_UX392FA
[Touch-packages] [Bug 1876529] [NEW] Massive screen tearing using fractional scaling
Public bug reported: The tearing appears when fractional scaling is active and set to 125% (I only tested it with 125%) AND only when the mouse cursor is moved. The tearing does not appear, when the cursor is not moved. The tearing does also not appear when the display is scaled to 100 or 200% no matter if fractional scaling is active or the cursor is moved. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 00:37:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:16a1] InstallationDate: Installed on 2020-04-30 (2 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 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 13d3:56dc IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX392FA_UX392FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=cbcf9a35-a5f8-429f-adad-ad8f21bff5df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX392FA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX392FA 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.:bvrUX392FA.301:bd07/17/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX392FA_UX392FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX392FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX392FA_UX392FA 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876529 Title: Massive screen tearing using fractional scaling Status in xorg package in Ubuntu: New Bug description: The tearing appears when fractional scaling is active and set to 125% (I only tested it with 125%) AND only when the mouse cursor is moved. The tearing does not appear, when the cursor is not moved. The tearing does also not appear when the display is scaled to 100 or 200% no matter if fractional scaling is active or the cursor is moved. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 00:37:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:16a1] InstallationDate: Installed on 2020-04-30 (2 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 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 13d3:56dc IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp.
[Touch-packages] [Bug 1649436] Re: package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade: package libdbus-1-3:amd64 is already installed and configured
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1649436 Title: package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade: package libdbus-1-3:amd64 is already installed and configured Status in dbus package in Ubuntu: Confirmed Bug description: I just read the mensage of error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdbus-1-3:amd64 1.10.6-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Mon Dec 12 23:12:04 2016 DuplicateSignature: package:libdbus-1-3:amd64:1.10.6-1ubuntu3.1 Processing triggers for desktop-file-utils (0.22-1ubuntu5) ... dpkg: error processing package libbrlapi0.6:amd64 (--configure): package libbrlapi0.6:amd64 is already installed and configured ErrorMessage: package libdbus-1-3:amd64 is already installed and configured InstallationDate: Installed on 2016-12-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: dbus Title: package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade: package libdbus-1-3:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1649436/+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 1876524] [NEW] Issue after repositioning display/monitor location usiing display settings
Public bug reported: After repositioning the display applications would only maximise to use the area of the screen that overlapped between the original and new positions, see attachment which is a screenshot of an application maximised on the affected display. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "maximised-window.png" https://bugs.launchpad.net/bugs/1876524/+attachment/5365398/+files/maximised-window.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/1876524 Title: Issue after repositioning display/monitor location usiing display settings Status in xorg package in Ubuntu: New Bug description: After repositioning the display applications would only maximise to use the area of the screen that overlapped between the original and new positions, see attachment which is a screenshot of an application maximised on the affected display. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876524/+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 1876516] Re: Mouse cursor lagging (or freezing) when moving over system tray when wayland session
There was a video how it looks like. https://github.com/home-sweet-gnome/dash-to-panel/issues/561 https://youtu.be/5g-_y9s1YaA ** Bug watch added: github.com/home-sweet-gnome/dash-to-panel/issues #561 https://github.com/home-sweet-gnome/dash-to-panel/issues/561 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1876516 Title: Mouse cursor lagging (or freezing) when moving over system tray when wayland session Status in wayland package in Ubuntu: New Bug description: Cursor lagging when using wayland session. It happens on edge of something new, for example: - between clock menu and keyboard langugge - between app window and left launch panel Xorg session has no mouse lagging over this edges. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwayland-client0 1.18.0-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 23:10:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 6320] [144d:c600] InstallationDate: Installed on 2020-04-26 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=b242dbf0-fbe1-4cf8-a5a6-57dd5d749833 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 03PS.M505.20110929.LEO dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 305U1A/305U1A dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 03PS dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr03PS.M505.20110929.LEO:bd09/29/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr03PS:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305U1A/305U1A:rvr03PS:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: 305U1A dmi.product.sku: To be filled by O.E.M. dmi.product.version: 03PS dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1876516/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection
I fixed in my network, but the problem was in router security settings. Maybe the issue is in the security settings from the router, according to this link: [https://www.tp-link.com/us/support/faq/1533/][1] In the router page, I discovered that the MAC address from my laptop was in a "Blocked DoS Host List", then I cleaned this list. Additionally, I increased the threshold values to 500. [1]: https://www.tp-link.com/us/support/faq/1533/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.15 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/0 pr500k-9912ec-1 36301ded-0ac5-4a86-9621-87290ef159af /org/freedesktop/NetworkManager/ActiveConnection/5 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged
[Touch-packages] [Bug 1875950] Re: rsyslog log files failing to rotate
VM reinstalled, logs are rotating now. ** Changed in: logrotate (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1875950 Title: rsyslog log files failing to rotate Status in logrotate package in Ubuntu: Invalid Bug description: In focal, /etc/logrotate.conf contains: su root adm logrotate does not rotate files in /var/log: error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. Parent directory permissions: drwxrwxr-x 9 root syslog 4096 Apr 29 17:17 log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1875950/+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 1876523] [NEW] Repositioning display/monitor location in display settings does not relocate appliication location
Public bug reported: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.10 DISTRIB_CODENAME=eoan DISTRIB_DESCRIPTION="Ubuntu 19.10" Lenovo ThinkPad P52 + Thunderbold dock + 3 monitors I repositioned a monitor in display settings to reflect the actual position. An open application on the monitor was not repositioned with the display. The windows title bar and buttons were not on the display so the window could not be re-positioned. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/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 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 20:10:34 2020 DistUpgraded: 2020-05-02 16:29:42,699 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.59, 5.3.0-51-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:225f] NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP107GLM [Quadro P1000 Mobile] [17aa:225f] InstallationDate: Installed on 2018-10-02 (578 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20M9CTO1WW ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2020-05-02 (0 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2CET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20M9CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2CET50W(1.33):bd01/15/2020:svnLENOVO:pn20M9CTO1WW:pvrThinkPadP52:rvnLENOVO:rn20M9CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P52 dmi.product.name: 20M9CTO1WW dmi.product.sku: LENOVO_MT_20M9_BU_Think_FM_ThinkPad P52 dmi.product.version: ThinkPad P52 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu ** Attachment added: "display-settings.png" https://bugs.launchpad.net/bugs/1876523/+attachment/5365379/+files/display-settings.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/1876523 Title: Repositioning display/monitor location in display settings does not relocate appliication location Status in xorg package in Ubuntu: New Bug description: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.10 DISTRIB_CODENAME=eoan DISTRIB_DESCRIPTION="Ubuntu 19.10" Lenovo ThinkPad P52 + Thunderbold dock + 3 monitors I repositioned a monitor in display settings to reflect the actual position. An open application on the monitor was not repositioned with the display. The windows title bar and buttons were not on the display so the window could not be re-positioned. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
[Touch-packages] [Bug 1876516] Re: Mouse cursor lagging (or freezing) when moving over system tray when wayland session
** Summary changed: - Mouse cursor lagging (or freezing) when moving over system tray + Mouse cursor lagging (or freezing) when moving over system tray when wayland session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1876516 Title: Mouse cursor lagging (or freezing) when moving over system tray when wayland session Status in wayland package in Ubuntu: New Bug description: Cursor lagging when using wayland session. It happens on edge of something new, for example: - between clock menu and keyboard langugge - between app window and left launch panel Xorg session has no mouse lagging over this edges. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwayland-client0 1.18.0-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 23:10:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 6320] [144d:c600] InstallationDate: Installed on 2020-04-26 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=b242dbf0-fbe1-4cf8-a5a6-57dd5d749833 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 03PS.M505.20110929.LEO dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 305U1A/305U1A dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 03PS dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr03PS.M505.20110929.LEO:bd09/29/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr03PS:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305U1A/305U1A:rvr03PS:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: 305U1A dmi.product.sku: To be filled by O.E.M. dmi.product.version: 03PS dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1876516/+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 1876518] [NEW] Gtk.Clipboard set_text() not working
Public bug reported:
Writing to Gtk.Clipboard doesn't work (reading works).
Example code:
#!/usr/bin/python3
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk, Gdk
clipboard = Gtk.Clipboard.get(Gdk.SELECTION_CLIPBOARD)
clipboard.set_text("Does a text of all texts contain itself?", -1)
clipboard.store()
Ubuntu 20.04 with Gtk 3.36.0-1
** Affects: pygobject (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1876518
Title:
Gtk.Clipboard set_text() not working
Status in pygobject package in Ubuntu:
New
Bug description:
Writing to Gtk.Clipboard doesn't work (reading works).
Example code:
#!/usr/bin/python3
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk, Gdk
clipboard = Gtk.Clipboard.get(Gdk.SELECTION_CLIPBOARD)
clipboard.set_text("Does a text of all texts contain itself?", -1)
clipboard.store()
Ubuntu 20.04 with Gtk 3.36.0-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1876518/+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 1876519] [NEW] Screens black: scaling to 125% for both monitors
Public bug reported: If I set the scaling of my two QHD monitors to 125%, they remain black when saved. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 22:23:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1070] [3842:6276] InstallationDate: Installed on 2020-05-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=54c03160-c1bb-40d5-8d7f-27e961fd8ee8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4101 dmi.board.asset.tag: Default string dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd07/10/2019:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 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 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/1876519 Title: Screens black: scaling to 125% for both monitors Status in xorg package in Ubuntu: New Bug description: If I set the scaling of my two QHD monitors to 125%, they remain black when saved. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 22:23:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1070] [3842:6276] InstallationDate: Installed on 2020-05-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=54c03160-c1bb-40d5-8d7f-27e961fd8ee8 ro quiet splash vt.handoff=7
[Touch-packages] [Bug 1876516] [NEW] Mouse cursor lagging (or freezing) when moving over system tray when wayland session
Public bug reported: Cursor lagging when using wayland session. It happens on edge of something new, for example: - between clock menu and keyboard langugge - between app window and left launch panel Xorg session has no mouse lagging over this edges. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwayland-client0 1.18.0-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 23:10:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 6320] [144d:c600] InstallationDate: Installed on 2020-04-26 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=b242dbf0-fbe1-4cf8-a5a6-57dd5d749833 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 03PS.M505.20110929.LEO dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 305U1A/305U1A dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 03PS dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr03PS.M505.20110929.LEO:bd09/29/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr03PS:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305U1A/305U1A:rvr03PS:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: 305U1A dmi.product.sku: To be filled by O.E.M. dmi.product.version: 03PS dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu wayland-session ** Summary changed: - mouse cursor lagging (or freezing) when moving over system tray + Mouse cursor lagging (or freezing) when moving over system tray -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1876516 Title: Mouse cursor lagging (or freezing) when moving over system tray when wayland session Status in wayland package in Ubuntu: New Bug description: Cursor lagging when using wayland session. It happens on edge of something new, for example: - between clock menu and keyboard langugge - between app window and left launch panel Xorg session has no mouse lagging over this edges. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwayland-client0 1.18.0-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 23:10:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 6320] [144d:c600] InstallationDate: Installed on 2020-04-26 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=b242dbf0-fbe1-4cf8-a5a6-57dd5d749833 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: No
[Touch-packages] [Bug 1876513] [NEW] .bashrc color_prompt check only works for xterm-color, not xterm-256color
Public bug reported: The `share/dot.bashrc` file checks like this whether to enable `color_prompt`: case "$TERM" in xterm-color) color_prompt=yes;; esac Nowaways, most terminals support 256 colors (instead of 8 like xterm- color). Their $TERM will usually be something like `xterm-256color`. Accordingly, this check was modified in the `skel`-package `/etc/skel/.bashrc` like this: case "$TERM" in xterm-color|*-256color) color_prompt=yes;; esac I would suggest the same modification be done in the base-files .bashrc. ** Affects: base-files (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1876513 Title: .bashrc color_prompt check only works for xterm-color, not xterm- 256color Status in base-files package in Ubuntu: New Bug description: The `share/dot.bashrc` file checks like this whether to enable `color_prompt`: case "$TERM" in xterm-color) color_prompt=yes;; esac Nowaways, most terminals support 256 colors (instead of 8 like xterm- color). Their $TERM will usually be something like `xterm-256color`. Accordingly, this check was modified in the `skel`-package `/etc/skel/.bashrc` like this: case "$TERM" in xterm-color|*-256color) color_prompt=yes;; esac I would suggest the same modification be done in the base-files .bashrc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1876513/+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 1876475] Re: lxc can't assign ipv4 address from lxc-container config file
But in older lxc containers (18 bionic) i do not remove /etc/netplan/10-lxc.yaml (it is full identical with ubuntu 20 lts /etc/netplan/10-lxc.yaml), and there is no problem with ip address assign.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1876475 Title: lxc can't assign ipv4 address from lxc-container config file Status in lxc package in Ubuntu: Invalid Bug description: I created and ran lxc-container with network config - others lxc-config on host system are the same like that (ipv4. addresses is different): __ # Template used to create this container: /usr/share/lxc/templates/lxc-ubuntu # Parameters passed to the template: # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware this has security implications) # Common configuration lxc.include = /usr/share/lxc/config/ubuntu.common.conf lxc.apparmor.profile = unconfined lxc.start.auto = 1 # Container specific configuration lxc.rootfs.path = dir:/var/lib/lxc/video/rootfs lxc.uts.name = video lxc.arch = amd64 # Network configuration lxc.net.0.type = veth lxc.net.0.flags = up lxc.net.0.link = lxcbr0 lxc.net.0.hwaddr = 4a:49:43:49:79:bf lxc.net.0.ipv4.address = 10.0.3.10/24 lxc.net.0.ipv4.gateway = 10.0.3.1 When container started - i can't see ip 10.0.3.10, it is not assigned after start: NAME STATE AUTOSTART GROUPS IPV4 IPV6 UNPRIVILEGED x RUNNING 1 - 10.0.3.2 -false y RUNNING 1 - 10.0.3.3 -false x1 RUNNING 1 - 10.0.3.7 -false x2 RUNNING 1 - 10.0.3.5 -false z3 RUNNING 1 - 10.0.3.4 -false z1 RUNNING 1 - 10.0.3.6 -false video RUNNING 0 - --false <-!!! Example (inside container "z1"): root@z1:/# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Example (inside problem container "video"): root@video:/# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal x,y,x1-3,z3,z1 - ubuntu 18 lts video - Ubuntu 20 LTS, host system ubuntu 20 lts. Host system: root@node:/var/lib/lxc/video# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal BUT! When I restarts all host-system, "video" container assigns ipv4 address after it. And if I stop the "video" container again (lxc-stop) and start the "video" container again (lxc-start -d -n video) - it losts ipv4 address and can't assign it again (from cli). root@node:/home/alex# dpkg -l | grep lxc ii liblxc-common 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools (common tools) ii liblxc1 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools (library) ii lxc 1:4.0.2-0ubuntu1 all Transitional package - lxc -> lxc-utils ii lxc-templates 3.0.4-3ubuntu1 amd64Linux Containers userspace tools (templates) ii lxc-utils 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools rc lxctl 0.3.1+debian-4 all Utility to manage LXC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxc 1:4.0.2-0ubuntu1 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 CasperMD5CheckResult: skip Date: Sat May 2 18:21:44 2020 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: lxc UpgradeStatus: Upgraded to focal on 2020-05-02 (0 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc.conf: lxc.network.link = lxcbr0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1876475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1876475] Re: lxc can't assign ipv4 address from lxc-container config file
1) I done full reinstall host OS. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal 2) create lxc container lxc-create -t ubuntu -n video 3) start container lxc-start -d -n video And no ip address assiged to my lxc container. It is _clear_ lxc container root@video:/# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal I remove /etc/netplan/10-lxc.yaml inside container, and now ip assigend! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1876475 Title: lxc can't assign ipv4 address from lxc-container config file Status in lxc package in Ubuntu: Invalid Bug description: I created and ran lxc-container with network config - others lxc-config on host system are the same like that (ipv4. addresses is different): __ # Template used to create this container: /usr/share/lxc/templates/lxc-ubuntu # Parameters passed to the template: # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware this has security implications) # Common configuration lxc.include = /usr/share/lxc/config/ubuntu.common.conf lxc.apparmor.profile = unconfined lxc.start.auto = 1 # Container specific configuration lxc.rootfs.path = dir:/var/lib/lxc/video/rootfs lxc.uts.name = video lxc.arch = amd64 # Network configuration lxc.net.0.type = veth lxc.net.0.flags = up lxc.net.0.link = lxcbr0 lxc.net.0.hwaddr = 4a:49:43:49:79:bf lxc.net.0.ipv4.address = 10.0.3.10/24 lxc.net.0.ipv4.gateway = 10.0.3.1 When container started - i can't see ip 10.0.3.10, it is not assigned after start: NAME STATE AUTOSTART GROUPS IPV4 IPV6 UNPRIVILEGED x RUNNING 1 - 10.0.3.2 -false y RUNNING 1 - 10.0.3.3 -false x1 RUNNING 1 - 10.0.3.7 -false x2 RUNNING 1 - 10.0.3.5 -false z3 RUNNING 1 - 10.0.3.4 -false z1 RUNNING 1 - 10.0.3.6 -false video RUNNING 0 - --false <-!!! Example (inside container "z1"): root@z1:/# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Example (inside problem container "video"): root@video:/# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal x,y,x1-3,z3,z1 - ubuntu 18 lts video - Ubuntu 20 LTS, host system ubuntu 20 lts. Host system: root@node:/var/lib/lxc/video# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal BUT! When I restarts all host-system, "video" container assigns ipv4 address after it. And if I stop the "video" container again (lxc-stop) and start the "video" container again (lxc-start -d -n video) - it losts ipv4 address and can't assign it again (from cli). root@node:/home/alex# dpkg -l | grep lxc ii liblxc-common 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools (common tools) ii liblxc1 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools (library) ii lxc 1:4.0.2-0ubuntu1 all Transitional package - lxc -> lxc-utils ii lxc-templates 3.0.4-3ubuntu1 amd64Linux Containers userspace tools (templates) ii lxc-utils 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools rc lxctl 0.3.1+debian-4 all Utility to manage LXC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxc 1:4.0.2-0ubuntu1 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 CasperMD5CheckResult: skip Date: Sat May 2 18:21:44 2020 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: lxc UpgradeStatus: Upgraded to focal on 2020-05-02 (0 days ago) defaults.conf: lxc.net.0.type = veth
[Touch-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
** Changed in: libxau (Ubuntu Bionic) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: In Progress Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 38000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+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 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
it have reported too in https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10 with that solution: https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/commit/0732f81a2c67354ddfa7a495bee6b0997c6ef244 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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/linux/+bug/1873895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Asus Zenbook UX533FTC, Ubuntu 20.04 fresh install, dual boot with Windows 10. Same was on Ubuntu 19.10 (dualboot). I already live half a year without sound on my laptop. Can uninstalling Windows to single-boot Ubuntu can help? -- 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/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR 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.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
I have similar problem with xubuntu & ubuntu studio (fresh install or upgrade) , it happen only with some resolutions & without screen rotation. i "solved" it increasing framebuffer in at least 1 pixel, eg: xrandr --fb 1441x900 --output DisplayPort-0 --mode 1440x900 --panning 1440x0 try? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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/linux/+bug/1873895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1876504] [NEW] Gdebi close when trying to install a .deb with right-clic
Public bug reported:
In focal(20.04), gdebi 0.9.5.7+nmu3 has a problem.
In a terminal : sudo gdebi xxx.deb works (but no graphic mode)
In a terminal : sudo gdebi-gtk launch gdebi. Then, in the graphic UI,
choose a .deb file ("file > open"), then clic on "install" and it's
works.
BUT right-clic on the .deb, then "open with gdebi" => gdebi launch, et
show the .deb file. But clic on "install" button, and gdebi close
without any installation.
Solution / workaround :
change in gdebi.desktop the line
exec=gdebi-gtk %f
by :
exec=sh -c "gdebi-gtk %f"
And it's works perfectly.
Please, change the gdebi.desktop in gdebi.deb on focal.
** Affects: gdebi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1876504
Title:
Gdebi close when trying to install a .deb with right-clic
Status in gdebi package in Ubuntu:
New
Bug description:
In focal(20.04), gdebi 0.9.5.7+nmu3 has a problem.
In a terminal : sudo gdebi xxx.deb works (but no graphic mode)
In a terminal : sudo gdebi-gtk launch gdebi. Then, in the graphic UI,
choose a .deb file ("file > open"), then clic on "install" and it's
works.
BUT right-clic on the .deb, then "open with gdebi" => gdebi launch, et
show the .deb file. But clic on "install" button, and gdebi close
without any installation.
Solution / workaround :
change in gdebi.desktop the line
exec=gdebi-gtk %f
by :
exec=sh -c "gdebi-gtk %f"
And it's works perfectly.
Please, change the gdebi.desktop in gdebi.deb on focal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1876504/+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 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]
After disabling apparmor, the dhcp server keeps crashing ... ** Package changed: apparmor (Ubuntu) => isc-dhcp (Ubuntu) -- 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/1872106 Title: isc-dhcp-server crashing constantly [Ubuntu 20.04] Status in isc-dhcp package in Ubuntu: Confirmed Bug description: isc-dhcp-server crashing constantly (sometimes within seconds or minutes, sometimes within hours) with the following error messages: Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service. Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ?? Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ?? Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ?? Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ?? Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ?? Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+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 1442649] Re: nautilus trash doesn't include btrfs and zfs subvolumes
** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #251 https://gitlab.gnome.org/GNOME/glib/issues/251 ** Changed in: glib Importance: Medium => Unknown ** Changed in: glib Status: Expired => Unknown ** Changed in: glib Remote watch: GNOME Bug Tracker #604015 => gitlab.gnome.org/GNOME/glib/issues #251 ** Bug watch removed: GNOME Bug Tracker #604015 https://gitlab.gnome.org/604015 ** No longer affects: nautilus (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #236 https://gitlab.gnome.org/GNOME/gvfs/issues/236 ** Also affects: gvfs via https://gitlab.gnome.org/GNOME/gvfs/issues/236 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1442649 Title: nautilus trash doesn't include btrfs and zfs subvolumes Status in GLib: Unknown Status in gvfs: Unknown Status in glib2.0 package in Ubuntu: Triaged Status in gvfs package in Ubuntu: Triaged Bug description: Files in `/path/to/subvolume/.Trash-1000` aren't listed in the global trash. Comment by bug triage team: comment 4 has a spot-on analysis of where this issue is coming from, an inconsistency between trash handling in gvfs and glib/gio. The problem has been around for quite a while. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1442649/+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 1876495] Re: bash-completion incorrectly shows source package names for APT
Though maybe it only needs work in apt, we'll see. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1876495 Title: bash-completion incorrectly shows source package names for APT Status in apt package in Ubuntu: Triaged Status in bash-completion package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Open terminal, enter one of the commands below 2a. apt install brisk 2b. apt source brisk-menu 2c. apt-get install brisk 2d. apt-get source brisk-menu 2e. apt-cache policy brisk Expected results: * The bash-completion should not lead to package name as there are no binary packages named with starting part "brisk" (see https://packages.ubuntu.com/search?suite=all=names=brisk ) Actual results: * all commands below get completed to the name of source package - in this example named "brisk-menu" (see https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames). This is absolutely unexpected, as user can not really install this package in binary form. ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30 Uname: Linux 5.4.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 2 20:35:48 2020 Dependencies: InstallationDate: Installed on 2020-04-22 (9 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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 1876495] Re: bash-completion incorrectly shows source package names for APT
source is certainly a bad example, as it does take source names. But yes, this is a minor inconvenience sometimes. This needs quite a bit of work to fix, in a coordinated fashion, across the two packages, and I'm not sure it's worth it. Probably needs some investigation whether we already return some other invalid names. ** Changed in: bash-completion (Ubuntu) Importance: Undecided => Medium ** Changed in: bash-completion (Ubuntu) Importance: Medium => Low ** Changed in: apt (Ubuntu) Importance: Undecided => Low ** Changed in: bash-completion (Ubuntu) Status: New => Triaged ** Changed in: apt (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1876495 Title: bash-completion incorrectly shows source package names for APT Status in apt package in Ubuntu: Triaged Status in bash-completion package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Open terminal, enter one of the commands below 2a. apt install brisk 2b. apt source brisk-menu 2c. apt-get install brisk 2d. apt-get source brisk-menu 2e. apt-cache policy brisk Expected results: * The bash-completion should not lead to package name as there are no binary packages named with starting part "brisk" (see https://packages.ubuntu.com/search?suite=all=names=brisk ) Actual results: * all commands below get completed to the name of source package - in this example named "brisk-menu" (see https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames). This is absolutely unexpected, as user can not really install this package in binary form. ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30 Uname: Linux 5.4.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 2 20:35:48 2020 Dependencies: InstallationDate: Installed on 2020-04-22 (9 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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 1876495] [NEW] bash-completion incorrectly shows source package names for APT
Public bug reported: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Open terminal, enter one of the commands below 2a. apt install brisk 2b. apt source brisk-menu 2c. apt-get install brisk 2d. apt-get source brisk-menu 2e. apt-cache policy brisk Expected results: * The bash-completion should not lead to package name as there are no binary packages named with starting part "brisk" (see https://packages.ubuntu.com/search?suite=all=names=brisk ) Actual results: * all commands below get completed to the name of source package - in this example named "brisk-menu" (see https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames). This is absolutely unexpected, as user can not really install this package in binary form. ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30 Uname: Linux 5.4.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 2 20:35:48 2020 Dependencies: InstallationDate: Installed on 2020-04-22 (9 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Affects: bash-completion (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Also affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1876495 Title: bash-completion incorrectly shows source package names for APT Status in apt package in Ubuntu: New Status in bash-completion package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Open terminal, enter one of the commands below 2a. apt install brisk 2b. apt source brisk-menu 2c. apt-get install brisk 2d. apt-get source brisk-menu 2e. apt-cache policy brisk Expected results: * The bash-completion should not lead to package name as there are no binary packages named with starting part "brisk" (see https://packages.ubuntu.com/search?suite=all=names=brisk ) Actual results: * all commands below get completed to the name of source package - in this example named "brisk-menu" (see https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames). This is absolutely unexpected, as user can not really install this package in binary form. ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30 Uname: Linux 5.4.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 2 20:35:48 2020 Dependencies: InstallationDate: Installed on 2020-04-22 (9 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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 1876487] Re: The screen is blinking at a random time
It looks like visual bell goes crazy (but I'm not sure in that). And yes, I love visual bell and usually do enable visual bell instead of audio bell. -- 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/1876487 Title: The screen is blinking at a random time Status in xorg package in Ubuntu: New Bug description: I've seen this error on Dell Latitude E7270 (with an internal video card) as well as Dell Precision 7540 (with NVidia card). I've seen this error on Ubuntu 18.04 and now on 20.04 I've never reported it yet but I think the time has come. In a random time (~ once a couple of weeks) I see a blinking screen. Today I've recorded a video on my phone to show you how it looks. You can see it here: https://youtu.be/JiUu7Ydg6uM This is bug finishes when I do logout from my desktop. Could you help me eliminate this error? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 2 19:28:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-21-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-25-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06db] InstallationDate: Installed on 2020-04-09 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Latitude E7270 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=9427d12e-3c69-4eb4-aa23-52bfe8bd2641 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 0T0V7J dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn0T0V7J:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7270 dmi.product.sku: 06DB 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876487/+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 1876489] [NEW] Xorg freeze
Public bug reported: I am dealing with freezing issues. When I did install Linux from a USB stick, it did freeze in the installation process, so I did the run installation in safe mode (taught changing drivers will help). After Linux is installed, So when I boot up ubuntu, it sometimes(70%) freezes after login, and also it sometimes freezes while I am using it. Sometimes I even can't get to log in before it stacks. Then I need to do a hard reset. Also sound sometimes is not working. I did try to change Nvidia drivers. First I did use 440 drivers. Problem with Nvidia 440 driver second monitor not detected. I did try change to xorg opensource driver it shows black screen after boot - Stops on vendor logo. At the moment I am using Nvidia 435 driver it is working, but freezes a lot. I did try to add nomodeset in grub file - GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset". Then built-in desktop freezes before login with hp logo, bet when I add a second display, Linux work on a second display. Also, in Nvidia settings when I set to performance mode, if I put a power saver, it uses integrated graphics(Intel HD 630), and the second monitor is not detected then. I did have ubuntu 19.04 and did work ok on this laptop, but I would like to use 20.04. Any suggestions? Thanks. I am booting dual boot with windows. Alos battery life is very bad, 3x times worse than windows. I am using TLP, but it doest seem to help a lot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 19:58:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.132, 5.4.0-26-generic, x86_64: installed nvidia, 390.132, 5.4.0-28-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:8519] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] [103c:8519] InstallationDate: Installed on 2020-04-27 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Spectre x360 Convertible 15-df0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=0ccbd646-0752-4cae-98bb-f816acbd2666 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: AMI dmi.bios.version: F.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8519 dmi.board.vendor: HP dmi.board.version: 11.72 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.40:bd11/27/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn8519:rvr11.72:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df0xxx dmi.product.sku: 4UU78EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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 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/1876489 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I am dealing with freezing issues. When I did install Linux from a USB stick, it did freeze in the installation process, so I did the run installation in safe mode (taught changing drivers will help). After Linux is installed, So when I boot up ubuntu, it sometimes(70%) freezes after login, and also it sometimes freezes while I am using it. Sometimes I even can't get to log in before it
[Touch-packages] [Bug 1876488] [NEW] [AWM914, playback] sound stops briefly about every minute
Public bug reported: Plays fine on my Bluetooth device but drops out randomly for only about a half second. Nothing else is being used at the time other than Rhythmbox. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lisa 1863 F pulseaudio /dev/snd/controlC0: lisa 1863 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 2 10:51:33 2020 InstallationDate: Installed on 2020-03-12 (51 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: AWM914 Symptom_PulseAudioLog: May 02 06:57:53 lisa-Legion-Y545-PG0 dbus-daemon[957]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.36' (uid=125 pid=1405 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") May 02 08:04:55 lisa-Legion-Y545-PG0 dbus-daemon[957]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.78" (uid=1000 pid=1863 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.3" (uid=0 pid=953 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [AWM914, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y545 PG0 dmi.modalias: dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0: dmi.product.family: Legion Y545 PG0 dmi.product.name: 81T2 dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0 dmi.product.version: Legion Y545 PG0 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876488 Title: [AWM914, playback] sound stops briefly about every minute Status in alsa-driver package in Ubuntu: New Bug description: Plays fine on my Bluetooth device but drops out randomly for only about a half second. Nothing else is being used at the time other than Rhythmbox. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lisa 1863 F pulseaudio /dev/snd/controlC0: lisa 1863 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 2 10:51:33 2020 InstallationDate: Installed on 2020-03-12 (51 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: AWM914 Symptom_PulseAudioLog: May 02 06:57:53 lisa-Legion-Y545-PG0 dbus-daemon[957]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.36' (uid=125 pid=1405 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") May 02 08:04:55 lisa-Legion-Y545-PG0 dbus-daemon[957]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.78" (uid=1000 pid=1863 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.3" (uid=0 pid=953 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [AWM914, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2019 dmi.bios.vendor:
[Touch-packages] [Bug 1876486] [NEW] Kernel panic booting after 18.04 to 20.04 upgrade
Public bug reported: Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not possible. The error messages is: /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get [4.608900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 See also attached photograph of screen during boot. Upgrade followed steps from here: https://help.ubuntu.com/community/FocalUpgrades/Kubuntu With the excpetion that The -d flag was used for the do-release-upgrade: sudo do-release-upgrade -d -m desktop 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Prior to upgrade: Ubuntu 18.04.4 After upgrade (but never booted): Ubuntu (Kubuntu) 20.04 Note that Ubuntu had originally be installed, but kubuntu-desktop was recently installed to change to Kubuntu, but no booting problems were experienced before updating to 20.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Unknown -- Package version may have changed when upgrading to 20.04. 3) What you expected to happen Boot without kernel panic. 4) What happened instead Could not boot. Even selecting safe mode from grub could not boot. Had to restore system from backups. Will not attempt upgrade again. ** Affects: libseccomp (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Attachment added: "Screen photograph of kernel panic during boot" https://bugs.launchpad.net/bugs/1876486/+attachment/5365144/+files/20200501_233503.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade Status in libseccomp package in Ubuntu: New Bug description: Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not possible. The error messages is: /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get [4.608900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 See also attached photograph of screen during boot. Upgrade followed steps from here: https://help.ubuntu.com/community/FocalUpgrades/Kubuntu With the excpetion that The -d flag was used for the do-release-upgrade: sudo do-release-upgrade -d -m desktop 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Prior to upgrade: Ubuntu 18.04.4 After upgrade (but never booted): Ubuntu (Kubuntu) 20.04 Note that Ubuntu had originally be installed, but kubuntu-desktop was recently installed to change to Kubuntu, but no booting problems were experienced before updating to 20.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Unknown -- Package version may have changed when upgrading to 20.04. 3) What you expected to happen Boot without kernel panic. 4) What happened instead Could not boot. Even selecting safe mode from grub could not boot. Had to restore system from backups. Will not attempt upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+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 1876487] [NEW] The screen is blinking at a random time
Public bug reported: I've seen this error on Dell Latitude E7270 (with an internal video card) as well as Dell Precision 7540 (with NVidia card). I've seen this error on Ubuntu 18.04 and now on 20.04 I've never reported it yet but I think the time has come. In a random time (~ once a couple of weeks) I see a blinking screen. Today I've recorded a video on my phone to show you how it looks. You can see it here: https://youtu.be/JiUu7Ydg6uM This is bug finishes when I do logout from my desktop. Could you help me eliminate this error? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 2 19:28:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-21-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-25-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06db] InstallationDate: Installed on 2020-04-09 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Latitude E7270 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=9427d12e-3c69-4eb4-aa23-52bfe8bd2641 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 0T0V7J dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn0T0V7J:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7270 dmi.product.sku: 06DB 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876487 Title: The screen is blinking at a random time Status in xorg package in Ubuntu: New Bug description: I've seen this error on Dell Latitude E7270 (with an internal video card) as well as Dell Precision 7540 (with NVidia card). I've seen this error on Ubuntu 18.04 and now on 20.04 I've never reported it yet but I think the time has come. In a random time (~ once a couple of weeks) I see a blinking screen. Today I've recorded a video on my phone to show you how it looks. You can see it here: https://youtu.be/JiUu7Ydg6uM This is bug finishes when I do logout from my desktop. Could you help me eliminate this error? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 2 19:28:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-21-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-25-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06db] InstallationDate: Installed on 2020-04-09 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Latitude E7270 ProcKernelCmdLine:
[Touch-packages] [Bug 1876484] [NEW] [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Speaker, Internal] No sound at all
Public bug reported: Hi, I have a problem with the sound. It doesn't work, it did work only once. When I did add Bluetooth speakers to it. https://i.imgur.com/2cyJwVJ.png - here speaker But now it recognizes speakers and built-in speakers, but no sound at all. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 2 19:23:55 2020 InstallationDate: Installed on 2020-04-27 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: AMI dmi.bios.version: F.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8519 dmi.board.vendor: HP dmi.board.version: 11.72 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.40:bd11/27/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn8519:rvr11.72:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df0xxx dmi.product.sku: 4UU78EA#ABD dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876484 Title: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hi, I have a problem with the sound. It doesn't work, it did work only once. When I did add Bluetooth speakers to it. https://i.imgur.com/2cyJwVJ.png - here speaker But now it recognizes speakers and built-in speakers, but no sound at all. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 2 19:23:55 2020 InstallationDate: Installed on 2020-04-27 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: AMI dmi.bios.version: F.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8519 dmi.board.vendor: HP dmi.board.version: 11.72 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.40:bd11/27/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn8519:rvr11.72:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df0xxx dmi.product.sku: 4UU78EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876484/+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 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
Hello Lucas, Thanks for taking this up. Yes I can provide you the required information. Why I believe this is a bug, is due to using putty there were no issues. So ssh client is causing the issue. For fixing reducing the MTU of VPN tunnel interface fixed the issue. So I think there is still a problem with ssh client with negotiating the SSH communication. === $dpkg -l | grep -i openssh ii openssh-client 1:7.2p2-4ubuntu2.8 --> ii openssh-server 1:7.2p2-4ubuntu2.8 ii openssh-sftp-server 1:7.2p2-4ubuntu2.8 $cat /etc/ssh/ssh_config # This is the ssh client system-wide configuration file. See # ssh_config(5) for more information. This file provides defaults for # users, and the values can be changed in per-user configuration files # or on the command line. # Configuration data is parsed as follows: # 1. command line options # 2. user-specific file # 3. system-wide file # Any configuration value is only changed the first time it is set. # Thus, host-specific definitions should be at the beginning of the # configuration file, and defaults at the end. # Site-wide defaults for some commonly used options. For a comprehensive # list of available options, their meanings and defaults, please see the # ssh_config(5) man page. Host * # ForwardAgent no # ForwardX11 no # ForwardX11Trusted yes # RhostsRSAAuthentication no # RSAAuthentication yes # PasswordAuthentication yes # HostbasedAuthentication no # GSSAPIAuthentication no # GSSAPIDelegateCredentials no # GSSAPIKeyExchange no # GSSAPITrustDNS no # BatchMode no # CheckHostIP yes # AddressFamily any # ConnectTimeout 0 # StrictHostKeyChecking ask # IdentityFile ~/.ssh/identity # IdentityFile ~/.ssh/id_rsa # IdentityFile ~/.ssh/id_dsa # IdentityFile ~/.ssh/id_ecdsa # IdentityFile ~/.ssh/id_ed25519 # Port 22 # Protocol 2 # Cipher 3des # Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc # MACs hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160 # EscapeChar ~ # Tunnel no # TunnelDevice any:any # PermitLocalCommand no # VisualHostKey no # ProxyCommand ssh -q -W %h:%p gateway.example.com # RekeyLimit 1G 1h SendEnv LANG LC_* HashKnownHosts yes GSSAPIAuthentication yes GSSAPIDelegateCredentials no ForwardX11Trusted yes ForwardX11Timeout 596h For VPN client connection we are using open-connect, so usually connect via $sudo openconnect $dpkg -l | grep openconnect ii libopenconnect5:amd64 7.06-2build2 amd64open client for Cisco AnyConnect VPN - shared library ii openconnect7.06-2build2 amd64open client for Cisco AnyConnect VPN I'm marking this bug status to confirmed. Thanks Jay ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: Incomplete Status in openvpn package in Ubuntu: Incomplete Bug description: Hello Team, SSH timeout issue, once connect to VPN. Environment == Dell XPS 9570 Ubuntu 16.04.6 Xenial Xerus) kernel - 4.15.0-55-generic $dpkg -l | grep -i openssh ii openssh-client 1:7.2p2-4ubuntu2.8 --> ii openssh-server 1:7.2p2-4ubuntu2.8 ii openssh-sftp-server 1:7.2p2-4ubuntu2.8 VPN tunnel info vpn0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:IP P-t-P:xx Mask:255.255.252.0 inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1406 Metric:1 RX packets:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:87839 (87.8 KB) TX bytes:238740 (238.7 KB) Issue Unable to connect to any host via ssh or sftp after VPN connection Tried = Reinstalled the openssh-client package and still no luck. May I know why the default cipher is not taking/hanging? Please let me know . There were no recent changes. Workaround === Able to connect to ssh / sftp $ssh -c aes128-ctr user@IP Below is the debug ssh client logs === == $ssh -vvv user@ip OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "IP" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to IP [IP]
[Touch-packages] [Bug 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify
Thank you Simon and Seth, for your quick response. I have looked into this further by installing a virgin Ubuntu Server 20.04 with SSH. Changing the 'Port' in /etc/ssh/sshd_config to 7722 starts sshd on port 7722 and NOT on port 22, just like you said, Simon. BUT: Rename sshd_config to something_else and replace sshd_config with two lines to include the original config (now called something_else) and set the Port to 7722: systemctl stop ssh mv /etc/ssh/sshd_config /etc/ssh/something_else cat > /etc/ssh/sshd_config
[Touch-packages] [Bug 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
According to #11, your usb sound card fails in the pulseaudio, could you please remove the usb and test. If that doesn't help, I guess you must install some package that conflict with pulseaudio, that can explain #10. If possible, please collect a pulseaudio.txt without usb sound card. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+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 1876475] [NEW] lxc can't assign ipv4 address from lxc-container config file
Public bug reported: I created and ran lxc-container with network config - others lxc-config on host system are the same like that (ipv4. addresses is different): __ # Template used to create this container: /usr/share/lxc/templates/lxc-ubuntu # Parameters passed to the template: # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware this has security implications) # Common configuration lxc.include = /usr/share/lxc/config/ubuntu.common.conf lxc.apparmor.profile = unconfined lxc.start.auto = 1 # Container specific configuration lxc.rootfs.path = dir:/var/lib/lxc/video/rootfs lxc.uts.name = video lxc.arch = amd64 # Network configuration lxc.net.0.type = veth lxc.net.0.flags = up lxc.net.0.link = lxcbr0 lxc.net.0.hwaddr = 4a:49:43:49:79:bf lxc.net.0.ipv4.address = 10.0.3.10/24 lxc.net.0.ipv4.gateway = 10.0.3.1 When container started - i can't see ip 10.0.3.10, it is not assigned after start: NAME STATE AUTOSTART GROUPS IPV4 IPV6 UNPRIVILEGED x RUNNING 1 - 10.0.3.2 -false y RUNNING 1 - 10.0.3.3 -false x1 RUNNING 1 - 10.0.3.7 -false x2 RUNNING 1 - 10.0.3.5 -false z3 RUNNING 1 - 10.0.3.4 -false z1 RUNNING 1 - 10.0.3.6 -false video RUNNING 0 - --false <-!!! Example (inside container "z1"): root@z1:/# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic Example (inside problem container "video"): root@video:/# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal x,y,x1-3,z3,z1 - ubuntu 18 lts video - Ubuntu 20 LTS, host system ubuntu 20 lts. Host system: root@node:/var/lib/lxc/video# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal BUT! When I restarts all host-system, "video" container assigns ipv4 address after it. And if I stop the "video" container again (lxc-stop) and start the "video" container again (lxc-start -d -n video) - it losts ipv4 address and can't assign it again (from cli). root@node:/home/alex# dpkg -l | grep lxc ii liblxc-common 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools (common tools) ii liblxc1 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools (library) ii lxc 1:4.0.2-0ubuntu1 all Transitional package - lxc -> lxc-utils ii lxc-templates 3.0.4-3ubuntu1 amd64Linux Containers userspace tools (templates) ii lxc-utils 1:4.0.2-0ubuntu1 amd64Linux Containers userspace tools rc lxctl 0.3.1+debian-4all Utility to manage LXC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxc 1:4.0.2-0ubuntu1 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 CasperMD5CheckResult: skip Date: Sat May 2 18:21:44 2020 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: lxc UpgradeStatus: Upgraded to focal on 2020-05-02 (0 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc.conf: lxc.network.link = lxcbr0 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1876475 Title: lxc can't assign ipv4 address from lxc-container config file Status in lxc package in Ubuntu: New Bug description: I created and ran lxc-container with network config - others lxc-config on host system are the same like that (ipv4. addresses is different): __ # Template used to create this container: /usr/share/lxc/templates/lxc-ubuntu # Parameters passed to the template: # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware
[Touch-packages] [Bug 1876474] [NEW] Dock disappears
Public bug reported: The Dock does not appear after the system went into "Blank Screen" (Standby) if I had a fullscreen Youtube Video paused while it went into standby. Pressing the super key twice brings the dock back. Probably related to me using multiple monitors, with firefox fullscreen on one of them. I hope I somewhat correctly categorized the bug, never did this before. If I should write firefox instead please let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 8.4.0 (Ubuntu 8.4.0-1ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 17:28:46 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-96-generic, x86_64: installed nvidia, 390.116, 4.15.0-99-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1070 Ti] [3842:6678] InstallationDate: Installed on 2019-05-10 (358 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Z390 UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=fcde5350-6206-d501-90d2-53506206d501 ro quiet splash vt.handoff=1 Renderer: Software 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: F10c dmi.board.asset.tag: Default string dmi.board.name: Z390 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10c:bd12/18/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ390UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z390 UD dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876474 Title: Dock disappears Status in xorg package in Ubuntu: New Bug description: The Dock does not appear after the system went into "Blank Screen" (Standby) if I had a fullscreen Youtube Video paused while it went into standby. Pressing the super key twice brings the dock back. Probably related to me using multiple monitors, with firefox fullscreen on one of them. I hope I somewhat correctly categorized the bug, never did this before. If I should write firefox instead please let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 8.4.0 (Ubuntu 8.4.0-1ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set
[Touch-packages] [Bug 1876473] [NEW] Displayport Audio Only Works Occasionally
Public bug reported: See https://askubuntu.com/questions/1226230/display-port-audio-pass- through-issue ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1483 F pulseaudio /dev/snd/controlC1: alex 1483 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 2 11:08:04 2020 InstallationDate: Installed on 2020-03-22 (40 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Sound works for a while, then breaks Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0404 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0404:bd07/03/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug audio eoan -- 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/1876473 Title: Displayport Audio Only Works Occasionally Status in alsa-driver package in Ubuntu: New Bug description: See https://askubuntu.com/questions/1226230/display-port-audio-pass- through-issue ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1483 F pulseaudio /dev/snd/controlC1: alex 1483 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 2 11:08:04 2020 InstallationDate: Installed on 2020-03-22 (40 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Sound works for a while, then breaks Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0404 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0404:bd07/03/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876473/+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 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
#9 requested pulseaudio.txt attached. ** Attachment added: "pulseaudio.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+attachment/5365059/+files/pulseaudio.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
Seb, what should we do if I have a fix in hand? Tag it failed, then re-upload one with proper fix? -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1875369] Re: recording device won't change
ok did that. a new and populated .config/pulse was created upon launch of pavucontrol-qt. bug still present as described. thank you, happy to keep trying things.. -- 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/1875369 Title: recording device won't change Status in pulseaudio package in Ubuntu: Incomplete Bug description: installed from lubuntu .iso fully updated as of yesterday fresh boot this morning some of these details are most likely irrelevant, but it's what i do to keep things simple: ignore graphical login screen, change to VT2 startx /usr/bin/xterm in the xterm: /opt/firefox/firefox& #(nightly) openbox& pavucontrol-qt& pavucontrol&#results are the same regardless which of the pavucontrols is invoked in firefox: voice.google.com start a call in either of the pavucontrols: try to change the recording device: the menu opens, select the desired device, but it just doesn't change. doesn't matter which of the two pavucontrols was invoked ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 27 07:49:12 2020 InstallationDate: Installed on 2020-03-15 (42 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) 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: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875369/+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 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
Tested Ubuntu 20.04 LTS liveCD and the sounds work correctly. System recognizes in the Settings>Sound output devices the following: "Speakers-Built-in Audio" "Digital Output (S/PDIF-Built-in Audio)" -- 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/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+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 1876463] [NEW] [Inspiron 5379, Realtek ALC3253, Speaker, Internal] No sound at all. Also not working for external headphones or internal microphone
Public bug reported: Description:Ubuntu 18.04.4 LTS Release:18.04 No sound playing on internal speakers, headphones (bluetooth which now no longer connect, or when plugged in through a wire) or wired earphones. Internal microphone also not working. Issue seems to have arisen following latest software update within Ubuntu 18.04. These all work fine on the Windows partition I also have on the Dell Inspiron 5379 machine. Attempts tried that had no effect: 1. Muting and un-muting speakers through settings (internal speakers are recognised but not playing). 2. Muting and un-muting, changing sound levels and sound card in alsamixer. 4. Running sudo alsa force-reload 5. Updating Ubuntu software and rebooting. 6. Checking input and output devices on pavucontrol (can see built-in audio analogue stereo sound slider is responding to e.g. youtube videos, but no sound actually produced. 7. Running rm -r ~/.config/pulse; pulseaudio -k, then rebooting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robertv6001 F pulseaudio /dev/snd/controlC1: robertv6001 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 2 14:51:24 2020 InstallationDate: Installed on 2018-09-16 (593 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1179 F pulseaudio robertv6001 F pulseaudio /dev/snd/controlC1: gdm1179 F pulseaudio robertv6001 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 5379, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0CG9YN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd03/05/2020:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0CG9YN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Sound is picked up in pavucontrol but cannot hear anyting" https://bugs.launchpad.net/bugs/1876463/+attachment/5365043/+files/sound_pavucontrol.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876463 Title: [Inspiron 5379, Realtek ALC3253, Speaker, Internal] No sound at all. Also not working for external headphones or internal microphone Status in alsa-driver package in Ubuntu: New Bug description: Description: Ubuntu 18.04.4 LTS Release: 18.04 No sound playing on internal speakers, headphones (bluetooth which now no longer connect, or when plugged in through a wire) or wired earphones. Internal microphone also not working. Issue seems to have arisen following latest software update within Ubuntu 18.04. These all work fine on the Windows partition I also have on the Dell Inspiron 5379 machine. Attempts tried that had no effect: 1. Muting and un-muting speakers through settings (internal speakers are recognised but not playing). 2. Muting and un-muting, changing sound levels and sound card in alsamixer. 4. Running sudo alsa force-reload 5. Updating Ubuntu software and rebooting. 6. Checking input and output devices on pavucontrol (can see built-in audio analogue stereo sound slider is responding to e.g. youtube videos, but no sound actually produced. 7. Running rm -r ~/.config/pulse; pulseaudio -k, then rebooting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robertv6001 F pulseaudio /dev/snd/controlC1: robertv6001 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 2 14:51:24 2020 InstallationDate: Installed on 2018-09-16 (593 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage:
[Touch-packages] [Bug 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
@Jere, No,your problem is not same as the ones in the #8. I need the log of pulseaudio, maybe that will help, to do so: edit /usr/lib/systemd/user/pulseaudio.service comment out the line of ExecStart= add a new line ExecStart=/usr/bin/pulseaudio - --log-target=file:/tmp/pulseaudio.txt reboot then upload the /tmp/pulseaudio.txt thx. -- 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/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard
@Kai-Heng Feng Mine is okay,too. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873384 A little suggestion: can you make a pop-up dialogue like ubuntu to choose headphone/headset/mic? It will makes a lot easier to use headphone/headset for KDE and Xfce4 users. Thanks a lot. Now I can use my headset's mic. -- 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/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Confirmed Bug description: After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters
> Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
This isn't because the file doesn't exist, because the udev rule checks
for its existence before trying to write to it. The error is because
the kernel is rejecting the write to its state file for some reason. In
a really quick test, it seems like this is because it's already online;
the kernel default has been CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=y since
at least 4.15.
I think the error message is harmless, since the memory is already
online, but the udev rule should be fixed to check if it's offline
before actually trying to online it.
Can you test with the systemd from this ppa to see if the error message is gone?
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1876018
Also please make sure all your memory and cpus are online after
booting/hotadding.
Note that I might just remove this rule entirely, since it really
shouldn't be needed anymore, now that the kernel default is to online
hotplugged cpus/memory, but I want to verify that first.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1876018
Title:
40-vm-hotadd.rules attempts to set non-existent sysfs parameters
Status in systemd package in Ubuntu:
New
Bug description:
In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
resulting in warnings such as:
Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
removed, or something else. This behavior is present on systems
upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
first reboot of the VM.
udev: 245.4-4ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+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 1870945] Re: ubuntu-disable-trigger.patch is effectively not enabled
** Changed in: ibus Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1870945 Title: ubuntu-disable-trigger.patch is effectively not enabled Status in ibus: New Status in ibus package in Ubuntu: In Progress Bug description: ubuntu-disable-trigger.patch has effectively not been enabled since XDG_CURRENT_DESKTOP was turned into a list of values instead of a single value. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1870945/+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 1876444] [NEW] Terratec 6Fire DMX snd-usb-6fire 2-4:1.0: unable to receive device firmware state.
Public bug reported: The external USB Audio Interface Terratec DMX 6Fire is not working. Connecting it gives the following output in dmesg: [ 652.274154] usb 2-4: USB disconnect, device number 5 [ 656.978219] usb 2-4: new high-speed USB device number 8 using xhci_hcd [ 657.000514] usb 2-4: New USB device found, idVendor=0ccd, idProduct=0080, bcdDevice= 1.01 [ 657.000519] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 657.000522] usb 2-4: Product: DMX 6Fire USB [ 657.000524] usb 2-4: Manufacturer: TerraTec [ 657.000527] usb 2-4: SerialNumber: 000A468B [ 657.001019] snd-usb-6fire 2-4:1.0: unable to receive device firmware state. [ 657.001032] snd-usb-6fire: probe of 2-4:1.0 failed with error -11 I used an unaltered 20.04 live USB enviroment to rule out other packages I might have installed. 1) Release: Description:Ubuntu 20.04 LTS Release:20.04 2) Version of package: Not sure about that. My guess is, that it is related to module snd-usb-6fire so here is the output of modinfo filename: /lib/modules/5.4.0-26-generic/kernel/sound/usb/6fire/snd-usb-6fire.ko license:GPL v2 description:TerraTec DMX 6Fire USB audio driver author: Torsten Schenk firmware: 6fire/dmx6firecf.bin firmware: 6fire/dmx6fireap.ihx firmware: 6fire/dmx6firel2.ihx srcversion: CB3529736C1EBE5A8B098F3 alias: usb:v0CCDp0080d*dc*dsc*dp*ic*isc*ip*in* depends:snd-pcm,snd-rawmidi,snd retpoline: Y intree: Y name: snd_usb_6fire vermagic: 5.4.0-26-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:2E:1C:6B:CE:DF:4D:6E:F0:5B:25:79:E8:B6:0E:F2:9A:9A:01:CB:AF sig_hashalgo: sha512 signature: 5B:92:9F:53:6C:E5:1E:2F:09:1E:D0:45:8C:43:DF:7D:B9:21:C2:43: B0:84:7E:FC:1D:BA:AC:32:75:51:FA:68:A9:05:BB:29:15:F3:DE:8B: AE:10:1F:4A:9B:0F:C5:C9:2F:B0:06:DB:71:9B:5A:A1:8F:32:F5:51: 35:73:B0:7A:0B:4A:96:F1:4E:02:68:27:C3:F7:1B:58:20:B6:36:43: 6C:93:3F:07:FB:35:0D:F3:D4:E1:B3:77:70:DD:2F:AD:5F:C4:E3:8B: F4:19:5D:00:84:7E:F7:7B:F4:BC:A0:1E:BF:9B:F2:7B:6E:68:D9:B0: 9E:89:E3:3C:1B:93:AC:FB:1F:29:55:7C:99:D8:D5:2C:08:B4:39:70: 7C:FE:09:98:DE:C0:C8:BE:B5:81:B4:F6:2E:86:82:F6:35:1B:7A:72: 5C:51:55:29:21:76:92:05:5A:EF:65:DA:14:44:35:F6:98:ED:44:C7: 3D:67:2E:90:DC:5D:18:AD:45:AE:C3:E7:06:CF:40:07:4E:32:D9:39: D8:27:0F:2A:06:66:FC:C5:79:B4:25:58:44:57:23:80:DB:2C:86:0C: 82:11:3F:B1:12:43:0B:74:FD:2C:AA:84:3F:48:3E:5A:4B:D8:B4:2D: 0D:E8:8D:AE:42:EF:AE:1D:CF:1B:00:27:3D:D6:7D:01:E4:ED:9A:FC: BF:8B:D9:F3:D9:50:DE:37:4D:D5:87:3E:95:E0:80:5D:E3:5C:F7:38: C8:37:86:FE:B1:AE:C9:39:75:22:B0:85:27:88:46:6D:DC:F8:75:18: F9:F1:AC:4A:8B:EA:9B:D8:CB:5C:02:B8:07:CE:94:B7:6A:D4:D4:DD: 72:89:CF:FE:ED:FD:1F:5C:3C:A2:A8:75:8F:B2:D9:85:20:AD:8D:08: 01:DB:37:46:07:78:2E:3C:EF:26:8E:E4:43:37:74:55:0C:8A:2A:96: 8E:2C:A0:B5:7D:45:FE:1D:F6:1B:BF:42:57:B8:A5:B6:1D:24:17:69: 0F:88:1C:DC:F1:A9:81:C1:E0:05:B1:F5:80:58:C6:B2:F5:13:36:76: 7B:97:B0:49:13:BA:7B:36:18:D3:46:4E:77:1C:23:29:61:F4:0D:B4: DE:79:CC:0D:CE:15:E7:5F:70:6F:15:DD:A1:3F:97:D1:18:D7:DB:F5: 59:B8:E2:46:AE:EF:A7:C2:9E:E2:52:F5:1F:0C:D3:43:04:EE:7F:02: 18:84:65:48:04:B5:88:CC:21:7C:C3:09:0A:70:DF:8E:A4:DD:A9:FF: F3:DC:0A:24:B2:28:BF:A0:AB:91:22:4E:81:BE:9E:81:B1:9E:CC:81: C9:65:28:E1:8F:46:5B:13:97:A3:BC:4D parm: index:Index value for the 6fire sound device (array of int) parm: id:ID string for the 6fire sound device. (array of charp) parm: enable:Enable the 6fire sound device. (array of bool) 3) What you expected to happen That I can use the inputs and outputs of the audio device 4) What happened instead Alsa is not detecting the device. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 5415 F pulseaudio /dev/snd/controlC0: ubuntu 5415 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Sat May 2 10:49:14 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade
[Touch-packages] [Bug 1870945] Re: ubuntu-disable-trigger.patch is effectively not enabled
While the non-working patch was dropped, I have proposed equivalent (working) code upstream: https://github.com/ibus/ibus/issues/ Awaiting upstream's reaction to that, I re-open this bug for now. ** Bug watch added: github.com/ibus/ibus/issues # https://github.com/ibus/ibus/issues/ ** Also affects: ibus via https://github.com/ibus/ibus/issues/ Importance: Unknown Status: Unknown ** Changed in: ibus (Ubuntu) Importance: Low => Medium ** Changed in: ibus (Ubuntu) Status: Fix Released => In Progress ** No longer affects: unity -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1870945 Title: ubuntu-disable-trigger.patch is effectively not enabled Status in ibus: Unknown Status in ibus package in Ubuntu: In Progress Bug description: ubuntu-disable-trigger.patch has effectively not been enabled since XDG_CURRENT_DESKTOP was turned into a list of values instead of a single value. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1870945/+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 1876442] [NEW] chromium causing many audit messages in syslog
Public bug reported: chromium as installed through snap: chromium 81.0.4044.129 1135 latest/stable canonical✓ - $ tail -f /var/log/syslog May 2 12:46:20 master3900x kernel: [56493.196311] audit: type=1326 audit(1588416380.844:3238): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:20 master3900x kernel: [56493.196389] audit: type=1326 audit(1588416380.844:3239): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:29 master3900x kernel: [56501.999823] audit: type=1326 audit(1588416389.648:3240): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:29 master3900x kernel: [56501.35] audit: type=1326 audit(1588416389.648:3241): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56502.993348] audit: type=1326 audit(1588416390.644:3242): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56502.993410] audit: type=1326 audit(1588416390.644:3243): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56503.104490] audit: type=1326 audit(1588416390.752:3244): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56503.104561] audit: type=1326 audit(1588416390.752:3245): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:34 master3900x kernel: [56506.398229] audit: type=1326 audit(1588416394.048:3246): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:34 master3900x kernel: [56506.398318] audit: type=1326 audit(1588416394.048:3247): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:49 master3900x kernel: [56521.357592] audit: type=1326 audit(1588416409.004:3248): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:49 master3900x kernel: [56521.357678] audit: type=1326 audit(1588416409.004:3249): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 ** Affects: chromium (Ubuntu) Importance: Undecided Status: New ** Package changed: alsa-driver (Ubuntu) => chromium (Ubuntu) -- 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/1876442 Title: chromium causing many audit messages in syslog Status in chromium package in Ubuntu: New Bug description: chromium as installed through snap: chromium 81.0.4044.129 1135 latest/stable canonical✓ - $ tail -f /var/log/syslog May 2 12:46:20 master3900x kernel: [56493.196311] audit: type=1326 audit(1588416380.844:3238): auid=4294967295
[Touch-packages] [Bug 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
Can this bug be linked with kernel bugs? Funny that everything was working with Ubuntu 18.04 LTS still. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869799 https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061 -- 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/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+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 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
#3 jackd uninstalled and rebooted. Did not help. === sudo apt-get remove jackd reboot === -- 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/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+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 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
#3 Jackd log attached. ** Attachment added: "Comment for #3" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+attachment/5364957/+files/.jackdrc -- 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/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+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 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
#2 request for Pulseaudio log attached according to following instructions. https://wiki.ubuntu.com/PulseAudio/Log ** Attachment added: "Reply to #2" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+attachment/5364949/+files/pulseverbose.log -- 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/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+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 1876316] Re: Default line out device missing after suspend in 20.04
** Package changed: linphone (Ubuntu) => pulseaudio (Ubuntu) -- 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/1876316 Title: Default line out device missing after suspend in 20.04 Status in pulseaudio package in Ubuntu: New Bug description: After suspending the computer the default sound device is gone and the sound output now defaults to the HDMI out. Resetting pulseaudio with pulseaudio -k makes no difference, removing the user pulseaudio config and killing / restarting the server as explained in some troubleshoot guides doesn't make any difference either. The only solution seems to be to restart the computer. This is happening in two different computers recently updated to 20.04 from 19.10 one of them and from 18.04 the other. Alsamixer seems to show the default sound device but pulseaudio can't see it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876316/+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 1876316] [NEW] Default line out device missing after suspend in 20.04
You have been subscribed to a public bug: After suspending the computer the default sound device is gone and the sound output now defaults to the HDMI out. Resetting pulseaudio with pulseaudio -k makes no difference, removing the user pulseaudio config and killing / restarting the server as explained in some troubleshoot guides doesn't make any difference either. The only solution seems to be to restart the computer. This is happening in two different computers recently updated to 20.04 from 19.10 one of them and from 18.04 the other. Alsamixer seems to show the default sound device but pulseaudio can't see it ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- Default line out device missing after suspend in 20.04 https://bugs.launchpad.net/bugs/1876316 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio 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 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]
It seems to be still an apparmor problem: [1863665.820588] audit: type=1400 audit(1588413129.073:171): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/sys/net/ipv4/ip_local_port_range" pid=38217 comm="dhcpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [1863665.820937] audit: type=1400 audit(1588413129.073:172): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/sys/net/ipv4/ip_local_port_range" pid=38217 comm="dhcpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [1863667.962021] audit: type=1400 audit(1588413131.217:173): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/sys/net/ipv4/ip_local_port_range" pid=38245 comm="dhcpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [1863667.962161] audit: type=1400 audit(1588413131.217:174): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/sys/net/ipv4/ip_local_port_range" pid=38245 comm="dhcpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [1863733.906438] audit: type=1400 audit(1588413197.163:175): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/sys/net/ipv4/ip_local_port_range" pid=38952 comm="dhcpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [1863733.906772] audit: type=1400 audit(1588413197.163:176): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/sys/net/ipv4/ip_local_port_range" pid=38952 comm="dhcpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [1863736.056880] audit: type=1400 audit(1588413199.315:177): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/sys/net/ipv4/ip_local_port_range" pid=38972 comm="dhcpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [1863736.057187] audit: type=1400 audit(1588413199.315:178): apparmor="DENIED" operation="open" profile="/usr/sbin/dhcpd" name="/proc/sys/net/ipv4/ip_local_port_range" pid=38972 comm="dhcpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 -- 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/1872106 Title: isc-dhcp-server crashing constantly [Ubuntu 20.04] Status in apparmor package in Ubuntu: Confirmed Bug description: isc-dhcp-server crashing constantly (sometimes within seconds or minutes, sometimes within hours) with the following error messages: Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service. Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ?? Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ?? Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ?? Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ?? Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ?? Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872106/+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 1876433] [NEW] Black screen after standby - clean Kubuntu on AMD T495
Public bug reported: I installed a fresh Kubuntu 20.04. on my Thinkpad T495 (AMD). No further software, simply clean installation. After every standby the Laptop wakes up, but shows only black screen. No way to get back to Kubuntu desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Sat May 2 11:48:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-05-01 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=537c947f-55fc-4bba-bb91-e7c4b91e39e6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET49W(1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET49W(1.19):bd01/06/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876433 Title: Black screen after standby - clean Kubuntu on AMD T495 Status in xorg package in Ubuntu: New Bug description: I installed a fresh Kubuntu 20.04. on my Thinkpad T495 (AMD). No further software, simply clean installation. After every standby the Laptop wakes up, but shows only black screen. No way to get back to Kubuntu desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Sat May 2 11:48:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-05-01 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=537c947f-55fc-4bba-bb91-e7c4b91e39e6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET49W(1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET49W(1.19):bd01/06/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2
[Touch-packages] [Bug 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]
My system is up to date with the newest package versions. ** Package changed: isc-dhcp (Ubuntu) => apparmor (Ubuntu) -- 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/1872106 Title: isc-dhcp-server crashing constantly [Ubuntu 20.04] Status in apparmor package in Ubuntu: Confirmed Bug description: isc-dhcp-server crashing constantly (sometimes within seconds or minutes, sometimes within hours) with the following error messages: Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service. Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ?? Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ?? Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ?? Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ?? Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ?? Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872106/+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 1859308] Re: software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working
Also affects Intel Corporation Wireless 8260 (rev 3a) on the Ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1859308 Title: software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working Status in software-properties package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 (development branch), as of today, Additional Drivers (software-properties-gtk 0.98.6) reports that the device "Intel Corporation: Wireless-AC 9260" is not working, and suggests using a manually installed driver (cf. screenshot). However the device is working correctly: * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show that its driver iwlwifi is in use * ls /lib/firmware/*9260* show that the appropriate firmware files are present And I am indeed writing this bug report connected to an ac (5 GHz) wifi network, where I can verify a ~130-160 Mbps download speed, so software-properties-gtk shouldn't report the device as not working and suggest manually installing a driver. Not sure why it says so? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 00:53:43 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+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
