You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lazpaint: lazpaint 7.2.2_linux64.deb
OS: xUbuntu 22.04.1 (fresh install)
Mono: version 6.12.0.182 (tarball Tue Jun 14 22:35:00 UTC 2022) via official ppa
Lazpaint opens OK. I can open an image file and change the canvas size but after resampling the program crashes completely.
Opening app via terminal gives a error message that suggests it's a mono failure (hence the updated version) and sometimes I get a error file (json) too.
Same behaviour with standard version of mono and either 7.22 or 7.1.6 too.
`Gtk-Message: 08:14:59.115: Failed to load module "xapp-gtk3-module"
(lazpaint:450873): dbind-WARNING **: 08:14:59.120: Couldn't connect to accessibility bus: Failed to connect to socket /root/.cache/at-spi/bus_0.0: Permission denied
`
After crash:
One way would be to compile it yourself. Here's how.
Install Lazarus package.
Download the source code of LazPaint, for example from upstream: https://github.com/bgrabitmap/lazpaint-upstream
Then run Lazarus.
With all necessary packages (bgrabitmap, bgracontrols, lazpaintcontrols)
open using package menu and find LPK file
go into package options, go to link options and set optimization level 0, in debug options check generate debug info
Then open LazPaint project (lazpaint.lpi)
Choose build mode Debug (next to Play button there is a config button, click the dropdown arrow, then choose)
Then click the Play button
You should get LazPaint running. If an error occurs, it will stop and show the line causing the problem. You can also open the stack trace with menu View > Debug window
I've tried on a virtual machine with xUbuntu 22.04.1 and resampled an image without issue. Can you provide a sample image that I can try to resample and steps to reproduce the bug?
Breaking news ! it only happened on the Lazpaint Qt5 version. Sorry, I didn't even knows that there is two versions. The GTK2 version works fine for me, no crash, no exception at startup.
I suggest to put something about the two existing versions in the About window.
Activity
circular17 commentedon Aug 25, 2022
Hello!
LazPaint doesnβt use Mono so I donβt understand how that would be the issue.
Can you give more details on the error youβre getting and the exact steps to reproduce?
If you can, you can debug it with Lazarus (I can explain how to) to get more detailed information or I will do that.
vexillia commentedon Aug 25, 2022
On start from terminal:
`Gtk-Message: 08:14:59.115: Failed to load module "xapp-gtk3-module"
(lazpaint:450873): dbind-WARNING **: 08:14:59.120: Couldn't connect to accessibility bus: Failed to connect to socket /root/.cache/at-spi/bus_0.0: Permission denied
`
After crash:
[FORMS.PP] ExceptionOccurred Sender=EAccessViolation Exception=Access violation Stack trace: $0000000000000000 $000055E7A044E264 $000055E7A02521A8 $000055E7A0251E37 $000055E7A02525BE $000055E7A044DC33 $000055E7A0252514 [FORMS.PP] ExceptionOccurredHope that helps.
circular17 commentedon Aug 25, 2022
Hmmm that looks like an issue between the program and the widget set. I will try on a VM to fix it
zeroheure commentedon Sep 9, 2022
Similar behaviour here on Debian Sid (up to date).
How can I launch Lazpaint with debug options ?
circular17 commentedon Sep 10, 2022
One way would be to compile it yourself. Here's how.
Install Lazarus package.
Download the source code of LazPaint, for example from upstream:
https://github.com/bgrabitmap/lazpaint-upstream
Then run Lazarus.
With all necessary packages (bgrabitmap, bgracontrols, lazpaintcontrols)
Then open LazPaint project (lazpaint.lpi)
Choose build mode Debug (next to Play button there is a config button, click the dropdown arrow, then choose)
Then click the Play button
You should get LazPaint running. If an error occurs, it will stop and show the line causing the problem. You can also open the stack trace with menu View > Debug window
Otherwise I will try to provide debug binaries
circular17 commentedon Sep 10, 2022
Here are debug binaries:
https://github.com/bgrabitmap/lazpaint/releases/download/v7.2.2/lazpaint7.2.2_linux64_gtk2_debug.tar.gz
circular17 commentedon Oct 6, 2022
I've tried on a virtual machine with xUbuntu 22.04.1 and resampled an image without issue. Can you provide a sample image that I can try to resample and steps to reproduce the bug?
vexillia commentedon Oct 6, 2022
Not sure it's image specific: it happened with each and every image I tried. Here's one anyway ...
zeroheure commentedon Oct 6, 2022
I've just downloaded the debug binaries (sorry, I was unable to do it before), and tried but I can't reproduce the bug.
Here's what I've done ;
Or
With Debian Sid binaries, it crash, with your debug binaries, no crash (same image).
This can be related : when debian binary opens, the window below is shown.
zeroheure commentedon Oct 6, 2022
Breaking news ! it only happened on the Lazpaint Qt5 version. Sorry, I didn't even knows that there is two versions. The GTK2 version works fine for me, no crash, no exception at startup.
I suggest to put something about the two existing versions in the About window.
circular17 commentedon Oct 6, 2022
Thanks for the detailed answer. I understand we are not always available.
Xfce is kind of related to Gtk so it makes sense it would be more compatible. Though there may be some way to avoid the crash with Qt5.
Ok I was able to reproduce the two bugs with Qt5 version. It it related to timer events.
circular17 commentedon Oct 6, 2022
I found a way to avoid the bugs by removing the yellow popup about action progress. Here is a fixed version for Qt5 :
https://github.com/bgrabitmap/lazpaint/releases/download/v7.2.2/lazpaint7.2.2_linux64_qt5_bugfix.tar.gz
zeroheure commentedon Oct 7, 2022
Tested, everything ok
Thanks for the good job Johann !
circular17 commentedon Oct 7, 2022
You're very welcome
Thanks for helping me finding the bugs !