Pinta

Bug #1478378
Comment #3

Comment 3 for bug 1478378

Revision history for this message

Rick Hayford (rickbarb) wrote on 2015-07-29: Re: [Bug 1478378] Re: Can't save work - unhandled exception: exception has been thrown by the target of an invocation

grofaty,

Thank you for taking the time to contact me in regard to the problem I
encountered with Pinta

1.6. I have a few thoughts I'd like to share with you, and will do so
trying to respect your time

by being as brief as possible.

First off, I got into computers back in the early 1980's, and have over
the years worked with

systems running CPM, various Apple OS's, and Windows. Some time in the
mid to late 1990's I

became aware of Linux, and though I really wanted to explore it, I
simply didn't have the time.

Three weeks ago I decided enough was enough -- it was time to learn
Linux by making it my

day-to-day OS; I bought a refurbished Dell desktop, downloaded and
installed Linux Mint 17.2,

and am trying my best not to turn on my Windows machine for anything.
I'm telling you this

because much of what I do with computers has to do with graphics, so to
stay immersed in

Linux and not go back to Windows, I need for Pinta to work. At the same
time, I am at best a

novice newbie when it comes to Linux, which will unfortunately limit my
ability to try things

you might suggest, or provide you to details about the interaction of
the OS and the software.

Once I had Mint installed and configured, the first thing I did was use
the Synaptic Package

Manager to install Pinta -- since I do a lot of pixel level work, I
chose Pinta because it's a nice

equivalent to the Windows paint program named Paint-dot-Net. I have to
tell you, though,

that I was surprised that the version of Pinta that was downloaded and
installed by the

Synaptic Package Manager came with no Curved Line tool; an absolute must
for me. As a

result, I went to the Pinta home page to find out if there was some
documentation on a way to

force the program to draw curved lines (apart from circles and ovals);
what I found was the

announcement of the release of Pinta 1.6, featuring (among other things)
the Curved Line tool.

I immediately used the Synaptic Package Manager to uninstall Pinta 1.3,
then used the

Terminal commands (apt-get) detailed on the Pinta website to download
and install Pinta 1.6.

Pinta 1.6 is perfect for what I need to do, if it can just get past the
save issue.

The bug that I reported on July 26th was in fact its second occurance
for me. The day before

(July 25th) I had been working in Pinta for about four hours when it
first occured -- when I

clicked the button to report the bug I was expecting what often occurs
in Windows;

specifically, that the bug report would be sent automatically, whereas I
was unexpectedly

taken to a website that was a series of bug reports. At that point I
did not notice the button in

the upper corner that I needed to click to enter my bug report, so that
initial encounter went

unreported -- when the problem came up the second time (July 26th), I
studied the website a

little more closely, because I wanted to report the bug, which will
hopefully lead to a solution

so I can continue my use of Linux and not have to go back to Windows (I
don't dislike

Windows, I just want to learn Linux).

Anyway, let me explain to you what I was doing both times when the
unhandled exception

came up -- hopefully this will give you some clue as to the cause. I
was creating a masthead

