On Monday 18 Jan 2016 20:38:10 Bruno Friedmann wrote:

On Monday 18 January 2016 16.01:35 ianseeks wrote:

...

On Monday 18 Jan 2016 15:38:26 Wolfgang Bauer wrote:

...

Am Montag, 18. Januar 2016, 13:05:07 schrieb ianseeks:

...

On Monday 18 Jan 2016 12:46:34 Wolfgang Bauer wrote:

...

Am Sonntag, 17. Januar 2016, 18:31:03 schrieb ianseeks:

...

Shouldn't the install process also automatically stop akonadi for you?

No, that's impossible.

The update/install process is running as root, it cannot stop the users' akonadi(s) that might be running.

Well, it could kill them of course, but that would cause the same possible problems that not stopping Akonadi before the update manually would be able to cause I think.

Could it not pop up a warning that says, "please stop akonadi (with the example command)...... and press Y when done?" I think doing this type of user friendly action makes the process more professional and will hopefully stop a few bug reports

No. You have the same problem again. The installation process running as root cannot connect to the users' X or DBUS session.

its a shame that there is no way round it, it makes parts of installation process difficult to fully automate

Well I consider it as administrative tasks. Now we all know we shouldn't have akonadi running during the update.

So from an admin point of view it quite simple: ask an user logged to get out and keep them away from the system man nologin could help.

Once you're sure there no more user process reunning fire up a zypper up/dup and it's done.

Do we really want to have to reboot like some systems to be able to make an update, not me as far I'm concern. certainly not.. their install process is shit :o)

This is a special case that needs migration and update. I would have thought a migration process should cater for dependencies in some way. The problem is that there may be ordinary users (e.g. my gran) who do not subscribe to these lists who will not know about it and will not have a clue how to stop akonadi. The current process is fine for Admins and developers. Perhaps there needs to be a way for a the process to find out which user launched its update session and then check if akonadi is running for that user. Or the update process creates an autostart file that runs the migration/update on log in before akonadi is started (if thats possible, i don;t know). -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org