[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Problem has NOT been fixed for my setup: - Kernel: 5.4.0-65-generic - OS: Kubuntu 20.04.1 LTS - Machine: Dell Latitude 5501 - Headset: Haylou GT1 Plus -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Autopkgtest regression report (software-properties/0.98.9.4)
All autopkgtests for the newly accepted software-properties (0.98.9.4) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
livecd-rootfs/2.664.15 (s390x)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#software-properties
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in software-properties package in Ubuntu:
Triaged
Status in software-properties source package in Eoan:
Won't Fix
Status in software-properties source package in Focal:
Fix Committed
Status in software-properties source package in Groovy:
Fix Committed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
[Impact]
* If selected mirrors are not reachable or have
expired GPG keys, software-properties-gtk
would crash
[Test Case]
* Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors
* Find your locale in this file and add a non-existent URL
to the list
* Run software-properties-gtk and choose your newly added
URL from the "Download From" dropdown menu
* Press "Close" in the bottom right, and when
prompted press "Reload"
* You should be presented with an error window rather than
the program crashing
[Where problems could occur]
* The new error window binds to the parent window. If the
parent window has gotten into a bad state this could
cause problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914467] Re: Problem with fractional scaling
*** This bug is a duplicate of bug 1873052 *** https://bugs.launchpad.net/bugs/1873052 By the way, a different scaling factor on the login screen is expected. Because that runs as a different user and so doesn't use the same display settings you chose for yourself. If you would like the login screen to use your own preferred scaling factor then you should be able to copy your monitor config to the login screen with something like: sudo cp ~/.config/monitors.xml ~gdm/.config/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1914467 Title: Problem with fractional scaling Status in xorg package in Ubuntu: New Bug description: Hello, I would like to report a problem with fractional scaling. I have set it at 125%. I'm using a Huawei Matebook 13inch 2020 AMD (Ryzen 5 3500u) with Radeon Vega 8 Graphics. After starting the laptop, at the logon screen, the scaling seems to be at 200% but after I logon and go into my user session it turns to a scaling of 125%. At that moment I see 2 mouse pointers, one scaled 200% and one scaled at 125%. The mouse pointer which is scaled at 200% remains in its last position before the login process. It stays on top of any app or window that you open which is a bit annoying. The second mouse pointer (scaled at 125%) behaves normally. I tried to take a screenshot, but on a screenshot neither mouse pointer appear so I took a picture which I've added to this bug report. This bug is not specific to this version of Ubuntu, I can reproduce the problem in version 20.10. I haven't tried this in version 20.04. PopOS 20.10 does not exhibit this problem. It's a pity that Gnome has not yet made a better implementation of fractional scaling, high density display have been around for a while now. One would expect if one sets the scaling at 125%, that this would be applied system wide (sorry for the rant). Best regards, Eric P.S. : Sorry if this bug has been reported in a wrong category. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 3 20:49:00 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. Picasso [19e5:3e14] InstallationDate: Installed on 2021-02-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) MachineType: HUAWEI HN-WX9X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=b98eae12-e501-4bfe-88e5-b713ae9b9843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2020 dmi.bios.release: 1.13 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.13 dmi.board.asset.tag: N/A dmi.board.name: HN-WX9X-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnHUAWEI:bvr1.13:bd09/04/2020:br1.13:efr1.13:svnHUAWEI:pnHN-WX9X:pvrM1130:rvnHUAWEI:rnHN-WX9X-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130: dmi.product.family: MateBook dmi.product.name: HN-WX9X dmi.product.sku: C100 dmi.product.version: M1130 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1914467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914467] Re: Problem with fractional scaling
*** This bug is a duplicate of bug 1873052 *** https://bugs.launchpad.net/bugs/1873052 Thanks for the bug report. The two cursors problem (which mostly affects amdgpu) is bug 1873052. There is also bug 1870736 which sounds related but that one seems to be for the Nvidia driver only. Since you're using amdgpu we should probably keep this bug separate(?) ** This bug has been marked a duplicate of bug 1873052 Showing two cursors after login -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1914467 Title: Problem with fractional scaling Status in xorg package in Ubuntu: New Bug description: Hello, I would like to report a problem with fractional scaling. I have set it at 125%. I'm using a Huawei Matebook 13inch 2020 AMD (Ryzen 5 3500u) with Radeon Vega 8 Graphics. After starting the laptop, at the logon screen, the scaling seems to be at 200% but after I logon and go into my user session it turns to a scaling of 125%. At that moment I see 2 mouse pointers, one scaled 200% and one scaled at 125%. The mouse pointer which is scaled at 200% remains in its last position before the login process. It stays on top of any app or window that you open which is a bit annoying. The second mouse pointer (scaled at 125%) behaves normally. I tried to take a screenshot, but on a screenshot neither mouse pointer appear so I took a picture which I've added to this bug report. This bug is not specific to this version of Ubuntu, I can reproduce the problem in version 20.10. I haven't tried this in version 20.04. PopOS 20.10 does not exhibit this problem. It's a pity that Gnome has not yet made a better implementation of fractional scaling, high density display have been around for a while now. One would expect if one sets the scaling at 125%, that this would be applied system wide (sorry for the rant). Best regards, Eric P.S. : Sorry if this bug has been reported in a wrong category. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 3 20:49:00 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. Picasso [19e5:3e14] InstallationDate: Installed on 2021-02-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) MachineType: HUAWEI HN-WX9X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=b98eae12-e501-4bfe-88e5-b713ae9b9843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2020 dmi.bios.release: 1.13 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.13 dmi.board.asset.tag: N/A dmi.board.name: HN-WX9X-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnHUAWEI:bvr1.13:bd09/04/2020:br1.13:efr1.13:svnHUAWEI:pnHN-WX9X:pvrM1130:rvnHUAWEI:rnHN-WX9X-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130: dmi.product.family: MateBook dmi.product.name: HN-WX9X dmi.product.sku: C100 dmi.product.version: M1130 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1914467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1910928] Re: Bluetooth (Intel AX1650i) won't go live after suspend Lenovo Thinkbook 14 IIL
** Summary changed: - Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL + Bluetooth (Intel AX1650i) won't go live after suspend Lenovo Thinkbook 14 IIL ** Summary changed: - Bluetooth (Intel AX1650i) won't go live after suspend Lenovo Thinkbook 14 IIL + Bluetooth (Intel AX201 / AX1650i) won't go live after suspend Lenovo Thinkbook 14 IIL ** Package changed: bluez (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1910928 Title: Bluetooth (Intel AX201 / AX1650i) won't go live after suspend Lenovo Thinkbook 14 IIL Status in linux package in Ubuntu: Confirmed Bug description: After I have installed the Ubuntu - I have noticed, that Bluetooth won't go turn on after Suspend. The only way to get it working - reboot the system. WiFi Adapter - AX201 I have tried the latest kernel (5.11.rc2) - no luck. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20SL NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: bluez 5.55-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN22WW dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL: dmi.product.family: Thinkbook 14-IIL dmi.product.name: 20SL dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL dmi.product.version: Lenovo ThinkBook 14-IIL dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:26:49:C4:B9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:19913 acl:0 sco:0 events:3169 errors:0 TX bytes:770617 acl:0 sco:0 commands:3167 errors:0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20SL NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: bluez 5.55-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN22WW dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL: dmi.product.family: Thinkbook 14-IIL dmi.product.name: 20SL dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL dmi.product.version: Lenovo ThinkBook 14-IIL dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914481] Re: stop assuming curl's data is null-terminated
This is the result of the following merge: https://bazaar.launchpad.net/~daisy-pluckers/whoopsie/trunk/revision/707 So affects Ubuntu 20.04 LTS and later releases. ** Also affects: whoopsie (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: whoopsie (Ubuntu Hirsute) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: whoopsie (Ubuntu Hirsute) Status: New => Triaged ** Changed in: whoopsie (Ubuntu Hirsute) Importance: Undecided => Medium ** Tags added: fr-1101 ** Summary changed: - stop assuming curl's data is null-terminated + use the size of the data when determing the server response -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1914481 Title: use the size of the data when determing the server response Status in whoopsie package in Ubuntu: Triaged Status in whoopsie source package in Focal: New Status in whoopsie source package in Groovy: New Status in whoopsie source package in Hirsute: Triaged Bug description: whoopsie's server_response code is using "g_string_append" instead of "g_string_append_len" which has the knock on effect of sending too much data to its "handle_response". This ends up being a problem if the daisy servers are running on Ubuntu 18.04 instead of Ubuntu 16.04. Here's an example when using whoopsie on groovy to send a crash to a bionic daisy server: [15:35:30] Sent; server replied with: No error [15:35:30] Response code: 200 [15:35:30] Initial response data is: 2bbb776e-64e6-11eb-a8d6-00163eddedf4 OOPSID 0 [15:35:30] Got command: OOPSID We can see a fair number of extra characters (\n0\n\n) after the OOSID command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1914481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914481] [NEW] use the size of the data when determing the server response
Public bug reported: whoopsie's server_response code is using "g_string_append" instead of "g_string_append_len" which has the knock on effect of sending too much data to its "handle_response". This ends up being a problem if the daisy servers are running on Ubuntu 18.04 instead of Ubuntu 16.04. Here's an example when using whoopsie on groovy to send a crash to a bionic daisy server: [15:35:30] Sent; server replied with: No error [15:35:30] Response code: 200 [15:35:30] Initial response data is: 2bbb776e-64e6-11eb-a8d6-00163eddedf4 OOPSID 0 [15:35:30] Got command: OOPSID We can see a fair number of extra characters (\n0\n\n) after the OOSID command. ** Affects: whoopsie (Ubuntu) Importance: Medium Assignee: Brian Murray (brian-murray) Status: Triaged ** Affects: whoopsie (Ubuntu Focal) Importance: Undecided Status: New ** Affects: whoopsie (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: whoopsie (Ubuntu Hirsute) Importance: Medium Assignee: Brian Murray (brian-murray) Status: Triaged ** Tags: fr-1101 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1914481 Title: use the size of the data when determing the server response Status in whoopsie package in Ubuntu: Triaged Status in whoopsie source package in Focal: New Status in whoopsie source package in Groovy: New Status in whoopsie source package in Hirsute: Triaged Bug description: whoopsie's server_response code is using "g_string_append" instead of "g_string_append_len" which has the knock on effect of sending too much data to its "handle_response". This ends up being a problem if the daisy servers are running on Ubuntu 18.04 instead of Ubuntu 16.04. Here's an example when using whoopsie on groovy to send a crash to a bionic daisy server: [15:35:30] Sent; server replied with: No error [15:35:30] Response code: 200 [15:35:30] Initial response data is: 2bbb776e-64e6-11eb-a8d6-00163eddedf4 OOPSID 0 [15:35:30] Got command: OOPSID We can see a fair number of extra characters (\n0\n\n) after the OOSID command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1914481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+attachment/5459534/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1905166 Title: systemd-shutdown cannot detach DM Status in systemd package in Ubuntu: Incomplete Bug description: when powering down the system systemd cannot unmount / systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy systemd-shutdown[1]: Failed to finalize DM devices, ignoring reboot: Power down as a result at each startup the filesystem is checked: Press Ctrl+C to cancel all filesystem checks in progress If systemd cannot unmount / that might not be a problem but it should be less noisy and not result in a filesystem check after each reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 11:40:05 2020 MachineType: Dell Inc. Latitude 7410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0M5G57 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd10/11/2020:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn0M5G57:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7410 dmi.product.sku: 09CD dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM
** Attachment added: "short.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+attachment/5459536/+files/short.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1905166 Title: systemd-shutdown cannot detach DM Status in systemd package in Ubuntu: Incomplete Bug description: when powering down the system systemd cannot unmount / systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy systemd-shutdown[1]: Failed to finalize DM devices, ignoring reboot: Power down as a result at each startup the filesystem is checked: Press Ctrl+C to cancel all filesystem checks in progress If systemd cannot unmount / that might not be a problem but it should be less noisy and not result in a filesystem check after each reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 11:40:05 2020 MachineType: Dell Inc. Latitude 7410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0M5G57 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd10/11/2020:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn0M5G57:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7410 dmi.product.sku: 09CD dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM
** Attachment added: "long.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+attachment/5459535/+files/long.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1905166 Title: systemd-shutdown cannot detach DM Status in systemd package in Ubuntu: Incomplete Bug description: when powering down the system systemd cannot unmount / systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy systemd-shutdown[1]: Failed to finalize DM devices, ignoring reboot: Power down as a result at each startup the filesystem is checked: Press Ctrl+C to cancel all filesystem checks in progress If systemd cannot unmount / that might not be a problem but it should be less noisy and not result in a filesystem check after each reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 11:40:05 2020 MachineType: Dell Inc. Latitude 7410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0M5G57 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd10/11/2020:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn0M5G57:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7410 dmi.product.sku: 09CD dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM
** Attachment added: "2.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+attachment/5459533/+files/2.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1905166 Title: systemd-shutdown cannot detach DM Status in systemd package in Ubuntu: Incomplete Bug description: when powering down the system systemd cannot unmount / systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy systemd-shutdown[1]: Failed to finalize DM devices, ignoring reboot: Power down as a result at each startup the filesystem is checked: Press Ctrl+C to cancel all filesystem checks in progress If systemd cannot unmount / that might not be a problem but it should be less noisy and not result in a filesystem check after each reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 11:40:05 2020 MachineType: Dell Inc. Latitude 7410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0M5G57 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd10/11/2020:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn0M5G57:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7410 dmi.product.sku: 09CD dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM
The message: systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy systemd-shutdown[1]: Failed to finalize DM devices, ignoring is not in the logs, idk why, here are some more logs, the image shows the message and the time before. I attached also a longer log file and kern log, if it helps..? ** Attachment added: "1.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+attachment/5459532/+files/1.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1905166 Title: systemd-shutdown cannot detach DM Status in systemd package in Ubuntu: Incomplete Bug description: when powering down the system systemd cannot unmount / systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy systemd-shutdown[1]: Failed to finalize DM devices, ignoring reboot: Power down as a result at each startup the filesystem is checked: Press Ctrl+C to cancel all filesystem checks in progress If systemd cannot unmount / that might not be a problem but it should be less noisy and not result in a filesystem check after each reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 11:40:05 2020 MachineType: Dell Inc. Latitude 7410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0M5G57 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd10/11/2020:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn0M5G57:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7410 dmi.product.sku: 09CD dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected,
Accepted software-properties into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.98.9.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in software-properties package in Ubuntu:
Triaged
Status in software-properties source package in Eoan:
Won't Fix
Status in software-properties source package in Focal:
Fix Committed
Status in software-properties source package in Groovy:
Fix Committed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
[Impact]
* If selected mirrors are not reachable or have
expired GPG keys, software-properties-gtk
would crash
[Test Case]
* Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors
* Find your locale in this file and add a non-existent URL
to the list
* Run software-properties-gtk and choose your newly added
URL from the "Download From" dropdown menu
* Press "Close" in the bottom right, and when
prompted press "Reload"
* You should be presented with an error window rather than
the program crashing
[Where problems could occur]
* The new error window binds to the parent window. If the
parent window has gotten into a bad state this could
cause problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
Hello errors.ubuntu.com, or anyone else affected,
Accepted software-properties into groovy-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.99.3.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: software-properties (Ubuntu Groovy)
Status: Confirmed => Fix Committed
** Tags added: verification-needed verification-needed-groovy
** Changed in: software-properties (Ubuntu Focal)
Status: Confirmed => Fix Committed
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in software-properties package in Ubuntu:
Triaged
Status in software-properties source package in Eoan:
Won't Fix
Status in software-properties source package in Focal:
Fix Committed
Status in software-properties source package in Groovy:
Fix Committed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
[Impact]
* If selected mirrors are not reachable or have
expired GPG keys, software-properties-gtk
would crash
[Test Case]
* Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors
* Find your locale in this file and add a non-existent URL
to the list
* Run software-properties-gtk and choose your newly added
URL from the "Download From" dropdown menu
* Press "Close" in the bottom right, and when
prompted press "Reload"
* You should be presented with an error window rather than
the program crashing
[Where problems could occur]
* The new error window binds to the parent window. If the
parent window has gotten into a bad state this could
cause problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829401/+subscriptions
--
[Touch-packages] [Bug 1914478] Re: package ca-certificates 20210119~20.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1914478 Title: package ca-certificates 20210119~20.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: I played around with certificates in docker containers earlier this day, which should not have affected host configuration. Now I was presented an update, which I started, resulting in a crash. Description: Ubuntu 20.04.2 LTS Release: 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ca-certificates 20210119~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 3 23:23:54 2021 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-11-02 (2285 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: ca-certificates Title: package ca-certificates 20210119~20.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-08-02 (185 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1914478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914478] [NEW] package ca-certificates 20210119~20.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit statu
Public bug reported: I played around with certificates in docker containers earlier this day, which should not have affected host configuration. Now I was presented an update, which I started, resulting in a crash. Description:Ubuntu 20.04.2 LTS Release:20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ca-certificates 20210119~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 3 23:23:54 2021 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-11-02 (2285 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: ca-certificates Title: package ca-certificates 20210119~20.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-08-02 (185 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1914478 Title: package ca-certificates 20210119~20.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: I played around with certificates in docker containers earlier this day, which should not have affected host configuration. Now I was presented an update, which I started, resulting in a crash. Description: Ubuntu 20.04.2 LTS Release: 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ca-certificates 20210119~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 3 23:23:54 2021 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-11-02 (2285 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: ca-certificates Title: package ca-certificates 20210119~20.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-08-02 (185 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1914478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
** Package changed: packagekit (Ubuntu) => software-properties (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in software-properties package in Ubuntu:
Triaged
Status in software-properties source package in Eoan:
Won't Fix
Status in software-properties source package in Focal:
Confirmed
Status in software-properties source package in Groovy:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
[Impact]
* If selected mirrors are not reachable or have
expired GPG keys, software-properties-gtk
would crash
[Test Case]
* Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors
* Find your locale in this file and add a non-existent URL
to the list
* Run software-properties-gtk and choose your newly added
URL from the "Download From" dropdown menu
* Press "Close" in the bottom right, and when
prompted press "Reload"
* You should be presented with an error window rather than
the program crashing
[Where problems could occur]
* The new error window binds to the parent window. If the
parent window has gotten into a bad state this could
cause problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: software-properties (Ubuntu Groovy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in software-properties package in Ubuntu:
Triaged
Status in software-properties source package in Eoan:
Won't Fix
Status in software-properties source package in Focal:
Confirmed
Status in software-properties source package in Groovy:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
[Impact]
* If selected mirrors are not reachable or have
expired GPG keys, software-properties-gtk
would crash
[Test Case]
* Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors
* Find your locale in this file and add a non-existent URL
to the list
* Run software-properties-gtk and choose your newly added
URL from the "Download From" dropdown menu
* Press "Close" in the bottom right, and when
prompted press "Reload"
* You should be presented with an error window rather than
the program crashing
[Where problems could occur]
* The new error window binds to the parent window. If the
parent window has gotten into a bad state this could
cause problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514183] Re: distutils : file "bdist_rpm.py" allows Shell injection in "name"
** Changed in: python Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1514183 Title: distutils : file "bdist_rpm.py" allows Shell injection in "name" Status in Python: Invalid Status in python2.7 package in Ubuntu: Incomplete Bug description: File : /usr/lib/python2.7/distutils/command/bdist_rpm.py Line 358 : This line in the code uses the depreached os.popen command, should be replaced with subprocess.Popen() : out = os.popen(q_cmd) Exploit demo : 1) Download the setup.py script wich i attached 2) Create a test folder an put the setup.py script in this folder 3) cd to the test folder 4) python setup.py bdist_rpm 5) A xmessage window pops up as a proof of concept ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libpython2.7-stdlib 2.7.10-4ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 8 13:47:34 2015 InstallationDate: Installed on 2015-10-22 (16 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: python2.7 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1514183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Ah, good to know! No problem at all, Brian! Cheers :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Fix Released
Bug description:
As far as I can tell gdb version 8.2.90 isn't searching the debug-
file-directory, which I set, for the '.gnu_debugaltlink' which is in
the debug symbols. Here's the error I'm seeing:
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
could not find '.gnu_debugaltlink' file for
/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)
Here's part of an strace of what's going on behind the scenes:
lstat("/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
{st_mode=S_IFREG|0644, st_size=839744, ...}) = 0
openat(AT_FDCWD,
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
This is the only time "/usr/lib/debug" is searched, generally
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/lib/debug/" is used. I'll attach the full strace though.
For completeness here's the gdb command I'm using:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
--ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
--ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
-linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox//usr/bin/gnome-calculator"' --ex 'core-file
/tmp/apport_core_1b6dn6np'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
@Sergio - Given the way the retracers are currently setup we are using
the version of gdb for the release for the crash we are retracing,
subsequently we'd need to SRU this to every release. Given that I've
already worked around this specific issue in apport backporting the fix
seems unnecessary.
I'm sorry I missed the fact that this had been fixed in hirsute!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Fix Released
Bug description:
As far as I can tell gdb version 8.2.90 isn't searching the debug-
file-directory, which I set, for the '.gnu_debugaltlink' which is in
the debug symbols. Here's the error I'm seeing:
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
could not find '.gnu_debugaltlink' file for
/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)
Here's part of an strace of what's going on behind the scenes:
lstat("/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
{st_mode=S_IFREG|0644, st_size=839744, ...}) = 0
openat(AT_FDCWD,
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
This is the only time "/usr/lib/debug" is searched, generally
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/lib/debug/" is used. I'll attach the full strace though.
For completeness here's the gdb command I'm using:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
--ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
--ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
-linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox//usr/bin/gnome-calculator"' --ex 'core-file
/tmp/apport_core_1b6dn6np'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
gdb (10.1-1.3) unstable; urgency=medium
* Non-maintainer upload.
* Convert to debhelper v10, not using the sequencer. Addresses: #973355.
* Search for DWZ files in debug-file-directories as well, patch taken
from the trunk.
* Only build with debuginfod on linux targets.
-- Matthias Klose Sun, 06 Dec 2020 22:42:31 +0100
** Changed in: gdb (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Fix Released
Bug description:
As far as I can tell gdb version 8.2.90 isn't searching the debug-
file-directory, which I set, for the '.gnu_debugaltlink' which is in
the debug symbols. Here's the error I'm seeing:
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
could not find '.gnu_debugaltlink' file for
/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)
Here's part of an strace of what's going on behind the scenes:
lstat("/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
{st_mode=S_IFREG|0644, st_size=839744, ...}) = 0
openat(AT_FDCWD,
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
This is the only time "/usr/lib/debug" is searched, generally
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/lib/debug/" is used. I'll attach the full strace though.
For completeness here's the gdb command I'm using:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
--ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
--ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
-linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox//usr/bin/gnome-calculator"' --ex 'core-file
/tmp/apport_core_1b6dn6np'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914467] [NEW] Problem with fractional scaling
Public bug reported: Hello, I would like to report a problem with fractional scaling. I have set it at 125%. I'm using a Huawei Matebook 13inch 2020 AMD (Ryzen 5 3500u) with Radeon Vega 8 Graphics. After starting the laptop, at the logon screen, the scaling seems to be at 200% but after I logon and go into my user session it turns to a scaling of 125%. At that moment I see 2 mouse pointers, one scaled 200% and one scaled at 125%. The mouse pointer which is scaled at 200% remains in its last position before the login process. It stays on top of any app or window that you open which is a bit annoying. The second mouse pointer (scaled at 125%) behaves normally. I tried to take a screenshot, but on a screenshot neither mouse pointer appear so I took a picture which I've added to this bug report. This bug is not specific to this version of Ubuntu, I can reproduce the problem in version 20.10. I haven't tried this in version 20.04. PopOS 20.10 does not exhibit this problem. It's a pity that Gnome has not yet made a better implementation of fractional scaling, high density display have been around for a while now. One would expect if one sets the scaling at 125%, that this would be applied system wide (sorry for the rant). Best regards, Eric P.S. : Sorry if this bug has been reported in a wrong category. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 3 20:49:00 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. Picasso [19e5:3e14] InstallationDate: Installed on 2021-02-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) MachineType: HUAWEI HN-WX9X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=b98eae12-e501-4bfe-88e5-b713ae9b9843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2020 dmi.bios.release: 1.13 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.13 dmi.board.asset.tag: N/A dmi.board.name: HN-WX9X-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnHUAWEI:bvr1.13:bd09/04/2020:br1.13:efr1.13:svnHUAWEI:pnHN-WX9X:pvrM1130:rvnHUAWEI:rnHN-WX9X-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130: dmi.product.family: MateBook dmi.product.name: HN-WX9X dmi.product.sku: C100 dmi.product.version: M1130 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute reproducible third-party-packages ubuntu ** Attachment added: "picture of the screen as the problem occurs" https://bugs.launchpad.net/bugs/1914467/+attachment/5459480/+files/IMG_0508.jpeg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1914467 Title: Problem with fractional scaling Status in xorg package in Ubuntu: New Bug description: Hello, I would like to report a problem with fractional scaling. I have set it at 125%. I'm using a Huawei Matebook 13inch 2020 AMD (Ryzen 5 3500u) with Radeon Vega 8 Graphics. After starting the laptop, at the logon screen, the scaling seems to be at 200% but after I logon and go into my user session it turns to a scaling of 125%. At that moment I see 2 mouse pointers, one scaled 200% and one scaled at 125%. The mouse pointer which is scaled at 200% remains in its last position before the login process. It stays on top of any app or window that you open which is a bit annoying. The second mouse pointer (scaled at 125%) behaves normally. I tried to take a screenshot, but on a screenshot neither mouse pointer appear so I took a picture which I've added to this bug report. This bug is not specific
[Touch-packages] [Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1795278
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
Michal, that's not how patching works, unfortunately. You can put all
that in a file and use the `patch` command. The easy way is to go to the
folder containing the file and run `sudo patch < /path/to/diff`.
Or you could simply edit the file (/usr/lib/python3/dist-
packages/softwareproperties/qt/SoftwarePropertiesQt.py) according to the
instructions given by the diff:
1. Starting at line 709, look at it and the following 7 lines for a total of
eight lines (this is what "-709,8" refers to in the original)
2. Note, too, that after the change, the same hunk is referenced as "+709,7"
meaning that the end result is one less line.
3. Remove the definition of the "url" variable in line 712.
4. In the next line (which is now 712) which defines the "filename" variable,
change it from using the KFileDialog.getOpenFileName method to the
QFileDialog.getOpenFileName method. Note that the arguments and their order are
different.
5. Save it and try again.
** Tags added: groovy hirsute
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Ah, I see that is has indeed been backport by Debian, and is already in
hirsute: debian/patches/2bf3b79d05bf85e41cbdcb020bd1cc424f59dd9a.diff is
the patch. @Brian, would you like me to backport the patch to another
release?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Confirmed
Bug description:
As far as I can tell gdb version 8.2.90 isn't searching the debug-
file-directory, which I set, for the '.gnu_debugaltlink' which is in
the debug symbols. Here's the error I'm seeing:
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
could not find '.gnu_debugaltlink' file for
/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)
Here's part of an strace of what's going on behind the scenes:
lstat("/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
{st_mode=S_IFREG|0644, st_size=839744, ...}) = 0
openat(AT_FDCWD,
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
This is the only time "/usr/lib/debug" is searched, generally
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/lib/debug/" is used. I'll attach the full strace though.
For completeness here's the gdb command I'm using:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
--ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
--ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
-linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox//usr/bin/gnome-calculator"' --ex 'core-file
/tmp/apport_core_1b6dn6np'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
P.S. added Hirsute and Groovy tags since the latest dupe shows it
affects Hirsute and thus should affect Groovy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
@Brian, Ops, sorry. I forgot about this bug, and then I kind of assumed
that it had already been backported on Debian. This is just for
hirsute, right? I can backport it now, give me just a second.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Confirmed
Bug description:
As far as I can tell gdb version 8.2.90 isn't searching the debug-
file-directory, which I set, for the '.gnu_debugaltlink' which is in
the debug symbols. Here's the error I'm seeing:
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
could not find '.gnu_debugaltlink' file for
/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)
Here's part of an strace of what's going on behind the scenes:
lstat("/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
{st_mode=S_IFREG|0644, st_size=839744, ...}) = 0
openat(AT_FDCWD,
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
This is the only time "/usr/lib/debug" is searched, generally
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/lib/debug/" is used. I'll attach the full strace though.
For completeness here's the gdb command I'm using:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
--ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
--ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
-linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox//usr/bin/gnome-calculator"' --ex 'core-file
/tmp/apport_core_1b6dn6np'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
downgrading systemd to the focal version in the lxc container fixes the issue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
@Sergio - Is this still something you are planning on backporting?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Confirmed
Bug description:
As far as I can tell gdb version 8.2.90 isn't searching the debug-
file-directory, which I set, for the '.gnu_debugaltlink' which is in
the debug symbols. Here's the error I'm seeing:
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
could not find '.gnu_debugaltlink' file for
/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)
Here's part of an strace of what's going on behind the scenes:
lstat("/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
{st_mode=S_IFREG|0644, st_size=839744, ...}) = 0
openat(AT_FDCWD,
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
This is the only time "/usr/lib/debug" is searched, generally
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/lib/debug/" is used. I'll attach the full strace though.
For completeness here's the gdb command I'm using:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
--ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
--ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
-linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox//usr/bin/gnome-calculator"' --ex 'core-file
/tmp/apport_core_1b6dn6np'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914461] Re: Unable to import key file in "authentication" in Software sources"
*** This bug is a duplicate of bug 1795278 ***
https://bugs.launchpad.net/bugs/1795278
Were you to `lxqt-sudo software-propreties-qt` you would see that this
is a duplicate of the other bug. Technically, it's got a fix. You might
want to try testing it and maybe we can actually get this resolved once
and for all.
** This bug has been marked a duplicate of bug 1795278
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1914461
Title:
Unable to import key file in "authentication" in Software sources"
Status in software-properties package in Ubuntu:
New
Bug description:
Running test on Lubuntu Hirsute daily ISO from QA testing tracker
http://cdimage.ubuntu.com/lubuntu/daily-live/20210203/hirsute-desktop-
amd64.iso
Unable to import key file in "authentication tab" - no error message
received
Steps to produce the bug
1. Open Software Sources from Preferences menu
2. Go to "Authentication" tab
3. Select/Click on "+Import Key File"
4. Nothing happens and no error message is received
The file manager should have opened and browsed for the key to import
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: software-properties-qt 0.99.5
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu57
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Wed Feb 3 18:37:11 2021
InstallationDate: Installed on 2021-02-03 (0 days ago)
InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210203)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1914461/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
l16 is was creates the issue ** Attachment added: "Example program showing the bug" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914062/+attachment/5459445/+files/bug.c -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
Reassigning to systemd but it could be a lxc issue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
The example works outside of the container or in a focal instance, commenting l30 makes it work on hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
Investigating the issue, udev fails to enumerate devices in the lxc environment when udev_enumerate_add_match_is_initialized is called. The same test program works in a focal instance. Discussing the issue on the LXD channel it was raised that the systemd udev changes in 247 could be creating problems. The network-manager 1.26 version works because the udev support was wrongly disabled, which was fixed in that commit https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/78dc57d8 ** Package changed: network-manager (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914461] [NEW] Unable to import key file in "authentication" in Software sources"
Public bug reported: Running test on Lubuntu Hirsute daily ISO from QA testing tracker http://cdimage.ubuntu.com/lubuntu/daily-live/20210203/hirsute-desktop- amd64.iso Unable to import key file in "authentication tab" - no error message received Steps to produce the bug 1. Open Software Sources from Preferences menu 2. Go to "Authentication" tab 3. Select/Click on "+Import Key File" 4. Nothing happens and no error message is received The file manager should have opened and browsed for the key to import ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: software-properties-qt 0.99.5 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Wed Feb 3 18:37:11 2021 InstallationDate: Installed on 2021-02-03 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210203) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1914461 Title: Unable to import key file in "authentication" in Software sources" Status in software-properties package in Ubuntu: New Bug description: Running test on Lubuntu Hirsute daily ISO from QA testing tracker http://cdimage.ubuntu.com/lubuntu/daily-live/20210203/hirsute-desktop- amd64.iso Unable to import key file in "authentication tab" - no error message received Steps to produce the bug 1. Open Software Sources from Preferences menu 2. Go to "Authentication" tab 3. Select/Click on "+Import Key File" 4. Nothing happens and no error message is received The file manager should have opened and browsed for the key to import ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: software-properties-qt 0.99.5 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Wed Feb 3 18:37:11 2021 InstallationDate: Installed on 2021-02-03 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210203) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1914461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: jacqueline fairgrieve (jac9) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for
[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
** Changed in: packagekit (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: packagekit (Ubuntu Eoan)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: packagekit (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: packagekit (Ubuntu Groovy)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Won't Fix
Status in packagekit source package in Focal:
Confirmed
Status in packagekit source package in Groovy:
New
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
[Impact]
* If selected mirrors are not reachable or have
expired GPG keys, software-properties-gtk
would crash
[Test Case]
* Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors
* Find your locale in this file and add a non-existent URL
to the list
* Run software-properties-gtk and choose your newly added
URL from the "Download From" dropdown menu
* Press "Close" in the bottom right, and when
prompted press "Reload"
* You should be presented with an error window rather than
the program crashing
[Where problems could occur]
* The new error window binds to the parent window. If the
parent window has gotten into a bad state this could
cause problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
I've sponsored this for Focal and Groovy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Won't Fix
Status in packagekit source package in Focal:
Confirmed
Status in packagekit source package in Groovy:
New
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
[Impact]
* If selected mirrors are not reachable or have
expired GPG keys, software-properties-gtk
would crash
[Test Case]
* Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors
* Find your locale in this file and add a non-existent URL
to the list
* Run software-properties-gtk and choose your newly added
URL from the "Download From" dropdown menu
* Press "Close" in the bottom right, and when
prompted press "Reload"
* You should be presented with an error window rather than
the program crashing
[Where problems could occur]
* The new error window binds to the parent window. If the
parent window has gotten into a bad state this could
cause problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
We believe that all the documentation errors and shortcomings have been addressed, subsequently I'm setting this bug to Fix Released. Additionally, the bugs with packages due to the 5.8 kernel have also been resolved and if they have not new bug reports about the specific package should be opened. Thanks again for reporting this bug and ensuring that we've communicated this change in behavior. ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to:
[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
** Also affects: packagekit (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Won't Fix
Status in packagekit source package in Focal:
Confirmed
Status in packagekit source package in Groovy:
New
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
[Impact]
* If selected mirrors are not reachable or have
expired GPG keys, software-properties-gtk
would crash
[Test Case]
* Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors
* Find your locale in this file and add a non-existent URL
to the list
* Run software-properties-gtk and choose your newly added
URL from the "Download From" dropdown menu
* Press "Close" in the bottom right, and when
prompted press "Reload"
* You should be presented with an error window rather than
the program crashing
[Where problems could occur]
* The new error window binds to the parent window. If the
parent window has gotten into a bad state this could
cause problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805666] Re: Evolution Alarm Notify continues pop-up reminders even though notifications disabled
CORRECTION: I solved my problem by deleting the CONTENT of this file: ~/.local/share/evolution/calendar/system/calendar.ics And also this file: ~/.evolution/calendar/local/system/calendar.ics I left the (now empty) files there after deleting their contents, in case something was expecting them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1805666 Title: Evolution Alarm Notify continues pop-up reminders even though notifications disabled Status in evolution-data-server package in Ubuntu: Invalid Bug description: I have turned off notifications for evolution alarm notify in settings: https://i.imgur.com/BNlfgzA.png But I still get pop-ups from the evolution alarm notify app for calendar events: https://i.imgur.com/BBdr9gm.png ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 28 11:31:46 2018 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2018-07-14 (136 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-29 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1805666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: (unassigned) => jacqueline fairgrieve (jac9) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for
[Touch-packages] [Bug 1910405] Re: bluetoothd hangs and cannot be killed
jan 11 11:59:05 omer kernel: Bluetooth: hci0: Received unexpected HCI Event jan 11 11:59:05 omer kernel: Bluetooth: hci0: Received unexpected HCI Event jan 11 11:59:05 omer kernel: Bluetooth: hci0: Received unexpected HCI Event jan 11 11:59:05 omer kernel: Bluetooth: hci0: Received unexpected HCI Event jan 11 11:59:47 omer bluetoothd[13716]: Suspend: Connection timed out (110) jan 11 11:59:47 omer kernel: Bluetooth: hci0: Received unexpected HCI Event Looks like a firmware issue and bug 1905214 updated firmware intel/ibt-20-1-3.sfi to REL13705 in Focal while it remains REL0310 in Bionic. Could you try download following two files and place them in /lib/firmware/intel. They are the firmware blobs currently used in Focal. Backup first of course. * https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-firmware/plain/intel/ibt-20-1-3.ddc?h=focal * https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-firmware/plain/intel/ibt-20-1-3.sfi?h=focal Upstream linux-firmware has even newer revisions. Please try following two if Focal's still don't resolve your problem: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/intel/ibt-20-1-3.ddc * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/intel/ibt-20-1-3.sfi ** Tags added: hwe-bluetooth ** Summary changed: - bluetoothd hangs and cannot be killed + Intel Bluetooth AX200 [8086:2723] Subsystem [1a56:1653]: bluetoothd hangs and cannot be killed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1910405 Title: Intel Bluetooth AX200 [8086:2723] Subsystem [1a56:1653]: bluetoothd hangs and cannot be killed Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hi, When having a bluetooth headphone (JBL Live) connected using the A2DP pulseaudio sink, the output sound suddenly stops during a music streaming of videocall session. Sometimes just disconnecting and reconnecting the headphone works, but some times reconnection is not possible anymore due to the hanging of bluetoothd. Bluetoothd still appears in the processes list, but cannot be killed, neither with "sudo service bluetooth stop" or "kill -9": $ ps afx | grep blue 9597 tty2 Sl+0:01 | \_ gnome-control-center bluetooth 5405 ?Ss 0:00 \_ /usr/lib/bluetooth/obexd 10694 pts/0S+ 0:00 \_ grep blue 20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd All programs keep working normally, only bluetooth is affected as well as the bluetooth settings page. The only solution is a hard reboot. A soft reboot doesn't even work: the systems keeps trying to end the bluetoothd process so one needs to press the power button for a few seconds to terminate the process. $ bluetoothd --version 5.48 $ uname -a Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working nice for over one year now just like previous versions. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-11-22 (415 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 7390 Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78 Tags: bionic Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/22/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:1D:96:DA:70:EA ACL MTU: 1021:4 SCO
[Touch-packages] [Bug 1914278] Re: apt autoremove is not removing unused kernels
TJ:
linux-image-5.4.0-40-generic/focal-updates,focal-security,now 5.4.0-40.44 amd64
[installed,automatic]
linux-image-5.4.0-40-lowlatency/focal-updates,focal-security,now 5.4.0-40.44
amd64 [installed,automatic]
linux-image-5.4.0-42-generic/focal-updates,focal-security,now 5.4.0-42.46 amd64
[installed,auto-removable]
linux-image-5.4.0-42-lowlatency/focal-updates,focal-security,now 5.4.0-42.46
amd64 [installed,auto-removable]
linux-image-5.4.0-65-generic/focal-updates,focal-security,now 5.4.0-65.73 amd64
[installed]
linux-image-5.4.0-65-lowlatency/focal-updates,focal-security,now 5.4.0-65.73
amd64 [installed]
linux-image-5.8.0-34-generic/focal-updates,focal-security,now
5.8.0-34.37~20.04.2 amd64 [installed,automatic]
linux-image-5.8.0-34-lowlatency/focal-updates,focal-security,now
5.8.0-34.37~20.04.2 amd64 [installed,automatic]
linux-image-5.8.0-41-generic/focal-updates,focal-security,now
5.8.0-41.46~20.04.1 amd64 [installed]
linux-image-5.8.0-41-lowlatency/focal-updates,focal-security,now
5.8.0-41.46~20.04.1 amd64 [installed]
linux-image-generic-hwe-20.04/focal-updates,focal-security,now
5.8.0.41.46~20.04.27 amd64 [installed,automatic]
linux-image-generic/focal-updates,focal-security,now 5.4.0.65.68 amd64
[installed,automatic]
linux-image-lowlatency-hwe-20.04/focal-updates,focal-security,now
5.8.0.41.46~20.04.27 amd64 [installed,automatic]
linux-image-lowlatency/focal-updates,focal-security,now 5.4.0.65.68 amd64
[installed,automatic]
Balint:
Result: https://paste.ubuntu.com/p/JVHZpFWBBT/
It appears as though apt and u-u are doing the job, but for some reason
the packages aren't getting marked as autoremovable when they're
upgraded? I had to manually mark these as autoremovable (apt-mark linux-
image-${version}-${generic|lowlatency} auto) to get u-u or apt to do
anything about it. If you look at the list above, even the 5.4.0-65 and
5.4.0-41 kernels are showing up as manually installed, which is not the
case (they were installed via their respective metapackages).
So, something is definitely not working as expected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1914278
Title:
apt autoremove is not removing unused kernels
Status in apt package in Ubuntu:
Incomplete
Status in discover package in Ubuntu:
New
Status in packagekit package in Ubuntu:
New
Status in unattended-upgrades package in Ubuntu:
Incomplete
Bug description:
With the machines I help administer, we have been finding situations
where the /boot directory is filling-up beyond 3 kernels on LUKS
encrypted systems. apt autoremove is not removing old kernels as
expected.
This may also be an issue with unattended-upgrades since I found the
following line commented-out by default:
// Remove unused automatically installed kernel-related packages
// (kernel images, kernel headers and kernel version locked tools).
// Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";
We have had a system with as many as 15 kernel packages installed as a
result of this not working as expected.
The majority of these machines are using Discover to do their package
upgrading, which uses PackageKit as its backend.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apt 2.0.4
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Tue Feb 2 09:29:01 2021
InstallationDate: Installed on 2020-11-07 (87 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
(20200731)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1910928] Re: Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1910928 Title: Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL Status in bluez package in Ubuntu: Confirmed Bug description: After I have installed the Ubuntu - I have noticed, that Bluetooth won't go turn on after Suspend. The only way to get it working - reboot the system. WiFi Adapter - AX201 I have tried the latest kernel (5.11.rc2) - no luck. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20SL NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: bluez 5.55-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN22WW dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL: dmi.product.family: Thinkbook 14-IIL dmi.product.name: 20SL dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL dmi.product.version: Lenovo ThinkBook 14-IIL dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:26:49:C4:B9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:19913 acl:0 sco:0 events:3169 errors:0 TX bytes:770617 acl:0 sco:0 commands:3167 errors:0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20SL NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: bluez 5.55-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN22WW dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL: dmi.product.family: Thinkbook 14-IIL dmi.product.name: 20SL dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL dmi.product.version: Lenovo ThinkBook 14-IIL dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
Updating the proposed change. This addresses the following: - Only run from the trigger stage when called from dpkg - Pass the same environmental flag as update-initramfs does (in theory there never should be need to generate an initrd) - Handle special case of installkernel called multiple times with the same version ** Patch added: "Proposed hirsute change (v2)" https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1877088/+attachment/5459430/+files/hirsute-linux-base.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: In Progress Status in debianutils package in Ubuntu: New Status in linux-base package in Ubuntu: In Progress Bug description: When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
There is here a change in behavior in lxc/lxd. Running https://paste.ubuntu.com/p/vz7SXcX3K9/: On hirsute lxd container: root@hirsute:~# ./test access errno 13 path is read only: 0 root@hirsute:~# mount | grep 'sysfs on /sys ' sysfs on /sys type sysfs (rw,relatime) On focal lxd container: root@focal:~# ./test path is read only: 1 root@focal:~# mount | grep 'sysfs on /sys ' sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime) (no idea why there are two mounts in focal) According to https://systemd.io/CONTAINER_INTERFACE/ , /sys should be mounted read-only? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in network-manager package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914409] Re: fsck integration is not flicker free
** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914409 Title: fsck integration is not flicker free Status in systemd package in Ubuntu: New Bug description: Install Ubuntu desktop, with full disk LUKS encryption, on an UEFI system. On boot, ESP & rootfs will have fsck started. This flickers briefly that fsck are in progress, although most of the time both the ESP and rootfs fsck finish/exit instantly. It would be nice delaying to show fsck progress in plymouth until it takes a substantial amount of time and/or if there is progress about it. I.e. ideally it should not be shown if it takes less than a second to complete (or some other very quick threshold). As there is not enough to time to show the message that the fsck is in progress, for the human to read it, before the message is dissmissed again. One can see this as a flickerfree boot effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1910405] Re: bluetoothd hangs and cannot be killed
The problem is back. This time I let the restart process wait for several minutes. See this output. peddecke@omer:~$ sudo service bluetooth restart Job for bluetooth.service failed because the control process exited with error code. See "systemctl status bluetooth.service" and "journalctl -xe" for details. peddecke@omer:~$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: failed (Result: exit-code) since Wed 2021-02-03 14:21:30 CET; 14s ago Docs: man:bluetoothd(8) Process: 18598 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=1/ Main PID: 18598 (code=exited, status=1/FAILURE) Status: "Starting up" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─25952 /usr/lib/bluetooth/bluetoothd feb 03 14:15:29 omer systemd[1]: bluetooth.service: Main process exited, code=exited, status=1/FAILURE feb 03 14:15:29 omer bluetoothd[18598]: Unable to get on D-Bus feb 03 14:16:59 omer systemd[1]: bluetooth.service: State 'stop-sigterm' timed out. Killing. feb 03 14:16:59 omer systemd[1]: bluetooth.service: Killing process 25952 (bluetoothd) with signal SIGKILL. feb 03 14:18:30 omer systemd[1]: bluetooth.service: Processes still around after SIGKILL. Ignoring. feb 03 14:20:00 omer systemd[1]: bluetooth.service: State 'stop-final-sigterm' timed out. Killing. feb 03 14:20:00 omer systemd[1]: bluetooth.service: Killing process 25952 (bluetoothd) with signal SIGKILL. feb 03 14:21:30 omer systemd[1]: bluetooth.service: Processes still around after final SIGKILL. Entering failed mode. feb 03 14:21:30 omer systemd[1]: bluetooth.service: Failed with result 'exit-code'. feb 03 14:21:30 omer systemd[1]: Failed to start Bluetooth service. Seems the same problem where killing doesn't work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1910405 Title: bluetoothd hangs and cannot be killed Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hi, When having a bluetooth headphone (JBL Live) connected using the A2DP pulseaudio sink, the output sound suddenly stops during a music streaming of videocall session. Sometimes just disconnecting and reconnecting the headphone works, but some times reconnection is not possible anymore due to the hanging of bluetoothd. Bluetoothd still appears in the processes list, but cannot be killed, neither with "sudo service bluetooth stop" or "kill -9": $ ps afx | grep blue 9597 tty2 Sl+0:01 | \_ gnome-control-center bluetooth 5405 ?Ss 0:00 \_ /usr/lib/bluetooth/obexd 10694 pts/0S+ 0:00 \_ grep blue 20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd All programs keep working normally, only bluetooth is affected as well as the bluetooth settings page. The only solution is a hard reboot. A soft reboot doesn't even work: the systems keeps trying to end the bluetoothd process so one needs to press the power button for a few seconds to terminate the process. $ bluetoothd --version 5.48 $ uname -a Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working nice for over one year now just like previous versions. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-11-22 (415 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 7390 Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78 Tags: bionic Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/22/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check
Request for truely flicker free boot is in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914409 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1880250 Title: Ctrl-C message displayed without any actual disk check Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in plymouth source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in plymouth source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: [Impact] * fsck messages is shown by plymouth, despite all fscks already completed. [Test Case] * Install Ubuntu Desktop with full disk encryption * Observe that fsck messages (press ctrl+c) is shown, and remains there on screen for a little while as plymouth transitions to gdm * After installing the update, observe that when fsck completes the messages are cleared and the transition to gdm is done without fsck/ctrl+c message present. * After this change lands in -updates, and daily desktop images are built with this, double check that casper-md5sum transition is also smooth. [Regression Potential] * plymouth spinner theme is adjusted to clear the footer, at the end of fsck, even if systemd-fsckd didn't do that. At the moment there are two consumers of the fsck apis systemd-fsckd & casper-md5sum used on installed systems and live-isos respectively. If something else pushes messages to the footer, they might get cleared at the end of fsck. [Other Info] * Original bug report It seems the transition to bgrt lost something with Ubuntu's disk check details. The only thing I see on my screen during a long disk check is the "press Ctrl-C to stop all in progress disk checks" with no progress. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check
Installed focal Ubuntu desktop .2 media with LUKS full disk encryption. On boot the fsck messages briefly flicker, and then are cleared, then there is smooth transition to gdm. It's a lot better than before, where fsck message would linger forever. It would be ideal to make it flickerfree. Aka delay displaying fsck message if it takes more than 1second and/or there is an update. ** Changed in: systemd (Ubuntu Focal) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu Groovy) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1880250 Title: Ctrl-C message displayed without any actual disk check Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in plymouth source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in plymouth source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: [Impact] * fsck messages is shown by plymouth, despite all fscks already completed. [Test Case] * Install Ubuntu Desktop with full disk encryption * Observe that fsck messages (press ctrl+c) is shown, and remains there on screen for a little while as plymouth transitions to gdm * After installing the update, observe that when fsck completes the messages are cleared and the transition to gdm is done without fsck/ctrl+c message present. * After this change lands in -updates, and daily desktop images are built with this, double check that casper-md5sum transition is also smooth. [Regression Potential] * plymouth spinner theme is adjusted to clear the footer, at the end of fsck, even if systemd-fsckd didn't do that. At the moment there are two consumers of the fsck apis systemd-fsckd & casper-md5sum used on installed systems and live-isos respectively. If something else pushes messages to the footer, they might get cleared at the end of fsck. [Other Info] * Original bug report It seems the transition to bgrt lost something with Ubuntu's disk check details. The only thing I see on my screen during a long disk check is the "press Ctrl-C to stop all in progress disk checks" with no progress. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914409] [NEW] fsck integration is not flicker free
Public bug reported: Install Ubuntu desktop, with full disk LUKS encryption, on an UEFI system. On boot, ESP & rootfs will have fsck started. This flickers briefly that fsck are in progress, although most of the time both the ESP and rootfs fsck finish/exit instantly. It would be nice delaying to show fsck progress in plymouth until it takes a substantial amount of time and/or if there is progress about it. I.e. ideally it should not be shown if it takes less than a second to complete (or some other very quick threshold). As there is not enough to time to show the message that the fsck is in progress, for the human to read it, before the message is dissmissed again. One can see this as a flickerfree boot effort. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: flickerfree -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914409 Title: fsck integration is not flicker free Status in systemd package in Ubuntu: New Bug description: Install Ubuntu desktop, with full disk LUKS encryption, on an UEFI system. On boot, ESP & rootfs will have fsck started. This flickers briefly that fsck are in progress, although most of the time both the ESP and rootfs fsck finish/exit instantly. It would be nice delaying to show fsck progress in plymouth until it takes a substantial amount of time and/or if there is progress about it. I.e. ideally it should not be shown if it takes less than a second to complete (or some other very quick threshold). As there is not enough to time to show the message that the fsck is in progress, for the human to read it, before the message is dissmissed again. One can see this as a flickerfree boot effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
Fix will come with network-manager-gnome 1.20.0. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1458322 Title: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were created by Docker. Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged under the gnome system tray icon which is kind of annoying. I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 24 14:22:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-29 (632 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) IpRoute: default via 192.168.178.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.40 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-08-19T11:46:06.705439 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914401] Re: Memory problems running finfo::buffer with PHP_CLI
** Package changed: ubuntu => file (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1914401
Title:
Memory problems running finfo::buffer with PHP_CLI
Status in file package in Ubuntu:
New
Bug description:
PHP internally uses libmagic for getting information about files. This
sample php code consumes 483 MB of RAM for detecting mimetype of a 48
MB MP3 file using php7.4 but it uses only 56 MB with php7.2.
$finfo = new finfo(FILEINFO_MIME_TYPE, '');
$contents = file_get_contents('file.mp3');
echo($finfo->buffer($contents));
The bug is reported to php as well. They say it should be reported to
libmagic. See https://bugs.php.net/bug.php?id=79263
The PHP bug is over 1 year old.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libmagic1 1:5.32-2ubuntu0.4
ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
Uname: Linux 4.15.0-135-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 3 15:04:30 2021
Dependencies:
gcc-8-base 8.4.0-1ubuntu1~18.04
libc6 2.27-3ubuntu1.4
libgcc1 1:8.4.0-1ubuntu1~18.04
libmagic-mgc 1:5.32-2ubuntu0.4
zlib1g 1:1.2.11.dfsg-0ubuntu2
InstallationDate: Installed on 2018-10-07 (849 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: file
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1914401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1571506] Re: update-initramfs should include firmware from /lib/firmware/updates
Apparently lots of things still ship stuff in /updates/ And because kernel says so, distributions are forced to follow. ** Changed in: initramfs-tools (Ubuntu) Status: Won't Fix => Triaged ** Also affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Hirsute) Importance: Wishlist Status: Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1571506 Title: update-initramfs should include firmware from /lib/firmware/updates Status in initramfs-tools package in Ubuntu: Triaged Status in initramfs-tools source package in Focal: New Status in initramfs-tools source package in Groovy: New Status in initramfs-tools source package in Hirsute: Triaged Bug description: according to the kernel doc http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/firmware_class/README Linux kernel will search firmware from "/lib/firmware/updates/" UTS_RELEASE, "/lib/firmware/updates", "/lib/firmware/" UTS_RELEASE, "/lib/firmware" But the add module function in initramfs-tools won't search the "/lib/firmware/updates". This problem applies to all Ubuntu releases. Attach patch to fix this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.2 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: Unity Date: Mon Apr 18 14:24:29 2016 InstallationDate: Installed on 2014-04-23 (725 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1571506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
I added some extra debug output in avahi and waited for the error to
happen again, in this way found out that the assertion failure happens
when the time_event_queue_root(q) call gives NULL so that the "else"
part is used in update_timeout() in avahi-core/timeeventq.c:
static void update_timeout(AvahiTimeEventQueue *q) {
AvahiTimeEvent *e;
assert(q);
if ((e = time_event_queue_root(q)))
q->poll_api->timeout_update(q->timeout, >expiry);
else
q->poll_api->timeout_update(q->timeout, NULL); <-- assertion failure
inside this call
}
So time_event_queue_root(q) gives NULL which means that q->prioq->root
is NULL. Why would that happen?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1820584
Title:
seahorse assert failure: seahorse: glib-watch.c:195: timeout_update:
Assertion `!t->dead' failed.
Status in avahi package in Ubuntu:
Confirmed
Bug description:
-
Description: Ubuntu Disco Dingo (development branch)
Release: 19.04
-
seahorse:
Installed: 3.32-1
Candidate: 3.32-1
Version table:
*** 3.32-1 500
500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
-
I have absolutely no idea why or how. Just collected this report from
apport-cli.
Some times receiving "internal error" reports, no details provided,
just "Cancel" or "Send report" options. So, I decided to check apport
and there was this report.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: seahorse 3.32-1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion
`!t->dead' failed.
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 17 18:09:01 2019
ExecutablePath: /usr/bin/seahorse
InstallationDate: Installed on 2019-03-17 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316)
ProcCmdline: /usr/bin/seahorse --gapplication-service
Signal: 6
SourcePackage: seahorse
StacktraceTop:
__assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s'
failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000
"glib-watch.c", line=195, function=) at assert.c:92
__GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000
"glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at
assert.c:101
?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3
?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update:
Assertion `!t->dead' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914401] [NEW] Memory problems running finfo::buffer with PHP_CLI
You have been subscribed to a public bug:
PHP internally uses libmagic for getting information about files. This
sample php code consumes 483 MB of RAM for detecting mimetype of a 48 MB
MP3 file using php7.4 but it uses only 56 MB with php7.2.
$finfo = new finfo(FILEINFO_MIME_TYPE, '');
$contents = file_get_contents('file.mp3');
echo($finfo->buffer($contents));
The bug is reported to php as well. They say it should be reported to
libmagic. See https://bugs.php.net/bug.php?id=79263
The PHP bug is over 1 year old.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libmagic1 1:5.32-2ubuntu0.4
ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
Uname: Linux 4.15.0-135-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 3 15:04:30 2021
Dependencies:
gcc-8-base 8.4.0-1ubuntu1~18.04
libc6 2.27-3ubuntu1.4
libgcc1 1:8.4.0-1ubuntu1~18.04
libmagic-mgc 1:5.32-2ubuntu0.4
zlib1g 1:1.2.11.dfsg-0ubuntu2
InstallationDate: Installed on 2018-10-07 (849 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: file
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: file (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
Memory problems running finfo::buffer with PHP_CLI
https://bugs.launchpad.net/bugs/1914401
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to file in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
I managed to get Campbell's patch to hide unmanaged devices upstreamed: https://gitlab.gnome.org/GNOME/network-manager- applet/-/merge_requests/93 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1458322 Title: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were created by Docker. Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged under the gnome system tray icon which is kind of annoying. I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 24 14:22:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-29 (632 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) IpRoute: default via 192.168.178.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.40 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-08-19T11:46:06.705439 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914398] [NEW] df reports negative number of used blocks on large filesystem
Public bug reported: df reports negative number of used blocks on large filesystem (18.5 TiB): nornetpp@oesthorn:~$ df /home Filesystem 1K-blocksUsed Available Use% Mounted on /dev/sdb1 2684353464 -1825532684 4509886148- /home nornetpp@oesthorn:~$ cat /etc/fstab | grep /home UUID=9a12de8d-1d01-4930-9897-5d4097b7f892 /home reiserfs defaults nornetpp@oesthorn:~$ sudo gdisk /dev/sdb [sudo] password for nornetpp: GPT fdisk (gdisk) version 1.0.5 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command (? for help): p Disk /dev/sdb: 39728447488 sectors, 18.5 TiB Model: Virtual disk Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 0956159A-AAFE-4DB4-8FD3-6F6A515B1727 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 39728447454 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector)End (sector) Size Code Name 12048 39728447454 18.5 TiB8300 Linux filesystem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: coreutils 8.30-3ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 3 12:35:45 2021 InstallationDate: Installed on 2012-10-12 (3036 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) SourcePackage: coreutils UpgradeStatus: Upgraded to focal on 2021-02-03 (0 days ago) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1914398 Title: df reports negative number of used blocks on large filesystem Status in coreutils package in Ubuntu: New Bug description: df reports negative number of used blocks on large filesystem (18.5 TiB): nornetpp@oesthorn:~$ df /home Filesystem 1K-blocksUsed Available Use% Mounted on /dev/sdb1 2684353464 -1825532684 4509886148- /home nornetpp@oesthorn:~$ cat /etc/fstab | grep /home UUID=9a12de8d-1d01-4930-9897-5d4097b7f892 /home reiserfs defaults nornetpp@oesthorn:~$ sudo gdisk /dev/sdb [sudo] password for nornetpp: GPT fdisk (gdisk) version 1.0.5 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command (? for help): p Disk /dev/sdb: 39728447488 sectors, 18.5 TiB Model: Virtual disk Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 0956159A-AAFE-4DB4-8FD3-6F6A515B1727 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 39728447454 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector)End (sector) Size Code Name 12048 39728447454 18.5 TiB8300 Linux filesystem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: coreutils 8.30-3ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 3 12:35:45 2021 InstallationDate: Installed on 2012-10-12 (3036 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) SourcePackage: coreutils UpgradeStatus: Upgraded to focal on 2021-02-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1914398/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914278] Re: apt autoremove is not removing unused kernels
Please install a few old kernels manually, mark them autoremovable and run u-u in verbose and debug mode. If u-u removes those kernels this is not an u-u bug. Then install those again and try removing them with apt. If apt removes those kernels than this is not an APT bug. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Incomplete ** Changed in: apt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1914278 Title: apt autoremove is not removing unused kernels Status in apt package in Ubuntu: Incomplete Status in discover package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: With the machines I help administer, we have been finding situations where the /boot directory is filling-up beyond 3 kernels on LUKS encrypted systems. apt autoremove is not removing old kernels as expected. This may also be an issue with unattended-upgrades since I found the following line commented-out by default: // Remove unused automatically installed kernel-related packages // (kernel images, kernel headers and kernel version locked tools). // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true"; We have had a system with as many as 15 kernel packages installed as a result of this not working as expected. The majority of these machines are using Discover to do their package upgrading, which uses PackageKit as its backend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.4 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Feb 2 09:29:01 2021 InstallationDate: Installed on 2020-11-07 (87 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This is only a linux package update process problem, and apt frontends can do nothing to prevent it. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
The linux packgages need to add breaks against in-archive dkms modules failing to build with the updated kernel, thus APT and APT frontends can hold back the upgrade until all dkms package updates become ready. ** Changed in: update-manager (Ubuntu) Status: New => Invalid ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
Since this breaks systems unattended I'm marking the bug as High, but I recommend the Critical severity. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
Reported upstream https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/650 ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #650 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/650 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in network-manager package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
