The officially official Devuan Forum!

You are not logged in.

#1 Installation » Testing Daedalus with KDE » 2023-04-03 17:25:49

Konna
Replies: 0

1. Editing sources
Python-apt-common-devuan is not automaticly installed when choosing to use KDE. With Xfce it is. I know it says it's for aptitude and synaptic, but software-properties-qt also needs that package to work. Both Apper and Discover uses s-p-qt for editing sources.
After installing that package, there is still problems with the Devuan.info that it has. All the underscores in the description lines causes s-p-qt not reading those lines. Then there is something wrong with the MatchURI. If it's the regex version, when you click the components in the first tab. It will not tick those boxes, instead it will make the entry to the other software tab. If you change the MatchURI to deb.devuan.org everything works corretly.
Also the codename in the /etc/os-release needs to be only the version you are using for s-p-qt to run.
Although after installing the package and fixing the above problems. Still can't open to edit sources with Discover. Opening Discover from terminal and then trying to open software sources, it says in terminal, could not start /usr/share/applications/software-properties-qt.desktop.
And lastly when you get the s-p-qt running, it says Ubuntu Software as the first tab.

2. Layout
The selected keyboard layout at install isn't saved/used with KDE. So you need to set the layout again.

3. Apper
With Apper , I can't install anything. Failed to obtain authentication is given as a reason. Need to start with sudo to use it.

4.
Why is policykit-1-gnome installed in kde system. The package description says "The remaining users of this implementation are Cinnamon, XFCE and Unity."

Will add if I come across anything else.

#2 Re: Other Issues » Featured in Discover (KDE Plasma) not working » 2023-04-03 17:08:41

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.

Board footer

Forum Software