Opened 2 years ago

Closed 2 years ago

#13443 closed bug (fixed)

SoftwareUpdater (as GUI) is slow to check for updates and gave errors

Reported by: Giova84 Owned by: perelandra
Priority: normal Milestone: Unscheduled
Component: Applications/SoftwareUpdater Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

hrev51122

When I run the SoftwareUpdater (as GUI), after a while (also about a minute, while it says "validating checksum") I got an error message which claims "Refreshing repository "Haiku" - or "HaikuPorts - failed". On my system I halso have a 3rd party repository (the which one from Michel Clasquin-Johnson) and I see no errors from his repository.

Please notice that the repos for Haiku and HaikuPorts, on my system, are https://packages.haiku-os.org/haiku/master/x86_gcc2/current and https://packages.haiku-os.org/haikuports/master/repo/x86_gcc2/current

Furthermore, it takes also a while of time on "Contacting software repositories to check for updates": seems very slow, and is not a fault of my connection: in facts, if from a Terminal window I run "SoftwareUpdater check" is very quick to do all these processes.

Change History (13)

comment:1 Changed 2 years ago by perelandra

What happens when you run 'pkgman update' in Terminal?

comment:2 Changed 2 years ago by Giova84

Nothing special: is fast and quick as SoftwareUpdater check.

comment:3 Changed 2 years ago by perelandra

Very strange. Runs quick from an updated hrev51122 on my test laptop. Did you do a reboot after updating to 51122? Can you run 'SoftwareUpdater update' from the Terminal and post the output?

Last edited 2 years ago by perelandra (previous) (diff)

comment:4 Changed 2 years ago by Giova84

Well, I went in the "Repositories" app, and here I have disabled and then enabled again all repos: now Software Updater no longer gave me errors and is quick and fast. Maybe is someting related to the repositories cache?

comment:5 Changed 2 years ago by perelandra

Hmm that reset something. I have seen some issues using the http:// url for the repositories but you said you were using the https:// ones. I will leave this ticket open for a while in case anyone else comes across the same issue.

comment:6 Changed 2 years ago by perelandra

Are you running x86_64 and did you get a crash of SoftwareUpdater before seeing this behavior? I was able to see this after replicating the crash reported in #13445.

Last edited 2 years ago by perelandra (previous) (diff)

comment:7 Changed 2 years ago by Giova84

Nope, I'm running gcc2_hybrid, and I didn't see any crash of the application,

However I noticed another issue. in this commit: https://cgit.haiku-os.org/haiku/commit/?id=b105213b81b4536f6d06f4462f3e008ddc02808e you declared that

"New prompt at application start to choose between doing an Update or a Full Sync. Also lays the ground work for implimenting silent check-only feature."

But when i started for the first time SoftwareUpdater, I didn't see any prompt which asked me to choose between doing an Update or a Full Sync. So I tried to see if from the Terminal would be possible to see any hints about usage: i run SoftwareUpdater --helpand I didn't see any help about usage as I expected, but however SoftwareUpdate showed me such prompt where to choose which action to perform: "Update, Full Sync or only Check"

comment:8 in reply to:  7 Changed 2 years ago by perelandra

Replying to Giova84:

"New prompt at application start to choose between doing an Update or a Full Sync. Also lays the ground work for implimenting silent check-only feature."

But when i started for the first time SoftwareUpdater, I didn't see any prompt

Yes this was before the command arguments were implemented. Most of the time an update should be done, and some people were finding the choice confusing. Now if you don't define a mode then update is used by default.

SoftwareUpdater --helpand I didn't see any help about usage as I expected, but however SoftwareUpdate showed me such prompt where to choose which action to perform: "Update, Full Sync or only Check"

Command options --help and --verbose are coming in the next release v1.0.1. If you give an option it does not recognize then you will get prompted for which mode to use.

comment:9 Changed 2 years ago by Giova84

From what I can understand, SoftwareUpdater is a "work in progress", so I'll wait to open "enhancements" tickets. Are you planning to implement a sort of preference panel or a config file (currently, at least on my system, i don't see a config file of SoftwareUpdate) where to store the default action? (Update, Full-Sync, only check)? I was think that a first/draft implementation (also to set a schedule to check for updates) would be, in the main window of SoftwareUpdater, to add a menu. What do you think about?

comment:10 Changed 2 years ago by humdinger

Are you planning to implement a sort of preference panel ...

This has been discussed a bit on the dev mailing lists's thread Time to add SoftwareUpdater to build?

comment:11 in reply to:  9 ; Changed 2 years ago by perelandra

Replying to Giova84:

From what I can understand, SoftwareUpdater is a "work in progress", so I'll wait to open "enhancements" tickets.

Go ahead, I am working on the next revision so if you have ideas I may add them. Right now I consider SU to be functional in it's core ability to do updates. It's just some tweaking to be done.

Are you planning to implement a sort of preference panel or a config file (currently, at least on my system, i don't see a config file of SoftwareUpdate) where to store the default action? (Update, Full-Sync, only check)?

I don't think I will at this time. First there is no built-in scheduling system in Haiku yet. Second, notifications totally disappear when they time out so if you are not at the computer when the check runs you will never see the notification. Of course there are third party schedulers out there that some have used but that will be up to the user for now.

comment:12 in reply to:  11 Changed 2 years ago by humdinger

Replying to perelandra:

Second, notifications totally disappear when they time out so if you are not at the computer when the check runs you will never see the notification.

Isn't it possible to disable the timeout for a notification? IMO the notification of available updates (maybe only for system packages) could very well be displayed until the user actively clicked on it. This behaviour could be the default and changed in the Notification prefs (once that part of the panel is working... :) ).

comment:13 Changed 2 years ago by perelandra

Resolution: fixed
Status: newclosed

Sounds like an issue with a correupt repo cache that got resolved by a refresh.

Note: See TracTickets for help on using tickets.