Hi, thanks for reporting this bug.
Assigned to the package maintainer.

Keywords: (none) => Triaged
Assignee: bugsquad => anssi.hannula

I'm looking into this.

I'll probably add a dependency on kdebase4-runtime and suggestions (installed automatically but not required) on zip, unzip, p7zip and kdiff3.

arj and lha are so rare I don't think it makes sense to include them by default, and unrar is nonfree so I don't feel it'd be appropriate.

Status: NEW => ASSIGNED

Thank you, I will test it with the upcoming Mga2 Alpha2

Please update the package for Mga1 too.

Yes, I'll do that soon (in the next few days).

krusader-2.0.0-5.1.mga1 submitted to mga1 core/updates_testing.

Suggested advisory:
===================
Krusader of Mageia 1 had a non-functioning "Start Root Mode Krusader" option. Also, the package didn't have all the correct dependencies set, which can cause some parts of Krusader to not work properly if those packages weren't already installed.

This update fixes those issues.
===================

Testing procedure:
==================
1. Install krusader
   (it should automatically pull in kdebase4-runtime if that wasn't installed,
    plus some suggested tools: zip, unzip, p7zip, kdiff3, krename)
2. Start krusader
3. Click Tools -> Start Root Mode Krusader.
- on old version, this will fail as krusader doesn't find kdesu.
- on new version, this works properly and a root mode krusader is started.
==================

CC: (none) => anssi.hannula
Assignee: anssi.hannula => qa-bugs

I will test it for Mga1 and Mga2 Alpha2. Both will be fresh minimal installation, then basic Window Manager and then Krusader.

Testing x86_64

Before
------

Can't start root mode krusader, because krusader or kdesu is missing from the path. Please configure the dependencies in Konfigurator!

After
-----

Asks for root password


This update will be affected by bug 2317 so adding as a 'depends' until the linking is completed.

From our depcheck script run both 64 bit and 32 bit..

x86_64:

The following packages will require linking:

canberra-common-0.27-2.mga1 (Core 32bit Release)
canberra-common-0.27-2.mga1 (Core Release)
dbus-x11-1.4.1-3.mga1 (Core 32bit Release)
dbus-x11-1.4.1-3.mga1 (Core Release)
lib64alsa2-1.0.24.1-3.mga1 (Core Release)
lib64canberra0-0.27-2.mga1 (Core Release)
lib64dri-drivers-7.10.2-4.mga1 (Core Release)
lib64exiv2_10-0.21.1-1.mga1 (Core Release)
lib64mesagl1-7.10.2-4.mga1 (Core Release)
lib64polkit-qt-agent-1_1-0.99.0-1.mga1 (Core Release)
lib64qca2-2.0.3-1.mga1 (Core Release)
lib64smbclient0-3.5.8-1.mga1 (Core Release)
lib64ssh4-0.4.7-1.mga1 (Core Release)
lib64talloc2-2.0.5-2.mga1 (Core Release)
lib64vorbisfile3-1.3.2-1.mga1 (Core Release)
lib64wbclient0-3.5.8-1.mga1 (Core Release)
lib64xscrnsaver1-1.2.1-2.mga1 (Core Release)
lib64xxf86vm1-1.1.1-2.mga1 (Core Release)
libalsa-data-1.0.24.1-3.mga1 (Core 32bit Release)
libalsa-data-1.0.24.1-3.mga1 (Core Release)
polkit-kde-agent-1-0.99.0-2.mga1 (Core 32bit Release)
polkit-kde-agent-1-0.99.0-2.mga1 (Core Release)
sound-theme-freedesktop-0.7-5.mga1 (Core 32bit Release)
sound-theme-freedesktop-0.7-5.mga1 (Core Release)

i586:

The following packages will require linking:

canberra-common-0.27-2.mga1 (Core Release)
dbus-x11-1.4.1-3.mga1 (Core Release)
libalsa2-1.0.24.1-3.mga1 (Core Release)
libalsa-data-1.0.24.1-3.mga1 (Core Release)
libcanberra0-0.27-2.mga1 (Core Release)
libdri-drivers-7.10.2-4.mga1 (Core Release)
libexiv2_10-0.21.1-1.mga1 (Core Release)
libmesagl1-7.10.2-4.mga1 (Core Release)
libpolkit-qt-agent-1_1-0.99.0-1.mga1 (Core Release)
libqca2-2.0.3-1.mga1 (Core Release)
libsmbclient0-3.5.8-1.mga1 (Core Release)
libssh4-0.4.7-1.mga1 (Core Release)
libtalloc2-2.0.5-2.mga1 (Core Release)
libvorbisfile3-1.3.2-1.mga1 (Core Release)
libwbclient0-3.5.8-1.mga1 (Core Release)
libxscrnsaver1-1.2.1-2.mga1 (Core Release)
libxxf86vm1-1.1.1-2.mga1 (Core Release)
polkit-kde-agent-1-0.99.0-2.mga1 (Core Release)
sound-theme-freedesktop-0.7-5.mga1 (Core Release)

