| 2020-06-11 00:04:15 |
Sascha |
bug |
|
|
added bug |
| 2020-06-11 00:05:06 |
Sascha |
affects |
linphone (Ubuntu) |
davfs2 (Ubuntu) |
|
| 2020-06-11 00:13:50 |
Sascha |
description |
I am getting segfaults everytime I want to unmount my webdav online-space (segfault error 4).
Hardware failure is impossible as I see - because error already reported on project page (and fixed).
Error should be fixed in davfs 1.5.6 (Maybe easiest to bump to version 1.5.6 on ubuntu repos ?) :)
See (line 4-6): http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156&view=markup&pathrev=MAIN
See 2: https://savannah.nongnu.org/bugs/?func=detailitem&item_id=56286#options |
I am getting segfaults everytime I want to unmount my webdav online-space (segfault error 4).
Hardware failure is impossible as I see - because error already reported on project page (and fixed).
Error should be fixed in davfs 1.5.6 (Maybe easiest to bump to version 1.5.6 on ubuntu repos ?) :)
See (line 4-6): http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156&view=markup&pathrev=MAIN
See 2: https://savannah.nongnu.org/bugs/?func=detailitem&item_id=56286#options
EDIT: Using Ubuntu 20.04 x64 |
|
| 2020-06-18 02:18:45 |
Woodrow Shen |
attachment added |
|
debdiff https://bugs.launchpad.net/ubuntu/+source/davfs2/+bug/1883025/+attachment/5384895/+files/debdiff |
|
| 2020-06-27 05:55:11 |
Woodrow Shen |
davfs2 (Ubuntu): status |
New |
In Progress |
|
| 2020-06-27 05:55:16 |
Woodrow Shen |
davfs2 (Ubuntu): assignee |
|
Woodrow Shen (woodrow-shen) |
|
| 2020-09-09 21:25:32 |
Gilles Schintgen |
bug |
|
|
added subscriber Gilles Schintgen |
| 2020-09-25 10:27:49 |
Maria Rigaki |
bug |
|
|
added subscriber Maria Rigaki |
| 2020-10-04 08:01:42 |
Woodrow Shen |
davfs2 (Ubuntu): status |
In Progress |
Confirmed |
|
| 2020-10-04 08:01:47 |
Woodrow Shen |
davfs2 (Ubuntu): assignee |
Woodrow Shen (woodrow-shen) |
|
|
| 2020-11-10 07:07:37 |
Sascha |
removed subscriber Sascha |
|
|
|
| 2021-02-15 16:41:32 |
Marcelo Alcocer |
bug |
|
|
added subscriber Marcelo Alcocer |
| 2021-02-16 12:09:51 |
Vasya Pupkin |
bug |
|
|
added subscriber Vasya Pupkin |
| 2021-03-28 10:19:08 |
Esther Grill |
bug |
|
|
added subscriber Esther Grill |
| 2021-03-29 09:29:32 |
Esther Grill |
removed subscriber Esther Grill |
|
|
|
| 2021-04-04 13:25:00 |
Rolf Leggewie |
summary |
davfs2 unable to unmount: segfault error 4 in libc.so |
[focal SRU] davfs2 unable to unmount: segfault error 4 in libc.so |
|
| 2021-04-04 13:31:42 |
Rolf Leggewie |
tags |
davfs segfault unmount |
davfs patch segfault unmount |
|
| 2021-04-04 13:37:55 |
Rolf Leggewie |
tags |
davfs patch segfault unmount |
davfs focal patch segfault unmount |
|
| 2021-04-04 13:49:11 |
Rolf Leggewie |
description |
I am getting segfaults everytime I want to unmount my webdav online-space (segfault error 4).
Hardware failure is impossible as I see - because error already reported on project page (and fixed).
Error should be fixed in davfs 1.5.6 (Maybe easiest to bump to version 1.5.6 on ubuntu repos ?) :)
See (line 4-6): http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156&view=markup&pathrev=MAIN
See 2: https://savannah.nongnu.org/bugs/?func=detailitem&item_id=56286#options
EDIT: Using Ubuntu 20.04 x64 |
[IMPACT]
umount.davfs consistently segfault in focal. This leads to a number of medium severity issues.
- inability to unmount (this might have security implications)
- inability to remount
- autofs fails to unmount
- reports of higher load in multi-user environments
- computer "hangs" on shutdown waiting for successful umount completion
[TEST CASE]
No need for a specific test case, simply mount a resource via davfs2.mount. Calling umount.davfs2 on that mount in focal will result in a segfault every time. Exit code 255 and failure is recorded in syslog. The mount stays mounted.
To verify the fix from #2 which is the backport of the fix from upstream, simply recompile davfs2 and try the procedure once more to see if the problem has been solved.
[REGRESSION POTENTIAL]
I will leave this mostly to others to evaluate. Currently, umount.davfs2 is completely dysfunctional so it's hard to imagine a regression for a binary that isn't doing anything except segfaulting.
[OTHER INFO]
groovy and later versions have already been fixed via a new upstream release. Upstream discussion of the a and m mixup can be found at the links below.
I am getting segfaults everytime I want to unmount my webdav online-space (segfault error 4).
Hardware failure is impossible as I see - because error already reported on project page (and fixed).
Error should be fixed in davfs 1.5.6 (Maybe easiest to bump to version 1.5.6 on ubuntu repos ?) :)
See (line 4-6): http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156&view=markup&pathrev=MAIN
See 2: https://savannah.nongnu.org/bugs/?func=detailitem&item_id=56286#options
EDIT: Using Ubuntu 20.04 x64 |
|
| 2021-04-04 13:49:30 |
Rolf Leggewie |
description |
[IMPACT]
umount.davfs consistently segfault in focal. This leads to a number of medium severity issues.
- inability to unmount (this might have security implications)
- inability to remount
- autofs fails to unmount
- reports of higher load in multi-user environments
- computer "hangs" on shutdown waiting for successful umount completion
[TEST CASE]
No need for a specific test case, simply mount a resource via davfs2.mount. Calling umount.davfs2 on that mount in focal will result in a segfault every time. Exit code 255 and failure is recorded in syslog. The mount stays mounted.
To verify the fix from #2 which is the backport of the fix from upstream, simply recompile davfs2 and try the procedure once more to see if the problem has been solved.
[REGRESSION POTENTIAL]
I will leave this mostly to others to evaluate. Currently, umount.davfs2 is completely dysfunctional so it's hard to imagine a regression for a binary that isn't doing anything except segfaulting.
[OTHER INFO]
groovy and later versions have already been fixed via a new upstream release. Upstream discussion of the a and m mixup can be found at the links below.
I am getting segfaults everytime I want to unmount my webdav online-space (segfault error 4).
Hardware failure is impossible as I see - because error already reported on project page (and fixed).
Error should be fixed in davfs 1.5.6 (Maybe easiest to bump to version 1.5.6 on ubuntu repos ?) :)
See (line 4-6): http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156&view=markup&pathrev=MAIN
See 2: https://savannah.nongnu.org/bugs/?func=detailitem&item_id=56286#options
EDIT: Using Ubuntu 20.04 x64 |
[IMPACT]
umount.davfs consistently segfault in focal. This leads to a number of medium severity issues.
- inability to unmount (this might have security implications)
- inability to remount
- autofs fails to unmount
- reports of higher load in multi-user environments
- computer "hangs" on shutdown waiting for successful umount completion
[TEST CASE]
No need for a specific test case, simply mount a resource via davfs2.mount. Calling umount.davfs2 on that mount in focal will result in a segfault every time. Exit code 255 and failure is recorded in syslog. The mount stays mounted.
To verify the fix from #2 which is the backport of the fix from upstream, simply recompile davfs2 and try the procedure once more to see if the problem has been solved.
[REGRESSION POTENTIAL]
I will leave this mostly to others to evaluate. Currently, umount.davfs2 is completely dysfunctional so it's hard to imagine a regression for a binary that isn't doing anything except segfaulting.
[OTHER INFO]
groovy and later versions have already been fixed via a new upstream release. Upstream discussion of the a and m mixup can be found at the links below.
[ORIGINAL REPORT]
I am getting segfaults everytime I want to unmount my webdav online-space (segfault error 4).
Hardware failure is impossible as I see - because error already reported on project page (and fixed).
Error should be fixed in davfs 1.5.6 (Maybe easiest to bump to version 1.5.6 on ubuntu repos ?) :)
See (line 4-6): http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156&view=markup&pathrev=MAIN
See 2: https://savannah.nongnu.org/bugs/?func=detailitem&item_id=56286#options
EDIT: Using Ubuntu 20.04 x64 |
|
| 2021-04-04 13:49:46 |
Rolf Leggewie |
bug |
|
|
added subscriber Rolf Leggewie |
| 2021-04-04 13:50:10 |
Rolf Leggewie |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2021-04-04 14:22:35 |
Rolf Leggewie |
description |
[IMPACT]
umount.davfs consistently segfault in focal. This leads to a number of medium severity issues.
- inability to unmount (this might have security implications)
- inability to remount
- autofs fails to unmount
- reports of higher load in multi-user environments
- computer "hangs" on shutdown waiting for successful umount completion
[TEST CASE]
No need for a specific test case, simply mount a resource via davfs2.mount. Calling umount.davfs2 on that mount in focal will result in a segfault every time. Exit code 255 and failure is recorded in syslog. The mount stays mounted.
To verify the fix from #2 which is the backport of the fix from upstream, simply recompile davfs2 and try the procedure once more to see if the problem has been solved.
[REGRESSION POTENTIAL]
I will leave this mostly to others to evaluate. Currently, umount.davfs2 is completely dysfunctional so it's hard to imagine a regression for a binary that isn't doing anything except segfaulting.
[OTHER INFO]
groovy and later versions have already been fixed via a new upstream release. Upstream discussion of the a and m mixup can be found at the links below.
[ORIGINAL REPORT]
I am getting segfaults everytime I want to unmount my webdav online-space (segfault error 4).
Hardware failure is impossible as I see - because error already reported on project page (and fixed).
Error should be fixed in davfs 1.5.6 (Maybe easiest to bump to version 1.5.6 on ubuntu repos ?) :)
See (line 4-6): http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156&view=markup&pathrev=MAIN
See 2: https://savannah.nongnu.org/bugs/?func=detailitem&item_id=56286#options
EDIT: Using Ubuntu 20.04 x64 |
[IMPACT]
umount.davfs consistently segfault in focal. This leads to a number of medium severity issues.
- inability to unmount (this might have security implications)
- inability to remount
- autofs fails to unmount
- reports of higher load in multi-user environments
- computer "hangs" on shutdown waiting for successful umount completion
[TEST CASE]
No need for a specific test case, simply mount a resource via davfs2.mount. Calling umount.davfs2 on that mount in focal will result in a segfault every time. Exit code 255 and failure is recorded in syslog. The mount stays mounted.
To verify the fix from #2 which is the backport of the fix from upstream, simply recompile davfs2 and try the procedure once more to see if the problem has been solved.
[REGRESSION POTENTIAL]
I will leave this mostly to others to evaluate. Currently, umount.davfs2 is completely dysfunctional so it's hard to imagine a regression for a binary that isn't doing anything except segfaulting.
[OTHER INFO]
groovy and later versions have already been fixed via a new upstream release. Upstream discussion of the a and m mixup can be found at the links below. Duplicate bug 1859293 also has some very good background.
[ORIGINAL REPORT]
I am getting segfaults everytime I want to unmount my webdav online-space (segfault error 4).
Hardware failure is impossible as I see - because error already reported on project page (and fixed).
Error should be fixed in davfs 1.5.6 (Maybe easiest to bump to version 1.5.6 on ubuntu repos ?) :)
See (line 4-6): http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156&view=markup&pathrev=MAIN
See 2: https://savannah.nongnu.org/bugs/?func=detailitem&item_id=56286#options
EDIT: Using Ubuntu 20.04 x64 |
|
| 2021-04-04 15:40:39 |
Robie Basak |
description |
[IMPACT]
umount.davfs consistently segfault in focal. This leads to a number of medium severity issues.
- inability to unmount (this might have security implications)
- inability to remount
- autofs fails to unmount
- reports of higher load in multi-user environments
- computer "hangs" on shutdown waiting for successful umount completion
[TEST CASE]
No need for a specific test case, simply mount a resource via davfs2.mount. Calling umount.davfs2 on that mount in focal will result in a segfault every time. Exit code 255 and failure is recorded in syslog. The mount stays mounted.
To verify the fix from #2 which is the backport of the fix from upstream, simply recompile davfs2 and try the procedure once more to see if the problem has been solved.
[REGRESSION POTENTIAL]
I will leave this mostly to others to evaluate. Currently, umount.davfs2 is completely dysfunctional so it's hard to imagine a regression for a binary that isn't doing anything except segfaulting.
[OTHER INFO]
groovy and later versions have already been fixed via a new upstream release. Upstream discussion of the a and m mixup can be found at the links below. Duplicate bug 1859293 also has some very good background.
[ORIGINAL REPORT]
I am getting segfaults everytime I want to unmount my webdav online-space (segfault error 4).
Hardware failure is impossible as I see - because error already reported on project page (and fixed).
Error should be fixed in davfs 1.5.6 (Maybe easiest to bump to version 1.5.6 on ubuntu repos ?) :)
See (line 4-6): http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156&view=markup&pathrev=MAIN
See 2: https://savannah.nongnu.org/bugs/?func=detailitem&item_id=56286#options
EDIT: Using Ubuntu 20.04 x64 |
[IMPACT]
umount.davfs consistently segfault in focal. This leads to a number of medium severity issues.
- inability to unmount (this might have security implications)
- inability to remount
- autofs fails to unmount
- reports of higher load in multi-user environments
- computer "hangs" on shutdown waiting for successful umount completion
[TEST CASE]
No need for a specific test case, simply mount a resource via davfs2.mount. Calling umount.davfs2 on that mount in focal will result in a segfault every time. Exit code 255 and failure is recorded in syslog. The mount stays mounted.
To verify the fix from #2 which is the backport of the fix from upstream, simply recompile davfs2 and try the procedure once more to see if the problem has been solved.
[REGRESSION POTENTIAL]
I will leave this mostly to others to evaluate. Currently, umount.davfs2 is completely dysfunctional so it's hard to imagine a regression for a binary that isn't doing anything except segfaulting.
[racb] Code that parses its own pidfile is being fixed. It was segfaulting before, so as mentioned it is unlikely to break further as a cause of this patch, except the normal latent bug being exposed on rebuild risk. If there is a problem with the pidfile parsing being introduced, then code further down this path could break.
[OTHER INFO]
groovy and later versions have already been fixed via a new upstream release. Upstream discussion of the a and m mixup can be found at the links below. Duplicate bug 1859293 also has some very good background.
[ORIGINAL REPORT]
I am getting segfaults everytime I want to unmount my webdav online-space (segfault error 4).
Hardware failure is impossible as I see - because error already reported on project page (and fixed).
Error should be fixed in davfs 1.5.6 (Maybe easiest to bump to version 1.5.6 on ubuntu repos ?) :)
See (line 4-6): http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156&view=markup&pathrev=MAIN
See 2: https://savannah.nongnu.org/bugs/?func=detailitem&item_id=56286#options
EDIT: Using Ubuntu 20.04 x64 |
|
| 2021-04-04 15:52:04 |
Robie Basak |
davfs2 (Ubuntu): status |
Confirmed |
In Progress |
|
| 2021-04-06 04:57:03 |
Mathew Hodson |
nominated for series |
|
Ubuntu Focal |
|
| 2021-04-06 04:57:03 |
Mathew Hodson |
bug task added |
|
davfs2 (Ubuntu Focal) |
|
| 2021-04-06 04:57:17 |
Mathew Hodson |
davfs2 (Ubuntu): importance |
Undecided |
Medium |
|
| 2021-04-06 04:57:19 |
Mathew Hodson |
davfs2 (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2021-04-06 04:59:45 |
Mathew Hodson |
davfs2 (Ubuntu): status |
In Progress |
Fix Released |
|
| 2021-04-06 14:21:48 |
Launchpad Janitor |
davfs2 (Ubuntu Focal): status |
New |
Confirmed |
|
| 2021-05-11 20:18:02 |
George |
bug |
|
|
added subscriber George |
| 2021-05-26 03:31:14 |
Chris Halse Rogers |
davfs2 (Ubuntu Focal): status |
Confirmed |
Fix Committed |
|
| 2021-05-26 03:31:17 |
Chris Halse Rogers |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-05-26 03:31:21 |
Chris Halse Rogers |
bug |
|
|
added subscriber SRU Verification |
| 2021-05-26 03:31:28 |
Chris Halse Rogers |
tags |
davfs focal patch segfault unmount |
davfs focal patch segfault unmount verification-needed verification-needed-focal |
|
| 2021-05-26 05:54:02 |
Vasya Pupkin |
tags |
davfs focal patch segfault unmount verification-needed verification-needed-focal |
davfs focal patch segfault unmount verification-done-focal verification-needed |
|
| 2021-06-02 16:40:11 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-06-02 16:55:02 |
Launchpad Janitor |
davfs2 (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
