[Bug 2059872] Re: Unable to listen on port 22 if multiple Port= present in sshd configuration
Is there a workaround for this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059872 Title: Unable to listen on port 22 if multiple Port= present in sshd configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963976] Re: Installing nvidia-cuda-toolkit removes nvidia-driver-510
This is a debian packaging issue.
rules.defs in the Debian source package has different rules for Debian and
Ubuntu for libnvidia-ml1 and libcuda1. From the jammy package of
11.5.1-1ubuntu1:
-snip-
package_libcuda1.Debian += libcuda1 (>=
$${nvidia:MinVersion}) [!armhf !ppc64el] |
package_libcuda1.Debian += libnvidia-tesla-495-cuda1(>=
$${nvidia:MinVersion}) [amd64 i386 arm64 ppc64el] |
package_libcuda1.Ubuntu += libnvidia-compute-495(>=
$${nvidia:MinVersion}) [amd64 i386] |
package_libcuda1.Ubuntu += libnvidia-compute-495-server (>=
$${nvidia:MinVersion}) [amd64 i386] |
package_libnvidia-ml1.Debian+= libnvidia-ml1(>=
$${nvidia:MinVersion}) [!armhf !ppc64el] |
package_libnvidia-ml1.Debian+= libnvidia-tesla-495-ml1 (>=
$${nvidia:MinVersion}) [amd64 i386 arm64 ppc64el] |
package_libnvidia-ml1.Ubuntu = $(package_libcuda1.Ubuntu)
-snip-
package_libnvidia-ml1.Ubuntu is missing the libnvidia-ml1 line. It's
depending upon a specific version of the package available package build
time. The Ubuntu Nvidia driver packages provide libnvidia-ml1 now, but
might not have in the past.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963976
Title:
Installing nvidia-cuda-toolkit removes nvidia-driver-510
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1963976/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800746] Re: Versioning mess upon upgrade from bionic to cosmic
I haven't had this issue in any other upgrades (disco, eoan, focal, groovy) since then. It was a specific version numbering issue between bionic and cosmic, and cosmic is long out of support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800746 Title: Versioning mess upon upgrade from bionic to cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1800746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905190] Re: rasdaemon 0.6.6-1 fails to start on groovy
** Description changed: rasdaemon 0.6.6-1 fails to start on groovy with "Failed to load environment files: No such file or directory". This issue was fixed on debian in 0.6.6-2. See linked debian #966698 The log output is here: systemctl status rasdaemon.service ● rasdaemon.service - RAS daemon to log the RAS events Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset: enabled) Active: failed (Result: resources) - Nov 22 13:56:45 fishasshole systemd[1]: rasdaemon.service: Failed to load environment files: No such file or directory - Nov 22 13:56:45 fishasshole systemd[1]: rasdaemon.service: Failed to run 'start' task: No such file or directory - Nov 22 13:56:45 fishasshole systemd[1]: rasdaemon.service: Failed with result 'resources'. - Nov 22 13:56:45 fishasshole systemd[1]: Failed to start RAS daemon to log the RAS events. - Nov 22 13:56:47 fishasshole systemd[1]: rasdaemon.service: Failed to load environment files: No such file or directory - Nov 22 13:56:47 fishasshole systemd[1]: rasdaemon.service: Failed to run 'start' task: No such file or directory - Nov 22 13:56:47 fishasshole systemd[1]: rasdaemon.service: Failed with result 'resources'. - Nov 22 13:56:47 fishasshole systemd[1]: Failed to start RAS daemon to log the RAS events. + Nov 22 13:56:45 myhost systemd[1]: rasdaemon.service: Failed to load environment files: No such file or directory + Nov 22 13:56:45 myhost systemd[1]: rasdaemon.service: Failed to run 'start' task: No such file or directory + Nov 22 13:56:45 myhost systemd[1]: rasdaemon.service: Failed with result 'resources'. + Nov 22 13:56:45 myhost systemd[1]: Failed to start RAS daemon to log the RAS events. + Nov 22 13:56:47 myhost systemd[1]: rasdaemon.service: Failed to load environment files: No such file or directory + Nov 22 13:56:47 myhost systemd[1]: rasdaemon.service: Failed to run 'start' task: No such file or directory + Nov 22 13:56:47 myhost systemd[1]: rasdaemon.service: Failed with result 'resources'. + Nov 22 13:56:47 myhost systemd[1]: Failed to start RAS daemon to log the RAS events. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905190 Title: rasdaemon 0.6.6-1 fails to start on groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1905190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905190] [NEW] rasdaemon 0.6.6-1 fails to start on groovy
Public bug reported: rasdaemon 0.6.6-1 fails to start on groovy with "Failed to load environment files: No such file or directory". This issue was fixed on debian in 0.6.6-2. See linked debian #966698 The log output is here: systemctl status rasdaemon.service ● rasdaemon.service - RAS daemon to log the RAS events Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset: enabled) Active: failed (Result: resources) Nov 22 13:56:45 fishasshole systemd[1]: rasdaemon.service: Failed to load environment files: No such file or directory Nov 22 13:56:45 fishasshole systemd[1]: rasdaemon.service: Failed to run 'start' task: No such file or directory Nov 22 13:56:45 fishasshole systemd[1]: rasdaemon.service: Failed with result 'resources'. Nov 22 13:56:45 fishasshole systemd[1]: Failed to start RAS daemon to log the RAS events. Nov 22 13:56:47 fishasshole systemd[1]: rasdaemon.service: Failed to load environment files: No such file or directory Nov 22 13:56:47 fishasshole systemd[1]: rasdaemon.service: Failed to run 'start' task: No such file or directory Nov 22 13:56:47 fishasshole systemd[1]: rasdaemon.service: Failed with result 'resources'. Nov 22 13:56:47 fishasshole systemd[1]: Failed to start RAS daemon to log the RAS events. ** Affects: rasdaemon (Ubuntu) Importance: Undecided Status: New ** Affects: rasdaemon (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #966698 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966698 ** Also affects: rasdaemon (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966698 Importance: Unknown Status: Unknown ** Description changed: rasdaemon 0.6.6-1 fails to start on groovy with "Failed to load environment files: No such file or directory". This issue was fixed on - debian in 0.6.6-2. See debian bug #966698 + debian in 0.6.6-2. See linked debian bug 966698 The log output is here: systemctl status rasdaemon.service ● rasdaemon.service - RAS daemon to log the RAS events - Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset: enabled) - Active: failed (Result: resources) + Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset: enabled) + Active: failed (Result: resources) Nov 22 13:56:45 fishasshole systemd[1]: rasdaemon.service: Failed to load environment files: No such file or directory Nov 22 13:56:45 fishasshole systemd[1]: rasdaemon.service: Failed to run 'start' task: No such file or directory Nov 22 13:56:45 fishasshole systemd[1]: rasdaemon.service: Failed with result 'resources'. Nov 22 13:56:45 fishasshole systemd[1]: Failed to start RAS daemon to log the RAS events. Nov 22 13:56:47 fishasshole systemd[1]: rasdaemon.service: Failed to load environment files: No such file or directory Nov 22 13:56:47 fishasshole systemd[1]: rasdaemon.service: Failed to run 'start' task: No such file or directory Nov 22 13:56:47 fishasshole systemd[1]: rasdaemon.service: Failed with result 'resources'. Nov 22 13:56:47 fishasshole systemd[1]: Failed to start RAS daemon to log the RAS events. ** Description changed: rasdaemon 0.6.6-1 fails to start on groovy with "Failed to load environment files: No such file or directory". This issue was fixed on - debian in 0.6.6-2. See linked debian bug 966698 + debian in 0.6.6-2. See linked debian #966698 The log output is here: systemctl status rasdaemon.service ● rasdaemon.service - RAS daemon to log the RAS events Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset: enabled) Active: failed (Result: resources) Nov 22 13:56:45 fishasshole systemd[1]: rasdaemon.service: Failed to load environment files: No such file or directory Nov 22 13:56:45 fishasshole systemd[1]: rasdaemon.service: Failed to run 'start' task: No such file or directory Nov 22 13:56:45 fishasshole systemd[1]: rasdaemon.service: Failed with result 'resources'. Nov 22 13:56:45 fishasshole systemd[1]: Failed to start RAS daemon to log the RAS events. Nov 22 13:56:47 fishasshole systemd[1]: rasdaemon.service: Failed to load environment files: No such file or directory Nov 22 13:56:47 fishasshole systemd[1]: rasdaemon.service: Failed to run 'start' task: No such file or directory Nov 22 13:56:47 fishasshole systemd[1]: rasdaemon.service: Failed with result 'resources'. Nov 22 13:56:47 fishasshole systemd[1]: Failed to start RAS daemon to log the RAS events. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905190 Title: rasdaemon 0.6.6-1 fails to start on groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1905190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubun
[Bug 1904357] Re: calibre crashes on startup
I just tried to run Calibre on 20.04 and ran into this. I was able to manually edit a python file to get it running: https://github.com/kovidgoyal/calibre/commit/7b6416ac6522fc40f24f6baf3ca552b17a8b91d6 Can the maintainer backport this to Calibre on 20.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904357 Title: calibre crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1904357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881427] [NEW] zfs-linux 0.8.3-1ubuntu14 has a broken backport of Linux 5.7 compat
Public bug reported: The backport of upstream commit 68dde63d138882860109178f4ab0b7b1b1bb3cfd in 0.8.3-1ubuntu14 is not correct for the 0.8.3 stable series and causes an oops on boot with a 5.7 kernel. The patch that shipped in 0.8.4 is slightly different, and works correctly: https://github.com/openzfs/zfs/commit/e6142ac0f28891a0ef3de366a45bb857a17ee25a [ 13.848194] BUG: kernel NULL pointer dereference, address: 0040 [ 13.848415] #PF: supervisor write access in kernel mode [ 13.848572] #PF: error_code(0x0002) - not-present page [ 13.848813] PGD 0 P4D 0 [ 13.848896] Oops: 0002 [#1] SMP PTI [ 13.849006] CPU: 3 PID: 1501 Comm: z_zvol Tainted: P OE 5.7.0-rc7-customskl #1 [ 13.849254] Hardware name: System manufacturer System Product Name/ROG MAXIMUS X HERO (WI-FI AC), BIOS 2301 02/25/2020 [ 13.849623] RIP: 0010:zvol_create_minor_impl+0x52a/0x810 [zfs] [ 13.849800] Code: 48 8b 54 24 18 49 89 87 08 01 00 00 48 8b 44 24 20 49 89 97 10 01 00 00 49 8b 97 a8 01 00 00 49 89 87 00 01 00 00 48 c1 e8 09 <48> 89 42 40 49 8b bf b0 01 00 00 e8 f6 3e f2 cf 49 8b bf b0 01 00 [ 13.850346] RSP: 0018:b75ac1df7cf8 EFLAGS: 00010206 [ 13.850504] RAX: 0200 RBX: 3471fa85c299b9ef RCX: [ 13.850715] RDX: RSI: 8000 RDI: a286a5775000 [ 13.850926] RBP: a286a0c60fb0 R08: a286ae55580f R09: [ 13.851137] R10: a286ae55582c R11: a286ae55580f R12: [ 13.851347] R13: R14: a286962ff380 R15: a286ac071800 [ 13.851560] FS: () GS:a286beac() knlGS: [ 13.851799] CS: 0010 DS: ES: CR0: 80050033 [ 13.851970] CR2: 0040 CR3: 00051f20a001 CR4: 003606e0 [ 13.852181] DR0: DR1: DR2: [ 13.852392] DR3: DR6: fffe0ff0 DR7: 0400 [ 13.852602] Call Trace: [ 13.852733] zvol_task_cb+0x258/0x570 [zfs] [ 13.852867] ? __schedule+0x1d8/0x560 [ 13.852988] taskq_thread+0x2c3/0x490 [spl] [ 13.853119] ? __switch_to_asm+0x34/0x70 [ 13.853241] ? wake_up_q+0xa0/0xa0 [ 13.853350] kthread+0xfb/0x130 [ 13.853453] ? task_done+0x90/0x90 [spl] [ 13.853573] ? kthread_park+0x90/0x90 [ 13.853686] ret_from_fork+0x35/0x40 [ 13.853797] Modules linked in: input_leds btusb uvcvideo btbcm btrtl videobuf2_vmalloc btintel videobuf2_memops snd_usb_audio videobuf2_v4l2 bluetooth videobuf2_common hid_generic videodev snd_usbmidi_lib ecdh_generic mc usbhid ecc intel_rapl_msr intel_rapl_common uas usb_storage zfs(POE) x86_pkg_temp_thermal zunicode(POE) intel_powerclamp zlua(POE) mxm_wmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel amdgpu snd_intel_dspcfg crct10dif_pclmul snd_hda_codec crc32_pclmul crc32c_intel snd_hwdep snd_hda_core rtwpci snd_pcm_oss rtw88 snd_mixer_oss zcommon(POE) ghash_clmulni_intel snd_pcm znvpair(POE) vfat zavl(POE) icp(POE) fat snd_seq_oss spl(OE) mac80211 snd_seq_midi mfd_core gpu_sched i2c_algo_bit aesni_intel snd_rawmidi ttm snd_seq_midi_event crypto_simd xhci_pci snd_seq xhci_hcd cryptd deflate snd_seq_device drm_kms_helper glue_helper efi_pstore cfg80211 e1000e snd_timer syscopyarea intel_cstate sysfillrect rfkill ptp sysimgblt efivars pps_core [ 13.853860] i2c_i801 usbcore snd libarc4 sr_mod intel_rapl_perf fb_sys_fops cec cdrom mei_hdcp usb_common sg rc_core soundcore video wmi acpi_pad button squashfs sch_fq_codel coretemp hwmon loop drm i2c_core nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables [ 13.857103] CR2: 0040 [ 13.857207] ---[ end trace a20c8291d85b28f4 ]--- [ 13.994917] RIP: 0010:zvol_create_minor_impl+0x52a/0x810 [zfs] [ 13.994993] Code: 48 8b 54 24 18 49 89 87 08 01 00 00 48 8b 44 24 20 49 89 97 10 01 00 00 49 8b 97 a8 01 00 00 49 89 87 00 01 00 00 48 c1 e8 09 <48> 89 42 40 49 8b bf b0 01 00 00 e8 f6 3e f2 cf 49 8b bf b0 01 00 [ 13.997900] RSP: 0018:b75ac1df7cf8 EFLAGS: 00010206 [ 14.000564] RAX: 0200 RBX: 3471fa85c299b9ef RCX: [ 14.003239] RDX: RSI: 8000 RDI: a286a5775000 [ 14.005901] RBP: a286a0c60fb0 R08: a286ae55580f R09: [ 14.008580] R10: a286ae55582c R11: a286ae55580f R12: [ 14.011210] R13: R14: a286962ff380 R15: a286ac071800 [ 14.013877] FS: () GS:a286beac() knlGS: [ 14.016555] CS: 0010 DS: ES: CR0: 80050033 [ 14.019184] CR2: 0040 CR3: 000c074fc006 CR4: 003606e0 [ 14.021851] DR0: DR1: DR2: [ 14.024495] DR3: DR6: fffe0ff0 DR7: 0400 ** Affects: zfs-linux (Ubuntu) Importance: Undecided
[Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
I currently have the package patched in my PPA to resolve the bug. It is a difficult to debug problem that has been sending users upstream to kodi with bug reports and confusing stack traces. This will get more exposure when focal is released due to the LTS status. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
Is this going to make it for focal? This bug causes kodi to crash when turning my TV screen off. ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859293] Re: davfs2 umount.davfs crashes when compiled with gcc 9
This bug causes umount to crash for davfs filesystem. I can't unmount them. The patch is simple and upstream. It looks like no one tested this after upgrading the compiler to gcc 9. Upgrading the package to davfs2 1.5.6 fixes this crash. Is this going to make it for focal? ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859293 Title: davfs2 umount.davfs crashes when compiled with gcc 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/davfs2/+bug/1859293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
No one is asking you to send them a fix. Since you are experiencing the issue on a stable release, you should let Mesa know that the issue exists in stable releases, and ask them to provide the fix for the stable 20.0.x branch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
Oibaf is using the development release of Mesa. It's not released yet. Mesa 20.1 isn't scheduled for release until May. You need them to backport the fix to the 20.0.x branch. Here is the upstream issue: https://gitlab.freedesktop.org/mesa/mesa/issues/2523 You can ask there for a backport to 20.0.x. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #2523 https://gitlab.freedesktop.org/mesa/mesa/issues/2523 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868352] Re: grub2 2.04-1ubuntu12.2 breaks boot on some machines
After enabling CONFIG_EFI_STUB=y both of my machines will not boot from filesystem UUID. The rootfs on both machines is a btrfs subvolume on an nvme partition. On boot, the kernel panics that it can't find the rootfs: kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) If I either specify by device path (/dev/nvme0n1p2 and /dev/nvme0n1p3 for the two machines) or by PARTUUID, it can find it and boot. I haven't investigated why the kernel can't find the filesystems by fs UUID, but they are not available after the EFI handover. To workaround it, I have set these options in /etc/default/grub: GRUB_DISABLE_LINUX_UUID=true GRUB_DISABLE_LINUX_PARTUUID=false This forces grub to pass the PARTUUID instead of the fs UUID. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868352 Title: grub2 2.04-1ubuntu12.2 breaks boot on some machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1868352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868352] Re: grub2 2.04-1ubuntu12.2 breaks boot on some machines
I filed this against grub2 originally. Somehow ubuntu-bug changed that to xorg. I added grub2 back. It's not letting me remove xorg. ** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** No longer affects: xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868352 Title: grub2 2.04-1ubuntu12.2 breaks boot on some machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1868352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868352] Re: grub2 2.04-1ubuntu12.2 breaks boot on some machines
I get "error: kernel doesn't support EFI handover" when trying to boot a kernel without EFISTUB. The patches for EFISTUB boot added with 2.04-1ubuntu12.2 mention fallback for kernels that don't have EFISTUB. That didn't work for my kernels. Was it tested? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868352 Title: grub2 2.04-1ubuntu12.2 breaks boot on some machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1868352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868352] Re: grub2 2.04-1ubuntu12.2 breaks boot on some machines
Now it did. The page does not work well on mobile. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868352 Title: grub2 2.04-1ubuntu12.2 breaks boot on some machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1868352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868352] [NEW] grub2 2.04-1ubuntu12.2 breaks boot on some machines
Public bug reported: 2.04-1ubuntu12.2 broke boot on my machine. It doesn't work with kernels that don't have CONFIG_EFI_STUB=y configured. This really needs to fall back to the old mode if EFI handover is not supported by the kernel. Also, after using a kernel with CONFIG_EFI_STUB=y it still failed to boot one of my machines with root specified by UUID. I was able to workaround it by manually specifying the boot device with /dev/nvme0n1p2 at the grub menu, and then specifying GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.10-customskl x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Mar 20 21:19:01 2020 DistUpgraded: 2019-10-26 18:15:16,011 DEBUG running apport_crash() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: zfs, 0.8.3, 5.5.10-customskl, x86_64: installed zfs, 0.8.3, 5.5.9-customskl, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:872f] InstallationDate: Installed on 2012-12-04 (2664 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.5.10-customskl root=/dev/nvme0n1p2 ro rootflags=subvol=@ drm_kms_helper.edid_firmware=DP-1:edid/monoprice_28_4k.edid SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-26 (146 days ago) dmi.bios.date: 10/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2203 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2203:bd10/07/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4~yasi1~19.10 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1~yasi1~19.10 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1~yasi1~19.10 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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 2:2.99.917+git20191209.2226.f66d3954-0ubuntu0+yasi1~19.10 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan fonts kubuntu regression-update third-party-packages ubuntu ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868352 Title: grub2 2.04-1ubuntu12.2 breaks boot on some machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864533] Re: grub wrongly booting via bios entry point instead of efi when secureboot disabled
2.04-1ubuntu12.2 broke boot on my machine. It doesn't work with kernels that don't have CONFIG_EFI_STUB=y configured. This really needs to fall back to the old mode if EFI handover is not supported by the kernel. Also, after using a kernel with CONFIG_EFI_STUB=y it still failed to boot one of my machines with root specified by UUID. I was able to workaround it by manually specifying the boot device with /dev/nvme0n1p2 at the grub menu, and then specifying GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864533 Title: grub wrongly booting via bios entry point instead of efi when secureboot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1864533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
This is supposed to be fixed in Mesa 20.1 git by c81aa15d, gallium/auxiliary/vl: fix bob compute shaders for deint yuv. See: https://gitlab.freedesktop.org/mesa/mesa/-/commit/c81aa15d646215eac38c8e0b6dc1a10b35bc13c3 This could be backported to Mesa 20 if someone wants to try it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
I'm marking this as also affects alsa-plugins since that is shipping a jack plugin by default, and this bug is triggered when jack isn't even running. Programs that scan for ALSA devices pick up that jack plugin and trigger the double close. ** Also affects: alsa-plugins (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/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859295] [NEW] zoneminder 1.32.3-2build1 does not work with MySQL 8
Public bug reported: The zoneminder 1.32.3-2 package was rebuilt against MySQL for eoan. However, zoneminder 1.32.3 is incompatible with MySQL 8. The database uses several reserved keywords as table and column names that are not escaped with backticks in php, perl and C++ code in the project. Reserved keywords include Function, Groups and System. It also uses the MySQL password command which is no longer available in MySQL. It doesn't look like the package was tested after doing the rebuild against MySQL 8. I've backported a patch to 1.32.3 from upstream git master. I'm not sure it's complete, but it works for my use cases. ** Affects: zoneminder (Ubuntu) Importance: Undecided Status: New ** Patch added: "Fix compatibility with MySQL 8." https://bugs.launchpad.net/bugs/1859295/+attachment/5319302/+files/fix-mysql8.patch ** Bug watch added: github.com/ZoneMinder/zoneminder/issues #2685 https://github.com/ZoneMinder/zoneminder/issues/2685 ** Bug watch added: github.com/ZoneMinder/zoneminder/issues #2659 https://github.com/ZoneMinder/zoneminder/issues/2659 ** Bug watch added: github.com/ZoneMinder/zoneminder/issues #2658 https://github.com/ZoneMinder/zoneminder/issues/2658 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859295 Title: zoneminder 1.32.3-2build1 does not work with MySQL 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zoneminder/+bug/1859295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859295] Re: zoneminder 1.32.3-2build1 does not work with MySQL 8
Upstream bug reports: https://github.com/ZoneMinder/zoneminder/issues/2685 https://github.com/ZoneMinder/zoneminder/issues/2659 https://github.com/ZoneMinder/zoneminder/issues/2658 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859295 Title: zoneminder 1.32.3-2build1 does not work with MySQL 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zoneminder/+bug/1859295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859293] Re: davfs2 umount.davfs crashes when compiled with gcc 9
Upstream bug: http://savannah.nongnu.org/bugs/index.php?56286 ** Bug watch added: Non-GNU Savannah Bug Tracker #56286 http://savannah.nongnu.org/bugs/?56286 ** Bug watch added: Red Hat Bugzilla #1762083 https://bugzilla.redhat.com/show_bug.cgi?id=1762083 ** Also affects: davfs2 (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1762083 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859293 Title: davfs2 umount.davfs crashes when compiled with gcc 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/davfs2/+bug/1859293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859293] Re: davfs2 umount.davfs crashes when compiled with gcc 9
Upstream fix: http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/src/umount_davfs.c?r1=1.2.4.6&r2=1.2.4.7 This is fixed in upstream davfs2 1.5.6. A version bump will fix this package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859293 Title: davfs2 umount.davfs crashes when compiled with gcc 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/davfs2/+bug/1859293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859293] [NEW] davfs2 umount.davfs crashes when compiled with gcc 9
Public bug reported: davfs2 uses the fscanf format string "%a[0-9]". "%a" is part of C89, but not C99, and tells fscanf to do the string allocation. The fscanf man page states: Note that the a modifier is not available if the program is compiled with gcc -std=c99 or gcc -D_ISOC99_SOURCE (unless _GNU_SOURCE is also specified), in which case the a is interpreted as a specifier for floating-point numbers (see above). Support for the m modifier was added to glibc starting with version 2.7, and new programs should use that modifier instead of a. Switching the a to an m prevents the crash. ** Affects: davfs2 (Ubuntu) Importance: Undecided Status: New ** Patch added: "Fix crash in umount due to fscanf format" https://bugs.launchpad.net/bugs/1859293/+attachment/5319301/+files/fixfscanf.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859293 Title: davfs2 umount.davfs crashes when compiled with gcc 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/davfs2/+bug/1859293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859293] Re: davfs2 umount.davfs crashes when compiled with gcc 9
This crash happens in eoan with davfs2 1.5.5 which was built with gcc 9. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859293 Title: davfs2 umount.davfs crashes when compiled with gcc 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/davfs2/+bug/1859293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
Can this package get updated to 1.9.13, or at least patched in time for 20.04? The security exploitability of this bug may be low, but the impact on affected users is high. It causes hard to debug, random crashes of other programs (e g. Kodi) that are scanning ALSA devices when the jack daemon isn't even started. On Wed, Nov 20, 2019, 10:40 PM Teeedubb <1833...@bugs.launchpad.net> wrote: > Hi, > > I am experiencing the same issue with Kodi 18.5 and Xubuntu 19.10 with > similar stack traces to joe-yasi. Is there anyway to install the updated > package via Ubuntu updates? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1833479 > > Title: > libjack-jackd2-0 double close on a failure to connect to jackd which > causes crashes in multithreaded programs > > Status in jackd2 package in Ubuntu: > Confirmed > Status in jackd2 package in Debian: > Confirmed > > Bug description: > After upgrading to Ubuntu 19.04, I started experiencing sporadic > crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded > alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin > is enabled by default in /etc/alsa/conf.d/50-jack.conf. > > The crashes are caused by a race condition when kodi's audio engine > thread is enumerating the ALSA sound devices, and the udev thread is > enumerating the udev devices triggered by the sound device add from > turning the AVR on. > > When enumerating the ALSA jack plugin device, it tries to connect to > connect to jackd. Since I don't have jackd installed, it fails to > connect. libjack closes the socket on error, and then closes it again > in it's cleanup code. Since it's closing the same file descriptor > twice, it interacts with other threads that have potentially opened > file descriptors, and causes the crash. > > This same bug could potentially affect other multi-threaded programs > that enumerate ALSA devices. > > Fix committed upstream: > > https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
jackd2 released version 1.9.13 which includes this fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
I just requested one and received: CVE-2019-13351 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-13351 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
** Description changed: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa- - plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is + plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. - When enumering the ALSA jack plugin device, it tries to connect to + When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. - This same bug could potentially affect other multithreaded programs that - enumerate ALSA devices. + This same bug could potentially affect other multi-threaded programs + that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
I'm marking this a security bug, since all double close bugs can potentially be security bugs in multithreaded programs depending on the close interleaving. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
See kodi issue with stack traces: https://github.com/xbmc/xbmc/issues/16258 ** Also affects: jackd2 (Debian) 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/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
** Patch added: "Set-fSocket-to--1-after-close-on-an-error-to-prevent-a-double-close.patch" https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+attachment/5271631/+files/Set-fSocket-to--1-after-close-on-an-error-to-prevent-a-double-close.patch ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833479] [NEW] libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
*** This bug is a security vulnerability *** Public security bug reported: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa- plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumering the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multithreaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Affects: jackd2 (Debian) Importance: Undecided Status: New ** Bug watch added: github.com/xbmc/xbmc/issues #16258 https://github.com/xbmc/xbmc/issues/16258 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800526] Re: After Upgrading from 18.04.1 to 18.10 librdb1 can not be installed
It looks like oath-toolkit 2.6.1-1.2ubuntu0.18.10.1 was pushed to cosmic-updates resolving bug 1783706. Will this be resolved soon? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800526 Title: After Upgrading from 18.04.1 to 18.10 librdb1 can not be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1800526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800746] [NEW] Versioning mess upon upgrade from bionic to cosmic
Public bug reported: Since the binary packages have different versions from the source package for the gcc-defaults package, but generate the deb revision based on the source package, some binary packages did not upgrade when upgrading from bionic to cosmic. In my case, these two packages were the bionic versions: gdc:amd64 4:8.2.0-1ubuntu2.1 libgphobos-dev:amd64 8.2.0-1ubuntu2.1 cosmic has gdc:amd64 4:8.2.0-1ubuntu1 libgphobos-dev:amd64 8.2.0-1ubuntu1 gccgo* also has the same problem. ** Affects: gcc-defaults (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/1800746 Title: Versioning mess upon upgrade from bionic to cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1800746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796645] Re: [SRU] ceph 12.2.8
I think this needs to get pushed to cosmic as well. Cosmic has 12.2.4 which created a bit of a mess on upgrade from bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796645 Title: [SRU] ceph 12.2.8 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1796645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788448] Re: CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11
It looks like libx11-1.6.6 was pulled into cosmic. So this is fixed there. This still needs a backport to earlier releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1788448 Title: CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1788448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788448] [NEW] CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11
*** This bug is a security vulnerability *** Public security bug reported: There are 3 security issues reported in libx11 that are fixed upstream in libx11 1.6.6. Bugs announced: https://lists.x.org/archives/xorg-announce/2018-August/002915.html Release announcement of libx11 1.6.6 with commits fixing them listed: https://lists.x.org/archives/xorg-announce/2018-August/002916.html ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14598 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14599 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14600 ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788448 Title: CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1788448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719724] Re: zfs-auto-snapshot 1.2.2-1 does not make snapshots
Most of the changes between 1.2.2 and 1.2.4 are related to fixing this bug. "make --quiet really quiet" and it's merge are the only things not related. All of the cron cleanups are for fixing this issue: https://github.com/zfsonlinux/zfs-auto-snapshot/commits/upstream/1.2.4 I've been running 1.2.4 on Artful in my PPA for a while. I'd could do the SRU backport, but I won't be able to get to it for at least 2 weeks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719724 Title: zfs-auto-snapshot 1.2.2-1 does not make snapshots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-auto-snapshot/+bug/1719724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719724] Re: zfs-auto-snapshot 1.2.2-1 does not make snapshots
** Summary changed: - zfs-auto-snapshot 1.2.2-1 is broken + zfs-auto-snapshot 1.2.2-1 does not make snapshots -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719724 Title: zfs-auto-snapshot 1.2.2-1 does not make snapshots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-auto-snapshot/+bug/1719724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719724] Re: zfs-auto-snapshot 1.2.2-1 is broken
Is this update going to make artful? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719724 Title: zfs-auto-snapshot 1.2.2-1 is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-auto-snapshot/+bug/1719724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719724] Re: zfs-auto-snapshot 1.2.2-1 is broken
The Debian bugs for the issues with 1.2.2 are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850776 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874182 1.2.3 and 1.2.4 were bug fix releases that fix this cron issue. With 1.2.2, the hourly, weekly and monthly snapshots do not happen. If a user was relying on them from a previous version of this tool, they could have data loss due to the missing snapshots. ** Bug watch added: Debian Bug tracker #850776 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850776 ** Bug watch added: Debian Bug tracker #874182 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874182 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719724 Title: zfs-auto-snapshot 1.2.2-1 is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-auto-snapshot/+bug/1719724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719724] Re: zfs-auto-snapshot 1.2.2-1 is broken
** Tags added: artful ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719724 Title: zfs-auto-snapshot 1.2.2-1 is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-auto-snapshot/+bug/1719724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719724] Re: zfs-auto-snapshot 1.2.2-1 is broken
I believe this update should have a FeatureFreeze exception. The current version in artful is non-functional due to the broken cron scripts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719724 Title: zfs-auto-snapshot 1.2.2-1 is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-auto-snapshot/+bug/1719724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719724] [NEW] zfs-auto-snapshot 1.2.2-1 is broken
Public bug reported: zfs-auto-snapshot 1.2.2-1 has broken exec logic in cron which causes it to not work at all. Upstream has released 1.2.4 which fixes the broken cron syntax issues. Debian has released it as 1.2.4-1. There are no reverse dependencies on zfs-auto-snapshot. ** Affects: zfs-auto-snapshot (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/1719724 Title: zfs-auto-snapshot 1.2.2-1 is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-auto-snapshot/+bug/1719724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719360] Re: libhdhomerun ABI breakage
** Also affects: kodi-pvr-hdhomerun (Ubuntu) Importance: Undecided Status: New ** Also affects: hdhomerun-config-gui (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/1719360 Title: libhdhomerun ABI breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdhomerun-config-gui/+bug/1719360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719360] Re: libhdhomerun ABI breakage
The kodi-pvr-hdhomerun and hdhomerun-config-gui packages are dependent on libhdhomerun3, and haven't been rebuilt since the libhdhomerun upgrade from 20161117-2 to 20170815-1. These packages are built against the old ABI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719360 Title: libhdhomerun ABI breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdhomerun-config-gui/+bug/1719360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719360] Re: libhdhomerun ABI breakage
I agree this should be a FreezeException due to the ABI breakage with 20170815-1. libhdhomerun changed some type definitions for exported functions between 20161117 and 20170815. See: https://github.com/Silicondust/libhdhomerun/commit/94edccd040a5a8021d28c37ca51677d8a8d9d07c https://github.com/Silicondust/libhdhomerun/commit/1d68aab36702497674cc26907bb48fff5ea8b7ee This causes the ABI differences between the versions, but the soname version wasn't bumped between 20161117-2 and 20170815-1. The soname version was bumped from 3 to 4 with 20170815-2 in Debian. If this fix isn't made, packages that were built against the previous 20161117-2 dev package won't work properly with 20170815-1 due to the ABI change. To fix this, the libhdhomerun package should be bumped to 20170815-2, and all dependencies on libhdhomerun3 rebuilt against the new dev package to get the new libhdhomerun4 dependency. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719360 Title: libhdhomerun ABI breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhdhomerun/+bug/1719360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719360] [NEW] libhdhomerun ABI breakage
Public bug reported: There was an ABI change with the bump to version 20170815-1 of libhdhomerun (the types of some exported function arguments were changed). libhdhomerun 20170815-2 has been released at debian which bumps libhdhomerun3 to libhdhomerun4 to reflect the ABI change. Can Ubuntu pull in libhdhomerun 20170815-2 and rebuild dependencies for Artful? ** Affects: libhdhomerun (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/1719360 Title: libhdhomerun ABI breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhdhomerun/+bug/1719360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670137] Re: cache on NVMe inhibits proper suspend/hibernate - zfs l2arc
I've attached my workaround script. To use: change the ZFSPOOLNAME variable in the script to the name of the zfspool with an NVMe L2ARC. change the NVMEL2ARCPART to the name of the cache partition. sudo cp zpool-offline-cache.sh /lib/systemd/system-sleep/ sudo chmod +x /lib/systemd/system-sleep/zpool-offline-cache.sh ** Attachment added: "L2ARC workaround sleep script" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+attachment/4954099/+files/zpool-offline-cache.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670137 Title: cache on NVMe inhibits proper suspend/hibernate - zfs l2arc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691532] Re: CVE-2016-7953 in libxvmc 1.0.9
Is this going to get pulled into Artful? It's been in Debian since Dec 5, 2016. It made it into Debian 9. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691532 Title: CVE-2016-7953 in libxvmc 1.0.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxvmc/+bug/1691532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670137] Re: cache on NVMe inhibits proper suspend/hibernate - zfs l2arc
That info is from: zpool status -v I've worked around this suspend issue by writing a script to take the NVMe L2ARC cache offline during suspend, and bring it back online on resume. The issue with bcache on suspend that I had for a similar situation is because a read can trigger a write to the cache when writes have been shut off during suspend. Potentially, ZFS could temporarily disable writes to the L2ARC during suspend and reenable on resume to prevent writing when unable to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670137 Title: cache on NVMe inhibits proper suspend/hibernate - zfs l2arc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670137] Re: zfs l2arc cache inhibits proper suspend
I am also seeing this issue with zfs and l2arc cache on an NVMe and 4.10.14 on zesty. I've seen it in the past with btrfs, and a bcache cache on NVMe as well, but not with the bcache cache on a SATA SSD. I will move my zfs l2arc cache to a SATA SSD to see if that fixes suspend. This is probably an issue in the NVMe kernel stack. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670137 Title: zfs l2arc cache inhibits proper suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641468] Re: systemd-resolve: fallback from resolve causes lookup of local network hosts to fail
I've just upgraded to zesty, and this problem is still present. Since systemd-resolved is sticking a 127.0.0.53 nameserver in resolv.conf, the problem is worse. To work around it, I have to replace resolv.conf with the old dnsmasq 127.0.1.1 address instead to prevent DNS lookups from going through systemd-resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641468 Title: systemd-resolve: fallback from resolve causes lookup of local network hosts to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1641468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671799] Re: FFe: xserver 1.19.3
Any reason libx11 wasn't bumped for zesty this? 1.6.4 has some security fixes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671799 Title: FFe: xserver 1.19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631796] Re: Yakkety version of transcode needed (removal causes unmet dependencies)
This gentoo patch is probably cleaner than my patch which leaves a bunch of warnings in place: https://gitweb.gentoo.org/repo/gentoo.git/tree/media-video/transcode/files/transcode-1.1.7-ffmpeg29.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631796 Title: Yakkety version of transcode needed (removal causes unmet dependencies) To manage notifications about this bug go to: https://bugs.launchpad.net/mythtv/+bug/1631796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631796] Re: Yakkety version of transcode needed (removal causes unmet dependencies)
This patch fixes the build with newer ffmpeg. ** Patch added: "Fix build with newer ffmpeg PIXFMT names" https://bugs.launchpad.net/ubuntu/+source/transcode/+bug/1631796/+attachment/4779421/+files/pixfmt_av.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631796 Title: Yakkety version of transcode needed (removal causes unmet dependencies) To manage notifications about this bug go to: https://bugs.launchpad.net/mythtv/+bug/1631796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631796] Re: Yakkety version of transcode needed (removal causes unmet depdendencies)
** Bug watch added: code.mythtv.org/trac/ #12898 http://code.mythtv.org/trac/ticket/12898 ** Changed in: mythtv Importance: Undecided => Unknown ** Changed in: mythtv Status: New => Unknown ** Changed in: mythtv Remote watch: None => code.mythtv.org/trac/ #12898 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631796 Title: Yakkety version of transcode needed (removal causes unmet depdendencies) To manage notifications about this bug go to: https://bugs.launchpad.net/mythtv/+bug/1631796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631796] Re: Yakkety version of transcode needed (removal causes unmet depdendencies)
** Also affects: mythtv 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/1631796 Title: Yakkety version of transcode needed (removal causes unmet depdendencies) To manage notifications about this bug go to: https://bugs.launchpad.net/mythtv/+bug/1631796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641468] [NEW] systemd-resolve: fallback from resolve causes lookup of local network hosts to fail
Public bug reported: After upgrading to Ubuntu 16.10 from 16.04, DNS resolution of hosts on my local network fails. The hosts line in /etc/nsswitch.conf is: hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns mdns4 If I change it to: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 I can resolve hosts on my local network. Appending .local to the hostname also allows DNS resolution since systemd-resolve returns a different error for that case. Ex: systemd-resolve rt-ac66u rt-ac66u: resolve call failed: All attempts to contact name servers or networks failed systemd-resolve rt-ac66u.local rt-ac66u.local: resolve call failed: No appropriate name servers or networks for name found "dig rt-ac66u" returns the correct ip. ** Affects: systemd (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/1641468 Title: systemd-resolve: fallback from resolve causes lookup of local network hosts to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1641468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624560] [NEW] Use XCB 64-bit sequence API
Public bug reported: libx11 suffers from 32-bit sequence wraparound for programs that make a large number of calls to the server. (See: https://lists.x.org/archives /xorg-devel/2013-October/038370.html ) The Freedesktop bug is here: https://bugs.freedesktop.org/show_bug.cgi?id=71338 This was fixed with this commit: https://cgit.freedesktop.org/xorg/lib/libX11/commit/?id=a72d2d06c002b644b7040a0a9936c8525e092ba8 This fix requires libxcb >= 1.11.1 for the 64-bit sequence API. Xenial and higher ship libxcb 1.11.1. Can this patch be pulled into the Ubuntu package? ** Affects: libx11 (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/1624560 Title: Use XCB 64-bit sequence API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1624560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548766] Re: Plasma crashes when the monitor is disconnected (when it sleeps, in some cases)
I've been suffering the same issue. Plasma crashes every time my 4K monitor sleeps or is turned off in Kubuntu 15.10. I had to pull in Qt 5.5 and this patch to make my desktop usable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548766 Title: Plasma crashes when the monitor is disconnected (when it sleeps, in some cases) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1548766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492774] Re: update-initramfs doesn't copy symlinked firmware files
*** This bug is a duplicate of bug 1496163 *** https://bugs.launchpad.net/bugs/1496163 ** This bug has been marked a duplicate of bug 1496163 i915 firmware is not copied to initrd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492774 Title: update-initramfs doesn't copy symlinked firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1492774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492774] Re: update-initramfs doesn't copy symlinked firmware files
This bug is a duplicate of #1496163. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492774 Title: update-initramfs doesn't copy symlinked firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1492774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492774] Re: update-initramfs doesn't copy symlinked firmware files
I want to add that this isn't in the Debian version of the package. The change to remove the call to copy_exec is what broke this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492774 Title: update-initramfs doesn't copy symlinked firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1492774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492774] [NEW] update-initramfs doesn't copy symlinked firmware files
Public bug reported: In /usr/share/initramfs-tools/hook-functions, the firmware is copied to the initramfs using: cp -a "$firmware" "$target_dir" For symlinked firmware such as /lib/firmware/i915/skl_dmc_ver1.bin for Intel Skylake, this results in a copy of the symlink instead of the firmware file. update-initramfs then deletes the broken symlink before packaging. This needs to be replaced with a cp command that dereferences symlinks such as: cp -prL "$firmware" "$target_dir" I ran into this on vivid, but it is in wily as well. ** Affects: initramfs-tools (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/1492774 Title: update-initramfs doesn't copy symlinked firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1492774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383036] [NEW] make-kpkg creates broken symlinks in the headers package
Public bug reported:
When building kernels with make-kpkg 13.014, it creates a broken symlink for
the architecture headers:
/usr/src/linux-headers-${KERNEL_VERSION}/include/asm/asm-x86 -> asm-x86
This symlink is breaking the nvidia driver compile. Removing it fixes
their build.
** Affects: kernel-package (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/1383036
Title:
make-kpkg creates broken symlinks in the headers package
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1383036/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1226766] Re: Mountall fails to mount NFS partitions on boot with GigE network managed by NM
I upgraded to Utopic and this problem got worse on that machine. I've attached the new mountall.log. The fstab line for the mount is now: rt-ac66u:/tmp/mnt/yasimedia /mnt/readyshare nfs _netdev,hard,intr,exec,nodev,nosuid,async,nobootwait 0 0 It looks like it's not detecting the mount as a remote share. The log says /mnt/readyshare is nowait. My workaround for this was sending a SIGUSR1 to mountall in rc.local, but that's not working anymore. It does not mount the NFS mount. A manual /mnt/readyshare works. ** Attachment added: "mountall.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1226766/+attachment/4209192/+files/mountall.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226766 Title: Mountall fails to mount NFS partitions on boot with GigE network managed by NM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1226766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1200006] Re: appmenu-gtk support dropped, but unity-gtk-module doesn't work outside unity
It's still working for me here. I just tried Pidgin to make sure the menu is exported. You'll need appmenu-gtk from the PPA and the version of GTK2 in the PPA. appmenu-gtk requires a patched version of GTK2. This will not work for GTK3 apps as I have not forward ported the patch for GTK3 from raring. You'll also need libdbusmenu-qt2. Do QT4 apps properly export the menu in KDE for you? Firefox and Libreoffice are also different since they don't use standard GTK2 menus. You'll need to set ui.use_unity_menubar = true in about:config for Firefox. The Firefox package will also have to have the unity menubar patch applied (which the standard Ubuntu Firefox has). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/126 Title: appmenu-gtk support dropped, but unity-gtk-module doesn't work outside unity To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1343800] [NEW] upstart 1.12.1-0ubuntu4.1 breaks xsession start with lightdm
Public bug reported: After upgrading to upstart 1.12.1-0ubuntu4.1, logging in via lightdm freezes on xsession start. The choice of xsession doesn't matter. It will not load KDE or TWM. It freezes after pressing login without trying to start the xsession. startx from the commandline launches the xsession properly. lightdm works again after reverting to upstart 1.12.1-0ubuntu4. ** Affects: upstart (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/1343800 Title: upstart 1.12.1-0ubuntu4.1 breaks xsession start with lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1343800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317528] Re: Packages nvidia-libopencl1-... don't provide libopencl-1.1-1 and libopencl-1.2-1, making some packages uninstallable
That's a problem with the wine dependencies. It shouldn't be an explicit dependency on ocl-icd-libopencl1. For other 32-bit packages that depend on libopencl-1.1-1, picking either ocl-icd-libopencl1 or nvidia- libopencl-1.1-1 should work. This needs to be Multi-Arch aware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317528 Title: Packages nvidia-libopencl1-... don't provide libopencl-1.1-1 and libopencl-1.2-1, making some packages uninstallable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1317528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317528] Re: Packages nvidia-libopencl1-... don't provide libopencl-1.1-1 and libopencl-1.2-1, making some packages uninstallable
In order to truly fix this, nvidia-libopencl1-, libcuda1- and nvidia-opencl-icd- will need to be made Multi-Arch aware. Right now, the amd64 package includes the 32-bit libraries. Since wine is 32-bit, it'll try to pull in nvidia-libopencl1-:i386 which conflicts with nvidia-libopencl1-:amd64 with the provides change to libopencl-1.1-1, etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317528 Title: Packages nvidia-libopencl1-... don't provide libopencl-1.1-1 and libopencl-1.2-1, making some packages uninstallable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1317528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280665] Re: libsdl1.2 always uses backingstore which causes tearing in modern X servers
I can verify that the bug still occurs with libsdl1.2debian 1.2.15-8ubuntu1 and is fixed by libsdl1.2debian 1.2.15-8ubuntu1.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280665 Title: libsdl1.2 always uses backingstore which causes tearing in modern X servers To manage notifications about this bug go to: https://bugs.launchpad.net/libsdl/+bug/1280665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280665] Re: libsdl1.2 always uses backingstore which causes tearing in modern X servers
It should be noted that upstream is not planning on making another SDL 1.2 release. They are building a compatibility API for SDL 2.0 instead. We should apply this patch until that compatibility API is ready. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280665 Title: libsdl1.2 always uses backingstore which causes tearing in modern X servers To manage notifications about this bug go to: https://bugs.launchpad.net/libsdl/+bug/1280665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307792] [NEW] nvidia-opencl-dev depend on nvidia-libopencl1-331 is too strict
Public bug reported: The nvidia-opencl-dev package depends on nvidia-libopencl1-331 | nvidia- libopencl1-331-updates. This dependency is too strict as nvidia- libopencl1-334 and nvidia-libopencl1-337 will also satisfy it. There should be a virtual dependency (libopencl1) ** Affects: nvidia-cuda-toolkit (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/1307792 Title: nvidia-opencl-dev depend on nvidia-libopencl1-331 is too strict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1307792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304787] [NEW] startkde qdbus invocation is broken with the 4:4.11.8-0ubuntu4 change
Public bug reported: The change to startkde introduced in kde-workspace 4:4.11.8-0ubuntu4 breaks KDE startup. The correct change for the qdbus line is: qdbus="env QT_SELECT=qt4 qdbus". ** Affects: kde-workspace (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/1304787 Title: startkde qdbus invocation is broken with the 4:4.11.8-0ubuntu4 change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1304787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280665] Re: libsdl1.2 always uses backingstore which causes tearing in modern X servers
** Description changed: libsdl1.2 always enables backingstore when it is present in the X server. For modern X servers, backingstore is implemented by redirecting through the composite extension. This causes tearing on SDL applications such as xbmc because the redirected rendering is not guaranteed to be synchronized. A discussion of the problem by Nvidia is here: https://devtalk.nvidia.com/default/topic/679688/linux/tearing-in-sdl-1-2 -apps-unless-composite-extension-is-completely- disabled-/post/4111287/#4111287 The upstream bug is here: - https://bugs.freedesktop.org/show_bug.cgi?id=74158 + https://bugzilla.libsdl.org/show_bug.cgi?id=2383 I have a patch that restores a check for the SDL_VIDEO_X11_BACKINGSTORE environment variable before trying to enable backingstore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280665 Title: libsdl1.2 always uses backingstore which causes tearing in modern X servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsdl1.2/+bug/1280665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280665] [NEW] libsdl1.2 always uses backingstore which causes tearing in modern X servers
Public bug reported: libsdl1.2 always enables backingstore when it is present in the X server. For modern X servers, backingstore is implemented by redirecting through the composite extension. This causes tearing on SDL applications such as xbmc because the redirected rendering is not guaranteed to be synchronized. A discussion of the problem by Nvidia is here: https://devtalk.nvidia.com/default/topic/679688/linux/tearing-in-sdl-1-2 -apps-unless-composite-extension-is-completely- disabled-/post/4111287/#4111287 The upstream bug is here: https://bugs.freedesktop.org/show_bug.cgi?id=74158 I have a patch that restores a check for the SDL_VIDEO_X11_BACKINGSTORE environment variable before trying to enable backingstore. ** Affects: libsdl1.2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "sdl-check-for-SDL_VIDEO_X11_BACKINGSTORE.patch" https://bugs.launchpad.net/bugs/1280665/+attachment/3982053/+files/sdl-check-for-SDL_VIDEO_X11_BACKINGSTORE.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280665 Title: libsdl1.2 always uses backingstore which causes tearing in modern X servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsdl1.2/+bug/1280665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196752] Re: Suspend only works once when using upower with logind -- s-shim needs to call /lib/systemd/system-sleep/*
KDE PowerDevil now checks for Upstart if the systemd version check fails. The version API implementation is no longer needed. The call to the sleep scripts still needs to happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196752 Title: Suspend only works once when using upower with logind -- s-shim needs to call /lib/systemd/system-sleep/* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1196752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1275030] [NEW] kubuntu-settings-desktop postinst and postrm are broken in 14.04ubuntu6
Public bug reported:
kubuntu-settings-desktop version 14.04ubuntu6 fails to install due to
syntax errors in kubuntu-settings-desktop.postinst and kubuntu-settings-
desktop.postinst. The warn() functions in these scripts are missing a
semicolon:
warn() { echo "W: $1" }
should be
warn() { echo "W: $1" ; }
** Affects: kubuntu-settings (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1275030
Title:
kubuntu-settings-desktop postinst and postrm are broken in
14.04ubuntu6
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1275030/+subscriptions
--
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1226766] Re: Mountall fails to mount NFS partitions on boot with GigE network managed by NM
I've just started seeing this again after upgrading to trusty. This time sending SIGUSR1 does not work. The mount.nfs process appears hung on boot. Killing this process, and then sending SIGUSR1 to mountall results in the partition mounting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226766 Title: Mountall fails to mount NFS partitions on boot with GigE network managed by NM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1226766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252664] Re: nvidia-331-uvm 331.20-0ubuntu1: nvidia-331-uvm kernel module failed to build [error: incompatible types when assigning to type ‘uid_t’ from type ‘kuid_t’]
So the reason I decided to check for kernel version instead of CONFIG_UIDGID_STRICT_TYPE_CHECKS was for possible future proofing. If the kernel in the future fragments with yet another config option for kuid_t, they would likely implement another __kuid_val function for that, and the patch would still work. Granted, we aren't guaranteed that something else won't break in a kernel API change, so it probably doesn't matter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252664 Title: nvidia-331-uvm 331.20-0ubuntu1: nvidia-331-uvm kernel module failed to build [error: incompatible types when assigning to type ‘uid_t’ from type ‘kuid_t’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1252664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252664] Re: nvidia-331-uvm 331.20-0ubuntu1: nvidia-331-uvm kernel module failed to build [error: incompatible types when assigning to type ‘uid_t’ from type ‘kuid_t’]
I dug through git, and kuid_t/kgid_t were introduced in kernel 3.5. The proper thing to do is to call __kuid_val(uid) to convert to uid_t on these kernels. The bug isn't a problem introduced with kernel 3.12. It is a problem with all kernels compiled with CONFIG_UIDGID_STRICT_TYPE_CHECKS. This patch should fix the problem for both cases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252664 Title: nvidia-331-uvm 331.20-0ubuntu1: nvidia-331-uvm kernel module failed to build [error: incompatible types when assigning to type ‘uid_t’ from type ‘kuid_t’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1252664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252664] Re: nvidia-331-uvm 331.20-0ubuntu1: nvidia-331-uvm kernel module failed to build [error: incompatible types when assigning to type ‘uid_t’ from type ‘kuid_t’]
** Patch added: "Fix building with CONFIG_UIDGID_STRICT_TYPE_CHECKS enabled" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1252664/+attachment/3943946/+files/buildfix_CONFIG_UIDGID_STRICT_TYPE_CHECKS.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252664 Title: nvidia-331-uvm 331.20-0ubuntu1: nvidia-331-uvm kernel module failed to build [error: incompatible types when assigning to type ‘uid_t’ from type ‘kuid_t’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1252664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252664] Re: nvidia-331-uvm 331.20-0ubuntu1: nvidia-331-uvm kernel module failed to build [error: incompatible types when assigning to type ‘uid_t’ from type ‘kuid_t’]
So it looks like the buildfix_kernel_3.12.patch is missing a check for CONFIG_UIDGID_STRICT_TYPE_CHECKS. The change to kuid_t only happens if that config flag is enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252664 Title: nvidia-331-uvm 331.20-0ubuntu1: nvidia-331-uvm kernel module failed to build [error: incompatible types when assigning to type ‘uid_t’ from type ‘kuid_t’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1252664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252664] Re: nvidia-331-uvm 331.20-0ubuntu1: nvidia-331-uvm kernel module failed to build [error: incompatible types when assigning to type ‘uid_t’ from type ‘kuid_t’]
The buildfix_kernel_3.12.patch breaks building on vanilla 3.12 kernels. The module builds fine without it on 3.12.6 In file included from /var/lib/dkms/nvidia-331-updates-uvm/331.20/build/nvidia_uvm_common.h:49:0, from /var/lib/dkms/nvidia-331-updates-uvm/331.20/build/nvidia_uvm_lite.c:26: /var/lib/dkms/nvidia-331-updates-uvm/331.20/build/nvidia_uvm_lite.c: In function ‘uvmlite_open’: /var/lib/dkms/nvidia-331-updates-uvm/331.20/build/nvidia_uvm_linux.h:395:70: error: request for member ‘val’ in something not a structure or union (((typeof(*current->cred) __force __kernel *)current->cred)->euid.val) ^ /var/lib/dkms/nvidia-331-updates-uvm/331.20/build/nvidia_uvm_lite.c:1326:39: note: in expansion of macro ‘NV_CURRENT_EUID’ pUvmPrivate->processRecord.euid = NV_CURRENT_EUID(); ^ make[3]: *** [/var/lib/dkms/nvidia-331-updates-uvm/331.20/build/nvidia_uvm_lite.o] Error 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252664 Title: nvidia-331-uvm 331.20-0ubuntu1: nvidia-331-uvm kernel module failed to build [error: incompatible types when assigning to type ‘uid_t’ from type ‘kuid_t’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1252664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1200006] Re: appmenu-gtk support dropped, but unity-gtk-module doesn't work outside unity
I've split them off into their own PPA: https://launchpad.net/~joe- yasi/+archive/appmenu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/126 Title: appmenu-gtk support dropped, but unity-gtk-module doesn't work outside unity To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1200006] Re: appmenu-gtk support dropped, but unity-gtk-module doesn't work outside unity
The Firefox problem is due to this bug: https://bugs.launchpad.net /globalmenu-extension/+bug/779344 I doubt anyone is looking at it because GTK+ apps don't work with KDE on saucy by default anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/126 Title: appmenu-gtk support dropped, but unity-gtk-module doesn't work outside unity To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1200006] Re: appmenu-gtk support dropped, but unity-gtk-module doesn't work outside unity
@avlas: Careful with my PPA, there's also experimental graphics drivers and stuff in there. I should probably split this out into another PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/126 Title: appmenu-gtk support dropped, but unity-gtk-module doesn't work outside unity To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1238221] [NEW] plasma-nm 0.9.3.0-0ubuntu3 is missing the program
Public bug reported: The published deb files for plasma-nm 0.9.3.0-0ubuntu3 are all nearly empty. They contain just the debian changelog and the copyright file. Something was missed when the transition package got added. ** Affects: plasma-nm (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/1238221 Title: plasma-nm 0.9.3.0-0ubuntu3 is missing the program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-nm/+bug/1238221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1226766] Re: Mountall fails to mount NFS partitions on boot
It's not just DNS. I changed the /etc/fstab entry to the IP address instead of the hostname, and it still fails to mount with: mount.nfs: mount system call failed mountall: mount /mnt/readyshare [811] terminated with status 32 mountall: Disconnected from Plymouth It must be racing the network stack to come up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226766 Title: Mountall fails to mount NFS partitions on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1226766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1226766] Re: Mountall fails to mount NFS partitions on boot with GigE network managed by NM
sudo status network-interface INTERFACE=eth0 network-interface (eth0) start/running Yes. It shows as running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226766 Title: Mountall fails to mount NFS partitions on boot with GigE network managed by NM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1226766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1226766] Re: Mountall fails to mount NFS partitions on boot
Okay, sending SIGUSR1 after booting does bring up the NFS mounts. The network configuration is just gigabit ethernet on eth0 configured via DHCP through NetworkManager as a system connection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226766 Title: Mountall fails to mount NFS partitions on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1226766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217610] Re: NFS mounts don't mount on boot
Filed as: #1226766 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217610 Title: NFS mounts don't mount on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1217610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1226766] Re: Mountall fails to mount NFS partitions on boot
Here is the mountall.log requested in bug #1217610 ** Attachment added: "mountall.log with --verbose passed." https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1226766/+attachment/3825793/+files/mountall.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226766 Title: Mountall fails to mount NFS partitions on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1226766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1226766] [NEW] Mountall fails to mount NFS partitions on boot
Public bug reported: NFS partitions fail to mount on boot, and mountall freezes without mounting them. If I revert this change to the init script: . /etc/default/rcS || true [ -f /forcefsck ] && force_fsck="--force-fsck" [ "$FSCKFIX" = "yes" ] && fsck_fix="--fsck-fix" + # Doesn't work so well if mountall is responsible for mounting /proc, heh. + if [ -e /proc/cmdline ]; then + for arg in $(cat /proc/cmdline); do + case $arg in + -q|--quiet|-v|--verbose|--debug) + debug_arg=$arg + ;; + esac + done + fi # set $LANG so that messages appearing in plymouth are translated if [ -r /etc/default/locale ]; then . /etc/default/locale || true export LANG LANGUAGE LC_MESSAGES LC_ALL fi - exec mountall --daemon $force_fsck $fsck_fix + exec mountall --daemon $force_fsck $fsck_fix $debug_arg end script it works. It seems strange that this would stop NFS from mounting on boot. It appears that the NFS mounts are occurring before DNS is up. mountall.log contains: mount.nfs: Failed to resolve server rt-ac66u: Name or service not known mountall: mount /mnt/readyshare [815] terminated with status 32 Filesystem could not be mounted: /mnt/readyshare mountall: Disconnected from Plymouth ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: mountall 2.51 Uname: Linux 3.11.1-customatom x86_64 NonfreeKernelModules: nvidia .run.mount.utab: ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Tue Sep 17 14:49:53 2013 ExecutablePath: /sbin/mountall InstallationDate: Installed on 2012-04-15 (520 days ago) InstallationMedia: Mythbuntu 12.04 "Precise Pangolin" - Beta amd64 (20120328) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.1-customatom root=UUID=708b3ba8-c42a-4adf-a195-c0fb8d8f8dd3 ro --verbose SourcePackage: mountall UpgradeStatus: Upgraded to saucy on 2013-06-28 (81 days ago) ** Affects: mountall (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226766 Title: Mountall fails to mount NFS partitions on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1226766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217610] Re: NFS mounts don't mount on boot
/proc/cmdline is: BOOT_IMAGE=/boot/vmlinuz-3.11.1-customatom root=UUID=708b3ba8-c42a-4adf-a195-c0fb8d8f8dd3 ro So, none of those options are passed to the kernel. Mountall is starting, and everything but the NFS mounts are mounting fine. When NFS fails to mount without those lines, mountall is still running after boot and frozen. When I remove those lines, everything mounts and mountall finishes so it is no longer running after boot. It is very strange. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217610 Title: NFS mounts don't mount on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1217610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217610] Re: NFS mounts don't mount on boot
Hmm, so if I revert this change to the init script: . /etc/default/rcS || true [ -f /forcefsck ] && force_fsck="--force-fsck" [ "$FSCKFIX" = "yes" ] && fsck_fix="--fsck-fix" +# Doesn't work so well if mountall is responsible for mounting /proc, heh. +if [ -e /proc/cmdline ]; then +for arg in $(cat /proc/cmdline); do +case $arg in +-q|--quiet|-v|--verbose|--debug) +debug_arg=$arg +;; +esac +done +fi # set $LANG so that messages appearing in plymouth are translated if [ -r /etc/default/locale ]; then . /etc/default/locale || true export LANG LANGUAGE LC_MESSAGES LC_ALL fi -exec mountall --daemon $force_fsck $fsck_fix +exec mountall --daemon $force_fsck $fsck_fix $debug_arg end script it works. It seems strange that this would stop NFS from mounting on boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217610 Title: NFS mounts don't mount on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1217610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217610] Re: NFS mounts don't mount on boot
It's something with mountall. It was upgraded from 2.49 to 2.50 and 2.51 before the last reboot. I reverted to 2.50 and the problem still occured. I reverted to 2.49 and the NFS mounts come up on boot. I'll take a look at what changed in the mountall package between 2.49 and 2.50. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217610 Title: NFS mounts don't mount on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1217610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
