Best thing is to file them and let the developers decide; the only real
way to tell us by reading the stack trace and having some knowledge of
the code.
--
[apport] udevd crashed with SIGSEGV
https://launchpad.net/bugs/85839
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
Thanks for your response. I reported a bunch (10?) of bugs today after
that crash; is there a way to tell if those were also not bugs? (Is
SIGSEGV a good sign that it's not an actual bug?)
--
[apport] udevd crashed with SIGSEGV
https://launchpad.net/bugs/85839
--
ubuntu-bugs mailing list
ubuntu
It SEGV'd while in sleep; your system simply ran out of RAM and the
kernel went around killing things.
No udev bug here
** Changed in: udev (Ubuntu)
Status: Unconfirmed => Rejected
--
[apport] udevd crashed with SIGSEGV
https://launchpad.net/bugs/85839
--
ubuntu-bugs mailing list
ubunt
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6461965/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://librarian.launchpad.net/6461966/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://librarian.launchpad.net/6461967/ProcStatus.txt
--
[appor
