• Unable to start Seahorse?


    hm… i do not get any error message here on installed GNOME but i need to kill seahorse also and the it will start…

  • So the conclusion is that it’s something odd going on with seahorse and gnome…

  • I do get the GUI on i3, so must Be a problem with unlocking the gnome key on login… May caused by lightdm?

  • Don’t think so… On my Virtualbox test install, I am using LightDM, on my two computers I am using GDM…

  • i do test with gdm and sehorse starts fine under GNOME :(

  • Hmmm… strange…

  • but closing it and try start again fails then too…

  • what is your seahorse version?

    pacman -Qs seahorse

  • seahorse 3.29.92+6+gdd81db31-1
    
  • i do have

    pacman -Qs seahorse
    local/seahorse 3.30-1
    

    from testing
    https://www.archlinux.org/packages/testing/x86_64/seahorse/
    installed now…
    seems to work without issue ;)

    3.29.92+6+gdd81db31-1 is Flagged out-of-date on 2018-09-11…

  • Why didn’t you say that at once… ;) That version works fine, for me too., thx… :)

  • i wanted to try downgrading first but then i see the testing version shown from within downgrade:

    downgrade seahorse 
    Available packages:
    
    *  1) seahorse-3.30-1-x86_64.pkg.tar.xz (remote)
    *  2) seahorse-3.30-1-x86_64.pkg.tar.xz (local)
       3) seahorse-3.29.92+6%2Bgdd81db31-1-x86_64.pkg.tar.xz (remote)
    *  4) seahorse-3.29.92+6+gdd81db31-1-x86_64.pkg.tar.xz (local)
       5) seahorse-3.20.0+288%2Bgce2340dc-1-x86_64.pkg.tar.xz (remote)
       6) seahorse-3.20.0+105%2Bgb31e32fe-1-x86_64.pkg.tar.xz (remote)
       7) seahorse-3.20.0+94%2Bg4c671a78-1-x86_64.pkg.tar.xz (remote)
       8) seahorse-3.20.0+44%2Bga1474bb-1-x86_64.pkg.tar.xz (remote)
       9) seahorse-3.20.0-2-x86_64.pkg.tar.xz (remote)
      10) seahorse-3.20.0-1-x86_64.pkg.tar.xz (remote)
    

    But it do not show repositories… then i do research and see it was from testing, and current version is out of date ;)

unable76 seahorse3 Posts 32Views 1073
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.