-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
everpad not working in ubuntu 16.04 #492
Comments
I am having a similar problem:
I am new to all this, but this is what I did to get it compiled on Linux Mint 18:
References: |
@squirrelboot Traceback (most recent call last): |
@squirrelboot Traceback (most recent call last): |
It looks like this project died a couple years ago. That's unfortunate. |
Everpad throws following error after few seconds
Traceback (most recent call last):
File "/usr/local/bin/everpad", line 9, in
load_entry_point('everpad===2.5dev-r0', 'gui_scripts', 'everpad')()
File "build/bdist.linux-x86_64/egg/everpad/pad/indicator.py", line 357, in main
File "build/bdist.linux-x86_64/egg/everpad/tools.py", line 39, in wrapper
File "build/bdist.linux-x86_64/egg/everpad/tools.py", line 15, in init
File "build/bdist.linux-x86_64/egg/everpad/tools.py", line 18, in load
File "build/bdist.linux-x86_64/egg/everpad/tools.py", line 55, in get_pad
File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in __init
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
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.
The text was updated successfully, but these errors were encountered: