You are not logged in.
Devuan 4.0
Message reads:
Unable to load applications.
Please verify Internet connectivity.
Is this a sources.list issue?
I have REM'd out the line pointing to the CD as I have done with previous installs for Devuan 3.0 and 3.1.1
Last edited by swarfendor437 (2021-12-20 22:28:45)
Offline
Discover just isn't working at all. When I enter the root password to edit the settings it falls over (cannot access settings). If I select 'Ignore' it states I should start Discover with the command:
kdesudo
which results in no such command.
Have repositories changed?
Currently I have:
Chimaera (main)
Chimaera security (main contrib non-free)
Chimaera updates (main contrib non-free)
I have unchecked the 'Sources'
Offline
Can't comment on Discover and KDE, not my DE.
But what hits my eyes is that for Chimaera you just have enabled main. And for the others also contrib nonfree. Does not make sense. Either all in or all out.
rolfie
Last edited by rolfie (2022-03-01 22:05:55)
Online
Can't comment on Discover and KDE, not my DE.
But what hits my eyes is that for Chimaera you just have enabled main. And for the others also contrib nonfree. Does not make sense. Either all in or all out.
rolfie
That is all that is available to me - should I keep the 'sources' in? Guess it's because I have come from a different GNU/Linux prior to Devuan.
Thanks for your time and input.
Offline
FWIW here is my sources.list:
$ cat /etc/apt/sources.list
deb http://deb.devuan.org/merged chimaera main non-free contrib
deb http://deb.devuan.org/merged chimaera-security main non-free contrib
deb http://deb.devuan.org/merged chimaera-updates main non-free contrib
deb http://deb.devuan.org/devuan chimaera-proposed-updates main non-free contrib
deb http://deb.devuan.org/merged chimaera-backports main non-free contrib
Offline
rolfie wrote:Can't comment on Discover and KDE, not my DE.
But what hits my eyes is that for Chimaera you just have enabled main. And for the others also contrib nonfree. Does not make sense. Either all in or all out.
rolfie
That is all that is available to me - should I keep the 'sources' in? Guess it's because I have come from a different GNU/Linux prior to Devuan.
Thanks for your time and input.
Looks like I wasn't clear enough. You wrote:
Chimaera (main)
Chimaera security (main contrib non-free)
Chimaera updates (main contrib non-free)
This is inconsistant. Your entries in the sources.list should read either full blown:
deb http://deb.devuan.org/merged chimaera main non-free contrib
deb http://deb.devuan.org/merged chimaera-security main non-free contrib
deb http://deb.devuan.org/merged chimaera-updates main non-free contrib
deb http://deb.devuan.org/devuan chimaera-proposed-updates main non-free contrib
deb http://deb.devuan.org/merged chimaera-backports main non-free contrib
which I would suggest or
deb http://deb.devuan.org/merged chimaera main
deb http://deb.devuan.org/merged chimaera-security main
deb http://deb.devuan.org/merged chimaera-updates main
deb http://deb.devuan.org/devuan chimaera-proposed-updates
deb http://deb.devuan.org/merged chimaera-backports main
if you don't want non-free packages or packages with other licences on your computer. It simply has to be all the same through the lines. As long as you do not compile your own packages, you do not need the sources.
Further readings at: https://www.devuan.org/os/packages
I hope I have made my point clear now.
rolfie
Last edited by rolfie (2022-03-03 08:54:24)
Online
My posting related to what shows in Discover | Settings, which is what I posted, not the sources list which does indeed give the full addresses as in your post. Perhaps I should have stated that in the first place. Thanks for your replies everyone.
Offline
Devuan 4.0
Message reads:
Unable to load applications.
Please verify Internet connectivity.Is this a sources.list issue?
I have REM'd out the line pointing to the CD as I have done with previous installs for Devuan 3.0 and 3.1.1
Same problem here.
I can update my system by using terminal and tiping "sudo apt update && sudo apt ugrade" or by using Synaptic, so the issue isn't from sources.
How can I fix Discover?
Thanks a lot and sorry for my bad english.
Offline
I'm afraid this will not work for a long time.
This can't be "fixed" because this is not really bug, sort of. The "appstream" package that provides yalm metadata for Discover has not been forked by Devuan. So actually it will search yalm metadata in Devuan repositories that do not have such yalm files as Debian have in https://appstream.debian.org/data/bookworm/main/ for example.
Offline
Can confirm the same issue now. I used to not like Discover or Plasma in general but they've grown on me, Discover reminds me of "Pamac" on Manjaro years ago.
Thierrybo, that is a great explanation. I guess its better to wait, at least we can just browse through the categories manually for now.
Offline
In Ceres (Unstable) which is on Plasma 5.27.2 now, Discover will no longer load categories with the following output:
fetch ratings! false
adding empty sources model QStandardItemModel(0x564b37dfbfc0)
no component found for "org.devuan.devuan"
Of course, this time I have only the apt backend. If I had the flatpak backend, apps from that should load.
Offline
I was able to fix this by manually putting the files in the right place. I followed the Debian instruction.
1. Get up-to-date data (e.g. from appstream.debian.org/data/: Navigate to the Debian suite you are
running (e.g. "unstable")and download the icon tarballs and *.yml.gz files for the archive components
(main, contrib, non-free) you want data for.)
2. Copy the *.yml.gz files to /var/cache/app-info/yaml (you may rename them, e.g. to
"unstable-main_amd64.yml.gz") and extract the 64x64 icon tarball to
/var/cache/app-info/icons/%{suite}-%{acomponent}/64x64, where "suite" is the archive suite the icons
are from (e.g. "unstable") and "acomponent" is the archive component (e.g. "main").
3. Run appstreamcli refresh-cache --force (needed for SCs which use the Xapian cache for fulltext search)
After you done that, you can run appstreamcli status command to see if it regognizes the yaml files. After that Discover finally works.
So with my limited understanding, the devs only needs to start to provide the metadata and icons for Appstream like Debian does. So no forking needed. Unless I'm missing something.
Last edited by Konna (2023-04-03 17:10:55)
Offline