Bug#1011138: Workaround for bug #1011138
On 2022-05-20 19:16:06 [+0200], Bernhard Schmidt wrote: > On 19/05/22 01:35 PM, Hopea Jonne wrote: > > > Uninstalling libssl-dev helped, for some reason libssl-dev also ships with > > a > > libssl.so binary which may or may not be of same version as other ones. > > I don't think this is the reason, libssl-dev does not ship the .so > binary, instead it ships a symlink to the libraries provided by libssl3 > > $ dpkg-deb -c libssl-dev_3.0.3-4_amd64.deb | grep .so > lrwxrwxrwx root/root 0 2022-05-16 23:20 > ./usr/lib/x86_64-linux-gnu/libcrypto.so -> libcrypto.so.3 > lrwxrwxrwx root/root 0 2022-05-16 23:20 > ./usr/lib/x86_64-linux-gnu/libssl.so -> libssl.so.3 > > However, your bugreport might still point to another problem in > libssl-dev, thus reassigning. > > Is it possible that you have a partially upgraded system (libssl-dev > from OpenSSL 1.1, but kmail linked to OpenSSL 3.0)? Now that I am back, what is the status here? Did this resolve by itself as part of the transition or is still relevant? > Bernhard Sebastian
Bug#1011138: Workaround for bug #1011138
Control: reassign -1 libssl-dev 3.0.3-4 Control: affects -1 kmail On 19/05/22 01:35 PM, Hopea Jonne wrote: > Uninstalling libssl-dev helped, for some reason libssl-dev also ships with a > libssl.so binary which may or may not be of same version as other ones. I don't think this is the reason, libssl-dev does not ship the .so binary, instead it ships a symlink to the libraries provided by libssl3 $ dpkg-deb -c libssl-dev_3.0.3-4_amd64.deb | grep .so lrwxrwxrwx root/root 0 2022-05-16 23:20 ./usr/lib/x86_64-linux-gnu/libcrypto.so -> libcrypto.so.3 lrwxrwxrwx root/root 0 2022-05-16 23:20 ./usr/lib/x86_64-linux-gnu/libssl.so -> libssl.so.3 However, your bugreport might still point to another problem in libssl-dev, thus reassigning. Is it possible that you have a partially upgraded system (libssl-dev from OpenSSL 1.1, but kmail linked to OpenSSL 3.0)? Bernhard
Bug#1011138: Workaround for bug #1011138
Not entirely sure, libssl-dev was 1.1.x while both libssl3 and libssl1.1 are installed. I assume that qt networking (and consequently kmail and other stuff like quassel) prefers the libssl.so symlink over libssl.so.3 but expects it to be 3.0. On May 20, 2022 8:16:06 PM GMT+03:00, Bernhard Schmidt wrote: >Control: reassign -1 libssl-dev 3.0.3-4 >Control: affects -1 kmail > >On 19/05/22 01:35 PM, Hopea Jonne wrote: > >> Uninstalling libssl-dev helped, for some reason libssl-dev also ships with a >> libssl.so binary which may or may not be of same version as other ones. > >I don't think this is the reason, libssl-dev does not ship the .so >binary, instead it ships a symlink to the libraries provided by libssl3 > >$ dpkg-deb -c libssl-dev_3.0.3-4_amd64.deb | grep .so >lrwxrwxrwx root/root 0 2022-05-16 23:20 >./usr/lib/x86_64-linux-gnu/libcrypto.so -> libcrypto.so.3 >lrwxrwxrwx root/root 0 2022-05-16 23:20 >./usr/lib/x86_64-linux-gnu/libssl.so -> libssl.so.3 > >However, your bugreport might still point to another problem in >libssl-dev, thus reassigning. > >Is it possible that you have a partially upgraded system (libssl-dev >from OpenSSL 1.1, but kmail linked to OpenSSL 3.0)? > >Bernhard
Bug#1011138: Workaround for bug #1011138
Uninstalling libssl-dev helped, for some reason libssl-dev also ships with a libssl.so binary which may or may not be of same version as other ones. -- Best regards, HJ
