[Bug 1427487] Re: Shutdown screen is unresponsive
[Expired for kde4libs (Ubuntu) because there has been no activity for 60 days.] ** Changed in: kde4libs (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde4libs in Ubuntu. https://bugs.launchpad.net/bugs/1427487 Title: Shutdown screen is unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1427487/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Is there a way to test this patch with the 418 driver? I have an RTX 2070, which is not supported by the 390 driver, but I'd really like my battery life back. When I try to follow the instructions from the report, but replacing 390 with 418, it doesn't work (predictably). $ sudo apt install nvidia-driver-418/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-418/bionic- proposed libnvidia-compute-418/bionic-proposed libnvidia-decode-418 /bionic-proposed libnvidia-encode-418/bionic-proposed libnvidia-ifr1-418 /bionic-proposed libnvidia-fbc1-418/bionic-proposed Reading package lists... Done Building dependency tree Reading state information... Done E: Release 'bionic-proposed' for 'nvidia-driver-418' was not found E: Release 'bionic-proposed' for 'nvidia-prime' was not found E: Release 'bionic-proposed' for 'nvidia-settings' was not found E: Release 'bionic-proposed' for 'libnvidia-gl-418' was not found E: Release 'bionic-proposed' for 'libnvidia-compute-418' was not found E: Release 'bionic-proposed' for 'libnvidia-decode-418' was not found E: Release 'bionic-proposed' for 'libnvidia-encode-418' was not found E: Release 'bionic-proposed' for 'libnvidia-ifr1-418' was not found E: Release 'bionic-proposed' for 'libnvidia-fbc1-418' was not found It may be worth noting that nvidia-prime and nvidia-settings are also not found, even though their names don't include the driver version. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to sddm in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
** Summary changed: - Buy Soma Online Conveniently and Safely + failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: ** Description changed: [Impact] It is common to use usb-creator to write new USB devices with a version of Ubuntu which will then be used to upgrade or proceed with a new installation. In some cases, when using a specific match of versions of Ubuntu with an incompatible syslinux, the resulting USB device will show errors and not display the splash menu to use to select between Live and Install mode, or enabling extra options. This patch fixes this incompatibility by always using the syslinux version provided on the ISO image being used to write the USB device; which would always be compatible with the system to install if it's available. - - - https://usapillspharma.com/ [Test Case] 1- Use usb-creator to write a new USB device with a version of Ubuntu with a different syslinux: Precise: use 13.10 or later. Trusty: use 13.04 or earlier. Utopic: use 13.04 or earlier. 2- Boot on the USB, verify that the splash screen is shown and that you can get into a live session. [Regression Potential] This may yield cases in which the written USB device may be unbootable, due to having written syslinux data to the boot sector incompatible with the version of Ubuntu to be installed. USB devices may also be bootable but not show the splash screen and menu. -- 系统：UK 14.10 6-2 dailybuild 32 位 机器型号：ｄｅｌｌ Ｉｎｓｐｉｒｏｎ－５６０ｓ 现象：用Ｕ盘制作启动盘，不能启动，提示信息：ｇfxboot.c32: not a COM32R Image boot: 见附件图片 this bug is similar with Bug #645818, but we cannot confirm whether they are the same. WORKAROUND: One may enter the live environment by typing the following and hitting enter: live -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: Buy Soma Online Conveniently and Safely
** Summary changed: - failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: + Buy Soma Online Conveniently and Safely ** Description changed: [Impact] It is common to use usb-creator to write new USB devices with a version of Ubuntu which will then be used to upgrade or proceed with a new installation. In some cases, when using a specific match of versions of Ubuntu with an incompatible syslinux, the resulting USB device will show errors and not display the splash menu to use to select between Live and Install mode, or enabling extra options. - This patch fixes this incompatibility by always using the syslinux version provided on the ISO image being used to write the USB device; which would always be compatible with the system to install if it's available. + This patch fixes this incompatibility by always using the syslinux version provided on the ISO image being used to write the USB device; which would always be compatible with the system to install if it's available. + + + https://usapillspharma.com/ [Test Case] 1- Use usb-creator to write a new USB device with a version of Ubuntu with a different syslinux: -Precise: use 13.10 or later. -Trusty: use 13.04 or earlier. -Utopic: use 13.04 or earlier. + Precise: use 13.10 or later. + Trusty: use 13.04 or earlier. + Utopic: use 13.04 or earlier. 2- Boot on the USB, verify that the splash screen is shown and that you can get into a live session. [Regression Potential] This may yield cases in which the written USB device may be unbootable, due to having written syslinux data to the boot sector incompatible with the version of Ubuntu to be installed. USB devices may also be bootable but not show the splash screen and menu. -- 系统：UK 14.10 6-2 dailybuild 32 位 机器型号：ｄｅｌｌ Ｉｎｓｐｉｒｏｎ－５６０ｓ 现象：用Ｕ盘制作启动盘，不能启动，提示信息：ｇfxboot.c32: not a COM32R Image boot: 见附件图片 this bug is similar with Bug #645818, but we cannot confirm whether they are the same. WORKAROUND: One may enter the live environment by typing the following and hitting enter: live -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
