[Bug 1371811] Re: cheese crashes when try to record video
I believe this is related information: When I attempt to record video, Cheese attempts to create a 47 minute video file, and then to append to that. The file size is enormous. And Cheese follows up by crashing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371811 Title: cheese crashes when try to record video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1371811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871962] Re: NETDEV WATCHDOG: enx106530060c6c (r8152): transmit queue 0 timed out
I have this seemingly related bug: When I connect to my ThinkPad Thunderbolt 3 dock with a ThinkPad X1 Carbon (6th Gen) using Ubuntu 20.10, after a few hours the NIC stops working: Dec 5 00:28:58 davido-thinkpad kernel: [46349.075202] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:29:04 davido-thinkpad kernel: [46354.963230] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:29:09 davido-thinkpad kernel: [46359.827136] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:29:14 davido-thinkpad kernel: [46364.947149] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:29:19 davido-thinkpad kernel: [46370.067211] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:29:25 davido-thinkpad kernel: [46375.955090] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:29:30 davido-thinkpad kernel: [46381.075069] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:29:36 davido-thinkpad kernel: [46386.963098] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:29:41 davido-thinkpad kernel: [46391.827108] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:29:46 davido-thinkpad kernel: [46396.947053] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:29:51 davido-thinkpad kernel: [46402.067077] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:29:57 davido-thinkpad kernel: [46407.954960] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:30:02 davido-thinkpad kernel: [46413.075025] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:30:08 davido-thinkpad kernel: [46418.962792] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:30:13 davido-thinkpad kernel: [46423.826987] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:30:18 davido-thinkpad kernel: [46428.946952] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:30:23 davido-thinkpad kernel: [46434.066892] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:30:29 davido-thinkpad kernel: [46439.954816] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:30:34 davido-thinkpad kernel: [46445.074832] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:30:40 davido-thinkpad kernel: [46450.962763] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:30:45 davido-thinkpad kernel: [46455.826743] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:30:46 davido-thinkpad NetworkManager[945]: [1607153446.6029] manager: NetworkManager state is now CONNECTED_SITE Dec 5 00:30:46 davido-thinkpad NetworkManager[945]: [1607153446.6072] manager: NetworkManager state is now CONNECTED_LOCAL Dec 5 00:30:46 davido-thinkpad NetworkManager[945]: [1607153446.6075] manager: NetworkManager state is now CONNECTED_SITE Dec 5 00:30:46 davido-thinkpad NetworkManager[945]: [1607153446.6077] policy: set 'Wired connection 2' (enx0050b6a7622b) as default for IPv4 routing and DNS Dec 5 00:30:46 davido-thinkpad dbus-daemon[943]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=945 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Dec 5 00:30:46 davido-thinkpad deja-dup-monito[25858]: Source ID 448 was not found when attempting to remove it Dec 5 00:30:46 davido-thinkpad systemd[1]: Starting Network Manager Script Dispatcher Service... Dec 5 00:30:46 davido-thinkpad dbus-daemon[943]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 5 00:30:46 davido-thinkpad systemd[1]: Started Network Manager Script Dispatcher Service. Dec 5 00:30:50 davido-thinkpad kernel: [46460.946787] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:30:52 davido-thinkpad whoopsie[5431]: [00:30:52] Cannot reach: https://daisy.ubuntu.com Dec 5 00:30:55 davido-thinkpad kernel: [46466.066797] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:30:57 davido-thinkpad systemd[1]: NetworkManager-dispatcher.service: Succeeded. Dec 5 00:31:01 davido-thinkpad kernel: [46471.954734] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:31:06 davido-thinkpad kernel: [46477.074659] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:31:12 davido-thinkpad kernel: [46482.962741] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:31:17 davido-thinkpad kernel: [46487.826611] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:31:22 davido-thinkpad kernel: [46492.946592] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:31:27 davido-thinkpad kernel: [46498.03] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:31:33 davido-thinkpad kernel: [46503.954576] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:31:38 davido-thinkpad kernel: [46509.074528] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout Dec 5 00:31:44 davido-thinkpad kernel: [46514.962608] r8152 6-1:1.0 enx0050b6a7622b: Tx timeout This TB3 dock is known to work relatively flawlessly with the same model laptop under Ubuntu 20.04, and on the same model laptop under Centos7. Kernel info: davido@davido-thinkpad:~$ uname -a Linux davido-thinkpad 5.8.0-31-generic
[Bug 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused
Upon boot, checking journalctl -eb: Nove 03 07:13:21 davido-thinkpad gnome-shell[6720]: Unable to connect to ibus: Could not connect: Connection refused So I can confirm the error still persists a couple years after reporting. I don't know what side effects it produces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761382 Title: Unable to connect to ibus: Could not connect: Connection refused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901279] Re: wacom tablet map to single monitor doesn't work with nvidia drivers
Additional info, when mapping buttons, if I set a Wacom tablet button to "Switch Monitor", when I tap that button all three of my monitors display the same Wacom Intuos BT M popup. Presumably this is because all three are mapped, not just one. If it were properly mapping a single monitor, that popup would appear only on one of the monitors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901279 Title: wacom tablet map to single monitor doesn't work with nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1901279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901279] Re: wacom tablet map to single monitor doesn't work with nvidia drivers
This doesn't seem limited only to Nvidia drivers. I'm using a Lenovo Thinkpad X1 Carbon, 6th Gen with Ubuntu 20.10. Sometimes the map to monitor setting works, other times it is completely ignored. When it is ignored, the relative vs absolute setting in the Settings | Wacom | Tablet gnome settings page is also ignored. My Thinkpad doesn't have Nvidia drivers. The Wacom tablet in use is the 6100 model. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901279 Title: wacom tablet map to single monitor doesn't work with nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1901279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901452] [NEW] Upgrade to 20.10 error. acpi-call-dkms : ERROR: Kernel configuration is invalid.
Public bug reported: Loading new acpi-call-1.1.0 DKMS files... Building for 5.8.0-25-generic Building initial module for 5.8.0-25-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/acpi-call-dkms.0.crash' Error! Bad return status for module build on kernel: 5.8.0-25-generic (x86_64) Consult /var/lib/dkms/acpi-call/1.1.0/build/make.log for more information. dpkg: error processing package acpi-call-dkms (--configure): installed acpi-call-dkms package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: acpi-call-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) davido@davido-thinkpad:~$ cat /var/lib/dkms/acpi-call/1.1.0/build/make.log DKMS make.log for acpi-call-1.1.0 for kernel 5.8.0-25-generic (x86_64) Sun Oct 25 05:55:39 PM MDT 2020 make: Entering directory '/usr/src/linux-headers-5.8.0-25-generic' ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it. make: *** [Makefile:746: include/config/auto.conf] Error 1 make: Leaving directory '/usr/src/linux-headers-5.8.0-25-generic' davido@davido-thinkpad:~$ dpkg --verify linux-headers-$(uname -r) ??5?? /usr/src/linux-headers-5.8.0-25-generic/include/generated/autoconf.h ??5?? /usr/src/linux-headers-5.8.0-25-generic/scripts/basic/.fixdep.cmd ??5?? /usr/src/linux-headers-5.8.0-25-generic/scripts/kconfig/.conf.o.cmd ??5?? /usr/src/linux-headers-5.8.0-25-generic/scripts/kconfig/.confdata.o.cmd ??5?? /usr/src/linux-headers-5.8.0-25-generic/scripts/kconfig/.expr.o.cmd davido@davido-thinkpad:~$ sudo ubuntu-bug acpi-call-dkms ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: acpi-call-dkms 1.1.0-6 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 25 18:01:46 2020 InstallationDate: Installed on 2019-05-02 (542 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: acpi-call UpgradeStatus: Upgraded to groovy on 2020-10-25 (0 days ago) ** Affects: acpi-call (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901452 Title: Upgrade to 20.10 error. acpi-call-dkms : ERROR: Kernel configuration is invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1901452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892657] Re: boltd1719]: probing: timeout, done - timeouts every few seconds from boltd
I have tested with bolt (0.8-4ubuntu1) and can confirm that on my system the 'Probing...' messages are no longer being spewed, and the notification icon no longer pops up every couple of seconds. It seems resolved to me. (Lenovo Thinkpad X1 Carbon, 6th Gen with Lenovo Thinkpad Thunderbolt 3 dock) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892657 Title: boltd1719]: probing: timeout, done - timeouts every few seconds from boltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1892657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892657] Re: boltd1719]: probing: timeout, done - timeouts every few seconds from boltd
I'm unfamiliar with the process. Now that a debdiff has been attached, what is the process for it being adopted and finding its way out to the end user? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892657 Title: boltd1719]: probing: timeout, done - timeouts every few seconds from boltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1892657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892657] Re: boltd1719]: probing: timeout, done - timeouts every few seconds from boltd
I can confirm that as of 2020-09-07 this bug persisted, despite the issue being marked "Fix Released" on 2020-08-24. The biggest annoyance with it is the fact that the connection snake icon appearing and disappearing from the top of the Gnome desktop causes any other icon to the left of it to shift over and back every few seconds. The annoyance is just a symptom of the problem described above, though. But it impacts the user experience significantly enough that I mostly avoid docking my laptop until it's fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892657 Title: boltd1719]: probing: timeout, done - timeouts every few seconds from boltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1892657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892657] Re: boltd1719]: probing: timeout, done - timeouts every few seconds from boltd
Aug 23 17:33:41 davido-thinkpad boltd[1719]: probing: started [1000] Aug 23 17:33:46 davido-thinkpad boltd[1719]: probing: timeout, done: [2114586] (200) Aug 23 17:33:47 davido-thinkpad boltd[1719]: probing: started [1000] Aug 23 17:33:49 davido-thinkpad boltd[1719]: probing: timeout, done: [2003449] (200) Aug 23 17:34:20 davido-thinkpad boltd[1719]: probing: started [1000] Aug 23 17:34:24 davido-thinkpad boltd[1719]: probing: timeout, done: [2141302] (200) Aug 23 17:34:37 davido-thinkpad boltd[1719]: probing: started [1000] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892657 Title: boltd1719]: probing: timeout, done - timeouts every few seconds from boltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1892657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892657] [NEW] boltd1719]: probing: timeout, done - timeouts every few seconds from boltd
Public bug reported: This may relate to https://gitlab.freedesktop.org/bolt/bolt/-/issues/156 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bolt 0.8-4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 17:32:55 2020 InstallationDate: Installed on 2019-05-02 (479 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bolt UpgradeStatus: Upgraded to focal on 2020-04-23 (121 days ago) ** Affects: bolt (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/1892657 Title: boltd1719]: probing: timeout, done - timeouts every few seconds from boltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1892657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736883] [NEW] Universal Access | Repeat Keys | Speed: Moving control to left causes repeat rate to increase. Moving right slows down repeat rate. This is opposite of convention.
Public bug reported: In the Universal Access control, Typing, Repeat Keys, the Speed slider slows repeat rate when moved rightward, and increases repeat rate when moved leftward. This is opposite of typical expectations, and defies convention, where typically sliding a control rightward increases its setting. The volume control, for example, increases when slid rightward. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 7 00:25:03 2017 ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736883 Title: Universal Access | Repeat Keys | Speed: Moving control to left causes repeat rate to increase. Moving right slows down repeat rate. This is opposite of convention. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1736883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727158] [NEW] lscpu shows incorrect instantaneous CPU MHz value
Public bug reported: Ubuntu 17.10: lscpu has the following fields of interest to this report: Model name: Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz CPU MHz: 3499.996 CPU max MHz: 5900. CPU min MHz: 1600. The CPU MHz field is incorrect: At idle it never shows down-step, and at full load, it never shows the CPU's boost frequency (which should be up to about 4.6GHz on my system). This was working correctly under Ubuntu 17.04, showing the full range between 1600 and 4600. But with Ubuntu 17.10 it remains constantly at the CPU's design spec of 3499.996. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: util-linux 2.30.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 22:00:02 2017 InstallationDate: Installed on 2017-09-01 (53 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727158 Title: lscpu shows incorrect instantaneous CPU MHz value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1727158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
