Bug 412828 - Color selector crashed the program
Summary: Color selector crashed the program
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Color Selectors (show other bugs)
Version: 4.2.6
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-10 19:41 UTC by nya.thecuteness.naomi
Modified: 2019-11-15 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kritacrash.log (24.32 KB, application/octet-stream)
2019-10-11 22:01 UTC, nya.thecuteness.naomi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nya.thecuteness.naomi 2019-10-10 19:41:54 UTC
Idk how or why the program simply stopped responding after it decided i clicked to select a color rather than reseting them to black and white and crashed the entire program, im assuming somehow the system overwhelmed itself with the most simple of functions. while im here the setup for the solor selector is disgustingly cluttered i liked it to be significantly more simplified like it used to be
Comment 1 Halla Rempt 2019-10-11 08:55:51 UTC
The configuration panel for the color selector hasn't changed in many years -- so I don't understand your "like it used to be".

Please try to find the kritacrash.log file in %APPDATA%\local and attach it to this bug; then we might be able to figure out what happened. Right now, your description does not provide enough information to try and debug the problem.
Comment 2 nya.thecuteness.naomi 2019-10-11 22:01:26 UTC
Created attachment 123147 [details]
kritacrash.log

I apologize for my ill informed critic, I was unaware that there were
multiple color sets that could be displayed and as a result when I updated
the program assumed it was altered upon seeing a different set of colors
than what i was used to. I discovered it shortly after the bug report so it
was a bit late to take back my comment.

Anyways I attached the kritacrash.log file you asked for and hope it
provides information that can make the program a bit more stable. I would
like to add that this is the only time its happened and couldve just been a
fluke caused by my laptop failing to execute the process properly

If it couldnt be told by my lack of knowledge on the program, Im fairly new
to it and still discovering things so please disregard any snarky comments
in my initial report

On Fri, Oct 11, 2019 at 3:55 AM Boudewijn Rempt <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=412828
>
> Boudewijn Rempt <boud@valdyas.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>              Status|REPORTED                    |NEEDSINFO
>                  CC|                            |boud@valdyas.org
>           Component|Tools/Colorize              |Color Selectors
>            Platform|Other                       |MS Windows
>
> --- Comment #1 from Boudewijn Rempt <boud@valdyas.org> ---
> The configuration panel for the color selector hasn't changed in many
> years --
> so I don't understand your "like it used to be".
>
> Please try to find the kritacrash.log file in %APPDATA%\local and attach
> it to
> this bug; then we might be able to figure out what happened. Right now,
> your
> description does not provide enough information to try and debug the
> problem.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Bug Janitor Service 2019-10-12 04:33:09 UTC
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.
Comment 4 Halla Rempt 2019-10-12 17:46:13 UTC
Hi,

This is actually a bug in Qt 5.12.4, and we updated the version of Qt for the 4.2.7 release, which should fix this issue. Could you please test the latest release?
Comment 5 Halla Rempt 2019-10-16 12:24:04 UTC
Setting to need info while waiting for confirmation.
Comment 6 Bug Janitor Service 2019-10-31 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2019-11-15 04:33:10 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!