Precise known bugs with workarounds

**Cavsfan** · September 26th, 2012

I am not sure if this has been mentioned before but, when in gnome classic I looked up at the date/time all I seen was the time.
No date was displayed.

I found a way to fix that here.

BTW, Precise whether in Unity or Gnome Classic is really working well as you would expect from an LTS.

**Freecore** · November 12th, 2012

I've recopiled the temporary solutions to the Bug 796076.

When you run "gksudo gedit /path/of/file" gedit tries to open an untitled document and keeps loading it.

The recopilation can be found on comment #25.

http://bugs.launchpad.net/gedit/+bug/796076

**Linuxisfast** · November 12th, 2012

Originally Posted by Freecore

I've recopiled the temporary solutions to the Bug 796076.

When you run "gksudo gedit /path/of/file" gedit tries to open an untitled document and keeps loading it.

The recopilation can be found on comment #25.

http://bugs.launchpad.net/gedit/+bug/796076

Yep confirmed this bug as well on launchpad, I get the same with Ubuntu Quantal x64.

**fballem** · November 12th, 2012

Originally Posted by whatthefunk

Crap Nvidia driver included on .iso. Solution is to remove any proprietary drivers and then revert to old Nvidia driver.

Code:

sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
 sudo apt-get update
 sudo apt-get install nvidia-current=295.33-0ubuntu1~precise~xup1

Reboot and you should be good to go.

This actually can be a larger problem, since on some nVidia cards, the driver simply won't work and ubuntu 12.04 will not boot. If this applies to you, then you will need to do a special installation process, which is described here: https://wiki.ubuntu.com/fballem/Soft...4#Installation

**Paddy Landau** · November 12th, 2012

Originally Posted by Freecore

When you run "gksudo gedit /path/of/file" gedit tries to open an untitled document and keeps loading it.

Thanks to Freecore, my original post giving a workaround is now redundant. Freecore found out that there is a much simpler way; just use gksudo twice, as follows.

Code:

gksudo gksudo gedit <file>

It works perfectly!

**Cavsfan** · January 20th, 2013

A couple of days ago I installed gdm (gnome display manager) via SPM in Precise. I chose lightdm to be the default display manager but,
still thought I would never be able to get back in to Precise. Since Precise's recovery mode is "read only" on all file systems I found very little I could do.

Then I stumbled upon a thread about recovery being read only and Paddy Landau had filed a bug. I cannot find that bug right now but I did note that Paddy had entered this in the comments of the bug as a workaround:
Login to recovery and drop to root shell and enter these:

Code:

mount --options remount,rw /
mount --all

I was then able to enter sudo dpkg-reconfigure lightdm without getting an error. I also purged gdm.
But, still when it booted up normally in gnome classic mode it would not get past the black screen with 4 dots changing to yellow and never going anywhere.
However, I found I could press ALT+F2 and get a login prompt. Once logged in I could start lightdm with sudo service start lightdm and it would then login normally.

By, now I know that lightdm is just not starting at bootup. I found this thread with the fix:
http://ubuntuforums.org/showthread.php?t=2049203

It told how sudo dpkg-reconfigure lightdm only put "lightdm" in /etc/X11/default-display-manager.
But, if you edited that file and put usr/sbin/lightdm in place of lightdm it would fix the whole problem.

**Paddy Landau** · January 20th, 2013

Originally Posted by Cavsfan

I cannot find that bug right now…

Bug #996454. Vote for it if it affects you.

**Cavsfan** · January 20th, 2013

Originally Posted by Paddy Landau

Bug #996454. Vote for it if it affects you.

Done! I cannot believe there are only 11 (after me) people that claim to be affected by this. This was a nightmare!
Thanks for the workaround Paddy! That saved doing a clean install and at least a couple of days getting things back like they were.
I will have those notes available at all times. I am pretty sure everything after Precise opens as read only in recovery.

I think I'll try to install the latest Nvidia driver from Nvidia's website.

**bogan** · January 21st, 2013

Hi!, Cavsfan.

"Done! I cannot believe there are only 11 (after me) people that claim to be affected by this".

Nor can I !

I just subscribed to it, and it now says:

Recovery Mode starts in read-only, does not mount home folder, and hangs when trying to do something Edit

Reported by Paddy Landau on 2012-05-08

You have subscribed to this bug report.

52
This bug affects you and 10 other people

A BUG in a bug, maybe??

Chao!, bogan.

**Paddy Landau** · January 21st, 2013

Originally Posted by bogan

I just subscribed to it … A BUG in a bug, maybe??

Subscribing is not a vote (you may subscribe but not consider it a problem). You need to click on the green wording, and it will ask you whether or not it affects you. Click "Yes" and it will add your vote.