[Touch-packages] [Bug 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?
I upgraded from 17.04 to this, and can't get to a desktop now. Really regretting using ubuntu, yet again. This is a dell xps 15 9550, I finally had to try an upgrade due to various weird issues with 17.04 still, but at least it worked vs. now. Might try nouveau as recommended. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1765923 Title: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug? Status in apt package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in sddm package in Ubuntu: Confirmed Bug description: Using the April 19th daily build of Kubuntu 18.04 I installed the Nvidia drivers via the following command. sudo ubuntu-drivers autoinstall The install process proceeds fine and after a logout process I get a black screen. I tried this on the April 17th daily build of bionic and a reboot also results in a black screen. The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE After I installed latest Nvidia driver-390 and tried to boot after shutting down once I faced a black screen problem. since, I'm a noob but something related to nvidia drivers couldn't be started. Then I followed https://askubuntu.com/a/968692/802490 While following these instructions re-installing of nvidia drivers failed. The only things that worked is purging the drivers and changing "WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install nvidia drivers again but I'm afraid that this will lead to that problem again. Can anyone help in re-installing the driver such that I won't face that problem? END QUOTE THE WORK AROUND Use Ctrl-Alt-f6 to get to a login prompt. Login run "startx" The x server will start and Nvidia drivers will function. THE PROBLEM When I try to run SDDM I get an error (Which I will try to copy down to add to this bug when I am on a different computer than the one I am reporting the bug about.). Installing lightDM does not work... it installs but is either will not run or will not actually start a x session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551122] Re: Crash on screen power save
I'm currently on 5.5.1+dfsg-16ubuntu7, which should be newer and include these, no? I found this digging into why xenial's kde5 plasma shell and all kde apps keep freaking when my 4k displays go away. Like others, I use big 4k tv's (3x of them) that give no signal when they power down, so the displays go away entirely with variable results. Harassing the kwin guys led me here as deeper qt bugs, but still seems present as of stated version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1551122 Title: Crash on screen power save Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: Continuation to bug #1548766 to consider another upstream fix from https://codereview.qt-project.org/#/c/138681/ The fix could affect both monitor power saving or attaching/detaching cycles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1551122/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1238194] Re: keyboard doesn't work to enter password with encrypted partitions ubuntu 13.10 saucy
I recently upgraded my trusty kernel from 3.16 to 3.19, and got hit with this bug with a logitech wireless keyboard. Seems all the kernel builds are omitting critical hid drivers in the initrd, yet again. Add in the fact my current mobo bios just simply wouldn't let grub catch my shift to break the boot menu to single mode. Very ugly, very not happy day. Since I've gone to 4.4 kernel, and see the same issue with it, so it seems persistent and unfixed still at least on trusty repos. With 4.4, at least wired keyboard works, so I've been just keeping a second one around until I got to hunt for this more. The recovery is obviously not pretty, and this has happened a few times I remember, as I've used luks since ~2008. It would be extremely nice if upstream or at least the vendor packagers run regression tests for this LUKS use case in particular formulated to avoid stranding people at their disk unlock menus and figuring out how to make a boot disk without the system they were just using. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1238194 Title: keyboard doesn't work to enter password with encrypted partitions ubuntu 13.10 saucy Status in initramfs-tools: New Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Precise: Fix Released Status in initramfs-tools source package in Saucy: Fix Released Bug description: [Justification] With the kernel in 13.10, some systems use a different USB host driver than previously. Failing to include this driver in the initramfs causes regressions for users who need to interact with the system in early boot using a USB keyboard, such as users with an encrypted root filesystem. Such systems are not bootable with this host driver missing. [Test case] 1. On an affected system, reboot to a kernel from 13.04. 2. Install the initramfs-tools package from -proposed. 3. Reboot to the kernel from 13.10. 4. Verify that you are able to type your passphrase at the prompt in the initramfs. [Regression potential] Minimal. The update-initramfs script will ignore missing modules (such as the many other modules in the list which are built-ins), and the only change made is to copy the module into the initramfs: it will only be loaded in the initramfs if udev determines it's needed, just as it would load it after switching to the root filesystem. Is the same problem as here but in the new ubuntu 13.10 saucy https://bugs.launchpad.net/bugs/1066376 I just can't use (i can install) a encrypted partition because when is time to introduce the password to unlock partition keyboard is not working. I don't know how to edit a bug to report it afects other version of ubuntu so i created this new bug... To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1238194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
