Results 1 to 5 of 5

Thread: synaptic broken

  1. #1
    Join Date
    Sep 2006
    Beans
    110

    synaptic broken

    Synaptic is broken. At this time I have 4 broken dependencies:ekiga, f-spot, rhythmbox and tomboy; 8 autoremovables:bluez-audio, ekiga, evolution-common, f-spot, language-selector-common, rhythmbox, tomboy and update-manager; 8 residual configurations: alacarte, apturl, bluez-utils, evolution, evolution-exchange,jockey-gtk, software-properties-gtk and update notifier. Can I fix these problems without reinstalling? I have checked these forums for fixes and every fix has made things progressively worse.

  2. #2
    Join Date
    Jun 2008
    Location
    Vancouver Canada
    Beans
    3,139
    Distro
    Xubuntu 14.04 Trusty Tahr

    Re: synaptic broken

    Hi ferd.

    If you go to synaptic, you'll see on the left of the screen,"broken".

    Click on this and an option to fix broken packages will appear.

    Click this and all should be well.
    I learn something ubuntu everyday.
    dell precision T7500 1Tb hdd x 2
    2.67 Ghz intel xeon X5550 cpu
    nvidia quadro fx 4800-1.5 Gb video card

  3. #3
    Join Date
    Sep 2006
    Beans
    110

    Re: synaptic broken

    Quote Originally Posted by hansdown View Post
    Hi ferd.

    If you go to synaptic, you'll see on the left of the screen,"broken".

    Click on this and an option to fix broken packages will appear.

    Click this and all should be well.
    NO. Error 139, as always. Thanks for trying.

  4. #4
    Join Date
    Nov 2007
    Location
    New Zealand
    Beans
    1,224
    Distro
    Ubuntu Development Release

    Re: synaptic broken

    Quote Originally Posted by ferd View Post
    NO. Error 139, as always. Thanks for trying.
    Here is something about error 139?.....http://ubuntu-virginia.ubuntuforums.....php?p=4449219

    What version of Ubuntu are you running?

  5. #5
    Join Date
    Sep 2006
    Beans
    110

    Re: synaptic broken

    Quote Originally Posted by robert shearer View Post
    Here is something about error 139?.....http://ubuntu-virginia.ubuntuforums.....php?p=4449219

    What version of Ubuntu are you running?
    I am running Hardy. I had seen that post. It indicates that bug was fixed for Hardy. I guess I will be doing a reinstall next.

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
  •