This stack trace looks curious, and I can't see anything obviously wrong
in the affected code. Do you have a way to reproduce this?
(Also, this bug does not have any duplicates, so it might just be gamma
rays, a RAM glitch, or whatnot)
** Changed in: udisks (Ubuntu)
Status: New => Incomplete
--
udisks-daemon crashed with SIGSEGV in fork()
https://bugs.launchpad.net/bugs/546549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
