Known Hardy bugs and workarounds

[yotam]

Excessive disk I/O in Firefox 3b5

Workaround - http://ubuntuforums.org/showpost.php?p=4770985&postcount=50
Bug report - https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/215728

The suggestion to uncheck the 'Tell me ... suspected attack sites'
and remove urlclassifier* files seems to help only a little.
Soon after some surfing I had my
~/.mozilla/firefox/*.default/urlclassifier3.sqlite
recreated.

[Stilor]

Bug: https://bugs.launchpad.net/ubuntu/ha...er/+bug/203016
Fix: Install package from Intrepid, fix is still not in Hardy. http://linux-tipps.blogspot.com/2008...rkmanager.html

[frodon]

Bug: https://bugs.launchpad.net/ubuntu/ha...er/+bug/203016
Fix: Install package from Intrepid, fix is still not in Hardy. http://linux-tipps.blogspot.com/2008...rkmanager.html

Added to the list, thanks for your feedback.

[fhsm]

Setting an invalid mount point makes removable media unaccessible
Bug: 107668
Bug Description:
After accidentally setting a bad mount point for an external drive it becomes inaccessible. Attempts to mount the drive return "Cannot mount volume. Unable to mount volume" "mount_point cannot contain the following characters: newline, G_DIR_SEPERATOR (usually /)".

Workaround:
1- Make a new spot to put mount your drive using mkdir.

sudo mkdir /media/yourdrivehere

Mounting external drives to /media is standard but not required. You should replace 'yourdrivehere' with a more useful name.

2- Figure out what the system is calling the device you are looking to mount by running fdisk -l with the device attached to the system.

sudo fdisk -l

In my case I was looking for the last device listed:

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            1        9729    78148161    7  HPFS/NTFS

Of use here is the device name /dev/sdb1 and the format NTFS

3- Set your device to mount to the new mount point using the mount command.

sudo mount -t ntfs /dev/sdb1 /media/yourdrivehere

For this last command you'll obviously need to use whatever your device is called (as found in step 2) the file system of your devices (NTFS in the example, could be ext3, vfat, etc) and the mount point you made in step 1.

continued in Update 2
--------------------------------------------------------------------------------------
Update:
While this will get you to your drive without any problem the solution is not persistent. The same error returns after a reboot. The solution works on subsistent reboots.

---------------------------------------------------------------------------------------
Update 2:

So I think I've got an actual solution to this problem now. Picking up from where I left off in the start of the post...

4- With the drive mounted successfully return to the HH gui and go to an icon for the drive (I used the icon on the desktop). Right click and select “properties” then the “Drive” tab of the resulting pop-up. On the “Drive” tab click “settings” to expand the options and delete anything that is in the three fields (Mount Point; File System; Mount Options) that appear. Then select the “Volume” tab and click on “Settings” and clear the three fields that appear. Click close on the bottom right side of the pop up.

5- Reboot the system with the drive attached. It should restart with the drive mounted into a default location like /media/DriveLable. At this point you are back where you started and can set a new mount point correctly.

[editrix]

Can't burn a CD: https://bugs.launchpad.net/bugs/149076

Two workarounds. One posted at the above URL that involves installing and configuring cdrecord, and one I just posted about using Wine and ImgBurn:
http://ubuntuforums.org/showthread.php?t=884700

Just found a third: http://ubuntuforums.org/showthread.p...44#post5721644

[zapree]

Ok so last night i turn off my computer normal, and then turn it on in the morning and the ubuntu logo comes up status bar, it loads finishes, and then goes to a terminal window asking for my username/password. Im stumped and not sure if the fix was in here. Also before it asks for my username/password it comes up with kinit not loading, or something like that. Right now i am using the boot disk to try and find a solution without reinstalling the whole thing.
thanks a bunch
patrick

[zapree]

sorry for posting before looking elswhere, i found my answer by searching kinit seems it has happened to many people (and perhaps you have it as one of your solutions and i just diddnt find it)
thanks
Patrick

[bthoward]

Gnome panel often crashes when clicking the clock to view the calendar.

If you have enabled a google calendar in Evolution your calendar events are pulled in from google. These are attempted to be displayed when you open the gnome calendar. Sometimes this works but very often gnome-panel crashes. Alt+F2 no longer works when in this state.

Do a CTRL+ALT+F1 then login and run killall gnome-panel then press ALT+F7 and gnome-panel will be automatically re-run and things will be back to normal. Turn off the google calendar source in Evolution and the panel becomes MUCH more robust.

[JohnsShadow]

dont forget the screen resolution problem

{run this in terminal}
gksu displayconfig-gtk

[macvr]

hi,
many might know this but adding to the list

if unable to access trash while using sudo nautlius

 gksudo nautilus

workaround:>

gksudo dbus-launch nautilus