everpad
everpad copied to clipboard
I can't start Everpad - (Api version Mismatch)
Hi,
I have an issue while executing latest (and older versions of) everpad (which was updated today - 2012.01.16). (I'm using ppa sources.) When I execute it it shows on tray, but says "api version mismatch / restart everpad"
I'm using linux mint 13 (maya) x64 with mate 1.4.2, "gir1.2-notify-0.7" is installed.
This is what I get when I try to execute "everpad" from terminal:
"sni-qt/19998" WARN 12:16:20.001 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE ERROR:dbus.proxies:Introspect error on :1.4:/EverpadProvider: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
This is what I get when I try to get "everpad-provider" from terminal:
Traceback (most recent call last):
File "/usr/bin/everpad-provider", line 9, in
This is what I get when I try "everpad-lens" from terminal:
ERROR:dbus.proxies:Introspect error on :1.123:/EverpadProvider: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
ERROR:dbus.proxies:Introspect error on :1.126:/EverpadProvider: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Traceback (most recent call last):
File "/usr/bin/everpad-lens", line 9, in
What could be the issue? How can I fix this?
Thanks,
Try to reboot. Error in everpad-provider 2.3.
Hi,
After the restart, the issue keeps on happening. It was also same on one older version.
Thanks,
What DE you use?
I'm using Mate 1.4.2 as Desktop Environment.
I am having the same problem as Ardakilic. I am using Linux Mint 14 KDE (4.9.4) 64 bit. Everpad 2.4.
same here Xubuntu 12.04.1 LTS restarted the whole system several times still showing the error "api version missmatch, please restart"
A workarround. In a terminal I run "everpad-provider" then in another terminal session I run "everpad" then it works. It looks like the main everpad script have problems starting everpad-provider by its own
everpad-provider does not start for me, it just dumps an error log at terminal and closes, so dotjorgeu's workaround does not work for me.
This is the report:
Traceback (most recent call last):
File "/usr/local/bin/everpad-provider", line 9, in
What you see when:
everpad --version
everpad-provider -- version
?
This is the output for both:
Everpad version: 2.4 API version: 2 Schema version: 3
Try to remove everpad package, and all of:
find /usr/ -name everpad
You have clash of versions. And install package.
There were two folders from git cloning (/usr/local/lib/python2.7/dist-packages/everpad-2.4dev-py2.7.egg/everpad and /usr/local/lib/python2.7/dist-packages/everpad-2.3dev-py2.7.egg/everpad), and this one: /usr/local/bin/everpad deleted them all (sudo rm -R /folder), and restarted the machine, installed the everpad again, same issue goes on. --version gives 2.4 for all.
This is very last terminal output of everpad:
"sni-qt/18814" WARN 16:25:08.055 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE ERROR:dbus.proxies:Introspect error on :1.116:/EverpadProvider: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
and this is the very last output of everpad-provider:
Traceback (most recent call last):
File "/usr/local/bin/everpad-provider", line 9, in
And this is the very last output of everpad-lens:
ERROR:dbus.proxies:Introspect error on :1.134:/EverpadProvider: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
ERROR:dbus.proxies:Introspect error on :1.137:/EverpadProvider: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Traceback (most recent call last):
File "/usr/local/bin/everpad-lens", line 9, in
Thanks for the interest
Try to remove everpad package, and all of:
find /usr/ -name everpad You have clash of versions. And install package.
I removed everpad via synaptic (complete removal). Issuing 'find /usr/ -name everpad' in terminal returned nothing. Reinstalled everpad 2.4 via synaptic and still get same output as Ardakilic:
Everpad version: 2.4 API version: 2 Schema version: 3
How do I avoid the conflict of versions?
Same issue here on Mint 14 Cinnamon 64 bit, installed via ppa
Everpad version: 2.4 API version: 2 Schema version: 3
Installed fine and was working but now doesn't show in panel. Running "everpad" command from terminal results in nothing. Running "everpad-provider" from terminal gives:
Traceback (most recent call last):
File "/usr/bin/everpad-provider", line 9, in
Attempting dotjorgeu's workaround of launching everpad in 2nd terminal results in
"sni-qt/6589" WARN 23:30:31.958 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE ERROR:dbus.proxies:Introspect error on :1.6:/EverpadProvider: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
When using Mate, make sure you have disabled all gnome related items in Startup Applications. Specifically keyring daemon. Both running gnome-keyring-daemon and mate-keyring-daemon result in conflict. I had the same issue in Mint Maya x64. After I disabled gnome-keyring-daemon startup everything works just fine. See https://bugs.launchpad.net/linuxmint/+bug/1005635
Also can't start everpad-provider.
Mint 14 Mate
$ everpad-provider --version Everpad version: 2.5 API version: 6 Schema version: 5
$ everpad-provider
Traceback (most recent call last):
File "/usr/bin/everpad-provider", line 9, in
Everpad doesn't start...
Mint 14 Mate 64bit
$ everpad --version Everpad version: 2.5 API version: 6 Schema version: 5
$ everpad-provider --version Everpad version: 2.5 API version: 6 Schema version: 5
ERROR:dbus.proxies:Introspect error on /EverpadProvider: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) 1
All gnome related items in Startup Applications are disabled. What I did: reboot, re-logon, removed "everpad package, and all of: find /usr/ -name everpad", reinstalled package (from ppa)
Have the same problem as below. Ubuntu 12.10. I have installed Everpad from scratch.
$ everpad --version Everpad version: 2.5 API version: 6 Schema version: 5 $ everpad-provider --version Everpad version: 2.5 API version: 6 Schema version: 5
Recently reinstalled linux mint 14 mate edition, and it has only mate-keyring-daemon and still gave this error, but after installing gnome-keyring-daemon it works.
I have:
$ everpad --version Everpad version: 2.5 API version: 6 Schema version: 5 $ everpad-provider --version Everpad version: 2.5 API version: 6 Schema version: 5
and the daemons running with the following parameters: /usr/bin/gnome-keyring-daemon --daemonize --login mate-keyring-daemon --start --components=gpg
On 06/01/2013 11:39 AM, Marco Constâncio wrote:
Recently reinstalled linux mint 14 mate edition, and it only has mate-keyring-daemon and still gave this error, but after installing gnome-keyring-daemon it works.
I have:
$ everpad --version Everpad version: 2.5 API version: 6 Schema version: 5 $ everpad-provider --version Everpad version: 2.5 API version: 6 Schema version: 5
and the daemons running with the following parameters: /usr/bin/gnome-keyring-daemon --daemonize --login mate-keyring-daemon --start --components=gpg
— Reply to this email directly or view it on GitHub https://github.com/nvbn/everpad/issues/215#issuecomment-18793441.
I especially like nixnotes. It syncs with Everpad and on the web and can accept imports from Dropbox that in turn pass on to Everpad. I am a KDE aficionado which makes me like nixnotes all the more. Just had an update yesterday. Rob Burness
Same issue here in a Ubuntu 14.04.1 LTS clean installation
uname -a
Linux HAL 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
root@HAL:~# apt-get install everpad
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
everpad
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 162 kB of archives.
After this operation, 1.887 kB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/nvbn-rm/ppa/ubuntu/ trusty/main everpad amd64 2.15.8-0~trusty [162 kB]
Fetched 162 kB in 1s (134 kB/s)
Selecting previously unselected package everpad.
(Reading database ... 234552 files and directories currently installed.)
Preparing to unpack .../everpad_2.15.8-0~trusty_amd64.deb ...
Unpacking everpad (2.15.8-0~trusty) ...
Processing triggers for hicolor-icon-theme (0.13-1) ...
Processing triggers for gnome-menus (3.10.1-0ubuntu2) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.54ubuntu1) ...
Setting up everpad (2.15.8-0~trusty) ...
Processing triggers for python-support (1.0.15) ...
root@HAL:~# everpad --version Everpad version: 2.5 API version: 6 Schema version: 5
root@HAL:~# everpad-provider --version Everpad version: 2.5 API version: 6 Schema version: 5
The first time show this warning
root@HAL:~# everpad "sni-qt/22274" WARN 04:33:58.999 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
and ask the password to unlock the keyring but after that is doing nothing
If the socket is busy i got this message
^C
root@HAL:~# everpad
"sni-qt/22326" WARN 04:35:01.535 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
Traceback (most recent call last):
File "/usr/bin/everpad", line 9, in
Linux Mint, 64bit. Can't start
faiwer@faiwer-mint ~ $ everpad-provider
Traceback (most recent call last):
File "/usr/bin/everpad-provider", line 9, in <module>
load_entry_point('everpad==2.5dev', 'console_scripts', 'everpad-provider')()
File "/usr/lib/pymodules/python2.7/everpad/provider/daemon.py", line 95, in main
app = ProviderApp(args.verbose, sys.argv)
File "/usr/lib/pymodules/python2.7/everpad/provider/daemon.py", line 34, in __init__
if get_auth_token():
File "/usr/lib/pymodules/python2.7/everpad/provider/tools.py", line 35, in get_auth_token
return get_keyring().get_password('everpad', 'oauth_token')
File "/usr/lib/python2.7/dist-packages/keyring/core.py", line 37, in get_password
return _keyring_backend.get_password(service_name, username)
File "/usr/lib/python2.7/dist-packages/keyring/backend.py", line 197, in get_password
_, session = service_iface.OpenSession("plain", "")
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "OpenSession" with signature "ss" on interface "org.freedesktop.Secret.Service" doesn't exist
Facing same error with Gnome Ubuntu 14.04. Built from source.
Also facing the same error, with Gnome and Ubuntu 15.04. Installed using the ppa repo.
also facing this issue in Ubuntu 15.10 (built from soruce code)
same issue on arch+ xfce (gnome-keyring installed)
I found the same "workaround" like dotjorgeu. In a second terminal i can start everpad but just the window appears. I cant log in or do any other interactions with this window. So it's a not working "workaround"
Anybody got a solution right now?