This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Stacer weirdness in Fossa

Tags: None
(comma "," separated)
mossbliss
Registered Member
Posts
14
Karma
0

Stacer weirdness in Fossa

Sat Aug 15, 2020 6:52 pm
I just installed KDE neon latest, and upgraded to Focal Fossa. I installed the things I usually install. One of those things is the system management tool, Stacer. I installed the latest version, 1.1.0.

It worked, but immediately Discover told me there was an update. I ran the update. Then I tried to restart Stacer and it said the program could not be found. So I reinstalled it again from my .deb and it worked again. And Discover immediately told me there was an upgrade.

If the "upgraded" version does not work, why should I upgrade it? And how can I mark Discover to ignore upgrades for this package?
User avatar
claydoh
Registered Member
Posts
1170
Karma
9
OS

Re: Stacer weirdness in Fossa

Sat Aug 15, 2020 7:13 pm
Why install the manually downloaded deb? 20.04 has the latest 1.1.0 in the normal repos. It installs from Discover or the command line and runs as expected for me here on my systems.

A deb file usually needs to be for the specific distro and release you are running, perhaps your deb is for a different ubuntu version, and/or puts its files in slightly different locations than your system is expecting? Can't tell as we don't know where you got the file from.


claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
mossbliss
Registered Member
Posts
14
Karma
0

Re: Stacer weirdness in Fossa

Sat Aug 15, 2020 10:43 pm
claydoh wrote:Why install the manually downloaded deb? 20.04 has the latest 1.1.0 in the normal repos. It installs from Discover or the command line and runs as expected for me here on my systems.

A deb file usually needs to be for the specific distro and release you are running, perhaps your deb is for a different ubuntu version, and/or puts its files in slightly different locations than your system is expecting? Can't tell as we don't know where you got the file from.

I assume that the update Discover wants to do is what's in the repo. So why doesn't it run? And I'm sorry, I had no clue Stacer ,ade it into the repo.
User avatar
claydoh
Registered Member
Posts
1170
Karma
9
OS

Re: Stacer weirdness in Fossa

Sat Aug 15, 2020 11:58 pm
mossbliss wrote:I assume that the update Discover wants to do is what's in the repo. So why doesn't it run? And I'm sorry, I had no clue Stacer ,ade it into the repo.


Not knowing the source of your deb file, it may be that it is not made for 20.04. The package itself may have a name/versioning that makes Discover/apt see it as older than the one in the repo.

Again not knowing where you got the file, it may be putting files in different places than what is correct, or it may be looking for libraries that are different than what you have on 20.04. If you ran it from the terminal, you probably would see an error saying it can't find something.

Deb files are almost always specifically made for a specific distro release. A deb made for 18.04 usually will not run on 20.04 due to different system files and libraries.


claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001


Bookmarks



Who is online

Registered users: bartoloni, Bing [Bot], Google [Bot], Sogou [Bot]