Closed GoogleCodeExporter closed 9 years ago
Just to be sure, I reverted to revision 145 (which was a revision I am sure did
not
crash upon exiting). I still get the crash reports when exiting. And I can't
move
tags either. I will upgrade again to 174 now.
Original comment by davito...@gmail.com
on 3 Feb 2009 at 9:17
it works for me (i'm using jbrout 0.3.174 on Ubuntu 8.10)
Original comment by thibaut....@gmail.com
on 3 Feb 2009 at 10:13
Hmmm. So is it something in my tags or category names? I am trying to move a
lower
case non-accented tag on a non-accented category. I tried several tags and
several
categories with the same result. Of course, I could erase my database and
rebuild it,
but this is hardly a user-friendly solution ;-)
I just emptied my Application Data/jBrout folder to check. I then started
jBrout. He
asked me the usual first-time questions and I got a nice empty view ;-) But
when I
exited jBrout (without doing anything else) I got the Windows error reporting
dialog.
I wonder what is going on.
Then I reloaded jBrout, re-importing my full picture collection... And getting
another import error dialog (sigh). I will file a separate issue for this. I'll
finish posting my test results once I finish importing my pictures and tags. If
I
ever manage to import them and don't go nuts first...
Original comment by davito...@gmail.com
on 3 Feb 2009 at 10:45
After managing to recover a few tags to test, I re-tested moving a tag from a
Category to another. I got another error:
File "jbrout.py", line 2578, in on_treeviewtags_drag_data_received
dragFrom =context.get_source_widget().__class__.__name__
AttributeError: 'gtk.gdk.DragContext' object has no attribute 'get_source_widget'
Original comment by davito...@gmail.com
on 3 Feb 2009 at 11:03
Can't reproduce on Gentoo Linux either but can reproduce in Windows XP virtual
Machine, looks like a windows only issue
Original comment by r...@wallace.gen.nz
on 5 Feb 2009 at 6:57
I have created a issue 68 for the crash upon exiting in as this is a different
issue
form the tag renaming.
Original comment by r...@wallace.gen.nz
on 21 Feb 2009 at 9:48
Fixed in r190 with an update to the Windows Python runtime.
With Versions as follows:
- pycairo-1.4.12-2.win32-py2.5
- pygobject-2.14.2-2.win32-py2.5
- pygtk-2.12.1-3.win32-py2.5
Original comment by r...@wallace.gen.nz
on 7 Apr 2009 at 10:55
Hmm, it does not seem to work. I believe I have the correct libraries (but I
don't
know how to check). I updated to r190. When I drag a tag to a category, I get:
Traceback (most recent call last):
File "jbrout.py", line 2573, in on_treeviewtags_drag_data_received
dragFrom =context.get_source_widget().__class__.__name__
AttributeError: 'gtk.gdk.DragContext' object has no attribute 'get_source_widget'
BTW, I suggest showing the libraries versions in the jBrout About dialog would
be
useful when debugging.
Original comment by davito...@gmail.com
on 7 Apr 2009 at 9:26
I have not found a way to completely check the library versions as the system
call
that shows the version for PyGTK omly shows the three parts not the additional
Windows build number which makes a significant difference.
Basic version numbers for those libraries tat support it have been added to the
about
box in r191
Original comment by r...@wallace.gen.nz
on 9 Apr 2009 at 11:34
Nice! Ok, here are my new infos:
Traceback (most recent call last):
File "jbrout.py", line 2580, in on_treeviewtags_drag_data_received
dragFrom =context.get_source_widget().__class__.__name__
AttributeError: 'gtk.gdk.DragContext' object has no attribute 'get_source_widget'
Library Versions:
Python: 2.5.2
PyGTK: 2.12.1
GTK: 2.12.9
PIL: 1.1.6
Strange, though, jBrout reports python 2.5.2, but here is what I get when I load
python manually from the command line:
Python 2.6.1 (r261:67517, Dec 4 2008, 16:51:00) [MSC v.1500 32 bit (Intel)] on
win32
... ah, jBrout uses it's own copy of the python engine! I have three different
versions: Python 2.6, jBrout's and OpenOffice's :-)
I updated the libraries for my python 2.6 (I wanted to update the engine for
Gimp),
not for python 2.5. Now I guess I'll have to update my jBrout python 2.5
version. Or
is there a way to tell jBrout to use my 2.6 engine instead?
Original comment by davito...@gmail.com
on 10 Apr 2009 at 7:50
Original issue reported on code.google.com by
davito...@gmail.com
on 3 Feb 2009 at 8:56