If i close the scribes window before it finishes loading a file, program does not end

I can't reproduce this problem. What version of scribes are you using?

scribes -v

Here you go!

# scribes -v
output : Scribes version 0.4-dev-build481

Can you reproduce the problem with build 499?

Yeap, i can. Just pulled from repository and tested.

Here's a video showing this bug happening http://www.2shared.com/file/8636253/4b6fc6c0/scribes-bug.html

Uses xvid codec.

Possible workaround for this problem is available in build 500. Please test.

Bug is still there.

This time, if i wait a little before closing scribes, i get this error message:

Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/SCRIBES/RegistrationManager.py", line 42, in __unregister_cb
    self.__unregister(_object)
  File "/usr/lib/python2.6/dist-packages/SCRIBES/RegistrationManager.py", line 33, in __unregister
    self.__objects.remove(_object)
ValueError: deque.remove(x): x not in deque

Please test build 501.

Thanks

Still get this error.

Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/SCRIBES/RegistrationManager.py", line 42, in __unregister_cb
    self.__unregister(_object)
  File "/usr/lib/python2.6/dist-packages/SCRIBES/RegistrationManager.py", line 33, in __unregister
    self.__objects.remove(_object)
ValueError: deque.remove(x): x not in deque

You're getting this error with build 501?

Let me see the output of scribes -i

Yeap. Still.

scribes -i

========================================================
System Info: ('Linux', 'italo-laptop', '2.6.28-16-generic', '#55-Ubuntu SMP Tue Oct 20 19:48:24 UTC 2009', 'i686')
Python Version: 2.6.2 (release26-maint, Apr 19 2009, 01:56:41)
[GCC 4.3.3]
System Byteorder: little
Python Modules: ('__builtin__', '__main__', '_ast', '_bisect', '_codecs', '_collections', '_functools', '_locale', '_random', '_socket', '_sre', '_struct', '_symtable', '_warnings', '_weakref', 'array', 'binascii', 'cPickle', 'cStringIO', 'errno', 'exceptions', 'fcntl', 'gc', 'grp', 'imp', 'itertools', 'marshal', 'math', 'operator', 'posix', 'pwd', 'select', 'signal', 'spwd', 'strop', 'sys', 'syslog', 'thread', 'time', 'unicodedata', 'xxsubtype', 'zipimport', 'zlib')
========================================================
Scribes Version: 0.4-dev-build501
Dbus Version: (0, 83, 0)
GTK+ Version: (2, 16, 1)
PyGTK Version: (2, 14, 1)
GNOME Python Version: (2, 26, 1)
Psyco Not Installed
========================================================
Running Instance: 0
========================================================
Python Path: /usr/lib/python2.6/dist-packages
Plugin Path: /usr/share/scribes/plugins
Data Path: /usr/share/scribes
Executable Path: /usr/bin
========================================================

I've added some debug code to build 502 to find the offending objects. Please run build 502 and print the output to the terminal here. I also want to know if Scribes quits properly.

Thanks

Ok, no error message this time, but i got a "Finalizado" message after killing the process. The problem persists with build 502.

Not was I was looking for. Where any python objects printed to the terminal. Let me see the exact output of the printout.

Thanks

Nothing else was printed in the terminal. Just "finalizado". Vc é brazileiro?

Please test build 503.

I blocked the close signal on the window until Scribes can quit properly. That's the only solution I can come up with because I can't reproduce the problem.

Thanks

Ok. I can't reproduce the bug with build 503. Did you try ALT+F4 just after the scribes window begins to show? That's how i make the bug happen.

Yeap, I tried all that and still could not reproduce the bug. I think the problem might be that certain services might be in the process of initializing when the quit signal is emitted. These services are not completely initialized thus don't get the quit signal. The current solution makes sures all the key services are properly initialized before you can quit Scribes.

Thanks for helping and testing.