Bug 426391 - Installing of global theme crash
Summary: Installing of global theme crash
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_lookandfeel (show other bugs)
Version: 5.19.2
Platform: FreeBSD Ports FreeBSD
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-09-11 00:32 UTC by Nathan
Modified: 2022-05-04 15:36 UTC (History)
3 users (show)

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


Attachments
New crash information added by DrKonqi (15.08 KB, text/plain)
2020-10-11 16:41 UTC, Peter G.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nathan 2020-09-11 00:32:32 UTC
Application: systemsettings5 (5.19.2)

Qt Version: 5.14.2
Frameworks Version: 5.71.0
Operating System: FreeBSD 12.1-RELEASE amd64
Windowing system: X11
Distribution (Platform): FreeBSD Ports

-- Information about the crash:
What I was doing when the application crashed:
I was in the process of installing a global theme in System settings

-- Backtrace:
Application: System Settings (systemsettings5), signal: Bus error

(lldb) process attach --pid 40048
(lldb) settings set term-width 200
(lldb) thread info
(lldb) bt all

Possible duplicates by query: bug 426388, bug 426289, bug 426202, bug 426114, bug 426090.

Reported using DrKonqi
Comment 1 Christoph Feck 2020-10-06 05:02:37 UTC
Could you please add the backtrace for the crash?
Comment 2 Peter G. 2020-10-11 16:41:12 UTC
Created attachment 132278 [details]
New crash information added by DrKonqi

systemsettings5 (5.18.5) using Qt 5.12.7

- What I was doing when the application crashed:

Installing a new Global Theme while in "Get New Global Themes".

-- Backtrace (Reduced):
Comment 3 Christoph Feck 2020-10-21 20:25:30 UTC
Probably needs a valgrind log. Crash is in freeing thread memory.
Comment 4 Nate Graham 2021-01-05 19:26:07 UTC
Thread 20 (Thread 0x7f5db4adf700 (LWP 2757)):
[KCrash Handler]
#4  0x00007f5e2ea96520 in raise () at /lib64/libc.so.6
#5  0x00007f5e2ea97b01 in abort () at /lib64/libc.so.6
#6  0x00007f5e2ead9957 in __libc_message () at /lib64/libc.so.6
#7  0x00007f5e2eae0173 in malloc_printerr () at /lib64/libc.so.6
#8  0x00007f5e2eae1a79 in _int_free () at /lib64/libc.so.6
#9  0x00007f5e2ebc6fab in tcache_thread_freeres () at /lib64/libc.so.6
#10 0x00007f5e2ebc7002 in __libc_thread_freeres () at /lib64/libc.so.6
#11 0x00007f5e2a82151e in start_thread () at /lib64/libpthread.so.0
#12 0x00007f5e2eb58fbf in clone () at /lib64/libc.so.6
Comment 5 Nate Graham 2022-04-19 15:46:54 UTC
A lot has changed since Plasma 5.19; can you try again with Plasma 5.24?
Comment 6 Bug Janitor Service 2022-05-04 04:35:13 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 Peter G. 2022-05-04 15:24:47 UTC
(In reply to Nate Graham from comment #5)
> A lot has changed since Plasma 5.19; can you try again with Plasma 5.24?

I don't exactly remember what computer I ran it on, but as far as I recall it was a 32-bit box. I tried it again on that computer. I have not seen it crash. It is very slow, but hasn't crashed yet. 

(In reply to Nate Graham from comment #5)
Comment 8 Nate Graham 2022-05-04 15:36:15 UTC
OK, thanks!