right, that was probably due to the memory corruption which has been
fixed with 2.17.91
** Changed in: gnome-system-tools (Ubuntu)
Status: Needs Info => Fix Released
--
network-admin crashes (segfaults) on starting
https://launchpad.net/bugs/83421
--
ubuntu-bugs mailing list
ubuntu-bugs
I think this is totally fixed with 2.17.91-0ubuntu1.
--
network-admin crashes (segfaults) on starting
https://launchpad.net/bugs/83421
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Sure.
** Attachment added: "gdb trace with pango sybols"
http://librarian.launchpad.net/6231985/gdb-network-admin.txt
--
network-admin crashes (segfaults) on starting
https://launchpad.net/bugs/83421
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
The problem seems to happen to pango, could you get a log with
libpango1.0-0-dbgsym installed?
--
network-admin crashes (segfaults) on starting
https://launchpad.net/bugs/83421
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Installing the dbgsym version didn't actually give any more gdb output.
Valgrind log is attached as per that wiki page.
** Attachment added: "Valgrind memcheck log"
http://librarian.launchpad.net/6223322/valgrind-logs-network-admin.tar.gz
--
network-admin crashes (segfaults) on starting
http
Thank you for your bug. The packages have a -dbgysm variant containing
the debug symbols you can install, that's described on
https://wiki.ubuntu.com/DebuggingProgramCrash. A crash to alloc looks
like a memory corruption. Could you try to get a valgrind log
(https://wiki.ubuntu.com/Valgrind) for th
