Bug 1535744 - gnome-software does nothing when clicking "install" (UnknownMethod: Method "Reboot")
Summary: gnome-software does nothing when clicking "install" (UnknownMethod: Method "R...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-software
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-18 00:57 UTC by Basic Six
Modified: 2021-05-25 14:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 14:57:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Basic Six 2018-01-18 00:57:52 UTC
Description of problem:

It's not possible to upgrade a Fedora 26 installation to Fedora 27 using the gnome-software gui. When clicking "Install", it asks for a password, but nothing happens after that. It's almost like a dead button.

In Bug 1370596, I've already complained about the fact that it doesn't work in KDE and that the program is not handling this error case properly because it doesn't show an error message.

In this case, the system is running Mate, where gnome-software used to work. The lack of an error message makes it difficult to guess why it doesn't work anymore.



Version-Release number of selected component (if applicable):

Fedora 26.



How reproducible:

Always.



Steps to Reproduce:
1. gnome-software
2. click "Install"
3. Nothing



Actual results:

Downloading the upgrade seems to work. Restarting the system to initiate the upgrade is what doesn't work. In addition to that, gnome-software does not handle this error case and thus won't tell the user that it didn't work and why. The user would just sit there and wait, assuming the upgrade would start after some time.



Expected results:

The upgrade should start OR a meaningful error message should be shown that says why it didn't start.



Additional info:

This is what's printed to the console:

23:36:24:0231 Gs  State change on */*/*/os-update/org.gnome.Software.OsUpdate/* from updatable to installed is not OK
23:36:24:0233 Gs  Calling org.gnome.SessionManager.Reboot failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "Reboot" with signature "" on interface "org.gnome.SessionManager" doesn't exist

Comment 1 Fedora End Of Life 2018-05-03 08:00:01 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2018-05-29 11:27:35 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Basic Six 2021-05-07 12:01:47 UTC
It's 2021 now and this official Fedora system update tool is still broken. Three years have passed since this bug was initially reported and five years have passed since Bug 1370596 was reported for the same issue in KDE. Let's put aside KDE for a moment, as this bug is about Mate, which is a Gnome fork.

I'm not even asking why the reboot isn't working, I'm asking why you don't have any error handling and show a dead Install button. Would it be too much to have a tiny little message pop up after clicking "Install", saying that the tool is attempting to restart the system to initiate the upgrade - in the Fedora version of this tool? Many tools are patched by the distribution in one way or another. Please don't say it's an upstream bug and forget about it while at the same time, you tell users that this tool is the official way to upgrade Fedora to the next release. I understand that software has bugs, sometimes even critical core components of the operating system like in this case, but it shouldn't take too much time for the Fedora team to either add a somewhat meaningful Install note to the Fedora version of the tool or remove the tool from the documentation completely because Fedora hasn't had a reliable upgrade tool in at least five years and end users shouldn't rely on Fedora as they might not be able to keep it up to date.

Comment 4 Ben Cotton 2021-05-25 14:57:58 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.