[Bug 1850485] Re: bionic/linux-hwe-edge: 5.3.0-21.22~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: main: linux-hwe-edge meta: linux-meta-hwe-edge signed: linux-signed-hwe-edge phase: Promote to Proposed phase-changed: Wednesday, 30. October 2019 17:16 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850485 Title: bionic/linux-hwe-edge: 5.3.0-21.22~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823299] Re: Package out of date
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: telegram-desktop (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823299 Title: Package out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1823299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847892] Re: large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel
Any specific params you want for iperf BTW? I ran some basic tests against a VM after all: it might have lost a few %, but wireless is so slow that it's not going to make any meaningful difference. [ ID] IntervalTransferBandwidth Reads Dist(bin=16.0K) [ 4] 0.-11.4354 sec 45.8 MBytes 33.6 Mbits/sec 22348 22341:6:0:1:0:0:0:0 [ 4] local 192.168.1.34 port 5001 connected with 192.168.1.33 port 45314 [ 4] 0.-10.3068 sec 68.6 MBytes 55.9 Mbits/sec 35906 35901:2:3:0:0:0:0:0 [ 4] local 192.168.1.34 port 5001 connected with 192.168.1.33 port 45316 [ 4] 0.-10.3491 sec 71.6 MBytes 58.1 Mbits/sec 35522 35512:2:4:4:0:0:0:0 [ 4] local 192.168.1.34 port 5001 connected with 192.168.1.33 port 45324 [ 4] 0.-10.3927 sec 75.1 MBytes 60.6 Mbits/sec 35410 35397:7:3:2:1:0:0:0 [ 4] local 192.168.1.34 port 5001 connected with 192.168.1.33 port 45326 [ 4] 0.-10.3910 sec 59.8 MBytes 48.2 Mbits/sec 30683 30675:3:4:1:0:0:0:0 The first run may well have had the wifi at low power: the client had just been woken up a couple of minutes earlier, but it tends to dial that back quite quickly. I left it in for completeness. An rsync right after the last run was 6,906,424.15 bytes/sec, so ~58.65 Mb/s. I think that's a good indicator of being able to trust the historical data from it. I may have the machine in here at some point in the next few days, and will test that too if so. For 1795116, the performance in that scenario (~6' and LOS) was fine: it wasn't that the driver was broken across the board, it just wasn't managing power properly so it fell apart if conditions weren't perfect. (Not saying this is the same bug, just reminding myself what a result like that means). I still need to boot into 16.04 / etc to try and find a working kernel. AFAICT 16.04.6 shipped with one that has the post-1795116 fix in it, so it should be okay off a USB. If not though I'll have to get creative, as there isn't a spare partition on that machine to install to. My notes show 4.15.0-55 as the first version with the old bug fixed. It would be helpful if there was a reasonable way for me to just install that, since there are multiple dist-upgrade's worth of other changes since then. While that specific kernel would be ideal from a testing standpoint, isn't there somewhere I can just grab the current Bionic kernel from, as a dpkg, and just install the damn thing without having to jump through any hoops? Surely there must be a better system in place already than randomly guessing at versions or doing builds on a system that is totally unsuitable for such tasks. :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847892 Title: large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823299] Re: Package out of date
That popup message is coming with updateServiceNotification from
Telegram backend.
[23:58:28.811 01-0001754] (dc:2) Recv: { core_message
msg_id: 6753703395900790785 [LONG],
seq_no: 85 [INT],
bytes: 184 [INT],
body: { updates
updates: [ vector<0x0>
{ updateServiceNotification
flags: 1 [INT],
popup: YES [ BY BIT 0 IN FIELD flags ],
inbox_date: [ SKIPPED BY BIT 1 IN FIELD flags ],
type: "API_ERROR_UPDATE_UNOFFICIAL" [STRING],
message: "Error. Please update your app to the latest version or switch
to the official version of Telegram." [STRING],
media: { messageMediaEmpty },
entities: [ vector<0x0> ],
},
],
users: [ vector<0x0> ],
chats: [ vector<0x0> ],
date: 1572469107 [INT],
seq: 1774 [INT],
},
}
I believe we are able to backport a new version to Bionic Beaver. At
least v1.8.15 is successfully compiled against Qt 5.9.5 and FFmpeg
3.4.6. Moreover, we could provide a new version via the bionic-updates
repository like Firefox or Thunderbird get updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823299
Title:
Package out of date
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1823299/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850201] Re: memory usage is growing over time
The test system was 19.10 in virtualbox. I removed almost every extensions, except for the built in ones (ubuntu dock, ubuntu appindicator, etc.). Gnome-shell uses ~200kB at the beginning. If I lock the screen and unlock it, the memory usage jumps to ~210kB. Repeatedly doing this, the memory usage is increasing. Similarly, suspending the system and wakeing it up also cause a jump in the memory usage, which remains there permanently. After manually reset gnome-shell (Alt+F2 r) the memory usage falls back to ~200kB. What is the theoretical memory usage of gnome-shell? When I reset it, the memory usage is ~90kB for a couple of second, and it grows back to ~200kB. It already happened that the memory usage at the beginning of the gnome session was very low (~80kB), and grew very slowly (couple of minutes with countinuous work, launching programs, browsering the web) until it reached the approx. 200kB usage. It is very suspecious. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850201 Title: memory usage is growing over time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671951] Re: networkd should allow configuring IPV6 MTU
@raharper could you give the systemd in this ppa a test: https://launchpad.net/~ddstreet/+archive/ubuntu/systemd also, you're setting the MTUBytes via .link file, but that won't work inside an lxd container as that setting only has any effect during udev processing of interface 'add' uevent, which doesn't happen inside an lxd container because 1) the interface already exists when the container boots up and 2) systemd-udev-trigger.service has no effect (unlike bare metal systems or vms) because unprivileged containers can't force uevent generation by writing to sysfs uevent nodes. Instead try adding a [Link] section to the .network file with the MTUBytes; that will get applied every time networkd starts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849416] Re: Xubuntu ping command leading to all of sessions closed
Could you add a journalctl log of a session having the issue? ** Changed in: iputils (Ubuntu) Importance: Undecided => Low ** Changed in: iputils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849416 Title: Xubuntu ping command leading to all of sessions closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1849416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850063] Re: Unable to install
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: ubiquity (Ubuntu) Importance: Undecided => Low ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850063 Title: Unable to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1850063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848309] Re: "Automatic Date & Time" doesn't reflect the service status
** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #752 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/752 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/752 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848309 Title: "Automatic Date & Time" doesn't reflect the service status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1848309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850048] Re: i do not know anything about the bug
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: grub-installer (Ubuntu) Importance: Undecided => Low ** Changed in: grub-installer (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850048 Title: i do not know anything about the bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1850048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849907] Re: Add Online Account Nextcloud no Connect button on Unity
** Package changed: gnome-online-accounts (Ubuntu) => unity-control- center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849907 Title: Add Online Account Nextcloud no Connect button on Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1849907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849002] Re: bionic/linux-bluefield: 5.0.0-1004.13 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850574 packages: main: linux-bluefield meta: linux-meta-bluefield phase: Holding before Promote to Proposed phase-changed: Wednesday, 30. October 2019 20:41 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued + promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849002 Title: bionic/linux-bluefield: 5.0.0-1004.13 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
Comment #10 means fixed in focal (20.04) only for now. Stable Release Update in eoan (19.10) to follow in due course. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850074] Re: No puedo actualizar a 19, 10. Error al momento de hacer la particion.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: ubiquity (Ubuntu) Importance: Undecided => Low ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850074 Title: No puedo actualizar a 19,10. Error al momento de hacer la particion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1850074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850718] Re: package virtualbox-dkms 6.0.14-dfsg-1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850718 Title: package virtualbox-dkms 6.0.14-dfsg-1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1850718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850718] [NEW] package virtualbox-dkms 6.0.14-dfsg-1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10
Public bug reported: upgrading from Ubuntu 16.04 to 16.10 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: virtualbox-dkms 6.0.14-dfsg-1 ProcVersionSignature: Ubuntu 5.3.0-20.21-generic 5.3.7 Uname: Linux 5.3.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 Date: Wed Oct 30 21:51:58 2019 ErrorMessage: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-07-27 (95 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: virtualbox Title: package virtualbox-dkms 6.0.14-dfsg-1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850718 Title: package virtualbox-dkms 6.0.14-dfsg-1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1850718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850125] Re: Can't start gnome/xorg -- says that the xsettings service is already running.
Thank you for your bug report. Could you add your journalctl log from a boot with the issue? ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Incomplete ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850125 Title: Can't start gnome/xorg -- says that the xsettings service is already running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1850125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
Given that my patch fixes the issue for me means: This works: grub_load_and_start_image(boot_image); grub_file_close (file); grub_loader_set (grub_chainloader_boot, grub_chainloader_unload, 0); return 0; This doesn't: grub_file_close (file); grub_loader_set (grub_secureboot_chainloader_boot, grub_secureboot_chainloader_unload, 0); return 0; I'm not that familiar with C but may be it has something to do with calling grub_file_close() before grub_loader_set()? I mean, hd0 is closed, will it work to call grub_load_and_start_image() later? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848784] Re: Crash in Qt 5.12.2
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848784 Title: Crash in Qt 5.12.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850046] Re: gedit freezes when opening PHP file with long lines
Could you test if the update on the other bug mentioned fixes the issue? ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850046 Title: gedit freezes when opening PHP file with long lines To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1850046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850046] Re: gedit freezes when opening PHP file with long lines
closing the gedit part since it's already reported as mentioned in the previous comments ** Changed in: gedit (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850046 Title: gedit freezes when opening PHP file with long lines To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1850046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184510] A change has been merged
Reviewed: https://reviews.mahara.org/10535 Committed: https://git.mahara.org/mahara/mahara/commit/7d12953a3a4a669a9dd0a62193fc3d574ba2b0f8 Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:19.10_STABLE commit 7d12953a3a4a669a9dd0a62193fc3d574ba2b0f8 Author: Evonne Date: Wed Oct 30 15:46:20 2019 +1300 Bug 184510 Small theme changes - gridstack left/right alignment fix while old layouts need to work - loading messages on dark background - view footer markup - list-group borders behatnotneeded Change-Id: Ib4b9a2b33ad3f18e8fa23a05545bb25bb2eb5d1d (cherry picked from commit e76f515b85be75fc04b55b938cdcab262a1fb38e) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/184510 Title: Bug 81910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/184510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184510] A change has been merged
Reviewed: https://reviews.mahara.org/10510 Committed: https://git.mahara.org/mahara/mahara/commit/e76f515b85be75fc04b55b938cdcab262a1fb38e Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:master commit e76f515b85be75fc04b55b938cdcab262a1fb38e Author: Evonne Date: Wed Oct 30 15:46:20 2019 +1300 Bug 184510 Small theme changes - gridstack left/right alignment fix while old layouts need to work - loading messages on dark background - view footer markup - list-group borders behatnotneeded Change-Id: Ib4b9a2b33ad3f18e8fa23a05545bb25bb2eb5d1d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/184510 Title: Bug 81910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/184510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184510] A patch has been submitted for review
Patch for "19.10_STABLE" branch: https://reviews.mahara.org/10535 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/184510 Title: Bug 81910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/184510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
This patch may be wrong but it fixes the issue for me. I already tested
it on my actual system (not just VirtualBox).
Now to your comments:
1. shim is not dependency of grub2. My 18.04, 18.10 and 19.04 installations had
only these packages and no shim:
grub-common, grub2-common, grub-efi-amd64, grub-efi-amd64-bin
Shim is not required on non-SB systems. Ubuntu supported direct usage of
grub without shim since forever and I see no reason to drop such
support. If you're sure shim is required then make it dependency of the
grub.
I didn't use boot-repair. I simply updated from 19.04 (without shim) to
19.10 (still without shim) which broke chainload.
2. You're right. While I don't exactly understand what grub_loader_set() does:
grub_loader_set (grub_secureboot_chainloader_boot,
grub_secureboot_chainloader_unload, 0);
but I took a look at grub_secureboot_chainloader_boot() and it indeed
gets 0 from handle_image()/read_header() and expected to call
grub_load_and_start_image(). However on my system the latest log record
comes from:
grub_dprintf ("chain", "Secure Boot is not enabled\n");
and then I guess from grub_load_and_start_image() it immediately goes
back to the menu.
This is the last page of logs with "debug=all" –
https://i.imgur.com/PFRSqg8.png
This screenshot has been taken using the latest grub2 from eoan without
any custom patches. If you want to see full video of boot process send
me a message using https://launchpad.net/~xeron-oskom/+contactuser.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845289
Title:
Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
i got an email about released. I also notice on here that a fix has been released. I don't see it as an update via software updates. How to I get the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849002] Re: bionic/linux-bluefield: 5.0.0-1004.13 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850574 packages: main: linux-bluefield meta: linux-meta-bluefield - phase: Packaging - phase-changed: Wednesday, 23. October 2019 08:30 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 30. October 2019 20:41 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849002 Title: bionic/linux-bluefield: 5.0.0-1004.13 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850485] Re: bionic/linux-hwe-edge: 5.3.0-21.22~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: main: linux-hwe-edge meta: linux-meta-hwe-edge signed: linux-signed-hwe-edge phase: Promote to Proposed phase-changed: Wednesday, 30. October 2019 17:16 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850485 Title: bionic/linux-hwe-edge: 5.3.0-21.22~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159031] Re: computer freezes when sshfs blocks waiting for connection
I disconnected from Wifi while an sshfs was active, and the /mnt directory was inaccessible afterwords. "ls /mnt" hung. "sudo umount /mnt/mysshfs" hung. "sudo umount -f /mnt/mysshfs" said "target was busy". "sudo umount -l /mnt/mysshfs" worked. Though that's not a nice solution because the file is still busy somewhere, but it worked for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/159031 Title: computer freezes when sshfs blocks waiting for connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/+bug/159031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580274] Re: Firefox should allow you to set New Tab to certain fixed values
Launchpad has imported 5 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1271727. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-05-10T17:51:11+00:00 U552789 wrote: >From Firefox 41 one is now unable in about:config to set the New Tab to a custom URL, and as far as I remember this is due to certain security issues with New Tab hijacking. So before one could set it to any URL, now one cannot set it to anything, but I think that something in between would be better, so I propose that one is allowed to set the New Tab URL in about:config to certain fixed values. Probably it would allow you to set it to: - about:newtab (Default New Tab page) - about:blank (Blank page) - about:home (Default Firefox home page) But nothing else so there shouldn't be any security issues around New Tab hijacking. Another thing to add, if this does get implemented then I think that the settings should also be accessible through about:preferences and not just about:config as these are essential settings like the home page and will be useful for all users and not just advanced ones. I originally filed a report on this issue here but thought I should also do so upstream: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274 Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274/comments/1 On 2017-09-10T22:00:16+00:00 Alex Mayorga wrote: [Tracking Requested - why for this release]: ¡Hola Nikita! I ended up here while investigating on https://support.mozilla.org/questions/1174370 https://addons.mozilla.org/firefox/addon/newtaburl/ apparently provided a fix but per the most recent comments and compatibility details it has stopped working since around Firefox 41. Hope this helps. Confirming per the SuMo question. ¡Gracias! Alex Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274/comments/2 On 2018-07-21T17:23:15+00:00 U552789 wrote: This is now allowed in about:preferences#home. So as this feature has now been implemented please mark as "FIXED". Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274/comments/3 On 2018-07-21T17:24:17+00:00 U552789 wrote: Whoops! Didn't mean to close the bug! It would really be better if it was given proper status. Rather than what a standard user can give it. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274/comments/4 On 2019-10-29T21:17:20+00:00 Jdavis-5 wrote: Hello! This bug has been closed due to inactivity and/or the potential for this bug to no longer be an issue with the new Discovery Stream-powered New Tab experience. Please help us triage by reopening if this issue still persists and should be addressed. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274/comments/6 ** Changed in: firefox Status: Confirmed => Won't Fix ** Changed in: firefox Importance: Wishlist => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580274 Title: Firefox should allow you to set New Tab to certain fixed values To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1580274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
> Hello - Does the recent switch from New -> Triaged for charm-cinder and charm-nova-compute mean that someone was able to determine that the charms are to blame and perhaps not the kernel? Sadly not; I'm just knocking them off new; the alternative is incomplete which means they'll time out after 60 days. As it is confirmed in the kernel, it may well be invalid for both charms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842751 Title: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1842751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846821] Re: Qt print dialog has wrong default page size
I can confirm that the patch fixes the problem, i.e. Qt print dialog now defaults to page size as set in System Settings Printers applet. To apply the fix, it was enough to add the PPA repository, upgrade libqt5printsupport5 package, and then close and reopen applications that were affected by the bug. Thank you very much for your work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846821 Title: Qt print dialog has wrong default page size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848768] Re: 19.10: cache is empty. You need to run "apt-file update" first.
Thanks! I was hit by this bug too (I filed 1849587, marked as a dup) and can report that after an update, apt-file is now working again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848768 Title: 19.10: cache is empty. You need to run "apt-file update" first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-file/+bug/1848768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843487] Re: UIO: mutex used in interrupt handler causes crash
@Tom- Ah yes, you'll need the headers packages too, in order to build your own modules. OK, I've now added the two "linux-headers-*" packages to https://kernel.ubuntu.com/~kamal/lp1843487/ ... I believe you'll have to install the pair together. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843487 Title: UIO: mutex used in interrupt handler causes crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850480] Re: eoan/linux-azure: 5.3.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Tuesday, 29. October 2019 23:36 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 30. October 2019 20:28 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait replaces: bug 1849058 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850480 Title: eoan/linux-azure: 5.3.0-1006.6 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850477] Re: eoan/linux-aws: 5.3.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Packaging - phase-changed: Tuesday, 29. October 2019 23:21 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 30. October 2019 20:27 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building replaces: bug 1849057 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850477 Title: eoan/linux-aws: 5.3.0-1006.6 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850481] Re: eoan/linux-gcp: 5.3.0-1007.7 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Tuesday, 29. October 2019 23:15 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + prepare-package: Stalled -- package tag not yet published + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait replaces: bug 1849060 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850481 Title: eoan/linux-gcp: 5.3.0-1007.7 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847772] Re: E-mail folder names are not localized in thunderbird 68
** Changed in: thunderbird (Ubuntu) Importance: Undecided => Low ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847772 Title: E-mail folder names are not localized in thunderbird 68 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850664] Re: setting-window size overflow
I see the same, and my understanding is that it's intentional when the screen resolution is not high enough to show the whole window. That's why there is a scrollbar, so you can scroll to the menu items at the bottom of the list. Is there anything the current design prevents you from accessing? ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850664 Title: setting-window size overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1850664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850664] Re: setting-window size overflow
Thank you for your bug report. It's a consequence of the number of panels and the way they are categorized, sort of known but also could be considered as a design issue. It would be nice if they would fit on the screen even for small vertical resolutions though ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850664 Title: setting-window size overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1850664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850159] Re: dhclient can't obtain IPv6 addr
closing since the description isn't clear, feel free to reopen if the requested screenshot showing the problem is added though ** Changed in: network-manager (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850159 Title: dhclient can't obtain IPv6 addr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850696] Re: Regression: cannot close notifications
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1803 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1803 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1803 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850696 Title: Regression: cannot close notifications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1850696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850214] Re: gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from g_settings_schema_get_value() from g_settings_schema_key_init() from g_settings_get_value() from g_settings_get
One thing we discussed with Marco a bit earlier is that it would be nice of apport included some flag if the gsettings cache was coming from /usr/local which is a common cause for reports like this one -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850214 Title: gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from g_settings_schema_get_value() from g_settings_schema_key_init() from g_settings_get_value() from g_settings_get_boolean() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844805] Autopkgtest regression report (ubuntu-release-upgrader/1:19.10.15.1)
All autopkgtests for the newly accepted ubuntu-release-upgrader (1:19.10.15.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: ubuntu-release-upgrader/1:19.10.15.1 (i386) 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/eoan/update_excuses.html#ubuntu-release-upgrader [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844805 Title: virtualbox, virtualbox-dkms, virtualbox-qt fail during upgrade from 19.04 to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1844805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850587] Re: bionic/linux-hwe: 5.0.0-34.36~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850574 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe - phase: Promote to Proposed - phase-changed: Wednesday, 30. October 2019 17:06 UTC + phase: Testing + phase-changed: Wednesday, 30. October 2019 20:02 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850587 Title: bionic/linux-hwe: 5.0.0-34.36~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850486] Re: eoan/linux: 5.3.0-21.22 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 30. October 2019 18:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1850485 eoan/linux-aws: bug 1849057, bug 1850477 - eoan/linux-azure: bug 1849058, bug 1850480 - eoan/linux-gcp: bug 1850481, bug 1849060 + eoan/linux-azure: bug 1850480, bug 1849058 + eoan/linux-gcp: bug 1849060, bug 1850481 eoan/linux-kvm: bug 1850482 eoan/linux-oracle: bug 1850483 eoan/linux-raspi2: bug 1850475 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850486 Title: eoan/linux: 5.3.0-21.22 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848994] Re: bionic/linux-gke-5.0: 5.0.0-1024.24~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1848995 packages: main: linux-gke-5.0 meta: linux-meta-gke-5.0 signed: linux-signed-gke-5.0 phase: Testing phase-changed: Friday, 25. October 2019 12:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gke-5.0/gke-kernel: bug 1848993 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848994 Title: bionic/linux-gke-5.0: 5.0.0-1024.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848994] Re: bionic/linux-gke-5.0: 5.0.0-1024.24~18.04.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848994 Title: bionic/linux-gke-5.0: 5.0.0-1024.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850483] Re: eoan/linux-oracle: 5.3.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Promote to Proposed - phase-changed: Wednesday, 30. October 2019 15:09 UTC + phase: Testing + phase-changed: Wednesday, 30. October 2019 20:01 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850483 Title: eoan/linux-oracle: 5.3.0-1005.5 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848991] Re: bionic/linux-gcp-edge: 5.0.0-1024.24~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1848992 packages: meta: linux-meta-gcp-edge phase: Testing phase-changed: Thursday, 24. October 2019 18:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848991 Title: bionic/linux-gcp-edge: 5.0.0-1024.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848991] Re: bionic/linux-gcp-edge: 5.0.0-1024.24~18.04.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848991 Title: bionic/linux-gcp-edge: 5.0.0-1024.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848992] Re: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848992 Title: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769061] Re: Screen lock + Laptop lid close forces suspend
For me Ctrl-Alt-F1 and then Ctrl-Alt-F7 enables the screen but shows a message "This session is locked", which never goes away. But Ctrl-Alt-F1 and then Ctrl-Alt-F8 allows to unlock normally. This is a workaround #1. This happens on a Dell laptop (7490, built-in Intel Graphics). Maybe Dell physically disconnects the screen when lid is closed. Workaround #2: Default Lid Close action in xfce Power Manager is "Lock". If I change it to "Suspend", the problem goes away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769061 Title: Screen lock + Laptop lid close forces suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1769061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848998] Re: disco/linux-oracle: 5.0.0-1006.10 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848998 Title: disco/linux-oracle: 5.0.0-1006.10 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850708] [NEW] focal - net-tools is is deprecated (remove from recommends)
Public bug reported: (c)rafaeldtinoco@ubuntu-ha:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal (c)rafaeldtinoco@ubuntu-ha:~$ apt-cache rdepends net-tools | grep resource-a resource-agents ** Affects: resource-agents (Ubuntu) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Changed in: resource-agents (Ubuntu) Status: New => Confirmed ** Changed in: resource-agents (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: resource-agents (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850708 Title: focal - net-tools is is deprecated (remove from recommends) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1850708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848992] Re: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1848995 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 24. October 2019 14:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1848991 bionic/linux-gcp/gcp-kernel: bug 1848990 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848992 Title: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848998] Re: disco/linux-oracle: 5.0.0-1006.10 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850574 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 23. October 2019 09:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.0: bug 1848997 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848998 Title: disco/linux-oracle: 5.0.0-1006.10 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850707] [NEW] "Data source "u...@gmail.com" does not support OAuth 2.0 authentication" shown each time Evolution starts
Public bug reported: Running Ubuntu 19.10 Gnome fully patched. MY GMail account is added via Gnome Online Accounts, with just Mail, Contacts and Calendar selected. Then, when I launch Evolution. I see an error displayed each time stating "Data source "u...@gmail.com" does not support OAuth 2.0 authentication". I am not sure whether two-factor authentication matters, but I have tried disabling and re-enabling it and it has made no difference. I can duplicate this on two separate installations so I assume this problem could be widespread. Thanks Nick ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: evolution 3.34.1-2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 19:45:17 2019 InstallationDate: Installed on 2019-04-29 (184 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: evolution UpgradeStatus: Upgraded to eoan on 2019-10-19 (11 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-05-01T13:13:33.160866 ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850707 Title: "Data source "u...@gmail.com" does not support OAuth 2.0 authentication" shown each time Evolution starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1850707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848986] Re: bionic/linux-azure-edge: 5.0.0-1024.25 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848986 Title: bionic/linux-azure-edge: 5.0.0-1024.25 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848981] Re: disco/linux-raspi2: 5.0.0-1021.21 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848981 Title: disco/linux-raspi2: 5.0.0-1021.21 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848984] Re: disco/linux-aws: 5.0.0-1020.22 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848984 Title: disco/linux-aws: 5.0.0-1020.22 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848991] Re: bionic/linux-gcp-edge: 5.0.0-1024.24~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848991 Title: bionic/linux-gcp-edge: 5.0.0-1024.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848995] Re: disco/linux-gcp: 5.0.0-1024.24 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848995 Title: disco/linux-gcp: 5.0.0-1024.24 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848983] Re: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848983 Title: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849057] Re: eoan/linux-aws: 5.3.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849057 Title: eoan/linux-aws: 5.3.0-1005.5 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848987] Re: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848987 Title: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850475] Re: eoan/linux-raspi2: 5.3.0-1010.11 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850475 Title: eoan/linux-raspi2: 5.3.0-1010.11 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848992] Re: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848992 Title: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849001] Re: bionic/linux-oem-osp1: 5.0.0-1026.29 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849001 Title: bionic/linux-oem-osp1: 5.0.0-1026.29 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850486] Re: eoan/linux: 5.3.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850486 Title: eoan/linux: 5.3.0-21.22 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848989] Re: disco/linux-azure: 5.0.0-1024.25 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848989 Title: disco/linux-azure: 5.0.0-1024.25 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848996] Re: disco/linux-kvm: 5.0.0-1021.22 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848996 Title: disco/linux-kvm: 5.0.0-1021.22 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848994] Re: bionic/linux-gke-5.0: 5.0.0-1024.24~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848994 Title: bionic/linux-gke-5.0: 5.0.0-1024.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848999] Re: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848999 Title: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848998] Re: disco/linux-oracle: 5.0.0-1006.10 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848998 Title: disco/linux-oracle: 5.0.0-1006.10 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850482] Re: eoan/linux-kvm: 5.3.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850482 Title: eoan/linux-kvm: 5.3.0-1006.6 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849060] Re: eoan/linux-gcp: 5.3.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849060 Title: eoan/linux-gcp: 5.3.0-1006.6 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849058] Re: eoan/linux-azure: 5.3.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849058 Title: eoan/linux-azure: 5.3.0-1005.5 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850574] Re: disco/linux: 5.0.0-34.36 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850574 Title: disco/linux: 5.0.0-34.36 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850673] Re: autofill and password sync does not work for snap version
*** This bug is a duplicate of bug 1849160 *** https://bugs.launchpad.net/bugs/1849160 This is bug #1849160, an unfortunate regression caused by the deb->snap migration. A fix is being SRUed, in the meantime the workaround is to run the following command in a terminal, then close and re-open chromium: snap connect chromium:password-manager-service ** This bug has been marked a duplicate of bug 1849160 after deb->snap transition, chromium no longer sees local password store -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850673 Title: autofill and password sync does not work for snap version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635944] Re: XFig only looks for system-wide app-defaults
@florian42: Where does your xfig 3.2.7a come from? Is it from the Ubuntu/Debian package or is it self compiled? If the latter, you may have to fix your configure options. If the former: what package version are you talking about exactly? Are you really sure, that it comes with the Fig file in /usr/local/share/X11/app-defaults instead of /etc/X11 /app-defaults? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635944 Title: XFig only looks for system-wide app-defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfig/+bug/1635944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850563] Re: [snap] Google Search via Microphone says No Internet Connection
The only workaround I'm aware of is to use chrome packaged by Google. ** Changed in: chromium-browser (Ubuntu) Assignee: Olivier Tilloy (osomon) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850563 Title: [snap] Google Search via Microphone says No Internet Connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849753] Re: AppArmor profile prohibits classic snap from inheriting file descriptors
Since the issue is that an fd is opened by the first app running in one
profile while transitioning to the snap-confine profile, there is an
option that would 'work'.
As a POC, I installed the hello-world snap and also created a test-
classic snap (just hello-world renamed with 'confinement: classic' and
installed with --classic --dangerous). Do nothing else, I then try to
reproduce the issue:
$ test-classic.sh
bash-5.0$ exec 3<> /run/user/$(id -u)/test.fd
bash-5.0$ test-classic.env > /dev/null
bash-5.0$
I see in the logs the familiar denial:
Oct 30 13:53:24 foo kernel: audit: type=1400 audit(1572461604.648:3444):
apparmor="DENIED" operation="file_inherit"
profile="/snap/core/8039/usr/lib/snapd/snap-confine"
name="/run/user/1000/test.fd" pid=24957 comm="snap-confine"
requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
I then updated /var/lib/snapd/apparmor/profiles/snap.test-classic.sh to
have:
/usr/lib/snapd/snap-confine ix,
/snap/core/8039/usr/lib/snapd/snap-confine ix,
^mount-namespace-capture-helper (complain) {
file,
unix,
signal,
}
and tried again:
$ test-classic.sh
bash-5.0$ exec 3<> /run/user/$(id -u)/test.fd
bash-5.0$ test-classic.env > /dev/null
bash-5.0$
and I observe in the logs there is no file_inherit denial.
This 'works' because the profile that snap-confine is running under is
the same as the classic snap and therefore has all the same accesses
that the snap does (I could've chosen the special 'unconfined', but
snap-confine will fail to run in that case).
Interestingly, if I run 'hello-world' from the classic snap:
$ test-classic.sh
bash-5.0$ exec 3<> /run/user/$(id -u)/test.fd
bash-5.0$ test-classic.env > /dev/null
bash-5.0$ hello-world.sh
bash-4.3$ cat /proc/self/fd/3
cat: /proc/self/fd/3: Permission denied
hello-world correctly gets the denials (first is inherit, 2nd
/apparmor/.null is how apparmor handles the access to the failed inherit
fd):
Oct 30 14:20:44 foo kernel: audit: type=1400 audit(1572463244.359:3449):
apparmor="DENIED" operation="file_inherit" profile="snap.hello-world.sh"
name="/run/user/1000/test.fd" pid=26175 comm="snap-exec" requested_mask="wr"
denied_mask="wr" fsuid=1000 ouid=1000
Oct 30 14:21:56 foo kernel: audit: type=1400 audit(1572463316.344:3451):
apparmor="DENIED" operation="open" profile="snap.hello-world.sh"
name="/apparmor/.null" pid=26244 comm="cat" requested_mask="r" denied_mask="r"
fsuid=1000 ouid=0
Now, I say 'works' because I don't care for how the snap-confine policy
is circumvented in the POC since a classic snap could then try to
exploit bugs in the setuid snap-confine. While one could argue that a
classic snap already has root on the system, many people will install
classic snaps that run as the user (ie, no daemons) and feel a bit
safer, but with the POC policy the snap could, running as the user, try
to exploit bugs in snap-confine to gain privileges.
There is possibly an acceptable way, but it would need to be
investigated to verify it works and for acceptable safety:
1. adjust the classic policy to use:
/usr/lib/snapd/snap-confine ix,
/snap/$SNAP_WITH_SNAPD/$SNAP_WITH_SNAPD_REVISION/usr/lib/snapd/snap-confine
ix,
2. adjust snap-confine to:
if apparmor enabled:
if unconfined:
if !change_profile(snap_confine_profile)
die("snap-confine has elevated permissions and is not confined but
should be"
The idea is, adjust the classic policy to transition to the unconfined
profile when calling snap-confine (the $SNAP_WITH_SNAPD* stuff is to
avoid conflicting x modifiers with the parser). This should allow snap-
confine to have the open fds without file_inherit denials. Then snap-
confine tries as early as possible to transition itself to the snap-
confine profile, dying if it can't. The kernel may revalidate the fds at
change_profile (needs verifying) and change_profile is not as strong as
fork/exec profile change, but might be acceptable for this case. snap-
confine would be susceptible to LD_PRELOAD issues, but because it is
setuid, secure_exec is in effect and areas in the filesystem that the
binary would honor with LD_PRELOAD are writable only by root (and if
someone runs the classic snap under sudo to circumvent this, they can
simply change the host however he/she desires).
An alternative without modifying snap-confine would be to have two snap-
confine profiles, one for strict and one for classic, and adjust the
classic template to transition to the classic snap-confine template
which has rules allowing 'rw' access to files and 'unix' for sockets.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849753
Title:
AppArmor profile prohibits classic snap from inheriting file
descriptors
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1849753/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
No; this patch is wrong. For starters, you really ought to have shim installed, and that is the primary cause for such failures -- somehow your install is incomplete, and shim was removed either because the package was removed, or through the use of boot-repair (IIRC it replaces shim with using grub directly, which is not supported). Then, the code for the chainloader already is supposed to handle Secure Boot being off -- if it's disabled, the linuxefi_secure_validate() function sees that and returns 1 (image is deemed valid, since SB is disabled). Then we run grub_secureboot_chainloader_boot(), which will execute handle_image(), which should immediately check read_header() and find out, again, whether Secure Boot is enabled and/or if shim is available; returning with whatever status was retrieved reading the header for the binary that is to be chainloaded. I'd expect that if Secure Boot is not enabled, you would again have a return code of 0 there, and move on to using the normal chainload behavior of load_image and start_image. Please, if you're running into this issue, try stopping at the grub menu, and edit the chainload entry to add: set debug="chain" At the top, taking a screenshot or video of the boot process that you can then attach here. We really need to know if this is caused by one unusually built binary, or what precisely is going on before making any patches to GRUB. ** Changed in: grub2 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638163] Re: Xfig fails to generate EPS preview
** Changed in: xfig (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638163 Title: Xfig fails to generate EPS preview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfig/+bug/1638163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635945] Re: XFig seems to ignore .xfig file
** Changed in: xfig (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635945 Title: XFig seems to ignore .xfig file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfig/+bug/1635945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849753] Re: AppArmor profile prohibits classic snap from inheriting file descriptors
" 1. adjust the classic policy to use: /usr/lib/snapd/snap-confine ix, /snap/$SNAP_WITH_SNAPD/$SNAP_WITH_SNAPD_REVISION/usr/lib/snapd/snap-confine ix, " This should have been: 1. adjust the classic policy to use: /usr/lib/snapd/snap-confine px -> unconfined, /snap/$SNAP_WITH_SNAPD/$SNAP_WITH_SNAPD_REVISION/usr/lib/snapd/snap-confine px -> unconfined, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849753 Title: AppArmor profile prohibits classic snap from inheriting file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1849753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802292] Re: xfig: interpolated spline draws polyline instead
** Changed in: xfig (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802292 Title: xfig: interpolated spline draws polyline instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfig/+bug/1802292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850704] Re: networkd doesn't set MTUBytes if interface is already up
** Bug watch added: github.com/systemd/systemd/issues #9254 https://github.com/systemd/systemd/issues/9254 ** Also affects: systemd via https://github.com/systemd/systemd/issues/9254 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850704 Title: networkd doesn't set MTUBytes if interface is already up To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1850704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850702] [NEW] No sound output with headphones
Public bug reported: I can't get sound of my laptop (Samsung Notebook 7 Force) through the headphone jack. The speakers work fine. When I plug a headphone, I can hear the sound being played very faintly. If I bump the volume to the maximum, that is. The sound is very distorted, like a buzz effect being applied over it. I noticed that if I delete /.config/pulse the distortion goes away, but the sound remains very low. After some time, the buzzing effect comes back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Oct 30 16:03:41 2019 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa-driver amd64 eoan ** Attachment added: "alsa-info.txt" https://bugs.launchpad.net/bugs/1850702/+attachment/5301496/+files/alsa-info.txt ** Package changed: ubuntu-release-upgrader (Ubuntu) => alsa-driver (Ubuntu) ** Description changed: I can't get sound of my laptop (Samsung Notebook 7 Force) through the headphone jack. The speakers work fine. When I plug a headphone, I can hear the sound being played very faintly. If I bump the volume to the maximum, that is. The sound is very distorted, like a buzz effect being applied over it. I noticed that if I delete /.config/pulse the distortion goes away, but - the sound remains very low. + the sound remains very low. After some time, the buzzing effect comes + back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Oct 30 16:03:41 2019 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850702 Title: No sound output with headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850698] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850698 Title: thinkpad x1 carbon 6th gen disconnect from dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850704] [NEW] networkd doesn't set MTUBytes if interface is already up
Public bug reported: [impact] if a networkd .network file specifies a [Link] section with MTUBytes=XXX set, networkd will only apply that mtu if the interface is down when networkd starts; if the interface is already up, the mtu won't be applied. [test case] on a bionic system, create a .network file like: [Match] Name=ens8 [Link] MTUBytes= then, reboot. The interface should be set correctly with that mtu: $ ip l show ens8 3: ens8: mtu qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff now, manually change the interface back to 1500 mtu, and restart networkd, then recheck the mtu: $ ip l show ens8 3: ens8: mtu qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff $ sudo ip l set mtu 1500 dev ens8 $ ip l show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff $ sudo systemctl restart systemd-networkd $ ip l show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff [regression potential] low, but any regression would likely involve failure to correctly set the configured mtu. this is needed only in bionic, it's fixed in disco and later already. ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Bionic) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850704 Title: networkd doesn't set MTUBytes if interface is already up To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1850704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848938] Re: installer crashed while installing on my dell insperion 3521
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubiquity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848938 Title: installer crashed while installing on my dell insperion 3521 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850699] Re: Please remove net-tools from bind9 Depends (replaced by iproute2)
** Changed in: bind9 (Ubuntu) Status: New => Triaged ** Changed in: bind9 (Ubuntu) Importance: Undecided => High ** Changed in: bind9 (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1850699 Title: Please remove net-tools from bind9 Depends (replaced by iproute2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1850699/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
** Changed in: network-manager Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional L2TP VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850699] Re: Please remove net-tools from bind9 Depends (replaced by iproute2)
** Changed in: bind9 (Ubuntu) Status: New => Triaged ** Changed in: bind9 (Ubuntu) Importance: Undecided => High ** Changed in: bind9 (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850699 Title: Please remove net-tools from bind9 Depends (replaced by iproute2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1850699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271487] Re: terminator need to highlight search string
C'mon, it's been 11 years. +11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/271487 Title: terminator need to highlight search string To manage notifications about this bug go to: https://bugs.launchpad.net/terminator/+bug/271487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
** Description changed: [Impact] When enabling ESM on precise, then upgrading that to current trusty, and from there to the proposed new trusty client (see #1832757), ESM gets disabled. This was found when executing test case (5) in the original SRU bug #1832757. The reason is that d/postinst, when dealing with this upgrade path, was conditioning a file rename on the package upgrade coming from version 1, which is the precise one. The fix is to drop that conditional, since the filename we intend to rename is the precise one (it has "precise" in its name) and there is no need to check for the version. [Test Case] lxc launch ubuntu-daily:precise p1 lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS - # confirm esm is enabled and working by downloading a package - lxc exec p1 -- apt-get install -d python-jinja2 - lxc exec p1 apt-get clean + # confirm esm is enabled and shows a positive pinning value + lxc exec p1 apt-cache policy|grep esm # ssh into p1 and call do-release-upgrade (doesn't work via lxc exec) ssh p1 - sudo do-release-upgrade - logout + sudo do-release-upgrade + logout lxc exec p1 -- bash -c "echo deb http://archive.ubuntu.com/ubuntu trusty-proposed main > /etc/apt/sources.list.d/trusty-proposed.list" lxc exec p1 apt-get update lxc exec p1 -- apt-get install -y ubuntu-advantage-tools lxc exec p1 apt-get update + # confirm esm is enabled and shows a positive pinning value lxc exec p1 apt-cache policy|grep esm - # try to download a trusty esm package, it should work - lxc exec p1 -- apt-get install -d python-jinja2 - lxc exec p1 apt-get clean [Regression Potential] Before we were pinning this upgrade path on having come from the exact precise package version, which is "1". Now we are dropping that requirement, and only checking if the precise esm sources.list file exists, then we rename it to the trusty name: ubuntu-esm-precise.list -> ubuntu-esm-infra-trusty.list do-release-upgrade will have renamed "precise" to "trusty" inside ubuntu-esm-precise.list. If someone is doing the upgrade manually via dist-upgrade, for example, then this person is expected to rename the precise repositories to trusty ones in all of /etc/apt/sources.list* [Other Info] As with the $1832757 SRU, this is being published only on trusty. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
** Description changed: [Impact] When enabling ESM on precise, then upgrading that to current trusty, and from there to the proposed new trusty client (see #1832757), ESM gets disabled. This was found when executing test case (5) in the original SRU bug #1832757. The reason is that d/postinst, when dealing with this upgrade path, was conditioning a file rename on the package upgrade coming from version 1, which is the precise one. The fix is to drop that conditional, since the filename we intend to rename is the precise one (it has "precise" in its name) and there is no need to check for the version. [Test Case] lxc launch ubuntu-daily:precise p1 lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS - # confirm esm is enabled and working by downloading a package - lxc exec p1 -- apt-get install -d python-jinja2 - lxc exec p1 apt-get clean + # confirm esm is enabled and shows a positive pinning value + lxc exec p1 apt-cache policy|grep esm # ssh into p1 and call do-release-upgrade (doesn't work via lxc exec) ssh p1 - sudo do-release-upgrade - logout + sudo do-release-upgrade + logout lxc exec p1 -- bash -c "echo deb http://archive.ubuntu.com/ubuntu trusty-proposed main > /etc/apt/sources.list.d/trusty-proposed.list" lxc exec p1 apt-get update lxc exec p1 -- apt-get install -y ubuntu-advantage-tools lxc exec p1 apt-get update + # confirm esm is enabled and shows a positive pinning value lxc exec p1 apt-cache policy|grep esm - # try to download a trusty esm package, it should work - lxc exec p1 -- apt-get install -d python-jinja2 - lxc exec p1 apt-get clean [Regression Potential] Before we were pinning this upgrade path on having come from the exact precise package version, which is "1". Now we are dropping that requirement, and only checking if the precise esm sources.list file exists, then we rename it to the trusty name: ubuntu-esm-precise.list -> ubuntu-esm-infra-trusty.list do-release-upgrade will have renamed "precise" to "trusty" inside ubuntu-esm-precise.list. If someone is doing the upgrade manually via dist-upgrade, for example, then this person is expected to rename the precise repositories to trusty ones in all of /etc/apt/sources.list* [Other Info] As with the $1832757 SRU, this is being published only on trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843487] Re: UIO: mutex used in interrupt handler causes crash
@Kamal thanks for the quick response. I tried the files you sent over but it looks like I need some additional packages in order to rebuild my kernel module for that kernel. I tried to tell modprobe to force load my module built against 4.15.0-66 and it would not load it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843487 Title: UIO: mutex used in interrupt handler causes crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
