Bug 24473

Summary: mgaapplet crashed (mkdir /var/cache/urpmi/partial: Permission denied at /usr/lib/perl5/vendor_perl/5.22.3/urpm.pm line 305.)
Product: Mageia Reporter: Christian C <bugzzzz>
Component: RPM PackagesAssignee: Mageia tools maintainers <mageiatools>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: marja11, ouaurelien, thierry.vignaud
Version: 6   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: mgaonline-3.24.1-1.mga6, urpmi CVE:
Status comment:

Description Christian C 2019-03-07 13:13:38 CET
The "mgaapplet" program crashed. Drakbug-17.88.3 caught it.

opening a new session after reboot

mkdir /var/cache/urpmi/partial: Permission denied at /usr/lib/perl5/vendor_perl/5.22.3/urpm.pm line 305.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/perl5/5.22.3/Carp.pm:166
Carp::croak() called from /usr/lib/perl5/5.22.3/File/Path.pm:156
File::Path::_mkpath() called from /usr/lib/perl5/5.22.3/File/Path.pm:114
File::Path::mkpath() called from /usr/lib/perl5/vendor_perl/5.22.3/urpm.pm:305
urpm::create_var_lib_rpm() called from /usr/lib/perl5/vendor_perl/5.22.3/urpm.pm:292
urpm::set_files() called from /usr/lib/perl5/vendor_perl/5.22.3/urpm.pm:150
urpm::new() called from /usr/lib/perl5/vendor_perl/5.22.3/Rpmdrake/open_db.pm:80
Rpmdrake::open_db::fast_open_urpmi_db() called from /usr/bin/mgaapplet:62

Theme name: Qt4
Kernel version = 4.14.100-desktop-1.mga6
Distribution=Mageia release 6 (Official) for x86_64
CPU=AMD Athlon(tm) II X4 620 Processor
Marja Van Waes 2019-03-09 07:51:40 CET

CC: (none) => marja11, thierry.vignaud
Summary: mgaapplet crashed => mgaapplet crashed (mkdir /var/cache/urpmi/partial: Permission denied at /usr/lib/perl5/vendor_perl/5.22.3/urpm.pm line 305.)
Source RPM: mgaonline-3.24.1-1.mga6 => mgaonline-3.24.1-1.mga6, urpmi
Assignee: bugsquad => mageiatools

Comment 1 Aurelien Oudelet 2020-08-16 22:50:32 CEST
Still in Mageia 7 or Cauldron ?

CC: (none) => ouaurelien
Ever confirmed: 1 => 0
Status: NEW => UNCONFIRMED

Comment 2 Aurelien Oudelet 2020-08-29 19:09:26 CEST
Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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