Description of problem: I cannot figure out which part(s) of the system has gone wrong, so let me describe the steps I have made. 1. Started from Mageia 1 Beta 2 KDE Live CD. 2. After KDE completely loaded, configured DSL PPPoE network connection. 3. Started Mageia Control Center, and configured media sources. 4. Went back to Mageia Control Center, and started updating the system. 5. Let the downloading & installation of packages proceed, and waited for LCD go into power saving mode. 6. Moved the mouse to make LCD restore from power saving mode. 7. The updating windows aborted disappeared. 8. Again from Mageia Control Center, configured & updated media sources. 9. Media sources update failed. 10. Task bar at the bottom of the desktop disappeared, then wallpaper disappeared, too. 11. Mageia Control Center did not disappear. 12. After a while, a small dialog appeared saying: KWin is unstable. It seems to have crashed several times in a row. You can select another window manager to run: ⦠Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce:
Created attachment 405 [details] the /var/log/messages file In the /var/log/messages file, MageiaUpdate progress seemed to be OK until Line 1382. After that, problems seemed to occur.
Attachment 405 mime type: application/octet-stream => text/plain Attachment 405 description: /var/log/messages => the /var/log/messages file
Created attachment 406 [details] the /home/live/.xsession-errors file Starting from Line 1927 in the /home/live/.xsession-errors file, we can see a series of crashes.
Seems like you're also running out of space cf May 14 21:36:43 localhost console-kit-daemon[2379]: WARNING: Error writing state file: No space left on device So a lot of things can break in that case :/ Ideally you should install the -debug package to provide a nice backtrace for upstream but without free space it's going to be difficult :/
CC: (none) => balcaen.john
Component: Installer => RPM Packages
(In reply to comment #3) > Seems like you're also running out of space > cf > May 14 21:36:43 localhost console-kit-daemon[2379]: WARNING: Error writing > state file: No space left on device > So a lot of things can break in that case :/ > Ideally you should install the -debug package to provide a nice backtrace for > upstream but without free space it's going to be difficult :/ I remember that in Mandriva if disk space of /var is lower than a specified value (may be dependent on how many packages you need to upgrade) it will refuse to upgrade. This would happen in my eeepc since the ssd space is quite small and I didn't give /usr and /var too much space. Does mageia do the same checkup? Suppose this lack-of-space problem should not happen.
CC: (none) => franklin
(In reply to comment #4) > I remember that in Mandriva if disk space of /var is lower than a specified > value (may be dependent on how many packages you need to upgrade) it will > refuse to upgrade. This would happen in my eeepc since the ssd space is quite > small and I didn't give /usr and /var too much space. Does mageia do the same > checkup? Suppose this lack-of-space problem should not happen. It should but i don't have any idea it would be nice to have a result of df to confirme or not my theory.
(In reply to comment #4) > (In reply to comment #3) > > Seems like you're also running out of space > > cf > > May 14 21:36:43 localhost console-kit-daemon[2379]: WARNING: Error writing > > state file: No space left on device > > So a lot of things can break in that case :/ > > Ideally you should install the -debug package to provide a nice backtrace for > > upstream but without free space it's going to be difficult :/ > > I remember that in Mandriva if disk space of /var is lower than a specified > value (may be dependent on how many packages you need to upgrade) it will > refuse to upgrade. That check was done by mdkonline (it's mgaonline in Mageia), since mgaonline has only been available for a couple of days you upgraded using urpmi from terminal, right? urpmi doesn't do the same check IIRC.
(In reply to comment #6) > (In reply to comment #4) > > I remember that in Mandriva if disk space of /var is lower than a specified > > value (may be dependent on how many packages you need to upgrade) it will > > refuse to upgrade. > > That check was done by mdkonline (it's mgaonline in Mageia), since mgaonline > has only been available for a couple of days you upgraded using urpmi from > terminal, right? urpmi doesn't do the same check IIRC. Okay. Since using urpmi to upgrade may have such problems, will it be possible to add this space check in urpmi? That would eliminate many possible problems.
(In reply to comment #5) > (In reply to comment #4) > > I remember that in Mandriva if disk space of /var is lower than a specified > > value (may be dependent on how many packages you need to upgrade) it will > > refuse to upgrade. This would happen in my eeepc since the ssd space is quite > > small and I didn't give /usr and /var too much space. Does mageia do the same > > checkup? Suppose this lack-of-space problem should not happen. > > It should but i don't have any idea > it would be nice to have a result of df to confirme or not my theory. I did not install the system to the hard disk, so the Live CD system only used my physical memory space (total 2GB)? Or which file could be useful to help confirm the problem? I have backed up a nearly full copy of the file system when those crashes occurred.
@Jin-tong, that may explain the issue, you simply ran out of RAM; the Live CD only uses the RAM, wfor _all_ the files including stuff in /var/ ... etc, you ran out of RAM, so apps started crashing...
(In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #4) > > > I remember that in Mandriva if disk space of /var is lower than a specified > > > value (may be dependent on how many packages you need to upgrade) it will > > > refuse to upgrade. > > > > That check was done by mdkonline (it's mgaonline in Mageia), since mgaonline > > has only been available for a couple of days you upgraded using urpmi from > > terminal, right? urpmi doesn't do the same check IIRC. > > Okay. Since using urpmi to upgrade may have such problems, will it be possible > to add this space check in urpmi? That would eliminate many possible problems. This is a bit off-topic here... IMHO, urpmi, like any CLI too, is supposed to be used by advanced users; and advanced users are expected to check for things such as having enough free HDD space; feel free to open an enhancement bug against urpmi, at least to see what the urpmi maintainers think about such a wish.
(In reply to comment #10) > This is a bit off-topic here... IMHO, urpmi, like any CLI too, is supposed to > be used by advanced users; and advanced users are expected to check for things > such as having enough free HDD space; feel free to open an enhancement bug > against urpmi, at least to see what the urpmi maintainers think about such a > wish. I think this kind of problem should be checked by the software, and it's more likely being a bug... The function of checking the space left on the disk should be implemented in urpmi, not in mgaonline, which would cause maintenance problem of mgaonline.
CC: (none) => elegant.pegasus
Summary: KWin crashed after LCD restored from power saving mode while updating system => KWin crashed after LCD restored from power saving mode while updating system (in live mode)
Is the initial bug still present ?
Keywords: (none) => NEEDINFOWhiteboard: (none) => check
The initial bug was reported when I tested Mageia 1 Beta 2 in Live CD mode. Now that Mageia 1 Final has been released for a while and I no longer use Mageia in Live CD mode, I'm not sure whether that bug is still present. The only thing I can make sure is that I haven't suffered from the bug again in Mageia 1 *installation* mode.
ok so I close as old.
Status: NEW => RESOLVEDResolution: (none) => OLD