Bug 26283 - Update nextcloud-client to 2.6.3
Summary: Update nextcloud-client to 2.6.3
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK MGA7-32-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2020-03-02 12:03 CET by José Jorge
Modified: 2020-03-06 17:15 CET (History)
5 users (show)

See Also:
Source RPM: nextcloud-client
CVE:
Status comment:


Attachments

Description José Jorge 2020-03-02 12:03:12 CET
- current next-cloud client asks for updates
Comment 1 José Jorge 2020-03-02 12:08:33 CET
Suggested advisory :
This is a bugfix version without any security fixes. It is provided as this is a client for online services, to ensure no bugs are left behind.

Ref : https://github.com/nextcloud/desktop/releases/tag/v2.6.3

SRPM:
nextcloud-client-2.6.3-1.mga7

RPMS :
nextcloud-client-2.6.3-1.mga7
nextcloud-client-nautilus-2.6.3-1.mga7
nextcloud-client-nemo-2.6.3-1.mga7
nextcloud-client-caja-2.6.3-1.mga7
nextcloud-client-dolphin-2.6.3-1.mga7
lib64nextcloudsync0-2.6.3-1.mga7
lib64ocsync0-2.6.3-1.mga7
lib64nextcloud-client-devel-2.6.3-1.mga7

CC: (none) => lists.jjorge
Assignee: lists.jjorge => qa-bugs

Comment 2 Morgan Leijström 2020-03-02 17:46:43 CET
OK 64 bit.
Thank you
Was using version 2.6.2
Using drakrpm I selected nextcloud-client-2.6.3, and it also pulled the relevant packages, in total:

- lib64nextcloudsync0-2.6.3-1.mga7.x86_64
- lib64ocsync0-2.6.3-1.mga7.x86_64
- nextcloud-client-2.6.3-1.mga7.x86_64
- nextcloud-client-dolphin-2.6.3-1.mga7.x86_64

Starting it, it picked up configuration and continued syncing.
Added a folder share to sync, and it worked.

In the terminal where i started it, there is a couple hundred lines 
(process:10002): GLib-GIO-CRITICAL **: 14:47:07.022: g_menu_remove_all: assertion 'G_IS_MENU (menu)' failed

I think it was similar with the old client.  Not beautiful, but OK.

CC: (none) => fri

Comment 3 José Jorge 2020-03-02 18:45:37 CET
(In reply to Morgan Leijström from comment #2)
> In the terminal where i started it, there is a couple hundred lines 
> (process:10002): GLib-GIO-CRITICAL **: 14:47:07.022: g_menu_remove_all:
> assertion 'G_IS_MENU (menu)' failed
> 
> I think it was similar with the old client.  Not beautiful, but OK.

I don't get this lines here, but I confirm the behaviour is the same with previous version : I get a segfault on quit with both ;-)

Whiteboard: (none) => MGA7-64-OK

Comment 4 Morgan Leijström 2020-03-02 18:50:06 CET
I also get a segfault at quit i see now, and i did with earlier version too... forgot to test that.
In an optimal world we should maybe test to see what happens if we quit it in the middle of syncing a folder, and see if it recovers nicely next start?
Comment 5 José Jorge 2020-03-03 08:11:13 CET
Tested in i586, all ok. And no segfault on quit.

Whiteboard: MGA7-64-OK => MGA7-64-OK MGA7-32-OK

Comment 6 Thomas Andrews 2020-03-04 16:31:01 CET
Validating. Advisory in Comment 1.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

Thomas Backlund 2020-03-06 16:38:37 CET

Keywords: (none) => advisory
CC: (none) => tmb

Comment 7 Mageia Robot 2020-03-06 17:15:27 CET
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0069.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.