Your message dated Sun, 08 Oct 2023 02:18:20 +0200
with message-id <5594270.zFmEUVrfbZ@tuxin>
and subject line Re: Bug#985989: nextcloud-desktop: segmentation fault when
trying to open settings
has caused the Debian Bug report #985989,
regarding nextcloud-desktop: segmentation fault when trying to open settings
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.)
--
985989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985989
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nextcloud-desktop
Version: 3.1.1-1
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainers,
When I try to access the settings of the nextcloud desktop client, it crashes.
What I did:
1. run nextcloud
2. right-click on nextcloud tray icon, then click 'Settings'
OR
click tray icon, then click account name (top left), then click 'Settings'
Result:
- the client crashes instantly. When running from terminal, "Segmentation
fault" is returned.
This happens every time.
Expectation:
- don't crash, open settings window
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'testing-security'), (10, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
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.31-10
ii libcloudproviders0 0.3.0-3
ii libgcc-s1 10.2.1-6
ii libglib2.0-0 2.66.7-2
ii libnextcloudsync0 3.1.1-1
ii libqt5core5a 5.15.2+dfsg-5
ii libqt5dbus5 5.15.2+dfsg-5
ii libqt5gui5 5.15.2+dfsg-5
ii libqt5keychain1 0.10.0-1
ii libqt5network5 5.15.2+dfsg-5
ii libqt5qml5 5.15.2+dfsg-5
ii libqt5quick5 5.15.2+dfsg-5
ii libqt5quickcontrols2-5 5.15.2+dfsg-2
ii libqt5sql5-sqlite 5.15.2+dfsg-5
ii libqt5svg5 5.15.2-2
ii libqt5webenginecore5 5.15.2+dfsg-3
ii libqt5webenginewidgets5 5.15.2+dfsg-3
ii libqt5webkit5 5.212.0~alpha4-11
ii libqt5widgets5 5.15.2+dfsg-5
ii libstdc++6 10.2.1-6
ii nextcloud-desktop-common 3.1.1-1
ii nextcloud-desktop-l10n 3.1.1-1
ii qml-module-qtgraphicaleffects 5.15.2-2
ii qml-module-qtqml-models2 5.15.2+dfsg-5
ii qml-module-qtquick-controls2 5.15.2+dfsg-2
ii qml-module-qtquick-layouts 5.15.2+dfsg-5
ii qml-module-qtquick-window2 5.15.2+dfsg-5
ii qml-module-qtquick2 5.15.2+dfsg-5
Versions of packages nextcloud-desktop recommends:
ii nextcloud-desktop-doc 3.1.1-1
nextcloud-desktop suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
without any information, we cannot fix it. Let's close it for now, if we get
any information we can reopen this bug again.
regards,
hefee
--
On Sonntag, 11. April 2021 14:21:36 CEST Bernhard Übelacker wrote:
> Hello till,
> I tried to reproduce this inside a minimal VM,
> but the crash did not show for me.
>
> Maybe you could provide some more details, e.g.
> by installing systemd-coredump and inspecting the
> journal after a crash happened and adding the lines
> of the crash time to this bug.
> Please see more details in [1].
>
> Kind regards,
> Bernhard
>
>
> [1] https://wiki.debian.org/HowToGetABacktrace
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
