Bug 562332 - Inkscape crashed when the create and edit text tool is tried to use it.
Summary: Inkscape crashed when the create and edit text tool is tried to use it.
Keywords:
Status: CLOSED DUPLICATE of bug 546179
Alias: None
Product: Fedora
Classification: Fedora
Component: inkscape
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-06 00:19 UTC by Yader Velásquez
Modified: 2010-02-08 00:04 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-08 00:04:46 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Yader Velásquez 2010-02-06 00:19:07 UTC 
Description of problem:

Inkscape show a window with the menssage about a internal error, when create and edit text tool is selected and tried to use it.

Version-Release number of selected component (if applicable):
Inkscape 0.47 r22583 (Nov 30 2009)

How reproducible:

Try to write something in inkscape.
 
Steps to Reproduce:
1.Selec the tool for create and edit text.
2.Click over the zone that you want to write.
3.
  
Actual results:
Inkscape show a window saying "A internal error has been found". Without any other details.

Expected results:
Be able to create and edit text in Inkscape :)

Additional info:
Comment 1 Máirín Duffy 2010-02-08 00:04:46 UTC 
Hi Yader,

Thanks for the bug report!

That is actually an old bug. Can you please upgrade to the latest version of Inkscape? It should be fixed in the latest version that has been available for some months now. The latest version in the Fedora repos is:

inkscape-0.47-1.fc12 (1 Dec 2009)

In the future, you should always try upgrading to the latest before reporting a bug. You can do this by running the following command as root:

yum update inkscape -y

Alternatively, you may use the software update tool available by selecting the System > Administration > Software Updates menu item - you will need an administrative password for your machine for this as well.

Thanks,
~m

*** This bug has been marked as a duplicate of bug 546179 ***
Note You need to log in before you can comment on or make changes to this bug.