[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2018-03-01 Thread Cedric Jehasse
*** This bug is a duplicate of bug 1561570 ***
https://bugs.launchpad.net/bugs/1561570

The trace i get is this:

SegvAnalysis:
 Segfault happened at: 0x7f022f4a25b9 :callq  
0x7f022f438240 <__memset_sse2>
 PC (0x7f022f4a25b9) ok
 source "0x7f022f438240" (0x7f022f438240) ok
 destination "(%rsp)" (0x7fffbca06f40) not located in a known VMA region 
(needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
SourcePackage: aufs-tools
Stacktrace:
 #0  ftw_startup (dir=0x1081010 
"/var/lib/docker/aufs/mnt/5f3306c6fad9d2fc750be5dd28b3d8d58db4eaa0d5947583d318829e2ea4326e",
 is_nftw=1, func=0x40149c, descriptors=1048566, flags=19) at 
../sysdeps/wordsize-64/../../io/ftw.c:654
 data = {dirstreams = 0x7fffbca06f40, actdir = 0, maxdir = 1048566, 
dirbuf = 0xff , dirbufsize 
= 0, ftw = {base = 0, level = 0}, flags = 0, cvt_arr = 0x0, func = 0x0, dev = 
0, known_objects = 0x0}
 st = {st_dev = 0, st_ino = 0, st_nlink = 0, st_mode = 0, st_uid = 0, 
st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 1523, st_blksize = 4, st_blocks 
= 17345968, st_atim = {tv_sec = 1531, tv_nsec = 17345968}, st_mtim = {tv_sec = 
48, tv_nsec = 17305728}, st_ctim = {tv_sec = 139647365056152, tv_nsec = 
1048576}, __glibc_reserved = {19, 1048566, 4199580}}
 result = 0
 cwdfd = -1
 cwd = 0x0
 cp = 
 #1  0x00401d52 in ?? ()
 No symbol table info available.
 #2  0x004013ec in ?? ()
 No symbol table info available.
 #3  0x7f022f3c9830 in __libc_start_main (main=0x401266, argc=3, 
argv=0x7fffbd207228, init=, fini=, 
rtld_fini=, stack_end=0x7fffbd207218) at ../csu/libc-start.c:291
 result = 
 unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -7392484191596224330, 
4198768, 140736366408224, 0, 0, 7392628052837490870, 7452542804783751350}, 
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x402820, 0x7f022f783ab0 
<_dl_fini>}, data = {prev = 0x0, cleanup = 0x0, canceltype = 4204576}}}
 not_first_call = 
 #4  0x00401199 in ?? ()
 No symbol table info available.


I looked at the ftw_startup implementation in glibc, and think this line could 
be exhausting the stack memory:
 data.dirstreams = (struct dir_data **) alloca (data.maxdir
 * sizeof (struct dir_data *));

The stacktrace shows data.maxdir is 1048566.
data.maxdir is coming from the nopendfd parameter of ntfw.

Looking at plink.c from aufs-tools package shows it uses the current number of 
files limit as nopenfd:
err = getrlimit(RLIMIT_NOFILE, );
if (err)
AuFin("getrlimit");
nftw(cwd, func, rlim.rlim_cur - 10,
 FTW_PHYS | FTW_MOUNT | FTW_ACTIONRETVAL);

It looks like rlim.rlim_cur is 1048576 when auplink crashes.

Is auplink started by dockerd?
I can see on my system dockerd has it's max open files set to 1048576:
cat /proc/2603/limits
Limit Soft Limit   Hard Limit   Units 
Max cpu time  unlimitedunlimitedseconds   
Max file size unlimitedunlimitedbytes 
Max data size unlimitedunlimitedbytes 
Max stack size8388608  unlimitedbytes 
Max core file sizeunlimitedunlimitedbytes 
Max resident set  unlimitedunlimitedbytes 
Max processes unlimitedunlimitedprocesses 
Max open files1048576  1048576  files 
Max locked memory 6553665536bytes 
Max address space unlimitedunlimitedbytes 
Max file locksunlimitedunlimitedlocks 
Max pending signals   3022830228signals   
Max msgqueue size 819200   819200   bytes 
Max nice priority 00
Max realtime priority 00
Max realtime timeout  unlimitedunlimitedus

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2017-09-22 Thread Craig Jellick
*** This bug is a duplicate of bug 1561570 ***
https://bugs.launchpad.net/bugs/1561570

If this affects you and you are using aufs as your docker storage driver
just because it is the default, you can just switch to the overlay2
storage driver to circumvent this crash.

