You are not logged in.
This bug has been going on for about a year now. I stopped using Scribes because of it. Recently I did a fresh install and wanted to see if the situation had changed.
No, it hasn't.
The fix discussed here does not--and has never--worked for me.
Since that thread has been revived by another user with the same problem, I thought I would start a new thread that does not have a misleading '[SOLVED]' in the title.
The problem is that `scribes` runs perfectly well as root.
When run as any other user, however, the following errors occur:
Traceback (most recent call last):
File "/usr/bin/scribes", line 11, in <module>
main()
File "/usr/lib/python2.7/site-packages/SCRIBES/Main.py", line 8, in main
__open()
File "/usr/lib/python2.7/site-packages/SCRIBES/Main.py", line 24, in __open
Manager().open_files(uris, "utf-8", stdin)
File "/usr/lib/python2.7/site-packages/SCRIBES/InstanceManager.py", line 79, in open_files
self.__new_editor(stdin=stdin)
File "/usr/lib/python2.7/site-packages/SCRIBES/InstanceManager.py", line 163, in __new_editor
Editor(self, str(uri), encoding, stdin)
File "/usr/lib/python2.7/site-packages/SCRIBES/Editor.py", line 9, in __init__
Initializer(self, manager, uri, encoding, stdin)
File "/usr/lib/python2.7/site-packages/SCRIBES/ServicesInitializer.py", line 30, in __init__
Manager(editor, uri)
File "/usr/lib/python2.7/site-packages/SCRIBES/GUI/Manager.py", line 5, in __init__
Manager(editor, uri)
File "/usr/lib/python2.7/site-packages/SCRIBES/GUI/MainGUI/Manager.py", line 5, in __init__
Manager(editor, uri)
File "/usr/lib/python2.7/site-packages/SCRIBES/GUI/MainGUI/Window/Manager.py", line 5, in __init__
Window(editor)
File "/usr/lib/python2.7/site-packages/SCRIBES/GUI/MainGUI/Window/Window.py", line 8, in __init__
self.__set_properties()
File "/usr/lib/python2.7/site-packages/SCRIBES/GUI/MainGUI/Window/Window.py", line 36, in __set_properties
if get_value(): self.__set_rgba()
File "/usr/lib/python2.7/site-packages/SCRIBES/WidgetTransparencyMetadata.py", line 13, in get_value
database.close()
UnboundLocalError: local variable 'database' referenced before assignment
Any help would be appreciated, as it is completely beyond me why this occurs and has apparently survived in the Arch packaging for quite some months.
Offline
Same problem here. I posted in the other thread, just posting here again so jceasless doesn't seems to be just a crazy one with a problem. There's a lot of people out there with the same problem, for about a year or so.
So, +1 here. Any solution at the horizon? I hope so.
See you
Intel Core 2 Duo E8400 3.0 GHz | 2x1GB 667MHz | 250+750GB Seageate SATAII | Samsung 19" TFT 1440x900
Openbox + obmenugen + PyTyle | bmpanel2 | oblogout | conky | pyBgSetter (with Esetroot as backend)
Projects: obmenugen, pyBgSetter
Offline
Would it be appropriate for me to add a bug through the Arch packages web interface?
Given that I had Scribes running as user on an openSUSE box recently, I have a feeling that it is not an upstream bug.
Offline
I think it is appropiate, besides, it is running ok as root user.
Hopefully this issue would find an end. It's reaaly annoying.
See you
Intel Core 2 Duo E8400 3.0 GHz | 2x1GB 667MHz | 250+750GB Seageate SATAII | Samsung 19" TFT 1440x900
Openbox + obmenugen + PyTyle | bmpanel2 | oblogout | conky | pyBgSetter (with Esetroot as backend)
Projects: obmenugen, pyBgSetter
Offline
Here is the bug report.
Offline
In fact, running `scribes` as root is not error-free either.
After starting up, Scribes attempts to load its word completion module. The following is written to stdout:
File "/usr/lib/scribes/GenericPlugins/WordCompletion/SuggestionProcess/ScribesWordCompletionSuggestionGenerator.py", line 5, in <module>
from SCRIBES.Utils import fork_process
ImportError: No module named SCRIBES.Utils
Traceback (most recent call last):
File "/usr/lib/scribes/GenericPlugins/RecentOpen/ExternalProcess/ScribesRecentFilesIndexer.py", line 8, in <module>
from gobject import MainLoop, threads_init
File "/usr/lib/python2.7/site-packages/gobject/__init__.py", line 26, in <module>
from glib import spawn_async, idle_add, timeout_add, timeout_add_seconds, \
File "/usr/lib/python2.7/site-packages/glib/__init__.py", line 22, in <module>
from glib._glib import *
ImportError: /usr/lib/libpyglib-2.0-python2.so.0: undefined symbol: _Py_ZeroStruct
Traceback (most recent call last):
File "/usr/lib/scribes/GenericPlugins/WordCompletion/IndexerProcess/ScribesWordCompletionIndexer.py", line 3, in <module>
from SCRIBES.Utils import fork_process
Other tracebacks occur, all of which include
ImportError: No module named SCRIBES.Utils
.
This seems similar to the word completion problem described (also by me) in this thread. I attempted to reconstitute the solution proposed in that thread by konradstrack.
From what `scribes -i` displays, it seems to me that Scribes knows where its libraries are and that it needs to run with Python 2.7.2.
# scribes -i
System Info: ('Linux', 'dxxxxxxxx', '3.1.4-1-ARCH', '#1 SMP PREEMPT Tue Nov 29 09:08:04 UTC 2011', 'i686')
Python Version: 2.7.2 (default, Nov 21 2011, 17:24:32)
[GCC 4.6.2]
System Byteorder: little
Python Modules: ('__builtin__', '__main__', '_ast', '_codecs', '_sre', '_symtable', '_warnings', '_weakref', 'errno', 'exceptions', 'gc', 'imp', 'marshal', 'posix', 'pwd', 'signal', 'sys', 'thread', 'xxsubtype', 'zipimport')
========================================================
Scribes Version: 0.4-dev-build954
Dbus Version: (0, 84, 0)
GTK+ Version: (2, 24, 8)
PyGTK Version: (2, 24, 0)
Psyco Not Installed
========================================================
Running Instance: 0
========================================================
Python Path: /usr/lib/python2.7/site-packages
Plugin Path: /usr/lib/scribes/GenericPlugins
Data Path: /usr/share/scribes
Executable Path: /usr/bin
========================================================
I made a PKGBUILD which applies the 'from sys import executable' pattern which solved the WordCompletion problem for konradstrack in the thread linked above. You can find it in my bug report findings.
The bad news is that it has no effect for the problem of running Scribes as a user (at least on my box). The error message remains exactly the same.
It does however, remove all but one error message from running Scribes as root:
/usr/lib/python2.7/site-packages/SCRIBES/Main.py:10: Warning: g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed
main()
Offline