[Bug 1876620] [NEW] Enable riscv64 build
Public bug reported: RISC-V EFI support is not yet in the Linux kernel (ca. 5.8: https://lkml.org/lkml/2020/4/20/1800), and while GRUB2 EFI Loader support needs to happen with the kernel (https://lists.gnu.org/archive/html/grub-devel/2020-04/msg00203.html), GRUB2 already has RISC-V EFI support. It can't currently boot anything, but it is a valid UEFI application and displays a pretty menu. Please see the attached debdiff. Of note: * grub2 requires efibootmgr and efivar. I've filed Debian bugs to enable riscv64 for them (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=959498 and https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=959499 respectively), but if this is actioned before those end up happening, it's a simple Architecture: update on each. * riscv-default-platform.patch: Upstreamed, allows `grub-install` to work without --platform. * riscv-relocation-offset.patch: Upstreamed, fixes "unaligned pointer" failure. * riscv-ubuntu-linuxefi.patch: Patches ubuntu-linuxefi.patch for riscv support; not sure if this should be integrated into ubuntu- linuxefi.patch. * Tested on qemu-system-riscv64 focal. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "grub2-riscv64.debdiff" https://bugs.launchpad.net/bugs/1876620/+attachment/5365841/+files/grub2-riscv64.debdiff ** Description changed: RISC-V EFI support is not yet in the Linux kernel (ca. 5.8: https://lkml.org/lkml/2020/4/20/1800), and while GRUB2 EFI Loader support needs to happen with the kernel (https://lists.gnu.org/archive/html/grub-devel/2020-04/msg00203.html), GRUB2 already has RISC-V EFI support. It can't currently boot anything, but it is a valid UEFI application and displays a pretty menu. Please see the attached debdiff. Of note: * grub2 requires efibootmgr and efivar. I've filed Debian bugs to enable riscv64 for them (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=959498 and https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=959499 respectively), but if this is actioned before those end up happening, it's a simple Architecture: update on each. * riscv-default-platform.patch: Upstreamed, allows `grub-install` to work without --platform. - * riscv-relocation-offset.patch: Upstreamed: fixes "unaligned pointer" + * riscv-relocation-offset.patch: Upstreamed, fixes "unaligned pointer" failure. * riscv-ubuntu-linuxefi.patch: Patches ubuntu-linuxefi.patch for riscv support; not sure if this should be integrated into linuxefi.patch. * Tested on qemu-system-riscv64 focal. ** Description changed: RISC-V EFI support is not yet in the Linux kernel (ca. 5.8: https://lkml.org/lkml/2020/4/20/1800), and while GRUB2 EFI Loader support needs to happen with the kernel (https://lists.gnu.org/archive/html/grub-devel/2020-04/msg00203.html), GRUB2 already has RISC-V EFI support. It can't currently boot anything, but it is a valid UEFI application and displays a pretty menu. Please see the attached debdiff. Of note: * grub2 requires efibootmgr and efivar. I've filed Debian bugs to enable riscv64 for them (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=959498 and https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=959499 respectively), but if this is actioned before those end up happening, it's a simple Architecture: update on each. * riscv-default-platform.patch: Upstreamed, allows `grub-install` to work without --platform. * riscv-relocation-offset.patch: Upstreamed, fixes "unaligned pointer" failure. * riscv-ubuntu-linuxefi.patch: Patches ubuntu-linuxefi.patch for riscv - support; not sure if this should be integrated into linuxefi.patch. + support; not sure if this should be integrated into ubuntu- + linuxefi.patch. * Tested on qemu-system-riscv64 focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876620 Title: Enable riscv64 build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872945] Re: risc-v doubles getting clobbered somehow
Sorry, I said 4.2-3ubuntu6 but meant 1:4.2-3ubuntu6~ppa5 from the PPA (which works). Sounds like Colin got 1:4.2-3ubuntu6 from the PPA; I will test 1:4.2-3ubuntu6 from -proposed to be sure. $ apt-cache policy qemu-system-misc qemu-system-misc: Installed: 1:4.2-3ubuntu6~ppa5 Candidate: 1:4.2-3ubuntu6~ppa5 Version table: *** 1:4.2-3ubuntu6~ppa5 500 500 http://ppa.launchpad.net/ci-train-ppa-service/4015/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2-3ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872945 Title: risc-v doubles getting clobbered somehow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872945] Re: risc-v doubles getting clobbered somehow
Yep, 1:4.2-3ubuntu6 from focal-proposed test case works 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/1872945 Title: risc-v doubles getting clobbered somehow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872945] Re: risc-v doubles getting clobbered somehow
Confirmed qemu 4.2-3ubuntu6 fixes the OpenSSH sshd hang on riscv64 guest. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872945 Title: risc-v doubles getting clobbered somehow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
I've bisected the problem down to commit
c35a4a858d0616e7817026d88f377c7201ad449a ("block: fix an integer
overflow in logical block size", upstream
ad6bf88a6c19a39fb3b0045d78ea880325dfcf15).
I don't know what the exact problem is with the commit, but seems to be
in the area of fs/block_dev.c set_init_blocksize() calling
bdev_logical_block_size() which the offending commit touches.
# bad: [a78d21bd8bb58c158f73108eb7d7402619fcae3d] UBUNTU: Ubuntu-4.15.0-91.92
# good: [d5b8ff45eabff3cb2232a2eea38a862edc647ab8] UBUNTU: Ubuntu-4.15.0-88.88
git bisect start 'Ubuntu-4.15.0-91.92' 'Ubuntu-4.15.0-88.88'
# bad: [c04c6d87ca3a7e2c8019e0a2349fcf1175ffcce0] KVM: PPC: Release all
hardware TCE tables attached to a group
git bisect bad c04c6d87ca3a7e2c8019e0a2349fcf1175ffcce0
# good: [9a6b3cea5792f94f03f579c668a60eb4ddd209f0] dt-bindings: reset: meson8b:
fix duplicate reset IDs
git bisect good 9a6b3cea5792f94f03f579c668a60eb4ddd209f0
# bad: [6783f1bf22bb55bcd2628d7cabeacc9c720971e6] ALSA: usb-audio: update quirk
for B&W PX to remove microphone
git bisect bad 6783f1bf22bb55bcd2628d7cabeacc9c720971e6
# skip: [c4099e7e88621e82a5b3a5b0a2e3d6d8eee4e8e0] ptp: free ptp device pin
descriptors properly
git bisect skip c4099e7e88621e82a5b3a5b0a2e3d6d8eee4e8e0
# bad: [3222d8b5d803ed733dba2da03b595cf90c871fe6] drm/nouveau/mmu: qualify vmm
during dtor
git bisect bad 3222d8b5d803ed733dba2da03b595cf90c871fe6
# skip: [3db4efba8dea644e54e339ac2e46b497aea93638] NFC: pn533: fix bulk-message
timeout
git bisect skip 3db4efba8dea644e54e339ac2e46b497aea93638
# skip: [211ff6ef5f2f19d86d35dcbb94d4b09ab7de00fc] batman-adv: Fix DAT
candidate selection on little endian systems
git bisect skip 211ff6ef5f2f19d86d35dcbb94d4b09ab7de00fc
# skip: [3cb4cbc154b57c2fb842fbacc6ea4bd625ce680f] perf hists: Fix variable
name's inconsistency in hists__for_each() macro
git bisect skip 3cb4cbc154b57c2fb842fbacc6ea4bd625ce680f
# good: [1d9d2aae71b2d1c18d7d69c4850ca57ebd1e6fc1] clk: Don't try to enable
critical clocks if prepare failed
git bisect good 1d9d2aae71b2d1c18d7d69c4850ca57ebd1e6fc1
# skip: [37f1c7c4bf8eaf03f0e07152f55e0dda97bd52e8] cfg80211: check for
set_wiphy_params
git bisect skip 37f1c7c4bf8eaf03f0e07152f55e0dda97bd52e8
# good: [43cdcecf3a1bd5fdf9cbce0f3908cdde789c7ffd] ALSA: seq: Fix racy access
for queue timer in proc read
git bisect good 43cdcecf3a1bd5fdf9cbce0f3908cdde789c7ffd
# bad: [7a10b28e6122e12323da46732fc345d476a21829] ARM: dts: am571x-idk: Fix
gpios property to have the correct gpio number
git bisect bad 7a10b28e6122e12323da46732fc345d476a21829
# good: [31e3c075719a3afe5ffd2b9b8e1f18e07255bd96] Fix built-in early-load
Intel microcode alignment
git bisect good 31e3c075719a3afe5ffd2b9b8e1f18e07255bd96
# bad: [c35a4a858d0616e7817026d88f377c7201ad449a] block: fix an integer
overflow in logical block size
git bisect bad c35a4a858d0616e7817026d88f377c7201ad449a
# first bad commit: [c35a4a858d0616e7817026d88f377c7201ad449a] block: fix an
integer overflow in logical block size
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
BTW, for future searchers, I've uploaded dmesg.202004081903 separately, and pasted the crash here: [ 194.36] bcache: bch_journal_replay() journal replay done, 3 keys in 6 entries, seq 23285862 [ 194.444622] bcache: register_cache() registered cache device sdb1 [ 194.448381] bcache: register_bdev() registered backing device md0 [ 194.602075] BUG: unable to handle kernel NULL pointer dereference at 0008 [ 194.602100] IP: create_empty_buffers+0x29/0xf0 [ 194.602110] PGD 0 P4D 0 [ 194.602121] Oops: [#1] SMP NOPTI [ 194.602137] Modules linked in: bcache ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter pps_ldisc aufs overlay cmac bnep bonding bridge stp llc arc4 snd_hda_codec_hdmi nls_iso8859_1 edac_mce_amd kvm_amd kvm irqbypass rtl8xxxu mac80211 btusb btrtl btbcm snd_hda_intel btintel snd_hda_codec bluetooth cfg80211 eeepc_wmi snd_hda_core asus_wmi joydev sparse_keymap snd_hwdep wmi_bmof input_leds snd_pcm ecdh_generic snd_timer snd soundcore ccp k10temp shpchp mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp libiscsi_tcp auth_rpcgss libiscsi nfs_acl scsi_transport_iscsi lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx [ 194.602323] xor raid6_pq libcrc32c hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nouveau crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc mxm_wmi video ttm drm_kms_helper aesni_intel syscopyarea sysfillrect igb sysimgblt aes_x86_64 fb_sys_fops crypto_simd glue_helper dca cryptd i2c_algo_bit drm i2c_piix4 ptp ahci nvme pps_core libahci nvme_core gpio_amdpt wmi gpio_generic [ 194.602406] CPU: 1 PID: 4403 Comm: bcache-register Not tainted 4.15.0-91-generic #92-Ubuntu [ 194.602425] Hardware name: System manufacturer System Product Name/PRIME X370-PRO, BIOS 4207 12/08/2018 [ 194.602447] RIP: 0010:create_empty_buffers+0x29/0xf0 [ 194.602459] RSP: 0018:a833cc37f7a8 EFLAGS: 00010246 [ 194.602471] RAX: RBX: f6227c3f4c00 RCX: 0013 [ 194.602487] RDX: RSI: 0008 RDI: f6227c3f4c00 [ 194.602503] RBP: a833cc37f7c0 R08: 0001 R09: dead00ff [ 194.602519] R10: 8976ca4f7aa0 R11: R12: [ 194.602535] R13: R14: R15: 0200 [ 194.602551] FS: 7f51c3bb2500() GS:89771ec4() knlGS: [ 194.602569] CS: 0010 DS: ES: CR0: 80050033 [ 194.602582] CR2: 0008 CR3: 000f24aea000 CR4: 003406e0 [ 194.602598] Call Trace: [ 194.602606] create_page_buffers+0x51/0x60 [ 194.602616] block_read_full_page+0x4e/0x370 [ 194.602626] ? set_init_blocksize+0x80/0x80 [ 194.602636] blkdev_readpage+0x18/0x20 [ 194.602646] do_read_cache_page+0x2a2/0x580 [ 194.602656] ? blkdev_writepages+0x40/0x40 [ 194.602667] ? update_load_avg+0x57f/0x6e0 [ 194.602676] read_cache_page+0x15/0x20 [ 194.602687] read_dev_sector+0x2d/0xd0 [ 194.602696] read_lba+0x130/0x220 [ 194.602704] ? efi_partition+0x11a/0x790 [ 194.602713] efi_partition+0x138/0x790 [ 194.602723] ? string+0x60/0x90 [ 194.602731] ? vsnprintf+0xfb/0x510 [ 194.602740] ? snprintf+0x45/0x70 [ 194.602748] ? is_gpt_valid.part.6+0x420/0x420 [ 194.602760] check_partition+0x130/0x230 [ 194.603304] ? check_partition+0x130/0x230 [ 194.603837] rescan_partitions+0xaa/0x350 [ 194.604372] bdev_disk_changed+0x53/0x60 [ 194.604895] __blkdev_get+0x34a/0x510 [ 194.605413] blkdev_get+0x129/0x320 [ 194.605930] ? wake_up_bit+0x42/0x50 [ 194.606445] ? unlock_new_inode+0x4c/0x80 [ 194.606947] ? bdget+0x108/0x120 [ 194.607432] device_add_disk+0x38b/0x490 [ 194.607909] ? bcache_dev_sectors_dirty_add+0xb0/0xb0 [bcache] [ 194.608373] bch_cached_dev_run.part.28+0x42/0x1a0 [bcache] [ 194.608821] ? wait_woken+0x80/0x80 [ 194.609258] bch_cached_dev_attach+0x3b5/0x4f0 [bcache] [ 194.609681] ? vprintk_func+0x47/0xc0 [ 194.610088] ? printk+0x52/0x6e [ 194.610479] register_bcache+0x864/0x1110 [bcache] [ 194.610861] ? register_bcache+0x864/0x1110 [bcache] [ 194.611227] kobj_attr_store+0x12/0x20 [ 194.611580] ? kobj_attr_store+0x12/0x20 [ 194.611925] sysfs_kf_write+0x3c/0x50 [ 194.612259] kernfs_fop_write+0x125/0x1a0 [ 194.612595] __vfs_write+0x1b/0x40 [ 194.612921] vfs_write+0xb1/0x1a0 [ 194.613245] SyS_write+0x5c/0xe0 [ 194.613565] do_syscall_64+0x73/0x130 [ 194.613886] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 194.614212] RIP: 0033:0x7f51c36b8154 [ 194.614530] RSP: 002b:7ffd27009a58 EFLAGS: 0246 ORIG_RAX: 0001 [ 194.614858] RAX: ffda RBX: 0009 RCX: 7f51c36b8154 [ 194.615183] RDX: 0009 RSI: 560160a77260 RDI: 0003 [ 194.615506] RBP: 560160a77260
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Here you go: https://www.finnie.org/stuff/lp1867916-crashdump.tar.xz (138MB) Some notes on the process: - Also blacklisted it87 (DKMS) so the running kernel wasn't "tainted" - Also disabled the relevant crypttab entry for this group - 768M produced "crashkernel reservation failed - No suitable area found" in dmesg, used 512M instead - Had to disable secure boot (https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869672 which you also appear to be working on, heh) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
I can confirm going from 4.15.0-88 to 4.15.0-91 on my bcache system
panics in the same way. Here's my layout:
-> sd{c,d,f,g,h}: each 4TB gpt, sd{c,d,f,g,h}1: each type linux_raid_member
--> md0: raid6, sd{c,d,f,g,h}1
--> sda: 512GB gpt, sda1: type bcache
---> bcache0: md0 + sda1
> whatadisk_crypt: LUKS on bcache0
-> LVM VG whatadisk: whatadisk_crypt
--> multiple LVs
There are also a handful of other disks (for example, nvme0n1 is the
encrypted boot disk), but the layout above is the only part which bcache
touches.
Happy to help with additional info or testing, please let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870850] Re: Multi-line paste broken between kitty and nano 4.8 [focal]
Thanks Benno. Yeah, I've tested that works (albeit with s,'\r',CR_CODE, on the - line since focal is currently 4.8). I've asked -release if it's possible to get a sync exception for 4.9.1-1 from sid since focal is past the freeze, rather than trying to SRU this (and e.g. LP: #1866820 crash); waiting to heard back about that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870850 Title: Multi-line paste broken between kitty and nano 4.8 [focal] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870850] Re: Multi-line paste broken between kitty and nano 4.8 [focal]
** Summary changed: - Multi-line paste broken between kitty ~0.15 and nano 8.4 [focal] + Multi-line paste broken between kitty and nano 4.8 [focal] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870850 Title: Multi-line paste broken between kitty and nano 4.8 [focal] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870850] [NEW] Multi-line paste broken between kitty ~0.15 and nano 8.4 [focal]
Public bug reported: Ubuntu 20.04 Focal beta (as of 2020-04-04) nano 4.8-1 What I expect to happen: multi-line paste into nano via kitty pastes multiple lines. What happens instead: pasted multi-line text is one line with no line breaks. There is a bit of a spat between the developers of kitty (gnome- terminal:kitty::screen:tmux, basically) and nano about how to do multi- line pasting. See e.g.: * https://savannah.gnu.org/bugs/?58010 * https://lists.gnu.org/archive/html/nano-devel/2020-03/msg5.html * https://github.com/kovidgoyal/kitty/issues/994 Without taking sides, the facts are: * With the current versions in focal (kitty 0.15.0 and nano 4.8), pasting multi-line will result in newlines being eaten. * nano 4.9 introduces a fix (commit 481529e8650d105c3280def764e4917af0cabb49) which brings the newline handling more in line with other terminal-aware programs (treating raw \n as line break). Peripherally, nano 4.8 introduced new bracketed paste mode support. This makes a read of the kitty github issue above harder, since the issue being reported here is about an incompatibility in bracketed paste mode between kitty and nano, not pre-bracketed ^J handling. ** Affects: nano (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870850 Title: Multi-line paste broken between kitty ~0.15 and nano 8.4 [focal] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580326] Re: Add raspi3 subarch
** Branch unlinked: lp:~fo0bar/livecd-rootfs/livecd-rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580326 Title: Add raspi3 subarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1580326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