Note that switching storage drivers will cause you to "lose" all you
docker images. You'll have to repull them.

Can switch the storage driver on ubuntu (w/systemd) by putting this:
```
{
"storage-driver": "overlay2"
}
```
in /etc/docker/daemon.json and restarting docker.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2017-08-02 Thread Danijel
*** This bug is a duplicate of bug 1561570 ***
https://bugs.launchpad.net/bugs/1561570

** This bug has been marked a duplicate of bug 1561570
   auplink crashed with SIGSEGV in fts_build()

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2017-07-25 Thread Julian Raschke
Also affects the current build of 17.10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2017-07-22 Thread Fábio Antunes
Has anyone with this issue noticed data corruption affecting docker
images or containers?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2017-07-14 Thread Steven Peters
I recently experienced this crash after upgrading to 16.04. While
debugging, I noticed that my `nvidia-docker` installation wasn't
working, so I upgraded that software, and I don't see the system problem
dialog on launch anymore. I'm not sure why it worked.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2017-03-10 Thread Krishnan Sriram Rama
This crashed on me too.

I am on 16.10 and I use Dell Latitude E7240. This crash happens
everytime I restart my machine. In addition, everytime I do a "docker
run", it crashes.

I'd appreciate if someone can provide a fix or workaround?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2017-03-01 Thread Celvin Rivas
This problem affects me as well, this is a fresh installation for Ubuntu
16.04.2 LTS.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-12-11 Thread John Paul Adrian Glaubitz
People, just a heads-up: Writing "me, too" or "+1" in this bug report is
absolutely pointless without providing any additional information which
is missing here. It just produces noise. If you just want to say "This
problem affects me as well", please just click " This bug affects 68
people. Does this bug affect you?".

Anything else just clutters the bug report and makes the work for the
people who want to work on this harder.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-07-14 Thread llb4ll
+1 on Xenial - Docker installed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-07-10 Thread Joern Heissler
Created new ticket https://sourceforge.net/p/aufs/bugs/26/ with
explanation and patch.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-06-18 Thread Kaluzki Demjan
+1

16.04
curl -fsSL https://get.docker.com/ | sh
sudo usermod -aG docker 

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-06-16 Thread Andreo de Aguiar Vieira
+1 on Xenial - Docker installed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-06-09 Thread Robert Smith
Just to include additional information, this error occurs after exiting
a Docker container or after booting on Ubuntu 16.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-05-24 Thread Rostás Balázs
+1 on Xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-05-17 Thread RH
+1 on Xenial (16.04)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-05-17 Thread Peter Cornelius
+1 on Xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-05-12 Thread Andrea Del Bene
+1  on a fresh install of Xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-05-10 Thread persona...@live.com
Confirmed on a fresh install of Xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-04-04 Thread Graham Weldon
Confirmed on Xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-04-01 Thread Salih EMIN
It happens when I build locally a docker image. It disconnects me from
the network but fortunately it reconnects back

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-03-07 Thread XerebZ
Seeing this on Xubuntu 16.04 Xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-02-03 Thread Jonas G. Drange
Confirmed for Xenial.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-02-01 Thread Norm Walsh
"Me too, too". Ubuntu Wily.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2016-01-14 Thread Ville Ranki
"Me too."

Is this related do docker? If so, I installed it from Ubuntu's
repositories. Now this crash happens on every boot so it's quite
annoying.

Running Ubuntu vivid (15.04).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2015-11-20 Thread Sławek Ehlert
bug #1441038 no longer exists. Is there a new one we could follow?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2015-06-25 Thread Alberto Salvia Novella
** Changed in: aufs-tools (Ubuntu)
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2015-06-24 Thread Syver Enstad
Sorry, newbie error, clicked on duplicate bug to see the details and
inadvertently deleted the duplicate bug status. I don't know how to undo

** This bug is no longer a duplicate of private bug 1441038

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2015-06-16 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1441038 ***
https://bugs.launchpad.net/bugs/1441038

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: aufs-tools (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1442892] Re: auplink crashed with SIGSEGV in ftw_startup()

2015-04-11 Thread Apport retracing service
*** This bug is a duplicate of bug 1441038 ***
https://bugs.launchpad.net/bugs/1441038

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.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1442892/+attachment/4372380/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1442892/+attachment/4372381/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1442892/+attachment/4372383/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1442892/+attachment/4372384/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1442892/+attachment/4372385/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1442892/+attachment/4372386/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1442892/+attachment/4372387/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1441038

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442892

Title:
  auplink crashed with SIGSEGV in ftw_startup()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs