[Bug 1853305] Re: ZFS - Failed to mount /target
** Summary changed: - Crash on install, with ZFS enabled (running on Virtualbox 6.0.14) + ZFS - Failed to mount /target ** Changed in: ubiquity (Ubuntu) Importance: Undecided => Medium ** 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/1853305 Title: ZFS - Failed to mount /target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1853305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621890] Re: Missing /usr/lib/virtualbox/VBoxNetNAT - Internet access in "NAT network" mode dosn't work
I checked on Ubuntu 18.04 upgraded to 21/11/2019, that means virtualbox 5.2.32. It works perfect now. Problem solved! Virtual machines in NatNetwork mode accesing internet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621890 Title: Missing /usr/lib/virtualbox/VBoxNetNAT - Internet access in "NAT network" mode dosn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1621890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798813] Re: Internet access in "NAT network" mode doesn't work in Ubuntu LTS 16.04 and LTS 18.04
I checked on Ubuntu 18.04 upgraded to 21/11/2019, that means virtualbox 5.2.32. It works perfect now. Problem solved! Virtual machines with NatNetwork mode accesing internet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798813 Title: Internet access in "NAT network" mode doesn't work in Ubuntu LTS 16.04 and LTS 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1798813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852303] Re: xenial/linux-fips: 4.4.0-1026.31 -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: 1852306 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Promote to Proposed phase-changed: Friday, 22. November 2019 19:02 UTC reason: - promote-signing-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Stalled -- ready for review 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/1852303 Title: xenial/linux-fips: 4.4.0-1026.31 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701028] Re: Jacksum -h option missing source help_en.txt
** Changed in: jacksum (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701028 Title: Jacksum -h option missing source help_en.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jacksum/+bug/1701028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800952] Re: Kubuntu 18.04: Konqueror won't show man/info pages
This was broken for me in the latest bionic 18.04-3, with or without backports. A work around seems to be to switch konqueror's Default Web Browser Engine to the KHTML renderer in Settings::Configure Konqueror::General. That makes the bug this one: KDE Bugtracking System – Bug 377084. A partial fix for that bug was committed upstream in July, 2018, here: https://phabricator.kde.org/D13924 I think the KHTML engine may have issues if you use it for browsing around, including some security issues, so be warned that the work- around may be best when using konqueror for local tasks rather than as the main web browser. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800952 Title: Kubuntu 18.04: Konqueror won't show man/info pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konqueror/+bug/1800952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
Please ignore the #36, the boot.scr in the http://cdimage.ubuntu.com /ubuntu-server/eoan/daily-preinstalled/20191122/ has some problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853494] Re: Add back WITH_SSL build parameter
A background worker process is crashed. dmesg line: [110854.430928] traps: icinga2[17383] general protection ip:7f403c6f4edc sp:7f40365cfe40 error:0 in libpthread-2.23.so[7f403c6e8000+18000] icinga use newer libboost, i checked the libbost source, just some backport changes lines. We disable the mysql stuff -> no crash. We enable again -> crash. I recompile mysql with this WITH_SSL -> no crash. Here is some gdb lines: #0 0x7f9bc5c10edc in pthread_rwlock_unlock () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f9bbbaa158f in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #2 0x7f9bc564dfaf in rsa_get_blinding (rsa=rsa@entry=0x7f9b9c0123a0, local=local@entry=0x7f9bc0057f0c, ctx=ctx@entry=0x7f9b9413c700) at rsa_eay.c:307 #3 0x7f9bc564f180 in RSA_eay_private_encrypt (flen=, from=, to=0x7f9bb41d3e08 "\222.\\.\021#\203\237\341\211\006\371\243ݕ\321"..., rsa=0x7f9b9c0123a0, padding=1) at rsa_eay.c:405 I dont know, is there any other apps with crash. we didnt find yet, but not using other such an app. we temporally workaround: switch back to .27, and hold. ps: i'm going to vacation. cannot answer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853494 Title: Add back WITH_SSL build parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1853494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 900901]
Thanks for info, very helpful! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/900901 Title: Steam overlay does not work due to GCC-4.6 issues To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/900901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H
Could you tell us the detailed steps to install the desktop on the rpi4 board? Since we only released the server version, there is no desktop in the server version. And the detailed steps to reproduce this issue. Then we will setup the same environment to debug this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852035 Title: Cannot use full resolution (2560x1440) of Dell U2715H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849721] Re: Raydium Touchscreen on ThinkPad L390 does not work
Can you please try this kernel: https://people.canonical.com/~khfeng/lp1849721-4/ Which included this commit: commit 0c8432236dea20a95f68fa17989ea3f8af0186a5 Author: Aaron Ma Date: Thu Nov 14 03:12:47 2019 +0800 HID: i2c-hid: fix no irq after reset on raydium 3118 On some ThinkPad L390 some raydium 3118 touchscreen devices doesn't response any data after reset, but some does. Add this ID to no irq quirk, then don't wait for any response alike on these touchscreens. All kinds of raydium 3118 devices work fine. BugLink: https://bugs.launchpad.net/bugs/1849721 Signed-off-by: Aaron Ma Signed-off-by: Jiri Kosina -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849721 Title: Raydium Touchscreen on ThinkPad L390 does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853005] Re: Wifi drops out at large bandwidth usage
** Summary changed: - Wifi randomly drops out + Wifi drops out at large bandwidth usage ** Description changed: System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux - Problem: Wifi randomly drops out. For example, I had trouble downloading - a folder from a ssh server at uni. During the download, the wifi - stopped. In the log of journalctl --follow, I found many records of the - kernel complaining about an unknown pci event, which I think is related - to the wifi dropping out. The output of journalctl --follow during the - wifi drop outs is attached as the file log.txt. I deleted all entries - from Nautilus and plank.desktop. + Problem: Wifi drops out with large bandwidth usage. For example, I had + trouble downloading a folder from a ssh server at uni. During the + download, the wifi stopped. In the log of journalctl --follow, I found + many records of the kernel complaining about an unknown pci event, which + I think is related to the wifi dropping out. The output of journalctl + --follow during the wifi drop outs is attached as the file log.txt. I + deleted all entries from Nautilus and plank.desktop. Additional notes: simply turning the wifi on and off again re- establishes the connection, but obviously irritating if I need to download lots of files from a ssh server. Furthermore, my iPad has internet connection after my Linux laptop wifi drops out, so the problem is not the router/ISP. - Update: limiting the download speed allowed me to download from the ssh - server. scp -r -l 100 user@address:~/Documents/Textbooks ./ + Limiting the download speed allowed me to download from the ssh server. + scp -r -l 100 user@address:~/Documents/Textbooks ./ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-70-generic 4.15.0-70.79 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 14:31:06 2019 HibernationDevice: RESUME=UUID=9f8b6855-caac-4e96-91bd-b366050fd722 InstallationDate: Installed on 2017-02-26 (995 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-70-generic N/A linux-backports-modules-4.15.0-70-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-06 (407 days ago) dmi.bios.date: 05/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.12.0 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853005 Title: Wifi drops out at large bandwidth usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853679] [NEW] One package downloaded and installed without password two did not download or install
Public bug reported: Opened Discover for downloads and one package downloaded and installed but two others were not installed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: discover (not installed) ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: KDE Date: Fri Nov 22 22:45:05 2019 InstallationDate: Installed on 2017-11-23 (729 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: discover UpgradeStatus: Upgraded to bionic on 2018-04-28 (573 days ago) ** Affects: discover (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Patch added: "These two did not download and install" https://bugs.launchpad.net/bugs/1853679/+attachment/5307230/+files/bug112220192250.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853679 Title: One package downloaded and installed without password two did not download or install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/discover/+bug/1853679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H
USB issue with 4GB maxmem seems to be fixed. 2560x1440 resolution issue not fixed. Cannot run glxinfo to get video driver information (immediate crash) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852035 Title: Cannot use full resolution (2560x1440) of Dell U2715H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H
[ 20.005106] ieee80211 phy0: brcmf_cfg80211_scan: Connecting: status (3) [ 22.175638] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI infoframe [ 35.824432] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI infoframe [ 59.528346] v3d fec0.v3d: MMU error from client L2T (0) at 0x161000, pte invalid [ 60.542090] v3d fec0.v3d: [drm:v3d_reset [v3d]] *ERROR* Resetting GPU for hang. [ 60.549816] v3d fec0.v3d: [drm:v3d_reset [v3d]] *ERROR* V3D_ERR_STAT: 0x00001000 [ 60.558638] v3d fec0.v3d: MMU error from client L2T (0) at 0x9761000, pte invalid [ 61.598102] v3d fec0.v3d: [drm:v3d_reset [v3d]] *ERROR* Resetting GPU for hang. [ 61.605839] v3d fec0.v3d: [drm:v3d_reset [v3d]] *ERROR* V3D_ERR_STAT: 0x00001000 [ 61.614690] v3d fec0.v3d: MMU error from client L2T (0) at 0x9741000, pte invalid [ 62.654095] v3d fec0.v3d: [drm:v3d_reset [v3d]] *ERROR* Resetting GPU for hang. [ 62.661828] v3d fec0.v3d: [drm:v3d_reset [v3d]] *ERROR* V3D_ERR_STAT: 0x00001000 [ 84.609153] v3d fec0.v3d: MMU error from client L2T (0) at 0x54c1000, pte invalid [ 84.617009] kernel BUG at arch/arm64/kernel/traps.c:405! [ 84.622312] Internal error: Oops - BUG: 0 [#1] SMP [ 84.625779] [ cut here ] [ 84.625784] [ cut here ] [ 84.625787] kernel BUG at arch/arm64/kernel/traps.c:405! [ 84.627094] Modules linked in: bnep aufs overlay nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vc4 drm_kms_helper snd_soc_core snd_compress sn d_seq_dummy ac97_bus snd_pcm_dmaengine snd_seq_oss snd_usb_audio snd_hwdep snd_u sbmidi_lib snd_seq_midi snd_pcm_oss snd_seq_midi_event btsdio snd_mixer_oss bluetooth snd_rawmidi joydev input_leds snd_pcm ecdh_generic ecc snd_seq brcmfmac sn d_seq_device snd_timer brcmutil bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) vc_sm_cm a(CE) v4l2_common snd videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 videobuf2_common fb_sys_fops syscopyarea sysfillrect videodev sysimgblt mc rasp berrypi_hwmon spidev rpivid_mem uio_pdrv_genirq uio sch_fq_codel ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_reco v async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid broadcom bcm_phy_lib mdio_bcm_unimac v3d gpu_sched drm crct10dif_ce sdhci_iproc [ 84.627165] gpio_regulator [ 84.631701] kernel BUG at arch/arm64/kernel/traps.c:405! [ 84.636304] genet phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 84.745110] CPU: 0 PID: 296 Comm: v3d_render Tainted: G C E 5.3.0-1013-raspi2 #15-Ubuntu [ 84.754318] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT) [ 84.760141] pstate: 00400085 (nzcv daIf +PAN -UAO) [ 84.764926] pc : do_undefinstr+0x64/0x68 [ 84.768838] lr : do_undefinstr+0x38/0x68 [ 84.772748] sp : 10003900 [ 84.776052] x29: 10003900 x28: ad7cafd3 [ 84.781354] x27: 55e291a0a5b8 x26: 55e29173e400 [ 84.786655] x25: ad7cbf9a5400 x24: [ 84.791956] x23: 20400085 x22: 55e2905200b8 [ 84.797257] x21: 0100b000 x20: [ 84.802557] x19: 10003920 x18: 0010 [ 84.807858] x17: x16: 55e290ad1c54 [ 84.813158] x15: ad7cafd30510 x14: 6e6920657470202c [ 84.818459] x13: 3030303163343578 x12: 3020746120293028 [ 84.823759] x11: 2054324c20746e65 x10: 0040 [ 84.829060] x9 : 55e291a2e2b8 x8 : 55e291a2e2b0 [ 84.834361] x7 : x6 : 100038f8 [ 84.839662] x5 : 100038f8 x4 : 55e291b3f0f8 [ 84.844962] x3 : 55e291a13868 x2 : e2aa3a6fde979f00 [
[Bug 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H
Have instability with the 1013 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852035 Title: Cannot use full resolution (2560x1440) of Dell U2715H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H
[ 22.661761] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI infoframe [ 39.686565] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI infoframe [ 70.888208] v3d fec0.v3d: MMU error from client L2T (0) at 0x4f41000, pte invalid [ 70.898755] kernel BUG at arch/arm64/kernel/traps.c:405! [ 70.899951] [ cut here ] [ 70.899952] [ cut here ] [ 70.899955] kernel BUG at arch/arm64/kernel/traps.c:405! [ 70.899959] Internal error: Oops - BUG: 0 [#1] SMP [ 70.899962] Modules linked in: bnep aufs overlay nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vc4 drm_kms_helper snd_soc_core snd_compress snd_seq_dummy ac97_bus snd_usb_audio snd_pcm_dmaengine snd_seq_oss snd_hwdep snd_usbmidi_lib snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm_oss snd_mixer_oss joydev btsdio snd_seq input_leds snd_pcm bluetooth ecdh_generic ecc snd_seq_device brcmfmac snd_timer bcm2835_v4l2(CE) brcmutil bcm2835_mmal_vchiq(CE) snd vc_sm_cma(CE) v4l2_common cfg80211 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev raspberrypi_hwmon fb_sys_fops mc syscopyarea sysfillrect sysimgblt spidev rpivid_mem uio_pdrv_genirq uio sch_fq_codel ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid broadcom bcm_phy_lib mdio_bcm_unimac v3d gpu_sched drm crct10dif_ce sdhci_iproc [ 70.900047] genet gpio_regulator phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 70.900061] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C E 5.3.0-1013-raspi2 #15-Ubuntu [ 70.900063] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT) [ 70.900068] pstate: 00400085 (nzcv daIf +PAN -UAO) [ 70.900085] pc : do_undefinstr+0x64/0x68 [ 70.900087] lr : do_undefinstr+0x38/0x68 [ 70.900090] sp : 1001bda0 [ 70.900091] x29: 1001bda0 x28: d680fbe33b00 [ 70.900095] x27: 01088421d67a x26: 1001c000 [ 70.900098] x25: 10018000 x24: [ 70.900100] x23: a0400085 x22: 24b002b22da0 [ 70.900103] x21: 0100b000 x20: [ 70.900106] x19: 1001bdc0 x18: [ 70.900108] x17: x16: [ 70.900110] x15: x14: [ 70.900113] x13: x12: 0001 [ 70.900117] x11: 24b0030a5a20 x10: 0040 [ 70.900119] x9 : 24b00382e2b8 x8 : 24b00382e2b0 [ 70.900121] x7 : d680fb800df0 x6 : 1001bd98 [ 70.900124] x5 : 1001bd98 x4 : 24b00393f0f8 [ 70.900126] x3 : 24b003813868 x2 : 4b3415783f25da00 [ 70.900128] x1 : x0 : a0400085 [ 70.900131] Call trace: [ 70.900134] do_undefinstr+0x64/0x68 [ 70.900138] el1_undef+0x10/0xb4 [ 70.900143] arch_timer_handler_phys+0x30/0x50 [ 70.900146] handle_percpu_devid_irq+0x90/0x238 [ 70.900149] generic_handle_irq+0x34/0x50 [ 70.900152] __handle_domain_irq+0x6c/0xc0 [ 70.900154] gic_handle_irq+0x58/0xa8 [ 70.900156] el1_irq+0x108/0x200 [ 70.900159] arch_cpu_idle+0x3c/0x1c8 [ 70.900165] default_idle_call+0x24/0x48 [ 70.900168] do_idle+0x210/0x2a0 [ 70.900171] cpu_startup_entry+0x2c/0x30 [ 70.900175] secondary_start_kernel+0x154/0x1c8 [ 70.900182] Code: 9400422f f9400bf3 a8c27bfd d65f03c0 (d421) [ 70.900188] ---[ end trace 27ce0cd0769ab3f5 ]--- [ 70.900191] Kernel panic - not syncing: Fatal exception in interrupt [ 70.900194] SMP: stopping secondary CPUs [ 70.900197] [ cut here ] [ 70.900199] kernel BUG at arch/arm64/kernel/traps.c:405! [ 71.213329] kernel BUG at arch/arm64/kernel/traps.c:405! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852035 Title: Cannot use full resolution (2560x1440) of Dell U2715H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836440] Re: RTL8723BS wifi not working
Is secure boot enabled? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836440 Title: RTL8723BS wifi not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853676] [NEW] Regression: fontawesome in is freeipa font-awesome in ubuntu
Public bug reported: Notice the bug and fix mentioned in https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1772921 is, somehow 're-broken' in eoan. Possibly because of: https://pagure.io/freeipa/c/78652a52f083bac5238f9e0a6520e0e448dadabe The result is none of the directional glyphs appear in the freeipa UI. Renders freeipa's web-ui unusable. work-around until patch is released: ln -s /usr/share/fonts/truetype/font-awesome /usr/share/fonts/truetype/fontawesome ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: freeipa-server 4.8.1-2ubuntu1 [modified: usr/share/ipa/html/ca.crt usr/share/ipa/html/krb.con usr/share/ipa/html/krb5.ini usr/share/ipa/html/krbrealm.con] ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Nov 22 22:05:14 2019 InstallationDate: Installed on 2019-11-01 (21 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: freeipa UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.ipa-dnskeysyncd: [modified] mtime.conffile..etc.default.ipa-dnskeysyncd: 2019-11-21T23:18:49.543399 ** Affects: freeipa (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/1853676 Title: Regression: fontawesome in is freeipa font-awesome in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1853676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837580] Re: memlock is not set
This is currently an issue in 19.10's systemd (version 242). By default,
unless services are configured to set LimitMEMLOCK, they will have 64k
as their memlock limit (though oddly, systemd bumped its own memlock
limit higher than previous versions have used). The only processes not
affected are those that increase their own memlock rlimits at runtime,
such as `systemd --user`.
```
# for pid in $(ps --ppid 1 | awk 'NR!=1 {print $1}'); do echo -n "${pid}: ";
cat "/proc/${pid}/limits" | grep locked ; done
400: Max locked memory 6553665536bytes
480: Max locked memory 6553665536bytes
514: Max locked memory 6553665536bytes
559: Max locked memory 6553665536bytes
561: Max locked memory 6553665536bytes
596: Max locked memory 6553665536bytes
657: Max locked memory 6553665536bytes
658: Max locked memory 6553665536bytes
659: Max locked memory 6553665536bytes
661: Max locked memory 6553665536bytes
662: Max locked memory 6553665536bytes
665: Max locked memory 6553665536bytes
681: Max locked memory 6553665536bytes
685: Max locked memory 6553665536bytes
688: Max locked memory 6553665536bytes
704: Max locked memory 6553665536bytes
710: Max locked memory 6553665536bytes
711: Max locked memory 6553665536bytes
732: Max locked memory 6553665536bytes
939: Max locked memory 6553665536bytes
6673: Max locked memory 67108864 67108864 bytes
7310: Max locked memory 6553665536bytes
# ps aux | grep 6673
root 6673 0.0 0.8 18132 8348 ?Ss 00:07 0:00
/lib/systemd/systemd --user
root 10442 0.0 0.0 8020 864 pts/2S+ 03:32 0:00 grep
--color=auto 6673
```
This includes sshd, but the forked (still `sshd`) children of sshd
appear to have their memlock limit increased. This results in direct
shell operations under sshd having realistic limits. However, processes
"kicked off" by an ssh shell session, but not actually originally
parented under them, will have the austere 64k memlock limit. This is
the case with docker (the ubuntu docker.io package) containers, as
containerd's systemd configuration
(/lib/systemd/system/containerd.service) does not set LimitMEMLOCK. And
it should not have to.
Per this thread
(https://twitter.com/ChaosDatumz/status/1198075570921394177), this is
causing problems for eBPF related functionality running under docker due
to the fact that the memlock limit is used to track eBPF maps and is
tracked on the user, which is an issue because root in a non-user
namespaced container is technically root on the outside, so on top of
this paltry memlock limit, existing host processes running as root are
counting towards the container's memlock limit. This likely has
cascading effects for anything eBPF-related that isn't being started by
a user's shell, but the user-based memlock accounting behavior will
likely cause other issues for anything running in a container that
performs such checks given that on a typical system, root host processes
may well already have more than 64k in locked kernel memory allocated. I
don't think the solution for this is just to special case containerd (or
docker.io) with a configuration, but to fix this at its heart, systemd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837580
Title:
memlock is not set
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837580/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837580] Re: memlock is not set
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (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/1837580 Title: memlock is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776642] Re: Temporal dithering and impaired graphical performance started appearing on Intel HD 530 graphics
Paul F, if you think you have found a bug, then you need to make a new, separate bug report under a new bug number, because your hardware is different and you are not discussing a regression in kernel 4.13.0-43, which is what this particular bug was about. Here are some instructions for reporting kernel bugs in Ubuntu: https://wiki.ubuntu.com/Kernel/Bugs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776642 Title: Temporal dithering and impaired graphical performance started appearing on Intel HD 530 graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075923] Re: nautilus hangs copying large directories from a samba share
Still a problem on Eoan. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075923 Title: nautilus hangs copying large directories from a samba share To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1075923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
** Attachment added: "tearing-1.mp4" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5307224/+files/tearing-1.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
** Attachment added: "tearing-2.mp4" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5307225/+files/tearing-2.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
@Akshay, Does it 100% happen? Did you login through keyboard/ssh connection/usb- serial console? Last could you please try the Image of #36. thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
@Unleavened, This is the image with the new kernel. http://cdimage.ubuntu.com/ubuntu- server/eoan/daily-preinstalled/20191122/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851190] Re: Ubuntu 18.04: kexec-tool shows "kexec: elfcorehdr doesn't fit cells-size" if crashkernel reserved beyond 4GB
Verification: ubuntu@bionic:~$ sudo kexec -p /boot/vmlinuz-`uname -r` --initrd=/boot/initrd.img-`uname -r` --reuse-cmdline ubuntu@bionic:~$ echo 1 | sudo tee /proc/sys/kernel/sysrq 1 ubuntu@bionic:~$ echo c | sudo tee /proc/sysrq-trigger c [ 164.962517] sysrq: SysRq : Trigger a crash [ 164.968259] Internal error: Accessing user space memory outside uaccess.h routines: 9644 [#1] SMP [ 164.980205] Modules linked in: isofs nls_iso8859_1 sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear virtio_blk virtio_net aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 165.027333] Process tee (pid: 995, stack limit = 0x(ptrval)) [ 165.035125] CPU: 0 PID: 995 Comm: tee Not tainted 4.15.0-70-generic #79-Ubuntu [ 165.043884] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 165.052153] pstate: 0045 (nzcv daif +PAN -UAO) [ 165.057891] pc : sysrq_handle_crash+0x24/0x30 [ 165.063361] lr : __handle_sysrq+0xbc/0x1c0 [ 165.068316] sp : 0b993d50 [ 165.072308] x29: 0b993d50 x28: 800173b73c00 [ 165.078722] x27: 08b42000 x26: 0040 [ 165.085075] x25: 0124 x24: 095ce000 [ 165.091453] x23: 0007 x22: 0002 [ 165.097766] x21: 0063 x20: 0953 [ 165.104181] x19: 095cea80 x18: [ 165.110614] x17: x16: [ 165.117007] x15: 09508c08 x14: 896b6ce7 [ 165.123376] x13: 096b6cf5 x12: 0953 [ 165.129697] x11: 09509660 x10: 08715e80 [ 165.136172] x9 : ffd0 x8 : 0017 [ 165.142496] x7 : 53203a7172737973 x6 : 80017fdce2e8 [ 165.148990] x5 : 80017fdce2e8 x4 : [ 165.155352] x3 : 80017fdd66c8 x2 : cc0b9440e8d0c900 [ 165.161663] x1 : x0 : 0001 [ 165.168036] Call trace: [ 165.171053] sysrq_handle_crash+0x24/0x30 [ 165.175855] __handle_sysrq+0xbc/0x1c0 [ 165.180378] write_sysrq_trigger+0xb8/0x120 [ 165.185223] proc_reg_write+0x80/0xc0 [ 165.189608] __vfs_write+0x48/0x80 [ 165.193883] vfs_write+0xac/0x1b0 [ 165.197962] SyS_write+0x74/0xf0 [ 165.201976] el0_svc_naked+0x30/0x34 [ 165.206719] Code: 52800020 b90ca020 d5033e9f d281 (3920) [ 165.252678] Starting crashdump kernel... [ 165.257367] Bye! [0.00] Booting Linux on physical CPU 0x00 [0x500f] [0.00] Linux version 4.15.0-70-generic (buildd@bos02-arm64-021) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #79-Ubuntu SMP Tue Nov 12 10:36:10 UTC 2019 (Ubuntu 4.15.0-70.79-generic 4.15.18) [0.00] efi: Getting EFI parameters from FDT: [0.00] efi: EFI v2.70 by EDK II ... ** Tags removed: verification-needed ** Tags added: verification-done ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851190 Title: Ubuntu 18.04: kexec-tool shows "kexec: elfcorehdr doesn't fit cells- size" if crashkernel reserved beyond 4GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851897] Re: devicetree command should be disabled in Secure Boot mode
bionic verification: GNU GRUB version 2.02 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. ESC at any time exits. grub> device-tree foo error: can't find command `device-tree'. grub> devicetree foo error: Secure Boot forbids loading devicetree from foo. grub> ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851897 Title: devicetree command should be disabled in Secure Boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853506] Re: [MIR] ndctl
** Description changed: https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506 [Availability] There is an on-going MIR for a package whose ndctl is a dependency: pmdk (LP: #1790856) * Package exists since bionic (-updates) in universe: 61.2-0ubuntu1~18.04.1 | bionic-updates/universe 63-1.3| disco/universe 65-1 | eoan/universe 67-1 | focal/universe * Packages: ndctl libndctl6 libndctl-dev daxctl libdaxctl1 libdaxctl-dev ndctl: dctl is utility for managing the "libnvdimm" kernel subsystem. The "libnvdimm" subsystem defines a kernel device model and control message interface for platform NVDIMM resources like those defined by the ACPI 6.0 NFIT (NVDIMM Firmware Interface Table). Operations supported by the tool include, provisioning capacity (namespaces), as well as enumerating/enabling/disabling the devices (dimms, regions, namespaces) associated with an NVDIMM bus. daxctl: The daxctl utility provides enumeration and provisioning commands for the Linux kernel Device-DAX facility. This facility enables DAX mappings of performance / feature differentiated memory without need of a filesystem. * Architectures: source, amd64, arm64, armhf, i386, ppc64el, s390x PMEM: A system-physical-address range where writes are persistent. A block device composed of PMEM is capable of DAX. A PMEM address range may span an interleave of several DIMMs. BLK: A set of one or more programmable memory mapped apertures provided by a DIMM to access its media. This indirection precludes the performance benefit of interleaving, but enables DIMM-bounded failure modes. DAX: File system extensions to bypass the page cache and block layer to mmap persistent memory, from a PMEM block device, directly into a process address space. Binary Packages: ndctl libndctl6 libndctl-dev daxctl libdaxctl1 libdaxctl-dev [Rationale] - This is part of the MIR activity for all dependencies of pmdk. + This is part of the MIR activity for all dependencies of pmdk. "ndctl" + and "daxctl" are userland tools used to configure NVDIMMs and should be + supported and put in main pocket (and server). The "main" MIR of it is at: https://bugs.launchpad.net/ubuntu/+source/pmdk/+bug/1790856 Package was introduced in bionic after bionic was released (19.04.1) in universe and it is still in universe until now. [Security] - TODO: check the security History of the package - - http://people.ubuntu.com/~ubuntu-security/cve/universe.html - - http://cve.mitre.org/cve/cve.html + - No related CVEs found at: cve.mitre.org [Quality assurance] * Documentation: - https://docs.pmem.io/ndctl-users-guide - https://nvdimm.wiki.kernel.org/ - Both packages (ndctl and daxctl) and its libraries (libndctl6, libndctl-dev, libdaxctl1, libdaxctl-dev) install fine and are operational (check comment #1). - There are no debconf templates and/or questions in this package. - TODO: There are no long-term outstanding bugs which affect the usability - of the program to a major degree. To support a package, we must be - reasonably convinced that upstream supports and cares for the package. - - TODO: The status of important bugs in Debian's, Ubuntu's, and upstream's - bug tracking systems must be evaluated. Important bugs must be pointed - out and discussed in the MIR report. - - TODO: The package is maintained well in Debian/Ubuntu (check out the - Debian PTS) - - TODO: The package should not deal with exotic hardware which we cannot - support. - - TODO: If the package ships a test suite, and there is no obvious reason - why it cannot work during build (e. g. it needs root privileges or - network access), it should be run during package build, and a failing - test suite should fail the build. - - TODO: The package uses a debian/watch file whenever possible. In cases - where this is not possible (e. g. native packages), the package should - either provide a debian/README.source file or a debian/watch file (with - comments only) providing clear instructions on how to generate the - source tar file. - - TODO: It is often useful to run lintian --pedantic on the package to - spot the most common packaging issues in advance - - TODO: The package should not rely on obsolete or about to be demoted - packages. That currently includes package dependencies on Python2 - (without providing Python3 packages), and packages depending on GTK2. + - The only existing/opened bug affecting the package was LP: #1811785 + and I have already provided 2 MRs fixing that issue. No other long-term + outstanding bug affecting it. Upstream seems well maintained and + isolating fix commits, making them easy to cherry-pick and/or backport. + + - There are no current
[Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address
Afternotes: I only noticed the bug shortly after upgrading from Ubuntu 16.04 to Ubuntu 18.04 Seems like 16.04 didn't yet use systemd-resolved, but dnsmasq, which only returned ipv4 addresses. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853669 Title: systemd resolves own hostname to link local ipv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Hello Torel and Juliet, If possible, could you please test the PPA above with either Bionic and/or Disco and make sure the packages fix the issue ? I'm preparing bdctl to be in "main" pocket for 20.04: https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506 and having this case fix would help to get traction in the MIR (main inclusion request). Thank you very much for reporting this and contributing to Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811785 Title: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840 To manage notifications about this bug go to: https://bugs.launchpad.net/ndctl/+bug/1811785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853669] [NEW] systemd resolves own hostname to link local ipv6 address
Public bug reported: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: inet6 linklocal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853669 Title: systemd resolves own hostname to link local ipv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
** Changed in: ndctl (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: ndctl (Ubuntu Disco) 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/1811785 Title: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840 To manage notifications about this bug go to: https://bugs.launchpad.net/ndctl/+bug/1811785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/ndctl/+git/ndctl/+merge/375930 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811785 Title: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840 To manage notifications about this bug go to: https://bugs.launchpad.net/ndctl/+bug/1811785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737976] Re: netplan cannot set IPv6 token
Not sure if that applies here, but "fe80::a8bb:ccff:fedd:eeff" is not a valid ipv6 address on this machine. instead try "fe80::a8bb:ccff:fedd:eeff%ens3" The problem might be with "systemd-resolved" which happily serves "fe80::a8bb:ccff:fedd:eeff" as an ipv6 address of this machine. I stumbled over this ticket based on symptoms I saw (unrelated to netplan), and searching for some keywords... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737976 Title: netplan cannot set IPv6 token To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1737976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/ndctl/+git/ndctl/+merge/375929 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811785 Title: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840 To manage notifications about this bug go to: https://bugs.launchpad.net/ndctl/+bug/1811785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
A PPA containing the fixes (Disco and Bionic) will be available here: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1811785 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811785 Title: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840 To manage notifications about this bug go to: https://bugs.launchpad.net/ndctl/+bug/1811785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853657] Re: librsvg 2.44.15 FTBFS in focal
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853657 Title: librsvg 2.44.15 FTBFS in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to
host (256 byte) labels
This issue is fixed by:
commit 9c6aae5
Author: Dan Williams
Date: Tue Jan 15 01:51:45 2019
ndctl/init-labels: Fix label slot accounting per UEFI 2.7
Quoting from Linux kernel commit 9e694d9c18dd "libnvdimm, label: change
nvdimm_num_label_slots per UEFI 2.7":
sizeof_namespace_index() fails when NVDIMM devices have the minimum
1024 bytes label storage area. nvdimm_num_label_slots() returns 3
slots while the area is only big enough for 2 slots.
Change nvdimm_num_label_slots() to calculate a number of label slots
according to UEFI 2.7 spec.
Without this fix attempts to initialize labels on a small (1K) label
area results in the following:
libndctl: sizeof_namespace_index: nmem2: label area (1024) too small to
host (128 byte) labels
libndctl: sizeof_namespace_index: nmem2: label area (1024) too small to
host (256 byte) labels
Based on an original patch by Toshi Kani
Fixes: bdaec95463ca ("ndctl: introduce
ndctl_dimm_{validate_labels,init_labels}")
Reported-by: Sujith Pandel
Link: https://github.com/pmem/ndctl/issues/78
Signed-off-by: Dan Williams
Signed-off-by: Vishal Verma
Upstream.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ndctl (Ubuntu)
Importance: Undecided => Medium
** Changed in: ndctl (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
To manage notifications about this bug go to:
https://bugs.launchpad.net/ndctl/+bug/1811785/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
It fixes an issue introduced by : Patch: bdaec95463ca In version v58 And the fix (9c6aae5) was introduced in v64. $ rmadison ndctl ndctl | 61.2-0ubuntu1~18.04.1 | bionic-updates/universe | source, amd64 ndctl | 63-1.3| disco/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x ndctl | 65-1 | eoan/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x ndctl | 67-1 | focal/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x Bionic and Disco are affected. ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ndctl (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: ndctl (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: ndctl (Ubuntu Disco) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Disco) ** No longer affects: linux (Ubuntu Eoan) ** Changed in: ndctl (Ubuntu) Status: Confirmed => Fix Released ** Changed in: ndctl (Ubuntu Eoan) Status: New => Fix Released ** Changed in: ndctl (Ubuntu Disco) Status: New => Confirmed ** Changed in: ndctl (Ubuntu Bionic) Status: New => Confirmed ** Changed in: ndctl (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: ndctl (Ubuntu Bionic) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: ndctl (Ubuntu Disco) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: ndctl (Ubuntu) Importance: Medium => Undecided ** Changed in: ndctl (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: ndctl (Ubuntu Bionic) 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/1811785 Title: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840 To manage notifications about this bug go to: https://bugs.launchpad.net/ndctl/+bug/1811785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853506] Re: [MIR] ndctl
When using dax: (k)rafaeldtinoco@emulated:~$ sudo mount -o dax /dev/pmem0p1 /mnt (k)rafaeldtinoco@emulated:~$ mount | grep -i mnt /dev/pmem0p1 on /mnt type ext4 (rw,relatime,dax,stripe=512) (k)rafaeldtinoco@emulated:~$ dd if=/dev/zero of=./teste bs=1M count=1024 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 0.43958 s, 2.4 GB/s ** Description changed: - https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506 [Availability] There is an on-going MIR for a package whose ndctl is a dependency: pmdk (LP: #1790856) * Package exists since bionic (-updates) in universe: - 61.2-0ubuntu1~18.04.1 | bionic-updates/universe - 63-1.3| disco/universe - 65-1 | eoan/universe - 67-1 | focal/universe + 61.2-0ubuntu1~18.04.1 | bionic-updates/universe + 63-1.3| disco/universe + 65-1 | eoan/universe + 67-1 | focal/universe * Packages: - ndctl libndctl6 libndctl-dev - daxctl libdaxctl1 libdaxctl-dev + ndctl libndctl6 libndctl-dev + daxctl libdaxctl1 libdaxctl-dev - ndctl: dctl is utility for managing the "libnvdimm" kernel - subsystem. The "libnvdimm" subsystem defines a kernel device - model and control message interface for platform NVDIMM resources - like those defined by the ACPI 6.0 NFIT (NVDIMM Firmware - Interface Table). - - Operations supported by the tool include, provisioning capacity - (namespaces), as well as enumerating/enabling/disabling the - devices (dimms, regions, namespaces) associated with an NVDIMM - bus. - - daxctl: The daxctl utility provides enumeration and provisioning - commands for the Linux kernel Device-DAX facility. This facility - enables DAX mappings of performance / feature differentiated - memory without need of a filesystem. + ndctl: dctl is utility for managing the "libnvdimm" kernel + subsystem. The "libnvdimm" subsystem defines a kernel device + model and control message interface for platform NVDIMM resources + like those defined by the ACPI 6.0 NFIT (NVDIMM Firmware + Interface Table). + + Operations supported by the tool include, provisioning capacity + (namespaces), as well as enumerating/enabling/disabling the + devices (dimms, regions, namespaces) associated with an NVDIMM + bus. + + daxctl: The daxctl utility provides enumeration and provisioning + commands for the Linux kernel Device-DAX facility. This facility + enables DAX mappings of performance / feature differentiated + memory without need of a filesystem. * Architectures: - source, amd64, arm64, armhf, i386, ppc64el, s390x + source, amd64, arm64, armhf, i386, ppc64el, s390x - PMEM: A system-physical-address range where writes are persistent. A - block device composed of PMEM is capable of DAX. A PMEM address + PMEM: A system-physical-address range where writes are persistent. A + block device composed of PMEM is capable of DAX. A PMEM address range may span an interleave of several DIMMs. - BLK: A set of one or more programmable memory mapped apertures - provided by a DIMM to access its media. This indirection precludes - the performance benefit of interleaving, but enables DIMM-bounded + BLK: A set of one or more programmable memory mapped apertures + provided by a DIMM to access its media. This indirection precludes + the performance benefit of interleaving, but enables DIMM-bounded failure modes. - DAX: File system extensions to bypass the page cache and block layer - to mmap persistent memory, from a PMEM block device, directly into a + DAX: File system extensions to bypass the page cache and block layer + to mmap persistent memory, from a PMEM block device, directly into a process address space. Binary Packages: - ndctl - libndctl6 - libndctl-dev - daxctl - libdaxctl1 - libdaxctl-dev + ndctl + libndctl6 + libndctl-dev + daxctl + libdaxctl1 + libdaxctl-dev [Rationale] This is part of the MIR activity for all dependencies of pmdk. The "main" MIR of it is at: https://bugs.launchpad.net/ubuntu/+source/pmdk/+bug/1790856 - Package was introduced in bionic after bionic was released (19.04.1) + Package was introduced in bionic after bionic was released (19.04.1) in universe and it is still in universe until now. [Security] TODO: check the security History of the package - http://people.ubuntu.com/~ubuntu-security/cve/universe.html - http://cve.mitre.org/cve/cve.html [Quality assurance] * Documentation: - - https://docs.pmem.io/ndctl-users-guide - - https://nvdimm.wiki.kernel.org/ + - https://docs.pmem.io/ndctl-users-guide + - https://nvdimm.wiki.kernel.org/ - Both packages (ndctl and daxctl) and its libraries (libndctl6, -
[Bug 1807732] Re: lots of "fail" and "error" messages in mmap test, yet test exits with a 0 code
** Changed in: stress-ng (Ubuntu Bionic) Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807732 Title: lots of "fail" and "error" messages in mmap test, yet test exits with a 0 code To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1807732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853666] 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/1853666 Title: Battery will not charge on Toshiba Satellite Pro A50-C-119 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853667] Re: Contents of home folder replace/disappeared on fresh ZFS install
I saw this as well after rebooting.
I was able to manually mount my home folder using the command this
generates:
mount | grep rpool/USERDATA/ | head -1 | \
awk -F '_' '{print $2}' | awk -v user=$USER \
'{print "sudo zfs mount rpool/USERDATA/" user "_"$1}'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853667
Title:
Contents of home folder replace/disappeared on fresh ZFS install
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1853667/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853667] Re: Contents of home folder replace/disappeared on fresh ZFS install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zsys (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/1853667 Title: Contents of home folder replace/disappeared on fresh ZFS install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1853667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853667] [NEW] Contents of home folder replace/disappeared on fresh ZFS install
Public bug reported: Description:Ubuntu 19.10 Release:19.10 The contents of my Home folder have been replaced/disappeared. ls now brings back: Desktop, Documents, Downloads, Music, Pictures, Public, Templates, Videos. The original contents of my home folder still existed at some point as I had previously created an SMB share which could still be access/written to but I couldn't "find" said folder. I tried rolling back to a ZFS snapshot created approximately 12 hours prior to the change but it hasn't made any difference, the changed folders are still there and I can't view the originals. Prior to noticing the change, I had tried enabling SMB sharing through ZFS on the USERDATA datasets as I was initially having trouble viewing the SMB share when it had been created through smb.conf. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 22 23:35:30 2019 InstallationDate: Installed on 2019-11-21 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zsys (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1853667 Title: Contents of home folder replace/disappeared on fresh ZFS install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1853667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853666] [NEW] Battery will not charge on Toshiba Satellite Pro A50-C-119
Public bug reported: Since I have switched from Windows 10 to Ubuntu, my battery will no longer charge. The battery shows 0% charge and says Estimating. Ubuntu appears to detect removing the battery as the battery indicator disappears and reappears upon replacing the battery. Unplugging the AC adaptor with the battery plugged in causes the computer to lose power immediately. When the computer is off with battery connected and AC adaptor removed, the computer will not switch on. I have bought a new battery but that produces the same problem. In Power Settings, the battery status is shown as Charging 0%. I believe this to be an ACPI issue. I have followed the instructions on these websites: https://ubuntu.com/blog/debug-dsdt-ssdt-with-acpica-utilities https://wiki.ubuntu.com/Kernel/Reference/ACPITricksAndTips The acpi driver loaded is toshiba_acpi. I have extracted some information using acpidump and acpiexec which is in the attached file acpiexec.log. Linux image linux-image-5.3.0-23-generic cat /proc/version_signature Ubuntu 5.3.0-23.25-generic 5.3.7 lsb_release -rd Description:Ubuntu 19.10 Release:19.10 sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI [8086:1604] (rev 09) Subsystem: Toshiba America Info Systems Broadwell-U Host Bridge -OPI [1179:0001] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: bdw_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:000d] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend- LnkCap: Port #6, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s (downgraded), Width x0 (downgraded) TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Slot #0, PowerLimit 0.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq+ LinkChg+ Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Via WAKE# ARIFwd- AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- AtomicOpsCtl: ReqEn- EgressBlck- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee01004 Data: 4028 Capabilities: [90] Subsystem: Toshiba America Info Systems Wildcat Point-LP PCI Express Root Port [1179:0001] Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pcieport 00:1c.2 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 [8086:9c94] (rev e3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
[Bug 1853665] [NEW] Bluetooth not working with Realtek RTL8821CE
Public bug reported: The driver installed just fine and wifi is working but bluetooth does not. I will gladly provide further debugging information. Ubuntu 19.10 ** Affects: linux-oem (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/1853665 Title: Bluetooth not working with Realtek RTL8821CE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1853665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832882] Re: libcurl-gnutls segfaults spotify client
> Pardon my ignorance about the Launchpad bug metadata states, > but: is there going to be an update for Ubuntu Disco fixing > this issue? Given that Eoan has now been released, and there is not an isolated bug fix for Disco, it is unlikely that an update will be pushed to Disco for this issue. ** Tags added: rls-dd-notfixing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832882 Title: libcurl-gnutls segfaults spotify client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687122] Re: /usr/bin/add-apt-repository:OSError:/usr/bin/add-apt-repository@168:add_source_from_shortcut:/usr/bin/add-apt-repository@172
** Changed in: software-properties (Ubuntu) Status: New => Fix Released ** Changed in: software-properties (Ubuntu) Milestone: ubuntu-17.08 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687122 Title: /usr/bin/add-apt-repository:OSError:/usr/bin/add-apt- repository@168:add_source_from_shortcut:/usr/bin/add-apt- repository@172 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1687122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687122] Re: /usr/bin/add-apt-repository:OSError:/usr/bin/add-apt-repository@168:add_source_from_shortcut:/usr/bin/add-apt-repository@172
** Changed in: software-properties (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687122 Title: /usr/bin/add-apt-repository:OSError:/usr/bin/add-apt- repository@168:add_source_from_shortcut:/usr/bin/add-apt- repository@172 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1687122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852300] Re: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker
** Changed in: kernel-sru-workflow/automated-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: 1852306 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 20. November 2019 02:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1852299 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/1852300 Title: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853506] Re: [MIR] ndctl
This is a good XML template for a VM emulating nvdimms. ** Attachment added: "emulated_vm.xml" https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506/+attachment/5307204/+files/emulated_vm.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853506 Title: [MIR] ndctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby
Can confirm the problem still exists with Ubuntu 19.10, all up-to-date. Where can I dig to debug? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612916 Title: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853506] Re: [MIR] ndctl
(k)rafaeldtinoco@emulated:~$ sudo ndctl enable-dimm all
enabled 2 nmems
(k)rafaeldtinoco@emulated:~$ sudo ndctl list -D
[
{
"dev":"nmem1",
"id":"8680-57341200",
"handle":2,
"phys_id":0,
"flag_failed_arm":true
},
{
"dev":"nmem0",
"id":"8680-56341200",
"handle":1,
"phys_id":0,
"flag_failed_arm":true
}
]
(k)rafaeldtinoco@emulated:~$ sudo ndctl enable-region all
enabled 2 regions
(k)rafaeldtinoco@emulated:~$ ndctl list -R
[
{
"dev":"region1",
"size":2145386496,
"available_size":0,
"max_available_extent":0,
"type":"pmem",
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":2145386496,
"available_size":0,
"max_available_extent":0,
"type":"pmem",
"persistence_domain":"unknown"
}
]
(k)rafaeldtinoco@emulated:~$ sudo ndctl create-namespace -r region0
{
"dev":"namespace0.0",
"mode":"fsdax",
"map":"dev",
"size":"2014.00 MiB (2111.83 MB)",
"uuid":"c3621fd1-6b37-4241-956f-eeffdb498872",
"sector_size":512,
"align":2097152,
"blockdev":"pmem0"
}
(k)rafaeldtinoco@emulated:~$ sudo ndctl create-namespace -r region1
{
"dev":"namespace1.0",
"mode":"fsdax",
"map":"dev",
"size":"2014.00 MiB (2111.83 MB)",
"uuid":"ec231ca1-cc4a-41e6-892b-e8afd3e36313",
"sector_size":512,
"align":2097152,
"blockdev":"pmem1"
}
(k)rafaeldtinoco@emulated:~$ sudo cat /proc/iomem
...
24000-2bfdf : Persistent Memory
24000-2bfdf : namespace0.0
2bfe0-33fbf : Persistent Memory
2bfe0-33fbf : namespace1.0
(k)rafaeldtinoco@emulated:~$ sudo fdisk -l /dev/pmem0
Disk /dev/pmem0: 1.99 GiB, 2111832064 bytes, 4124672 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x6e3d7965
Device Boot Start End Sectors Size Id Type
/dev/pmem0p1 4096 4124671 4120576 2G 83 Linux
(k)rafaeldtinoco@emulated:~$ sudo mkfs.ext4 -b 4096 -E stride=512 -F /dev/pmem0
mke2fs 1.45.3 (14-Jul-2019)
Found a dos partition table in /dev/pmem0
Creating filesystem with 515584 4k blocks and 129024 inodes
Filesystem UUID: d6d72f36-28bb-40ed-9108-252e3787b08e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
k)rafaeldtinoco@emulated:~$ sudo mkfs.ext4 -b 4096 -E stride=512 /dev/pmem0
pmem0# pmem0p1#
(k)rafaeldtinoco@emulated:~$ sudo mkfs.ext4 -b 4096 -E stride=512 /dev/pmem0p1
mke2fs 1.45.3 (14-Jul-2019)
Creating filesystem with 515072 4k blocks and 128768 inodes
Filesystem UUID: 56e9b056-eea1-41dd-9eaa-3f9e66c712d0
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
(k)rafaeldtinoco@emulated:~$ sudo mount /dev/pmem0p1 /mnt
(k)rafaeldtinoco@emulated:/mnt$ sudo dd if=/dev/zero of=./teste bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 2.70624 s, 397 MB/s
** Description changed:
+
+ https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506
+
[Availability]
- There is an on-going MIR for a package whose ndctl is a dependency: pmdk
- (LP: #1790856)
+ There is an on-going MIR for a package whose ndctl is a dependency:
+ pmdk (LP: #1790856)
- TODO: The package must already be in the Ubuntu universe, and must build
- for the architectures it is designed to work on.
+ * Package exists since bionic (-updates) in universe:
- TODO: mention which binaries we actually want (if the package builds
- more than one). Check the dependency-tree.txt file which binary we
- actually need vs the debian/control file in the source
+ 61.2-0ubuntu1~18.04.1 | bionic-updates/universe
+ 63-1.3| disco/universe
+ 65-1 | eoan/universe
+ 67-1 | focal/universe
+
+ * Packages:
+
+ ndctl libndctl6 libndctl-dev
+ daxctl libdaxctl1 libdaxctl-dev
+
+ ndctl: dctl is utility for managing the "libnvdimm" kernel
+ subsystem. The "libnvdimm" subsystem defines a kernel device
+ model and control message interface for platform NVDIMM resources
+ like those defined by the ACPI 6.0 NFIT (NVDIMM Firmware
+ Interface Table).
+
+ Operations supported by the tool include, provisioning capacity
+ (namespaces), as well as enumerating/enabling/disabling the
+ devices (dimms, regions, namespaces) associated with an NVDIMM
+ bus.
+
+ daxctl: The daxctl utility provides enumeration and provisioning
+ commands for
[Bug 1852302] Re: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker
** Changed in: kernel-sru-workflow/automated-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: 1852306 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 20. November 2019 07:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1852301 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/1852302 Title: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux (Ubuntu Disco) Status: New => Invalid ** Changed in: lvm2 (Ubuntu Cosmic) Status: New => Won't Fix ** Changed in: lvm2 (Ubuntu Eoan) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853661] [NEW] systemd-timesyncd.server failed with exit code 3
Public bug reported: This happened on a Raspberry Pi 4 on which I had installed the arm64 image from http://cdimage.ubuntu.com/ubuntu-server/eoan/daily- preinstalled/20191122/. Its worth noting I also encountered a crash with cloud-init, bug 1853660, so maybe everything wasn't set up properly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.2 ProcVersionSignature: User Name 5.3.0-1013.15-raspi2 5.3.10 Uname: Linux 5.3.0-1013-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: arm64 Date: Thu Apr 11 17:08:55 2019 ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:37:37:07 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 eoan package-from-proposed uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853661 Title: systemd-timesyncd.server failed with exit code 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853643] Re: Menu Fails to Launch Applications
The problem manifested in 19.04 before the upgrade. I had hoped 19.10 would fix. The issue is intermittent. Logging out or rebooting fixes for a time. Launching favorited apps from the Icon Task List always works, so problem has been easy to ignore. This is the first Ubuntu bug I have ever filed, so it took me some time to get here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853643 Title: Menu Fails to Launch Applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1853643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853660] Re: cloud-init crashed with OSError in write_file(): [Errno 117] Structure needs cleaning: '/var/lib/cloud/data/tmpcct746jf' -> '/var/lib/cloud/data/status.json'
** Tags removed: need-duplicate-check ** Changed in: cloud-init (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/1853660 Title: cloud-init crashed with OSError in write_file(): [Errno 117] Structure needs cleaning: '/var/lib/cloud/data/tmpcct746jf' -> '/var/lib/cloud/data/status.json' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1853660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853657] Re: librsvg 2.44.15 FTBFS in focal
Follow-up patch that updates the vendored crates in the source tarball accordingly. ** Patch added: "cssparser-update-vendored-crates.patch" https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+attachment/5307180/+files/cssparser-update-vendored-crates.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853657 Title: librsvg 2.44.15 FTBFS in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853657] Re: librsvg 2.44.15 FTBFS in focal
Patch for the upstream commit (https://gitlab.gnome.org/GNOME/librsvg/commit/de26c4d8). ** Patch added: "upstream-de26c4d8.patch" https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+attachment/5307179/+files/upstream-de26c4d8.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853657 Title: librsvg 2.44.15 FTBFS in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853659] [NEW] Disco update: upstream stable patchset 2019-11-22
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-11-22 Ported from the following upstream stable releases: v4.19.84, v5.3.11 from git://git.kernel.org/ bonding: fix state transition issue in link monitoring CDC-NCM: handle incomplete transfer of MTU ipv4: Fix table id reference in fib_sync_down_addr net: ethernet: octeon_mgmt: Account for second possible VLAN header net: fix data-race in neigh_event_send() net: qualcomm: rmnet: Fix potential UAF when unregistering net: usb: qmi_wwan: add support for DW5821e with eSIM support NFC: fdp: fix incorrect free object nfc: netlink: fix double device reference drop NFC: st21nfca: fix double free qede: fix NULL pointer deref in __qede_remove() net: mscc: ocelot: don't handle netdev events for other netdevs net: mscc: ocelot: fix NULL pointer on LAG slave removal ipv6: fixes rt6_probe() and fib6_nh->last_probe init net: hns: Fix the stray netpoll locks causing deadlock in NAPI path ALSA: timer: Fix incorrectly assigned timer instance ALSA: bebob: fix to detect configured source of sampling clock for Focusrite Saffire Pro i/o series ALSA: hda/ca0132 - Fix possible workqueue stall mm: memcontrol: fix network errors from failing __GFP_ATOMIC charges mm, meminit: recalculate pcpu batch and high limits after init completes mm: thp: handle page cache THP correctly in PageTransCompoundMap mm, vmstat: hide /proc/pagetypeinfo from normal users dump_stack: avoid the livelock of the dump_lock tools: gpio: Use !building_out_of_srctree to determine srctree perf tools: Fix time sorting drm/radeon: fix si_enable_smc_cac() failed issue HID: wacom: generic: Treat serial number and related fields as unsigned soundwire: depend on ACPI soundwire: bus: set initial value to port_status arm64: Do not mask out PTE_RDONLY in pte_same() ceph: fix use-after-free in __ceph_remove_cap() ceph: add missing check in d_revalidate snapdir handling iio: adc: stm32-adc: fix stopping dma iio: imu: adis16480: make sure provided frequency is positive iio: srf04: fix wrong limitation in distance measuring ARM: sunxi: Fix CPU powerdown on A83T netfilter: nf_tables: Align nft_expr private data to 64-bit netfilter: ipset: Fix an error code in ip_set_sockfn_get() intel_th: pci: Add Comet Lake PCH support intel_th: pci: Add Jasper Lake PCH support x86/apic/32: Avoid bogus LDR warnings SMB3: Fix persistent handles reconnect can: usb_8dev: fix use-after-free on disconnect can: flexcan: disable completely the ECC mechanism can: c_can: c_can_poll(): only read status register after status IRQ can: peak_usb: fix a potential out-of-sync while decoding packets can: rx-offload: can_rx_offload_queue_sorted(): fix error handling, avoid skb mem leak can: gs_usb: gs_can_open(): prevent memory leak can: dev: add missing of_node_put() after calling of_get_child_by_name() can: mcba_usb: fix use-after-free on disconnect can: peak_usb: fix slab info leak configfs: stash the data we need into configfs_buffer at open time configfs_register_group() shouldn't be (and isn't) called in rmdirable parts configfs: new object reprsenting tree fragments configfs: provide exclusion between IO and removals configfs: fix a deadlock in configfs_symlink() ALSA: usb-audio: More validations of descriptor units ALSA: usb-audio: Simplify parse_audio_unit() ALSA: usb-audio: Unify the release of usb_mixer_elem_info objects ALSA: usb-audio: Remove superfluous bLength checks ALSA: usb-audio: Clean up check_input_term() ALSA: usb-audio: Fix possible NULL dereference at create_yamaha_midi_quirk() ALSA: usb-audio: remove some dead code ALSA: usb-audio: Fix copy error in the validator usbip: Fix vhci_urb_enqueue() URB null transfer buffer error path usbip: Implement SG support to vhci-hcd and stub driver PCI: tegra: Enable Relaxed Ordering only for Tegra20 & Tegra30 HID: google: add magnemite/masterball USB ids dmaengine: xilinx_dma: Fix control reg update in vdma_channel_set_config dmaengine: sprd: Fix the possible memory leak issue HID: intel-ish-hid: fix wrong error handling in ishtp_cl_alloc_tx_ring() RDMA/mlx5: Clear old rate limit when closing QP iw_cxgb4: fix ECN check on the passive accept RDMA/qedr: Fix reported firmware version net/mlx5e: TX, Fix consumer index of error cqe dump net/mlx5: prevent memory leak in mlx5_fpga_conn_create_cq scsi: qla2xxx: fixup incorrect usage of host_byte RDMA/uverbs: Prevent potential underflow net: openvswitch: free vport unless register_netdevice() succeeds scsi: lpfc: Honor module parameter lpfc_use_adisc scsi:
[Bug 1853657] Re: librsvg 2.44.15 FTBFS in focal
Build log with the above two patches applied, unit tests fail. ** Attachment added: "buildlog_ubuntu-focal-amd64.librsvg_2.44.15-1ubuntu1_ppa8_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+attachment/5307181/+files/buildlog_ubuntu-focal-amd64.librsvg_2.44.15-1ubuntu1_ppa8_BUILDING.txt.gz ** Changed in: librsvg (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: librsvg (Ubuntu) Status: New => Triaged ** Changed in: librsvg (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853657 Title: librsvg 2.44.15 FTBFS in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853657] [NEW] librsvg 2.44.15 FTBFS in focal
Public bug reported: focal currently has rustc 1.38 (1.38.0+dfsg0.2+llvm-0ubuntu1), and librsvg 2.44.15 fails to build from source with this version. It built fine with rustc 1.37 (although there was a unit test failure on ppc64el, which prevented it from leaving focal-proposed, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942022). The upstream commit that addresses this is https://gitlab.gnome.org/GNOME/librsvg/commit/de26c4d8. I backported it and added another patch to update the vendored crates in the source tarball accordingly, and the build succeeds again, but unit tests consistently fail, on all architectures. The upstream commit message says « Although you should rather be using the 2.46 branch of librsvg as 2.44 is EOL », so we should probably update librsvg in debian to 2.46 indeed. ** Affects: librsvg (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853657 Title: librsvg 2.44.15 FTBFS in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853660] [NEW] cloud-init crashed with OSError in write_file(): [Errno 117] Structure needs cleaning: '/var/lib/cloud/data/tmpcct746jf' -> '/var/lib/cloud/data/status.json'
Public bug reported: I found this crash file on a Raspberry Pi 4 on which I had installed the arm64 image from http://cdimage.ubuntu.com/ubuntu-server/eoan/daily- preinstalled/20191122/. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cloud-init 19.2-36-g059d049c-0ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-1013.15-raspi2 5.3.10 Uname: Linux 5.3.0-1013-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: arm64 Date: Thu Apr 11 16:28:44 2019 ExecutablePath: /usr/bin/cloud-init ExecutableTimestamp: 1570656737 InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/cloud-init init ProcCwd: / ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=linux Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonArgs: ['/usr/bin/cloud-init', 'init'] PythonDetails: N/A SourcePackage: cloud-init Title: cloud-init crashed with OSError in write_file(): [Errno 117] Structure needs cleaning: '/var/lib/cloud/data/tmpcct746jf' -> '/var/lib/cloud/data/status.json' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: cloud-init (Ubuntu) Importance: Medium Status: New ** Tags: apport-crash arm64 eoan uec-images ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853660 Title: cloud-init crashed with OSError in write_file(): [Errno 117] Structure needs cleaning: '/var/lib/cloud/data/tmpcct746jf' -> '/var/lib/cloud/data/status.json' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1853660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853656] Re: how to get percocet online
** Package changed: compiz-plugins-main (Ubuntu) => null-and-void ** Information type changed from Public to Private ** Changed in: null-and-void 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/1853656 Title: how to get percocet online To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1853656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853656] [NEW] how to get percocet online
Private bug reported: ORDER PERCOCET ONLINE: https://redditpharmacy.com/product-category/buy-percocet-online/ I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm switching workspaces, it occasionally locks up (becoming more frequent). Most of the time, I'm going from the current one down (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able to correct things by backing out to a terminal then returning (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual screen setup acts as one large screen (windows are stretched to the full width of both screens) and many of the windows collect on the first workspace. Ubuntu 11.04 (Classic) All packages up-to-date. If there are any logs/etc that would be helpful, let me know. --- Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale] DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) NonfreeKernelModules: nvidia Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Tags: natty natty ubuntu Uname: Linux 2.6.38-10-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare ** Affects: null-and-void Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853656 Title: how to get percocet online To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1853656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844764] Re: ubuntu_lttng_smoke_test failed with module build on B-hwe-edge 5.3.0
** Also affects: lttng-modules (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: lttng-modules (Ubuntu Bionic) Status: New => In Progress ** Changed in: lttng-modules (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: lttng-modules (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: lttng-modules (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844764 Title: ubuntu_lttng_smoke_test failed with module build on B-hwe-edge 5.3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1844764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852616] Re: r8168-dkms 8.047.04-1 fails to build with 5.4 kernel
Also builds fine with 5.0.0-30-generic. $ sudo dkms build r8168/8.045.08 -k 5.0.0-30-generic Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area. make -j1 KERNELRELEASE=5.0.0-30-generic -C /lib/modules/5.0.0-30-generic/build M=/var/lib/dkms/r8168/8.045.08/build.. Signing module: - /var/lib/dkms/r8168/8.045.08/5.0.0-30-generic/x86_64/module/r8168.ko EFI variables are not supported on this system /sys/firmware/efi/efivars not found, aborting. cleaning build area. DKMS: build completed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852616 Title: r8168-dkms 8.047.04-1 fails to build with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/r8168/+bug/1852616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852616] Re: r8168-dkms 8.047.04-1 fails to build with 5.4 kernel
Finally, builds fine with 4.15.0-68-generic. $ sudo dkms build r8168/8.045.08 -k 4.15.0-68-generic Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area.. make -j1 KERNELRELEASE=4.15.0-68-generic -C /lib/modules/4.15.0-68-generic/build M=/var/lib/dkms/r8168/8.045.08/build... Signing module: - /var/lib/dkms/r8168/8.045.08/4.15.0-68-generic/x86_64/module/r8168.ko EFI variables are not supported on this system /sys/firmware/efi/efivars not found, aborting. cleaning build area. DKMS: build completed. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852616 Title: r8168-dkms 8.047.04-1 fails to build with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/r8168/+bug/1852616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844764] Re: ubuntu_lttng_smoke_test failed with module build on B-hwe-edge 5.3.0
** Changed in: lttng-modules (Ubuntu)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
** Changed in: lttng-modules (Ubuntu)
Status: New => In Progress
** Description changed:
+ [Impact]
+ The DKMS package won't work with new kernels on bionic.
+
+ [Test case]
+ Install and load the modules.
+
+ [Regression potential]
+ This might break the functioning of the module.
+
+ ---
+
Module failed to build on B-hwe-edge (5.3.0):
- DKMS make.log for lttng-modules-2.10.8 for kernel 5.3.0-12-generic (i686)
- Fri Sep 20 03:27:45 UTC 2019
- make: Entering directory '/usr/src/linux-headers-5.3.0-12-generic'
- find: '/var/lib/dkms/lttng-modules/2.10.8/build/extra_version/patches/': No
such file or directory
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/lttng-ring-buffer-client-discard.o
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/lttng-ring-buffer-client-overwrite.o
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/lttng-ring-buffer-metadata-client.o
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/lttng-ring-buffer-client-mmap-discard.o
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/lttng-ring-buffer-client-mmap-overwrite.o
- find:
'/var/lib/dkms/lttng-modules/2.10.8/build/probes/../extra_version/patches/': No
such file or directory
- find:
'/var/lib/dkms/lttng-modules/2.10.8/build/lib/../extra_version/patches/': No
such file or directory
- find:
'/var/lib/dkms/lttng-modules/2.10.8/build/tests/../extra_version/patches/': No
such file or directory
- /var/lib/dkms/lttng-modules/2.10.8/build/probes/Kbuild:41: File
./arch/x86/kvm/lapic.h not found. Probe "kvm" x86-specific is disabled. Use
full kernel source tree to enable it.
-CC [M] /var/lib/dkms/lttng-modules/2.10.8/build/tests/probes/lttng-test.o
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/lib/ringbuffer/ring_buffer_backend.o
- /var/lib/dkms/lttng-modules/2.10.8/build/probes/Kbuild:166: Files
./fs/btrfs/*.h not found. Probe "btrfs" is disabled. Use full kernel source
tree to enable it.
- /var/lib/dkms/lttng-modules/2.10.8/build/probes/Kbuild:182: Files
./fs/ext4/*.h not found. Probe "ext4" is disabled. Use full kernel source tree
to enable it.
- /var/lib/dkms/lttng-modules/2.10.8/build/probes/Kbuild:215: File
./drivers/base/regmap/trace.h not found. Probe "regmap" is disabled. Need Linux
4.1+ kernel source tree to enable it.
- /var/lib/dkms/lttng-modules/2.10.8/build/probes/Kbuild:265: Files
./kernel/trace/trace.h not found. Probe "ftrace" is disabled. Use full kernel
source tree to enable it.
-CC [M] /var/lib/dkms/lttng-modules/2.10.8/build/probes/lttng-probe-sched.o
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/tests/clock-plugin/lttng-clock-plugin-test.o
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/lib/ringbuffer/ring_buffer_frontend.o
-LD [M] /var/lib/dkms/lttng-modules/2.10.8/build/tests/lttng-test.o
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/lib/ringbuffer/ring_buffer_iterator.o
-CC [M] /var/lib/dkms/lttng-modules/2.10.8/build/probes/lttng-probe-irq.o
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/lttng-ring-buffer-metadata-mmap-client.o
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/lib/ringbuffer/ring_buffer_vfs.o
-CC [M] /var/lib/dkms/lttng-modules/2.10.8/build/lttng-clock.o
-LD [M]
/var/lib/dkms/lttng-modules/2.10.8/build/tests/lttng-clock-plugin-test.o
-CC [M] /var/lib/dkms/lttng-modules/2.10.8/build/lttng-events.o
-CC [M] /var/lib/dkms/lttng-modules/2.10.8/build/probes/lttng-probe-timer.o
-CC [M] /var/lib/dkms/lttng-modules/2.10.8/build/lttng-abi.o
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/lib/ringbuffer/ring_buffer_splice.o
-CC [M] /var/lib/dkms/lttng-modules/2.10.8/build/probes/lttng-probe-kmem.o
- /var/lib/dkms/lttng-modules/2.10.8/build/lttng-events.c: In function
'synchronize_trace':
- /var/lib/dkms/lttng-modules/2.10.8/build/lttng-events.c:92:2: error:
implicit declaration of function 'synchronize_sched'; did you mean
'synchronize_srcu'? [-Werror=implicit-function-declaration]
-synchronize_sched();
-^
-synchronize_srcu
-CC [M] /var/lib/dkms/lttng-modules/2.10.8/build/lttng-string-utils.o
- /var/lib/dkms/lttng-modules/2.10.8/build/lttng-events.c: In function
'lttng_session_list_tracker_pids':
- /var/lib/dkms/lttng-modules/2.10.8/build/lttng-events.c:1121:15: warning:
comparison of constant '2147483647' with boolean expression is always false
[-Wbool-compare]
- 1, INT_MAX) == INT_MAX) {
- ^~
-CC [M]
/var/lib/dkms/lttng-modules/2.10.8/build/lib/ringbuffer/ring_buffer_mmap.o
- /var/lib/dkms/lttng-modules/2.10.8/build/lttng-string-utils.c: In function
'strutils_star_glob_match_char_cb':
- /var/lib/dkms/lttng-modules/2.10.8/build/lttng-string-utils.c:315:6:
warning: this statement may fall through [-Wimplicit-fallthrough=]
- p =
[Bug 1848588] Re: ndiswrapper 1.60-8ubuntu1 ADT test failure with linux 5.4.0-1.2
I've sponsored an upload from Paolo to address this issue. I've asked him to fill in the SRU template and I'm hoping that he's able to do that before the SRU team gets to the upload. ** Changed in: ndiswrapper (Ubuntu Bionic) Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Paolo Pisati (p-pisati) ** Changed in: ndiswrapper (Ubuntu Bionic) 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/1848588 Title: ndiswrapper 1.60-8ubuntu1 ADT test failure with linux 5.4.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1848588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852616] Re: r8168-dkms 8.047.04-1 fails to build with 5.4 kernel
bionic version works fine with linux-hwe-edge-5.3.0-23-generic Unpacking r8168-dkms (8.045.08-2ubuntu1) over (8.045.08-2) ... Setting up r8168-dkms (8.045.08-2ubuntu1) ... Loading new r8168-8.045.08 DKMS files... Building for 5.3.0-21-generic 5.3.0-23-generic Module build for kernel 5.3.0-21-generic was skipped since the kernel headers for this kernel does not seem to be installed. Building initial module for 5.3.0-23-generic EFI variables are not supported on this system /sys/firmware/efi/efivars not found, aborting. Done. r8168: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.3.0-23-generic/updates/dkms/ depmod -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852616 Title: r8168-dkms 8.047.04-1 fails to build with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/r8168/+bug/1852616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848596] Re: xtables-addons 3.2-1ubuntu3 ADT test failure with linux 5.4.0-1.2
I've sponsored an upload from Paolo to address this issue in Bionic. I've asked him to fill in the SRU template and I'm hoping that he's able to do that before the SRU team gets to the upload. ** Also affects: xtables-addons (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: xtables-addons (Ubuntu Bionic) Status: New => In Progress ** Changed in: xtables-addons (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: xtables-addons (Ubuntu Bionic) Assignee: (unassigned) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848596 Title: xtables-addons 3.2-1ubuntu3 ADT test failure with linux 5.4.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1848596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837889] Re: ndiswrapper 1.60-8 ADT test failure with linux 5.3.0-0.1
Sorry Thadeu but Paolo had already passed me a debdiff to sponsor for this bug. ** Changed in: ndiswrapper (Ubuntu Bionic) Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837889 Title: ndiswrapper 1.60-8 ADT test failure with linux 5.3.0-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1837889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848584] Re: dahdi-linux 1:2.11.1~dfsg-1ubuntu5 ADT test failure with linux 5.4.0-1.2
I've sponsored an upload from Paolo to address this issue. I've asked him to fill in the SRU template and I'm hoping that he's able to do that before the SRU team gets to the upload. ** Also affects: dahdi-linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: dahdi-linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: dahdi-linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: dahdi-linux (Ubuntu Bionic) Assignee: (unassigned) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848584 Title: dahdi-linux 1:2.11.1~dfsg-1ubuntu5 ADT test failure with linux 5.4.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1848584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849566] Re: r8168 8.045.08-2 ADT test failure with linux-hwe-edge 5.3.0-19.20~18.04.2
Unpacking r8168-dkms (8.045.08-2ubuntu1) over (8.045.08-2) ... Setting up r8168-dkms (8.045.08-2ubuntu1) ... Loading new r8168-8.045.08 DKMS files... Building for 5.3.0-21-generic 5.3.0-23-generic Module build for kernel 5.3.0-21-generic was skipped since the kernel headers for this kernel does not seem to be installed. Building initial module for 5.3.0-23-generic EFI variables are not supported on this system /sys/firmware/efi/efivars not found, aborting. Done. r8168: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.3.0-23-generic/updates/dkms/ depmod -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849566 Title: r8168 8.045.08-2 ADT test failure with linux-hwe-edge 5.3.0-19.20~18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/r8168/+bug/1849566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853643] Re: Menu Fails to Launch Applications
Has it been broken since you upgraded 28 days ago or just recently? If the latter what do you install or remove at or around the time of the breakage? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853643 Title: Menu Fails to Launch Applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1853643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851897] Re: devicetree command should be disabled in Secure Boot mode
disco verification: GNU GRUB version 2.02 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> devicetree x error: Secure Boot forbids loading devicetree from x. grub> ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851897 Title: devicetree command should be disabled in Secure Boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1853525] [NEW] no python 2.7.17 in LTS version
Hello, If you understand my frustration, you should understand how frustrating and uninformative "Segmentation fault error" is. This is my issue. there is segmentation fault when trying to ingest records to the database, that is why trace shows error in ingestIncremental function. The tool is written by Apple not by me and it will NOT BE REWRITTEN for python3, That I can be sure. This is the only tool they provided for the job and it worked perfectly. So therefore something like minimal reproducer does not exist - you should have the tool,mysqldb module with patch,database on your own server, and source data - that package is available only to accepted affiliates and I am not allowed to shared it. The issue is simple - the code that once worked in python 2.7 no longer works in python 2.7. Code is the same,no errors are logged in EPFLog so the issue must be with interpreter that unfortunately I upgraded - this is the lesson, never ever upgrade something that works. My python version is "Python 2.7.15+ (default, Oct 7 2019, 17:39:04)" python2.7/bionic-updates,bionic-security,now 2.7.15-4ubuntu4~18.04.2 amd64 [installed] Interactive high-level object-oriented language (version 2.7) On Fri, Nov 22, 2019 at 2:00 AM Dimitri John Ledkov wrote: > > I am sorry you have an issue with python on Ubuntu. > > By policy, Ubuntu does not blindly upgrade toolchains to point releases in > an LTS release, but we go through extensive validation with rebuild and > autopkgtests across all of our supported 6 architectures, which is usually > in excess of upstream testing. See > https://wiki.ubuntu.com/StableReleaseUpdates > > Note your bug report suggests that you are using out of date package. rc1 > is not the latest version of python2.7 in bionic. It has been updated to > final release, and has had security updates since. Can you please verify > you are using 2.7.15-4ubuntu4~18.04.2 ? > > What particular issue are you having? Can you provide a minimized > reproducer? Traceback? Segfault / coredump? If we have those details about > the issue you are experiencing we can work towards resolving it with > regression testcase, patch and eventual release of an SRU. > > I understand you feel frustrated, but please take some time to explain in > detail the issue you are experiencing. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1853525 > > Title: > no python 2.7.17 in LTS version > > Status in python2.7 package in Ubuntu: > New > > Bug description: > Python 2.7 in 18.04 that is LTS version is in 2.7.15 RC1 version > this version broke my scripts and get me segmentation fault each time I > trying to do something. > IN LTS version always LATEST python 2.7 should be supported which is > 2.7.17. so why I have .15 and in RC1 version. > > Who is maintainer of this package that sleeps so long. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1853525/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853525 Title: no python 2.7.17 in LTS version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1853525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687910] Re: [Lenovo W520] Linux Freezing Issue At Boot
Yes, with several 4.x kernels and even with kernel 5.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687910 Title: [Lenovo W520] Linux Freezing Issue At Boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775067] Re: D-Bus bug in 18.04 i386 SDL: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed
I too found this bug with Ubuntu 18.04 LTS on Nvidia Jetson TX2 system. Running ffplay : ffplay /dev/video0 produces: dbus[9467]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Aborted (core dumped) Workaround 1) from above solved the problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775067 Title: D-Bus bug in 18.04 i386 SDL: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1775067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853489] Re: Ignoring the default NAT when using the virtio adapter
I found that the problem only happens when the "virtio" device model is used in both pfSense internal and UBUNTU interfaces. I tested all combinations and get the following results: pfSense default confinada UBUNTU result virtio virtio virtioERR virtio virtio rtl8139 OK virtio rtl8139virtioOK virtio rtl8139rtl8139 OK rtl8139 virtiovirtio ERR rtl8139 virtiortl8139OK rtl8139 rtl8139 virtio OK rtl8139 rtl8139 rtl8139OK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853489 Title: Ignoring the default NAT when using the virtio adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776642] Re: Temporal dithering and impaired graphical performance started appearing on Intel HD 530 graphics
Question link > https://askubuntu.com/questions/1190609/eye-strain-and- nausea-when-running-18-04-1-on-intel-i915-graphics I have eye strain and headaches using Ubuntu which I believe is caused by temporal dithering being enabled. I have posted on AskUbuntu and it was suggested I update this bug report with some information. *-display description: VGA compatible controller product: Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 12 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:26 memory:fb80-fbbf memory:d000-dfff ioport:dc00(size=8) memory:c-d Linux paul-Aspire-X3950 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) I would like the option to turn dithering off. I believe this can be performed using xrandr on Nvidia cards however no such solution is available for Intel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776642 Title: Temporal dithering and impaired graphical performance started appearing on Intel HD 530 graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851123] Re: Ubuntu 19.10 and focal live cloned create and mount casper-rw partition
@nio-wiklund, @mwhudson : Thanks for your replies. @nio-wiklund : Your solution would probably do the trick, but has the inconvenient of indiscriminately replacing a string with another in the whole image, hence possibly in places where it's not desired. I think I will rather do one of those two things : 1. Create a partition that occupies the remaining space on the USB stick, hence preventing the live image from creating (and writing to) one without my consent 2. Create a custom Grub config file on the EFI partition on the stick, specifying my own parameters The first solution is the most straightforward, has the advantage the stick can be used for additional purposes, but the inconvenient that it's hardware-dependent (not all sticks have the same size). To have the integrity check work, I would have to rehash after modifying, and maintain different hashes, one hash per stick. The second solution requires more changes, but would work for all sticks. It probably won't work if I boot the stick on a non-EFI BIOS though. For integrity-checking purposes I would have to rehash too, but would only require one hash for all sticks. Concerning your change proposal, adding an additional entry to Grub solves indeed the problem of risking a typo compared to having to type "nopersistent" and/or "toram" at every boot, to avoid undesired writes. However, it still requires to never forget interrupting the boot process. @mwhudson : Imho, the current situation of the 19.10 live image can be considered a bug, since it changes a default that has been there for more than a decade, and that's in many minds, that a live OS image is volatile. That's not due to a coding error, like most bugs are, but rather in comparison to usually expected behaviour, or "untold specification". Moreover, your reasons for wanting it to become a default are unclear, especially considering that the ones who want persistence could achieve that by passing a one-time option at boot, and being OK for subsequent boots, which obviously people who don't want persistence can't do, precisely because they don't want persistence. For these reasons it can be worth clarifying, outside of a bug process why not. I just started a thread : https://ubuntuforums.org/showthread.php?t=2431843 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851123 Title: Ubuntu 19.10 and focal live cloned create and mount casper-rw partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853200] Re: cpu features hle and rtm disabled for security are present in /usr/share/libvirt/cpu_map.xml
FYI: I got message from sbeattie that security will take a look at the backports for these qemu fixes. For libvirt we can check again then if the types got updated, and if no one did I can send something there as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853200 Title: cpu features hle and rtm disabled for security are present in /usr/share/libvirt/cpu_map.xml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] Re: 19.10 Boots into a black screen
Hey, I was able to find that the bug was fixed in v5.4-rc1. I haven't been able to find the commit that fixes the issue though. Trying to run: $ make -j`nproc` deb-pkg Gives me the error: make: *** No rule to make target 'nproc'. Stop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853489] Re: Ignoring the default NAT when using the virtio adapter
I made some more tests and found that ICMP packets are NAT'ed OK independent of the device model used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853489 Title: Ignoring the default NAT when using the virtio adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker
** Changed in: kernel-sru-workflow/automated-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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 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: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 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/1852306 Title: xenial/linux: 4.4.0-170.199 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
Hui Wang - I tried your proposed solution. Post rebooting the system freezes at login after I type in my password. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837889] Re: ndiswrapper 1.60-8 ADT test failure with linux 5.3.0-0.1
** Patch added: "fix for bionic" https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1837889/+attachment/5307176/+files/ndiswrapper_1.60-6ubuntu0.2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837889 Title: ndiswrapper 1.60-8 ADT test failure with linux 5.3.0-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1837889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512322] Re: dpkg assert failure: dpkg: ../../src/packages.c:245: process_queue:
https://errors.ubuntu.com/problem/07b782dcfeb6404740f227f16789748f68ff9b8b shows no instances post 18.10, and there are no other similar crash signatures shown on https://errors.ubuntu.com/?package=dpkg=week, so I'm going to presume this is resolved for 19.04 and later. ** Changed in: dpkg (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512322 Title: dpkg assert failure: dpkg: ../../src/packages.c:245: process_queue: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1512322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848588] Re: ndiswrapper 1.60-8ubuntu1 ADT test failure with linux 5.4.0-1.2
** Also affects: ndiswrapper (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ndiswrapper (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: ndiswrapper (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/1848588 Title: ndiswrapper 1.60-8ubuntu1 ADT test failure with linux 5.4.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1848588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837889] Re: ndiswrapper 1.60-8 ADT test failure with linux 5.3.0-0.1
** Also affects: ndiswrapper (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: + [Impact] + ndiswrapper-dkms won't build with linux-hwe-edge 5.3 kernels. + + [Test case] + Build the dkms successfully. + Install linux-hwe-edge, then install ndiswrapper-dkms. + + [Regression potential] + It might fail to build with older kernels. Test that it builds with older kernels as well. + + -- + Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/n/ndiswrapper/20190724_125316_ead1d@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/n/ndiswrapper/20190724_125316_ead1d@/log.gz ** Changed in: ndiswrapper (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: ndiswrapper (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/1837889 Title: ndiswrapper 1.60-8 ADT test failure with linux 5.3.0-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1837889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853614] Re: System stuck in reboot loop on AMD EPYC 7542 32-Core Processor
I am seeing this too on an AMD EPYC 7352 24-Core processor. Removing amd64-microcode 3.20191021.1ubuntu0.18.04.2 fixed the cyclic reboot issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853614 Title: System stuck in reboot loop on AMD EPYC 7542 32-Core Processor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1853614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853614] Re: System stuck in reboot loop on AMD EPYC 7542 32-Core Processor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: amd64-microcode (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/1853614 Title: System stuck in reboot loop on AMD EPYC 7542 32-Core Processor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1853614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512322] Re: dpkg assert failure: dpkg: ../../src/packages.c:245: process_queue:
** Changed in: dpkg (Ubuntu Bionic) Status: Fix Released => Triaged ** Changed in: dpkg (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512322 Title: dpkg assert failure: dpkg: ../../src/packages.c:245: process_queue: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1512322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852233] Re: disco/linux-raspi2: 5.0.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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: 1852253 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 15. November 2019 08:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED certification-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/1852233 Title: disco/linux-raspi2: 5.0.0-1023.24 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
