After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 627038 - I see a traceback error message when I would like restart Orca with orca --replace command
I see a traceback error message when I would like restart Orca with orca --re...
Status: RESOLVED INCOMPLETE
Product: orca
Classification: Applications
Component: general
2.31.x
Other Linux
: Normal critical
: ---
Assigned To: Orca Maintainers
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-16 11:54 UTC by Hammer Attila
Modified: 2011-01-09 18:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Hammer Attila 2010-08-16 11:54:07 UTC 
Dear Developers,

When Orca is running, and I run orca --replace command, some time I see following traceback error message and Orca is not started:
root@hammera-laptop:/orca/orca# orca --replace

** (orca:4237): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (orca:4237): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (orca:4237): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
Traceback (most recent call last):

+ Trace 223253

  • File "<string>", line 1 in <module>
  • File "/usr/local/lib/python2.6/dist-packages/orca/orca.py", line 2119 in main 
    init(pyatspi.Registry)
  • File "/usr/local/lib/python2.6/dist-packages/orca/orca.py", line 1607 in init 
    registry.registerEventListener(_onChildrenChanged,
  • File "/usr/lib/python2.6/dist-packages/pyatspi/registry.py", line 331 in __getattribute__ 
    raise RuntimeError('Could not find or activate registry')
RuntimeError: Could not find or activate registry 
root@hammera-laptop:/orca/orca# 

I using Ubuntu Lucid, Orca latest uptodated git master version.

When I run orca --replace command again, Orca is launch fine. Unfortunately I unable to make this problem a debug.out file if I see this traceback error message. Or have a practical method to do Orca debug with this situation? I tryed orca --replace --debug-file=debug.out command.

Attila
Comment 1 Trevor Saunders (IRC: tbsaunde) 2011-01-07 21:21:34 UTC 
I see this was done from a root shell,  can you reproduce this from a normal user shell particularly the user running orca?  if not this is just that when you use sudo / us to become root a lot of your enviroment changes, and you can't communicate with orbit and corba touse pyatspi, or for that matter dbus.
Comment 2 Hammer Attila 2011-01-08 06:12:51 UTC 
Trevor, normal account I newer see this problem with longer time.
For example now I try running orca --replace command with my normal account, Orca process replaced succesful and Orca restarted.

Attila
Comment 3 Trevor Saunders (IRC: tbsaunde) 2011-01-08 06:34:33 UTC 
I'm not sure I  understand what you aid there, do I understand correctly that you don't have any issue anymore?
Comment 4 Joanmarie Diggs (IRC: joanie) 2011-01-09 18:52:32 UTC 
Trev, I'm taking Attila's comments to mean that things are working as expected. Closing as INCOMPLETE because I don't believe that we did anything in Orca to make this problem go away. We just don't know why it happened in the first place and cannot reproduce it now. Plus, for some reason, bgo lacks WORKSFORME.

Attila, if the bug reappears, please re-open.

Thanks guys!