something wrong with plasma update widget since 2017

[Peter G.]

The update widget runs automatically, even though I turned off 
automatic updates in system settings. Still, when I right-
click on the widget, a completely different and reduced set of 
options appears, which does not include turning it off.

While I don't mind it running, even though I do all of my 
system updating on the command line, the widget runs every 
hour or more, it would appear and generates endless error 
output, always the following:

"The task was forcibly canceled The task was canceled 
successfully and no packages were changed.

The backend did not exit cleanly."

How can I either have it run correctly or just turn it off?

[Rex Dieter]

Peter G.  wrote:

>  The update widget runs automatically, even though I turned off
>  automatic updates in system settings. Still, when I right-
>  click on the widget, a completely different and reduced set of
>  options appears, which does not include turning it off.
>  
>  While I don't mind it running, even though I do all of my
>  system updating on the command line, the widget runs every
>  hour or more, it would appear and generates endless error
>  output, always the following:
>  
>  "The task was forcibly canceled The task was canceled
>  successfully and no packages were changed.
>  The backend did not exit cleanly."
>  
>  How can I either have it run correctly or just turn it off? 
It means the packagekit daemon (that handles installs/upgrades) encountered 
an error and/or crashed.

To turn it off, right click ^ in system tray => system tray settings => 
general => extra items => (uncheck) "Software updates"

-- Rex

[Peter G.]

Rex Dieter wrote:

>  To turn it off, right click ^ in system tray => system tray 
settings =>
>  general => extra items => (uncheck) "Software
> updates" 
Thanks!

[Peter G.]

Peter G.  wrote:

>  Rex Dieter wrote:
>  
> > To turn it off, right click ^ in system tray => system tray
>  settings =>
> > general => extra items => (uncheck) "Software updates"
>  
>  Thanks! 
That DIDN'T WORK!!!?

I've done that AND I've got updates turned off in system 
settings and I JUST NOW got yet another _backend did not exit 
cleanly_ message!

What is causing this? Could Gnome* have a secret update 
program running in the background that I don't know about?

*When I install, I just use the regular install image and the 
first command I run is dnf install '@KDE Plasma Workspaces'.

[Reindl Harald]

Am 08.02.2017 um 17:33 schrieb Peter G.:
>  Peter G.  wrote:
>
> > Rex Dieter wrote:
> >
> >> To turn it off, right click ^ in system tray => system tray
> > settings =>
> >> general => extra items => (uncheck) "Software updates"
> >
> > Thanks!
>
>  That DIDN'T WORK!!!?
>
>  I've done that AND I've got updates turned off in system
>  settings and I JUST NOW got yet another _backend did not exit
>  cleanly_ message!
>
>  What is causing this? Could Gnome* have a secret update
>  program running in the background that I don't know about?
>
>  *When I install, I just use the regular install image and the
>  first command I run is dnf install '@KDE Plasma Workspaces' 
just try to uninstall packagekit and friends and use dnf/yum regulary

[harry@srv-rhsoft:~]$ rpm -qa | grep -i package
python3-javapackages-4.6.0-15.fc24.noarch
PackageKit-Qt5-0.9.5-6.fc24.x86_64
kf5-kpackage-5.29.1-3.fc24.x86_64
fontpackages-filesystem-1.44-17.fc24.noarch
javapackages-tools-4.6.0-15.fc24.noarch
[harry@srv-rhsoft:~]$

[Reindl Harald]

Am 08.02.2017 um 17:36 schrieb Reindl Harald:
>  Am 08.02.2017 um 17:33 schrieb Peter G.:
> > Peter G.  wrote:
> >
> >> Rex Dieter wrote:
> >>
> >>> To turn it off, right click ^ in system tray => system tray
> >> settings =>
> >>> general => extra items => (uncheck) "Software updates"
> >>
> >> Thanks!
> >
> > That DIDN'T WORK!!!?
> >
> > I've done that AND I've got updates turned off in system
> > settings and I JUST NOW got yet another _backend did not exit
> > cleanly_ message!
> >
> > What is causing this? Could Gnome* have a secret update
> > program running in the background that I don't know about?
> >
> > *When I install, I just use the regular install image and the
> > first command I run is dnf install '@KDE Plasma Workspaces'
>
>  just try to uninstall packagekit and friends and use dnf/yum regulary
>
>  [harry@srv-rhsoft:~]$ rpm -qa | grep -i package
>  python3-javapackages-4.6.0-15.fc24.noarch
>  PackageKit-Qt5-0.9.5-6.fc24.x86_64
>  kf5-kpackage-5.29.1-3.fc24.x86_64
>  fontpackages-filesystem-1.44-17.fc24.noarch
>  javapackages-tools-4.6.0-15.fc24.noarch
>  [harry@srv-rhsoft:~]$ 
and the same for all that gnome crap without hard dependencies

[harry@srv-rhsoft:~]$ rpm -qa | grep gnome
gnome-vfs2-common-2.24.4-20.fc24.noarch
libgnomecanvas-2.30.3-11.fc24.x86_64
gnome-python2-canvas-2.28.1-17.fc24.x86_64
polkit-gnome-0.105-10.fc24.x86_64
gnome-python2-gconf-2.28.1-17.fc24.x86_64
libgnome-keyring-3.12.0-6.fc24.x86_64
libgnomeui-2.24.5-12.fc24.x86_64
gnome-python2-2.28.1-17.fc24.x86_64
libgnome-2.32.1-11.fc24.x86_64
gnome-python2-gnome-2.28.1-17.fc24.x86_64
gnome-python2-gnomevfs-2.28.1-17.fc24.x86_64
gnome-python2-bonobo-2.28.1-17.fc24.x86_64
gnome-vfs2-2.24.4-20.fc24.x86_64
[harry@srv-rhsoft:~]$

"dnf leaves" may help

[root@srv-rhsoft:~]$ rpm -qa | grep dnf | grep leaves
python3-dnf-plugins-extras-leaves-0.0.12-3.fc24.noarch
python3-dnf-plugins-extras-show-leaves-0.0.12-3.fc24.noarch

[Peter G.]

Reindl Harald wrote:

>  just try to uninstall packagekit and friends and use dnf/yum 
regulary
>  
>  [harry@srv-rhsoft:~]$ rpm -qa | grep -i package
>  python3-javapackages-4.6.0-15.fc24.noarch
>  PackageKit-Qt5-0.9.5-6.fc24.x86_64
>  kf5-kpackage-5.29.1-3.fc24.x86_64
>  fontpackages-filesystem-1.44-17.fc24.noarch
>  javapackages-tools-4.6.0-15.fc24.noarch 
I might have to resort to that, but...

NOW, I really am curious! What program is running? How can I 
find out?

I ran the leaves command and it returned nothing! Does that 
mean anything?

[Peter G.]

Peter G.  wrote:

>  That DIDN'T WORK!!!?
>  
>  I've done that AND I've got updates turned off in system
>  settings and I JUST NOW got yet another _backend did not exit
>  cleanly_ message! 
A system restart solved it.