Plasma 5 Notifications In Wrong Locations

I use a version of Linux on the one of my computers named ‘Plato’, that has Debian / Stretch as its base, but which also has Plasma 5 as its desktop manager. This was a system which I created from a Kanotix Live DVD, from before Kanotix had an official Debian / Stretch release. According to that Live Disk, the desktop manager was LXDE !  LXDE stands for “Lightweight X Desktop Environment”, while Plasma 5 is the successor to KDE 4, and is a powerful, CPU-consuming desktop manager. In the meantime, Kanotix has created two official ‘Stretch’ releases, one with LXDE and one with Plasma 5, both named ‘Kanotix Steelfire’.

What I felt I needed to do with Plato, was to install Plasma 5 via the package manager, even though the Kanotix developers had not yet done so. This customized Plasma 5 environment has been running fine for some time.

But only recently, after my email client – Thunderbird – received an update to version 60.x, I did notice that some of my desktop notifications seemed a little odd. Instead of appearing as official Plasma / KDE notifications, they appeared either as stylized bubbles, or as more-boring drop-down lists from the center, of the top, of my screen. And so this can lead to some confusion, or to some doubt in whether the system is still stable. In fact, I’ve read some other complaints from the Web, of people who ran in to the same behavior exactly. What seemed to irk them as well as me most, was that although we can use our KDE / Plasma Notification settings to designate, where we want notifications to appear, these apparently rogue notifications seem to disregard this setting.

Continue reading Plasma 5 Notifications In Wrong Locations

I no longer have Compiz-Fusion running on the LXDE-based computer, named ‘Klexel’.

According to this earlier posting, I had run in to stability issues with my newly-reinstalled Linux computer, which I name ‘Klexel’. Well, the only sensible way, finally, to solve those problems, was to deactivate ‘Compiz Fusion’, which is a special window-manager / compositor, that creates a desktop cube animation, as well as certain other effects, chosen by the user out of a long menu of effects, but which needs to run on the graphics hardware, using OpenGL.

Even though Compiz Fusion is fancy and seems like a nice idea, I’ve run in to the following problems with it, in my own experience:

  • Compiz is incompatible with Plasma 5, which is still my preferred desktop manager,
  • If we have a weak graphics-chip, such as the one provided on the computer named ‘Klexel’ using ‘i915 Support’, trying to run Compiz on it forces the so-called GPU to jump through too many hoops, to display what it’s being asked to display.

Before a certain point in time, even a hardware-accelerated graphics chip, only consisted of X vertex pipelines and Y fragment pipelines, and had other strict limitations on what it could do. It was after a point in time, that the “Unified Shader Model” was introduced, whereby any GPU core could act, as a vertex shader core, as a fragment shader core, etc.. And after that point in time, the GPU also became capable of rendering its output to texture images, several stages deep… Well, programmers today tend to program for the eventuality, that the host machine has ‘a real GPU’, with Unified Shader Model and unlimited cores, as well as unlimited texture space.

The “HP Compaq DC7100 SFF”, that has become my computer ‘Klexel’, is an ancient computer whose graphics chip stems from ‘the old days’. That seems to have been an Intel 910, which has as hardware-capability, direct-rendering with OpenGL 1.4 , the Open-Source equivalent of DirectX 7 or 8 . Even though some Compiz effects only require OpenGL 1.4 , by default, I need to run the computer named ‘Klexel’ without compositing:

screenshot-from-2018-09-04-11-56-50

Also, before, when this was the computer ‘Walnut’, it actually still had KDE 3 on it! KDE 3 was essentially also, without compositing.

It should finally be stable again, now.

By comparison, the computer which acts as Web-server and hosts this blog, which I name ‘Phoenix’, has as graphics chip an Nvidia “GeForce 6150SE”, that is more powerful than the Intel ‘i915′ series was, is capable of OpenGL 2.1 , equivalent to DirectX 9 , but still predated the Unified Shader Model chips. Microsoft has even dropped support for this graphics chip, because according to Microsoft, it’s also not powerful enough anymore. And so up-to-date Windows versions won’t run on either of these two computers.

(Update 09/04/2018, 18h20 : )

Continue reading I no longer have Compiz-Fusion running on the LXDE-based computer, named ‘Klexel’.

Some Bugs of my LXDE-based Computer, ‘Klexel’

I wrote only yesterday, that I had set up a computer with the Linux desktop-manager ‘LXDE’, and that I had named that computer ‘Klexel’.

