in Xfce under Manjaro the administrator-krusader can't change the settings for toolbar. It is always "Only text". To start the administrator-krusader from other Desktops unlike KDE-Plasma it is following necessary (why?): sudo pacman -S dbus-x11 --> dbus delete: j sudo pacman -S kde-cli-tools cd /usr/lib64/ sudo mkdir libexec cd libexec sudo ln -s ../../lib/kf5/ Under LXQT shows the administrator-krusader the same settings as the normal krusader (it's not normal). regards Ch. Hanisch
I have found that following is helpful: KDE_SESSION_VERSION=5 KDE_FULL_SESSION=true krusader or in ~/Desktop/org.kde.krusader.root-mode.desktop ... Exec=kdesu "-c KDE_SESSION_VERSION=5 KDE_FULL_SESSION=true krusader"
very interesting is the following: Whenever I boot first to KDE-Plasma und than Logout/login to Xfce the administrator-krusader have changeable settings for toolbar. What is the reason for that?
>sudo pacman -S dbus-x11 --> dbus delete: j This is a know issue for applications using dbus running as different user in Xorg. You can also use "dbus-launch kruader" >sudo pacman -S kde-cli-tools >cd /usr/lib64/ >sudo mkdir libexec >cd libexec >sudo ln -s ../../lib/kf5/ The path to kdesu is needed at compile time now. We have a new cmake option for this: -DKDESU_PATH. I'll report downstream (Arch maintainers). >Under LXQT shows the administrator-krusader the same settings as the normal krusader (it's not normal). See bug 373720. I'll investigate. >in Xfce under Manjaro the administrator-krusader can't change the settings for toolbar. It is always "Only text". This is what i cannot reproduce (with Arch and LXQt). Changing the toolbar works always fine. >I have found that following is helpful: >... Does it solve toolbar problem? >Whenever I boot first to KDE-Plasma und than Logout/login to Xfce the administrator-krusader have changeable settings for toolbar. >What is the reason for that? Ehh, no idea.
Hello, Am 25.04.2017 um 18:13 schrieb Alex Bikadorov: https://bugs.kde.org/show_bug.cgi?id=379149 Alex Bikadorov <alex.bikadorov@kdemail.net> [1] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| | alex.bikadorov@kdemail.net [1] --- Comment #3 from Alex Bikadorov <alex.bikadorov@kdemail.net> [1] --- Under LXQT shows the administrator-krusader the same settings as the normal krusader (it's not normal). See bug 373720. I'll investigate. in Xfce under Manjaro the administrator-krusader can't change the settings for toolbar. It is always "Only text". This is what i cannot reproduce (with Arch and LXQt). Changing the toolbar works always fine. The unchangeable toolbar is also in LXQt under Manjaro and Kubuntu (Krusader Version 2.4.0-beta3 "Single Step"). I have found that following is helpful: ... Does it solve toolbar problem? Only partial. The unchangeable toolbar with that helpful settings is than "Only symbols". regards Ch. Hanisch 1. mailto:alex.bikadorov@kdemail.net
Could you please check if it's still the case for v2.6? Also, what is administrator-krusader exactly? A script to run krusader with kdesu? If you run 1. sudo su - 2. krusader do you have the same problem? Thanks!
<If you run <1. sudo su - <2. krusader <do you have the same problem? No, with that the Icons in Toolbar are present.
I'm closing as it seems to be shell environment problem with a administrator-krusader program that Krusader team doesn't produce.
(In reply to Nikita Melnichenko from comment #7) > I'm closing as it seems to be shell environment problem with a > administrator-krusader program that Krusader team doesn't produce. Ok. But how can I solve the problem on my system?
> what is administrator-krusader exactly? He talks about Krusader, but executed with root privileges, I attach some screenshots:
Created attachment 112775 [details] The usual menu entry in a Kubuntu 14.04 machine, it was installed when installing the Krusader package.
Created attachment 112776 [details] The {Krusader - root mode} menu entry in the same Kubuntu 14.04 machine, it was also installed when installing the Krusader package.
Created attachment 112777 [details] Using Kubuntu 18.04, after executing: sudo krusader
Created attachment 112778 [details] Using Kubuntu 18.04, after executing: sudo su - ; krusader Note: It's interesting that there are two Oxygen icons (not Breeze ones). :-?
(In reply to Hanisch from comment #8) > (In reply to Nikita Melnichenko from comment #7) > > I'm closing as it seems to be shell environment problem with a > > administrator-krusader program that Krusader team doesn't produce. > > Ok. But how can I solve the problem on my system? What's the problem exactly? It's not clear so far. Please provide steps and screenshots, what system and Krusader version you're using. Are you using {Krusader - root mode} menu entry like Toni said? It's been removed since v2.6. Current stable is v2.7.0 - please consider upgrading if you haven't done so. If you still want to run krusader in a root mode, please run `sudo krusader`. (In reply to Toni Asensi Esteve from comment #13) > Created attachment 112778 [details] > Using Kubuntu 18.04, after executing: sudo su - ; krusader > > Note: It's interesting that there are two Oxygen icons (not Breeze ones). :-? Thanks for the screenshots, Toni. My system doesn't have the issue with Oxygen icons. `su -` changes environment to root user env, it may be that under Ubuntu it's not configured well enough. Are you using v2.7? What `krusader -d` shows?
Thank you, Nikita. > Are you using v2.7? I am using the latest git version. > What `krusader -d` shows? I'll attach some files :-)
Created attachment 112781 [details] Kubuntu 18_04 - after executing `sudo krusader -d`
Created attachment 112782 [details] Kubuntu 18_04 - after executing `sudo su - ; krusader` Note: This time a warning about icons is seen: 09:23:10.023-warning default IconEngine::pixmap@292 # Unable to find icon "inode-chardevice" of size QSize(22, 22) in any configured theme
Thanks Toni! Interesting that > System icon theme: "hicolor" From debug output it's unclear what's the difference. I need to debug to understand. I'll try to check this issue when I debug the icon code on Ubuntu next time.
Sorry, on my Kubuntu 18.04 Desktop LXQT User-Krusader has only Icons and no changing that is possible. And root-Krusader has only Text-Icons without any possibility of changing. That is the unrevised situation.
Created attachment 112812 [details] Using Kubuntu 18.04 (and its Plasma 5): after pressing the secondary button of the mouse This is a screenshot of what is seen, using Kubuntu 18.04 (and its Plasma 5), after pressing (above the toolbar) the secondary button of the mouse. Hanisch, do you see the same?
Created attachment 113071 [details] A screenshots where icons are seen correctly. Kdesu was used [While Hanisch answers, we can deal with other pending subjects.] > > 09:23:10.023-warning default IconEngine::pixmap@292 # Unable > > to find icon "inode-chardevice" of size QSize(22, 22) > > in any configured theme > From debug output it's unclear what's the difference. I > need to debug to understand. I'll try to check this issue > when I debug the icon code on Ubuntu next time. Using the command line of Kubuntu 18.04 I executed partitionmanager and I saw: Executing: "/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu" "-c KDE_FULL_SESSION=true XDG_RUNTIME_DIR=/run/user/1000 DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-3RvIgIPNgv,guid=10fab758a29498a25cc8deb65b052450 partitionmanager --dontsu" [...] so, using a similar way to execute a graphical program using root permissions, I executed /usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu -c KDE_FULL_SESSION=true krusader # // Note: Some other arguments may be used. # // Note: In `man kdesu` we can see that we could also have executed: $(kde4-config --path libexec)kdesu -c [...] and the result was that correct icons were seen. The attached screenshot can be viewed.
I can't understand that all. Why that are no solution implemented for that all?
> I can't understand that all. > Why that are no solution implemented for that all? Martin Gräßlin wrote that executing malware while executing a X11 application as root... is extremely insecure (this shouldn't be a surprise [^1]) and pushed a new feature to mainstream KDE that removed the ability of users to run Dolphin or Kwrite or Kate text editors as root, though [^1]. [^1]: Even Martin Gräßlin wrote that "if you run an application which is malicious you are already owned". Fortunately, KDE ended up seeing use cases where there was no other option than using graphical programs (like Kate) as the root user: - [allow Kate and Dolphin to be run with the root user account again](https://pointieststick.wordpress.com/2018/06/02/this-week-in-usability-productivity-part-21/). - [Dolphin](https://bugs.kde.org/show_bug.cgi?id=387974) and [Kate](https://bugs.kde.org/show_bug.cgi?id=387973) can once again be launched when logged in as the root user, and [and Dolphin displays a warning](https://phabricator.kde.org/D12732). And also fortunately... Krusader provides some ways, for example we can try executing $(kde4-config --path libexec)kdesu -c KDE_FULL_SESSION=true krusader and later we can press F4 to edit files.