Feeds:
Posts
Comments

Archive for the ‘Booting/Login/GRUB’ Category

If you’ve upgraded your Ubuntu system only to find you don’t have permission to do pretty much anything, as I did after upgrading to 13.10, it can be pretty annoying even for an advanced user, and downright scary for a novice. The symptoms are pretty obvious, as when you go to install updates, all you get is an error message saying “This operation cannot continue since proper authorization was not provided“. And using the Shutdown button seems to do nothing, and even using a terminal command to power off might see the shutdown process halt half-way through, forcing you to use the PC’s power button.

On top of that, even mounting removable drives (or other partitions on your internal drive) ends in being told you can’t, and even trying to play a DVD ends with “Unable to access “DVDVIDEO”. Not authorized to perform operation.

While there are ways around all of these situations for more advanced users, those less experienced with Ubuntu/Linux would find it all quite daunting, and pretty much look at their system as unusable. And one shouldn’t have to go through the bother of manually mounting drives through the terminal, or invoking the Software Updater as superuser, or any other thing we usually take for granted.

Luckily, the fix – which involves PAM (Pluggable Authentication Modules) – is actually quite simple, and should have everything back to normal in no time.

In a terminal, enter the following command to edit the PAM authentication file for the LightDM display manager:

gksu gedit /etc/pam.d/lightdm

Under the first line “#%PAM-1.0” paste the following 2 lines:

session required pam_loginuid.so
session required pam_systemd.so

Save and exit the file, then log out and back in again, and all should now be fine (you shouldn’t need to reboot).

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Another method, which fixed the problem for some (but not in my case, and many others) is to run:

sudo pam-auth-update --force

This opens PAM‘s config within the terminal, at which you either check or uncheck items, or just hit Tab to go to OK, and hit Enter.

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

If need be, like you have GDM installed and it is interfering with LightDM, run dpkg-reconfigure gdm and select lightdm (you may need to reboot).

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Did this information make your day? Did it rescue you from hours of headache? Then please consider making a donation via PayPal, to buy me a donut, beer, or some fish’n’chips for my time and effort! Many thanks!

Buy Ubuntu Genius a Beer to say Thanks!

Advertisements

Read Full Post »

Ubuntu is pretty awesome when it comes to automounting your drives and USB devices; in my experience, it is miles ahead of Windows, and it keeps getting better with each release. But for a greater level of control, you can’t beat the old-fashioned way: mounting your drives via fstab at boot.

While Ubuntu now mounts drives and partitions in folders with names based on the labels, which includes spaces in the names, fstab is a tad more touchy when it comes to this. If you try mounting a drive in fstab to a mount-point with a path name like /media/Windows XP, the mounting will fail because of the space. Usual methods to get around this, like close the path off with / (ie: /media/Windows XP/) or put it in quotes (ie: ‘/media/Windows XP’ or “/media/Windows XP”), will fail – but there is a solution other than replacing spaces with hypens or underscores.

Simply replace any spaces with \040, so your line in fstab should look something like:

UUID=1D666EVIL6661D /media/Windows\040XP

The drive will mount in the appropriate folder from then onwards (ie: /media/Windows XP), and there’s no need to reboot if you’re urgently trying to access a drive – simply open a terminal and run sudo mount -a to mount all devices in fstab.

°ºÒθÓº°¤°ºÒθÓº°¤°ºÒθÓº°

Just in case you are unfamiliar with fstab, the way you edit it is sudo gedit /etc/fstab. However, if you needed that bit of info, chances are you really shouldn’t be doing so, unless you’ve first read a little of the abundant info available out there on the subject of fstab and mounting drives in Ubuntu (and other Linux distros). The last thing you would want to do is render your system unbootable because you made an error in editing fstab. While this guide is just for how to deal with spaces in paths, still exercise caution if this is all new to you.

°ºÒθÓº°¤°ºÒθÓº°¤°ºÒθÓº°

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Did this information make your day? Did it rescue you from hours of headache? Then please consider making a donation via PayPal, to buy me a donut, beer, or some fish’n’chips for my time and effort! Many thanks!

Buy Ubuntu Genius a Beer to say Thanks!

Read Full Post »

Older Posts »