KDE: update process remains at 49%

[dolphin_oracle]

I knew there was a reason I didn't really trust Discover with serious tasks ....

Obviously it seems to be that Discover itself is not the basic problem, because Discover works in KDEneon without any problems!
In my post https://forum.mxlinux.org/viewtopic.php?t=71839, concerning this problem, fehlix gave a very interesting answer:

Scheint mit Discover zusammenzuhängen.
Es gibt drei/vier Dateien mit kleinen MX Anpassungen , die Debian gern mit seinen neueren Versionen ersetzten möchte, da wartet es möglicher weise im Hintergrund auf Bestätigung und hängt.

I try to translate: "This seems to be in connection with Discover. There are three/four files with little MX adaptions, Debian would like to replace with newer versions, possibly the system is waiting in the background for confirmation."
This sounds rather that it's a problem of adaption to MX-system.

Cheers
Giova85

All the other apt system managers allow an interface for those kind of questions to be asked. Discover does not. Maybe later discovers will.

[asqwerth]

Obviously it seems to be that Discover itself is not the basic problem, because Discover works in KDEneon without any problems!
In my post https://forum.mxlinux.org/viewtopic.php?t=71839, concerning this problem, fehlix gave a very interesting answer:

Scheint mit Discover zusammenzuhängen.
Es gibt drei/vier Dateien mit kleinen MX Anpassungen , die Debian gern mit seinen neueren Versionen ersetzten möchte, da wartet es möglicher weise im Hintergrund auf Bestätigung und hängt.

I try to translate: "This seems to be in connection with Discover. There are three/four files with little MX adaptions, Debian would like to replace with newer versions, possibly the system is waiting in the background for confirmation."
This sounds rather that it's a problem of adaption to MX-system.

Cheers
Giova85

I do use KDE Neon (Dev edition). I can't answer your points for sure, but I am almost certain this has nothing to do with MX and everything to do with Debian. 2 points:

1. Neon is based on Ubuntu, not Debian. MX is Debian-based. As far as I know, in Debian, whenever there is an update to a package that ships with a vanilla config file, the system will ask you whether to replace or keep config files already on your system. Even if you use Synaptic or MX-updater (I tested it with both apt and nala), you do get asked those questions. Only Discover did not.

Note that it doesn't have to be changes to the config file created by MX-system. I recall similar questions pop up when the user him/herself has made changes to the config of a program. Eg I recall previous updates to lighdm where I was asked to answer questions [whether to keep current config or replace with lightdm dev's vanilla config file], and it happened because I had changed the lightdm config file by changing the default background wallpaper on my lightdm login page.


2. The Plasma version in KDE Neon is newer than in Debian Stable. It might be that the Discover in that version has been improved.

On the other hand, I don't use Discover in Neon either. I use the command
sudo pkcon update
to update the system. [https://blog.neon.kde.org/2017/06/16/ho ... -software/ ] This is supposed to be the same packagekit backend command used in Discover.

Even so, my last update of Neon led to incomplete post-install configuration (I believe there was a grub update as well), and I had to use

sudo dpkg --configure --pending

to sort out all the unfinished package configurations and triggers.

No questions popped up during upgrade.

[Giova85]

Many thanks for your extensiv answer!

Your arguement 1.:
Absolutely right! I wasn't asked as well.

"because I had changed the lightdm config file by changing the default background wallpaper on my lightdm login page"

sounds really adventurous.

Your argument 2.:
Different versions might be the handycap!
The better way for updating is surely "sudo pkcon update" what I usually use as well.
But concerning the problem, I used Discover to learn what's happening.
I didn't have any problems. Surely our systems are somehow different. I don't know the reason for that.
In my case there were no questions concerning the update as well.

Looking at the overall scenery:
I don't know, how developers of different linux systems are communicating. But: MX-Linux is market-leader since years. So you do have a mighty position.
This enables you to take influence on important participants of the linux world. Even on KDE!
Don't forget that.

Cheers
Giova85

[Adrian]

MX-Linux is market-leader

We are leader of what market?

[asqwerth]

......
But concerning the problem, I used Discover to learn what's happening.
I didn't have any problems. Surely our systems are somehow different. I don't know the reason for that.
....

Are you using the standard user version of KDE Neon, or the Developer version? Mine is the latter one.

...MX-Linux is market-leader since years. So you do have a mighty position.
This enables you to take influence on important participants of the linux world. Even on KDE!.....

I'm afraid you are mistaken if you think MX has any influence on Debian or Plasma development. MX just uses whatever version of Plasma is in Debian Stable at that time. And that version of Plasma is always older than what is available on rolling distros and KDE Neon.

The Distrowatch list just shows which distro has the most number of clicks on that site. It has nothing to do with number of MX users.

[Giova85]

I know about distrowatch and what it shows.
But you should not forget one fact: People who are curious about Linux use distrowatch to get first impressions about what is the market and the products.
So this gives a first impression about potential customers. No curiosity, no customer!
In comparison to other distributions, MX has a unique selling point:
The general opinion about Linux is: This is s.th. for nerds and experts, because people learned that you have to use a commandline to fix problems. And that means you should know a lot about codes to be used there.
MX now takes that fear away by creating MX-tools. I.e.: Many scripts are ready to be used to fix a lot of common problems by using them with a grafical interface. This closes a big gap and brings users closer to a system.
Looking around, there are lots of people discussing MX-Linux. And I think, this is a mighty position. Probably you can see at your servers how figures of access are developing.
I am sure, your market is growing.
And finally, even Plasma and Debian are of course interested in being used by distributions. First of all in growing and modern ones.
So for sure you do have influence if you try to have some.

Cheers
Giova85