15.10: After some update (?), GUI asks for password but accepts none

[Al_Savage]

I am not certain of the chronology, as I did not look at this running computer for about three weeks. I think I authorized some software updates and the next boot, I had a GUI login I had never seen before. OK, these things happen: I typed my usual password, but after the screen blinked heavily, I was presented the same screen:

266396

I used the grub boot loader to boot to Recovery mode, remounted / as rw, and reset the password on that account:

266395

After rebooting again, same situation: typing the known-good password results in the login screen being re-presented.

The kernel is .31

Thoughts?

[Bashing-om]

Al_Savage; Hello; Welcome to the forum:

Yeah a thought from:


I authorized some software updates

a broken graphic's driver ?

What does the log file " /var/log/Xorg.0.log " relate about this condition ?



it could be

[Al_Savage]

/var/log/Xorg.0.log is zipped & attached. I am not qualified to say what is abnormal in it.

[Bashing-om]

Al_Savage; Well ...

I do not have a means in this - my work install - to extract the zip file .
Maybe use our pastebin site to post the file ?


sudo apt-get install pastebinit
cat /var/log/Xorg.0.log | pastebinit

The result is a URL back in terminal. Pass that link back here to the thread .



more than one way

[Al_Savage]

I am out of time tonight. That box is not currently internet-connected, and walking to/from it with a flash drive I cannot do tonight. I will try to post tomorrow after work (yes, I work Sundays).

[Al_Savage]

http://paste.ubuntu.com/14237764/

[Bashing-om]

Al_Savage; Hey ...

You do good, not so with your system.

But, I am not too sure of what I know .
Seems your system is encrypted:


Kernel command line: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
and I have no experience in this realm.

What we do know from the log file:


44.198] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[ 44.198] (EE) NVIDIA: system's kernel log for additional error messages and
[ 44.198] (EE) NVIDIA: consult the NVIDIA README for details.
[ 44.198] (EE) [drm] KMS not enabled

bk

44.991] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)


From the F1 console ( directories have been UNencrypted, yes ??)
Let's try and (RE-)install the driver.
Run terminal commands:


sudo apt-get --purge remove nvidia*
sudo rm /etc/X11/xorg.conf
sudo apt-get install nvidia-340
sudo nvidia xconfig


Reboot the machine, can you now boot to the GUI ?




maybe YES

[Al_Savage]

I haven't rebooted yet, because . . .


sudo apt-get --purge remove nvidia* OK


sudo rm /etc/X11/xorg.conf file not found


sudo apt-get install nvidia-340 OK


sudo nvidia xconfig
nvidia not found

Before I reboot, can you verify that those two missing files should be missing?

[Bashing-om]

Al_Savage; Yeah ...

Should be good .
With the advent of DKMS - Dynamic Kernel Mode Setting in many instances the use of the driver config file is no longer required.
The kernel does all the heavy lifting now.
I am aware on several instances that the file does not exist any longer.

Try and see what results.
Reboot and




see, it workie

[Al_Savage]

Rebooted to GUI: same as before: the correct password is not accepted.

[Bashing-om]

Al_Savage; Yuk ...

I was aware of that possibility, I could hope otherwise.

I bet we are looking at this situation :


44.196] (WW) Unresolved symbol: fbGetGCPrivateKey

Where the directory is not unlocked due to encryption ??
As I advised, I know nothing in this layer. Others who have the knowledge and experience here will have to advise.



in this instance



i just do not know

[Al_Savage]

What I find odd is that I don't recall setting up disk encryption; I am fairly new with Ubuntu and in most cases let the installer have its way. The system was lightly used for a few months, then one day: can't log in. Odd.

[MAFoElffen]

OP: Please backup... First you should show what hardware you "have"...


sudo lshw -n -c video
usdo lspci -l | grep -i VGA

Because his logs say that normal nvidia and Nouveau shpuld work, but they don't... which could be a few things.

Nouveau drivers work up to GTX400, so anything newer, it will fail. Nvdvia vers340 works up through nVidia Geforce GTX 700 series cards... so if newer, then both those drivers will fail... and the Op will havew to use the Edger's PPA and nvidia Update type driver. Either that or the vendor's binary driver.

[Al_Savage]

Changed:

sudo lshw -n -c video
to
sudo lshw -numeric -c video


*-display UNCLAIMED
description: VGA compatible controller
product: GT200GL [Quadro FX 4800] [10DE:5FE]
vendor: NVIDIA Corporation [10DE]
physical id: 0
bus info: pci@0000:03:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller cap_list
configuration: latency=0
resources: memory:f6000000-f6ffffff memory:e0000000-efffffff memory:f4000000-f5ffffff ioport:dc80(size=128) memory:f7e00000-f7e7ffff

Changed:

usdo lspci -l | grep -i VGA
(unknown option -l)
to
sudo lspci | grep -i VGA


