Sorry about that.
Now when I try to make tuxpaint crash, apport ignores it because the
problem was already reported.
I found the original crashlog, and I attached it as a zip file.
** Attachment added: "old crash log"
http://launchpadlibrarian.net/28900488/_usr_bin_tuxpaint.1000.crash.zip
--
It hasn't though. This is the only bug you've submitted and it hasn't
been added to this.
You probably have to be logged into launchpad if you weren't.
--
tuxpaint crashes with no notification
https://bugs.launchpad.net/bugs/390424
You received this bug notification because you are a member of U
I just ran tuxpaint with apport running. The webpage that came up said the the
crashlog would be added automatically when I finished.
Thanks for all your help with this.
--
tuxpaint crashes with no notification
https://bugs.launchpad.net/bugs/390424
You received this bug notification because yo
I've sent it upstream but we need to work out how to get info we can
work with. I think we need to ask you to re-enable apport. The segfault
message itself doesn't tell us very much.
If you look at : https://wiki.kubuntu.org/Apport#Per-
package%2520Apport%2520Hooks
Could you try:
sudo force_star
** Bug watch added: SourceForge.net Tracker #2817073
http://sourceforge.net/support/tracker.php?aid=2817073
** Also affects: tuxpaint via
http://sourceforge.net/support/tracker.php?aid=2817073
Importance: Unknown
Status: Unknown
--
tuxpaint crashes with no notification
https://bu
