[Moltke]

I created root access in my KDE LL build. Took a few hours of research to get a reliable, working fix.
This is the way it would be implemented for Dolphin & Kwrite:

.desktops: (may have to create folders)
~/.local/share/kservicess5/ServiceMenus/

polkits:
/usr/share/polkit-1/actions

Create a polkit file for Dolphin:

com.ubuntu.pkexec.dolphin.policy

Code:

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE policyconfig PUBLIC   "-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"   "http://www.freedesktop.org/standards/PolicyKit/1/policyconfig.dtd"> <policyconfig>     <vendor>Linux Lite</vendor>   <vendor_url>https://linuxliteos.com/</vendor_url>     <action id="com.ubuntu.pkexec.dolphin">     <message>Authentication is required to run Dolphin</message>     <icon_name>window-close</icon_name>     <defaults>       <allow_any>auth_admin</allow_any>       <allow_inactive>auth_admin</allow_inactive>       <allow_active>auth_admin</allow_active>     </defaults>     <annotate key="org.freedesktop.policykit.exec.path">/usr/bin/dolphin</annotate>     <annotate key="org.freedesktop.policykit.exec.allow_gui">true</annotate>   </action> </policyconfig>

.desktop for Dolphin:

dolphin-root.desktop

Code:

[Desktop Action root] Exec=pkexec dolphin Icon=window-close Name=Open as Admin [Desktop Entry] Actions=root Icon=window-close MimeType=inode/directory ServiceTypes=KonqPopupMenu/Plugin Type=Service X-KDE-Priority=TopLevel X-KDE-StartupNotify=false

For Kwrite, rinse and repeat, just change where obvious.

I haven't tried this yet but will do as soon as I figure how to on my kde box with debian. I did find this post https://fitzcarraldoblog.wordpress.com/2...root-user/ and the solutions posted there worked just fine.

EDIT: Just found a solution here http://forums.debian.net/viewtopic.php?f...71#p700768 and it was as easy as install a pkg.

[Benedict Yappy]

One thing I'm not liking is KDE "wallet." Every time I boot, kwallet asks me for a password just to connect to my own wifi from my own computer (which I logged into with my own username and password). That doesn't seem well thought out. I've got a feeling it serves a very good purpose and in the future we're all going to be using wallets. But, right now, I'm not liking it.

Issues discussed here are probably more specific to distro default config than KDE...

kWallet is a secret keeper, which can be secured with a password not necessarily identical with linux user password. If the login system assume that it is identical when it isn't, and try to open the wallet with the linux user password, you get error message on every login for failing to open the wallet.

Wallets store not only trivialities like wifi passwords,  but also encryption keys to more important stuffs like Chrome browser data, that includes saved online passwords. Linux give us the possibility to have multi wallet with multi password, but the default behavior (asking wallet password every login) might feel inconvenient.

On my daily driver, I set my default wallet password identical to linux user login password, and configure the login system to open the wallet when logging in (using linux user password as wallet password). This is configured in /etc/pam.d folder.

If the operating system is configured for simplicity, then assuming that the wallet password and user password will be the same is very sensible, but to my experience hopping distro so far, most distro does not do this by default.

Other issues discussed, ie waiting for NFS to cleanly unmount before shutting down, is probably also related with the distro's default configuration, hidden in places like samba config, systemd services config, timeout settings etc. These are things (Jerry's bread and butter?) which casual users would never configure themselves (not many windows user know how to use msconfig, not all linux users ever enter /etc folder)

Kubuntu's default might be carried over from Ubuntu's use case as server, it should must wait for services within it to really gracefully exit before OS shut down (SQL database corruption is a bad bad bad thing), while in GUI systems, a simple confirmation is all it takes to gracefully exit all GUI program.

I'm sure that the fine tuning of LL can also be carried over into KDE, to ensure an experience more attuned to what users expect. I just want to say that resolving these issues are perfectly doable with KDE.

PS: I was just trying out LL, and I think it is a distro I can use immediately after installation, instead of needing-customization-to-be-usable. I'll use LL as my OS-in-flashdrive that I use for backup purposes. (I use openSUSE tumbleweed KDE for daily driver).

[valtam]

Haven't done an update on this VM for a while, check out the memory use with everything installed. Unreal.

[torreydale]

[member=2]Jerry[/member] ,

I hadn't logged into the forum in a bit, and this is exactly the topic that was on my mind.  Thanks for the update.

[TheDead]

That... is impressive! o.0

With Jerry's magic touch, can't wait to try it out.

Can't... wait...

[BerryBenson]

After seeing this thread I tried adding KDE to linux lite. It turns it's not possible. I don't like that. One of linux appeal is that you have the freedom to do what you want with it.

[TheDead]

Heya!

Changing desktop is always a challenge.
Starting from a "core" build would get you the most success, but even if I used Linux a few years, I still consider myself a noob when dealing with "deep" stuff.

I successfully installed XFCE on two other distro that didn't have it, results were... o.k., but not bug free.
It gave me more respect for distro builders like Jerry. It can be a labor of love sometime .

[firenice03]

After seeing this thread I tried adding KDE to linux lite. It turns it's not possible. I don't like that. One of linux appeal is that you have the freedom to do what you want with it.

Its possible, although not necessarily advised. If you choose to there isn't support. Remember LL is built for newbies and Windows refugees.
LL is what is says - Simple and Fast.. and of course FREE!

Jerry has built LL to be very stable.

Installing any DE is of course always up to the user - but its not a simple click and install as would any DE that's not prebuilt with the OS...

[TheDead]

Friday's broken brain idea!

I don't think it would be feasible but having the choice of XFCE or KDE on boot/install would be awesome.
But, since I didn't see any distros doing that and always having seperate distro flavors with their own ISO files, I guess this is an Utopian though (or heresy?).
Also, the size of the ISO could be huge... so sad.

[trinidad]

Net install like Debian lets you build what you want. LL's version of XFCE is highly modified and appended with additonal distro specific software which would definitely make it more difficult to range between QT and GTK and Xorg and Wayland. Expect one or the other as seperate LL ISOs without a net install repository configuration, which in itself would be a very expensive undertaking, and a heavy burden on the developers, and wrought with problems for new users. The code cleanliness and usability of this distro is its primary cache.

TC