Well I’m finding out that this computer has a bug. If I leave it with its screen-locker locked for some time, and then unlock with my password, the unlock dialog seems to succeed, but only reveals a black desktop, with only the mouse-pointer visible.

I suspect that I know what causes this. The computer in question has an old ‘Intel 910′ graphics chip-set, and although it may be good the the chip-set is supported, that chip-set and its drivers have quirks. I do have OpenGL 1.4, which should be high enough a version. But it may be that ‘behind the screen-locker’, by the time I’ve unlocked the machine again, the ‘Compiz Fusion’ desktop compositor has crashed.

There are certain other quirks which point to a graphics chip problem:

  • The window title-bars sometimes don’t render, until I click in the region where the title-bar should be, in which case they reappear.
  • Wobbly Windows needs to be enabled, in order for me to be able to restore the title-bars in this simple way.

I found that a practical way to deal with this not-resuming from the screen-locker, may be, by setting the key-sequence <Ctrl>+<Alt>+<Backspace> just to kill the X-server, as it would do under KDE or Plasma 5, using the following customization. I can right-click on the Keyboard Layout Tray Icon, then left-click on “Keyboard Layout Handler Settings”, and then:

screenshot-from-2018-09-02-06-21-12_c

I have set 2 ‘setxkbmap Options':

  1. The Compose Key,
  2. The X-server kill key.

Killing the X- just prompts me for a log-in again.

Note:

There is some possibility that the Compiz crash, on resuming from a plain lock-screen, may have to do with the Compiz setting, to display a Splash Image. By default, Kanotix systems come with an animated Kanotix splash-screen, that may look nice on systems with stable graphics, and for the first few times the system is explored. We can change this splash-screen to something other than the Kanotix splash-screen.

But I have noticed that, just for Compiz to start the splash-screen, causes instability with the Intel 910 chip-set, even if it does work. So what may be happening, is that on resuming from the lock-screen, Compiz may be programmed to display the splash-screen, and doing so may be what crashes my session. And so for now, I’ve also disabled this feature, and will comment later, on whether having done so has fixed the crashes.

(Update 09/05/2018, 15h30 … )

(As of 09/02/2018 : )

Continue reading Some Bugs of my LXDE-based Computer, ‘Klexel’

Just Installed Kanotix Steelfire on one of my Boxes

For more than a week, I was worried about Kanotix, because their Web-site was down. But after just checking today, I found it was up again! :-)  It has been a habit of mine to install initial Debian systems, from Kanotix Live Disks.

I already posses a powerful computer which I name ‘Plato’, onto which I installed Debian / Stretch by way of an experimental Live Disk from Kanotix, but cannot fully say that that one is a Kanotix computer, because at the time, Kanotix didn’t have an official Debian / Stretch release yet. What I did have was two systems running the slightly older Debian / Jessie, and the official Kanotix release with that, is called “Kanotix Spitfire”.

But what I also had for some time, was a weaker PC that still had Debian / Lenny on it, which was an antique system, that required its own security measures, just not to pose a vulnerability to me.

My special security measure for that computer, was just never to turn it on. In fact, it had no eligible Web-browser. But like that, because the hardware was still good, this represented wasted hardware, just sitting in my computer room.

So, now that the Kanotix site is back up, what I did was to download a 32-bit, LXDE Disk Image, of “Kanotix Steelfire”, which is by now their official Debian / Stretch release. In principle many people, including Kanotix experts, would agree that it makes more sense to use as desktop manager, Plasma 5, but as it happens, the computer that just received a new O/S is so weak in terms of RAM and graphics chip-set, that I didn’t think it could handle Plasma 5.

The newly-set-up computer used to be named ‘Walnut’, but is now to be named ‘Klexel’. It has as graphics acceleration, an old Intel chip-set, which Kanotix distributions actually support, in the form of ‘i915 support’. This is neither an Nvidia, nor an AMD/ATI chip-set. But amazingly, I do have some level of direct-rendering with it, and, in addition, I have Compiz Fusion on that box now, and at least, the 3D desktop-switching belonging to Compiz works!

So now, with ‘Klexel’ wiped, I can take my time with it, and install what I think it should have. But what will slow me down a bit, is the fact that I’m not used to LXDE as a main window-manager. In the past I goofed around with LXDE a bit, but now, this is going to be Klexel’s window manager, under which the GUI is arranged differently, from what I’m used to.

(Update 09/01/2018, 23h10 : )

(As of 09/01/2018, 21h35 : )

Continue reading Just Installed Kanotix Steelfire on one of my Boxes