Page 5 of 7 FirstFirst ... 34567 LastLast
Results 41 to 50 of 64

Thread: Known Hardy bugs and workarounds

  1. #41
    Join Date
    Jan 2005
    Location
    Israel
    Beans
    74

    Re: Known Hardy bugs and workarounds

    Quote Originally Posted by chrisccoulson View Post
    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.

  2. #42
    Join Date
    Jul 2008
    Beans
    3

    Re: Known Hardy bugs and workarounds

    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

  3. #43
    Join Date
    Jun 2005
    Location
    France
    Beans
    7,100
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Known Hardy bugs and workarounds

    Quote Originally Posted by Stilor View Post
    Added to the list, thanks for your feedback.

  4. #44
    Join Date
    Aug 2008
    Beans
    76

    Re: Known Hardy bugs and workarounds

    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.
    Code:
    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.
    Code:
    sudo fdisk -l
    In my case I was looking for the last device listed:
    Code:
    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.
    Code:
    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.
    Last edited by fhsm; August 6th, 2008 at 12:53 AM. Reason: New Information

  5. #45
    Join Date
    Oct 2005
    Beans
    660

    Re: Known Hardy bugs and workarounds

    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
    Last edited by editrix; September 6th, 2008 at 10:11 AM. Reason: New info

  6. #46
    Join Date
    Jun 2008
    Beans
    53

    not sure if problem here...

    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

  7. #47
    Join Date
    Jun 2008
    Beans
    53

    found solution

    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

  8. #48
    Join Date
    Oct 2007
    Beans
    145

    Re: Known Hardy bugs and workarounds

    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.

  9. #49
    Join Date
    Feb 2008
    Location
    wouldnt you like to know
    Beans
    57
    Distro
    Ubuntu 9.10 Karmic Koala

    Smile Re: Known Hardy bugs and workarounds

    dont forget the screen resolution problem

    {run this in terminal}
    gksu displayconfig-gtk

  10. #50
    Join Date
    Oct 2007
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Known Hardy bugs and workarounds

    hi,
    many might know this but adding to the list

    if unable to access trash while using sudo nautlius
    Code:
     gksudo nautilus
    workaround:>
    Code:
    gksudo dbus-launch nautilus

Page 5 of 7 FirstFirst ... 34567 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •