The "mgaapplet-update-checker" program crashed. Drakbug-16.26.8 caught it. Just accepted update as of today thursday 27'th february 2014. mkdir /var/cache/urpmi/partial: Adgang nægtet 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.9-server-1.mga4 Distribution=Mageia release 4 (Official) for x86_64 CPU=Intel(R) Core(TM) i5-3350P CPU @ 3.10GHz
according to reverso "Adgang nægtet" mean "access denied" so what give "ll /var/cache/urpmi/" ?
(In reply to Manuel Hiebel from comment #1) > according to reverso "Adgang nægtet" mean "access denied" > > so what give "ll /var/cache/urpmi/" ? I couldn't find the ll command, tried ls instead - OK ? bash-4.2$ ls -al /var/cache/urpmi/ totalt 112 drwxr-xr-x 4 root root 4096 feb 28 06:51 . drwxr-xr-x 13 root root 4096 nov 27 16:15 .. -rw-r--r-- 1 root root 1437 feb 28 06:51 .metalink -rw-r--r-- 1 root root 91211 feb 27 08:29 mirrors.cache drwxr-xr-x 2 root root 4096 feb 28 06:51 partial drwxr-xr-x 2 root root 4096 feb 27 08:29 rpms bash-4.2$
yep, no ideas then
CC: (none) => thierry.vignaud
Summary: mgaapplet-update-checker crashed => mgaapplet-update-checker crashed (mkdir /var/cache/urpmi/partial: access denied)
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 => RESOLVEDResolution: (none) => OLD
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=19697