| Peppep | Hi. I installed the latest development build with kernel 5.0.0.7, and am unable to login. After about a second after entering the password, I'm back at login | 12:58 |
|---|---|---|
| Peppep | Currently in tty3 to get weechat running, can anyone give any troubleshooting tips? | 12:59 |
| BluesKaj | try nomodeset | 12:59 |
| BluesKaj | !nomodeset | 12:59 |
| ubottu | A common kernel (boot)parameter is nomodeset, which is needed for some graphic cards that otherwise boot into a black screen or show corrupted splash screen. See http://ubuntuforums.org/showthread.php?t=1613132 on how to use this parameter | 12:59 |
| Peppep | Hmm, okay. I've actually used nomodeset before, but then I didn't get passed Grub, and I was under the impression that the Nvidia drivers would be carried over to the new install. Thanks! | 13:01 |
| Peppep | I tried nomodeset and nouveau.modeset=0, but I still couldn't log in | 13:12 |
| Peppep | And updating from nvidia-390 to nvidia-410 did not help. Are there any logs I could check to get some indication about the culprit? | 13:19 |
| BluesKaj | Peppep, /var/log/syslog | 13:39 |
| Peppep | gsd-keyboard fatal io error 11, gsd-media-keys fatal io error 11 etc | 13:51 |
| Peppep | Unrecoverable failture in required component org.gnome.Shell.desktop. I know it's not much, and I'm trying to search other places, but I included a few of the errors here in case they are common and fixable | 13:55 |
| BluesKaj | Peppep, did you update and upgrade while in the VT/TTY? | 14:03 |
| Peppep | BluesKaj: The nvidia driver? Yes. Is that something I shouldn't do? :/ | 14:09 |
| Peppep | But it doesn't seem to be running. When I do lshw c -video, the driver seems to be the Intel one for the integrated GPU (on Dell XPS 9560), not the Nvidia card | 14:11 |
| Peppep | running/loaded* | 14:11 |
| BluesKaj | Peppep, I sudo apt update && sudo apt upgrade ..all packages | 14:13 |
| BluesKaj | meant | 14:13 |
| Peppep | Oh, yeah, I did that as well. There wasn't anything to upgrade | 14:13 |
| BluesKaj | bummer | 14:13 |
| BluesKaj | definitely a hardware problem alright, dunno if the 410 nvidia driver is the corect one for your gpu if the 390 was the recommended driver in ubuntu-drivers... try, sudo ubuntu-drivers list | 14:17 |
| Peppep | 390 was the recommended one for 18.10 I believe, when I ran "ubuntu-drivers devices" 410 was recommended | 14:18 |
| Peppep | On 19.04 | 14:18 |
| Peppep | BluesKaj: Any other ideas? I'm close to reinstalling 18.10 now. :/ | 14:53 |
| BluesKaj | did some googling, but couldn't find anything applicable Peppep ...maybe 18.10 will work for you, altho it's more buggy than 18.04LTS | 14:55 |
| Peppep | The only theory I have is that some of the customizations I did to GNOME on 18.10 is incompatible with 19.04. But I don't know if it could cause fatal errors like this | 14:57 |
| Peppep | Since a lot of the syslog messages are related to GNOME | 14:57 |
| BluesKaj | which gnome customizations, like tweak or themes or? | 14:58 |
| Peppep | Mostly dash to dock, alttab changes etc. And I updated dash to dock from v17 to v19 because they added GNOME 3.32 support, so that shouldn't be it. But I had like 5-6 extensions | 15:00 |
| BluesKaj | not a gnome user so that's not my strong suit | 15:01 |
| Peppep | Tried deleting .gnome and .config/dconf/user in case it's related to the manual config. Fingers crossed. Thanks for the patience in any case | 15:09 |
| * BluesKaj crosses fingers | 15:12 | |
| Peppep | Re 18.04 vs 18.10... I upgraded from 18.10 which was stable for me. I had to do nomodeset and a few other fixes initially, and I had to restart the network-manager service a few times, but overall I was happy | 15:12 |
| BluesKaj | ok | 15:12 |
| Peppep | But yeah, I could give 18.04LTS a shot in case it works perfectly out of the box | 15:12 |
| Peppep | Since it seems that I have to do a reinstall | 15:12 |
| BluesKaj | it's more mature and it receives more devel attention | 15:13 |
| Peppep | Yeah. Unfortunately I tend to run latest/beta versions of everything which sometimes causes hours and hours of troubleshooting like today :p | 15:14 |
| Peppep | Android Beta, Chrome Dev, Ubuntu 19.04 etc etc. And I'm not developing for any of those platforms, so I don't really have a good reason, other than wanting to have the newest stuff all the time | 15:15 |
| BluesKaj | well, if you like more edge then by all means Peppep | 15:15 |
| Peppep | In general, I do. But I'll use 18.04 until 19.04's official release. Then I'll do a live-boot before giving it another shot ;) | 15:17 |
| Peppep | Anyway, thanks again! | 15:18 |
| Peppep | BluesKaj++ | 15:18 |
| Peppep | Hmm. Isn't there a karma system here? Crap | 15:19 |
| BluesKaj | hehe | 15:19 |
| Peppep | ;) | 15:20 |
| Peppep | loooooool | 15:21 |
| Peppep | After giving up | 15:21 |
| Peppep | Doing the final reboot | 15:21 |
| Peppep | It worked | 15:21 |
| Peppep | I'm officially on 19.04 | 15:22 |
| BluesKaj | coolness! | 15:23 |
| tomreyn | being offficially on 19.04 is unlikely at this date, unless you can time travel | 15:23 |
| tomreyn | (but i'm glad you succeeded in fixing this issue) | 15:24 |
| Peppep | I'm not on official 19.04, I'm officially on (a) 19.04 (build) | 15:31 |
| Peppep | ;) | 15:31 |
| tomreyn | cool :) just making sure you're aware | 15:31 |
| Peppep | Oh, I'm way too aware, just spent hours troubleshooting since there's basically no possibilities of finding anyone else with similar issues at this stage. | 15:35 |
| Peppep | And for future reference, it was either the Intel driver (since I re-enabled my Nvidia card) or GNOME customizations from 18.10. Will disable to nvidia card again now to further narrow it down | 15:37 |
| tomreyn | gnome shell extensions are a good way to break gnome(-shell). generally, also on supported releases, use them at your own risk. | 15:39 |
| tomreyn | and surely disable them before anything else if there are any issues. | 15:39 |
| Peppep | Ah. I expected that they could cause issues, but not as fatally as this (stuck on login-screen) | 15:40 |
| Peppep | Was planning on disabling them before upgrading, but forgot about it, lol | 15:40 |
| Peppep | So my fingerprint reader is recognized in lsusb now (Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. VFS7552 Touch Fingerprint Sensor) | 15:54 |
| Peppep | And I've enabled fingerprint auth in sudo pam-auth-update. But it still doesn't show up under Users. :/ | 15:55 |
| OerHeks | according to https://launchpad.net/~fingerprint/+archive/ubuntu/fingerprint-gui and https://fprint.freedesktop.org/supported-devices.html, your "138a:0091 " is not there | 16:00 |
| Peppep | Ah :/ | 16:10 |
| tomreyn | also https://www.dell.com/community/Linux-Developer-Systems/XPS-13-Fingerprint-reader-Linux-support/td-p/5090723 | 16:12 |
| tomreyn | but then, fingerprint readers are not a safe authentication mechanism anyways. ;-) | 16:13 |
| OerHeks | a token or jubikey is my best access | 16:14 |
| OerHeks | or choose a password larger than 16 characters.. most rainbowtables stop there | 16:15 |
| BluesKaj | I didn't bother with fingerprint authentication on the Dell laptop | 16:20 |
| BluesKaj | my fingertips are almost calloused anyway ... drumsticks will do that | 16:22 |
| Peppep | Sometimes convenience wins over security unfortunately. But I'm getting there, step by step. Voluntarily by going from Windows to Linux, involuntarily by not being able to use fingerprints | 16:24 |
| Peppep | As of now, fp auth is pretty much the only thing Win10 wins on. Otherwise Ubuntu has better battery life, faster boot (and especially resume from sleep) ++ | 16:26 |
| tomreyn | https://github.com/hmaarrfk/Validity91 is probably your best bet | 16:27 |
| tomreyn | 112x112 pixels, i wonder how brute forceable that is. | 16:29 |
| OerHeks | and unencrypted .. | 16:29 |
| Peppep | Is 112x112 a hardware limitation or just what they've been able to get so far? If the former, I agree, that's way more insecure than I was aware of | 16:37 |
| OerHeks | 180 x 256 pixels is more regular, mind that it should be encrypted before sending too | 16:41 |
| Peppep | BluesKaj tomreyn: It was the GNOME settings. I disabled the Nvidia card and the Intel drivers runs without issues | 16:56 |
| BluesKaj | Peppep, good stuff! | 16:57 |
| Peppep | The power consumption in 19.04 is even lower than in 18.10. Discharge rate at 3.9W-4.9W running weechat and powertop | 17:04 |
| Peppep | And wifi performence seems to be improved. Happy camper so far. | 17:08 |
| Peppep | Anyway, gtg, thanks guys! | 17:08 |
| Joe_from_next_do | Hello is the option for minimal installs still available in 1904? I didn't see it in my VM. | 17:40 |
| OerHeks | not in tasksel, only in ubiquity | 17:45 |
| Joe_from_next_do | Oh yes sorry I forgot to copy that. I'll go try it out again.. | 17:48 |
| erle- | <Peppep> The power consumption in 19.04 is even lower than in 18.10. Discharge rate at 3.9W-4.9W running weechat and powertop | 18:44 |
| erle- | nice | 18:44 |
| erle- | maybe that is also because of Gnome Shell efficiency | 18:44 |
| erle- | Is there a way to reboot everything except the kernel? | 18:45 |
| erle- | Important would be not to unmount /any/ file systems | 18:45 |
| erle- | to be more precise: boot live CD, do apt dist-upgrade and then reload everything (except kernel) so that the state if the live session stay intact (installed packets, settings in /home/ubuntu etc.) | 18:46 |
| erle- | Why was gnome-books not in Ubuntu before? | 18:52 |
| erle- | finally a reader that enables one to read epub without eyes hurting | 18:52 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!