Bug 33343

Summary: drakconf crashed
Product: Mageia Reporter: Markus Ernst Nicolussi Paolaz <mcwimpy>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: fri, lewyssmith, lovaren
Version: 9   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: drakconf-13.29-1.1.mga9 CVE:
Status comment:

Description Markus Ernst Nicolussi Paolaz 2024-07-01 03:44:59 CEST
The "drakconf" program crashed. Drakbug-18.65 caught it.

ending the program with key combo ALT+F4 or started the program

you must be root to run this program at /usr/lib/libDrakX/common.pm line 596.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/libDrakX/common.pm:596
common::require_root_capability() called from /usr/libexec/drakconf:72

Theme name: Breeze
Kernel version = 6.6.33-desktop-1.mga9
Distribution=Mageia release 9 (Official) for x86_64
CPU=AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx
Comment 1 Markus Ernst Nicolussi Paolaz 2024-07-01 03:45:14 CEST
it's happening all the time currently... i could submit countless bugreports like this, but i guess they are all the same. in case not, i submit 2 more. all good things are 3 they say where i come from.
love from Vienna <3
Comment 2 Kristoffer Grundström 2024-07-01 04:38:45 CEST
Does it also happen with a new user?

CC: (none) => lovaren

Comment 3 Morgan Leijström 2024-07-01 08:31:06 CEST
Do you know after which update the problem appeared?

If you start it as root, or using sudo, do you still see same problem?

Are you using many packages from testing repos?
Kernel version = 6.6.33 is not to be released.
In testing we currently have to 6.6.34-2.
6.6.28 is last official update.

Do the problem go away if you downgrade/sync to released updates
https://wiki.mageia.org/en/Using_DNF#Synchronize_with_repos

CC: (none) => fri

Comment 4 Morgan Leijström 2024-07-01 08:32:09 CEST
*** Bug 33342 has been marked as a duplicate of this bug. ***
Comment 5 Morgan Leijström 2024-07-01 08:32:20 CEST
*** Bug 33341 has been marked as a duplicate of this bug. ***
Comment 6 Morgan Leijström 2024-07-01 09:11:21 CEST
(In reply to Morgan Leijström from comment #3)
> In testing we currently have to 6.6.34-2.
I meant 6.6.36-2
Comment 7 Lewis Smith 2024-07-05 21:02:42 CEST
We have many bugs with the same title, but they are essentially one-off.
This one is the first which is repetetive.
(In reply to Markus Ernst Nicolussi Paolaz from comment #1)
> it's happening all the time currently... i could submit countless bugreports
> like this, but i guess they are all the same. in case not, i submit 2 more.
> all good things are 3 they say where i come from.
> love from Vienna
Please do not submit more identical bugs!

It is true that the current released kernel is 6.6.28, so it is just to ask that Markus uses that.
Also, please say exactly what you are doing which causes the crash.

> love from Vienna
Wien I know! Nice to know we have a user there.

CC: (none) => lewyssmith

Comment 8 Markus Ernst Nicolussi Paolaz 2024-07-06 01:34:28 CEST
you have many users here lol, i'm just the most crazy of them all :-P

ok i read what you said. it is logical too me. i will do as you requested,
but give me a day or two, it's currently very busy here.

love from Vienna <3
Comment 9 Markus Ernst Nicolussi Paolaz 2024-07-06 01:36:27 CEST
just real quick: i was using the request linux, just installed kernel 6.6.36-3 from the testing repo, and will conduct tests with that. all tests you requested.
Comment 10 Markus Ernst Nicolussi Paolaz 2024-07-06 01:40:56 CEST
(In reply to Morgan Leijström from comment #6)
> (In reply to Morgan Leijström from comment #3)
> > In testing we currently have to 6.6.34-2.
> I meant 6.6.36-2
just real quick: i was using the request linux 6.6.36-2, just installed kernel 6.6.36-3 from the testing repo, and will conduct tests with that. all tests you requested.
Comment 11 Markus Ernst Nicolussi Paolaz 2024-07-06 01:43:21 CEST
i will test with new user,
i will test with stable kernel.
i will test after downgrade/sync to released updates
https://wiki.mageia.org/en/Using_DNF#Synchronize_with_repos
(and no more duplicates, understood.)
Comment 12 sturmvogel 2024-07-06 07:53:49 CEST
And please don‘t forget to provide the basic informations which are necessary to reproduce such an issue:
- desktop environment in use
- how do you try to open MCC? Via command line? Which command? Which application icon from where?…
- which module in MCC do you use when the crash occures?
Comment 13 sturmvogel 2024-07-06 07:54:57 CEST
- what happens when you close the module/MCC via the designed and intented way via closing button or the x button?
Comment 14 Markus Ernst Nicolussi Paolaz 2024-07-14 19:39:58 CEST
hey guys i really wanted to do all the testing but then some operating systems didn't boot any more and after fixing that and updating mageia also, the problem did not ever occur again. i think whatever it was, it must have been due to an interims state, that has gone now, which i had because I was using testing packages. so i believe this is fixed and the bug report can be marked solved.

kindest regards
M.E.N.P.

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 15 Morgan Leijström 2024-07-14 20:54:47 CEST
Thank you for updating us on the subject.