Bug 33452 - drakx11 in text mode crash on "too small screen" (in reality 4K) after preparing kernel module, making root filesystem unmountable
Summary: drakx11 in text mode crash on "too small screen" (in reality 4K) after prepar...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard: MGA9TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-02 11:20 CEST by Morgan Leijström
Modified: 2024-08-02 17:47 CEST (History)
0 users

See Also:
Source RPM: drakx-kbd-mouse-x11-1.38-1.mga9
CVE:
Status comment: in Wiki


Attachments
For reference: log of fixing the broken filesystem (3.02 KB, text/plain)
2024-08-02 14:11 CEST, Morgan Leijström
Details

Description Morgan Leijström 2024-08-02 11:20:51 CEST
I had graphics issues after resuming, desktop unresponsive, so I hit Ctrl+Alt+F4 to text terminal and launched drakx11 in order to switch from nouveau to nvidia470.

drakx11 operated as expected whilei selected the driver, I answered I wanted the proprietary driver, and I saw it building the kernel module etc, using full width of my screen for progress text output.

But when I expect drakx11 was to ask the final questions, the screen just said:


 Your screen is currently too small for the application.
 Resize the screen and restart the application.
 Press <CTRL+C> to exit...

 Ignore the following Glib::Object::Introspection & Gtk3 warnings
                                                                 Cannot be **

(At ** it goes on and on but i stop typing it out.)
Note the interesting line feed between "warnings" and "Cannot"
and the long line is broken like that continuously, which is about five line sections for the full width of my screen.

So it seems to first run OK, and for later it somehow get wrong information about the width of my screen.


I hit Ctrl+C, and got to the # cursor but nothing I type gets displayed.
I then typed reboot and enter, and it rebooted.

During boot, after entering LUKS pass for the partition for the PV for the LVM  LV for my root system, it drops me to rescue mode...
I see the root filesystem contain a non-empty orphan, it say.

(I will boot on a stick to fix that. Later.)

---

Not the first time this hit me but it seem I have forgot to report it as separate bug.
This time is first, I think, that it corrupted the filesystem but it also may be the first time i in this situation changed *to* a proprietary driver - i used to use drakx11 in text mode only switch from prop. to free, maybe that it the difference from breaking the filesystem and not.
Morgan Leijström 2024-08-02 11:21:40 CEST

Whiteboard: (none) => MGA9TOO

Comment 1 Morgan Leijström 2024-08-02 14:11:29 CEST
Created attachment 14618 [details]
For reference: log of fixing the broken filesystem

I booted on a USB stick loaded with https://www.system-rescue.org/ to fix the broken root filesystem.  Attached is a copy from the console.
Comment 2 Morgan Leijström 2024-08-02 17:37:33 CEST
After fixing the filesystem per Comment 1, the system booted but did not reach graphical login.

I again launched drakx11, this time selecting Xorg modesetting in the nvidia section. That went well, after reboot system seem to operate normally.

Operated this way, drakx11 is always displayed and have no problem.
So is seem that the problem appear only when it installs proprietary driver, causing other text is output from that process, and when that part is finished, drakx11 crash when it is about to display another dialogue.

Summary: drakx11 crash on "too small screen" (in reality 4K), making root filesystem unmountable => drakx11 crash on "too small screen" (in reality 4K) after preparing kernel module, making root filesystem unmountable

Morgan Leijström 2024-08-02 17:39:09 CEST

Summary: drakx11 crash on "too small screen" (in reality 4K) after preparing kernel module, making root filesystem unmountable => drakx11 in text mode crash on "too small screen" (in reality 4K) after preparing kernel module, making root filesystem unmountable

Comment 3 Morgan Leijström 2024-08-02 17:47:05 CEST
Now noted, with link back here, under
https://wiki.mageia.org/en/Setup_the_graphical_server#Known_Nvidia_issues

Status comment: (none) => in Wiki


Note You need to log in before you can comment on or make changes to this bug.