Created attachment 2111495 [details]
File: proc_pid_status

Created attachment 2111496 [details]
File: maps

Created attachment 2111497 [details]
File: limits

Created attachment 2111498 [details]
File: environ

Created attachment 2111499 [details]
File: open_fds

Created attachment 2111500 [details]
File: mountinfo

Created attachment 2111501 [details]
File: os_info

Created attachment 2111502 [details]
File: cpuinfo

Created attachment 2111503 [details]
File: runlevel

Created attachment 2111504 [details]
File: core_backtrace

Created attachment 2111505 [details]
File: exploitable

Created attachment 2111506 [details]
File: dso_list

Created attachment 2111507 [details]
File: var_log_messages

Created attachment 2111508 [details]
File: backtrace

When I invoke the file attached to https://bugzilla.mozilla.org/show_bug.cgi?id=1997776#c1, it causes Krita to frequently, but not 100% reproducibly, SEGV.


reporter:       libreport-2.17.15
type:           CCpp
reason:         krita killed by SIGSEGV
journald_cursor: s=a2d6d580caa24cf3a9483be7f85033e4;i=3ee77f;b=c014f4ba49924118bf4223f5b2e46a0b;m=72dc851f;t=64292cbe8fc64;x=3679b684ad98b35b
executable:     /usr/bin/krita
cmdline:        /usr/bin/krita
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-\x2fusr\x2fbin\x2fkrita
rootdir:        /
uid:            1000
kernel:         6.17.5-300.fc43.x86_64
package:        krita-5.2.11-2.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: _Py_Dealloc
comment:        When I invoke the file attached to https://bugzilla.mozilla.org/show_bug.cgi?id=1997776#c1, it causes Krita to frequently, but not 100% reproducibly, SEGV.

Created attachment 2111949 [details]
The Problematic File

As at https://bugzilla.redhat.com/show_bug.cgi?id=2411817#c13.

Created attachment 2111951 [details]
A Screencast That Demonstrates How To Reproduce This

As at https://bugzilla.redhat.com/show_bug.cgi?id=2411817#c14.

I attempted to open a file.


reporter:       libreport-2.17.15
type:           CCpp
reason:         krita killed by SIGSEGV
journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=d08c78;b=1e681fab903148e1867791abf31bfa83;m=21811a93a;t=6429f72acf16b;x=2a55ee94fd65a770
executable:     /usr/bin/krita
cmdline:        /usr/bin/krita
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-\x2fusr\x2fbin\x2fkrita
rootdir:        /
uid:            1000
kernel:         6.17.5-300.fc43.x86_64
package:        krita-5.2.11-2.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: _Py_Dealloc
comment:        I attempted to open a file.

oh hmm I didn't realize that what I was working on would also get attached to the bug report. I won't stop you and it's safe to open at work but just a fair bit of warning that I'm not entirely sure what's in there. just don't judge me for it and we'll be fine :P

(In reply to eblu from comment #19)

> oh hmm I didn't realize that what I was working on would also get attached
> to the bug report. I won't stop you and it's safe to open at work but just a
> fair bit of warning that I'm not entirely sure what's in there. just don't
> judge me for it and we'll be fine :P

Is it? I don't see it, but am not certain what to search for. If you didn't explicitly check a box in the GNOME Abrt wizard, that's probably worth filing at https://github.com/abrt/gnome-abrt/issues/new. In the meantime, https://discussion.fedoraproject.org/t/how-can-i-retroactively-make-a-red-hat-bug-private/154974/6 might be of use in future.

Since the past few updates, if I try to start Krita, it will usually crash half a second after the Krita welcome prompt appears.


reporter:       libreport-2.17.15
type:           CCpp
reason:         krita killed by SIGSEGV
journald_cursor: s=335228fac95448039323844ecb6b3504;i=743c2a;b=38998d0fc3e2464fb58bb6a666a85ccc;m=1e54654c8;t=642c521757961;x=1d46ebb461880b21
executable:     /usr/bin/krita
cmdline:        /usr/bin/krita
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-\x2fusr\x2fbin\x2fkrita
rootdir:        /
uid:            1000
kernel:         6.17.6-300.fc43.x86_64
package:        krita-5.2.11-2.fc43
runlevel:       /bin/sh: regel 1: runlevel: opdracht niet gevonden
backtrace_rating: 4
crash_function: _Py_Dealloc
comment:        Since the past few updates, if I try to start Krita, it will usually crash half a second after the Krita welcome prompt appears.

Just started it. It crashes immediately on start


reporter:       libreport-2.17.15
type:           CCpp
reason:         krita killed by SIGSEGV
journald_cursor: s=351cfd3a2bf04e7ebaf30f2c7d12e6e6;i=959449;b=79f8533c3943430bacbb5cf977697311;m=2a9676297;t=6430836985bf5;x=325b01f955fb389f
executable:     /usr/bin/krita
cmdline:        /usr/bin/krita
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-\x2fusr\x2fbin\x2fkrita
rootdir:        /
uid:            1000
kernel:         6.17.7-300.fc43.x86_64
package:        krita-5.2.11-2.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: _Py_Dealloc
comment:        Just started it. It crashes immediately on start

Tried to open Krita : (


reporter:       libreport-2.17.15
type:           CCpp
reason:         krita killed by SIGSEGV
journald_cursor: s=5a9313e7844e449daa6244ea4db0c4da;i=12a6903;b=b4db0fb85c4f4850af9ed34ff9a85010;m=2a4fe3439;t=64373b8064d5e;x=b027d0370b219783
executable:     /usr/bin/krita
cmdline:        /usr/bin/krita
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.kde.krita-18617.scope
rootdir:        /
uid:            1000
kernel:         6.17.7-300.fc43.x86_64
package:        krita-5.2.11-2.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: _Py_Dealloc
comment:        Tried to open Krita : (