Bug 26073

Summary:	umount.davfs2 - segfault
Product:	Mageia	Reporter:	Mészáros Csaba <csablak>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	csablak, lewyssmith
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	davfs2-1.5.5-1.mga7.src.rpm	CVE:
Status comment:

Description Mészáros Csaba 2020-01-14 21:58:24 CET

user - mount davfs2 - ok
user - umount davfs2 - nothing
root - umount davfs2 - segfault
my fstab:
######### webdav
https://dav.box.com/dav /mnt/https/Box davfs rw,user,uid=csablak,noauto 0 0

I found a topic about this in:

forums.gentoo.org/viewtopic-t-1096160-start-0.html
https://forum.ubuntuusers.de/topic/segfault-bei-umount-davfs/?flavour=full
bodhi.fedoraproject.org/updates/FEDORA-2019-d671e74bd5

It looks like a newer version should be compiled for Mageia 7.

Mészáros Csaba 2020-01-14 21:58:30 CET

CC: (none) => pingvin

Comment 1 Lewis Smith 2020-01-15 20:48:51 CET

Thank you for reporting this, and the valuable pointers.
For clarity only:
https://forums.gentoo.org/viewtopic-t-1096160-start-0.html
https://forum.ubuntuusers.de/topic/segfault-bei-umount-davfs/?flavour=full
https://bodhi.fedoraproject.org/updates/FEDORA-2019-d671e74bd5

We already have (thanks again to DavidG) version: 1.5.6 in Cauldron. I could not see from http://savannah.nongnu.org/projects/davfs2 :
"Version 1.5.6 released
     posted by wbaumann, Thu 26 Dec 2019 10:11:38 AM UTC - 0 replies
This is a bugfix release. Please see file ChangeLog for details."
 (because I could not find the changelog) whether this includes the fix.
Since this report is for Cauldron, can you please try the new version?

Source RPM: davfs2-1.5.5-1.mga7 => davfs2-1.5.5-1.mga7.src.rpm
CC: (none) => lewyssmith

Comment 2 Aurelien Oudelet 2020-08-26 13:38:24 CEST

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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