** Changed in: gst
Importance: Unknown => Critical
--
network-admin segfaults on startup
https://bugs.launchpad.net/bugs/86357
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
This upload fixes the bug:
gnome-system-tools (2.18.1-0ubuntu1) feisty; urgency=low
.
* New upstream version:
Common:
- Remove nonexistent .desktop files categories
Network:
- Do a sanity check when migrating old locations (Ubuntu: #86357)
Time:
- Mark previously
** Changed in: gst (upstream)
Status: Rejected => Fix Released
--
network-admin segfaults on startup
https://bugs.launchpad.net/bugs/86357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
the bug is fixed upstream now
** Bug watch removed: GNOME Bug Tracker #409975
http://bugzilla.gnome.org/show_bug.cgi?id=409975
** Bug watch added: GNOME Bug Tracker #422969
http://bugzilla.gnome.org/show_bug.cgi?id=422969
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed
** Changed in: gst (upstream)
Status: Unconfirmed => Rejected
--
network-admin segfaults on startup
https://bugs.launchpad.net/bugs/86357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
This popped up on me when I changed the hostname of my machine. I
changed it everywhere but the old hostname was still in some of my
network-admin-locations profiles. The network-admin app would segfault
when I started it with the hostname set differently than the current
profile. Despite chan
Removing /root/.gnome2/network-admin-locations solved the issue for me..
--
network-admin segfaults on startup
https://launchpad.net/bugs/86357
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: gst (upstream)
Status: Unknown => Unconfirmed
--
network-admin segfaults on startup
https://launchpad.net/bugs/86357
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have not modified any profiles by hand.
Here's the only profile I have -- 'Docked'
** Attachment added: "network-admin-locations/Docked profile"
http://librarian.launchpad.net/6480705/Docked
--
network-admin segfaults on startup
https://launchpad.net/bugs/86357
--
ubuntu-bugs mailing l
Did you modify any profile by hand? Upstream asks if you can attach
/root/.gnome2/network-admin-locations/* to the bug (look if there is no
private data first and replace them maybe)
--
network-admin segfaults on startup
https://launchpad.net/bugs/86357
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Thank you for the work on that, I've forwarded those informations
upstream: http://bugzilla.gnome.org/show_bug.cgi?id=409975
** Changed in: gnome-system-tools (Ubuntu)
Status: Needs Info => Confirmed
** Bug watch added: GNOME Bug Tracker #409975
http://bugzilla.gnome.org/show_bug.cgi?id
Backtrace from gdb with thread apply all bt full.
** Attachment added: "(gdb) thread apply all bt full"
http://librarian.launchpad.net/6477785/network-admin.txt
--
network-admin segfaults on startup
https://launchpad.net/bugs/86357
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
Thank you for your bug. Could you get a backtrace by typing "thread
apply all bt full" on the gdb prompt after the crash?
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
--
n
valgrind log generated with:
sudo valgrind -v --tool=memcheck --leak-check=full --num-callers=12
--log-file=valgrind.log network-admin
tar -zcf valgrind-logs-network-admin.tar.gz valgrind.log.*
** Attachment added: "valgrind log with gnome-system-tools-dbgsym"
http://librarian.launchpad.net/6
14 matches
Mail list logo
