Description of problem: since the last updates, when typing the command "grub-customizer" in a terminal, the process normally begins, and just before he is completed, the grub-customizer windows closes [root@mag6 alain4]# LANGUAGE=C grub-customizer Error creating proxy: The connection is closed (g-io-error-quark, 18) Error creating proxy: The connection is closed (g-io-error-quark, 18) Error creating proxy: The connection is closed (g-io-error-quark, 18) Error creating proxy: The connection is closed (g-io-error-quark, 18) *** initializing (w/o specified bootloader type)… * reading partition info… * Loading Framebuffer resolutions (background process) * Finding out if this is a live CD *** initializing (w/ specified bootloader type)… * Checking if the config directory is clean *** loading configuration *** loading - preserveConfig: no * unsetting saved config *** loading settings *** loading grub list * loading scripts… * loading proxies… * cleaning up proxy configuration… * creating proxifiedScript links & chmodding other files… * running grub2-mkconfig * restoring grub configuration * removing invalid proxies from list * loading completed *** grub list completely loaded *** loading saved grub list Erreur de segmentation (core dumped) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
after rebooting this bug has disappeared as mysteriously it appeared!
(In reply to peter lawford from comment #1) > after rebooting this bug has disappeared as mysteriously it appeared! Thanks for the feedback. Setting to unconfirmed, if it doesn't happen again to you or doesn't hit anyone else, we can close this report a few weeks from now.
Status: NEW => UNCONFIRMEDCC: (none) => marja11Ever confirmed: 1 => 0
(In reply to Marja Van Waes from comment #2) > (In reply to peter lawford from comment #1) > > after rebooting this bug has disappeared as mysteriously it appeared! > > Thanks for the feedback. Setting to unconfirmed, if it doesn't happen again > to you or doesn't hit anyone else, we can close this report a few weeks from > now. I am really sorry, but this bug again appears; even after rebooting, it subsists; impossible to open grub-customizer; this bug is closed to bug #22681
I retried to open grub-customizer with no application (as mozilla-firefox or thunderbird) opened, but the bug subsists; and I NEED GRUB-CUSTOMIZER
here attached return of the command: [alain4@mag6 ~]$ sudo strace $(which grub-customizer) on the other hand command coredumpctl returns nothing: [root@mag6 alain4]# coredumpctl No coredumps found.
Created attachment 10230 [details] sudo return of strace $(which grub-customizer)
in the attached document 10230, I wished to say: return of sudo strace $(which grub-customizer) here the return of dmesg: [alain4@mag6 ~]$ dmesg |grep grub-customizer [ 437.153782] grub-customizer[29261]: segfault at 25 ip 0000000000478942 sp 00007fcf09f6b500 error 4 in grub-customizer[400000+150000] [ 437.153874] audit: type=1701 audit(1528547387.084:180): auid=500 uid=0 gid=0 ses=3 pid=29230 comm="grub-customizer" exe="/usr/bin/grub-customizer" sig=11 res=1 [ 649.339430] grub-customizer[17183]: segfault at 25 ip 0000000000478942 sp 00007f730d2e6500 error 4 in grub-customizer[400000+150000] [ 649.339503] audit: type=1701 audit(1528547599.265:188): auid=500 uid=0 gid=0 ses=3 pid=14971 comm="grub-customizer" exe="/usr/bin/grub-customizer" sig=11 res=1 [alain4@mag6 ~]$
I have uninstalled and reinstalled grub-customizer, rebooted the system, and the bug persists
Thanks for the feedback, Peter. Assigning to all packagers collectively, since there is no registered maintainer for this package. CC'ing some committers.
Assignee: bugsquad => pkg-bugsEver confirmed: 0 => 1Status: UNCONFIRMED => NEWCC: (none) => cjw, geiger.david68210, shlomif, smelror, tarakbumba, zen25000
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 6's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Best regards, Aurélien Bugsquad Team
CC: (none) => ouaurelienResolution: (none) => OLDStatus: NEW => RESOLVED