gnome-nettool crashed with SIGSEGV in gtk_paint_layout()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-nettool (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-nettool
ubuntu@ubuntu:~$ lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04
ubuntu@ubuntu:~$ sudo apt-cache policy gnome-nettool
gnome-nettool:
Installed: 2.30.0-0ubuntu1
Candidate: 2.30.0-0ubuntu1
Version table:
*** 2.30.0-0ubuntu1 0
500 http://
100 /var/lib/
I booted Ubuntu 10.04 beta2 Desktop i386 from a USB flash drive. The flash drive was created using USB Creator (of Ubuntu 9.04 Desktop i386). When I tried to start gnome-nettool from the menu "System > Administration > Network Tools", it crashed immediately.
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-nettool 2.30.0-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sun Apr 18 01:16:12 2010
ExecutablePath: /usr/bin/
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcCmdline: gnome-nettool
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xf6658e: mov 0x38(%esi),%eax
PC (0x00f6658e) ok
source "0x38(%esi)" (0x00000038) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-nettool
StacktraceTop:
?? () from /usr/lib/
gtk_paint_layout () from /usr/lib/
?? ()
on_ping_
?? () from /usr/lib/
Title: gnome-nettool crashed with SIGSEGV in gtk_paint_layout()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(polkit-
(gnome-
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #565522, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.