Why the Linux guest-system, on my Linux-tablet, is only a shell.

According to some of my own postings, I possess an old Android-based tablet, which is a Samsung Galaxy Tab S, first generation, onto which I installed a Linux guest-system, using the Android apps “GNURoot (Debian)” and “XSDL”, both available from Google Play. The latter of these apps emulates a simple X-server, which Linux-programs running under the first app can make use of.

The desktop-manager which I chose to use for my Linux guest-system is LXDE, precisely because that desktop-manager does not strictly require that Linux-based daemons be running.

But there are certain standard, LXDE-features which will not even work on that setup:

  • The Trash Bin
  • The LXDE-Settings Panel
  • (etc.)

The LXDE Trash Bin requires the package ‘gvfs’, and the Settings Panel requires the package ‘lxde-settings-daemon’. Both these dependencies launch daemons – i.e., programs that run in the background, and that make up part of a real Linux-session.

The ability to run daemons, essentially, requires that the user have a rooted tablet. Because I never rooted my tablet, I am without any daemons, that would normally belong to any Linux guest-system.

Continue reading Why the Linux guest-system, on my Linux-tablet, is only a shell.

Debian Category Missing From Plasma Menu.

I use several Linux-based computers, which include an older machine running Debian / Jessie and the KDE 4 desktop manager, and a more-recently-installed machine, running Debian / Stretch and the Plasma 5.8 desktop manager.

Under KDE 4 – which I’ve grown used to over the years – the K-Menu – aka, the Application Launcher – would display a nested menu-system, that included the KDE categories into which applications should fit, which are defined essentially by ‘.desktop’ files, plus a separate category called ‘Debian’, which was denoted by a folder-icon, and which was nested several levels deep, into which almost every installed application should be sortable, defined essentially by the contents of the directory ‘/usr/share/menu’.

k-menu_1s

Under my Plasma 5.8 setup, one fact which I was missing, was the earlier presence of this Debian -category:

k-menu_2s

 

Instead, this computer has a larger abundance of entries, in its Lost+Found category (not shown), which is really just another way of saying, ‘entries which it cannot otherwise put into categories’. In fact, many of the entries that now occur under Lost+Found, also occur under listed categories.

(Updated 12/14/2017 : )

Continue reading Debian Category Missing From Plasma Menu.

Understanding The Intricacies Of KDE Logic

In This Posting, I was describing a problem with my Linux laptop named ‘Klystron’, in which the laptop would take itself off my WiFi, apparently every time I closed the lid.

In the short term, there was a solution to this problem. I was able to go into my KDE Power Management Settings, where I had set the action on closing the lid to “Lock Screen”, and I was able to change this setting to “Do Nothing”. The suspicion had never occurred to me, that there could be two distinct behaviors:

1) After (x) minutes, the screensaver can come on, and if the attempt is made to interrupt the screensaver after (y) additional seconds, that screensaver can ask the user for his password.

2) The user can ask KDE to “Lock The Screen”.

According to the way KDE works, (1) and (2) are as different as Night and Day. So apparently, Locking The Screen is also supposed to mean, Disconnect From WiFi. But the screensaver asking the user for his password to stop, does not mean Disconnecting The WiFi.

Live and Learn.

And actually, one main reason for which I do close the lid usually, is the fact that the laptop is more protected from dust etc., with the lid closed.

Dirk

(Edit : ) This laptop setup uses Network Manager. So just this afternoon I left-clicked on the Network Manager icon while connected to my home WiFi, and then drilled deeper into its GUI, to adjust which settings would be displayed as additional information about the network I am connected to. Network Manager is somewhat flexible in this GUI layout adjustment, but does not really allow settings to be fine-tuned in the same way.

Some KDE setups use ‘WICD‘ instead of ‘Network manager‘.

What I saw, was that there was no specific parameter to display, for whether a WiFi network should disconnect, on locking the desktop.

The only relevant WiFi-related detail I was able to add to the display, was “WiFi Band”, which could plausibly have complemented “WiFi Security”, which was already included. For my home access point, WiFi Band now displays “b/g“, as a result of further troubleshooting steps of mine.

I have since disabled 802.11n from the kernel module…

This means in practice, according to my logic, that the behavior I described in this posting, of cutting out when I close the laptop lid, cannot be deliberate. If it was deliberate, it would also be something which can be configured differently. And thus, this can also not be due to any translation error.

Therefore, this is a bug, and one I can now reproduce any time I want to.