Can others please verify, thankyou.

Depends on: (none) => 2317

I think it will also need kdebase4-runtime linking, not sure why it hasn't picked that up.

Tested: installed pure Mga1 minimal system, installed task-x11 WindowMaker and krusader

All features are working - icons present, fish/ftp/etc present, unpacking files present, root-mode working

There are just annoying error messages:

Both for a user and the root:

File /root/.kde4/share/config/kdedrc isn't writeable. Please contact the administrator

File /root/.kde4/share/config/krusaderrc isn't writable. Please contact the administrator

Welcome message

Krusader's configuration is in READ ONLY mode (why is that!?) Changed values will not be saved

(In reply to comment #9)
> I think it will also need kdebase4-runtime linking, not sure why it hasn't
> picked that up.

kdebase4-runtime is already in Core Updates.

CC: (none) => davidwhodgins

(In reply to comment #10)
> Tested: installed pure Mga1 minimal system, installed task-x11 WindowMaker and
> krusader
> 
> All features are working - icons present, fish/ftp/etc present, unpacking files
> present, root-mode working
> 
> There are just annoying error messages:
> 
> Both for a user and the root:
> 
> File /root/.kde4/share/config/kdedrc isn't writeable. Please contact the
> administrator
> 
> File /root/.kde4/share/config/krusaderrc isn't writable. Please contact the
> administrator
> 
> Welcome message
> 
> Krusader's configuration is in READ ONLY mode (why is that!?) Changed values
> will not be saved

Did you install all updates available prior to installing krusador?  The directory
doesn't exist because the root user has never logged in to kde.  Since the directory doesn't exist, the configuration changes cannot be saved.

I'm pretty sure there is a resolved bug about the missing directory, but
can't find it right now.

If you did install all of the available regular updates before installing
krusader from updates testing, then there is a problem.

Note when qa testing anything from updates testing, you should always install
all available updates from the updates repository first.

I can reproduce the warning message. It is rather weird, since it only happens on first start, and the configuration settings *are* actually saved so the message seems wrong. I'll try to investigate in the next few days.

Anssi, should we go ahead and validate this update or do you want to
make other changes regarding the message at first start?

I'll try to check it today or tomorrow.

Sorry for the delay.

The dialog bug is in kdelibs, I opened an upstream review request with a proposed fix: https://git.reviewboard.kde.org/r/103577/
I also opened Mageia Bug #3943 to get it fixed in mga1.

I was able to workaround the "Krusader's configuration is in READ ONLY mode (why is that!?) Changed values will not be saved" dialog in krusader code, and submitted krusader-2.0.0-5.2.mga1 which doesn't have that dialog.

The two "File foo.bar isn't writeable" messages aren't fixed by this (they seem less common than the third one in my testing, though). They'll be fixed when bug #3943 is fixed (i.e. when the patch there will be applied).

Should we wait for bug 3943 to be fixed, or go ahead and validate this update?

IMO go ahead.

Validating the update.

Could someone from the sysadmin team push the srpm
krusader-2.0.0-5.2.mga1.src.rpm
from Core Updates Testing to Core Updates.  In addition, the following
rpm packages will have to be linked from Core Release to Core Updates.
canberra-common-0.27-2.mga1
dbus-x11-1.4.1-3.mga1
libalsa2-1.0.24.1-3.mga1
libalsa-data-1.0.24.1-3.mga1
libcanberra0-0.27-2.mga1
libdri-drivers-7.10.2-4.mga1
libexiv2_10-0.21.1-1.mga1
libmesagl1-7.10.2-4.mga1
libpolkit-qt-agent-1_1-0.99.0-1.mga1
libqca2-2.0.3-1.mga1
libssh4-0.4.7-1.mga1
libtalloc2-2.0.5-2.mga1
libvorbisfile3-1.3.2-1.mga1
libxscrnsaver1-1.2.1-2.mga1
libxxf86vm1-1.1.1-2.mga1
polkit-kde-agent-1-0.99.0-2.mga1
sound-theme-freedesktop-0.7-5.mga1

Advisory: Krusader of Mageia 1 had a non-functioning "Start Root Mode Krusader" option.
Also, the package didn't have all the correct dependencies set, which can cause
some parts of Krusader to not work properly if those packages weren't already
installed.

This update fixes those issues.

https://bugs.mageia.org/show_bug.cgi?id=3601

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

packages linked and update pushed.

Status: ASSIGNED => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED