Bug 1147162 - [abrt] cherrytree: core.py:3319:image_handle:GError: Couldn't recognize the image file format for file '/home/jeff/GDriveDocs/College/BSA375/TeamC Project/Logical Model Diagram.vsd'
Summary: [abrt] cherrytree: core.py:3319:image_handle:GError: Couldn't recognize the i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cherrytree
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robin Lee
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:6d3895f16a337b811efd0ff4b91...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-27 18:40 UTC by Jeff
Modified: 2014-10-22 23:34 UTC (History)
3 users (show)

Fixed In Version: cherrytree-0.35.1-1.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-22 08:51:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (743 bytes, text/plain)
2014-09-27 18:40 UTC, Jeff
no flags Details
File: environ (1.81 KB, text/plain)
2014-09-27 18:40 UTC, Jeff
no flags Details

Description Jeff 2014-09-27 18:40:07 UTC
Description of problem:
I tried to import a visio image.  Obviously, Visio format is not recognized by CherryTree.  My bad.

Version-Release number of selected component:
cherrytree-0.33.4-1.fc20

Additional info:
reporter:       libreport-2.2.3
cmdline:        /usr/bin/python /usr/bin/cherrytree
executable:     /usr/bin/cherrytree
kernel:         3.16.3-200.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
core.py:3319:image_handle:GError: Couldn't recognize the image file format for file '/home/jeff/GDriveDocs/College/BSA375/TeamC Project/Logical Model Diagram.vsd'

Traceback (most recent call last):
  File "/usr/share/cherrytree/modules/core.py", line 3319, in image_handle
    pixbuf = gtk.gdk.pixbuf_new_from_file(filename)
GError: Couldn't recognize the image file format for file '/home/jeff/GDriveDocs/College/BSA375/TeamC Project/Logical Model Diagram.vsd'

Local variables in innermost frame:
self: <core.CherryTree instance at 0x22ded88>
args: (<gtk.Action object at 0x35bc140 (GtkAction at 0x33ea620)>,)
iter_insert: <GtkTextIter at 0x37c18f0>
filename: u'/home/jeff/GDriveDocs/College/BSA375/TeamC Project/Logical Model Diagram.vsd'

Comment 1 Jeff 2014-09-27 18:40:08 UTC
Created attachment 941841 [details]
File: backtrace

Comment 2 Jeff 2014-09-27 18:40:09 UTC
Created attachment 941842 [details]
File: environ

Comment 3 Giuseppe Penone 2014-09-28 07:59:32 UTC
this is fixed in upcoming 0.35.0

Comment 4 Jeff 2014-09-28 23:09:33 UTC
(In reply to Giuseppe Penone from comment #3)
> this is fixed in upcoming 0.35.0

Alright.  That is surprising, but looking forward to it.  I did find out  how to enter a file location for the Visio diagram.  That works fine as long as I upload the Visio file along with the Cherry Tree file and provide a proper link withn the Cherry Tree document.

Comment 5 Fedora Update System 2014-10-12 14:46:41 UTC
cherrytree-0.35.1-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/cherrytree-0.35.1-1.fc20

Comment 6 Fedora Update System 2014-10-14 04:34:06 UTC
Package cherrytree-0.35.1-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cherrytree-0.35.1-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-12769/cherrytree-0.35.1-1.fc20
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2014-10-22 08:51:33 UTC
cherrytree-0.35.1-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Jeff 2014-10-22 23:34:23 UTC
Thanks for your response.  I'm enjoying Cherry Tree and look forward to using the updated version.


Note You need to log in before you can comment on or make changes to this bug.