[Bug 2059401] [NEW] No sound from Jabra 510 speaker after upgrade to 23.10
Public bug reported:
My Jabra 510 speaker used to work in older releases of Ubuntu but, since
upgrade to 23.10 and switch to pipewire, only the microphone works. If
I select the speaker output in settings or directly in Zoom I hear
nothing.
I found an upstream issue here:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1984. Some
users report that pipewire master fixes the issue.
I tried creating a file /etc/pipewire/pipewire.conf and adding the
configuration from that ticket:
context.properties = {
default.clock.quantum = 2048
default.clock.min-quantum = 1024
default.clock.max-quantum = 4096
}
The Jabra speaker then started working in Zoom but the Ubuntu settings app
showed no devices at all. I'm guessing that the quantum setting worked around
the bug but creating the file overrode some other config that Ubuntu is relying
on. It's not clear how to configure pipewire on ubuntu, upstream seems to use
a different file layout.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pipewire 0.3.79-2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 28 09:23:03 2024
InstallationDate: Installed on 2018-12-11 (1934 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: pipewire
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: pipewire
Importance: Unknown
Status: Unknown
** Affects: pipewire (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #1984
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1984
** Also affects: pipewire via
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1984
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059401
Title:
No sound from Jabra 510 speaker after upgrade to 23.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/pipewire/+bug/2059401/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956386] Re: CVE patch request
Updates for CVE-2021-44224 and CVE-2021-44790 have been released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956386 Title: CVE patch request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1956386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944094] Re: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD
Hey, look what I found! https://gitlab.freedesktop.org/drm/amd/-/issues/1671 there is also https://gitlab.freedesktop.org/drm/amd/-/issues/1438 which is the bug report for the previous legion laptops, that one seems to center around the 4000 series APUs, whereas this time it's centered around the 5000 series. ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1671 https://gitlab.freedesktop.org/drm/amd/-/issues/1671 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1438 https://gitlab.freedesktop.org/drm/amd/-/issues/1438 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944094 Title: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944094] Re: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD
** Also affects: linux (Arch Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944094 Title: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944094] Re: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD
Update to my previous comment - I've extensively tested different configurations (mostly kernel parameters) on my Legion 5 15ach6. I did manage to get the brightness to change when using just the dedicated GPU (selected as such within the BIOS,) using the parameter nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1 and this causes the nvidia gpu to show up in /sys/class/backlight/ alongside the amd one, but both of the /sys/class/backlight/*/brightness files do nothing. In hybrid mode and in integrated only mode (using optimus-manager to do it) acpi_backlight=video/vendor/native/none all do nothing, i tested each individually with amdgpu.backlight=1 and amdgpu.backlight=0, and did not get any hint of a way to control backlight, only the AMD iGPU showed up in /sys/class/backlight/, and changing the brightness value did nothing. Something else of note was that I noticed that when using just the dedicated NVIDIA card, xrandr showed DP-1 as the active montior, while when I was using the AMD iGPU, it was showing as eDP. Does anyone know if the MUX switch needs something from the kernel or nvidia driver to work properly? Is there any way for us to be able to check the position of the switch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944094 Title: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944094] Re: Can't adjust screen backlight on Legion Slim 7 AMD
This seems to also effect the Legion 5 15ach6 (AMD) There are two versions of the legion 5, the 2020 version and the 2021 version. It seems that this issue is fixed on the 2020 version by adding the kernel parameter amdgpu.backlight=0 but I can confirm that this does not fix the issue on the 2021 version, so its likely that the 2021 laptop is suffering from whatever this issue is. I'm guessing that the MUX switch is involved in one way or another, as it means that the NVIDIA dGPU does not have to pass frames through the AMD iGPU, it connects to the display separately, and I'm not sure which GPU actually has control over the brightness control. I wonder if the brightness isn't tied to either GPU, maybe its a separate system entirely? ** Summary changed: - Can't adjust screen backlight on Legion Slim 7 AMD + Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944094 Title: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899193] Re: local denial of service due to parsing bugs in arfile.cc
its laging and not adding my pakadges or exepting my passwords -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899193 Title: local denial of service due to parsing bugs in arfile.cc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1899193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912851] Re: Dell 5530: Trackpad, wifi and thunderbolt screen stop working after upgrade from kernel v5.4 to v5.8
Just booted into 5.8.0-48-generic and it seems to be working :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912851 Title: Dell 5530: Trackpad, wifi and thunderbolt screen stop working after upgrade from kernel v5.4 to v5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1912851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912851] Re: Dell 5530: Trackpad, wifi and thunderbolt screen stop working after upgrade from kernel v5.4 to v5.8
Tried upgrading firmware to latest 1.18.1 but see the same issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912851 Title: Dell 5530: Trackpad, wifi and thunderbolt screen stop working after upgrade from kernel v5.4 to v5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1912851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912851] Re: Dell 5530: Trackpad, wifi and thunderbolt screen stop working after upgrade from kernel v5.4 to v5.8
** Attachment added: "dmesg output on v5.8; seems to be full of ACPI errors" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1912851/+attachment/5459052/+files/dmesg-v5.8.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912851 Title: Dell 5530: Trackpad, wifi and thunderbolt screen stop working after upgrade from kernel v5.4 to v5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1912851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912851] [NEW] Dell 5530: Trackpad, wifi and thunderbolt screen stop working after upgrade from kernel v5.4 to v5.8
Public bug reported: After installing the v5.8 kernel, my laptop becomes unusable with multiple issues: * Trackpad stops working * External screen connected over USB-C stops working * Wifi stops working I collected the apport report to file and then rebooted in v5.4 to send it. On v5.4 this laptop is pretty stable with all three of the above working reliably. Interestingly, the USB hub itself in the monitor works fine because I can use the keyboard through the monitor. It's only the graphics that stops working. Screen stays off when I plug it in. I also noticed that the laptop screen runs in a different resolution rather than the one I selected while v5.4 was installed. I run the screen at half-res to match the DPI of my external screen but it booted in full res so everything was tiny. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-40-generic 5.8.0-40.45~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 22 20:50:57 2021 InstallationDate: Installed on 2018-12-11 (773 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: Upgraded to focal on 2020-05-02 (265 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-10-15T09:26:41.949637 ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: After installing the v5.8 kernel, my laptop becomes unusable with multiple issues: * Trackpad stops working * External screen connected over USB-C stops working * Wifi stops working I collected the apport report to file and then rebooted in v5.4 to send it. On v5.4 this laptop is pretty stable with all three of the above working reliably. + + Interestingly, the USB hub itself in the monitor works fine because I + can use the keyboard through the monitor. It's only the graphics that + stops working. Screen stays off when I plug it in. + + I also noticed that the laptop screen runs in a different resolution + rather than the one I selected while v5.4 was installed. I run the + screen at half-res to match the DPI of my external screen but it booted + in full res so everything was tiny. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-40-generic 5.8.0-40.45~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 22 20:50:57 2021 InstallationDate: Installed on 2018-12-11 (773 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: Upgraded to focal on 2020-05-02 (265 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-10-15T09:26:41.949637 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912851 Title: Dell 5530: Trackpad, wifi and thunderbolt screen stop working after upgrade from kernel v5.4 to v5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1912851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899766] Re: Xorg freeze after selecting large cursor
Found the source of the v4l warnings; I was experimenting with v4lloopback to use a camera as webcam. Disabled that and it's gone away. Unfortunately, /var/crash is empty and I didn't see any report from the right time in the errors webpage. After applying the change to add "Crash" to the crashdb.conf, I still don't see a crash dump in /var/crash after repro. However, I did find that the problem only repros in NVIDIA PRIME mode, not Intel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899766 Title: Xorg freeze after selecting large cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1899766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899766] [NEW] Xorg freeze after selecting large cursor
Public bug reported: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:25:23 2020 DistUpgraded: 2020-05-02 16:08:06,720 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2018-12-11 (672 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (164 days ago) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899766 Title: Xorg freeze after selecting large cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1899766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896229] Re: systemd-networkd thinks it loses its lease every renewal
Doesn't seem to repro on 20.04 with systemd 245.4-4ubuntu3.2 ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896229 Title: systemd-networkd thinks it loses its lease every renewal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896229] Re: systemd-networkd thinks it loses its lease every renewal
** Attachment added: "PCAP of DHCP traffic" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+attachment/5412183/+files/dhcp.pcap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896229 Title: systemd-networkd thinks it loses its lease every renewal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896229] Re: systemd-networkd thinks it loses its lease every renewal
Looks like the restart to enable debug triggered a DHCPDISCOVER, that's the easiest point to use to synchronise the PCAP and the log. Note logs of successful DHCP ACK messages followed by "Lease lost!". ** Attachment added: "systemd-networkd logs" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+attachment/5412184/+files/systemd-networkd.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896229 Title: systemd-networkd thinks it loses its lease every renewal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896229] Re: systemd-networkd thinks it loses its lease every renewal
Hmm, looks like this server is on 19.10, not 20.04 as I'd thought. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896229 Title: systemd-networkd thinks it loses its lease every renewal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896229] [NEW] systemd-networkd thinks it loses its lease every renewal
Public bug reported: With a server running 20.04 on AWS, I noticed connectivity glitches once per half hour. Eventually managed to correlate it with DHCP renewals. Each time systemd-networkd does a renewal, it logs that the lease was lost and goes through a cycle of removing and re-adding the IP and routes (Even though it's the same IP and routes). This causes disruption, especially to SNATted flows; if a packet arrives for an SNATted flow during hte windows where the IP is removed then (I think) the host sends a RST and the flow gets torn down. (In any case, such flows get lost during the glitch.) I'd expect a DHCP renewal to be completely transparent; the IP shouldn't flap, it should just be updated to have a longer lifetime. I managed to capture a PCAP of the DHCP renewals along with a debug log from systemd-networkd. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.11 ProcVersionSignature: User Name 5.3.0-1030.32-aws 5.3.18 Uname: Linux 5.3.0-1030-aws x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 Date: Fri Sep 18 13:05:22 2020 Ec2AMI: ami-0d3d788094d3f0aa9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 t3.large ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-1030-aws root=PARTUUID=e96a8035-01 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-0fc0b0107c428fe19 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnt3.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: t3.large dmi.sys.vendor: Amazon EC2 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896229 Title: systemd-networkd thinks it loses its lease every renewal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895434] Re: Display corruption after suspend with recent kernel update
Tried baking down to kernel -42, which is much older but I'm still seeing the problem. Maybe the issue is not with the kernel, it just happened to occur at the same time :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895434 Title: Display corruption after suspend with recent kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895434] Re: Display corruption after suspend with recent kernel update
Same problem after resuming from hibernation or suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895434 Title: Display corruption after suspend with recent kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895434] Re: Display corruption after suspend with recent kernel update
Tried updating firmware from v1.15.0 to v1.17.1; doesn't seem to have helped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895434 Title: Display corruption after suspend with recent kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895434] Re: Display corruption after suspend with recent kernel update
** Attachment added: "Photo of the problem" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895434/+attachment/5410333/+files/IMG_20200913_110623.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895434 Title: Display corruption after suspend with recent kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895434] Re: Display corruption after suspend with recent kernel update
Looks like the black boxes aren't the only corruption I see; websites like this one aren't rendering properly either, content is smearing like it's not being redrawn properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895434 Title: Display corruption after suspend with recent kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895434] [NEW] Display corruption after suspend with recent kernel update
50 [ 59.251535] ksys_ioctl+0x67/0x90 [ 59.251538] __x64_sys_ioctl+0x1a/0x20 [ 59.251542] do_syscall_64+0x57/0x190 [ 59.251547] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 59.251548] RIP: 0033:0x7fab7c00537b [ 59.251551] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [ 59.251552] RSP: 002b:7fffa3357b68 EFLAGS: 0246 ORIG_RAX: 0010 [ 59.251554] RAX: ffda RBX: 0017 RCX: 7fab7c00537b [ 59.251556] RDX: 7fffa3357c20 RSI: 80685600 RDI: 0017 [ 59.251557] RBP: 7fffa3357d10 R08: R09: 2f5a17cee340 [ 59.251558] R10: R11: 0246 R12: 7fffa3357b90 [ 59.251560] R13: 2f5a17cdb0c0 R14: 2f5a17cee450 R15: 2f5a17cebb70 [ 59.251562] ---[ end trace a46f21f7de3e614d ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaun 2662 F pulseaudio /dev/snd/controlC0: shaun 2662 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 10:51:25 2020 InstallationDate: Installed on 2018-12-11 (641 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (133 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895434 Title: Display corruption after suspend with recent kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882510] [NEW] IRQ/51-SYNA2393 using lots of CPU after suspend/resume
Public bug reported: After a suspend/resume cycle (using "deep" suspend mode), the process IRQ/51-SYNA2393 uses considerable CPU 10+%. Using the trackpad for a few seconds seems to fix the issue. I don't normally use the trackpad while docked so it's a bit annoying to have to remember to use it just to get this problem to go away. Looks like others have hit the same issue; I found this on askubuntu: https://askubuntu.com/questions/1138642/ubuntu-18-04-drains-battery- very-fast-after-wake-up-from-a-deep-sleep ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic 5.4.0.33.38 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaun 2997 F pulseaudio /dev/snd/controlC0: shaun 2997 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 11:30:07 2020 InstallationDate: Installed on 2018-12-11 (544 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (36 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882510 Title: IRQ/51-SYNA2393 using lots of CPU after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
HI My problem returned. When I use analog I run pavucontrol-qt and then I select the correvt input device. I don't know why but it seems like the default audio selector does not work [Shaun .T - Chat @ Spike](https://spikenow.com/r/a/?ref=spike-organic- signature&_ts=hc2k8) [hc2k8] On April 24, 2020 at 21:21 GMT, David Bridson wrote: I'm experiencing the same problem on a fresh install of Ubuntu Mate 20.04 on a Dell XPS 13 9350. Sound works correctly using the internal speakers. If you plug in analog headphones to the 3.5mm jack, there is no sound from the headphones or the internal speakers. All relevant options are unmuted in Sound Settings. The Speaker Test exhibits the same behaviour. Analog headphones worked correctly on this system under 18.04. -- You received this bug notification because you are subscribed to a duplicate bug report (1872146). https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in gnome-control-center: Unknown Status in PulseAudio: New Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: Invalid Status in pulseaudio source package in Focal: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872146] Re: Audio on Headphones stopped working
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 HI I did sudo apt-get install --reinstall alsa-base pulseaudio sudo alsa force-reload Did a restart and it sems to be working now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872146 Title: Audio on Headphones stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872146] Re: Audio on Headphones stopped working
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 Still seems to be the same. I booted from a Manjaro USB Pendrive. The sounds works then on all devices. Back in Kubuntu 20.04 only normal speakers works and Bluetooth HEadsets. Any audio via my Headphone Jack does not. Any info I can get. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872146 Title: Audio on Headphones stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Hi Daniel, > Since your setup only uses gnome-shell in the host and not the guest it Host is KDE Plasma, guest is GNOME => I have problems with clipboard when I close virt-manager or shutdown the guest => no problems So if I remove GNOME from the equation, then it's OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Hi Daniel, Thank you for coming back to me so fast. I don't think it's related to either of those bugs you mentioned. This is happening only when I'm running virtual machines and have "virt- manager" opened. Is it a bug in gnome-shell? It's difficult to say. I'm not experiencing the issue with non-desktop VMs (no X) so it might be something in X11. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873413] [NEW] hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Public bug reported: Could you please try install: - Kubuntu 20.04 Focal desktop on bare metal (laptop) - Upgrade all packages - Install virtualization as usually (qemu-kvm, libvirt, virt-manager) - Install Ubuntu 20.04 inside a VM - upgrade all packages in the VM - Start copying (CTRL+X, CTRL+V) plain text between the Kubuntu on laptop and Ubuntu inside VM? Doesn't take too long - doesn't need to much testing. After a couple of trials, the clipboard will hang and you loose the text in clipboard... I don't remember such issues in past. Copying worked fine when I used virt-manager a couple of years ago. Thank you all great people in Canonical for Ubuntu. Ian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 04:43:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872146] Re: Audio on Headphones stopped working
After I removed it works, but the problems comes back afetr a few hours. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872146 Title: Audio on Headphones stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872146] Re: Audio on Headphones stopped working
After 30 minutes my audio on headphones stopped working again. Pease let me know what other tests I can run. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872146 Title: Audio on Headphones stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1872146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872146] Re: Audio on Headphones stopped working
** Summary changed: - Audio on Headphones dtopped working + Audio on Headphones stopped working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872146 Title: Audio on Headphones stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1872146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872146] Re: Audio on Headphones dtopped working
Hi It is working, I installed pulseaudio-module-gsettings. And set Automatically switch all running streams when a new output becomes availible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872146 Title: Audio on Headphones dtopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1872146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872146] [NEW] Audio on Headphones dtopped working
Public bug reported: Audio via my headphones worked yesterday, Today no such luck. When I plug in my headphone, Plasma picks it up but no sound. Bluetooth headset still works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Apr 10 23:03:09 2020 InstallationDate: Installed on 2020-04-05 (5 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404) PackageArchitecture: all ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872146 Title: Audio on Headphones dtopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1872146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869814] Re: ubuntu-docs build failure - possible solution
So in general, syntax errors in translations just cause a warning, and the original text is used. itstool only errors on syntax if you pass --strict, and yelp.m4 doesn't even give you a way to pass --strict. There's a chance this is itstool's fault. You do still have to do memory management with libxml2's Python bindings, so stuff like double frees in application code is possible. But since this crash happens during error reporting for a language with many-byte UTF-8 chars, and since it weirdly only happens with Python 3, I suspect it's this libxml2 bug: https://bugzilla.gnome.org/show_bug.cgi?id=789714 ** Bug watch added: bugzilla.gnome.org/ #789714 https://bugzilla.gnome.org/show_bug.cgi?id=789714 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869814 Title: ubuntu-docs build failure - possible solution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834583] Re: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus()
I was hitting this on disco-proposed. I found that it was resolved by setting an APT priority of -1 for disco-proposed and doing a dist- upgrade (i.e. downgrading all packages to disco-updates). I found that downgrading mutter and gnome-shell was insufficient (I guess there are lots of related libraries). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834583 Title: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1834583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835420] Re: Gnome-shell unresponsive, using 100% cpu
** Attachment added: "GDB backtraces" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835420/+attachment/5275066/+files/gdb.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835420 Title: Gnome-shell unresponsive, using 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835420] [NEW] Gnome-shell unresponsive, using 100% cpu
Public bug reported: Was typing in a text box in goland (java based IDE). Desktop froze so I switched to a try and collected diags. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Thu Jul 4 15:07:39 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-11 (204 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1~19.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-24 (71 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835420 Title: Gnome-shell unresponsive, using 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
Yes, will see if I can borrow a Windows laptop to do that. How would I switch to hid-microsoft? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
Attaching the dmesg.log with dyndgg=+p Device that disconnected was "Microsoft Comfort Curve Keyboard" ** Attachment added: "dmesg with usbcore.dyndbg=+p" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+attachment/5258924/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258721/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258719/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258720/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
Upgraded to 19.04, which has a kernel that works with the dock and attached the diagnostics. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258718/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258713/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258716/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258714/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258717/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258715/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258712/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258709/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258710/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258711/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
apport information ** Tags added: apport-collected ** Description changed: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. - Other devices disconnect too but the pattern is different. Much more - likely to see the disconnect under heavy load, such as webcam/headset - getting disconnected during a conference call. + Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC4: shaun 2837 F pulseaudio + /dev/snd/controlC3: shaun 2837 F pulseaudio + /dev/snd/controlC1: shaun 2837 F pulseaudio + /dev/snd/controlC0: shaun 2837 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2018-12-11 (133 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + MachineType: Dell Inc. Precision 5530 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-13-generic N/A + linux-backports-modules-5.0.0-13-generic N/A + linux-firmware1.178 + Tags: disco + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 02/01/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.8.1 + dmi.board.name: 0FP2W2 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: Precision + dmi.product.name: Precision 5530 + dmi.product.sku: 087D + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258707/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258708/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
another datapoint: kernel 5.0.4 from UKUU doesn't show the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752165 Title: TB16 dock freezes X on hotplug when used with external displays To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1752165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
I tried the latest kernel on 18.10 but still see the issue: 4.18.0-17. Dell Precision 5530, Intel+NVIDIA graphics with Intel graphics selected. I'm also using the workaround from https://bugs.freedesktop.org/show_bug.cgi?id=109675, which prevents the screen from "shuffling" back and forth after plugging in the dock. ** Bug watch added: freedesktop.org Bugzilla #109675 https://bugs.freedesktop.org/show_bug.cgi?id=109675 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752165 Title: TB16 dock freezes X on hotplug when used with external displays To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1752165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
Dock is unusable with current Ubuntu kernel (screen locks up) as per https://bugs.launchpad.net/dell-sputnik/+bug/1752165 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
** Attachment added: "lspci output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+attachment/5250165/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822089] [NEW] Frequent (silent) USB disconnects with Dell TB16 dock
Public bug reported: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
Following kernel seems to fix the issue (running on 18.10 with kernel installed by UKUU): 4.20.0-042000-generic #201812232030 SMP Mon Dec 24 01:32:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I still see one or two of these errors when hotplugging but the others are gone and the external screen works: [drm:intel_mst_pre_enable_dp [i915]] *ERROR* failed to allocate vcpi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752165 Title: TB16 dock freezes X on hotplug when used with external displays To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1752165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
Still seems to be an issue; I tried 4.18.16 on 18.10 and it didn't help (nor did the most recent 4.19 kernel in UKUU). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752165 Title: TB16 dock freezes X on hotplug when used with external displays To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1752165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1531220] Re: Setting Preferences Application for PDF to 'Always ask' or 'Download' results in failed download
A very *old* bug post! Yes, this was fixed some time back - clear to close I think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1531220 Title: Setting Preferences Application for PDF to 'Always ask' or 'Download' results in failed download To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1531220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775812] [NEW] instal error
Public bug reported: coudn insyall due to hdd ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubiquity 17.04.9 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CasperVersion: 1.380 Date: Fri Jun 8 11:22:27 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: LANGUAGE=en_GB.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-17.04.9 ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775812 Title: instal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1775812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768552] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1768552/+attachment/5132102/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768552 Title: apt-add-repository fails to add key for PPA with non-ASCII name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1768552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768552] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1768552/+attachment/5132103/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768552 Title: apt-add-repository fails to add key for PPA with non-ASCII name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1768552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768552] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1768552/+attachment/5132104/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768552 Title: apt-add-repository fails to add key for PPA with non-ASCII name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1768552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768552] [NEW] apt-add-repository fails to add key for PPA with non-ASCII name
Public bug reported: If the terminal is not configured for a UTF-8 locale, the following command fails: # sudo add-apt-repository ppa:cz.nic-labs/bird The BIRD Internet Routing Daemon PPA (by upstream & .deb maintainer) More info: https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird Press [ENTER] to continue or ctrl-c to cancel adding it gpg: keyring `/tmp/tmpsbr85z99/secring.gpg' created gpg: keyring `/tmp/tmpsbr85z99/pubring.gpg' created gpg: requesting key F9C59A45 from hkp server keyserver.ubuntu.com gpg: /tmp/tmpsbr85z99/trustdb.gpg: trustdb created gpg: key F9C59A45: public key "Launchpad Datov� schr�nky" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) 'ascii' codec can't decode byte 0xc3 in position 86: ordinal not in range(128) I'd expect it to work, but fail to display the characters that aren't supported. While I have a workaround, which is to switch locale, the context is that I'm trying to instruct the users of my application on how to install the above PPA and that's a lot more complicated if I have to explain to them how to check the locale and install a UTF-8 version of their locale and switch to it. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-08-28 (1343 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Package: software-properties-common 0.96.20.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Tags: xenial Uname: Linux 4.4.0-119-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-08-01 (638 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected xenial ** Tags added: apport-collected xenial ** Description changed: If the terminal is not configured for a UTF-8 locale, the following command fails: # sudo add-apt-repository ppa:cz.nic-labs/bird The BIRD Internet Routing Daemon PPA (by upstream & .deb maintainer) More info: https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird Press [ENTER] to continue or ctrl-c to cancel adding it gpg: keyring `/tmp/tmpsbr85z99/secring.gpg' created gpg: keyring `/tmp/tmpsbr85z99/pubring.gpg' created gpg: requesting key F9C59A45 from hkp server keyserver.ubuntu.com gpg: /tmp/tmpsbr85z99/trustdb.gpg: trustdb created gpg: key F9C59A45: public key "Launchpad Datov� schr�nky" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) 'ascii' codec can't decode byte 0xc3 in position 86: ordinal not in range(128) I'd expect it to work, but fail to display the characters that aren't supported. - While I have a workaround, which is to switch locale, the context is - that I'm trying to instruct the users of my application on how to - install the above PPA and that's a lot more complicated if I have to - explain to them how to check the locale and install a UTF-8 version of - their locale and switch to it. + While I have a workaround, which is to switch locale, the context is that I'm trying to instruct the users of my application on how to install the above PPA and that's a lot more complicated if I have to explain to them how to check the locale and install a UTF-8 version of their locale and switch to it. + --- + ApportVersion: 2.20.1-0ubuntu2.16 + Architecture: amd64 + CurrentDesktop: GNOME-Flashback:Unity + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2014-08-28 (1343 days ago) + InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) + Package: software-properties-common 0.96.20.7 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 + Tags: xenial + Uname: Linux 4.4.0-119-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2016-08-01 (638 days ago) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768552 Title: apt-add-repository fails to add key for PPA with non-ASCII name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1768552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742250] Re: Adding and deleting a veth leaks a systemd unit
I tried this on Ubuntu 16.04, started on GCE and it didn't seem to repro there. When I add a veth, systemd units are added but they all seem to be cleaned up when the veth is removed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742250 Title: Adding and deleting a veth leaks a systemd unit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1742250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742250] Re: Adding and deleting a veth leaks a systemd unit
As a workaround, running systemctl daemon-reload removes all the leaked units. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742250 Title: Adding and deleting a veth leaks a systemd unit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1742250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742250] [NEW] Adding and deleting a veth leaks a systemd unit
Public bug reported: When I add a veth device: sudo ip link add name test1 type veth I see these systemd units appear: systemctl list-units --all | grep test  sys-devices-virtual-net-test1.device  loadedactive plugged /sys/devices/virtual/net/test1  sys-subsystem-net-devices-test1.device  loadedactive plugged /sys/subsystem/net/devices/test1 However, if I then delete the veth: sudo ip link del dev test1 Then only one of the units is removed: systemctl list-units --all | grep test   sys-devices-virtual-net-test1.device  loadedactive plugged /sys/devices/virtual/net/test1 This is a big problem when running, for example, a Kubernetes cluster since each pod creation/deletion leaks a systemd unit. When enough have been leaked, systemd becomes unresponsive and the system is broken until reboot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 9 18:57:34 2018 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=c66b8cf4-2a6c-4fb3-9f39-59483a6a025c ro scsi_mod.use_blk_mq=Y console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 1AF4A7E8-D62B-D331-0693-3511A041DD96 dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful uec-images ** Description changed: When I add a veth device: - sudo ip link add name test1 type veth + sudo ip link add name test1 type veth I see these systemd units appear: - systemctl list-units --all | grep test - smc-kubeadm-node-0: Tue Jan 9 19:02:41 2018 + systemctl list-units --all | grep test - sys-devices-virtual-net-test1.device - loadedactive plugged /sys/devices/virtual/net/test1 +  sys-devices-virtual-net-test1.device +  loadedactive plugged /sys/devices/virtual/net/test1 - sys-subsystem-net-devices-test1.device - loadedactive plugged /sys/subsystem/net/devices/test1 +  sys-subsystem-net-devices-test1.device +  loadedactive plugged /sys/subsystem/net/devices/test1 However, if I then delete the veth: - sudo ip link del dev test1 + sudo ip link del dev test1 Then only one of the units is removed: - systemctl list-units --all | grep test - smc-kubeadm-node-0: Tue Jan 9 19:03:53 2018 + systemctl list-units --all | grep test - sys-devices-virtual-net-test1.device - loadedactive plugged /sys/devices/virtual/net/test1 +   sys-devices-virtual-net-test1.device +  loadedactive plugged /sys/devices/virtual/net/test1 This is a big problem when running, for example, a Kubernetes cluster since each pod creation/deletion leaks a systemd unit. When enough have been leaked, systemd becomes unresponsive and the system is broken until reboot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 9 18:57:34 2018 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=c66b8cf4-2a6c-4fb3-9f39-59483a6a025c ro scsi_mod.use_blk_mq=Y console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 1AF4A7E8-D62B-D331-0693-3511A041DD96 dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742250 Title: Adding and deleting a veth leaks a systemd unit To manage notifications about this bug go
[Bug 1738534] Re: Processor turbo dsiabled/throttled after suspend
It may have been as early as the upgrade to 16.04. I remember having some performance/overheating issues at that time so I disabled intel_pstate for a while; but I never fully diagnosed the issue. The 17.10 install was a fresh install though, I wiped the system. I'll try the new kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738534 Title: Processor turbo dsiabled/throttled after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738534] Re: Processor turbo dsiabled/throttled after suspend
As a workaround, I created a post-resume script that runs the above
commands at /lib/systemd/system-sleep/throttle-workaround. It works in
the first scenario, but not if the full power cycle was done on battery
power.
#!/bin/sh
# Action script to prevent CPU throttling after resume.
set -e
PATH=/sbin:/usr/sbin:/bin:/usr/bin
case "${1}" in
post)
x86_energy_perf_policy --turbo-enable 1
cpufreq-set -r --max=3.0GHz
;;
esac
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738534
Title:
Processor turbo dsiabled/throttled after suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738534/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738538] [NEW] Scrolling (with two finger scroll) not working in shotwell
Public bug reported: Scrolling the photos pane with my trackpad doesn't work in shotwell. Scrolling the library pane (list of events) works fine. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: shotwell 0.26.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 16 12:37:09 2017 InstallationDate: Installed on 2017-12-14 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738538 Title: Scrolling (with two finger scroll) not working in shotwell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1738538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738534] Re: Processor turbo dsiabled/throttled after suspend
Just tried another scenario. If I do the full power cycle while on battery power, then it boots up with turbo disabled and frequency locked. This command then seems to work (cpupower then reports turbo is active/supported): sudo x86_energy_perf_policy --turbo-enable 1 But this command has no effect: sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz (Where, int he previous scenario, it did work.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738534 Title: Processor turbo dsiabled/throttled after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738534] [NEW] Processor turbo dsiabled/throttled after suspend
Public bug reported: After suspending/resuming my laptop on battery power, I noticed choppy video playback. I've narrowed it down to the CPU being locked to lower frequencies after suspend/resume (only on battery). Plugging the laptop back in does not restore the normal performance, nor does suspend/resume after plugging it back in. The performance doesn't drop until after the suspend/resume, I'm not sure if it is _supposed_ to throttle when on battery, but either way the behaviour is wrong. Doing a full shutdown and restart restores the performance to normal. Prior to a suspend/resume cycle, cpupower reports: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 3.00 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.26 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has no effect) and turbo is disabled: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 1.80 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 950 MHz (asserted by call to kernel) boost state support: Supported: no Active: no 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Trying to re-enable turbo mode by setting the no_turbo intel_pstate /sys/ entry back to 0 is rejected: $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo 0 tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted However, these two commands *do* work around the problem, forcing turbo mode back on and then restoring the normal frequency range: sudo x86_energy_perf_policy --turbo-enable 1 sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz I also see this error in dmesg after some resumes (but the above problem sometimes happens without this error message): Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by BIOS or unavailable on processor ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 16 11:18:12 2017 InstallationDate: Installed on 2017-12-14 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 001 Device 004: ID 2232:1024 Silicon Motion Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-19-generic root=UUID=7352de8c-0017-44e1-81fb-0145ad9c1185 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:
[Bug 1719220] [NEW] package libcupsmime1:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: package libcupsmime1:amd64 is already installed and configured
Public bug reported: yes ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libcupsmime1:amd64 2.1.3-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-lowlatency 4.10.17 Uname: Linux 4.10.0-35-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 600:0:117:292008:2017-09-24 15:29:25.739557266 -0400:2017-09-24 15:29:26.739557266 -0400:/var/crash/libcups2:amd64.0.crash 600:0:117:292002:2017-09-24 15:29:25.775565147 -0400:2017-09-24 15:29:26.775565147 -0400:/var/crash/cups-daemon.0.crash 600:0:117:292016:2017-09-24 15:29:25.754560470 -0400:2017-09-24 15:29:26.754560470 -0400:/var/crash/libcupsmime1:amd64.0.crash CupsErrorLog: Date: Sun Sep 24 15:29:26 2017 DuplicateSignature: package:libcupsmime1:amd64:2.1.3-4ubuntu0.3 Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... dpkg: error processing package libcups2:amd64 (--configure): package libcups2:amd64 is already installed and configured ErrorMessage: package libcupsmime1:amd64 is already installed and configured InstallationDate: Installed on 2017-09-08 (16 days ago) InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Latitude E5430 non-vPro Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-lowlatency root=UUID=f16090e3-ea0a-41ca-950c-f83d7e982692 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-lowlatency root=UUID=f16090e3-ea0a-41ca-950c-f83d7e982692 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: cups Title: package libcupsmime1:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: package libcupsmime1:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0MYF02 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd09/24/2014:svnDellInc.:pnLatitudeE5430non-vPro:pvr01:rvnDellInc.:rn0MYF02:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5430 non-vPro dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719220 Title: package libcupsmime1:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: package libcupsmime1:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1719220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711296] [NEW] crashed during installation
Public bug reported: Crashed during installation from live USB. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.2 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CasperVersion: 1.384 Date: Thu Aug 17 08:05:28 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170815) ProcEnviron: LANGUAGE=en_GB.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubiquity-17.10.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711296 Title: crashed during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1711296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699480] Re: package console-data 2:1.12-5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal
Thanks Mattia. I've already reworked it, and have been using it since then. Unless this information helps with some known bug or symptom, I suggest just ignoring it. I can't see how to close or otherwise disposition this report, so I'll leave it to you and your team. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699480 Title: package console-data 2:1.12-5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-data/+bug/1699480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701247] [NEW] package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1701135 *** https://bugs.launchpad.net/bugs/1701135 Public bug reported: issues started from failed install of google-earth- stable_current_amd64.deb ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mick 1887 F pulseaudio /dev/snd/controlC0: mick 1887 F pulseaudio Date: Thu Jun 29 20:29:10 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=8cd168e8-560f-45d6-9891-4b84d75bea51 InstallationDate: Installed on 2016-06-20 (373 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK Computer Inc. K53TK ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=87c1650a-7ab7-486f-8fe6-9608bd989fc6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 205 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53TK 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.:bvr205:bd02/15/2012:svnASUSTeKComputerInc.:pnK53TK:pvr1.0:rvnASUSTeKComputerInc.:rnK53TK:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53TK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701247 Title: package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699480] [NEW] package console-data 2:1.12-5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal
Public bug reported: After the lengthy account creation, I don't remember much. I was trying to install console-data, it didn't work, I couldn't remove it cleanly. This went back and forth a few times. Finally it threw a serious error and asked to report to the mothership. This is within a vmware fusion VM from Mac OS X. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: console-data 2:1.12-5 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: console-data: Remove NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 21 04:15:18 2017 Dependencies: DpkgTerminalLog: dpkg: error processing package console-data (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2017-06-13 (7 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: console-data Title: package console-data 2:1.12-5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-data (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699480 Title: package console-data 2:1.12-5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-data/+bug/1699480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675144] [NEW] tried to install alongside windows on an empty partition, got error
Public bug reported: Windows 10 Installed on partition, empty partition next to it. Tried to "install alongside windows", got error. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.14 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 Date: Wed Mar 22 15:38:06 2017 InstallCmdLine: BOOT_IMAGE=/multiboot/ubuntu-16.10-desktop-amd64/casper/vmlinuz.efi iso-scan/filename=/multiboot/ubuntu-16.10-desktop-amd64/ubuntu-16.10-desktop-amd64.iso boot=casper noprompt floppy.allowed_drive_mask=0 ignore_uuid LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-16.10.14 yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675144 Title: tried to install alongside windows on an empty partition, got error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1675144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639374] Re: grub-pc fails to remove, rendering lubuntu uninstallable on EFI machines
I was able recover from this issue, by booting a livecd, chrooting in and running 'apt-get -f install && apt-get install grub2-common. I checked the grub config and it looked good. I also did a "grub install" but that was probably not required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639374 Title: grub-pc fails to remove, rendering lubuntu uninstallable on EFI machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1639374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666130] [NEW] unable to install to a partition, using efi - unexpected installer exit
Public bug reported: installer appeared to be working fine. THe unexpected exit was the only message that was presented. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.14 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 Date: Sun Feb 19 23:43:05 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/lubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lubuntu ubiquity-16.10.14 yakkety ** Summary changed: - installing lubuntu on a Gigabyte P57X, unable to install on Sony Vaio VGN-Z either + installing lubuntu to a partition, using efi ** Summary changed: - installing lubuntu to a partition, using efi + unable to install to a partition, using efi - unexpected installer exit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666130 Title: unable to install to a partition, using efi - unexpected installer exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1666130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666130] Re: unable to install to a partition, using efi - unexpected installer exit
:~$ mount | grep /target /dev/sda6 on /target type ext4 (rw,relatime,errors=remount-ro,data=ordered) /dev/sda1 on /target/boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) proc on /target/proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /target/sys type sysfs (rw,nosuid,nodev,noexec,relatime) udev on /target/dev type devtmpfs (rw,nosuid,relatime,size=8138340k,nr_inodes=2034585,mode=755) tmpfs on /target/run type tmpfs (rw,nosuid,noexec,relatime,size=1630788k,mode=755) The intent was to install on /dev/sda6, as use my own EFI boot loader to launch it. Unfortunately, the installer unexpectedly exits before returning a success status. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666130 Title: unable to install to a partition, using efi - unexpected installer exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1666130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643165] Re: Wifi drops out regularly after upgrade to 16.04
Ah, after disabling 40MHz bands on my router, the problem seems to have gone away; seems the bug is triggered by the router switching between 20 and 40MHz. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643165 Title: Wifi drops out regularly after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662355] [NEW] Signon shows up as Safari
Public bug reported: Signon UI popped up and asked me to log into Google. After logging in, Google immediately sent me a message asking whether I logged in as Safari, with my public IP (so I have no reason to think it was anyone but me). Is signon-ui spoofing as safari? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: signon-ui 0.17+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 6 22:41:44 2017 InstallationDate: Installed on 2012-09-26 (1594 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) PackageArchitecture: all SourcePackage: signon-ui UpgradeStatus: Upgraded to yakkety on 2017-01-23 (13 days ago) ** Affects: signon-ui (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662355 Title: Signon shows up as Safari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1662355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661764] [NEW] Videos stutter with thermald enabled
Public bug reported: Since upgrading to Yakkety, I noticed youtube ad vimeo videos slow down and stutter after a few minutes but it didn't seem to be due to buffering. dmesg logs hinted that some sort of throttling was happening. I tried stopping thermald and that seems to help. sensors reports the CPU temperature is a bit higher with thermald disabled (91-2C vs 87C) but I'd rather have my laptop run a little hot than be unusable for watching videos. Since it's a mobile part, the rated max temperature for my CPU is 105C so it seems like thermald is taking drastic throttling action while there's still quite a bit of headroom. Obviously, it'd be great if I could watch youtube at 65C instead! CPU is an i7-3517U, Samsung NP900X4C-A03US laptop. I've tried with and without "intel_pstate" enabled with similar results. Fan is working as expected: seems to spin up high when it's hot and shut off when it's cool. I tried cleaning out the case but it made no difference and the fan doesn't seem dirty (it's small and ducted though so I can't really clean it). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: thermald 1.5.3-4 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 3 22:30:38 2017 InstallationDate: Installed on 2012-09-26 (1591 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) SourcePackage: thermald UpgradeStatus: Upgraded to yakkety on 2017-01-23 (10 days ago) ** Affects: thermald (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661764 Title: Videos stutter with thermald enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1661764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654754] Re: Wifi stopped working; ath10k_pci firmware crash in dmesg log
Looks similar to Bug #1627474, not sure if trace is identical though -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654754 Title: Wifi stopped working; ath10k_pci firmware crash in dmesg log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1654754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654754] [NEW] Wifi stopped working; ath10k_pci firmware crash in dmesg log
Public bug reported: Wifi worked fine for a while then stopped working. dmesg log has a correlated firmware crash for the Wifi adapter's driver. Disabling and reenabling Wifi in the network manager widget seemed to make it work for a while again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-firmware 1.161.1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 7 15:42:55 2017 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-20 (18 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to yakkety on 2017-01-03 (3 days ago) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654754 Title: Wifi stopped working; ath10k_pci firmware crash in dmesg log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1654754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654754] Re: Wifi stopped working; ath10k_pci firmware crash in dmesg log
Here's the dmesg crash report: [ 3683.563419] wlp58s0: AP 00:07:26:aa:e0:45 changed bandwidth, new config is 2472 MHz, width 2 (2462/0 MHz) [ 3708.293559] ath10k_pci :3a:00.0: failed to stop wmi scan: -11 [ 3708.293565] ath10k_pci :3a:00.0: failed to stop scan: -11 [ 3708.293568] ath10k_pci :3a:00.0: failed to start hw scan: -110 [ 3712.407418] ath10k_pci :3a:00.0: failed to start hw scan: -11 [ 3713.437730] ath10k_pci :3a:00.0: firmware crashed! (uuid f68629ee-b9ac-4afa-a8ab-78f9b8dbc58d) [ 3713.437757] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [ 3713.437764] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 3713.439421] ath10k_pci :3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 [ 3713.440186] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 [ 3713.440195] ath10k_pci :3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 3713.442262] ath10k_pci :3a:00.0: firmware register dump: [ 3713.442273] ath10k_pci :3a:00.0: [00]: 0x0503 0x15B3 0x009860FA 0x00955B31 [ 3713.442280] ath10k_pci :3a:00.0: [04]: 0x009860FA 0x00060730 0x0004 0x0040E8A0 [ 3713.442287] ath10k_pci :3a:00.0: [08]: 0x00498110 0x00955A00 0x000B 0x0040 [ 3713.442293] ath10k_pci :3a:00.0: [12]: 0x0009 0x 0x00952CD0 0x00952CE6 [ 3713.442299] ath10k_pci :3a:00.0: [16]: 0x00952CC4 0x0091080D 0x 0x0091080D [ 3713.442305] ath10k_pci :3a:00.0: [20]: 0x409860FA 0x0040E7E8 0x 0x0041E0DC [ 3713.442311] ath10k_pci :3a:00.0: [24]: 0x800B5A1D 0x0040E848 0x000F 0xC09860FA [ 3713.442317] ath10k_pci :3a:00.0: [28]: 0x809B3230 0x0040E948 0x0018 0x004313B8 [ 3713.442323] ath10k_pci :3a:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9BC 0x00429548 [ 3713.442329] ath10k_pci :3a:00.0: [36]: 0x8091D252 0x0040E9B8 0x 0x0001 [ 3713.442335] ath10k_pci :3a:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 0x00429C10 [ 3713.442341] ath10k_pci :3a:00.0: [44]: 0x809FCFDB 0x0040EA88 0x0043A380 0x0001 [ 3713.442351] ath10k_pci :3a:00.0: [48]: 0x80911210 0x0040EAD8 0x0010 0x004041D0 [ 3713.442357] ath10k_pci :3a:00.0: [52]: 0x80911154 0x0040EB28 0x0040 0x [ 3713.442363] ath10k_pci :3a:00.0: [56]: 0x8091122D 0x0040EB48 0x 0x00400600 [ 3713.442467] ath10k_pci :3a:00.0: failed to start hw scan: -108 [ 3713.525461] ieee80211 phy0: Hardware restart was requested [ 3715.944232] ath10k_pci :3a:00.0: device successfully recovered [ 3743.622083] wlp58s0: deauthenticated from 00:07:26:aa:e0:45 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA) [ 3743.664676] wlp58s0: authenticate with 00:07:26:aa:e0:45 [ 3743.706559] wlp58s0: send auth to 00:07:26:aa:e0:45 (try 1/3) [ 3743.708669] wlp58s0: authenticated [ 3743.715614] wlp58s0: associate with 00:07:26:aa:e0:45 (try 1/3) [ 3743.720081] wlp58s0: RX AssocResp from 00:07:26:aa:e0:45 (capab=0x431 status=0 aid=3) [ 3743.723689] wlp58s0: associated [ 3743.732696] ath: EEPROM regdomain: 0x833a [ 3743.732699] ath: EEPROM indicates we should expect a country code [ 3743.732702] ath: doing EEPROM country->regdmn map search [ 3743.732705] ath: country maps to regdmn code: 0x37 [ 3743.732707] ath: Country alpha2 being used: GB [ 3743.732709] ath: Regpair used: 0x37 [ 3743.732712] ath: regdomain 0x833a dynamically updated by country IE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654754 Title: Wifi stopped working; ath10k_pci firmware crash in dmesg log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1654754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647453] [NEW] postgresql-common 154ubuntu1 checks for existence of /var/run/postgresql and terminates before it has change to create via 'start' function in /usr/share/postgresql-common/init.d-f
Public bug reported:
The init script /etc/init.d/postgresql in Ubuntu 14.04 Trusty Tahr has
check:
start|stop|restart|reload)
if [ -z "`pg_lsclusters -h`" ]; then
log_warning_msg 'No PostgreSQL clusters exist; see "man
pg_createcluster"'
exit 0
fi
pg_lsclusters -h command will return an empty string (to STDOUT) if
/var/run/postgresql does not exist.
/var/run/postgresql does not get initialized however until the init
script can reach a call to 'start' from /usr/share/postgresql-
common/init.d-functions:
start() {
# create socket directory
if [ -d /var/run/postgresql ]; then
chmod 2775 /var/run/postgresql
else
install -d -m 2775 -o postgres -g postgres /var/run/postgresql
[ -x /sbin/restorecon ] && restorecon -R /var/run/postgresql || true
fi
do_ctl_all start "$1" "Starting PostgreSQL $1 database server"
}
/var/run is a volatile file system by default in Trusty - so on reboot
/var/run/postgresql will not exist.
Essentially, postgresql will fail to start on reboot.
** Affects: postgresql-common (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647453
Title:
postgresql-common 154ubuntu1 checks for existence of
/var/run/postgresql and terminates before it has change to create via
'start' function in /usr/share/postgresql-common/init.d-functions
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1647453/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643165] Re: Wifi drops out regularly after upgrade to 16.04
Running 4.9.0-040900rc6, just had a drop out. Noticed that dmesg had this output: First this line, which seemed to coincide with the dropout: [ 3627.072802] wlan0: AP 00:07:26:aa:e0:45 changed bandwidth, new config is 2462 MHz, width 2 (2452/0 MHz) Then, after a minute, this and it came back: [ 3707.386740] wlan0: authenticate with 00:07:26:aa:e0:45 [ 3707.394906] wlan0: send auth to 00:07:26:aa:e0:45 (try 1/3) [ 3707.397243] wlan0: authenticated [ 3707.397828] wlan0: associate with 00:07:26:aa:e0:45 (try 1/3) [ 3707.406078] wlan0: RX AssocResp from 00:07:26:aa:e0:45 (capab=0x431 status=0 aid=1) [ 3707.413670] wlan0: associated [ 3707.447412] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 00:07:26:aa:e0:45 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643165 Title: Wifi drops out regularly after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643165] [NEW] Wifi drops out regularly after upgrade to 16.04
Public bug reported: Since upgrading to 16.04, my wifi has seemed a lot more flaky, it'll drop out for 20s every few minutes then come back. network manager still thinks that it is connected, but websites will fail to load/time out. Reconnecting to the AP (by clicking on it in network-manager) seems to re-establish the connection. I typically sit 6ft from the access point so the signal is strong and much stronger than any nearby APs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 2212 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 19 10:39:23 2016 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_pstate=enable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643165 Title: Wifi drops out regularly after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643163] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779947/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1643163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643163] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779938/+files/IpAddr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1643163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643163] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779937/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1643163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
