Your message dated Wed, 25 Mar 2026 23:19:54 +0100
with message-id <3999074.CbtlEUcBR6@tuxin>
and subject line Re: Bug#1037364: Solved by removing old libssl.1 lib
has caused the Debian Bug report #1037364,
regarding nextcloud-desktop: TLS initilization failed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1037364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037364
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nextcloud-desktop
Version: 3.7.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Nexcloud-Desktop is unable to connect the Nextcloud Server comaplining TLS 
initialization failed.

SSL Cert on Server is valid. Access with browser and from another computer 
still on Debian 11 works as expected.

   * What led up to the situation?

Upgrade from Debian 11 to Debian 12

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Searching via Google hints to an issue with QT and SSL Version.

   * What was the outcome of this action?

No solution found yet


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_CH:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nextcloud-desktop depends on:
ii  libc6                          2.36-9
ii  libcloudproviders0             0.3.1-2
ii  libgcc-s1                      12.2.0-14
ii  libglib2.0-0                   2.74.6-2
ii  libkf5archive5                 5.103.0-1
ii  libnextcloudsync0              3.7.3-1
ii  libqt5core5a                   5.15.8+dfsg-11
ii  libqt5dbus5                    5.15.8+dfsg-11
ii  libqt5gui5                     5.15.8+dfsg-11
ii  libqt5keychain1                0.13.2-5
ii  libqt5network5                 5.15.8+dfsg-11
ii  libqt5qml5                     5.15.8+dfsg-3
ii  libqt5quick5                   5.15.8+dfsg-3
ii  libqt5quickcontrols2-5         5.15.8+dfsg-2
ii  libqt5sql5-sqlite              5.15.8+dfsg-11
ii  libqt5svg5                     5.15.8-3
ii  libqt5webenginecore5           5.15.13+dfsg-1~deb12u1
ii  libqt5webenginewidgets5        5.15.13+dfsg-1~deb12u1
ii  libqt5widgets5                 5.15.8+dfsg-11
ii  libstdc++6                     12.2.0-14
ii  nextcloud-desktop-common       3.7.3-1
ii  nextcloud-desktop-l10n         3.7.3-1
ii  qml-module-qt-labs-platform    5.15.8+dfsg-2
ii  qml-module-qtgraphicaleffects  5.15.8-2
ii  qml-module-qtqml               5.15.8+dfsg-3
ii  qml-module-qtqml-models2       5.15.8+dfsg-3
ii  qml-module-qtquick-controls2   5.15.8+dfsg-2
ii  qml-module-qtquick-dialogs     5.15.8-2
ii  qml-module-qtquick-layouts     5.15.8+dfsg-3
ii  qml-module-qtquick-window2     5.15.8+dfsg-3
ii  qml-module-qtquick2            5.15.8+dfsg-3

Versions of packages nextcloud-desktop recommends:
ii  nextcloud-desktop-doc  3.7.3-1

nextcloud-desktop suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi,

okay there is no sign, that this has anything to do with nextcloud desktop.
As there is no prove, that it is possible with other cli tools to connect to 
the server and that the server is updated. Without those information, it is 
impossible to help and fix the issue.
This bug report is now open for 2 year with moreinfo needed and not got any 
information, let's just cleanup and close this bug.

It is always possible to still provide information and reopen the bugreport.

Regards,

hefee

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to