https://bugzilla.novell.com/show_bug.cgi?id=346987
User bryeny@mi-tech.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=346987#c2
Bryen Yunashko
Please attach y2logs. If you are in doubt follow:
http://en.opensuse.org/Bugs/YaST
Thanks!
Hi Cyril, I'm helping Darragh with collecting symptoms, so I'll post the logs here. I have identified an interesting difference in behavior. In the above first report, that is generated when you do: 1. Command line to start Orca 2. Start Yast2 in Gnome. 3. In this case, it is the module that crashes and generates the error mentioned above. 4. The yast2log is attached as y2log-826 (indicating it happened at 8:26 p.m.) I tried recreating this in a different method by: 1. Command line to start Orca 2. In a second gnome-terminal window, start yast2 from the command line. 2a. The following output occurs on the yast2 gnome-terminal window: (y2controlcenter-gnome:4026): libgnomevfs-CRITICAL **: gnome_vfs_get_uri_from_local_path: assertion `g_path_is_absolute (local_full_path)' failed (y2controlcenter-gnome:4026): libgnomevfs-CRITICAL **: gnome_vfs_monitor_add: assertion `text_uri != NULL' failed (y2controlcenter-gnome:4026): libgnomevfs-CRITICAL **: gnome_vfs_get_uri_from_local_path: assertion `g_path_is_absolute (local_full_path)' failed (y2controlcenter-gnome:4026): libgnomevfs-CRITICAL **: gnome_vfs_monitor_add: assertion `text_uri != NULL' failed 2b. Yast2 does start up and everything is fine. 2c. However, going back to the first gnome-terminal where Orca was started on the command line: Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/orca/atspi.py", line 700, in __init__ self.accessible.ref() COMM_FAILURE Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/orca/atspi.py", line 700, in __init__ self.accessible.ref() COMM_FAILURE Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/orca/atspi.py", line 700, in __init__ self.accessible.ref() COMM_FAILURE 3. Selected a module (in this case Software Repositories) 3a. Accessing the Package Management Failed: Another process is accessing the package database. Package management cannot be used now." 4. Despite these errors, Orca is still running. It is only Yast2 that does not continue. The log report in this case is y2log-917 (because it occurred at 9:17 p.m.) Please let us know if we can provide any further information. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.