[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
Thanks. This is now fixed for me with the 470.57.02 and the 460.91.03. drivers from the normal repositories in 21.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
470 just got out of beta today: https://www.nvidia.com/Download/driverResults.aspx/177145/en-us https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470 shows in which repositories including PPAs it is available in. Currently only the beta is listed there. And a bug to track the testing and releases should be listed on https://people.canonical.com/~ubuntu-archive/pending-sru.html soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
You have to install another driver than nvidia-driver-460 in order to update all your packages again. This is because nvidia-driver-460 does have the version 460.80 in the repositories now. Easiest is to change to nvidia-driver-460-server if that works for you, next easiest is to enable the PPA I mentioned above to install the 470 beta driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
@Keith This does not seem to be kernel related, when I upgraded to 460.80 and 465.27 and got hit by this bug, I first tried to boot with older kernels I had installed with the same problem then. And look at https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782 there users have tried a lot of different kernels without it helping. You can either install the nvidia-driver-460-server which is at 460.73.01, or install it manually if it gives other problems, see above. Or use the 470 beta from https://launchpad.net/~albertomilone/+archive/ubuntu/nvidia-testing And then just update all other packages including kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934461] Re: Nvidia driver 460 fails in install on 21.04
Since you wrote in the other issue that you reinstalled 20.04 this should not be relevant anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934461 Title: Nvidia driver 460 fails in install on 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1934461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934461] Re: Nvidia driver 460 fails in install on 21.04
Hi Anatoli, There is a problem with your apt sources according to your screenshot. The 460.84 driver from 20.10 conflicts with the 460.80 driver from 21.04 Have a look in the other software tab in Software & Updates, where you might have the graphics-driver PPA enabled and set to groovy. Either disable it so you get the driver from the normal Ubuntu repositories, or set the distribution of the PPA to hirsute. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934461 Title: Nvidia driver 460 fails in install on 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1934461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
This is fixed with the new 470 beta drivers from https://launchpad.net/~albertomilone/+archive/ubuntu/nvidia-testing At least for me on my affected system. There are no 32bit packages there yet though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931131] Re: Update the 465 and the 460 NVIDIA driver series
I have tested 460.84 and 465.42 from jirsute-proposed on hirsute on a system affected by https://bugs.launchpad.net/ubuntu/+source/nvidia- graphics-drivers-465/+bug/1930733 The kernel oops still happens when I connect my Acer XF270HU monitor with DisplayPort, but with HDMI both drivers worked. I tested it with playing a bit of Hitman 2 with proton, and Total War: Warhammer II which is a Linux native game. I also checked that I can boot up with the new 450-server driver into a desktop with DisplayPort, and the same with 460-server, and here I also played the mentioned games without problems with DisplayPort All tests where done with the default 5.11 kernel from Hirsute from the linux-generic package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931131 Title: Update the 465 and the 460 NVIDIA driver series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
Gabe, this bug results in a complete locked up computer, not just a wrong resolution. I suggest you report a new bug with your problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
I have tried 460.84 and 465.31 on a fresh hirsute install upgraded to impish with proposed enabled. Both result in a kernel oops when using DisplayPort -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
The nvidia-driver-460-server packages in the Ubuntu repositries are on 460.73.01 I installed those, and disconnected my monitor from HDMI and connected with DisplayPort instead. This seems to work without problems. What is the purpose of the server packages? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
** Also affects: nvidia-graphics-drivers-460 (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/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930980] Re: Hang on loading initial ramdisk on kernels 5.4.0-72+, 5.11.0-16+ with nvidia drivers 440+
This looks similar to https://bugs.launchpad.net/ubuntu/+source/nvidia- graphics-drivers-465/+bug/1930733 Do you use DisplayPort? If yes can you try with HDMI? For me it only happens with DisplayPort -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930980 Title: Hang on loading initial ramdisk on kernels 5.4.0-72+, 5.11.0-16+ with nvidia drivers 440+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
I have a problem with DisplayPort on the new drivers too and created https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-465/+bug/1930733 about it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1925522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
460.80 does also work with HDMI -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers
I do not get a kernel oops with 465.27 when I attach my monitor with HDMI instead of DisplayPort ** Summary changed: - Kernel oops with the 460.80 and 465.27 drivers + Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] [NEW] Kernel oops with the 460.80 and 465.27 drivers
Public bug reported: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2:
[Bug 1908921] Re: No system tray detected by hp-systray
*** This bug is a duplicate of bug 1905370 *** https://bugs.launchpad.net/bugs/1905370 The update to gnome-shell-extension-appindicator 35-1 on hirsute today fixed this for me on hirsute. At least I got the applet loading without problems three restarts in a row, and recently it failed on every restart on the previous version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908921 Title: No system tray detected by hp-systray To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910798] Re: nvidia-graphics-drivers-460 went into updates at the same time as proposed
There where several security problems in 455 fixed with 460.32.03 https://nvidia.custhelp.com/app/answers/detail/a_id/5142 ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+question/694972 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910798 Title: nvidia-graphics-drivers-460 went into updates at the same time as proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1910798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901904] Re: [SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1
Hi Kopa, If you follow the instructions from the linked https://wiki.ubuntu.com/Testing/EnableProposed then you will only get the packages from proposed you specify from proposed. But you can also follow the links from where Timo wrote "Hello Stefan, or anyone else affected," in the recent comments whee the packages got to proposed https://launchpad.net/ubuntu/+source/virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.1 https://launchpad.net/ubuntu/+source/virtualbox-guest-additions- iso/6.1.16-1~ubuntu1.20.04.1 https://launchpad.net/ubuntu/+source/liblzf/3.6-2~ubuntu1.20.04.1 and get the deb files from there Use apt list --installed|grep virtualbox to see what virtualbox packages you have installed now and get the updated ones from the links. You also need https://launchpad.net/ubuntu/focal/+package/liblzf-dev -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901904 Title: [SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liblzf/+bug/1901904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910798] Re: nvidia-graphics-drivers-460 went into updates at the same time as proposed
I have upgraded to the 460 drivers on a 20.10 desktop with a 1050ti and on a 20.04 laptop with a 1050ti Mobile wihtout any roblems from apt. And both seems to work ok, but I have only used both for desktop stuff so far, not gaming or cuda yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910798 Title: nvidia-graphics-drivers-460 went into updates at the same time as proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1910798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901904] Re: [SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1
I have installed and tested some of the packages on 20.10 and 20.04 On 20.10 I installed virtualbox-dkms/groovy-proposed virtualbox-ext-pack/groovy-proposed virtualbox-qt/groovy-proposed virtualbox/groovy-proposed and I could use some previously installed VMs without problems then. virtualbox-guest-additions-iso/groovy-proposed was not available yet, I try to check tht when its in proposed. On 20.04 I installed virtualbox-guest-additions-iso/focal-proposed virtualbox-qt/focal-proposed virtualbox/focal-proposed virtualbox-dkms/focal-proposed and could also use previously installed VMs without problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901904 Title: [SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liblzf/+bug/1901904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910798] [NEW] nvidia-graphics-drivers-460 went into updates at the same time as proposed
Public bug reported: I noticed that I get the nvidia-graphics-drivers-460 as an upgrade from 455 on my 20.10 PC today, on the day after Nvidia released the first non beta of it. First I thought that I must had the PPA on, or proposed, or my mirror was messed up so I switched to the main server, but the packages do come from the normal groovy updates apt policy nvidia-dkms-455 nvidia-dkms-455: Installed: 455.45.01-0ubuntu0.20.10.1 Candidate: 460.32.03-0ubuntu0.20.10.1 Version table: 460.32.03-0ubuntu0.20.10.1 500 500 http://archive.ubuntu.com/ubuntu groovy-updates/restricted amd64 Packages *** 455.45.01-0ubuntu0.20.10.1 100 100 /var/lib/dpkg/status And not only for groovy, but also bionic and focal according to https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460 Is that really the intention? Then https://wiki.ubuntu.com/NVidiaUpdates needs some updating. And should it not have replaced 450 instead? Anyway I am going to upgrade and test it now. ** Affects: nvidia-graphics-drivers-460 (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/1910798 Title: nvidia-graphics-drivers-460 went into updates at the same time as proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1910798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890804] Re: 20.10 groovy proposed: resolvconf-pull-resolved.service fails to start if resolvconf is installed at the same time
This also happened for me on a 20.10 with resolvconf yesterday, I do not have proposed enabled on that system. I used the chroot process described at https://help.ubuntu.com/community/LiveCdRecovery to be able to get into that system and then uninstalling resolvconf after finding this bug and the mentioned debian bug. That fixed it. I have that system since 12.10 so before systemd. On another 20.10 I have installed as 19.10 there is no resolvconf installed and that did not see this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890804 Title: 20.10 groovy proposed: resolvconf-pull-resolved.service fails to start if resolvconf is installed at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1890804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876522] Re: apt chooses Ubuntu repo instead of nvidia-graphics PPA
According to the supported products at https://www.nvidia.com/en- us/drivers/unix/ 390 is the highest driver that support your GPU.I wonder why you did not get that installed automatically instead of the really old 340. You should try to install 390, and you do not need the PPA for that. However for those that can use 440 and want the newest 440.82 apt pinning works. Create a file named /etc/apt/preferences.d/priority-nvidia with this : Package: * Pin: release o=LP-PPA-graphics-drivers Pin-Priority: 1000 Check the policy with apt-cache policy nvidia-driver-440 and then install the driver. Can the version in the PPA for 440.82 in 20.04 please be bumped so its higher than 440.82+really.440.64? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876522 Title: apt chooses Ubuntu repo instead of nvidia-graphics PPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1876522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
I saw this bug mentioned on https://discourse.ubuntu.com/t/release-bugs- for-week-commencing-monday-24th-february-2020/14540 with the comment "can’t confirm, lew activity, suggest we untarget from rls set" It would really be a shame if this stays the way it is now, since it is annoying for those that are hit by it, although with an easy workaround, just do anything else requiring authorisation, and then the toggles work too. For example highlighting one source and then selecting edit and then ok without do any changes. Or just repeating the mouse clicks until it works like others wrote. But those workarounds are not obvious for all new users. I can reproduce it by trying to toggle the extra sources with my mouse, It seems to work every time with keyboard though, maybe that is the reason not to be able to reproduce? This is on several different systems, both on physical hardware and in virtualbox, ranging from 18.04 to 20.04 including all those in between. And this is not just for the Canonical Partners repository, but any repositories I have in a system. On some system with not much extra or even fresh installs of 19.04 and 19.10 I can not reproduce it every time on the first try, but closing software-properties-gtk down and starting it again seems to increase the chance of a failure by a lot. So please try closing and opening a few times if you can not reproduce the bug. I am not sure but I think that app indicators like psensor and indicator-cpufreq also increase the chance of failure to display the authorization window. If I try to toggle an apt source and do not fix it with one of the working functions, or by repeating the mouse clicks, but instead wait for the screenlock to come and then unlock it, I actually get an authorisation window in the upper left corner. It does take my password, but software-properties-gtk does not get notified by it then. Mint asks for authorising right away on starting their modified software-properties-gtk, so they do not get this problem. If the bug can not be found and fixed in time for 20.04, could we then get a "unlock" button on the "Other Software" tab? Once any of the other functions that requires authorization have been used, the toggles on the "Other Software" tab do work every time. The "Revert" button actually gets active after the authorisation for the toggles fails, and that reliably opens the authorisation window. So maybe it could start active but with the text "Unlock" and then changing to the text "Revert" after a successful authorisation. Then there would be an obvious way for users that do not know the workarounds to toggle software sources, and those that do not experience the bug will not see any functionality changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858500] Re: Upgrading from 19.04 to 19.10 will keep the 19.04 chromium-browser due to a higher version than the transitional deb in 19.10
This worked for me too after enabling eoan-proposed, I have now the snap on that installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858500 Title: Upgrading from 19.04 to 19.10 will keep the 19.04 chromium-browser due to a higher version than the transitional deb in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858500] [NEW] Upgrading from 19.04 to 19.10 will keep the 19.04 chromium-browser due to a higher version than the transitional deb in 19.10
Public bug reported: 19.04 has got a higher version chromium-browser now than the transitional deb package that install the snap version, so the 19.04 version will be kept when someone upgrades since 19.04 got a higher version, and then no further updates. apt show chromium-browser -a Package: chromium-browser Version: 79.0.3945.79-0ubuntu0.19.04.3 Status: install ok installed Priority: optional Section: web Maintainer: Ubuntu Developers Installed-Size: 225 MB Provides: chromium-browser-inspector, www-browser Pre-Depends: dpkg (>= 1.15.6) Depends: libasound2 (>= 1.0.16), libatk-bridge2.0-0 (>= 2.5.3), libatk1.0-0 (>= 2.2.0), libatspi2.0-0 (>= 2.9.90), libc6 (>= 2.29), libcairo2 (>= 1.6.0), libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.9.14), libexpat1 (>= 2.0.1), libgcc1 (>= 1:4.0), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), libgtk-3-0 (>= 3.9.10), libnspr4 (>= 2:4.9-2~), libnss3 (>= 2:3.22), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libstdc++6 (>= 7), libx11-6 (>= 2:1.4.99.1), libx11-xcb1, libxcb1 (>= 1.6), libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3 (>= 1:5.0), libxi6 (>= 2:1.2.99.4), libxrandr2 (>= 2:1.2.99.3), libxrender1, libxss1, libxtst6, bash (>= 4), xdg-utils, chromium-codecs-ffmpeg-extra (= 79.0.3945.79-0ubuntu0.19.04.3) | chromium-codecs-ffmpeg (= 79.0.3945.79-0ubuntu0.19.04.3) Recommends: chromium-browser-l10n Suggests: webaccounts-chromium-extension, unity-chromium-extension, adobe-flashplugin Conflicts: chromium-browser-inspector Replaces: chromium-browser-inspector Homepage: https://chromium.googlesource.com/chromium/src/ Download-Size: unknown APT-Manual-Installed: yes APT-Sources: /var/lib/dpkg/status Description: Chromium web browser, open-source version of Chrome An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. Package: chromium-browser Version: 77.0.3865.120-0ubuntu1.19.10.1 Priority: optional Section: universe/web Origin: Ubuntu Maintainer: Ubuntu Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 163 kB Provides: www-browser Pre-Depends: debconf, snapd Depends: debconf (>= 0.5) | debconf-2.0 Homepage: https://chromium.googlesource.com/chromium/src/ Download-Size: 48.7 kB APT-Sources: http://dk.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 Packages Description: Transitional package - chromium-browser -> chromium snap This is a transitional dummy package. It can safely be removed. . chromium-browser is now replaced by the chromium snap. Package: chromium-browser Version: 77.0.3865.120-0ubuntu1~snap1 Priority: optional Section: universe/web Origin: Ubuntu Maintainer: Ubuntu Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 163 kB Provides: www-browser Pre-Depends: debconf, snapd Depends: debconf (>= 0.5) | debconf-2.0 Homepage: https://chromium.googlesource.com/chromium/src/ Download-Size: 48.8 kB APT-Sources: http://dk.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages Description: Transitional package - chromium-browser -> chromium snap This is a transitional dummy package. It can safely be removed. . chromium-browser is now replaced by the chromium snap. snap list Name Version Rev Tracking Publisher Notes core 16-2.42.5 8268 stablecanonical✓ core core18201912121288 stablecanonical✓ base gnome-3-28-1804 3.28.0-16-g27c9498.27c9498 110 stable/… canonical✓ - gnome-calculator 3.34.1+git1.d34dc842544 stable/… canonical✓ - gnome-characters v3.32.1+git3.b9120df375 stable/… canonical✓ - gnome-logs3.34.0 81stable/… canonical✓ - gnome-system-monitor 3.32.1-3-g0ea89b4922123 stable/… canonical✓ - gtk-common-themes 0.1-25-gcc83164 1353 stable/… canonical✓ - lsb_release -rd Description:Ubuntu 19.10 Release:19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser 79.0.3945.79-0ubuntu0.19.04.3 [origin: unknown] ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 21:49:51 2020 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' Env: 'None' 'None' InstallationDate: Installed on 2019-12-23 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InstalledPlugins: Load-Avg-1min: 0.58 Load-Processes-Running-Percent: 0.2% Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Mach
[Bug 1852333] Re: 19.10 Grub install fail on Alienware Steammachine R2
*** This bug is a duplicate of bug 1851560 *** https://bugs.launchpad.net/bugs/1851560 I then installed grub manually: ubuntu@ubuntu:/$ sudo mount /dev/nvme0n1p3 /mnt ubuntu@ubuntu:/$ sudo mount --bind /dev /mnt/dev ubuntu@ubuntu:/$ sudo mount --bind /proc /mnt/proc ubuntu@ubuntu:/$ sudo mount --bind /sys /mnt/sys ubuntu@ubuntu:/$ sudo chroot /mnt root@ubuntu:/# sudo update-grub sudo: unable to resolve host ubuntu: Temporary failure in name resolution Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.3.0-19-generic Found initrd image: /boot/initrd.img-5.3.0-19-generic Found linux image: /boot/vmlinuz-5.3.0-18-generic Found initrd image: /boot/initrd.img-5.3.0-18-generic grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map. Found SteamOS 2.0 (2.0) on /dev/sda3 Adding boot menu entry for EFI firmware configuration done several minutes went before the line "grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map." appeared and the command finished. /dev/sdb1 is the usb stick with the installer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852333 Title: 19.10 Grub install fail on Alienware Steammachine R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1852333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851560] Re: Install 19.10 on Alieanware Steammachine R2
I got the same result with a fresh downloaded installer and reported #1852333 for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851560 Title: Install 19.10 on Alieanware Steammachine R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1851560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852333] [NEW] 19.10 Grub install fail on Alienware Steammachine R2
Public bug reported: I did a new install of 19.10 on an Alienware Steammachine R2 along SteamOS 2.0 and got a grub install error. The error message was Executing 'grub-install /dev/nvme0n1' failed. This is a fatal error. The installation was to a nvme where I had left around 140GB unused partition space, which the installer chose correctly when I chose install along side SteamOS. I started the installer directly from the grub menu. I then selected Normal Installation, Download updates and install third party software. This was with a fresh downloaded installer today, I reported a previously bug in 1851560 where I used the beta installer from September 26 and that time I started Ubuntu first without installing and started the installer from the desktop. With the same result. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 20:53:22 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed quiet splash --- LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.21 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852333 Title: 19.10 Grub install fail on Alienware Steammachine R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1852333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851560] Re: Install 19.10 on Alieanware Steammachine R2
Thank you for looking into this. The error came at the bootloader install part. I do not remember the exact wording and did not take a screenshot, but it was at least similar to what UbiquitySyslog.txt logged: Nov 6 19:57:37 ubuntu /plugininstall.py: "GrubInstaller failed with code %d" % ret) Nov 6 19:57:37 ubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller failed with code 1 I was able to install grub from a chroot and then boot and it is a working system. There where leftovers since the cleanup part was not run. I did find some installed packages named with ubiquity which I uninstalled. But looking at UbiquitySyslog.txt which start at September 26 I now realize that I used the beta installer from September 26. The September 26 part of that log is from another and successful install on a different system. Since I did not use this install much, I will download the released installer and remove the partitions created by this install and try again to see if it the new installer will install grub successfully. And report back here about how that goes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851560 Title: Install 19.10 on Alieanware Steammachine R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1851560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851560] [NEW] Install 19.10 on Alieanware Steammachine R2
Public bug reported: I attempted to install 19.10 on an Alienware Steammachine R2 along SteamOS 2.0 and got an error at the end. The installation was to a nvme where I had left around 140GB unused partition space, which the installer chose correctly. SteamOS is installed on a separate harddisk. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.12 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.419 Date: Wed Nov 6 20:57:44 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.12 ubuntu ** Attachment added: "partman" https://bugs.launchpad.net/bugs/1851560/+attachment/5303328/+files/partman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851560 Title: Install 19.10 on Alieanware Steammachine R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1851560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851560] Re: Install 19.10 on Alieanware Steammachine R2
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1851560/+attachment/5303337/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851560 Title: Install 19.10 on Alieanware Steammachine R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1851560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
