Bug 30093

What's the output of "df -h|grep -v tmp" and "df -i|grep -v tmp"?

CC: (none) => davidwhodgins

The answer to the question in comment 1 is:

[mike@localhost ~]$ df -h|grep -v tmp" and "df -i|grep -v tmp
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        50G   42G  5.6G  89% /
/dev/sda6       405G   17G  388G   4% /home
[mike@localhost ~]$ 

Yes, I notice this response, pasted from console, is not the one expected.

Notice the user here is mike, not ken. mike was created during Mageia 8's first installation, and has not been used since. ken is not being used because it has lost control of the system due to unexplained activities within it.

After I get both the laptop and the external screen working together, I decisded to play an educational DVD via VLC. It started OK, but several minutes into the video the screen image stopped changing while the audio continued. I tried to run kodi as a program, but that was a dead end. I remembered seeing kode as a desktop environment, so I rebooted and chose it for the first time. After a bit of futzing around, I got it to play the DVD. I played several lectures, tdhen exited from it. I wanted to reboot to rechoose Plasma, but I soon found myself locked out of Plasma, then unable to control GNOME Wayland without any menus, and the screens were no longer booting together in synchrony.Things went from bad to worse through several reboots, including a request for the root password to run package manager, followed by a visit to the command line, asking if I wanted to manage the system repair process. I wasn't a happy camper.

Finally, I got the idea to try to reboot as a different user, and mike then appeared. The applications bar return to the bottom of the screen because mike had never moved it to the top, as had ken. Moving the mouse between screens is problematic, though I did get a glimpse of what appeared to be a more normal menu structure above the Mageia logo. mike got Mageia Welcome to launch Firefox, which came up as for a new user, but Mageia Welcome appears to have frozen. It will not allow mike to install Claws Mail, since I don't want to disturb ken's Thunderbird, which does not appear to be installed for mike as yet.

All in all, the combination of the tsk games install's menu system changes, and what appears to be kodi's trashing of my ability to reboot the system to Plasma has left this Latitude in a seriously unstable position regarding user ken, and users mike and root have yet to decipher this box of riddles.

I have an in-class examination in less than a dozen hours. Fortunately, I have another working machine which will allow me to log into the exam while in the classroom. I'm sorry to write an email in the Bugzilla database, but it's what I have available to answer the question. I'll attempt to read some more here on the other side of the exam.

(In reply to Kenneth Marcy from comment #2)
> followed by a visit to the command line, asking if I wanted to manage the
> system repair process. I wasn't a happy camper.

As far as I'm aware, the only thing that would ask for the repair process
is triggered by file system corruption that typically indicates the drive
lost power in the middle of writing files, or a failing disk drive.

Does (as root) "smartctl -a /dev/sda" show any errors? Replace sda with the
appropriate drive letter.

Installed task-games
525 packages got installed
26 GB space neede
17GB downloaded

No regression found. Made screenshots of all menues before installation and compared it after the installation was done. Nothing changed except that the Games menu was filled.

If i read your description i can only second Dave's opinion that something one your system is really broken. Your profiles/system seems already borked before installation of task-games was startet.

Ever confirmed: 1 => 0
Status: NEW => UNCONFIRMED

(In reply to Dave Hodgins from comment #3)
> (In reply to Kenneth Marcy from comment #2)
> > followed by a visit to the command line, asking if I wanted to manage the
> > system repair process. I wasn't a happy camper.
> 
> As far as I'm aware, the only thing that would ask for the repair process
> is triggered by file system corruption that typically indicates the drive
> lost power in the middle of writing files, or a failing disk drive.
> 
> Does (as root) "smartctl -a /dev/sda" show any errors? Replace sda with the
> appropriate drive letter.

@ Kenneth

ping?

Keywords: (none) => NEEDINFO
CC: (none) => marja11

months later, no reply, closing

Resolution: (none) => OLD
Status: UNCONFIRMED => RESOLVED