Dear Maintainer,
I completely cannot edit pcb layout.
When I try to open .kicad_pcb in my kicad project, I get two
messageboxes "cannot open shared library libwx_gtk2u_gl-3.0.so.0" and
"could not load kiface library /usr/bin/_pcbnew.kiface"

When I do
ldd /usr/bin/_pcbnew.kiface
in terminal, I get
libwx_gtk2u_gl-3.0.so.0 => not found
libwx_gtk2u_aui-3.0.so.0 => not found
libwx_gtk2u_adv-3.0.so.0 => not found
libwx_gtk2u_html-3.0.so.0 => not found
libwx_gtk2u_core-3.0.so.0 => not found
libwx_gtk2u_stc-3.0.so.0 => not found

I try to find "apt search wx gtk2", but no such packages in repository.
We cannot use kicad in debian for 2 years! Do you ever test the
package?
How could it be possible? Debian some time ago was splendid distro but
now its quality breaks another bottom.

Hello,

Am Fri, Mar 04, 2022 at 07:52:43AM +0400 schrieb scaldov:

these all are GTK+2 related libraries where KiCad in Debian is not
linked against it since the release of buster! This is almost 3 years
ago.
So the question for me is where the file/symlink in /usr/bin is comming
from, but apperently not from a recent Debian package in my eyes.

$ ldd /usr/bin/_pcbnew.kiface | grep libwx
	libwx_gtk3u_gl-3.0.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk3u_gl-3.0.so.0 (0x00007fa353f55000)
	libwx_gtk3u_aui-3.0.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk3u_aui-3.0.so.0 (0x00007fa353eba000)
	libwx_gtk3u_adv-3.0.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk3u_adv-3.0.so.0 (0x00007fa353cd2000)
	libwx_gtk3u_html-3.0.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk3u_html-3.0.so.0 (0x00007fa353bec000)
	libwx_gtk3u_core-3.0.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0 (0x00007fa353573000)
	libwx_baseu_net-3.0.so.0 => /usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0 (0x00007fa353529000)
	libwx_baseu-3.0.so.0 => /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 (0x00007fa353291000)
	libwx_gtk3u_propgrid-3.0.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk3u_propgrid-3.0.so.0 (0x00007fa353198000)
	libwx_baseu_xml-3.0.so.0 => /usr/lib/x86_64-linux-gnu/libwx_baseu_xml-3.0.so.0 (0x00007fa353186000)
	libwx_gtk3u_stc-3.0.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk3u_stc-3.0.so.0 (0x00007fa352f82000)

Unfortunately you don't have used the reportbug tool in a way that were
we could see some more information about your local installation.

Also you don't provide enough information about what you have done, and
what not, which architecture you are running etc, and if you use some other
packages sources which are not from Debian etc.

Yes, that's quite normal as Debian isn't supporting the WX tookit with
GTK+2 bindings anymore as a release goal for bullseye.

Of course we test new KiCad packages in various ways, but I wonder a bit
how you can say KiCad is unusable for 2 years and you haven't complaint
before about.

For me Debian is still my first choise, but you are free to use what ever
distribution you like.
It's not helpfull for me or other users complaining about very
unspecific things. I've no idea what you mean by "quality breaks" since some
time.

You could be more helpful by providing more and detailed information.

What EXACTELY you are unhappy about?
How can the issue you have readjusted by others?
Did these problems also happen if started within a new and fresh Debian
installation?

Please try to have a look at your issue(s) from a POV of a maintainer, the
package maintainer don't know you local setup not what you have done. Without
enough information it's mostly impossible to fix up things.

Regards
Carsten

Hello,

please use "Reply all" so your answer will get also into the BTS.


Am 04.03.22 um 21:10 schrieb scaldov:

Is there a special reason why you use these entries? Using the CDN
behind the official Debian resources should be smart enough to always
find a official Debian mirror, mirror.one.com is located in Danemark.
Please try to use the following data

And please don't use deb-multimedia.org (anymore)!
The archive from there is know to make trouble at sometome if you don't
really know what package you can use from there.
Exactly the problems you are seeing right now might happen.
There is no reason left to use deb-multimedia today.

That is still the original problem, something inside the binary is
requiring GTK+2 libraries. And then the binary can't be from the latest
packaged KiCad version. I've no idea where that file could come from,
the answer to this is something only you can know.

I suggest to get rid of all potential installed packages and also local
cached packages.

So I'd do something like this.

sudo apt remove --purge kicad*
sudo apt autoclean

Check if something is left now, if yes remove the files.

ls -la /usr/bin/_*.kiface
ls -la /usr/lib/kicad/_*.kiface

Change the file /et/apt/sources.list so it uses the official Debian CDN
as written above.
Update the local package source data, means run "apt-get update".
Next install the kicad package.

Install the package "debsums" (if not already happen) and check the
checksums for the package kicad

debsums kicad

You also can additional verify some files by the data, especially the
underlaying kicad libararies that include the deps to the wx libraries.

If this still isn't working I'd strat to pick up the packges from the
Debian package site and install them manually.
I can also imagine have a somehow misconfigured ld.so.conf environment.

As there was no feedback since my last email I'll close the report now.

Am 06.03.22 um 09:00 schrieb Carsten Schoenert: