[Bug 2063456] Re: package cephadm: dependency "cephadmlib" missing
I don't understand this being fixed. I installed a new 24.04 installation two days ago. installed cephadm today. Installed version is "19.2.0~git20240301.4c76c50-0ubuntu6" (not 6.1). Notes indicate that this should have been moved to proposed to updates by now. But it hasn't. What is the status of this fix or is there something I need to do to get this to update properly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063456 Title: package cephadm: dependency "cephadmlib" missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/2063456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
> Thank you for doing your research into the issue but I am confused by > your results. > > Are you claiming that removing mentioned Ubuntu specific commit resolves > the issue? Specifically it's the first commit where I experience the bug, so I would assume that reverting it will resolve the issue. The commit enables the following compile time kernel config options: CONFIG_INTEL_IOMMU_DEFAULT_ON=y CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y These enable the Intel IOMMU by default (although it can still be disabled by the linux command line at runtime via Grub). For completeness here is the corresponding commit in the noble kernel: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?id=77e530c1a864c601b96622db03bc1f38e51155f1 > What about the fact that the issue also affect upstream/mainline > kernels? I don't know how the kernel config values for the mainline builds that I linked to were derived, but in the build that I tried (built July 25 2024) the above config options were also enabled. I don't know if this is because the upstream kernel has now enabled these config options by default or if the builds that I linked to still use custom Ubuntu config options. > Are you trying to say that the issue is just related to the conditions > described in the commit and intel_iommu=igfx_off? Specifying intel_iommu= on the linux command line is a way of overriding at runtime whatever is specified by the CONFIG_INTEL_IOMMU_DEFAULT_ON config option when the kernel is compiled. Specifying intel_iommu=off would be the way to completely undo the config changed by the problematic commit, but since the bug that we are experiencing only (to my knowledge) affects graphics, I figured that intel_iommu=igfx_off would be more conservative workaround, as it only disables Intel's integrated graphics from going through the IOMMU but otherwise keeps the IOMMU enabled. It's not exactly clear to me what the benefits of having graphics going through the Intel IOMMU are, but if Intel's IOMMU was only enabled recently in Ubuntu kernels then I just assume that I won't miss whatever those benefits are. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
Despite some of the nondeterminism behind this bug, I believe I have bisected this bug to the following commit in the Ubuntu kernel tree: 14ebfcacaeb07b02235f2ea881fd6e34e3de0d6f . More info is available on this commit here: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/unstable/commit/?id=14ebfcacaeb07b02235f2ea881fd6e34e3de0d6f The commit text reads: > UBUNTU: [Config] enable Intel DMA remapping by default > BugLink: https://bugs.launchpad.net/bugs/1951440 > > We have tried in the past to enable CONFIG_INTEL_IOMMU_DEFAULT_ON and > CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON (starting with Jammy), but > there were multiple issues (especially with old hardware), so we ended > up disabling these options afterwards, see LP: #1971699. > > Considering that IOMMU is enabled by default in upstream kernels, > probably most of these issues are solved now (or old hardware has been > decommissioned). > > Moreover, having this enabled by default can prevent potential issues > with modern hardware and drivers (see for example LP #1958004). > > Acked-by: Philip Cox > Acked-by: Andrei Gherzan > Signed-off-by: Andrea Righi The commit text even predicts that the commit may introduce problems with older hardware. Its predictions appear unfortunately accurate. Operating under the assumption that this commit introduced the bug, as a workaround, I have found that adding: intel_iommu=igfx_off to the GRUB_CMDLINE appears to resolve the issue for me. Unfortunately, there appears to be no relief in the newest kernels. I tried the latest daily build available here: https://kernel.ubuntu.com/mainline/daily/ ...and found that the issue still persists there with the default GRUB_CMDLINE. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy and noble
Hello all, SQA has tested cloud-init on jammy and focal and didnt run into any issues. The results are only visible by Canonical employees but, Jammy: * https://solutions.qa.canonical.com/testruns/759c1d91-74ac-4908-b1bd-a7374937c88c * https://solutions.qa.canonical.com/testruns/41ae6b95-4744-4638-a008-d0d8313fb910 Focal: * https://solutions.qa.canonical.com/testruns/575b6a60-099f-4cdc-945d-229f4ca0863d * https://solutions.qa.canonical.com/testruns/d4ca914b-e0f0-455d-be5e-d328f3a48a8f Please note, we are not testing on Nobel at this moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071762 Title: sru cloud-init (24.2 update) to focal, jammy and noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2071762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071510] [NEW] package input-remapper-gtk (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/input-remapper-gtk', which is also in package input-remapper 2.0.1
Public bug reported: install failed ProblemType: Package DistroRelease: Ubuntu 24.04 Package: input-remapper-gtk (not installed) ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 AptOrdering: python3-inputremapper:amd64: Install input-remapper-daemon:amd64: Install input-remapper-gtk:amd64: Install input-remapper:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 29 05:16:56 2024 DuplicateSignature: package:input-remapper-gtk:(not installed) Unpacking python3-inputremapper (2.0.1-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-inputremapper_2.0.1-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/input_remapper-2.0.1.egg-info/PKG-INFO', which is also in package input-remapper 2.0.1 ErrorMessage: trying to overwrite '/usr/bin/input-remapper-gtk', which is also in package input-remapper 2.0.1 InstallationDate: Installed on 2024-05-31 (29 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: input-remapper Title: package input-remapper-gtk (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/input-remapper-gtk', which is also in package input-remapper 2.0.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: input-remapper (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071510 Title: package input-remapper-gtk (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/input-remapper-gtk', which is also in package input-remapper 2.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/input-remapper/+bug/2071510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
Just another reason to avoid snaps. For me... why is LXD a snap??? If you're using LXD then the machine is likely an important hypervisor host and why wouldn't you want LXD fully integrated into the host's filesystem. Isolating the program that isolates others? No sane person would install proxmox as a snap. Why would LXD be different? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064356] [NEW] 24.04 rtorrent buffer overflows when using session
Public bug reported: rtorrent is crashing whenever it is tried to be run with a session # mkdir .session # rtorrent -s .session *** buffer overflow detected ***: terminated Aborted (core dumped) 1) release of ubuntu: Ubuntu Server 24.04 (in an LXC container) 2) 0.9.8-1build3 3) Expected rtorrent to run like it did under 23.10 4) crashed with a buffer overflow. If I don't use a "session" in rtorrent it runs fine. But with a session it throws the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rtorrent 0.9.8-1build3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20240423 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) Date: Tue Apr 30 21:55:34 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= SourcePackage: rtorrent UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rtorrent (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cloud-image noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064356 Title: 24.04 rtorrent buffer overflows when using session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtorrent/+bug/2064356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056100] Re: sru cloud-init (24.1.3 update) Focal, Jammy, and Mantic
Hello all, SQA has tested cloud-init on jammy and focal and didn't run into any issues. The results are only visible by Canonical employees but, The Focal testplan can be found at: https://solutions.qa.canonical.com/releasetests/24059ebd-9fd9-4d5f-8619-ca359e25809d/ and Jammy testplan can be found at: https://solutions.qa.canonical.com/releasetests/d49f6faa-7a58-4002-90d3-1f089f30b02d/ Sorry there's a bug in our version report script, which said 23.4.4 in the report, but we confirmed manually 24.1.3 is actually tested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056100 Title: sru cloud-init (24.1.3 update) Focal, Jammy, and Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059970] [NEW] Graphics driver wrong cant change. Now trying to upgrade to 22.04 not working. Hoped upgrade solved graphics issue.
Public bug reported: Computer locking on boot due to Graphics. llvmpipe (LLVM 12.0.0, 256 bits) this driver comes up in safe mode. I have installed, uninstalled, purged, re-installed Nvidia many times. The system still boots only in safe mode and with the aforementioned graphics. I cannot run a second monitor which is my main issue. I can boot if I change boot to "nomodeset"" but that leaves the second monitor unable to function. I wanted to upgrade to 22.04 with the thought this may solve this issue, but that did not work either. Currently I am downloading an image of 22.04 to install from scratch. I am a newbie but know enough to know I don't know jack. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.41 ProcVersionSignature: Ubuntu 5.15.0-101.111~20.04.1-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon Apr 1 12:52:03 2024 InstallationDate: Installed on 2024-03-30 (1 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2024-04-01 (0 days ago) VarLogDistupgradeAptlog: Log time: 2024-04-01 12:50:14.113864 Log time: 2024-04-01 12:50:26.804172 Log time: 2024-04-01 12:51:49.392804 Log time: 2024-04-01 12:52:05.941324 VarLogDistupgradeTermlog: ** 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/2059970 Title: Graphics driver wrong cant change. Now trying to upgrade to 22.04 not working. Hoped upgrade solved graphics issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2059970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058328] [NEW] rasdaemon doesn't actually log anything
Public bug reported: Release:23.10 % apt policy rasdaemon rasdaemon: Installed: 0.6.8-1.1 Candidate: 0.6.8-1.1 Version table: *** 0.6.8-1.1 500 500 http://us.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages 100 /var/lib/dpkg/status % uname -r 6.5.0-26-generic Machine check errors are noted in dmesg, but rasdaemon logs nothing. [Mon Mar 18 21:56:36 2024] mce: [Hardware Error]: Machine check events logged [Mon Mar 18 21:56:37 2024] mce: [Hardware Error]: Machine check events logged [Mon Mar 18 22:07:29 2024] mce: [Hardware Error]: Machine check events logged [Mon Mar 18 22:07:30 2024] mce: [Hardware Error]: Machine check events logged [Mon Mar 18 22:15:20 2024] mce: [Hardware Error]: Machine check events logged % sudo journalctl -f -u rasdaemon Mar 18 21:52:41 fractal rasdaemon[988]: Family 6 Model b7 CPU: only decoding architectural errors Mar 18 21:52:41 fractal rasdaemon[988]: mce:mce_record event enabled Mar 18 21:52:41 fractal systemd[1]: Started rasdaemon.service - RAS daemon to log the RAS events. Mar 18 21:52:41 fractal rasdaemon[988]: Enabled event mce:mce_record Mar 18 21:52:41 fractal rasdaemon[988]: ras:extlog_mem_event event enabled Mar 18 21:52:41 fractal rasdaemon[988]: Enabled event ras:extlog_mem_event Mar 18 21:52:41 fractal rasdaemon[988]: rasdaemon: Recording mc_event events Mar 18 21:52:41 fractal rasdaemon[988]: rasdaemon: Recording aer_event events Mar 18 21:52:41 fractal rasdaemon[988]: rasdaemon: Recording extlog_event events Mar 18 21:52:41 fractal rasdaemon[988]: rasdaemon: Recording mce_record events % sudo ras-mc-ctl --errors No Memory errors. No PCIe AER errors. No Extlog errors. No MCE errors. ** Affects: rasdaemon (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/2058328 Title: rasdaemon doesn't actually log anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/2058328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056605] [NEW] HWE 6.5.0-25-generic kernel does not boot due to VirtualBox
Public bug reported: Hi Everyone, I'm running Ubuntu 22.04, x86_64, fully patched. I have VirtualBox installed. Both linux-image-generic and linux-image-generic-hwe kernels are installed, just in case. And I almost always boot to the HWE kernel. I performed an `aptitude upgrade` and and `aptitude safe-upgrade` this morning. The upgrade installed the 6.5.0-25-generic kernel. During the reboot, the machine hung with the message "Failed to start LSB: VirtualBox Linux kernel module." I reset the machine, selected the [old] 6.5.0-21-generic kernel, and the machine booted Ok. - After the failed boot and reboot to the lower kernel, I performed: $ sudo apt-get remove --purge '*6.5.0-25-generic*' $ sudo apt-mark hold '*6.5.0-25-generic*' - $ ls /lib/modules 5.15.0-100-generic 6.5.0-21-generic $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy ** Affects: virtualbox (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/2056605 Title: HWE 6.5.0-25-generic kernel does not boot due to VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2056605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810241] Re: NULL dereference when decompressing specially crafted archives
Update to my comment, issue is applicable to versions prior to 1.32 of TAR. Be that as it may, Jammy is not affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1810241 Title: NULL dereference when decompressing specially crafted archives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1810241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810241] Re: NULL dereference when decompressing specially crafted archives
This issue is shown as Open on Jammy. The CVE is applicable to 1.32 and prior versions of TAR. Jammy uses 1.34, so this status should be not affected or closed. This was fixed in Focal in 1.30+dfsg-7ubuntu0.20.04.1. Please update the CVE status on Jammy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1810241 Title: NULL dereference when decompressing specially crafted archives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1810241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
Sebastien, do you know how I can mark my ethernet connection as the default one? The ethernet connection I want to set as default is the wired ethernet, which is enp4s0 in the dumps shown above. I cannot find a setting in the Settings program to set a default connection. I also cannot find a discussion of it in the docs.[1,2] The docs only say the program usually picks the right one:[1] In most cases the wired network connection will simply work without any changes to the default Kubuntu configuration. Wired network connections are selected as default when they are available. (And it is not picking a wired connection as stated in the docs. It is picking a Wifi connection via the Android phone). [1] https://userbase.kde.org/Kubuntu/Basic/en#Networking [2] https://userbase.kde.org/NetworkManagement -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
> Sebastien Bacher wrote: > > yes, the current details are about a working system but we want to work on > the bug Thanks again Sebastien. I rebooted the machine with the phone tethered and it used USB0 as the network adapter. I then ran 'apport-collect 1975549'. Here is the current nmcli when running the command in its current state (boot with phone tethered): $ nmcli usb0: connected to Ethernet "Google Nexus 4/5/7/10" ethernet (rndis_host), 82:1F:DF:52:0B:39, hw, mtu 1500 ip4 default inet4 192.168.11.182/24 route4 0.0.0.0/0 route4 192.168.11.0/24 route4 169.254.0.0/16 inet6 fe80::801f:dfff:fe52:b39/64 route6 fe80::/64 enp4s0: disconnected "Qualcomm Atheros Killer E2400" 1 connection available ethernet (alx), D8:9E:F3:92:24:60, hw, mtu 1500 wlp3s0: disconnected "Qualcomm Atheros QCA9377" wifi (ath10k_pci), 90:32:4B:76:E0:B9, hw, mtu 1500 p2p-dev-wlp3s0: disconnected "p2p-dev-wlp3s0" wifi-p2p, hw lo: unmanaged "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536 DNS configuration: servers: 192.168.11.111 interface: usb0 Use "nmcli device show" to get complete information about known devices and "nmcli connection show" to get an overview on active connection profiles. Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592937/+files/nmcli-dev.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592935/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592936/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592934/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592933/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592932/+files/PciNetwork.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] NetDevice.wlp3s0.txt
apport information ** Attachment added: "NetDevice.wlp3s0.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592930/+files/NetDevice.wlp3s0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592931/+files/NetworkManager.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] NetDevice.usb0.txt
apport information ** Attachment added: "NetDevice.usb0.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592929/+files/NetDevice.usb0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592928/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] NetDevice.enp4s0.txt
apport information ** Attachment added: "NetDevice.enp4s0.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592927/+files/NetDevice.enp4s0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592926/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592925/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592924/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
apport information
** Description changed:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It literally
calls the connection "ethernet", as if it was using the network adapter.
This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called "ethernet"
instead of something more meaningful like "USB" or "Android" or "wired
hotspot".
The third item ("ethernet" name when using Android phone) was misleading
enough to waste a lot of time troubleshooting the issue. I thought I had
an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is the
Android phone uses Wifi and it is on a different VLAN and subnet to keep
traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.24
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2022-02-05 (108 days ago)
+ InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
+ IpRoute:
+ default via 192.168.11.111 dev usb0 proto dhcp metric 100
+ 169.254.0.0/16 dev usb0 scope link metric 1000
+ 192.168.11.0/24 dev usb0 proto kernel scope link src 192.168.11.182 metric
100
+ Package: network-manager 1.22.10-1ubuntu2.3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
+ Tags: focal
+ Uname: Linux 5.13.0-44-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ nmcli-con:
+
[Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
> It's a bit weird, https://launchpadlibrarian.net/602981658/nmcli-dev.txt > shows no connection associated to the usb device nor IP for it Thanks again Sebastien. This may be because I booted the machine with the phone unplugged. I can run apport again with the phone plugged in (and then reboot) to duplicate the issue. Would you like me to run apport again after booting with the phone plugged in? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
> Thank you for your bug report, could you do > > $ apport-collect 1975549 > > on the machine at the time you are having the issue? Thanks Sebastien. This caught my eye (from the apport generated files): Android phone: * ID_NET_LINK_FILE=/usr/lib/systemd/network/73-usb-net-by-mac.link NIC adapter: * ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link I can envision a situation where 73 is given higher precedence than 99. What I don't know is, why things changed recently (assuming they were the same way in the past). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592648/+files/nmcli-dev.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592647/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592646/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592645/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592644/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592642/+files/NetworkManager.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592643/+files/PciNetwork.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] NetDevice.wlp3s0.txt
apport information ** Attachment added: "NetDevice.wlp3s0.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592641/+files/NetDevice.wlp3s0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] NetDevice.usb0.txt
apport information ** Attachment added: "NetDevice.usb0.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592640/+files/NetDevice.usb0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592639/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] NetDevice.enp4s0.txt
apport information ** Attachment added: "NetDevice.enp4s0.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592638/+files/NetDevice.enp4s0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592637/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592636/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1975549/+attachment/5592635/+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/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
apport information
** Tags added: apport-collected focal
** Description changed:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It literally
calls the connection "ethernet", as if it was using the network adapter.
This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called "ethernet"
instead of something more meaningful like "USB" or "Android" or "wired
hotspot".
The third item ("ethernet" name when using Android phone) was misleading
enough to waste a lot of time troubleshooting the issue. I thought I had
an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is the
Android phone uses Wifi and it is on a different VLAN and subnet to keep
traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.24
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2022-02-05 (107 days ago)
+ InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
+ IpRoute:
+ default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
+ 169.254.0.0/16 dev enp4s0 scope link metric 1000
+ 172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
+ Package: network-manager 1.22.10-1ubuntu2.3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
+ Tags: focal
+ Uname: Linux 5.13.0-44-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ nmcli-con:
+ NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
+ Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
+ nmcli-nm:
+ RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
+ running 1.22.10 connected started full enabled enabled
enabled enabled enabled
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592634/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] [NEW] NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
Public bug reported:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It literally
calls the connection "ethernet", as if it was using the network adapter.
This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called "ethernet"
instead of something more meaningful like "USB" or "Android" or "wired
hotspot".
The third item ("ethernet" name when using Android phone) was misleading
enough to waste a lot of time troubleshooting the issue. I thought I had
an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is the
Android phone uses Wifi and it is on a different VLAN and subnet to keep
traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
** Affects: network-manager (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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956040] Re: Malformed TLS handshake with OpenSSL 3.0 (breaks subversion)
@schopin This curious patch appears to fix subversion in my use cases, and it looks like wireshark can disect the TLS traffic again too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956040 Title: Malformed TLS handshake with OpenSSL 3.0 (breaks subversion) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/serf/+bug/1956040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960280] Re: subverion's svn fails against https servers
I believe that this bug is a duplicate of this one: https://bugs.launchpad.net/ubuntu/+source/serf/+bug/1956040 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960280 Title: subverion's svn fails against https servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1960280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960848] Re: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure
I've uploaded a new upstream version, also to sid. Can you upload to jammy? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960848 Title: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1960848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960848] Re: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure
I've got a fix for this, and I'll upload a new upstream version of gscan2pdf to fix this ASAP, I hope in the next 12 hours. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960848 Title: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1960848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960848] Re: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure
I'll install sane-backends v1.1.1 and take a look. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960848 Title: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1960848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956040] Re: Malformed TLS handshake with OpenSSL 3.0 (breaks subversion)
** Tags added: transition-openssl3-jj -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956040 Title: Malformed TLS handshake with OpenSSL 3.0 (breaks subversion) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/serf/+bug/1956040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956376] Re: Constant stream of message boxes with "Unable to mount MTP device" plugging in GoPro HERO 7
>Unable to mount HERO7 >Unable to open MTP device "xxx,yyy" > > In the message, xxx appear to always be 001. yyy changes, and > takes the values 001, 002, 003, 004, ... it looks like the yyy values loop at 128. So the range is [001, 002, ..., 126, 127]. After 127 the value loops back around to 001. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956376 Title: Constant stream of message boxes with "Unable to mount MTP device" plugging in GoPro HERO 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1956376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956376] Re: Constant stream of message boxes with "Unable to mount MTP device" plugging in GoPro HERO 7
** Attachment added: "A small sampling of the message boxes on the Desktop" https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1956376/+attachment/5551156/+files/message-box-spam.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956376 Title: Constant stream of message boxes with "Unable to mount MTP device" plugging in GoPro HERO 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1956376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956376] [NEW] Constant stream of message boxes with "Unable to mount MTP device" plugging in GoPro HERO 7
Public bug reported: Hi Everyone, I am using Ubuntu 20.04.3 LTS, x86_64, fully patched. I installed Cinnamon and got rid of GNOME because I needed a tiling window manager. The File Manager used with Cinnamon is Nemo. I bought a GoPro HERO 7 and plugged it in over USB to charge the battery. The result is a constant stream of message boxes that states: Unable to mount HERO7 Unable to open MTP device "xxx,yyy" In the message, xxx appear to always be 001. yyy changes, and takes the values 001, 002, 003, 004, ... A new message box appears approximately every 10 seconds. I think one message box will do just fine. There's no need to spam me every 10 seconds. My apologies if this is not a Nemo issue. Looking at the message box, it is the sort of thing provided by the file manager. == $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal $ wmctrl -m Name: Mutter (Muffin) Class: N/A PID: N/A Window manager's "showing the desktop" mode: OFF $ apt-cache show lightdm Package: lightdm Architecture: amd64 Version: 1.30.0-0ubuntu4~20.04.1 Priority: optional Section: universe/x11 $ apt-cache show cinnamon Package: cinnamon Architecture: amd64 Version: 4.4.8-4ubuntu0.2 Priority: optional Section: universe/x11 Origin: Ubuntu $ apt-cache show nemo Package: nemo Architecture: amd64 Version: 4.4.2-2ubuntu2 Priority: optional Section: universe/misc Origin: Ubuntu ** Affects: nemo (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/1956376 Title: Constant stream of message boxes with "Unable to mount MTP device" plugging in GoPro HERO 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1956376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956159] [NEW] XDMCP sessions show "Oh no!" screen instead of greeter
Public bug reported: On both Impish and Jammy, gdm3 does not offer greeter to XDMCP sessions. Instead, it shows the "Oh no! Something has gone wrong" image on the root window. This indicates that the XDMCP part is working, but the session is not. Expected: remote sessions should work out of the box. $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 $ apt policy gdm3 gdm3: Installed: 41.0-3ubuntu2 Candidate: 41.0-3ubuntu2 Version table: *** 41.0-3ubuntu2 500 500 http://mirrors.sonic.net/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy gnome-session-bin gnome-session-bin: Installed: 40.1.1-3ubuntu1 Candidate: 40.1.1-3ubuntu1 Version table: *** 40.1.1-3ubuntu1 500 500 http://mirrors.sonic.net/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status $ diff -u gdm3/etc/gdm3/custom.conf /etc/gdm3/custom.conf --- gdm3/etc/gdm3/custom.conf 2021-12-08 08:06:05.0 -0800 +++ /etc/gdm3/custom.conf 2022-01-01 09:54:55.293144516 -0800 @@ -18,6 +18,9 @@ [security] [xdmcp] +Enable=true +HonorIndirect=true +ShowLocalGreeter=false [chooser] @@ -25,5 +28,5 @@ # Uncomment the line below to turn on debugging # More verbose logs # Additionally lets the X server dump core if it crashes -#Enable=true +Enable=true ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog from remote session attempt" https://bugs.launchpad.net/bugs/1956159/+attachment/5550576/+files/xdmcp-session-syslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956159 Title: XDMCP sessions show "Oh no!" screen instead of greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1956159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956040] [NEW] Malformed TLS handshake with OpenSSL 3.0 (breaks subversion)
Public bug reported: This bug is a regression in libserf-1-1 version 1.3.9-10ubuntu1, which switched to OpenSSL 3.0. Version 1.3.9-10, which uses OpenSSL 1.1, does not have this bug. Using version 1.3.9-10ubuntu1, Subversion, which is the only dependant of this package in the Ubuntu repository, breaks when using the https protocol. For instance, the command... svn info https://svn.apache.org/repos/asf/subversion/trunk ... will no longer work and, depending on the server, may close the connection or return some sort of error. Attempting to analyze the problem in wireshark, I discovered that the TLS traffic generated by libserf is malformed and cannot be parsed by wireshark's packet disassemblers. At a glance, it appears that libserf is sending a raw TLS Client Hello without first sending a TLS record header. For instance, to use the illustrated handshake example here [1], the handshake that libserf generates appears to be missing the first five bytes (the TLS record header) and instead begins with what the illustrated example calls the TLS handshake header. [1] https://tls.ulfheim.net/ ** Affects: serf (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/1956040 Title: Malformed TLS handshake with OpenSSL 3.0 (breaks subversion) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/serf/+bug/1956040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953733] [NEW] package matlab-support 0.0.21.1 failed to install/upgrade: 已安装 matlab-support 软件包 post-installation 脚本 子进程返回错误状态 1
Public bug reported: I can not install it. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: matlab-support 0.0.21.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 18:22:31 2021 ErrorMessage: 已安装 matlab-support 软件包 post-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2021-12-07 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: matlab-support Title: package matlab-support 0.0.21.1 failed to install/upgrade: 已安装 matlab-support 软件包 post-installation 脚本 子进程返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: matlab-support (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953733 Title: package matlab-support 0.0.21.1 failed to install/upgrade: 已安装 matlab- support 软件包 post-installation 脚本 子进程返回错误状态 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matlab-support/+bug/1953733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953305] [NEW] hdparm and inappropriate ioctl for NVMe device
Public bug reported: I'm working on a HP ProBook 640 G4 (https://www.amazon.com/gp/product/B088KL637G). The machine runs Ubuntu 20.04.3 LTS x86_64 fully patched. The machine has a Samsung EVO SSD. The SSD is a NVMe device on the PCI Express bus. According to HP's Maintenance and Service Guide (http://h10032.www1.hp.com/ctg/Manual/c05956070.pdf), the interface is ATA-7. Running `hdparm -tT /dev/nvme0n1` results in: # hdparm -tT /dev/nvme0n1 /dev/nvme0n1: Timing cached reads: 29318 MB in 1.99 seconds = 14752.57 MB/sec HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device Timing buffered disk reads: 8206 MB in 3.00 seconds = 2735.13 MB/sec I believe hdparm should be able to communicate with the device since it uses a standard ATA interface. Reading through the web about the error, one source says the error is due to a down leve hdparm. Cf., https://www.cyberciti.biz/faq/hdiodrive_cmdidentify-failed- inappropriate-ioctl-device/. Ubuntu supplies hdparm v9.58, but the latest is hdparm v9.62. hdparm v9.58 was released in October 2018, while hdparm v9.58 was released May 2021. It may be a time to update hdparm. - $ lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal $ apt info hdparm Package: hdparm Version: 9.58+ds-4 Priority: standard Section: admin Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Alexandre Mestiashvili Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 251 kB Depends: libc6 (>= 2.14), lsb-base Recommends: powermgmt-base Homepage: http://sourceforge.net/projects/hdparm/ Task: standard Download-Size: 94.8 kB APT-Manual-Installed: no APT-Sources: http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages Description: tune hard disk parameters for high performance Get/set device parameters for Linux SATA/IDE drives. ** Affects: hdparm (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/1953305 Title: hdparm and inappropriate ioctl for NVMe device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/1953305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951701] [NEW] systemd-resolved doesn't play well with dnsmasq cname entries
Public bug reported: See also https://community.ui.com/questions/USG-dnsmasq-cname-options- not-playing-well-with-systemd- resolved/11592045-d530-4f55-9cd2-9d45fc637e1d I've set up my UniFi Security Gateway with dnsmasq so that I can resolve local hostnames on my network. I can resolve most hostnames, except for one: unifi. $ nslookup unifi Server: 127.0.0.53 Address:127.0.0.53#53 ** server can't find unifi.lan: SERVFAIL $ nslookup unifi.lan Server: 127.0.0.53 Address:127.0.0.53#53 ** server can't find unifi.lan: SERVFAIL However, it works if I specifically query my router: $ nslookup unifi 192.168.1.1 Server: 192.168.1.1 Address:192.168.1.1#53 unifi.lan canonical name = unifi. Name: unifi Address: 192.168.1.6 $ nslookup unifi.lan 192.168.1.1 Server: 192.168.1.1 Address:192.168.1.1#53 unifi.lan canonical name = unifi. Name: unifi Address: 192.168.1.6 So this seems specifically like a problem with systemd-resolved. Asking systemd-resolved to resolve these hosts is interesting: $ systemd-resolve unifi unifi.lan unifi: 192.168.1.6 -- link: wlp2s0 -- Information acquired via protocol DNS in 6.4ms. -- Data is authenticated: no unifi.lan: resolve call failed: No appropriate name servers or networks for name found Following the steps [here](https://wiki.ubuntu.com/DebuggingSystemd#systemd- resolved_:_DNS_resolution_issues) I captured some systemd-resolved logs: - unifi.lan error: https://pastebin.com/pjzUvQfi - unifi success: https://pastebin.com/QN8hD9a1 And I found a setting in the router that seemed to be causing the problem. Removing that setting in my router resulted in this log: - unifi.lan success after deleting option cname: https://pastebin.com/4csYdW5B But ultimately this seems like a bug in systemd-resolved since things seem to be working correctly if I take systemd-resolved out of the loop $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.13 Candidate: 245.4-4ubuntu3.13 Version table: *** 245.4-4ubuntu3.13 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3.11 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 245.4-4ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: See also https://community.ui.com/questions/USG-dnsmasq-cname-options- not-playing-well-with-systemd- resolved/11592045-d530-4f55-9cd2-9d45fc637e1d I've set up my UniFi Security Gateway with dnsmasq so that I can resolve local hostnames on my network. I can resolve most hostnames, except for one: unifi. $ nslookup unifi Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find unifi.lan: SERVFAIL $ nslookup unifi.lan Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find unifi.lan: SERVFAIL However, it works if I specifically query my router: $ nslookup unifi 192.168.1.1 Server: 192.168.1.1 Address: 192.168.1.1#53 unifi.lan canonical name = unifi. Name: unifi Address: 192.168.1.6 $ nslookup unifi.lan 192.168.1.1 Server: 192.168.1.1 Address: 192.168.1.1#53 unifi.lan canonical name = unifi. Name: unifi Address: 192.168.1.6 So this seems specifically like a problem with systemd-resolved. Asking systemd-resolved to resolve these hosts is interesting: $ systemd-resolve unifi unifi.lan unifi: 192.168.1.6 -- link: wlp2s0 -- Information acquired via protocol DNS in 6.4ms. -- Data is authenticated: no unifi.lan: resolve call failed: No appropriate name servers or networks for name found Following the steps [here](https://wiki.ubuntu.com/DebuggingSystemd#systemd- resolved_:_DNS_resolution_issues) I captured some systemd-resolved logs: - - unifi.lan error: https://pastebin.com/pjzUvQfi - - unifi success: https://pastebin.com/QN8hD9a1 + - unifi.lan error: https://pastebin.com/pjzUvQfi + - unifi success: https://pastebin.com/QN8hD9a1 And I found a setting in the router that seemed to be causing the problem. Removing that setting in my router resulted in this log: - - unifi.lan success after deleting option cname: + - unifi.lan success after deleting option cname: https://pastebin.com/4csYdW5B But ultimately this seems like a bug in systemd-resolved since things seem to be working correctly if I take systemd-resolved out of the loop + + $ lsb_release -rd + Description: Ubuntu 20.04.3 LTS + Release: 20.04 + $ apt-cache policy systemd + systemd: + Installed: 245.4-4ubuntu3.13 + Candidate:
[Bug 1950515] Re: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others
I have the same issue with a Dell XPS 17 9700 when using 5.13.0-21. 5.13.0-20 works with a full power cycle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950515 Title: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938978] Re: nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid)
** Description changed: ProblemType: Package DKMSBuildLog: - DKMS make.log for nvidia-340-340.108 for kernel 5.11.0-25-generic (x86_64) - to. 05. aug. 06:23:28 +0200 2021 - NVIDIA: calling KBUILD... - make[1]: Entering directory '/usr/src/linux-headers-5.11.0-25-generic' - test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( - \ - echo >&2;\ - echo >&2 " ERROR: Kernel configuration is invalid.";\ - echo >&2 " include/generated/autoconf.h or include/config/auto.conf are - missing.";\ - echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it + DKMS make.log for nvidia-340-340.108 for kernel 5.11.0-25-generic (x86_64) + to. 05. aug. 06:23:28 +0200 2021 + NVIDIA: calling KBUILD... + make[1]: Entering directory '/usr/src/linux-headers-5.11.0-25-generic' + test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( + \ + echo >&2;\ + echo >&2 " ERROR: Kernel configuration is invalid.";\ + echo >&2 " include/generated/autoconf.h or include/config/auto.conf are + missing.";\ + echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it ."; \ - echo >&2 ; \ - /bin/false) - make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia-340/340.108/build \ - single-build= \ - need-builtin=1 need-modorder=1 -cc -Wp,-MMD,/var/lib/dkms/nvidia-340/340.108/build/.nv.o.d -nostdinc -isyste + echo >&2 ; \ + /bin/false) + make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia-340/340.108/build \ + single-build= \ + need-builtin=1 need-modorder=1 + cc -Wp,-MMD,/var/lib/dkms/nvidia-340/340.108/build/.nv.o.d -nostdinc -isyste m /usr/lib/gcc/x86_64-linux-gnu/9/include -I./arch/x86/include -I./arch/x86/inc lude/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/gener ated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/k...etc - /var/crash$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 06:24:36 2021 InstallationDate: Installed on 2021-05-01 (95 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: - dpkg 1.19.7ubuntu3 - apt 2.0.6 + dpkg 1.19.7ubuntu3 + apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938978 Title: nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1938978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804592] Re: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
This issue is still present in Ubuntu 20.04.3 LTS running the 5.4.0-81-generic kernel. [0.725170] xhci_hcd :02:00.0: xHCI Host Controller [0.725172] xhci_hcd :02:00.0: new USB bus registered, assigned bus number 4 [0.725174] xhci_hcd :02:00.0: Host supports USB 3.1 Enhanced SuperSpeed [0.725242] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [0.725253] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04 [0.725254] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.725255] usb usb4: Product: xHCI Host Controller [0.725255] usb usb4: Manufacturer: Linux 5.4.0-81-generic xhci-hcd [0.725256] usb usb4: SerialNumber: :02:00.0 [0.725340] hub 4-0:1.0: USB hub found [0.725346] hub 4-0:1.0: 2 ports detected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804592 Title: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939671] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939671 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1939671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939399] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939399 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1939399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939251] Re: nvidia driver crashes after kernel upgrade
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug is no longer a duplicate of bug 1939254 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939251 Title: nvidia driver crashes after kernel upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939254] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939254 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1939254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939226] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939226 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1939226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939220] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939220 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1939220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939185] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939185 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1939185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939183] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939183 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1939183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1920649] Re: ubuntu 20.04 LTS - aide crashes on initialization
Thanks - I repeated your recipe step by step, and, sure enough, running aideinit -f did not cause a segfault. But after running for over an hour and a half, with zero bytes written to aide.db.new, it was clearly not going anywhere, so I killed it. Joe On Sun, Jul 25, 2021 at 11:40 AM Konstantin Kalmykov < 1920...@bugs.launchpad.net> wrote: > I can tell what I did to mitigate this bug, and It’s worked for me (do > it as power user or root): > > 1. Completely purge installed AIDE: > > apt purge aide aide-common > rm -rf /var/log/aide > > 2. Install AIDE back again: > > apt update > apt install aide-common aide-dynamic > > 3. Then rebuild config: > > update-aide.conf > cp -v /var/lib/aide/aide.conf.autogenerated /etc/aide/aide.conf > > 4. Run init script: > > aideinit -f > > Then for me it was no errors, and AIDE running well. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1920649 > > Title: > ubuntu 20.04 LTS - aide crashes on initialization > > Status in aide package in Ubuntu: > Confirmed > > Bug description: > root@flynn:~# aideinit > Running aide --init... > Segmentation fault (core dumped) > AIDE --init return code 139 > > > [Sat Mar 20 18:21:48 2021] aide[6409]: segfault at 0 ip 7f903f98714b > sp 7ffefb573de8 error 4 in libc-2.31.so[7f903f88c000+178000] > [Sat Mar 20 18:21:48 2021] Code: 89 01 48 83 c8 ff c3 0f 1f 84 00 00 00 > 00 00 f3 0f 1e fa 48 8b 05 25 ad 0c 00 48 83 ff 10 74 47 48 83 ff 1a 74 49 > 48 8b 40 60 <48> 8b 10 48 85 d2 75 12 eb 1b 0f 1f 00 48 8b 50 10 48 83 c0 > 10 48 > > root@flynn:~# uname -a > Linux flynn 5.8.0-45-generic #51~20.04.1-Ubuntu SMP Tue Feb 23 13:46:31 > UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > root@flynn:~# > > root@flynn:~# cat /etc/os-release > NAME="Ubuntu" > VERSION="20.04.2 LTS (Focal Fossa)" > ID=ubuntu > ID_LIKE=debian > PRETTY_NAME="Ubuntu 20.04.2 LTS" > VERSION_ID="20.04" > HOME_URL="https://www.ubuntu.com/; > SUPPORT_URL="https://help.ubuntu.com/; > BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; > PRIVACY_POLICY_URL=" > https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; > VERSION_CODENAME=focal > UBUNTU_CODENAME=focal > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: aide 0.16.1-1build2 > ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-45-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.16 > Architecture: amd64 > CasperMD5CheckResult: skip > Date: Sat Mar 20 18:45:43 2021 > InstallationDate: Installed on 2021-03-20 (0 days ago) > InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release > amd64 (20210209.1) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: aide > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1920649/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920649 Title: ubuntu 20.04 LTS - aide crashes on initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1920649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870971] Re: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode
Add an Acer Aspire 5 Laptop (https://www.amazon.com/gp/product/B07RF1XD36) to the list of problem platforms. The machine was just upgraded to Linux Mint 20.2. Mint 20.1 was OK. Linux Mint 20 is based on Ubuntu 20.04 LTS. - $ dmesg | grep -i error [0.755376] RAS: Correctable Errors collector initialized. [0.775485] Error adding keys to platform keyring UEFI:db [0.775487] Error adding keys to platform keyring UEFI:db [8.440674] EXT4-fs (nvme0n1p2): re-mounted. Opts: errors=remount-ro [9.210068] snd_rn_pci_acp3x: probe of :05:00.5 failed with error -22 [ 20.681023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=4 [ 20.681156] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 688 thread Xorg:cs0 pid 742 [ 25.505358] [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 [ 25.505562] [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 [ 25.505769] [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 [ 25.505985] [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 [ 25.506167] [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 [ 25.506369] [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 [ 25.506579] [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 [ 25.506789] [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 [ 25.507012] [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 [ 25.507220] [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 [ 25.507402] [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 [ 25.507601] [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929712] [NEW] Crashed on install on RPi3B+
Public bug reported: Install Error ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi armv7l ApportVersion: 2.20.11-0ubuntu50 Architecture: armhf CasperMD5CheckResult: skip Date: Wed May 26 09:33:08 2021 ImageMediaBuild: 20201028 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UbiquityDebug: UbiquitySyslog: UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf groovy oem-config -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929712 Title: Crashed on install on RPi3B+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1929712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924929] [NEW] Upgrade from 18.04 to 20.04 fails. Purged all PPA's
Public bug reported: I removed all PPA's and still get the same error. I went through the logs and found some python and qt problems. I think I resolved those, but I am still getting the error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: X-Cinnamon Date: Sun Apr 18 15:04:09 2021 InstallationDate: Installed on 2019-06-07 (681 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-04-18 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924929 Title: Upgrade from 18.04 to 20.04 fails. Purged all PPA's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922949] [NEW] Can't stop the computer from sleeping or hibernating; lost SSH access
Public bug reported: I'm using Ubuntu 20.04 LTS, x86_64, fully patched. I removed the stock window/desktop manager because Gnome3 and its derivatives suck. I installed Cinnamon desktop to get a usable desktop that I can interact with. The login manager is lightdm. Despite my sincerest efforts, I cannot stop this computer from sleeping or hibernating. I've set my power management settings thusly: * turn monitor off: 15 minutes * turn disk off: never * lock computer: off I disabled apcid.service. I cannot find a setting in lightdm.conf to disable sleep or hibernation. After about 15 minutes, the computer sleeps or hibernates and I lose my SSH connection. The only workaround I have found is go over to the computer and login. Once logged in the computer honors the "no sleep" or "no hibernate" settings. Ubuntu's wiki article on power management does not offer useful advice. I try things suggested in places like Ask Ubuntu and Super User but the problem persists. Based on my searching this appears to be a widespread problem on Linux. Sadly, OS X and Windows don't seem to have these problems. Only Linux. This is incredibly annoying. ** Affects: cinnamon (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/1922949 Title: Can't stop the computer from sleeping or hibernating; lost SSH access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1922949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660121] Re: LightDM can't use the user background on Mate
** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660121 Title: LightDM can't use the user background on Mate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1660121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922212] Re: SSHD does not honor configuration files
Something is really sideways here: # sshd -T | grep -i -E 'password|pam|authentication|publickey' usepam yes hostbasedauthentication no pubkeyauthentication yes kerberosauthentication no gssapiauthentication no passwordauthentication yes kbdinteractiveauthentication yes challengeresponseauthentication yes permitemptypasswords no authenticationmethods any -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922212 Title: SSHD does not honor configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922212] Re: SSHD does not honor configuration files
Also see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109846. It is an old bug report (from 2001), but it says this is what we need: PasswordAuthentication no ChallengeResponseAuthentication no UsePAM no ** Bug watch added: Debian Bug tracker #109846 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109846 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922212 Title: SSHD does not honor configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922212] Re: SSHD does not honor configuration files
This gets worse. Adding the following to the tail of /etc/ssh/sshd_config does not configure the service properly. PasswordAuthentication no ChallengeResponseAuthentication no UsePAM no PubkeyAuthentication yes PermitRootLogin no The login attempts are still allowed: Apr 01 09:31:10 localhost sshd[239597]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.77 user=root Apr 01 09:31:13 localhost sshd[239597]: Failed password for root from 49.88.112.77 port 50368 ssh2 Apr 01 09:31:16 localhost sshd[239597]: Failed password for root from 49.88.112.77 port 50368 ssh2 Apr 01 09:31:19 localhost sshd[239597]: Failed password for root from 49.88.112.77 port 50368 ssh2 Apr 01 09:31:20 localhost sshd[239597]: Received disconnect from 49.88.112.77 port 50368:11: [preauth] Apr 01 09:31:20 localhost sshd[239597]: Disconnected from authenticating user root 49.88.112.77 port 50368 [preauth] Apr 01 09:31:20 localhost sshd[239597]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.77 user=root -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922212 Title: SSHD does not honor configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922212] [NEW] SSHD does not honor configuration files
Public bug reported: I'm working on Ubuntu 20, x86_64, fully patched. # lsb_release -a Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS ... We are seeing reports of failed password-based logins using root: jounralctl -xe ... Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 49.88.112.77 port 36206 ssh2 Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 49.88.112.77 port 36206 ssh2 ... There are three attempts every second or two (literally): # journalctl -xe | grep -i -c 'Failed password for root' 324 Our OpenSSH server is configured with both no-password based logins and no-root logins. # ls /etc/ssh/sshd_config.d/ 10_pubkey_auth.conf 20_disable_root_login.conf # cat /etc/ssh/sshd_config.d/10_pubkey_auth.conf # Disable passwords PasswordAuthentication no ChallengeResponseAuthentication no UsePAM no # Enable public key PubkeyAuthentication yes # cat /etc/ssh/sshd_config.d/20_disable_root_login.conf PermitRootLogin no The config files are included last in our /etc/ssh/sshd_config file: # tail -n 3 /etc/ssh/sshd_config # For some reason OpenSSH does not include additional conf files by default. Include /etc/ssh/sshd_config.d/*.conf I dislike modifying /etc/ssh/sshd_config since it will be overwritten by the distro. With that said, I modified it without success. It really annoys me that we can't secure this service. Something looks very broken here. - # apt-cache show openssh-server Package: openssh-server Architecture: amd64 Version: 1:8.2p1-4ubuntu0.2 Multi-Arch: foreign Priority: optional Section: net Source: openssh Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian OpenSSH Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug ** Affects: openssh (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/1922212 Title: SSHD does not honor configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1398947] Re: Gnome Session Fallback uses "Open disk analyzer" as default action
I guess the problem is, then, Why does Disk Analyzer open instead of a file browser? That's certainly incorrect behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1398947 Title: Gnome Session Fallback uses "Open disk analyzer" as default action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1398947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920649] [NEW] ubuntu 20.04 LTS - aide crashes on initialization
Public bug reported: root@flynn:~# aideinit Running aide --init... Segmentation fault (core dumped) AIDE --init return code 139 [Sat Mar 20 18:21:48 2021] aide[6409]: segfault at 0 ip 7f903f98714b sp 7ffefb573de8 error 4 in libc-2.31.so[7f903f88c000+178000] [Sat Mar 20 18:21:48 2021] Code: 89 01 48 83 c8 ff c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 8b 05 25 ad 0c 00 48 83 ff 10 74 47 48 83 ff 1a 74 49 48 8b 40 60 <48> 8b 10 48 85 d2 75 12 eb 1b 0f 1f 00 48 8b 50 10 48 83 c0 10 48 root@flynn:~# uname -a Linux flynn 5.8.0-45-generic #51~20.04.1-Ubuntu SMP Tue Feb 23 13:46:31 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux root@flynn:~# root@flynn:~# cat /etc/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: aide 0.16.1-1build2 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 20 18:45:43 2021 InstallationDate: Installed on 2021-03-20 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: aide UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: aide (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/1920649 Title: ubuntu 20.04 LTS - aide crashes on initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1920649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844582] Re: "Invalid argument" when trying to scan
@PaulHazelden (tenuki57): I don't see "invalid argument" anywhere in the log. It looks to me that SANE did not find any scanners. Was your scanner plugged in? What does the following return: scanimage -L ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844582 Title: "Invalid argument" when trying to scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819543] Re: Does not exit correctly, have to "kill -9
Thank you very much everyone. I have several senior citizens on Linux Mint and they really needed VLC to exit correctly. They don't do the command line so they can't fix it themselves. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819543 Title: Does not exit correctly, have to "kill -9 To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/1819543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844582] Re: "Invalid argument" when trying to scan
What happens if you try the following from the command line: scanimage -x 210 --mode=Color --resolution=300 --batch ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844582 Title: "Invalid argument" when trying to scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905519] Re: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using someth
apt update then apt upgrade fixed the problem for me about four days ago. Thank you for fixing this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905519 Title: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905519] Re: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using someth
I made a duplicate bug report. The reply to me to post comments here in this bug report instead. The specs for my bug report is here: https://bugs.launchpad.net/bugs/1912816 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905519 Title: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912816] Re: Object St.Bin (0x558f64771240), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using someth
System:Host: BDXR-2ML Kernel: 5.10.4-051004-generic x86_64 bits: 64 Desktop: GNOME 3.38.1 Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Laptop System: Dell product: G5 5505 v: 1.5.0 serial: # Mobo: Dell model: 0YHTJ7 v: A00 serial: UEFI: Dell v: 1.5.0 date: 10/27/2020 Battery: ID-1: BAT0 charge: 51.0 Wh condition: 51.0/51.0 Wh (100%) CPU: Info: 8-Core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64 type: MT MCP L2 cache: 4096 KiB Speed: 1863 MHz min/max: 1400/2900 MHz Core speeds (MHz): 1: 1397 2: 1397 3: 1397 4: 1462 5: 1405 6: 1397 7: 1558 8: 1402 9: 1303 10: 1515 11: 1659 12: 2488 13: 1488 14: 1588 15: 1813 16: 1397 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Device-2: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel Display: server: X.Org 1.20.9 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~144Hz OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.10.4-051004-generic LLVM 10.0.0) v: 4.6 Mesa 20.0.5 Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel Device-3: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: snd_rn_pci_acp3x Device-4: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel Sound Server: ALSA v: k5.10.4-051004-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: enp5s0 state: down mac: ### Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi IF: wlp6s0 state: up mac: # IF-ID-1: virbr0 state: down mac: ## IF-ID-2: virbr0-nic state: down mac: ### Drives:Local Storage: total: 5.01 TiB used: 766.08 GiB (14.9%) ID-1: /dev/nvme0n1 vendor: SK Hynix model: BC511 NVMe 512GB size: 476.94 GiB ID-2: /dev/sda type: USB vendor: Western Digital model: WD easystore 2647 size: 4.55 TiB Partition: ID-1: / size: 466.30 GiB used: 188.75 GiB (40.5%) fs: ext4 dev: /dev/dm-1 ID-2: /boot size: 704.5 MiB used: 331.5 MiB (47.1%) fs: ext4 dev: /dev/nvme0n1p2 Swap: ID-1: swap-1 type: partition size: 980.0 MiB used: 0 KiB (0.0%) dev: /dev/dm-2 Sensors: System Temperatures: cpu: 56.5 C mobo: N/A Fan Speeds (RPM): N/A GPU: device: amdgpu temp: 50.0 C device: amdgpu temp: 53.0 C fan: 65535 Info: Processes: 417 Uptime: 33m Memory: 30.79 GiB used: 2.96 GiB (9.6%) Shell: Bash inxi: 3.1.07 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912816 Title: Object St.Bin (0x558f64771240), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912816] Re: Object St.Bin (0x558f64771240), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using someth
I have a Dell G5 15 SE (Gaming Laptop). The Laptop is so new that I can only install Ubuntu with the current config: Kernel 5.10 (has the AMD Radeon GPU drivers). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912816 Title: Object St.Bin (0x558f64771240), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912816] [NEW] Object St.Bin (0x558f64771240), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using some
Public bug reported: Journalctl -f repeately shows every 1 to 2 seconds: Object St.Bin (0x558f64771240), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Before that it shows: Jan 22 11:18:30 BDXR-2ML gnome-shell[2931]: == Stack trace for context 0x558f639f9270 == Jan 22 11:18:30 BDXR-2ML gnome-shell[2931]: #0 7ffc767f5f00 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1f3aba6af420 @ 208) Jan 22 11:18:30 BDXR-2ML gnome-shell[2931]: == Stack trace for context 0x558f639f9270 == Jan 22 11:18:30 BDXR-2ML gnome-shell[2931]: #0 7ffc767f5f00 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1f3aba6af420 @ 208) Jan 22 11:18:30 BDXR-2ML gnome-shell[2931]: Object St.Bin (0x558f64771240), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jan 22 11:18:30 BDXR-2ML gnome-shell[2931]: Object St.Bin (0x558f6751a480), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 Uname: Linux 5.10.4-051004-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 22 11:29:57 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2020-12-24 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-12-24 (28 days ago) ** Affects: gnome-shell (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/1912816 Title: Object St.Bin (0x558f64771240), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809206] Re: Amd ACPI Error
I'm still seeing this issue on Focal. The rub is, this is a new machine - a Dell 8930 with fully updated firmware (https://www.amazon.com/gp/product/B078N85NCR). Here's part of dmesg: ... [ 1217.951042] ACPI: Waking up from system sleep state S3 [ 1219.092307] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [DRQL] at bit offset/length 136/8 exceeds size of target Buffer (128 bits) (20190816/dsopcode-198) [ 1219.092311] No Local Variables are initialized for Method [DSRS] [ 1219.092312] Initialized Arguments for Method [DSRS]: (2 arguments defined for method invocation) [ 1219.092313] Arg0: de355a44Buffer(16) 47 01 F8 03 FF 03 00 08 [ 1219.092316] Arg1: 27af9512Integer [ 1219.092318] ACPI Error: Aborting method \_SB.PCI0.LPCB.SIO1.DSRS due to previous error (AE_AML_BUFFER_LIMIT) (20190816/psparse-529) [ 1219.092322] ACPI Error: Aborting method \_SB.PCI0.LPCB.UAR1._SRS due to previous error (AE_AML_BUFFER_LIMIT) (20190816/psparse-529) [ 1219.092325] serial 00:02: activation failed [ 1219.092328] PM: dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -5 [ 1219.092329] PM: Device 00:02 failed to resume: error -5 [ 1219.094879] sd 1:0:0:0: [sda] Starting disk ... Attached is acpidump. Sorry about the late reply. I forgot you asked for acpidump. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809206 Title: Amd ACPI Error To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1809206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809206] Re: Amd ACPI Error
Output of acpidump. ** Attachment added: "Output of acpidump." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809206/+attachment/5455179/+files/acpidump.txt.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809206 Title: Amd ACPI Error To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1809206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910567] [NEW] Wget cannot download from ftp.gnu.org using Let's Encrypt R3 CA certificate
Public bug reported:
I'm working on Ubuntu 18.05, x86_64, fully patched. The system has been
through both apt-get upgrade and dist-upgrade. The system provides Wget
1.19.4
The program below fails to download from ftp.gnu.org using Let's Encrypt
R3 CA certificate. Let's Encrypt R3 is the issuer for ftp.gnu.org. It is
about the best trust anchor you can choose (sans pinning the host's
public key).
If I use Daniel Stenberg's cacert.pem
(https://curl.haxx.se/docs/caextract.html), then the download succeeds.
I'm not a fan of using the CA Zoo when I know the Issuing CA in advance.
There's no reason to trust every PKI in the world.
If I use a newer version of Wget built with an OpenSSL backend, then the
download succeeds. For example, Wget 1.20.3 and Wget 1.21 with an
OpenSSL backend work fine.
-
$ ./wget-test.sh
Failed to download Ncurses
# Hmm... Add --debug to Wget command
$ ./wget-test.sh
Setting --quiet (quiet) to 1
Setting --quiet (quiet) to 1
Setting --output-document (outputdocument) to ncurses-6.1.tar.gz
Setting --output-document (outputdocument) to ncurses-6.1.tar.gz
Setting --ca-certificate (cacertificate) to lets-encrypt-roots.pem
Setting --ca-certificate (cacertificate) to lets-encrypt-roots.pem
DEBUG output created by Wget 1.19.4 on linux-gnu.
Reading HSTS entries from /home/jwalton/.wget-hsts
URI encoding = ‘UTF-8’
Caching ftp.gnu.org => 209.51.188.20 2001:470:142:3::b
Created socket 4.
Releasing 0x5590bdacd590 (new refcount 1).
Initiating SSL handshake.
Handshake successful; connected socket 4 to SSL handle 0x5590bdad1fd0
certificate:
subject: CN=ftp.gnu.org
issuer: CN=R3,O=Let's Encrypt,C=US
Closed 4/SSL 0x5590bdad1fd0
Failed to download Ncurses
$ cat ./wget-test.sh
#!/usr/bin/env bash
{
# This is the new "Let's Encrypt Authority R3"
# https://letsencrypt.org/certificates/
echo "-BEGIN CERTIFICATE-
MIIFFjCCAv6gAwIBAgIRAJErCErPDBinU/bWLiWnX1owDQYJKoZIhvcNAQELBQAw
TzELMAkGA1UEBhMCVVMxKTAnBgNVBAoTIEludGVybmV0IFNlY3VyaXR5IFJlc2Vh
cmNoIEdyb3VwMRUwEwYDVQQDEwxJU1JHIFJvb3QgWDEwHhcNMjAwOTA0MDAwMDAw
WhcNMjUwOTE1MTYwMDAwWjAyMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNTGV0J3Mg
RW5jcnlwdDELMAkGA1UEAxMCUjMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQC7AhUozPaglNMPEuyNVZLD+ILxmaZ6QoinXSaqtSu5xUyxr45r+XXIo9cP
R5QUVTVXjJ6oojkZ9YI8QqlObvU7wy7bjcCwXPNZOOftz2nwWgsbvsCUJCWH+jdx
sxPnHKzhm+/b5DtFUkWWqcFTzjTIUu61ru2P3mBw4qVUq7ZtDpelQDRrK9O8Zutm
NHz6a4uPVymZ+DAXXbpyb/uBxa3Shlg9F8fnCbvxK/eG3MHacV3URuPMrSXBiLxg
Z3Vms/EY96Jc5lP/Ooi2R6X/ExjqmAl3P51T+c8B5fWmcBcUr2Ok/5mzk53cU6cG
/kiFHaFpriV1uxPMUgP17VGhi9sVAgMBAAGjggEIMIIBBDAOBgNVHQ8BAf8EBAMC
AYYwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMBMBIGA1UdEwEB/wQIMAYB
Af8CAQAwHQYDVR0OBBYEFBQusxe3WFbLrlAJQOYfr52LFMLGMB8GA1UdIwQYMBaA
FHm0WeZ7tuXkAXOACIjIGlj26ZtuMDIGCCsGAQUFBwEBBCYwJDAiBggrBgEFBQcw
AoYWaHR0cDovL3gxLmkubGVuY3Iub3JnLzAnBgNVHR8EIDAeMBygGqAYhhZodHRw
Oi8veDEuYy5sZW5jci5vcmcvMCIGA1UdIAQbMBkwCAYGZ4EMAQIBMA0GCysGAQQB
gt8TAQEBMA0GCSqGSIb3DQEBCwUAA4ICAQCFyk5HPqP3hUSFvNVneLKYY611TR6W
PTNlclQtgaDqw+34IL9fzLdwALduO/ZelN7kIJ+m74uyA+eitRY8kc607TkC53wl
ikfmZW4/RvTZ8M6UK+5UzhK8jCdLuMGYL6KvzXGRSgi3yLgjewQtCPkIVz6D2QQz
CkcheAmCJ8MqyJu5zlzyZMjAvnnAT45tRAxekrsu94sQ4egdRCnbWSDtY7kh+BIm
lJNXoB1lBMEKIq4QDUOXoRgffuDghje1WrG9ML+Hbisq/yFOGwXD9RiX8F6sw6W4
avAuvDszue5L3sz85K+EC4Y/wFVDNvZo4TYXao6Z0f+lQKc0t8DQYzk1OXVu8rp2
yJMC6alLbBfODALZvYH7n7do1AZls4I9d1P4jnkDrQoxB3UqQ9hVl3LEKQ73xF1O
yK5GhDDX8oVfGKF5u+decIsH4YaTw7mP3GFxJSqv3+0lUFJoi5Lc5da149p90Ids
hCExroL1+7mryIkXPeFM5TgO9r0rvZaBFOvV2z0gp35Z0+L4WPlbuEjN/lxPFin+
HlUjr8gRsI3qfJOQFy/9rKIJR0Y/8Omwt/8oTWgy1mdeHmmjk7j1nYsvC9JSQ6Zv
MldlTTKB3zhThV1+XWYp6rjd5JW1zbVWEkLNxE7GJThEUG3szgBVGP7pSWTUTsqX
nLRbwHOoq7hHwg==
-END CERTIFICATE-"
# This is the original "Let's Encrypt Authority X3"
# https://letsencrypt.org/certificates/
echo "-BEGIN CERTIFICATE-
MIIEkjCCA3qgAwIBAgIQCgFBQgAAAVOFc2oLheynCDANBgkqhkiG9w0BAQsFADA/
MSQwIgYDVQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMT
DkRTVCBSb290IENBIFgzMB4XDTE2MDMxNzE2NDA0NloXDTIxMDMxNzE2NDA0Nlow
SjELMAkGA1UEBhMCVVMxFjAUBgNVBAoTDUxldCdzIEVuY3J5cHQxIzAhBgNVBAMT
GkxldCdzIEVuY3J5cHQgQXV0aG9yaXR5IFgzMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEAnNMM8FrlLke3cl03g7NoYzDq1zUmGSXhvb418XCSL7e4S0EF
q6meNQhY7LEqxGiHC6PjdeTm86dicbp5gWAf15Gan/PQeGdxyGkOlZHP/uaZ6WA8
SMx+yk13EiSdRxta67nsHjcAHJyse6cF6s5K671B5TaYucv9bTyWaN8jKkKQDIZ0
Z8h/pZq4UmEUEz9l6YKHy9v6Dlb2honzhT+Xhq+w3Brvaw2VFn3EK6BlspkENnWA
a6xK8xuQSXgvopZPKiAlKQTGdMDQMc2PMTiVFrqoM7hD8bEfwzB/onkxEz0tNvjj
/PIzark5McWvxI0NHWQWM6r6hCm21AvA2H3DkwIDAQABo4IBfTCCAXkwEgYDVR0T
AQH/BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwfwYIKwYBBQUHAQEEczBxMDIG
CCsGAQUFBzABhiZodHRwOi8vaXNyZy50cnVzdGlkLm9jc3AuaWRlbnRydXN0LmNv
bTA7BggrBgEFBQcwAoYvaHR0cDovL2FwcHMuaWRlbnRydXN0LmNvbS9yb290cy9k
c3Ryb290Y2F4My5wN2MwHwYDVR0jBBgwFoAUxKexpHsscfrb4UuQdf/EFWCFiRAw
VAYDVR0gBE0wSzAIBgZngQwBAgEwPwYLKwYBBAGC3xMBAQEwMDAuBggrBgEFBQcC
ARYiaHR0cDovL2Nwcy5yb290LXgxLmxldHNlbmNyeXB0Lm9yZzA8BgNVHR8ENTAz
MDGgL6AthitodHRwOi8vY3JsLmlkZW50cnVzdC5jb20vRFNUUk9PVENBWDNDUkwu
[Bug 1910475] Re: VLC does not open 2nd, 3rd, 4th, ... movie when double-clicking the movie
** Description changed: I have Linux Mint 20 (ulyana), x86_64, fully patched. The machine has - been through a upgrade and dist-upgrade. The machine has 3.0.9.2-1 - installed. Mint is an Ubuntu derivative, and apt-cache for thepackage + been through a upgrade and dist-upgrade. The machine has VLC 3.0.9.2-1 + installed. Mint is an Ubuntu derivative, and apt-cache for the package says to file bug reports here. VLC is the default media player. I copied two DVDs to my hard drive. The first movie is THE_PATRIOT.mov. The second movie is THE_NATURAL.mov. I double click THE_PATRIOT.mov the media player opens and plays the movie. Everything is OK. Next I close the player by clicking 'X' in the upper right hand corner of the window. Next, I double click THE_NATURAL.mov. The media player fails to open and play the movie. I'm not sure where the failure is, but there is no error displayed to me. I find if I perform a `ps -A | grep vlc` and then `kill -9 ` the VLC player will start working again. I also find if I choose Media->Quit the media player does exit, and the VLC player will start working again. I noticed there's a Tools->Preference setting about minimizing the player in Interface->Main Interface->Qt. Unchecking "Systray icon" does not help. The same behavior is present. The bigger problem I have is, the machine is for my parents. They are getting off Windows. They don't know how to use the Linux command line. They are barely qualified to use Linux, and that's why they are getting a Linux-on-Training-Wheels via Linux Mint. The ps/grep/kill chain is too complicated for them. And I probably won't be able to break their habit of clicking "X" to close an app. They spent years learning it, and they probably won't be able to unlearn it for this one program. -- It would be incredibly helpful for beginners if clicking the "X" button actually closed the media player. That way, the media player is ready for the next movie. If you can't fix the "X" button, then please consider fixing the communication problem that's getting in the way of opening the 2nd, 3rd, 4th, ... movie when a user double clicks on a movie. Finally, the issue may be present when clicking on songs in the Music folder. I did not test it. - Upstream bug at https://trac.videolan.org/vlc/ticket/25368 - $ apt-cache show vlc Package: vlc Architecture: amd64 Version: 3.0.9.2-1 Priority: optional Section: universe/graphics Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian Multimedia Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 224 Provides: mp3-decoder Depends: vlc-bin (= 3.0.9.2-1), vlc-plugin-base (= 3.0.9.2-1), vlc-plugin-qt (= 3.0.9.2-1), vlc-plugin-video-output (= 3.0.9.2-1) Recommends: vlc-l10n (= 3.0.9.2-1), vlc-plugin-notify (= 3.0.9.2-1), vlc-plugin-samba (= 3.0.9.2-1), vlc-plugin-skins2 (= 3.0.9.2-1), vlc-plugin-video-splitter (= 3.0.9.2-1), vlc-plugin-visualization (= 3.0.9.2-1) Filename: pool/universe/v/vlc/vlc_3.0.9.2-1_amd64.deb Size: 34000 MD5sum: 7468fd0721eefe6ad4f1c379e06426a4 SHA1: 9627ef2f5994cb6fb043ab2412a8031241b87146 SHA256: e85843fa69aed492ece8190f3aafee43a4e1487bc05e6603779e62507a7a737f Homepage: https://www.videolan.org/vlc/ Description-en: multimedia player and streamer - VLC is the VideoLAN project's media player. It plays MPEG, MPEG-2, MPEG-4, - DivX, MOV, WMV, QuickTime, WebM, FLAC, MP3, Ogg/Vorbis files, DVDs, VCDs, - podcasts, and multimedia streams from various network sources. - . - VLC can also be used as a streaming server that duplicates the stream it - reads and multicasts them through the network to other clients, or serves - them through HTTP. - . - VLC has support for on-the-fly transcoding of audio and video formats, either - for broadcasting purposes or for movie format transformations. Support for - most output methods is provided by this package, but features can be added by - installing additional plugins: - * vlc-plugin-access-extra - * vlc-plugin-fluidsynth - * vlc-plugin-jack - * vlc-plugin-notify - * vlc-plugin-samba - * vlc-plugin-skins2 - * vlc-plugin-svg - * vlc-plugin-video-splitter - * vlc-plugin-visualization + VLC is the VideoLAN project's media player. It plays MPEG, MPEG-2, MPEG-4, + DivX, MOV, WMV, QuickTime, WebM, FLAC, MP3, Ogg/Vorbis files, DVDs, VCDs, + podcasts, and multimedia streams from various network sources. + . + VLC can also be used as a streaming server that duplicates the stream it + reads and multicasts them through the network to other clients, or serves + them through HTTP. + . + VLC has support for on-the-fly transcoding of audio and video formats, either + for broadcasting purposes or for movie format transformations. Support for + most output methods is provided by this package, but features can be added by +
[Bug 1910475] [NEW] VLC does not open 2nd, 3rd, 4th, ... movie when double-clicking the movie
Public bug reported: I have Linux Mint 20 (ulyana), x86_64, fully patched. The machine has been through a upgrade and dist-upgrade. The machine has 3.0.9.2-1 installed. Mint is an Ubuntu derivative, and apt-cache for thepackage says to file bug reports here. VLC is the default media player. I copied two DVDs to my hard drive. The first movie is THE_PATRIOT.mov. The second movie is THE_NATURAL.mov. I double click THE_PATRIOT.mov the media player opens and plays the movie. Everything is OK. Next I close the player by clicking 'X' in the upper right hand corner of the window. Next, I double click THE_NATURAL.mov. The media player fails to open and play the movie. I'm not sure where the failure is, but there is no error displayed to me. I find if I perform a `ps -A | grep vlc` and then `kill -9 ` the VLC player will start working again. I also find if I choose Media->Quit the media player does exit, and the VLC player will start working again. I noticed there's a Tools->Preference setting about minimizing the player in Interface->Main Interface->Qt. Unchecking "Systray icon" does not help. The same behavior is present. The bigger problem I have is, the machine is for my parents. They are getting off Windows. They don't know how to use the Linux command line. They are barely qualified to use Linux, and that's why they are getting a Linux-on-Training-Wheels via Linux Mint. The ps/grep/kill chain is too complicated for them. And I probably won't be able to break their habit of clicking "X" to close an app. They spent years learning it, and they probably won't be able to unlearn it for this one program. -- It would be incredibly helpful for beginners if clicking the "X" button actually closed the media player. That way, the media player is ready for the next movie. If you can't fix the "X" button, then please consider fixing the communication problem that's getting in the way of opening the 2nd, 3rd, 4th, ... movie when a user double clicks on a movie. Finally, the issue may be present when clicking on songs in the Music folder. I did not test it. - Upstream bug at https://trac.videolan.org/vlc/ticket/25368 - $ apt-cache show vlc Package: vlc Architecture: amd64 Version: 3.0.9.2-1 Priority: optional Section: universe/graphics Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian Multimedia Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 224 Provides: mp3-decoder Depends: vlc-bin (= 3.0.9.2-1), vlc-plugin-base (= 3.0.9.2-1), vlc-plugin-qt (= 3.0.9.2-1), vlc-plugin-video-output (= 3.0.9.2-1) Recommends: vlc-l10n (= 3.0.9.2-1), vlc-plugin-notify (= 3.0.9.2-1), vlc-plugin-samba (= 3.0.9.2-1), vlc-plugin-skins2 (= 3.0.9.2-1), vlc-plugin-video-splitter (= 3.0.9.2-1), vlc-plugin-visualization (= 3.0.9.2-1) Filename: pool/universe/v/vlc/vlc_3.0.9.2-1_amd64.deb Size: 34000 MD5sum: 7468fd0721eefe6ad4f1c379e06426a4 SHA1: 9627ef2f5994cb6fb043ab2412a8031241b87146 SHA256: e85843fa69aed492ece8190f3aafee43a4e1487bc05e6603779e62507a7a737f Homepage: https://www.videolan.org/vlc/ Description-en: multimedia player and streamer VLC is the VideoLAN project's media player. It plays MPEG, MPEG-2, MPEG-4, DivX, MOV, WMV, QuickTime, WebM, FLAC, MP3, Ogg/Vorbis files, DVDs, VCDs, podcasts, and multimedia streams from various network sources. . VLC can also be used as a streaming server that duplicates the stream it reads and multicasts them through the network to other clients, or serves them through HTTP. . VLC has support for on-the-fly transcoding of audio and video formats, either for broadcasting purposes or for movie format transformations. Support for most output methods is provided by this package, but features can be added by installing additional plugins: * vlc-plugin-access-extra * vlc-plugin-fluidsynth * vlc-plugin-jack * vlc-plugin-notify * vlc-plugin-samba * vlc-plugin-skins2 * vlc-plugin-svg * vlc-plugin-video-splitter * vlc-plugin-visualization Description-md5: d96da6b991aa50928533b16fb11b3136 Task: kubuntu-desktop, kubuntu-full, lubuntu-desktop, ubuntustudio-video ** Affects: vlc (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/1910475 Title: VLC does not open 2nd, 3rd, 4th, ... movie when double-clicking the movie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1910475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904907] Re: Bad arg length for Socket::inet_ntoa, length is 16, should be 4 at /usr/share/perl5/HTTP/Daemon.pm line 51
Ping... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904907 Title: Bad arg length for Socket::inet_ntoa, length is 16, should be 4 at /usr/share/perl5/HTTP/Daemon.pm line 51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhttp-daemon-perl/+bug/1904907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892242] Re: Curtin doesn't handle type:mount entries without 'path' element
So, where have clients (especially MaaS clients) been informed of this change to Curtin? I can imagine a few would want to add the Curtin PPA to their list of repos... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892242 Title: Curtin doesn't handle type:mount entries without 'path' element To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1892242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
