xpaint crashes due to stack smashing on Vivid Vervet and Xenial Xerus Beta2

Bug #1440115 reported by JMB
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xpaint (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

xpaint crashes when trying to move a selected region (by 15. icon, i.e. rectangular region selection).
This only happens on Vivid Vervet (Beta 2) - 14.04 LTS works in that respect.
It happened on two systems with different resolution (UHD = 4k: 3860× 2160 and WQHD: 2560× 1440).
Any image (using GIFs in any size) can be used to see the error - so reproducing it under Vivid should
be an easy task.

I could not find a similar report for xpaint - but one concerning lshw:
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1389589
seems to be similar (stack smashing detected) and also concerns Vivid.

Could it be that something in Vivid has unintentionally changed so that some programs react with
"stack smashing" error messages and if so could this be security related?

Anyway - I am using xpaint a lot and already use Vivid as main OS replacing Trusty.
So any information, workaround or - in the best case - bugfix would be highly appreciated.

Best wishes,

JMB

P.S.: Vivid Vervet was newly installed with freshly released Xubuntu Beta2 amd64.
  I did not try it but I would be astonished if XFCE flavor has anything to say in that matter,
  so it probably is a general Ubuntu 15.04 (Vivid Vervet) problem.

P.P.S.: As far as I can tell Vivid better is much more stable an mature than 14.04 LTS ever was
  which caused many problem and workarounds - and HWE is a mess with crashing X servers
  on my Intel graphic chipset system ... this is the only bug (besides the hang after installation)
  which I encountered - which makes it my person best experience with any Ubuntu release!
  So thanks to the developers for their good job!

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xpaint 2.9.1.4-3.1
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Apr 3 17:38:45 2015
InstallationDate: Installed on 2015-03-27 (7 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
SourcePackage: xpaint
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
JMB (jmb-tux) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xpaint (Ubuntu):
status: New → Confirmed
Changed in xpaint (Ubuntu):
importance: Undecided → Medium
JMB (jmb-tux)
tags: added: xenial
JMB (jmb-tux)
summary: - xpaint crashes due to stack smashing on Vivid Vervet Beta
+ xpaint crashes due to stack smashing on Vivid Vervet and Xenial Xerus
+ Beta2
Revision history for this message
JMB (jmb-tux) wrote :

It seems that nothing has changed in nearly a year.
The bug lived within Werewolf ... and further.

With the upcoming LTS (16.04 Xenial Xerus Beta2 - up do date as I write this comment)
the same xpaint version 2.9.1.4-3.1 (AMD64) is included with the same bug:
crashing when trying to move a selected region.

Is this reported or even visible to upstream (Debian or devoloper)?
How can one get further information?
Is there anything one can do to improve this situation - as a bug report
seems to have no effect?

Best wishes,

JMB

Revision history for this message
JMB (jmb-tux) wrote :

The bug is living in Yakkety Yak (Xubuntu 16.10) as tested right now ...
same error messages when selecting a region and trying to move it:
   *** stack smashing detected ***: xpaint terminated
   Aborted (core dumped)
It's a pitty that there seems to be no one responsible/able to fix the error.
I am still willing to help ...

Revision history for this message
JMB (jmb-tux) wrote :

The bug is - no wonder - still present in Zesty Zapus going final tomorrow.
Unfortunately there seems to be not much interest in xpaint.
For most of the tasks I now use kolourpaint - no gif support, worse handling ...
so if someone may be intersted in fixing it, I would like to help testing patched
version ... just in case ...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.