[Bug 1828084] Re: Kernel modules generated incorrectly when system is localized to a non-English language
https://lists.ubuntu.com/archives/kernel-team/2019-June/101708.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828084 Title: Kernel modules generated incorrectly when system is localized to a non-English language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834570] [NEW] kdiff3 does not work with remote sftp files
Public bug reported: Kdiff3 in Ubuntu 19.04 (v. 1.7.90-3) cannot compare files with remote addresses sftp://: while it works well in Ubuntu 18.04 (kdiff3 v. 0.9.98-4). Remote address is changed to local one and only is kept in the input field after clicking Ok button. The kio itself works well with sftp files e.g. in krusader. The comparison of the remote files in kdiff3 does not work also in case of action "Compare files" in kursader. ** Affects: kdiff3 (Ubuntu) Importance: Undecided Status: New ** Tags: kdiff3 kio sftp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834570 Title: kdiff3 does not work with remote sftp files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/1834570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833470] Re: ca0132 audio in Ubuntu 19.04 only after Windows 10 started
Probably because of this: [3.768667] snd_hda_intel :00:1f.3: Direct firmware load for ctefx-r3di.bin failed with error -2 I've raised the issue to the developer, stay tuned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833470 Title: ca0132 audio in Ubuntu 19.04 only after Windows 10 started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834568] Re: gdm fails to start on nvidia based systems on cosmic
*** This bug is a duplicate of bug 1798790 *** https://bugs.launchpad.net/bugs/1798790 Found this bug to be a copy of https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790. ** This bug has been marked a duplicate of bug 1798790 Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system (and setting WaylandEnable=false fixes it) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834568 Title: gdm fails to start on nvidia based systems on cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1834568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798790] Re: Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system (and setting WaylandEnable=false fixes it)
I also have this issue, but I discovered if I pressed Alt+F{N>2} then
Alt+F1 gdm boots immediatly.
I opemed a bug here,
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1834568 but I will
close it now that I found this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798790
Title:
Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia
system (and setting WaylandEnable=false fixes it)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1798790/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834561] Re: Don't link to 64-arphic-uming.conf
This bug was fixed in the package fonts-arphic-uming - 0.2.20080216.2-10ubuntu2 --- fonts-arphic-uming (0.2.20080216.2-10ubuntu2) eoan; urgency=low * debian/fonts-arphic-uming.links: - Disable 64-arphic-uming.conf by dropping the symlink to it, since the file isn't compatible with the 69-language-selector-zh-*.conf files (LP: #1834561). -- Gunnar Hjalmarsson Fri, 28 Jun 2019 06:53:00 +0200 ** Changed in: fonts-arphic-uming (Ubuntu) Status: In Progress => 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/1834561 Title: Don't link to 64-arphic-uming.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-uming/+bug/1834561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834568] [NEW] gdm fails to start on nvidia based systems on cosmic
Public bug reported:
Hello,
After upgrading to Cosmic Cuttlefish yesterday when I came to reboot gdm
seemingly was unable to start. There was not much in the logs, and after
much tinkering I discovered that after the Ubuntu splash screen if I
pressed Alt + F{N>1} then pressed Alt+F1 gdm would immediatly start up.
But if I left it to load as normal, it would fall into a stalled state
where I am forced to reboot.
If you need any diagnostics please don't hisitate to ask.
Prior to discovering this work around I checked the logs using
`journalctl -xb` but was unable to see anything related to GDM, so it
may not be that but this is the configuration I have:
- Nvidia RTX 2080Ti
- Nvidia 430 drivers from nvidia ppa
- Wayland enabled
- Cosmic Cuttlefish 18.10
This bug is not present when I disable wayland.
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Hello,
After upgrading to Cosmic Cuttlefish yesterday when I came to reboot gdm
seemingly was unable to start. There was not much in the logs, and after
much tinkering I discovered that after the Ubuntu splash screen if I
- pressed Alt + F{N<1} then pressed F1 gdm would immediatly start up.
+ pressed Alt + F{N>1} then pressed F1 gdm would immediatly start up.
But if I left it to load as normal, it would fall into a stalled state
where I am forced to reboot.
If you need any diagnostics please don't hisitate to ask.
Prior to discovering this work around I checked the logs using
`journalctl -xe` but was unable to see anything related to GDM, so it
may not be that but this is the configuration I have:
- Nvidia RTX 2080Ti
- Nvidia 430 drivers from nvidia ppa
- Wayland enabled
- Cosmic Cuttlefish 18.10
This bug is not present when I disable wayland.
** Description changed:
Hello,
After upgrading to Cosmic Cuttlefish yesterday when I came to reboot gdm
seemingly was unable to start. There was not much in the logs, and after
much tinkering I discovered that after the Ubuntu splash screen if I
- pressed Alt + F{N>1} then pressed F1 gdm would immediatly start up.
+ pressed Alt + F{N>1} then pressed Alt+F1 gdm would immediatly start up.
But if I left it to load as normal, it would fall into a stalled state
where I am forced to reboot.
If you need any diagnostics please don't hisitate to ask.
Prior to discovering this work around I checked the logs using
`journalctl -xe` but was unable to see anything related to GDM, so it
may not be that but this is the configuration I have:
- Nvidia RTX 2080Ti
- Nvidia 430 drivers from nvidia ppa
- Wayland enabled
- Cosmic Cuttlefish 18.10
This bug is not present when I disable wayland.
** Description changed:
Hello,
After upgrading to Cosmic Cuttlefish yesterday when I came to reboot gdm
seemingly was unable to start. There was not much in the logs, and after
much tinkering I discovered that after the Ubuntu splash screen if I
pressed Alt + F{N>1} then pressed Alt+F1 gdm would immediatly start up.
But if I left it to load as normal, it would fall into a stalled state
where I am forced to reboot.
If you need any diagnostics please don't hisitate to ask.
Prior to discovering this work around I checked the logs using
- `journalctl -xe` but was unable to see anything related to GDM, so it
+ `journalctl -xb` but was unable to see anything related to GDM, so it
may not be that but this is the configuration I have:
- Nvidia RTX 2080Ti
- Nvidia 430 drivers from nvidia ppa
- Wayland enabled
- Cosmic Cuttlefish 18.10
This bug is not present when I disable wayland.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834568
Title:
gdm fails to start on nvidia based systems on cosmic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1834568/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834521] Re: Devices
I can be a regression, please test older kernel version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834521 Title: Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613898] Re: Python easy_install fails when second of two python parts builds
** Project changed: snapcraft => extreme-citadel-208123 ** Changed in: extreme-citadel-208123 Assignee: Sergio Schvezov (sergiusens) => Rohit travels & tours (rtatnet2) ** Also affects: 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/1613898 Title: Python easy_install fails when second of two python parts builds To manage notifications about this bug go to: https://bugs.launchpad.net/extreme-citadel-208123/+bug/1613898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834550] Re: System hangs after play video from thunderbolt HDD and then S3
** Changed in: linux-oem (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834550 Title: System hangs after play video from thunderbolt HDD and then S3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1834550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
I am experimenting with disabling tso via ethtool now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829679] Re: Resolution stuck at 1024x768
If it still happens on older kernels then sounds like it's a hardware issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829679 Title: Resolution stuck at 1024x768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
I am seeing this on a Intel Corporation Ethernet Connection I218-V. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS" Linux server 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Jun 27 22:16:23 server kernel: [ 95.305441] [ cut here ] Jun 27 22:16:23 server kernel: [ 95.305445] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out Jun 27 22:16:23 server kernel: [ 95.305481] WARNING: CPU: 3 PID: 0 at /build/linux-jmOa1Y/linux-4.15.0/net/sched/sch_generic.c:323 dev_watchdog+0x221/0x230 Jun 27 22:16:23 server kernel: [ 95.305482] Modules linked in: dm_crypt algif_skcipher af_alg nls_iso8859_1 ppdev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw parport_pc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic parport snd_hda_intel acpi_pad snd_hda_codec snd_hda_core snd_hwdep mei_me mei snd_pcm shpchp lpc_ich mac_hid snd_timer snd soundcore 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 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd Jun 27 22:16:23 server kernel: [ 95.305591] glue_helper mxm_wmi cryptd i2c_algo_bit drm_kms_helper syscopyarea e1000e sysfillrect sysimgblt fb_sys_fops ahci ptp drm libahci pps_core wmi video Jun 27 22:16:23 server kernel: [ 95.305621] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.15.0-54-generic #58-Ubuntu Jun 27 22:16:23 server kernel: [ 95.305623] Hardware name: MSI MS-7817/H97M ECO (MS-7817), BIOS V26.8 02/18/2016 Jun 27 22:16:23 server kernel: [ 95.305629] RIP: 0010:dev_watchdog+0x221/0x230 Jun 27 22:16:23 server kernel: [ 95.305631] RSP: 0018:967b9eb83e58 EFLAGS: 00010286 Jun 27 22:16:23 server kernel: [ 95.305635] RAX: RBX: RCX: 0006 Jun 27 22:16:23 server kernel: [ 95.305638] RDX: 0007 RSI: 0092 RDI: 967b9eb96490 Jun 27 22:16:23 server kernel: [ 95.305641] RBP: 967b9eb83e88 R08: 0001 R09: 044c Jun 27 22:16:23 server kernel: [ 95.305643] R10: daca8f63f580 R11: R12: 0001 Jun 27 22:16:23 server kernel: [ 95.305646] R13: 967b80934000 R14: 967b80934478 R15: 967b81020880 Jun 27 22:16:23 server kernel: [ 95.305650] FS: () GS:967b9eb8() knlGS: Jun 27 22:16:23 server kernel: [ 95.305653] CS: 0010 DS: ES: CR0: 80050033 Jun 27 22:16:23 server kernel: [ 95.305655] CR2: 555b6574ea28 CR3: 00025a40a006 CR4: 001606e0 Jun 27 22:16:23 server kernel: [ 95.305658] Call Trace: Jun 27 22:16:23 server kernel: [ 95.305662] Jun 27 22:16:23 server kernel: [ 95.305671] ? dev_deactivate_queue.constprop.33+0x60/0x60 Jun 27 22:16:23 server kernel: [ 95.305678] call_timer_fn+0x30/0x130 Jun 27 22:16:23 server kernel: [ 95.305683] run_timer_softirq+0x3fb/0x450 Jun 27 22:16:23 server kernel: [ 95.305689] ? ktime_get+0x43/0xa0 Jun 27 22:16:23 server kernel: [ 95.305697] ? lapic_next_deadline+0x26/0x30 Jun 27 22:16:23 server kernel: [ 95.305705] __do_softirq+0xe4/0x2bb Jun 27 22:16:23 server kernel: [ 95.305713] irq_exit+0xb8/0xc0 Jun 27 22:16:23 server kernel: [ 95.305718] smp_apic_timer_interrupt+0x79/0x130 Jun 27 22:16:23 server kernel: [ 95.305723] apic_timer_interrupt+0x84/0x90 Jun 27 22:16:23 server kernel: [ 95.305725] Jun 27 22:16:23 server kernel: [ 95.305735] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 Jun 27 22:16:23 server kernel: [ 95.305737] RSP: 0018:a32c41933e68 EFLAGS: 0246 ORIG_RAX: ff11 Jun 27 22:16:23 server kernel: [ 95.305742] RAX: 967b9eba2840 RBX: 001630a50a51 RCX: 001f Jun 27 22:16:23 server kernel: [ 95.305744] RDX: 001630a50a51 RSI: fffca1795958 RDI: Jun 27 22:16:23 server kernel: [ 95.305747] RBP: a32c41933ea8 R08: 0ee2 R09: 08f8 Jun 27 22:16:23 server kernel: [ 95.305749] R10: a32c41933e38 R11: 0edf R12: 967b9ebacc00 Jun 27 22:16:23 server kernel: [ 95.305752] R13: 0005 R14: b3d71e38 R15: Jun 27 22:16:23 server kernel: [ 95.305760] ? cpuidle_enter_state+0x97/0x2f0 Jun 27 22:16:23 server kernel: [ 95.305767] cpuidle_enter+0x17/0x20 Jun 27 22:16:23 server kernel: [ 95.305774] call_cpuidle+0x23/0x40 Jun 27 22:16:23 server kernel: [ 95.305780] do_idle+0x18c/0x1f0 Jun 27 22:16:23 server kernel: [ 95.305786] cpu_startup_entry+0x73/0x80 Jun 27 22:16:23 server ker
[Bug 1834566] [NEW] Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298
Public bug reported: Unable to get system speakers working running 19.04. At max volume, sound is barely perceptible through headphones. Pavucontrol shows sounds is present, but no amount of adjustments makes a difference. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 3355 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 28 00:44:13 2019 InstallationDate: Installed on 2019-06-05 (22 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AHK.029.190425.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP930MBE-K04US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: Notebook 9 Series dmi.product.name: 930MBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK dmi.product.version: P02AHK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834566 Title: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834095] Re: update-grub fails on zfs with root and boot datasets when using mawk
This is committed in the grub ubuntu packaging branch, waiting for the next release handled by the foundation team (due to a FTBFS to debug + merge) ** Changed in: grub2 (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834095 Title: update-grub fails on zfs with root and boot datasets when using mawk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1834095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834528] Re: linux-ibm-gt: 4.15.0-1026.28 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1833987 - phase: Ready for Packaging - phase-changed: Thursday, 27. June 2019 20:24 UTC + phase: Packaging + phase-changed: Friday, 28. June 2019 05:12 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded 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/1834528 Title: linux-ibm-gt: 4.15.0-1026.28 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831840] Re: Support new ums-realtek device
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831840 Title: Support new ums-realtek device To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834511] Re: policyd-spf crashes on UnicodeEncodeError
That's correct. It was fixed in 2.0.0, but I'm not sure the fix would directly apply to 1.3.2. I've targeted the bug appropriately for 16.04. Perhaps someone involved in Ubuntu development will take a look. ** Also affects: pypolicyd-spf (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: pypolicyd-spf (Ubuntu Xenial) Status: New => Triaged ** Changed in: pypolicyd-spf (Ubuntu) Status: New => Fix Released ** Changed in: pypolicyd-spf (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/1834511 Title: policyd-spf crashes on UnicodeEncodeError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pypolicyd-spf/+bug/1834511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553688] Re: Lenovo Y700-17ISK: mmc0: Unknown controller version (3)
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc6/ Particularly, commit 0086fc217d5d7ac2939c500733d1d046b9ac5012 Author: ernest.zhang Date: Mon Jul 16 14:26:54 2018 +0800 mmc: sdhci: Add support for O2 hardware tuning Add hardware tuning function instead of software tuning because O2/Bayhub SD host controller support hardware tuning. Signed-off-by: ernest.zhang Acked-by: Adrian Hunter Signed-off-by: Ulf Hansson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553688 Title: Lenovo Y700-17ISK: mmc0: Unknown controller version (3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834528] Re: linux-ibm-gt: 4.15.0-1026.28 -proposed tracker
** Summary changed: - linux-ibm-gt: -proposed tracker + linux-ibm-gt: 4.15.0-1026.28 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834528 Title: linux-ibm-gt: 4.15.0-1026.28 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
** Also affects: python-pygraphviz (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: python-pygraphviz (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: python-pygraphviz (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: python-pygraphviz (Ubuntu Cosmic) 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/1834379 Title: armhf Bionic python3-pygraphviz package errors for simple use case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833018] Re: After Installing Updates, system fails to boot on first try
Ah, please try kernel parameter "nopti". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833018 Title: After Installing Updates, system fails to boot on first try To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812159] Re: q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels
** Changed in: linux-kvm (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-kvm (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-kvm (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux-kvm (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812159 Title: q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834561] [NEW] Don't link to 64-arphic-uming.conf
Public bug reported:
Since Ubuntu 18.04 the intended default Chinese font for serif is "Noto
Serif CJK {SC,TC}".
https://launchpad.net/ubuntu/+source/language-selector/0.182
At the same time we install the fonts-arphic-uming package for Chinese
users. fonts-arphic-uming installs the fontconfig configuration file 64
-arphic-uming.conf. That file includes strong bindings to "AR PL UMing"
and "DejaVu Serif" which conflict with the Ubuntu specific 69-language-
selector-zh-*.conf files.
Example:
$ LC_CTYPE=zh_CN.UTF-8 fc-match serif
uming.ttc: "AR PL UMing CN" "Light"
I would have expected that command to return:
NotoSerifCJK-Regular.ttc: "Noto Serif CJK SC" "Regular"
The issue was brought to my attention through the Ask Ubuntu question
.
Given that we handle the font configuration for Chinese users via Ubuntu
specific files, 64-arphic-uming.conf does not fit well on Ubuntu.
Dropping the related symlink in /etc/fonts/conf.d appears to be a
reasonable solution.
** Affects: fonts-arphic-uming (Ubuntu)
Importance: Medium
Assignee: Gunnar Hjalmarsson (gunnarhj)
Status: 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/1834561
Title:
Don't link to 64-arphic-uming.conf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-uming/+bug/1834561/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834559] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1834559 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834559 Title: Touchpad stopped working after minor update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
So this "fix" seems to cause Kernels released with zesty (and newer) keep the monitor always ON. No blanking, and no power down either. Before this fix, a clean install of Ubuntu server would signal the monitor to sleep/standby after a short while. Now the default behavior is to leave the monitor always on, wasting power. While blanking itself should be negligible to power savings and monitor longevity, sleep states are still an important feature. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767568] Re: Console DPMS Nonfunctional in Ubuntu Server 18.04
The following "fix" seems to be the cause of this bug. Link below: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832299] Re: Add new sound card PCIID into the alsa driver
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: Fix Committed ** Also affects: linux-oem (Ubuntu Eoan) Importance: Undecided Status: Fix Released ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832299 Title: Add new sound card PCIID into the alsa driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1832299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826636] Re: Xorg freeze
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826636 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1826636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819949] Re: ZSH not working
[Expired for zsh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: zsh (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819949 Title: ZSH not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1819949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826606] Re: mouse sometimes only works after system reboot
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826606 Title: mouse sometimes only works after system reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1826606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826713] Re: arret systeme, mise en veille
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826713 Title: arret systeme, mise en veille To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1826713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826732] Re: package shim-signed 1.33.1~16.04.5+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.] ** Changed in: shim-signed (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826732 Title: package shim-signed 1.33.1~16.04.5+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1826732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834559] [NEW] Touchpad stopped working after minor update
Public bug reported: Touchpad stopped working after a minor OS update. I was unable to move the cursor even before rebooting the machine. The output of /proc/bus/input/devices is attached and, as you can see, does not contain my Synaptics touchpad. ** Affects: linux (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/1834559 Title: Touchpad stopped working after minor update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809843] Re: sky2 ethernet card link not up after suspend
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809843 Title: sky2 ethernet card link not up after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834554] Re: [nvidia] Screen displays dynamic corruptions
Yeah, I considered that and I guess it's a possibility, but if it's the case it's only exercised by the 18.04 X code, this has never appeared prior to the installation of 18.04 a couple of days ago (was previously running 16.04). I don't recall seeing it while running the live usb either, but I can check that when I'm back at the machine. The other things that makes me feel like it's a software issue is the interdependence of the effect and other activity on the system as mentioned: typing changes the cadence of the updates as does disk i/o; I would not expect that behaviour if it were graphics card RAM failure. It almost feels like someone is writing a buffer in an incorrect location, but the allocation of the screen memory changes with resolution change and this can randomly choose somewhere that's not being abused like that (random stab in the dark). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834554 Title: [nvidia] Screen displays dynamic corruptions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1834554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834558] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1834558 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834558 Title: intel_idle enable in ICL To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833410] Re: idle-page oopses when accessing page frames that are out of range
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833410 Title: idle-page oopses when accessing page frames that are out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834558] [NEW] intel_idle enable in ICL
Public bug reported: Description: Support for intel_idle on Ice Lake (client) Target Release: 19.10 Target Kernel: 5.3 ** Affects: intel Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel-kernel-19.10 ** Also affects: linux (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/1834558 Title: intel_idle enable in ICL To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834554] Re: [nvidia] Screen displays dynamic corruptions
I mean if it is a hardware problem then it might come and go depending on the resolution or which area of graphics memory the driver is using. But when the problem does appear, if it keeps appearing around the same area then that would suggest a hardware fault. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834554 Title: [nvidia] Screen displays dynamic corruptions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1834554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832693] Re: System auto suspend again during resuming
** Changed in: oem-priority 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/1832693 Title: System auto suspend again during resuming To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1832693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834554] Re: [nvidia] Screen displays dynamic corruptions
If the location and shape of the problem never changes then one possible explanation would be small areas of failing RAM on the graphics card. It might also be a software bug of course. ** Summary changed: - Screen displays dynamic corruptions + [nvidia] Screen displays dynamic corruptions ** Tags added: nvidia ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-340 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834554 Title: [nvidia] Screen displays dynamic corruptions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1834554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829829] Re: Ubuntu CI has been flaky for a week
In the meantime, I brought arm64 back almost as soon as https://salsa.debian.org/systemd-team/systemd/merge_requests/34 was merged. It looks promising except that the "upstream" test is flaky there as well. It'd be great to turn it off on Ubuntu CI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829829 Title: Ubuntu CI has been flaky for a week To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834554] Re: Screen displays dynamic corruptions
Screen shots of the corruption do not work as the screen shot tool appears to overwrite the corruption. Video capture does work. ** Attachment added: "Video capture of screen corruption" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834554/+attachment/5273854/+files/screen-speckles.ogv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834554 Title: Screen displays dynamic corruptions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834554] [NEW] Screen displays dynamic corruptions
Public bug reported: Regularly the screen displays corruptions that change depending on disk i/o, keyboard/mouse and other system activity. The screen corruptions do not appear on each session and can be removed by selecting an alternative resolution and then changing back (or reverting without accepting the change). The location of the corruptions is stereotypical and always has the same shape characteristics. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Jun 28 12:14:17 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 4.18.0-15-generic, x86_64: installed nvidia-340, 340.107, 4.18.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT200b [GeForce GTX 275] [10de:05e6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology GT200b [GeForce GTX 275] [10b0:0801] Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 470/480/570/580] [1458:22fc] InstallationDate: Installed on 2019-06-25 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-24-generic root=UUID=b92b7098-365d-445a-b980-7fe3bc3b73da ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0504 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0504:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834554 Title: Screen displays dynamic corruptions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157490] Re: Fullscreen with two monitors
Interesting project; thanks for sharing dreamer_ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157490 Title: Fullscreen with two monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dosbox/+bug/1157490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834439] Re: designated object in OVAL definition may be wrong
this issue is unrelated to the actual linux operating system but the OVAL definition ubuntu security team has provided. hence the obvious omission of log files. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834439 Title: designated object in OVAL definition may be wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Sorry, I forgot to mention that after editing that file you need to run: sudo update-grub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831751] Re: rtlwifi: aggressive memory leak
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831751 Title: rtlwifi: aggressive memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1831751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834262] Re: i915: Secondary screen shows a bluish color shift. White turns into a turquoise.
Please try turning OFF the colour profile switch in: Settings > Devices > Colour -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834262 Title: i915: Secondary screen shows a bluish color shift. White turns into a turquoise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834493] Re: Update mutter to 3.32.2+git20190626
** Summary changed: - Update to 3.32.2+git20190626 + Update mutter to 3.32.2+git20190626 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834493 Title: Update mutter to 3.32.2+git20190626 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1834493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816468] Re: Acceleration cinder - glance with ceph not working
Reviewed: https://review.opendev.org/664512 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b4b47a59c7ff1d60e69dbdea07de9163948cb680 Submitter: Zuul Branch:stable/stein commit b4b47a59c7ff1d60e69dbdea07de9163948cb680 Author: Edward Hope-Morley Date: Thu Jun 6 12:26:26 2019 +0100 Fix python3 compatibility of rbd get_fsid In py3 librados's get_fsid() function returns a binary string which breaks comparison when compared with the same value as a string. This is currently breakin the logic that compares ceph cluster fsids when deciding whether the image used to boot an instance is cow-clonable. Change-Id: I79b40ca40400c67b0805926096317afd875ffabb Closes-Bug: #1816468 (cherry picked from commit e8b6b0bc78ec229803d1d27f8a4706e2c425bd77) ** Changed in: cloud-archive/stein Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816468 Title: Acceleration cinder - glance with ceph not working To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1816468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834517] Re: Update gnome-shell to 3.32.2
** Summary changed: - Update to 3.32.2 + Update gnome-shell to 3.32.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834517 Title: Update gnome-shell to 3.32.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834550] [NEW] System hangs after play video from thunderbolt HDD and then S3
Public bug reported: [Impact] System hangs after played video from TBT storage, and then suspend the system. It enters suspend correctly, but hangs during waking up. [Fix] There are 2 commits in upstream which fix this issue. 95c80bc6952b PCI/PME: Fix hotplug/sysfs remove deadlock in pcie_pme_remove() 3943af9d01e9 PCI: pciehp: Ignore Link State Changes after powering off a slot [Test] Verified on below thunderbolt interface with thunderbolt HDD 01:00.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev 02) [Regression Potential] Low, both commits have been SRU to Ubuntu Disco 5.0 kernel through stable update, and the fix on remove functions are small and reasonable. ** Affects: linux-oem (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: Invalid ** Affects: linux-oem (Ubuntu Bionic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-oem (Ubuntu Bionic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem (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/1834550 Title: System hangs after play video from thunderbolt HDD and then S3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1834550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001
** Attachment added: "noto-sans-cjk-news.txt"
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+attachment/5273833/+files/noto-sans-cjk-news.txt
** Description changed:
- This ships the latest Noto CJK fonts to the users in good time before
- the 19.10 release, and will help with the progress of the meta bug
- #1828884 which is about desired changes due to the new Japanese era
- Reiwa. Verson 2.001 includes glyphs for Reiwa.
+ [Impact]
+
+ Due to Japan's new era, a Unicode character has been introduced which
+ represents the era name (Reiwa) as one single character. The version of
+ fonts-noto-cjk in the stable releases does not support the new
+ character, which is what motivates a backport of the eoan fonts-noto-cjk
+ version. The proposed SRU is in line with the meta bug #1828884.
+
+ This means an upgrade of Noto Sans CJK from version 1.004 to 2.001, and
+ it will bring a few other changes in the bargain. Most notably a new set
+ of Hong Kong fonts has been added to the previous ones (simplified and
+ traditional Chinese, Japanese, and Korean). Attached to this bug report
+ please see the file noto-sans-cjk-news.txt with upstream's detailing of
+ the changes.
+
+ [Test Case]
+
+ Install from {bionic,cosmic,disco}-proposed:
+
+ - fonts-noto-cjk
+ - fonts-noto-cjk-extra
+ - language-selector-common
+ - language-selector-gnome
+
+ 1. The Reiwa glyph
+ --
+ Visit http://people.ubuntu.com/~gunnarhj/square-era-name-reiwa.html
+ and find that a proper Japanese character, and not a tofu, is shown.
+
+ 2. Presence and configuration of HK fonts
+ -
+ (This also bears on the language-selector changes.)
+
+ * Install the Hong Kong locale:
+
+ sudo locale-gen zh_HK.UTF-8
+
+ * Run this command:
+
+ LC_CTYPE=zh_HK.UTF-8 fc-match
+
+ and find that it returns:
+
+ NotoSansCJK-Regular.ttc: "Noto Sans CJK HK" "Regular"
+
+ 3. General use
+ --
+ Browse some web sites with Chinese, Japanese or Korean contents and
+ confirm that the upgrade does not cause any font rendering issues.
+
+ [Regression Potential]
+
+ This somewhat aggressive SRU proposal is based on trust in Google and
+ Adobe as solid upstream providers of these fonts. Version 2.000 (which
+ includes most of the changes) was released in November 2018, while
+ version 2.001 (with the Reiwa glyph) was released in April 2019. Serious
+ problems should have been known by now. The upstream bug tracker gives
+ no cause for concern:
+
+ https://github.com/googlefonts/noto-cjk/issues
+
+ It may be worth mentioning that the fonts are provided as OTC files, and
+ we don't compile those files ourselves. Hence just patching the new
+ glyph would not be a practicable option.
+
+ It would be easy to reverse this upgrade, if regressions would be
+ reported. Basically we are talking about 7 files on the file system.
+
+ [Other Info re. eoan]
Since Debian hasn't packaged this yet, we have created a modified
- .orig.tar.xz file where 7 .ttc files (plus NEWS and HISTORY) differs
- from version 1:20181130+repack1-1~exp1, i.e. the latest Debian upload.
+ .orig.tar.xz file where 7 .ttc files (plus NEWS and HISTORY) differ from
+ version 1:20181130+repack1-1~exp1, i.e. the latest Debian upload.
There is no other Ubuntu/Debian delta, so as soon as Debian has catched
up, it will be fine to start syncing again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834406
Title:
Upgrade Noto Sans CJK fonts to version 2.001
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833299] Re: lasso includes "Destination" attribute in SAML AuthnRequest populated with SP AssertionConsumerServiceURL when ECP workflow is used which leads to IdP-side errors
The attachment "0001-PAOS-Do-not-populate-Destination-attribute.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** 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/1833299 Title: lasso includes "Destination" attribute in SAML AuthnRequest populated with SP AssertionConsumerServiceURL when ECP workflow is used which leads to IdP-side errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lasso/+bug/1833299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833299] Re: lasso includes "Destination" attribute in SAML AuthnRequest populated with SP AssertionConsumerServiceURL when ECP workflow is used which leads to IdP-side errors
https://dev.entrouvert.org/issues/34409 ** Bug watch added: dev.entrouvert.org/issues #34409 https://dev.entrouvert.org/issues/34409 ** Patch added: "0001-PAOS-Do-not-populate-Destination-attribute.patch" https://bugs.launchpad.net/ubuntu/+source/lasso/+bug/1833299/+attachment/5273832/+files/0001-PAOS-Do-not-populate-Destination-attribute.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833299 Title: lasso includes "Destination" attribute in SAML AuthnRequest populated with SP AssertionConsumerServiceURL when ECP workflow is used which leads to IdP-side errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lasso/+bug/1833299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831751] Re: rtlwifi: aggressive memory leak
** Changed in: linux Status: Unknown => 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/1831751 Title: rtlwifi: aggressive memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1831751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
** Patch added: "deb.diff" https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+attachment/5273831/+files/deb.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834379 Title: armhf Bionic python3-pygraphviz package errors for simple use case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
** Description changed:
[Impact]
python3-pygraphviz does not work for even simple use cases on armhf
Bionic. See error output in Test Case section from adding an edge to a
graph.
This package is currently being used as a dependency of ROS2, which is
now including armhf as a target platform. The functionality that depends
on this package fails to run.
Conclusion from below testing is that the current package is somehow
corrupted.
A no-change rebuild in ppa:emersonknapp/ppa works properly on armhf.
[Test Case]
Using the following test file, and running python3 test.py, the program
raises an error. However program exits with no output as expected on
x86_64 and aarch64
```
# test.py
#!/usr/bin/env python3
import pygraphviz
graph = pygraphviz.AGraph()
graph.add_node('foo')
graph.add_node('bar')
graph.add_edge('foo', 'bar')
```
Error seen
```
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1561, in
__new__
nh = gv.agnode(graph.handle, n.encode(graph.encoding), _Action.find)
KeyError: 'agnode: no key'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "test.py", line 8, in
graph.add_edge('foo', 'bar')
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 478, in
add_edge
e = Edge(self, eh=eh)
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1625, in
__new__
s = Node(graph, nh=source)
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1563, in
__new__
raise KeyError("Node %s not in graph." % n)
KeyError: 'Node None not in graph.'
```
-
[Regression Potential]
- This package doesn't currently seem to work at all, so I don't see how
- it could get worse.
+ This is a no-change rebuild, regression potential is very low.
[Other Info]
If I upgrade to 1.5 via pip after installing the apt dependency
libgraphviz-dev, this same snippet works on all of these platforms.
It also works if I install pygraphviz 1.4rc1 from pip. Also, it seems to
work with the debian package python3-pygraphviz 1.4 from cosmic. As far
as I can tell, there are no differences between the cosmic and the
bionic packages, other than it was rebuilt for Python 3.7.
Here's a summary:
Bionic1.4~rc1 Debian Broken
Cosmic1.4~rc1 Debian Works
Disco 1.5 Debian Works
Bionic1.4~rc1 pip Works
Bionic1.5 pip Works
And one more data point; if I pull down the debian sources (apt-get
source python3-pygraphviz ; apt-get build-dep python3-pygraphviz), build
with no modifications (debuild -uc -us), and then install (dpkg -i
python3-pygraphviz_1.4~rc1-1build2_armhf.deb), it works just fine.
From all of this, I can only conclude that the Ubuntu Bionic armhf
debian package is somehow corrupt. Perhaps a rebuild of the package
would solve the problem.
-
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python3-pygraphviz 1.4~rc1-1build2
ProcVersionSignature: Ubuntu 4.15.0-1041.43-aws 4.15.18
Uname: Linux 4.15.0-1041-aws aarch64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: armhf
Date: Wed Jun 26 22:23:47 2019
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SourcePackage: python-pygraphviz
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834379
Title:
armhf Bionic python3-pygraphviz package errors for simple use case
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
diff -Nru python-pygraphviz-1.4~rc1/debian/changelog python-pygraphviz-1.4~rc1/debian/changelog --- python-pygraphviz-1.4~rc1/debian/changelog 2017-08-05 02:38:34.0 -0700 +++ python-pygraphviz-1.4~rc1/debian/changelog 2019-06-27 17:08:25.0 -0700 @@ -1,3 +1,9 @@ +python-pygraphviz (1.4~rc1-1build3) bionic; urgency=medium + + * No change rebuild (LP: #1834379) + + -- Emerson Knapp (aubdsk) Thu, 27 Jun 2019 17:08:25 -0700 + python-pygraphviz (1.4~rc1-1build2) artful; urgency=medium * No change rebuild to drop Python 3.5 support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834379 Title: armhf Bionic python3-pygraphviz package errors for simple use case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832299] Re: Add new sound card PCIID into the alsa driver
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832299 Title: Add new sound card PCIID into the alsa driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1832299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
** Description changed:
+ [Impact]
+ python3-pygraphviz does not work for even simple use cases on armhf Bionic.
See error output in Test Case section from adding an edge to a graph.
+
+ This package is currently being used as a dependency of ROS2, which is
+ now including armhf as a target platform. The functionality that depends
+ on this package fails
+
+ Conclusion from below testing is that the current package is somehow
+ corrupted.
+
+ A no-change rebuild in ppa:emersonknapp/ppa works properly on armhf.
+
+ [Test Case]
+
Using the following test file, and running python3 test.py, the program
raises an error. However program exits with no output as expected on
x86_64 and aarch64
```
# test.py
#!/usr/bin/env python3
import pygraphviz
graph = pygraphviz.AGraph()
graph.add_node('foo')
graph.add_node('bar')
graph.add_edge('foo', 'bar')
```
Error seen
```
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1561, in
__new__
nh = gv.agnode(graph.handle, n.encode(graph.encoding), _Action.find)
KeyError: 'agnode: no key'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "test.py", line 8, in
graph.add_edge('foo', 'bar')
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 478, in
add_edge
e = Edge(self, eh=eh)
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1625, in
__new__
s = Node(graph, nh=source)
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1563, in
__new__
raise KeyError("Node %s not in graph." % n)
KeyError: 'Node None not in graph.'
```
If I upgrade to 1.5 via pip after installing the apt dependency
libgraphviz-dev, this same snippet works on all of these platforms.
It also works if I install pygraphviz 1.4rc1 from pip. Also, it seems to
work with the debian package python3-pygraphviz 1.4 from cosmic. As far
as I can tell, there are no differences between the cosmic and the
bionic packages, other than it was rebuilt for Python 3.7.
Here's a summary:
Bionic1.4~rc1 Debian Broken
Cosmic1.4~rc1 Debian Works
Disco 1.5 Debian Works
Bionic1.4~rc1 pip Works
Bionic1.5 pip Works
And one more data point; if I pull down the debian sources (apt-get
source python3-pygraphviz ; apt-get build-dep python3-pygraphviz), build
with no modifications (debuild -uc -us), and then install (dpkg -i
python3-pygraphviz_1.4~rc1-1build2_armhf.deb), it works just fine.
From all of this, I can only conclude that the Ubuntu Bionic armhf
debian package is somehow corrupt. Perhaps a rebuild of the package
would solve the problem.
+ [Regression Potential]
+ This package doesn't currently seem to work at all, so I don't see how it
could get worse.
+
+
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python3-pygraphviz 1.4~rc1-1build2
ProcVersionSignature: Ubuntu 4.15.0-1041.43-aws 4.15.18
Uname: Linux 4.15.0-1041-aws aarch64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: armhf
Date: Wed Jun 26 22:23:47 2019
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SourcePackage: python-pygraphviz
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
[Impact]
python3-pygraphviz does not work for even simple use cases on armhf Bionic.
See error output in Test Case section from adding an edge to a graph.
This package is currently being used as a dependency of ROS2, which is
now including armhf as a target platform. The functionality that depends
- on this package fails
+ on this package fails to run.
Conclusion from below testing is that the current package is somehow
corrupted.
A no-change rebuild in ppa:emersonknapp/ppa works properly on armhf.
[Test Case]
Using the following test file, and running python3 test.py, the program
raises an error. However program exits with no output as expected on
x86_64 and aarch64
```
# test.py
#!/usr/bin/env python3
import pygraphviz
graph = pygraphviz.AGraph()
graph.add_node('foo')
graph.add_node('bar')
graph.add_edge('foo', 'bar')
```
Error seen
```
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1561, in
__new__
nh = gv.agnode(graph.handle, n.encode(graph.encoding), _Action.find)
KeyError: 'agnode: no key'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "test.py", line 8, in
graph.add_edge('foo', 'bar')
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 478, in
add_edge
e = Edge(self, eh=eh)
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1625, in
__new__
s = Node(graph, n
Re: [Bug 1834487] Re: Frequent crash at startup after upgrading intel-microcode package
Hello, Please Update the firmware (BIOS/UEFI) on your Asus computer. Asus did something on their firmware which requires the microcode update to be done by the BIOS/UEFI. Asus knows about it, and so does Intel. Supposedly, they're addressing it. Maybe a new microcode update (or for that matter, a new version of Asus firmware) will be more compatible. Until then, you will depend on Asus issuing bios/uefi updates (and you have to apply them to get the fixes). -- Henrique de Moraes Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834487 Title: Frequent crash at startup after upgrading intel-microcode package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1834487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Thanks for working on this and preparing the debdiffs. Has the debian package changed from interest to interest-noawait? Is there a bug in debian regarding 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/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828798] Re: Eletrical noise occurred when external headset enter powersaving mode on a DEll machine
** Tags added: erville som verification-done-bionic ** Tags removed: verification-needed-bionic ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828798 Title: Eletrical noise occurred when external headset enter powersaving mode on a DEll machine To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1828798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834248] Re: HDMI audio and AC3 audio output does not work in Intel NUC
Probably it is the graphic driver's problem. need to test different kernel versions to locate the problem. like kernel-v5.2-rc1/2/3 or v5.1-rc1/2/3 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834248 Title: HDMI audio and AC3 audio output does not work in Intel NUC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
Ok - I created a PPA and did a no-change rebuild (correctly to the best of my knowledge, this is my first time uploading to a PPA) Build: https://launchpad.net/~emersonknapp/+archive/ubuntu/ppa/+build/17197601 If I use that build, the test file works now. ``` add-apt-repository ppa:emersonknapp/ppa apt-get update apt-get install -y python3-pygraphviz python3 test.py ``` Seems pretty conclusive - what are the next steps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834379 Title: armhf Bionic python3-pygraphviz package errors for simple use case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833299] Re: lasso includes "Destination" attribute in SAML AuthnRequest populated with SP AssertionConsumerServiceURL when ECP workflow is used which leads to IdP-side errors
** Description changed: See comments on the bug: https://bugs.launchpad.net/charm-keystone-saml-mellon/+bug/1833134 Lasso is used by libapache2-mod-auth-mellon to create SAML messages. When ECP profile (http://docs.oasis-open.org/security/saml/Post2.0/saml- ecp/v2.0/cs01/saml-ecp-v2.0-cs01.pdf) is used it populates an AuthnRequest with the "Destination" attribute as follows: https://keystone.maas:5000/v3/OS-FEDERATION/identity_providers/samltestid/protocols/saml2/auth/mellon/paosResponse"; Consent="urn:oasis:names:tc:SAML:2.0:consent:current-implicit" SignType="0" SignMethod="0" ForceAuthn="false" IsPassive="false" AssertionConsumerServiceURL="https://keystone.maas:5000/v3/OS-FEDERATION/identity_providers/samltestid/protocols/saml2/auth/mellon/paosResponse";> - https://keystone.maas:5000/v3/OS-FEDERATION/identity_providers/samltestid/protocols/saml2/auth - http://www.w3.org/2000/09/xmldsig#";> + https://keystone.maas:5000/v3/OS-FEDERATION/identity_providers/samltestid/protocols/saml2/auth + http://www.w3.org/2000/09/xmldsig#";> - - This triggers the Destination attribute validation logic relevant for "HTTP Redirect Binding" only (per the spec, section 3.4.5.2), not SOAP or PAOS bindings (sections before 3.4). - http://docs.oasis-open.org/security/saml/v2.0/saml-bindings-2.0-os.pdf + This triggers the Destination attribute validation logic relevant for "HTTP Redirect" and "HTTP POST" bindings only (per the spec, sections 3.4.5.2 and 3.5.5.2), not SOAP or PAOS bindings (sections before 3.4). + http://docs.oasis-open.org/security/saml/v2.0/saml-bindings-2.0-os.pdf For example, Shibboleth IdP (samltest.id) errors out as follows as the Destination attribute was populated with an SP URL: 2019-06-18 16:54:25,435 - ERROR [org.opensaml.saml.common.binding.security.impl.ReceivedEndpointSecurityHandler:?] - Message Handler: SAML message intended destination endpoint 'https://keystone.maas:5000/v3/OS- FEDERATION/identity_providers/samltestid/protocols/saml2/auth/mellon/paosResponse' did not match the recipient endpoint 'https://samltest.id/idp/profile/SAML2/SOAP/ECP' For ECP it makes sense to avoid inclusion of the "Destination" attribute to AuthnRequest (see https://bugs.launchpad.net/charm-keystone-saml- mellon/+bug/1833134/comments/3). The attached patch is merely an illustration that not using Destination with ECP results in a successful authentication: https://bugs.launchpad.net/charm-keystone-saml-mellon/+bug/1833134/comments/2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833299 Title: lasso includes "Destination" attribute in SAML AuthnRequest populated with SP AssertionConsumerServiceURL when ECP workflow is used which leads to IdP-side errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lasso/+bug/1833299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823718] Re: Installation fails with Python3.7 SyntaxError on Ubuntu Disco
** Tags added: seg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823718 Title: Installation fails with Python3.7 SyntaxError on Ubuntu Disco To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1823718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833939] Re: linux-aws-edge: 4.18.0-1020.24~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833940 phase: Testing phase-changed: Thursday, 27. June 2019 20:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - 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/1833939 Title: linux-aws-edge: 4.18.0-1020.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830823] Re: Ubuntu image builds broken for powerpc on xenial
This bug was fixed in the package livecd-rootfs - 2.408.50 --- livecd-rootfs (2.408.50) xenial; urgency=medium * Actually, do not depend on snapd on powerpc as well. Snaps are not supported on this platform at all. (LP: #1830823) -- Łukasz 'sil2100' Zemczak Tue, 25 Jun 2019 22:54:10 +0200 ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Fix Committed => 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/1830823 Title: Ubuntu image builds broken for powerpc on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1830823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830064] Re: zfs-linux 0.7.12-1ubuntu5 ADT test failure with linux 5.2.0-0.1
** Changed in: zfs-linux (Ubuntu) Status: In Progress => 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/1830064 Title: zfs-linux 0.7.12-1ubuntu5 ADT test failure with linux 5.2.0-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1830064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834494] Re: latest bzip2 reports crc errors incorrectly
** Tags added: bionic ** Also affects: bzip2 (Ubuntu Bionic) 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/1834494 Title: latest bzip2 reports crc errors incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833950] Re: linux-hwe: 4.18.0-25.26~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833952 - phase: Promote to Proposed - phase-changed: Thursday, 27. June 2019 17:08 UTC + phase: Testing + phase-changed: Thursday, 27. June 2019 22:38 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress 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/1833950 Title: linux-hwe: 4.18.0-25.26~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Changed in: systemd (Debian) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810346] Re: VLC interface not displayed correctly
I also tested 18.04 again with another setup, still dual screen on a samsung TV, the vlc GUI is exageratly zoomed but still correctly visible and usable, not sure if they want it to be zoomed like that. ** Attachment added: "IdUAJtp.png" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+attachment/5273828/+files/IdUAJtp.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810346 Title: VLC interface not displayed correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
I edited that line in /etc/default/grub so it reads: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.dyndbg=+p" However, I don't see any changes in dmesg after I reboot: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=e5e53ee1-0a10-48ee-8f7c-1d553ecc5607 ro quiet splash vt.handoff=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833930] Re: linux-hwe-edge: 5.0.0-20.21~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833934 phase: Testing phase-changed: Thursday, 27. June 2019 21:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - 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/1833930 Title: linux-hwe-edge: 5.0.0-20.21~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834030] Re: linux: 4.4.0-154.181 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates 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 backports: bug 1834028 (trusty/linux-aws), bug 1834029 (trusty/linux-lts-xenial) derivatives: bug 1834018 (pc-kernel), bug 1834020 (linux-aws), bug 1834021 (linux-kvm), bug 1834024 (linux-raspi2), bug 1834026 (linux-snapdragon), bug 1834027 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Release - phase-changed: Thursday, 27. June 2019 20:26 UTC + phase: Holding before Security + phase-changed: Thursday, 27. June 2019 22:04 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published 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/1834030 Title: linux: 4.4.0-154.181 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834499] Re: [linux-azure] Block Layer Commits Requested in Azure Kernels
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834499 Title: [linux-azure] Block Layer Commits Requested in Azure Kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834030] Re: linux: 4.4.0-154.181 -proposed tracker
This bug was fixed in the package linux - 4.4.0-154.181 --- linux (4.4.0-154.181) xenial; urgency=medium * linux: 4.4.0-154.181 -proposed tracker (LP: #1834030) * CVE-2019-11478 - tcp: refine memory limit test in tcp_fragment() * CVE-2019-11479 - SAUCE: tcp: add tcp_min_snd_mss sysctl - SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing() -- Khalid Elmously Tue, 25 Jun 2019 00:36:38 -0400 ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11478 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11479 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834030 Title: linux: 4.4.0-154.181 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833930] Re: linux-hwe-edge: 5.0.0-20.21~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Invalid ** 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: 1833934 - phase: Promote to Proposed - phase-changed: Thursday, 27. June 2019 15:06 UTC + phase: Testing + phase-changed: Thursday, 27. June 2019 21:37 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + 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/1833930 Title: linux-hwe-edge: 5.0.0-20.21~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (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/1827948 Title: Use libreoffice-style-breeze as the default icon theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1827948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764414] Re: LibreOffice’s spin buttons have the wrong background
It's still affecting Ambiance in: Version: 6.2.4.2 Build ID: 1:6.2.4-0ubuntu0.18.04.1~lo1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764414 Title: LibreOffice’s spin buttons have the wrong background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1764414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834386] Re: Ebooks thumbnails fail in Nemo over SMB
I know it looks like it does not recognise the image format, but using this command fixes the issue, in fact i added this command to my /etc/rc.local so i can keep apparmor up and running, after that it generates all the thumbnails correctly for the differents formats of ebooks, and it doesn't display this error message anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834386 Title: Ebooks thumbnails fail in Nemo over SMB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1834386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767568] Re: Console DPMS Nonfunctional in Ubuntu Server 18.04
Summary of my tests WORKS: * Ubuntu 16.04.6 LTS (xenial), clean install and after updates as well * Ubuntu 16.10 (Yakkety Yak), clean install and after updates as well FAILS: (no DPMS) * Ubuntu 16.04.6 LTS (xenial), with HWE kernel * Ubuntu 17.04 (Zesty Zapus) I tried some APT pinning to test kernel combinations: WORKS: * Ubuntu 17.04 (Zesty Zapus), with kernel from 16.10 using apt pinning. FAILS: * Ubuntu 16.10 (Yakkety Yak), with kernel from 17.04 using apt pinning. So I'm convinced it's something in the kernel package. Could be the options the kernels are compiled with, or something upstream? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833982] Re: linux-azure-edge: 4.15.0.1049.32 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates 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: 1834091 - phase: Release - phase-changed: Thursday, 27. June 2019 20:21 UTC + phase: Holding before Security + phase-changed: Thursday, 27. June 2019 21:29 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published 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/1833982 Title: linux-azure-edge: 4.15.0.1049.32 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722886] Re: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data
This bug was fixed in the package gnome-shell - 3.32.2-2ubuntu1 --- gnome-shell (3.32.2-2ubuntu1) eoan; urgency=medium * Merge with Debian. Remaining changes: + Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds + Add some Recommends: - ubuntu-session (| gnome-session) to have the ubuntu session available - xserver-xorg-legacy - yaru-theme-gnome-shell for the default ubuntu theming + Update debian/gbp.conf with Ubuntu settings + gnome-shell-common.install: Install Ubuntu mode + gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative + ubuntu/desktop_detect.patch: - add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. + ubuntu/smarter_alt_tab.patch: - quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. + ubuntu/lightdm-user-switching.patch: - Allow user switching when using LightDM. + ubuntu/lock_on_suspend.patch - Respect Ubuntu's lock-on-suspend setting. + ubuntu/gdm.patch - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu styling by default, not impacting the gnome user session though. + ubuntu/background_login.patch - Change default background color as we modified the default GDM color for our ubuntu session. Change it as well here, still applying the background noise loading. + ubuntu/gdm_alternatives.patch - Add support for GDM3 theme alternatives + ubuntu/block_mode_extension_update.patch - Don't allow ubuntu mode extension to update + optional-hot-corner.patch - enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. + volume-Add-back-sound-feedback-on-scroll.patch - Fix regression causing missing feedback on volume slider scroll + main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: - Improve debug JS tracing for crash reports + st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch, st-scroll-view-Remove-scrollbars-references-on-dispose.patch: - Fix crash on theme changes + ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: - stop searches when requested from UI + magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Show monitor scaled cursor when magnifier is enabled gnome-shell (3.32.2-2) experimental; urgency=medium * debian/source_gnome-shell.py: + Add more informations that we might need to debug information in the apport retracing (LP: #1722886): - All the desktop shared gsettings key - Mutter gsettings key and version - Settings daemon settings key used by the shell - ~/.config/monitors.xml - Shell's journalctl since it will include errors and JS stacktrace. * d/p/boxpointer-Unset-the-sourceActor-on-destruction.patch: - Avoid crash on reallocation of dead actors (LP: #1831555) -- Iain Lane Thu, 27 Jun 2019 18:02:14 +0100 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => 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/1722886 Title: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831555] Re: gnome-shell crashed with SIGTRAP in gjs_callback_closure() from ffi_closure_unix64_inner() from ffi_closure_unix64() from clutter_actor_allocate_internal() from clutter_actor_allocat
This bug was fixed in the package gnome-shell - 3.32.2-2ubuntu1 --- gnome-shell (3.32.2-2ubuntu1) eoan; urgency=medium * Merge with Debian. Remaining changes: + Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds + Add some Recommends: - ubuntu-session (| gnome-session) to have the ubuntu session available - xserver-xorg-legacy - yaru-theme-gnome-shell for the default ubuntu theming + Update debian/gbp.conf with Ubuntu settings + gnome-shell-common.install: Install Ubuntu mode + gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative + ubuntu/desktop_detect.patch: - add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. + ubuntu/smarter_alt_tab.patch: - quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. + ubuntu/lightdm-user-switching.patch: - Allow user switching when using LightDM. + ubuntu/lock_on_suspend.patch - Respect Ubuntu's lock-on-suspend setting. + ubuntu/gdm.patch - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu styling by default, not impacting the gnome user session though. + ubuntu/background_login.patch - Change default background color as we modified the default GDM color for our ubuntu session. Change it as well here, still applying the background noise loading. + ubuntu/gdm_alternatives.patch - Add support for GDM3 theme alternatives + ubuntu/block_mode_extension_update.patch - Don't allow ubuntu mode extension to update + optional-hot-corner.patch - enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. + volume-Add-back-sound-feedback-on-scroll.patch - Fix regression causing missing feedback on volume slider scroll + main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: - Improve debug JS tracing for crash reports + st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch, st-scroll-view-Remove-scrollbars-references-on-dispose.patch: - Fix crash on theme changes + ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: - stop searches when requested from UI + magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Show monitor scaled cursor when magnifier is enabled gnome-shell (3.32.2-2) experimental; urgency=medium * debian/source_gnome-shell.py: + Add more informations that we might need to debug information in the apport retracing (LP: #1722886): - All the desktop shared gsettings key - Mutter gsettings key and version - Settings daemon settings key used by the shell - ~/.config/monitors.xml - Shell's journalctl since it will include errors and JS stacktrace. * d/p/boxpointer-Unset-the-sourceActor-on-destruction.patch: - Avoid crash on reallocation of dead actors (LP: #1831555) -- Iain Lane Thu, 27 Jun 2019 18:02:14 +0100 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => 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/1831555 Title: gnome-shell crashed with SIGTRAP in gjs_callback_closure() from ffi_closure_unix64_inner() from ffi_closure_unix64() from clutter_actor_allocate_internal() from clutter_actor_allocate() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1831555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833950] Re: linux-hwe: 4.18.0-25.26~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833952 phase: Promote to Proposed phase-changed: Thursday, 27. June 2019 17:08 UTC reason: - promote-to-proposed: Pending -- packages copied to Proposed signed:building + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833950 Title: linux-hwe: 4.18.0-25.26~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
This is confusing, I'm seeing the timeout with a TLSv1.2 connection, and the commit pointed out in comment #9 mentions TLSv1.3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833039 Title: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
I can try some or all of the patches mentioned in https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689/comments/2 That bug might be a duplicate, btw. (or this one) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833039 Title: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834529] Re: Disco update: 5.0.15 upstream stable release
** Description changed: 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: + a minimally backported form of that patch. 5.0.15 upstream stable release from git://git.kernel.org/ - The following patches from 5.0.15 stable release have been applied: + The following upstream stable patches should be included in the Ubuntu + kernel: * net: stmmac: Use bfsize1 in ndesc_init_rx_desc * Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() * ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings * staging: greybus: power_supply: fix prop-descriptor request size * staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. * staging: most: cdev: fix chrdev_region leak in mod_exit * staging: most: sound: pass correct device when creating a sound card * ASoC: tlv320aic3x: fix reset gpio reference counting * ASoC: hdmi-codec: fix S/PDIF DAI * ASoC: stm32: sai: fix iec958 controls indexation * ASoC: stm32: sai: fix exposed capabilities in spdif mode * ASoC: stm32: sai: fix race condition in irq handler * ASoC:soc-pcm:fix a codec fixup issue in TDM case * ASoC:hdac_hda:use correct format to setup hda codec * ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform * ASoC: dpcm: prevent snd_soc_dpcm use after free * ASoC: nau8824: fix the issue of the widget with prefix name * ASoC: nau8810: fix the issue of widget with prefixed name * ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate * ASoC: rt5682: Check JD status when system resume * ASoC: rt5682: fix jack type detection issue * ASoC: rt5682: recording has no sound after booting * ASoC: wm_adsp: Add locking to wm_adsp2_bus_error * clk: meson-gxbb: round the vdec dividers to closest * ASoC: stm32: dfsdm: manage multiple prepare * ASoC: stm32: dfsdm: fix debugfs warnings on entry creation * ASoC: cs4270: Set auto-increment bit for register writes * ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol * drm/omap: hdmi4_cec: Fix CEC clock handling for PM * IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state * IB/hfi1: Eliminate opcode tests on mr deref * IB/hfi1: Fix the allocation of RSM table * MIPS: KGDB: fix kgdb support for SMP platforms. * ASoC: tlv320aic32x4: Fix Common Pins * drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() * perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS * perf/x86/intel: Initialize TFA MSR * linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() * iov_iter: Fix build error without CONFIG_CRYPTO * xtensa: fix initialization of pt_regs::syscall in start_thread * ASoC: rockchip: pdm: fix regmap_ops hang issue * drm/amdkfd: Add picasso pci id * drm/amdgpu: Adjust IB test timeout for XGMI configuration * drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list * drm/amd/display: fix cursor black issue * ASoC: cs35l35: Disable regulators on driver removal * objtool: Add rewind_stack_do_exit() to the noreturn list * slab: fix a crash by reading /proc/slab_allocators * drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind * virtio_pci: fix a NULL pointer reference in vp_del_vqs * RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove * RDMA/hns: Fix bug that caused srq creation to fail * KEYS: trusted: fix -Wvarags warning * scsi: csiostor: fix missing data copy in csio_scsi_err_handler() * drm/mediatek: fix possible object reference leak * drm/mediatek: fix the rate and divder of hdmi phy for MT2701 * drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy * drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy * drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy * drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy * ASoC: Intel: kbl: fix wrong number of channels * ASoC: stm32: sai: fix master clock management * ALSA: hda: Fix racy display power access * virtio-blk: limit number of hw queues by nr_cpu_ids * blk-mq: introduce blk_mq_complete_request_sync() * nvme: cancel request synchronously * nvme-fc: correct csn initialization and increments on error * nvmet: fix discover log page when offsets are used * platform/x86: pmc_atom: Drop __initconst on dmi table * NFSv4.1 fix incorrect return value in copy_file_range * perf/core: Fix perf_event_disable_inatomic() race * iommu/amd: Set exclusion range co
[Bug 1834501] Re: do-release-upgrade from bionic->any disables lxd without snapstore access
I suspect for lxd, this is likely a WontFix; for cosmic and later, it's provided via snap, and unlikely to go back to a deb. I targeted this against u-r-u as well, as the 'best' fix for this may be to add a check at the start of the upgrade process, and let the upgrader choose at that point what to do, instead of waiting until mid-upgrade to let them know they need to abort the upgrade. Additionally, whatever warning/error message is printed, either by lxd package->snap upgrade itself, and/or do-release-upgrade, should mention the snap proxy, as enterprise customers with a firewall setup will likely need to use the snap proxy. https://docs.ubuntu.com/snap-store-proxy/en/ ** Description changed: [impact] a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air- gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade. [test case] see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io) -create VM using the bionic cloud image -in the bionic guest: $ sudo apt update $ sudo apt dist-upgrade -note: snapd and lxd should already be installed; verify this $ dpkg -l |grep -E '^ii (lxd|snapd)' ii lxd3.0.3-0ubuntu1~18.04.1 amd64Container hypervisor based on LXC - daemon ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64Container hypervisor based on LXC - client ii snapd 2.39.2+18.04 amd64Daemon and tooling that enable snap packages -edit /etc/update-manager/release-upgrades to set Prompt=normal -reboot, if needed due to kernel upgrade -upgrade: $ sudo do-release-upgrade Once the upgrade reaches the lxd package, it will display: -- Your system is unable to reach the snap store, please make sure you're connected to the Internet and update any firewall or proxy settings as needed so that you can reach the snap store. You can manually check for connectivity by running "snap info lxd" Aborting will cause the upgrade to fail and will require it to be re- attempted once snapd is functional on the system. Skipping will let the package upgrade continue but the LXD commands will not be functional until the LXD snap is installed. Skipping is allowed only when LXD is not activated on the system. Unable to reach the snap store -- With the possible choices of: Retry Abort Skip Retry, of course, will never succeed. Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd is populated). If lxd (and/or lxd-client) are installed but not configured, skip can be chosen to continue the upgrade, and after upgrade is complete, the lxd package will not be - installed. + installed. If skip is attempted when lxd has been initialized, this is + shown: + + -- + Skipping is not allowed when LXD has been initialized + + LXD appears to have been configured on this system. Please stop LXD and + remove local data in /var/lib/lxd/ if you would like to skip installing + the LXD snap and migrating the local data. + -- Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits; it is unclear if the system is in a good fully-upgraded state at this point (besides not having an upgraded lxd, of course). [regression potential] TBD [other info] this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade. I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic. ** Also affects: ubuntu-release-upgrader (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/1834501 Title: do-release-upgrade from bionic->any disables lxd without snapstore access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1834501/+subscriptions -- ubuntu-
[Bug 1834501] Re: do-release-upgrade from bionic->any disables lxd without snapstore access
> and let the upgrader choose at that point what to do by 'upgrader' i meant the actual person doing the upgrade should be notified, and choose what to do, before upgrade starts ** Changed in: lxd (Ubuntu Eoan) Importance: High => Undecided ** Changed in: lxd (Ubuntu Disco) Importance: High => Undecided ** Changed in: lxd (Ubuntu Cosmic) Importance: High => Undecided ** Description changed: [impact] a bionic system with lxd installed, and configured, when upgraded to cosmic using do-release-upgrade, will attempt to convert the lxd deb into a snap. However, if the snapstore isn't reachable (which is a common situation in enterprise environments, where they use local apt mirrors and firewall internet access, or even are completely air- gapped), the upgrade complains loudly about being unable to access the snapstore, and the only option presented to allow install to continue is to skip or abort lxd upgrade, which states lxd will be unusable after the upgrade. [test case] see bug 1831933 for testbed setup (use a libvirt vm with nwfilter blocking api.snapcraft.io) -create VM using the bionic cloud image -in the bionic guest: $ sudo apt update $ sudo apt dist-upgrade -note: snapd and lxd should already be installed; verify this $ dpkg -l |grep -E '^ii (lxd|snapd)' ii lxd3.0.3-0ubuntu1~18.04.1 amd64Container hypervisor based on LXC - daemon ii lxd-client 3.0.3-0ubuntu1~18.04.1 amd64Container hypervisor based on LXC - client ii snapd 2.39.2+18.04 amd64Daemon and tooling that enable snap packages -edit /etc/update-manager/release-upgrades to set Prompt=normal -reboot, if needed due to kernel upgrade -upgrade: $ sudo do-release-upgrade Once the upgrade reaches the lxd package, it will display: -- Your system is unable to reach the snap store, please make sure you're connected to the Internet and update any firewall or proxy settings as needed so that you can reach the snap store. You can manually check for connectivity by running "snap info lxd" Aborting will cause the upgrade to fail and will require it to be re- attempted once snapd is functional on the system. Skipping will let the package upgrade continue but the LXD commands will not be functional until the LXD snap is installed. Skipping is allowed only when LXD is not activated on the system. Unable to reach the snap store -- With the possible choices of: Retry Abort Skip Retry, of course, will never succeed. Skip is not allowed if lxd has been configured (i.e. 'lxd init' was run, and /var/lib/lxd is populated). If lxd (and/or lxd-client) are installed but not configured, skip can be chosen to continue the upgrade, and after upgrade is complete, the lxd package will not be installed. If skip is attempted when lxd has been initialized, this is shown: -- Skipping is not allowed when LXD has been initialized LXD appears to have been configured on this system. Please stop LXD and remove local data in /var/lib/lxd/ if you would like to skip installing the LXD snap and migrating the local data. -- Abort continues the upgrade remaining packages, after asking if the lxd upgrade failure report should be sent. However, at the end of the remaining package upgrades, the upgrade reports error and exits; it is unclear if the system is in a good fully-upgraded state at this point (besides not having an upgraded lxd, of course). [regression potential] TBD [other info] this is related to bug 1831933, but much more serious, if lxd really is unusable after the upgrade. I targeted this bug as affecting cosmic, disco, and eoan, however currently the upgrade from bionic must go through cosmic first. And since the lxd upgrade from b->c fails without snapstore access, and there is no way to install lxd as a deb into cosmic, this bug really is just about upgrading *from* bionic. + + This bug is unlikely to be seen by any enterprise customers right now, + as most of them stick to LTS releases. However in 2020 once the LTS + series 20.04 is released, some enterprise customers whose deployment is + firewalled and/or airgapped may start to see this during upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834501 Title: do-release-upgrade from bionic->any disables lxd without snapstore access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1834501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834529] Re: Disco update: 5.0.15 upstream stable release
The following patch has already been applied: * "Bluetooth: hidp: fix buffer overflow" -- introduced to ML to fix CVE-2019-11884. ** Description changed: + SRU Justification - 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: - 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: + 5.0.15 upstream stable release + from git://git.kernel.org/ -5.0.15 upstream stable release -from git://git.kernel.org/ + The following patches from 5.0.15 stable release have been applied: + + * net: stmmac: Use bfsize1 in ndesc_init_rx_desc + * Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() + * ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings + * staging: greybus: power_supply: fix prop-descriptor request size + * staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. + * staging: most: cdev: fix chrdev_region leak in mod_exit + * staging: most: sound: pass correct device when creating a sound card + * ASoC: tlv320aic3x: fix reset gpio reference counting + * ASoC: hdmi-codec: fix S/PDIF DAI + * ASoC: stm32: sai: fix iec958 controls indexation + * ASoC: stm32: sai: fix exposed capabilities in spdif mode + * ASoC: stm32: sai: fix race condition in irq handler + * ASoC:soc-pcm:fix a codec fixup issue in TDM case + * ASoC:hdac_hda:use correct format to setup hda codec + * ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform + * ASoC: dpcm: prevent snd_soc_dpcm use after free + * ASoC: nau8824: fix the issue of the widget with prefix name + * ASoC: nau8810: fix the issue of widget with prefixed name + * ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate + * ASoC: rt5682: Check JD status when system resume + * ASoC: rt5682: fix jack type detection issue + * ASoC: rt5682: recording has no sound after booting + * ASoC: wm_adsp: Add locking to wm_adsp2_bus_error + * clk: meson-gxbb: round the vdec dividers to closest + * ASoC: stm32: dfsdm: manage multiple prepare + * ASoC: stm32: dfsdm: fix debugfs warnings on entry creation + * ASoC: cs4270: Set auto-increment bit for register writes + * ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol + * drm/omap: hdmi4_cec: Fix CEC clock handling for PM + * IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state + * IB/hfi1: Eliminate opcode tests on mr deref + * IB/hfi1: Fix the allocation of RSM table + * MIPS: KGDB: fix kgdb support for SMP platforms. + * ASoC: tlv320aic32x4: Fix Common Pins + * drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() + * perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS + * perf/x86/intel: Initialize TFA MSR + * linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() + * iov_iter: Fix build error without CONFIG_CRYPTO + * xtensa: fix initialization of pt_regs::syscall in start_thread + * ASoC: rockchip: pdm: fix regmap_ops hang issue + * drm/amdkfd: Add picasso pci id + * drm/amdgpu: Adjust IB test timeout for XGMI configuration + * drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list + * drm/amd/display: fix cursor black issue + * ASoC: cs35l35: Disable regulators on driver removal + * objtool: Add rewind_stack_do_exit() to the noreturn list + * slab: fix a crash by reading /proc/slab_allocators + * drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind + * virtio_pci: fix a NULL pointer reference in vp_del_vqs + * RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove + * RDMA/hns: Fix bug that caused srq creation to fail + * KEYS: trusted: fix -Wvarags warning + * scsi: csiostor: fix missing data copy in csio_scsi_err_handler() + * drm/mediatek: fix possible object reference leak + * drm/mediatek: fix the rate and divder of hdmi phy for MT2701 + * drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy + * drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy + * drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy + * drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy + * ASoC: Intel: kbl: fix wrong number of channels + * ASoC: stm32: sai: fix maste
[Bug 1834024] Re: linux-raspi2: 4.4.0-1114.123 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates 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 derivatives: bug 1834022 (pi2-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 - phase: Release - phase-changed: Thursday, 27. June 2019 20:28 UTC + phase: Holding before Security + phase-changed: Thursday, 27. June 2019 20:48 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published 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/1834024 Title: linux-raspi2: 4.4.0-1114.123 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834507] Re: Attempting to load sss.so in Bionic fails due to SMB_IDMAP_INTERFACE_VERSION mismatch
** Description changed:
[Impact]
When attempting to load the sss.so module, on a Bionic box running
samba-* on 4.7 and sssd-* 1.16.1, one sees the following in syslog:
winbindd[13099]: load_module_absolute_path: Module
'/usr/lib/x86_64-linux-gnu/samba/idmap/sss.so' loaded
winbindd[13099]: Failed to register idmap module.
winbindd[13099]: The module was compiled against
SMB_IDMAP_INTERFACE_VERSION 5,
winbindd[13099]: current SMB_IDMAP_INTERFACE_VERSION is 6.
This issue has been reported upstream, and made it into 1.16.2+ version
of sssd, but not into 1.16.1, which is currently found in Bionic.
[Test Case]
* sudo apt update
* sudo apt install sssd winbind
* Create this /etc/samba/smb.conf:
[global]
log file = /var/log/samba/log.%m
map to guest = Bad User
max log size = 1000
panic action = /usr/share/samba/panic-action %d
server role = standalone server
server string = %h server (Samba, Ubuntu)
syslog = 0
idmap config * : backend = sss
idmap config * : range = 20-2147483647
* sudo systemctl restart winbind
Run this command to trigger the loading of the sss module. It will fail
because, among other reasons, this machine is not part of a domain, but that's
fine:
# wbinfo --allocate-uid
failed to call wbcAllocateUid: WBC_ERR_DOMAIN_NOT_FOUND
Could not allocate a uid
Now /var/log/samba/log.winbindd-idmap will contain:
[2019/06/27 17:45:18.420790, 0]
../source3/winbindd/idmap.c:328(smb_register_idmap)
Failed to register idmap module.
The module was compiled against SMB_IDMAP_INTERFACE_VERSION 5,
current SMB_IDMAP_INTERFACE_VERSION is 6.
Please recompile against the current version of samba!
[2019/06/27 17:45:18.421110, 0]
../lib/util/modules.c:173(load_module_absolute_path)
load_module_absolute_path: Module
'/usr/lib/x86_64-linux-gnu/samba/idmap/sss.so' initialization failed: {Wrong
Type} There is a mismatch between the type of object that is required by the
requested operation and the type of object that is specified in the request.
This confirms the bug.
[Regression Potential]
[Other informations]
- *Cosmic and late are okay.
-
- *Xenial is also okay, as it doesn't uses version "6"
+ *Cosmic and late aren't impacted.
+ *Xenial is not impacted, as it doesn't uses version "6"
+ -
samba-4.3.11+dfsg/source3/include/idmap.h:
#define SMB_IDMAP_INTERFACE_VERSION 5
-
+ -
*Upstream:
https://pagure.io/SSSD/sssd/issue/3741
https://github.com/SSSD/sssd/pull/572
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834507
Title:
Attempting to load sss.so in Bionic fails due to
SMB_IDMAP_INTERFACE_VERSION mismatch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1834507/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
