auplink crashed with SIGSEGV in ftw_startup()

Bug #1748418 reported by Rüdiger Busche
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aufs-tools (Ubuntu)
New
Undecided
Unassigned

Bug Description

Popped up on start up on Ubuntu 16.04

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: aufs-tools 1:3.2+20130722-1.1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 6 10:56:04 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu10
 libgcc1 1:6.0.1-0ubuntu1
ExecutablePath: /sbin/auplink
InstallationDate: Installed on 2015-05-02 (1014 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: auplink /var/lib/docker/aufs/mnt/4f9ef888e9cb9e2a264b348c8cf562acec9e286b4dedbb8f4561d3353a093151 flush
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: aufs-tools
StacktraceTop:
 ftw_startup (dir=0x1cbe010 "/var/lib/docker/aufs/mnt/4f9ef888e9cb9e2a264b348c8cf562acec9e286b4dedbb8f4561d3353a093151", is_nftw=1, func=0x40149c, descriptors=1048566, flags=19) at ../sysdeps/wordsize-64/../../io/ftw.c:654
 ?? ()
 ?? ()
 __libc_start_main (main=0x401266, argc=3, argv=0x7ffe47c1d1c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe47c1d1b8) at ../csu/libc-start.c:291
 ?? ()
Title: auplink crashed with SIGSEGV in ftw_startup()
UpgradeStatus: Upgraded to xenial on 2017-10-23 (108 days ago)
UserGroups:

Revision history for this message
Rüdiger Busche (ruedigerbusche) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1441038, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.