Bug 429724 - palapeli crash on saved puzzle load
Summary: palapeli crash on saved puzzle load
Status: RESOLVED WORKSFORME
Alias: None
Product: palapeli
Classification: Applications
Component: general (show other bugs)
Version: 2.1.200380
Platform: Debian stable Linux
: NOR critical
Target Milestone: ---
Assignee: Stefan Majewsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-27 15:16 UTC by jraviotta
Modified: 2020-11-29 18:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
attachment-16669-0.html (1.80 KB, text/html)
2020-11-28 01:12 UTC, jraviotta 		Details
attachment-30106-0.html (1.75 KB, text/html)
2020-11-29 13:49 UTC, jraviotta 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description jraviotta 2020-11-27 15:16:22 UTC 
SUMMARY
Palapeli crashes on re-opening custom puzzle.

STEPS TO REPRODUCE
1. Create a new puzzle from image
2. open puzzle
3. close palapeli
4. open palapeli
5. open saved puzzle

OBSERVED RESULT
On 1st open error message about having active trays before trying to move pieces appears without trying to move pieces
Crash

EXPECTED RESULT
no crash

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION
Comment 1 Albert Astals Cid 2020-11-28 01:00:43 UTC 
works fine here.

Can you reproduce it all the time?
Comment 2 jraviotta 2020-11-28 01:12:31 UTC 
Created attachment 133694 [details]
attachment-16669-0.html

seems to be a bug with custom mouse settings. I reset to default and now it
doesn't crash.

Jonathan Raviotta


On Fri, Nov 27, 2020 at 8:00 PM Albert Astals Cid <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=429724
>
> Albert Astals Cid <aacid@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |aacid@kde.org
>              Status|REPORTED                    |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
>
> --- Comment #1 from Albert Astals Cid <aacid@kde.org> ---
> works fine here.
>
> Can you reproduce it all the time?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Albert Astals Cid 2020-11-28 01:19:46 UTC 
Would you be able to go back to your crashy settings so we can try to reproduce the crash and potentially fix it?
Comment 4 jraviotta 2020-11-29 13:49:03 UTC 
Created attachment 133728 [details]
attachment-30106-0.html

Sorry, I can't reproduce my settings that caused the problem. Are there any
logs I can provide?

I suppose you can close this bug and I'll open another if the problem
recurs.

Thanks for your prompt response.

Jonathan Raviotta


On Fri, Nov 27, 2020 at 8:19 PM Albert Astals Cid <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=429724
>
> --- Comment #3 from Albert Astals Cid <aacid@kde.org> ---
> Would you be able to go back to your crashy settings so we can try to
> reproduce
> the crash and potentially fix it?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 5 Albert Astals Cid 2020-11-29 18:11:36 UTC 
Yes please come back to us if you're able to reproduce the crash.