abrt 1.0.6 detected a crash. architecture: i686 cmdline: python /usr/bin/wallpapoz component: wallpapoz executable: /usr/bin/wallpapoz kernel: 2.6.31.12-174.2.22.fc12.i686 package: wallpapoz-0.4.1-16.svn92_trunk.fc12 release: Fedora release 12 (Constantine) backtrace ----- Summary: TBbff02bde wallpapoz:897:reordering_node_after_cut_and_paste:ValueError: invalid tree path Traceback (most recent call last): File "/usr/bin/wallpapoz", line 1025, in delete_wallpaper self.cut_and_reordering_treeiter() File "/usr/bin/wallpapoz", line 978, in cut_and_reordering_treeiter lowest_iter_list = self.reordering_node_after_cut_and_paste( self.selected_iter ) File "/usr/bin/wallpapoz", line 897, in reordering_node_after_cut_and_paste self.store.get_iter( (parent_number_index, iter_workspace_index+1) ) ) ValueError: invalid tree path Local variables in innermost frame: done_workspace: False lowest_iter_list: [] copy_iter_child_number: 0 parent_number_index: 0 self: <__main__.Wallpapoz instance at 0x86945ac> copy_iter: <GtkTreeIter at 0x8823a60> copy_iter_list: [<GtkTreeIter at 0x8823a60>] copy_iter_parent_number: 0 iter_workspace_index: 0
Created attachment 395389 [details] File: backtrace
Would you - provide the exact procedure how to reproduce this issue in detail? - attach your * ~/.wallpapoz/wallpapoz.xml * ~/.xsession-errors ? - What desktop environment are you using and how many workspaces do you have? Also would you tell me if you have some desktop effect enabled?
Created attachment 395562 [details] wallpapoz.xml
Created attachment 395565 [details] xsession-errors
I used the standard crash reporting utility of Fedora Core 12. Just before the crash I was adding pictures and using copy-and-paste to move pictures to other workspaces. I do not remember *exactly* what I did. Sorry about that. I tried to reproduce the error tonight but was unsuccessful. Next time I will make better notes. I have added the requested files. The .xsession-errors is edited to show only the wallpapoz related loggings. I hope you can find a clue there! I use Gnome, desktop-effects are enabled (no wobbly windows and no desktop cube) and have the standard 4 workspaces. Happy bug hunting!
Would you remember what names (full paths) of files you were going to add?
These are four examples of filenames: /disk/export/Fotoalbum/Vakantie/2006 Mexico/IMG_3066.JPG /disk/export/Fotoalbum/Vakantie/2009 Athene/IMG_1972.JPG /home/robert/Pictures/IMG_2541.jpg /home/robert/Pictures/foto030.jpg The exact imagenumber (3066,1972,2541,030) was maybe different.
One more question - Are there any files which contains non-UTF8 characters "near" the files you were trying to add (e.g. in the same or child directories)?
No there are not. There is one subdirectory in one of those aforementioned directories for which I do not have permission to access.
Package: wallpapoz-0.4.1-20.svn92_trunk.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) Comment ----- removing active wallpaper from the list
Package: wallpapoz-0.4.1-20.svn92_trunk.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Open up wallpapoz trough the Gnome menu 2. Select a wallpaper and press <Delete> key. 3. Comment ----- Only happens when there is only 1 wallpaper per desktop.
(In reply to comment #12) > Comment > ----- > Only happens when there is only 1 wallpaper per desktop. Reproducible...
Would you try this? http://kojipkgs.fedoraproject.org/packages/wallpapoz/0.4.1/23.svn92_trunk.fc12/
Tried that one. # rpm -qa wallpapoz wallpapoz-0.4.1-23.svn92_trunk.fc12.noarch # With one desktop picture per desktop the *Delete wallpaper* is greyed out now. Also selecting with the <shift> or <ctrl> keys to select multiple pictures to be deleted doesn't work anymore.
As wallpapoz requires that one workspace has at least one wallpaper entry, it is an expected behavior currently. ( For example, if you try - once save (backup) ~/.wallpapoz/wallpapoz.xml to somewhere - remove wallpapoz.xml - then execute $ wallpapoz Then wallpapoz.xml is initialized and that xml file has one wallpaper on every workspace entry ) So for now I regard that this issue is fixed.
(In reply to comment #16) > As wallpapoz requires that one workspace has at least one wallpaper > entry, it is an expected behavior currently. Hmm. I'm ok with that. But i'm still puzzled about the <shift> and <ctrl> key selection that works before and isn't now. Should i file a new bugzilla on this. PS: Thanks for the updates. I really appriciate it.
(In reply to comment #17) > But i'm still puzzled about the <shift> and <ctrl> key selection that works > before and isn't now. > > Should i file a new bugzilla on this. Actually with this comment of yours, I firstly noticed that there was a way to remove multiple wallpapers at once. Maybe are you trying to remove multiple wallpapers across desktop or remove all wallpapers in one desktop? I guess the formar didn't work even with previous rpm, and now the latter won't work because at least one wallpaper is required on each desktop. If neither of this is your case, please file another bug (providing the _detailed_ procedure to reproduce this issue is appreciated).
wallpapoz-0.4.1-24.svn92_trunk.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/wallpapoz-0.4.1-24.svn92_trunk.fc13
wallpapoz-0.4.1-24.svn92_trunk.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/wallpapoz-0.4.1-24.svn92_trunk.fc12
wallpapoz-0.4.1-24.svn92_trunk.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update wallpapoz'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/wallpapoz-0.4.1-24.svn92_trunk.fc12
wallpapoz-0.4.1-24.svn92_trunk.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
wallpapoz-0.4.1-24.svn92_trunk.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.