what is "Software" supposed to do with Pending?

asked 2016-08-22 09:54:47 -0600

This post is a wiki. Anyone with karma >750 is welcome to improve it.

I have recently upgraded to fedora23 .

I note DNF is replacing YUM.

So I can use dnf(1) on the command line and all is well. However if I use the GUI Activites -> "type to search" yum, it offers Yum Extender (DNF) , which I'm guessing is a DNF flavour of the yum extender GUI ... I'll go for that.

I choose it, it pops up a pretty screen shot and offers install . A bit of poking around with xprop(1) suggest ths is a GUI called "Software" .. can't see what the actual command is (so can't read the man page of find the config files) I click on the install button and it changes to "pending" ...then nothing else. I've done this a few time and now have 3 copies saying "pending" I also launched "Software" via the same Activites -> "type to search" Software and it gives the same GUI , anything I add just changes to "pending" across are 3 tabs All, Installed(7), Updates ... selecting updates shows a grey page with "Go online and check for updates" [Network Settings] if I choose [Network settings] it simply shows my proxy settings (which are correct)

The GUI seems to be waiting to do something . Since it's not doing it and I can't find the command name hence the man page and config setup I can't see what it's waiting for . If I were to guess I'd say it's ignoring the proxy settings , but it's a closed box , can't see what it really is trying to do.

edit retag flag offensive close merge delete

Comments

in regards to yum extender you are guessing right. Program is called yumex-dnf but it's not always working correctly. It should show up as Yumex DNF, or so.

Software is something else, it's the program gnome-software which use PackageKit. Unfortunately, PackageKit and DNF do not use the same database for transaction. That means one doesn't know what the other did, which can result in a weird state. Best would currently be, to only use dnf.

florian ( 2016-08-22 15:01:54 -0600 )edit

If I use the GUI at all: activities -> type to search, it uses a GUI tool (gnome-software I guess?) whenever it does have the application already installed. So I can't really avoid it getting involved. Having found the tool was "Yum Extender (DNF)" I'd just goto the dnf command to install it ... but of course that does not give me the real package name to install (which I now guess is yumex-dnf) all seems a bit ill thought out ;-(

graemev ( 2016-08-24 12:44:53 -0600 )edit

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2016-08-22 14:58:20 -0600

davidva
3965 ●10 ●56 ●72 http://www.kuboosoft.b...

mmm, without a log, impossible help you...

Open a terminal and write...

gnome-software --verbose | tee $HOME/gnome_software-log

not finished?

Ctrl + c

Now share the log in your home "gnome_software-log"

edit flag offensive delete link

add a comment

answered 2016-08-24 12:38:30 -0600

graemev
13 ●3 ●5 ●8

updated 2016-08-24 14:19:46 -0600

florian
11133 ●77 ●349 ●331

an attempt to add the log says "60 points are needed to upload files" ... so I'll need to C&P inline here .... it's going to be big sadly:

(gnome-software:3078): Gs-DEBUG: compatible-project: GNOME
(gnome-software:3078): Gs-DEBUG: compatible-project: KDE
(gnome-software:3078): Gs-DEBUG: compatible-project: XFCE
(gnome-software:3078): As-DEBUG: run GsPlugin::setup
(gnome-software:3078): Gs-DEBUG: searching for plugins in /usr/lib64/gs-plugins-9
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_hardcoded-featured.so: hardcoded-featured
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_fwupd.so: fwupd
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_packagekit.so: packagekit
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_systemd-updates.so: systemd-updates
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_provenance.so: provenance
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_packagekit-offline.so: packagekit-offline
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_moduleset.so: moduleset
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_epiphany.so: epiphany
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_packagekit-refine.so: packagekit-refine
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_packagekit-proxy.so: packagekit-proxy
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_packagekit-origin.so: packagekit-origin
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_appstream.so: appstream
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_icons.so: icons
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_dummy.so: dummy
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_fedora_distro_upgrades.so: fedora-distro-upgrades
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_menu-spec-categories.so: menu-spec-categories
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_fedora_tagger_usage.so: fedora-tagger-usage
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_packagekit-refresh.so: packagekit-refresh
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_packagekit-history.so: packagekit-history
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_menu-spec-refine.so: menu-spec-refine
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_hardcoded-blacklist.so: hardcoded-blacklist
(gnome-software:3078): Gs-DEBUG: opened plugin /usr/lib64/gs-plugins-9/libgs_plugin_packagekit-upgrade.so: packagekit-upgrade
(gnome-software:3078): Gs-DEBUG: provenance [0.0] to be ordered after packagekit-refine [0.0] so promoting to [1.0]
(gnome-software:3078): Gs-DEBUG: moduleset [0.0] to be ordered after menu-spec-categories [0.0] so promoting to [1.0]
(gnome-software:3078): Gs-DEBUG: epiphany [0.0] to be ordered after appstream [0.0] so promoting to [1.0]
(gnome-software:3078): Gs-DEBUG: packagekit-refine [0.0] to be ordered after appstream [0.0] so promoting to [1.0]
(gnome-software:3078): Gs-DEBUG: provenance [1.0] to be ordered after packagekit-refine [1.0] so promoting to [2.0]
(gnome-software:3078): Gs-DEBUG: packagekit-origin [0.0] to be ordered after packagekit-refine [1.0] so promoting to [2.0]
(gnome-software:3078): Gs-DEBUG: appstream [0.0] to be ordered after menu-spec-categories [0.0] so promoting to [1.0]
(gnome-software:3078): Gs-DEBUG: moduleset [1.0] to be ordered after appstream [1.0] so promoting to [2.0]
(gnome-software:3078): Gs-DEBUG: epiphany [1.0] to be ordered after appstream [1.0] so promoting to [2.0]
(gnome-software:3078): Gs-DEBUG: packagekit-refine [1.0] to be ordered after appstream [1.0] so promoting to [2.0]
(gnome-software:3078): Gs-DEBUG: provenance [2.0] to be ordered after packagekit-refine [2.0] so promoting to [3 ...

(more)

edit flag offensive delete link

Comments

For future reference, please:

1.) Try to edit your inital question and do not post additional information as answer (as it isn't one)

2.) Try formatting the pasted text nicely so that it is better readable (I quickly did that for you by marking the text and clicking on the 101010 icon, the fifth from the left)

3.) You can always link to outputs that you can upload here: fpaste.org

florian ( 2016-08-24 14:17:53 -0600 )edit

add a comment

what is "Software" supposed to do with Pending?

Comments

2 Answers

Comments

Question Tools

Stats

Related questions

what is "Software" supposed to do with Pending? edit

Comments

2 Answers

Comments

Question Tools

Stats

Related questions

what is "Software" supposed to do with Pending?