(banner) for a newsletter (the masthead is primarily graphical, and will
occupy most of the

first page, so it's fairly large) -- to create it, I purchased several
pieces of clipart, all of which

require editing before I can combine them together to become the new
masthead. During the

creative process, I delete unneeded portions of each graphic, draw new
parts, manually add

anti-aliasing to new lines, resize, rotate, and flip images, copy,
paste, and rearrange the location

of images, and probably do a few other things, such change colors of
image parts, and add text.

Specifically, what I was doing both days just before the exception
errors occurred was using

the Rectangle Selection tool and the Lasso Selection tool to remove
unwanted parts of the clip

art images, Bucket filling in the areas where the removed parts had
been, and then using the

Pencil or Brush tool at the pixel level to color over the remaining
dashed boundary lines of the

selection tools. I don't recall in the past that much (if any) of the
selection tool boundary lines

remaining on screen after Bucket filling the area where the removed
parts had been, but it

seemed that the longer I worked in Pinta, the more of the boundary lines
that remained and

had to be colored over manually; nonetheless, I still received no
exception error messages

until the moment I tried to save my work.

I'm sorry this ended up being so long, but if it enables you to solve
the problem and allows me

to continue using and learning Linux, it was worth it to me.

------ Original Message ------
From: "grofaty" <email address hidden>
To: <email address hidden>
Sent: 7/27/2015 12:16:23 PM
Subject: [Bug 1478378] Re: Can't save work - unhandled exception:
exception has been thrown by the target of an invocation

>@Rick, I have encountering several this "can't save work" problems in
>resent years in several Pinta releases, but it was never (in my case at
>least) a problem in "save" operation itself, but in some other problem
>(bug) happening at least one action before save. I always got some
>exception error and then when save was performed it couldn't be done,
>because of the exception happening before it. I assume this is the same
>in you case.
>
>It would be nice if you could figure it out what are the exact steps
>that triggered exception and then fail of save after. That would really
>help to debug and fix a problem.
>
>I also suggest to download latest development version (currently pretty
>stable - fixed some v1.6 bugs, maybe your problem arelady fixed). If
>using Windows download file under "Windows" button and if using Linux
>or
>OS-X then download "Zip" file extract it and run it using command: mono
>Pinta.exe.
>
>P.S. You have made a correct decision and open a new bug, because both
>bugs in your posts are marked fixed and fix of specific "save" problems
>were already released. So you problem is most probably a new problem.
>
>--
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1478378
>
>Title:
> Can't save work - unhandled exception: exception has been thrown by
> the target of an invocation
>
>Status in Pinta:
> New
>
>Bug description:
> July 26, 2015 - This appears to be the same bug reported in 2010 as #
> 603458 and in 2012 as # 704265. My reason for reporting it as a
>"NEW"
> bug is because it is now a few years later and it's showing up in the
> latest version of Pinta (version 1.6). The only thing that is
> different this time from the two previous reports and fixes is that
>it
> occurs after I've been working for a couple of hours or more and have
> saved my work multiple times already (with the other occurrences, the
> problem seemed to happen by the second (or so) save ( in order words,
> previously it was happening early on).
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/pinta/+bug/1478378/+subscriptions
>

grofaty,

Thank you for taking the time to contact me in regard to the problem I 
encountered with Pinta

1.6.  I have a few thoughts I'd like to share with you, and will do so 
trying to respect your time

by being as brief as possible.

First off, I got into computers back in the early 1980's, and have over 
the years worked with

systems running CPM, various Apple OS's, and Windows.  Some time in the 
mid to late 1990's I

became aware of Linux, and though I really wanted to explore it, I 
simply didn't have the time.

Three weeks ago I decided enough was enough -- it was time to learn 
Linux by making it my

day-to-day OS; I bought a refurbished Dell desktop, downloaded and 
installed Linux Mint 17.2,

and am trying my best not to turn on my Windows machine for anything.  
I'm telling you this

because much of what I do with computers has to do with graphics, so to 
stay immersed in

Linux and not go back to Windows, I need for Pinta to work.  At the same 
time, I am at best a

novice newbie when it comes to Linux, which will unfortunately limit my 
ability to try things

you might suggest, or provide you to details about the interaction of 
the OS and the software.

Once I had Mint installed and configured, the first thing I did was use 
the Synaptic Package

Manager to install Pinta -- since I do a lot of pixel level work, I 
chose Pinta because it's a nice

equivalent to the Windows paint program named Paint-dot-Net.  I have to 
tell you, though,

that I was surprised that the version of Pinta that was  downloaded and 
installed by the

Synaptic Package Manager came with no Curved Line tool; an absolute must 
for me.  As a

result, I went to the Pinta home page to find out if there was some 
documentation on a way to

force the program to draw curved lines (apart from circles and ovals); 
what I found was the

announcement of the release of Pinta 1.6, featuring (among other things) 
the Curved Line tool.

I immediately used the Synaptic Package Manager to uninstall Pinta 1.3, 
then used the

Terminal commands (apt-get) detailed on the Pinta website to download 
and install  Pinta 1.6.

Pinta 1.6 is perfect for what I need to do, if it can just get past the 
save issue.

The bug that I reported on July 26th was in fact its second occurance 
for me.  The day before

(July 25th) I had been working in Pinta for about four hours when it 
first occured -- when I

clicked the button to report the bug I was expecting what often occurs 
in Windows;

specifically, that the bug report would be sent automatically, whereas I 
was unexpectedly

taken to a website that was a series of bug reports.  At that point I 
did not notice the button in

the upper corner that I needed to click to enter my bug report, so that 
initial encounter went

unreported -- when the problem came up the second time (July 26th), I 
studied the website a

little more  closely, because I wanted to report the bug, which will 
hopefully lead to a solution

so I can continue my use of Linux and not have to go back to Windows (I 
don't dislike

Windows, I just want to learn Linux).

Anyway, let me explain to you what I was doing both times when the 
unhandled exception

came up -- hopefully this will give you some clue as to the cause.  I 
was creating a masthead

(banner) for a newsletter (the masthead is primarily graphical, and will 
occupy most of the

first page, so it's fairly large) -- to create it, I purchased several 
pieces of clipart, all of which

require editing before I can combine them together to become the new 
masthead.  During the

creative process, I delete unneeded portions of each graphic, draw new 
parts, manually add

anti-aliasing to new lines, resize, rotate, and flip images, copy, 
paste, and rearrange the location

of images, and probably do a few other things, such change colors of 
image parts, and add text.

Specifically, what I was doing both days just before the exception 
errors occurred was using

the Rectangle Selection tool and the Lasso Selection tool to remove 
unwanted parts of the clip

art images, Bucket filling in the areas where the removed parts had 
been, and then using the

Pencil or Brush tool at the pixel level to color over the remaining 
dashed boundary lines of the

selection tools.  I don't recall in the past that much (if any) of the 
selection tool boundary lines

remaining on screen after Bucket filling the area where the removed 
parts had been, but it

seemed that the longer I worked in Pinta, the more of the boundary lines 
that remained and

had to be colored over manually; nonetheless, I still received no 
exception error messages

until the moment I tried to save my work.

I'm sorry this ended up being so long, but if it enables you to solve 
the problem and allows me

to continue using and learning Linux, it was worth it to me.

------ Original Message ------
From: "grofaty" <1478378@bugs.launchpad.net>
To: rickbarb@cox.net
Sent: 7/27/2015 12:16:23 PM
Subject: [Bug 1478378] Re: Can't save work - unhandled exception: 
exception has been thrown by the target of an invocation

>@Rick, I have encountering several this "can't save work" problems in
>resent years in several Pinta releases, but it was never (in my case at
>least) a problem in "save" operation itself, but in some other problem
>(bug) happening at least one action before save. I always got some
>exception error and then when save was performed it couldn't be done,
>because of the exception happening before it. I assume this is the same
>in you case.
>
>It would be nice if you could figure it out what are the exact steps
>that triggered exception and then fail of save after. That would really
>help to debug and fix a problem.
>
>I also suggest to download latest development version (currently pretty
>stable - fixed some v1.6 bugs, maybe your problem arelady fixed). If
>using Windows download file under "Windows" button and if using Linux 
>or
>OS-X then download "Zip" file extract it and run it using command: mono
>Pinta.exe.
>
>P.S. You have made a correct decision and open a new bug, because both
>bugs in your posts are marked fixed and fix of specific "save" problems
>were already released. So you problem is most probably a new problem.
>
>--
>You received this bug notification because you are subscribed to the 
>bug
>report.
>https://bugs.launchpad.net/bugs/1478378
>
>Title:
>   Can't save work - unhandled exception: exception has been thrown by
>   the target of an invocation
>
>Status in Pinta:
>   New
>
>Bug description:
>   July 26, 2015 - This appears to be the same bug reported in 2010 as #
>   603458 and in 2012 as # 704265.  My reason for reporting it as a 
>"NEW"
>   bug is because it is now a few years later and it's showing up in the
>   latest version of Pinta (version 1.6).  The only thing that is
>   different this time from the two previous reports and fixes is that 
>it
>   occurs after I've been working for a couple of hours or more and have
>   saved my work multiple times already (with the other occurrences, the
>   problem seemed to happen by the second (or so) save ( in order words,
>   previously it was happening early on).
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/pinta/+bug/1478378/+subscriptions
>