| Summary: | XFdrake crashed (can't call method "attron" on an undefined value at Curses/UI/Checkbox.pm line 221) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thierry Vignaud <thierry.vignaud> |
| Component: | RPM Packages | Assignee: | Mageia tools maintainers <mageiatools> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | fri, ghibomgx, marja11, pterjan |
| Version: | Cauldron | Keywords: | FOR_ERRATA8, IN_ERRATA9 |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | MGA9TOO, MGA8TOO | ||
| Source RPM: | drakx-kbd-mouse-x11, perl-Curses-UI | CVE: | |
| Status comment: | |||
| Attachments: | Screenshot of drakx11 crashing in console, runlevel 3 | ||
|
Description
Thierry Vignaud
2015-04-05 13:49:39 CEST
I was reconfiguring Xorg after switching from QXL to Cirrus for video
Thierry Vignaud
2015-04-05 13:57:20 CEST
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)
Thierry Vignaud
2015-06-02 14:14:44 CEST
Source RPM:
drakx-kbd-mouse-x11 =>
drakx-kbd-mouse-x11, perl-Curses-UI
Samuel Verschelde
2015-06-06 17:02:26 CEST
Whiteboard:
(none) =>
MGA5TOO
Marja Van Waes
2016-10-15 23:44:19 CEST
Assignee:
bugsquad =>
mageiatools 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 =>
High 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
Lewis Smith
2023-08-28 10:43:36 CEST
Keywords:
FOR_ERRATA9 =>
IN_ERRATA9 |