| Summary: | mgaapplet-update-checker crashed | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | José MarÃa Alonso <garral> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | thierry.vignaud |
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | Output from lspcidrake -v, as suggested in the eror message | ||
Your system is read-only. That is not supported. CC:
(none) =>
thierry.vignaud Also you don't have /var/lib/rpm which means your system is pretty broken Well, now it is not pretty broken, it is dead as a stone. After sending the information above I tried to restart and grub was all I was able to reach, but not a step beyond. I wonder how Mageia happened to die in such a fast and unexpected way, since I had installed it from scratch about a month ago. During that time I worked with it, installed maintenance, and all the usual with no visible problem. If it may d of some help -though not for me, my computer is now an ugly black box with beautiful blue lights-, the last maintenance I installed -I think it was last Friday, July 4th- included rpmdrake and some more rpm related packets. Maybe there was some problem that I did not see installing that maintenance. So I think I will reinstall Mageia 4 from scratch. If something goes wrong I will tell you. Thank you very much. Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Status:
NEW =>
RESOLVED |
Created attachment 5264 [details] Output from lspcidrake -v, as suggested in the eror message The "mgaapplet-update-checker" program crashed. Drakbug-16.26.11 caught it. Absolutely nothing. I saw this error message when I "waked up" the computer after a day and a half without using it. mkdir /var/lib/rpm: Sistema de ficheros de sólo lectura at /usr/lib/perl5/vendor_perl/5.18.1/urpm.pm line 305. Perl's trace: standalone::bug_handler() called from /usr/lib/perl5/5.18.1/Carp.pm:100 Carp::croak() called from /usr/lib/perl5/5.18.1/File/Path.pm:156 File::Path::_mkpath() called from /usr/lib/perl5/5.18.1/File/Path.pm:114 File::Path::mkpath() called from /usr/lib/perl5/vendor_perl/5.18.1/urpm.pm:305 urpm::create_var_lib_rpm() called from /usr/lib/perl5/vendor_perl/5.18.1/urpm.pm:293 urpm::set_files() called from /usr/lib/perl5/vendor_perl/5.18.1/urpm.pm:151 urpm::new() called from /usr/lib/perl5/vendor_perl/5.18.1/Rpmdrake/open_db.pm:80 Rpmdrake::open_db::fast_open_urpmi_db() called from /usr/bin/mgaapplet-update-checker:40 Theme name: oxygen-gtk Kernel version = 3.12.21-desktop-2.mga4 Distribution=Mageia release 4 (Official) for x86_64 CPU=AMD Athlon(tm) II X2 215 Processor