Bug 28826 - Nextcloud-client crash and failed to start after changing parameter into Nextloud-client configuration window
Summary: Nextcloud-client crash and failed to start after changing parameter into Next...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2021-04-22 08:09 CEST by david Cossé
Modified: 2021-04-22 14:07 CEST (History)
1 user (show)

See Also:
Source RPM: nextcloud-client-3.1.3-1.mga8
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description david Cossé 2021-04-22 08:09:24 CEST 
Description of problem:
Nextcloud-client crash and failed to start after changing parameter into Nextloud-client configuration window

2021-04-22 07:54:41:139 [ fatal default ]:      ENFORCE: "allow_failure" in file /home/iurt/rpmbuild/BUILD/desktop-3.1.3/src/common/ownsql.cpp, line 265 with message: SQLITE Prepare error
Abandon (core dumped)

Version-Release number of selected component (if applicable):
3.1.3-1.mga8

How reproducible:
Every time, on one machine but not all

Steps to Reproduce:
1. If Nexcloud client is started
2. right click on nexcloud applet
3. select parameter
4. check off "Talk"
Comment 1 Morgan Leijström 2021-04-22 13:55:41 CEST 
Thank you for reporting.
Can it be this one upstream?
https://github.com/nextcloud/desktop/issues/2536

CC: (none) => fri

Comment 2 david Cossé 2021-04-22 14:01:32 CEST 
(In reply to Morgan Leijström from comment #1)
> Thank you for reporting.
> Can it be this one upstream?
> https://github.com/nextcloud/desktop/issues/2536

No, as It was not an OnCloud server before.
It was working until I unchecked "Talk"

Anyway removing .config/Nextcloud solved the problem.
Comment 3 Morgan Leijström 2021-04-22 14:07:17 CEST 
Ah, good
Thank you for the update.
Not our bug.

Resolution: (none) => INVALID
Status: NEW => RESOLVED
Keywords: (none) => UPSTREAM
Note You need to log in before you can comment on or make changes to this bug.