https://bugs.kde.org/show_bug.cgi?id=481192
Dominic changed:
What|Removed |Added
Resolution|BACKTRACE |FIXED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=481192
--- Comment #14 from Bug Janitor Service ---
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
https://bugs.kde.org/show_bug.cgi?id=481192
Nate Graham changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=481192
Dominic changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=481192
fanzhuyi...@gmail.com changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=481192
--- Comment #11 from Dominic ---
(In reply to fanzhuyifan from comment #10)
> For the original reporter -- which Qt version are you using? Is this also
> fixed for you on Qt 6.6.2?
Yes it is, I haven't had any crashes on any of the modules, it's
https://bugs.kde.org/show_bug.cgi?id=481192
fanzhuyi...@gmail.com changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=481192
--- Comment #9 from Jure Repinc ---
I just did a regular morning update of packages and the problem appears to be
fixed. All mentioned KCMs open now. During the update Qt was updated to version
6.6.2 so maybe that version has a fix for this problem.
https://bugs.kde.org/show_bug.cgi?id=481192
--- Comment #8 from Dominic ---
I know it's insecure and a bad practice but I ran kdesu systemsettings and was
able to enter the modules that are broken. Could it be a plasmoid or
colorscheme is causing things to break?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=481192
--- Comment #7 from Dominic ---
(In reply to Nate Graham from comment #3)
> To the Arch people. But if you do want to continue here, we need a backtrace
> of the crash. See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
>
https://bugs.kde.org/show_bug.cgi?id=481192
Nate Graham changed:
What|Removed |Added
Resolution|BACKTRACE |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=481192
--- Comment #5 from Jure Repinc ---
Hi this is my backtrace from running "gdb --args systemsettings kcm_pulseaudio"
since KDE crash handler does not catch this crash:
[New Thread 0x724006c0 (LWP 18127)]
[New Thread 0x714006c0 (LWP 18128)]
https://bugs.kde.org/show_bug.cgi?id=481192
--- Comment #4 from fanzhuyi...@gmail.com ---
(In reply to Nate Graham from comment #3)
> To the Arch people. But if you do want to continue here, we need a backtrace
> of the crash. See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
>
https://bugs.kde.org/show_bug.cgi?id=481192
Nate Graham changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=481192
Jure Repinc changed:
What|Removed |Added
CC||j...@holodeck1.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=481192
--- Comment #2 from Dominic ---
(In reply to fanzhuyifan from comment #1)
> Can't reproduce on Arch source build of git master. Perhaps this is a
> packaging issue?
Thanks for testing, it might a packaging issue, where do I go to report it?
--
You
https://bugs.kde.org/show_bug.cgi?id=481192
fanzhuyi...@gmail.com changed:
What|Removed |Added
CC||fanzhuyi...@gmail.com
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=481192
Dominic changed:
What|Removed |Added
CC||dominicglus...@gmail.com
--
You are receiving this
18 matches
Mail list logo
