*** 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"
*** 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
*** 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
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:
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()
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
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
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
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
+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:
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
+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
+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:
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
+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:
+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:
+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:
+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:
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:
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:
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
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:
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:
"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:
"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.
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
** 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
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
*** 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
*** 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.
30 matches
Mail list logo