03:00.0 VGA compatible controller: NVIDIA Corporation GT200GL [Quadro FX 4800] (rev a1)

[Bashing-om]

Al_Savage; Well ...

What we now know, no driver is loaded and that for the " Quadro FX 4800 " graphic's card that Nvidia recommends the 340 driver.
What we do not know is what is preventing building the 340 driver .

Again; this says you have some level of encryption:


Kernel command line: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash

AND this says to me that there is a problem:


44.196] (WW) Unresolved symbol: fbGetGCPrivateKey


And I am stuck because I am not familiar with the means to access encrypted volumes, nor how to verify the " fbGetGCPrivateKey " .
It is MAFoElffen to our rescue.



knowledge is a good thing

[MAFoElffen]

Al_Savage; Well ...

What we now know, no driver is loaded and that for the " Quadro FX 4800 " graphic's card that Nvidia recommends the 340 driver.
What we do not know is what is preventing building the 340 driver .

Again; this says you have some level of encryption:

AND this says to me that there is a problem:


And I am stuck because I am not familiar with the means to access encrypted volumes, nor how to verify the " fbGetGCPrivateKey " .
It is MAFoElffen to our rescue.

knowledge is a good thing



NO, we can both help ... That is what I recommend. We work together on this.


Kernel command line: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash

..Implies that it is just an LVM. That is the default VG (Volume Group) name for the root when you install LVM in the LiveCD installer (in partman). The other default VG (if he checks with fdiask -l) would be ubuntu--vg--swap.

Another thing to try is to uninstall nvidia drivers, temp add "nomodeset" as a boot option, then let Additional Drivers adds what it determines as recommended... It may be the other way around, where his card is too old to run except on legacy... although neouveau should work with that out of the box... (strange).

[Bashing-om]

MAFoElffen; K ..

Always willing to learn, just do not want to lead anyone down a garden path leading to a high cliff !
We have purged and attempted a re-install .. with negative results.

How bout this for a thought, as we have LVM, and presently in making up the volume groups, /boot is created very small. Maybe what we have here is a out-of space condition such that linux-generic can not work to build the Nvidia module ??

@ Al_Savage; Given this thought ^ ;
What returns for :


df -h
df -i
and we verify disk space usage.
Is linux-generic even installed ?


dpkg -l | grep linux-


cause, I say again -> there has to be a reason .

[Al_Savage]

I'm pretty sure I was using the nouveau driver before I began having this problem.


df -h

Filesystem Size Used Avail Use% Mounted on
udev 63G 0 63G 0% /dev
tmpfs 13G 9.4M 13G 1% /run
/dev/dm-0 870G 271G 555G 33% /
tmpfs 63G 0 63G 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 63G 0 63G 0% /sys/fs/cgroup
/dev/sde1 236M 51M 173M 23% /boot
/dev/sdf1 7.3G 84K 7.3G 1% /media/usb
df -i

Filesystem Inodes IUsed IFree IUse% Mounted on
udev 16499204 575 16498629 1% /dev
tmpfs 16503333 756 16502577 1% /run
/dev/dm-0 57892864 199696 57693168 1% /
tmpfs 16503333 1 16503332 1% /dev/shm
tmpfs 16503333 3 16503330 1% /run/lock
tmpfs 16503333 15 16503318 1% /sys/fs/cgroup
/dev/sde1 62248 302 61946 1% /boot
/dev/sdf1 0 0 0 - /media/usb
dpkg -l | grep linux-

ii linux-firmware 1.149.3 all Firmware for Linux kernel drivers
rc linux-image-3.19.0-30-generic 3.19.0-30.34 amd64 Linux kernel image for version 3.19.0 on 64 bit x86 SMP
ii linux-image-3.19.0-31-generic 3.19.0-31.36 amd64 Linux kernel image for version 3.19.0 on 64 bit x86 SMP
rc linux-image-extra-3.19.0-30-generic 3.19.0-30.34 amd64 Linux kernel extra modules for version 3.19.0 on 64 bit x86 SMP
ii linux-image-extra-3.19.0-31-generic 3.19.0-31.36 amd64 Linux kernel extra modules for version 3.19.0 on 64 bit x86 SMP
ii linux-libc-dev:amd64 4.2.0-22.27 amd64 Linux Kernel Headers for development
ii linux-sound-base 1.0.25+dfsg-0ubuntu5 all base package for ALSA and OSS sound systems
ii syslinux-common 3:6.03+dfsg-8ubuntu2 all collection of bootloaders (common)
ii syslinux-legacy 2:3.63+dfsg-2ubuntu8 amd64 Bootloader for Linux/i386 using MS-DOS floppies

[Bashing-om]

Al_Savage; Well ...

It ain't a space constraint problem, and linux-generic is installed.
But you have an old kernel.
Current is :


Version 3.19.0.42.41 (vivid)

Is there a reason you have not updated ?


while I continue to scratch my head

[bapoumba]

Another reason may be .Xauthority is not owned by your user :

ls -l .Xauthority

[Al_Savage]

root@Winni3: ls -l .Xauthority
[ . . . ]No such file or directory

Just prior to running "dpkg -l | grep linux-" above, I had run:

apt-get update
apt-get upgrade

Is there something else I should be doing to update the kernel?

[Vladlenin5000]

Is there something else I should be doing to update the kernel?

Yes: sudo apt-get dist-upgrade

[Al_Savage]

That's got it!

Previously:

dpkg -l | grep linux-

ii linux-firmware 1.149.3 all Firmware for Linux kernel drivers
rc linux-image-3.19.0-30-generic 3.19.0-30.34 amd64 Linux kernel image for version 3.19.0 on 64 bit x86 SMP
ii linux-image-3.19.0-31-generic 3.19.0-31.36 amd64 Linux kernel image for version 3.19.0 on 64 bit x86 SMP
rc linux-image-extra-3.19.0-30-generic 3.19.0-30.34 amd64 Linux kernel extra modules for version 3.19.0 on 64 bit x86 SMP
ii linux-image-extra-3.19.0-31-generic 3.19.0-31.36 amd64 Linux kernel extra modules for version 3.19.0 on 64 bit x86 SMP
ii linux-libc-dev:amd64 4.2.0-22.27 amd64 Linux Kernel Headers for development
ii linux-sound-base 1.0.25+dfsg-0ubuntu5 all base package for ALSA and OSS sound systems
ii syslinux-common 3:6.03+dfsg-8ubuntu2 all collection of bootloaders (common)
ii syslinux-legacy 2:3.63+dfsg-2ubuntu8 amd64 Bootloader for Linux/i386 using MS-DOS floppies

I then ran:
apt-get install linux-generic
Now:

dpkg -l | grep linux-

ii linux-firmware 1.149.3 all Firmware for Linux kernel drivers
ii linux-generic 4.2.0.22.24 amd64 Complete Generic Linux kernel and headers
ii linux-headers-4.2.0-22 4.2.0-22.27 all Header files related to Linux kernel version 4.2.0
ii linux-headers-4.2.0-22-generic 4.2.0-22.27 amd64 Linux kernel headers for version 4.2.0 on 64 bit x86 SMP
ii linux-headers-generic 4.2.0.22.24 amd64 Generic Linux kernel headers
rc linux-image-3.19.0-30-generic 3.19.0-30.34 amd64 Linux kernel image for version 3.19.0 on 64 bit x86 SMP
ii linux-image-3.19.0-31-generic 3.19.0-31.36 amd64 Linux kernel image for version 3.19.0 on 64 bit x86 SMP
ii linux-image-4.2.0-22-generic 4.2.0-22.27 amd64 Linux kernel image for version 4.2.0 on 64 bit x86 SMP
rc linux-image-extra-3.19.0-30-generic 3.19.0-30.34 amd64 Linux kernel extra modules for version 3.19.0 on 64 bit x86 SMP
ii linux-image-extra-3.19.0-31-generic 3.19.0-31.36 amd64 Linux kernel extra modules for version 3.19.0 on 64 bit x86 SMP
ii linux-image-extra-4.2.0-22-generic 4.2.0-22.27 amd64 Linux kernel extra modules for version 4.2.0 on 64 bit x86 SMP
ii linux-image-generic 4.2.0.22.24 amd64 Generic Linux kernel image
ii linux-libc-dev:amd64 4.2.0-22.27 amd64 Linux Kernel Headers for development
ii linux-sound-base 1.0.25+dfsg-0ubuntu5 all base package for ALSA and OSS sound systems
ii syslinux-common 3:6.03+dfsg-8ubuntu2 all collection of bootloaders (common)
ii syslinux-legacy 2:3.63+dfsg-2ubuntu8 amd64 Bootloader for Linux/i386 using MS-DOS floppies

And the system boots correctly to the GUI, without prompting for a password (my original, correct behaviour).

And, now:
al@Winni3:~$ ls -l .Xauthority
-rw------- 1 al al 51 Dec 28 13:20 .Xauthority


Now, how do I get the kernel to this:
Version 3.19.0.42.41 (vivid)

[Al_Savage]

al@Winni3:~$ sudo apt-get dist-upgrade
[sudo] password for al:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

[Bashing-om]

Al_Savage; heh hey !

You have the kernel of wily now installed. " Version 4.2.0.22.24 (wily) " ; an even later version than that of vivid.
If all is now good -- hey fine good and dandy .

If at a stopping point, reboot and show what the booting kernel is now:


uname -r



who wudda thunk it



who wudda thunk it

[Al_Savage]

al@Winni3:~$ uname -r
4.2.0-22-generic

[Bashing-om]

Al_Savage; :)

All is happy in whoville now .



all's well that ends well