can't call method "attron" on an undefined value at Curses/UI/Checkbox.pm line 221 drakbug::bug_handler() called from interactive/curses.pm:557 interactive::curses::ask_fromW_() called from interactive/curses.pm:495 interactive::curses::ask_fromW() called from interactive.pm:658 interactive::ask_from_real() called from interactive.pm:646 interactive::ask_from_() called from Xconfig/main.pm:152 Xconfig::main::configure_choose_raw() called from Xconfig/main.pm:165 Xconfig::main::configure_chooser() called from Xconfig/main.pm:192 Xconfig::main::configure_everything_or_configure_chooser() called from drakx11::48 Reproducible: Steps to Reproduce:
I was reconfiguring Xorg after switching from QXL to Cirrus for video
Summary: XFdrake crashed (can't call method "attron" on an undefined value at Curses/UI/Checkbox.pm line 221Ã => XFdrake crashed (can't call method "attron" on an undefined value at Curses/UI/Checkbox.pm line 221)
Source RPM: drakx-kbd-mouse-x11 => drakx-kbd-mouse-x11, perl-Curses-UICC: (none) => pterjan
Whiteboard: (none) => MGA5TOO
Assignee: bugsquad => mageiatoolsCC: (none) => marja11
Created attachment 13941 [details] Screenshot of drakx11 crashing in console, runlevel 3 Screenshot of drakx11 crashing in console, runlevel 3 This is on Cauldron for Mageia 9 I have seen this several times this spring and summer because of trying various drivers for my nvidia card. I have booted the system by in grub, choosing Advanced, then recovery mode, give root pawd, issue 'telinit 3', log in as root, then run drakx11. It works almost to the end, i.e when shifting from Xorg modesetting to a nvidia proprietary driver i see it build the module (dkms) but after drakx11 crashing and i reboot, still modesetting is used, and launching MCC-> graphics i am told modesetting is chosen. If i there then choose same proprietary driver it takes no time to build dkms module, and after rebooting the proprietary is used. So, it crash after operating dkms, but before it have altered needed configuration.
CC: (none) => fri
Giuseppe, you wrote you have seen it too Prio high: Users must be able to choose graphics driver - especially when GUI can not start. Drivers are hard enough without this problem, and we encourage users to try different...
Priority: Normal => HighCC: (none) => ghibomgxWhiteboard: MGA5TOO => MGA9TOO, MGA8TOO
At least when a workaround is found it should go into errata. Until then, I dont know if/what to say there.
Keywords: (none) => FOR_ERRATA8, FOR_ERRATA9
Keywords: FOR_ERRATA9 => IN_ERRATA9