Segmentation fault using lookup

Bug #1627204 reported by Phill
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-nettool (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Ubuntu 16.04 LTS installed from scratch with all recent updates (although problem has existed since first install of 16.04 LTS).

Steps to reproduce:

1) Run `gnome-nettool` in a terminal.
2) Open the lookup tab.
3) Lookup yahoo.com, or anything, I've not found anything that works.
4) Click the lookup button.
5) The program closes with `Segmentation fault (core dumped)` in the terminal.

I can't find the core dump file. The above still happens if run from the launcher, and comes up with the "report problem" box, which I've clicked yes to many of times over the last few months.

Happens on two different computers, both x84_64. The computers have little in common hardware wise.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-nettool 3.8.1-1build3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Sep 23 22:59:06 2016
InstallationDate: Installed on 2016-06-13 (102 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-nettool
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Phill (phill.l) wrote :
Revision history for this message
alexcums (alexcums) wrote :

Based on the information provided, it seems that you're experiencing a segmentation fault (segfault) issue with gnome-nettool on Ubuntu 16.04 LTS. This could be caused by various factors, such as software bugs or system-specific configurations. Here are some steps you can try to troubleshoot and resolve the issue:

Update the System:
Ensure that your system is fully up-to-date by running the following commands in a terminal:

sql
Copy code
sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
Check for Bug Reports:
Visit the Ubuntu bug tracker or GNOME's bugzilla to check if there are existing bug reports related to the gnome-nettool segmentation fault. If you find a relevant bug report, check for possible workarounds or solutions suggested by other users.

Check for Core Dump File:
If the program is crashing with a segmentation fault and generating a core dump, you can check the /var/crash/ directory for core dump files. Use the following command to list the core dumps:

bash
Copy code
ls -lh /var/crash/
If you find a core dump file related to gnome-nettool, you can analyze it using tools like gdb to get more information about the crash.

Use gdb for Debugging (Optional):
If you are comfortable with using the terminal and debugging tools, you can try running gnome-nettool under gdb to see if you can get more information about the crash. Open a terminal and run the following command:

Copy code
gdb gnome-nettool
Then, inside the gdb prompt, type run and hit Enter. This will start the gnome-nettool program. Try to reproduce the issue, and when it crashes, gdb should provide additional information about the crash. You can type bt (backtrace) to see the stack trace and possibly identify the cause of the segmentation fault https://migrationunity.com/

Revision history for this message
Sudip Mukherjee (sudipmuk) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I tried to reproduce this on Ubuntu Focal and other later releases but could not reproduce the segfault. Though I managed to see another issue with "stack smashing" which also resulted in a coredump. Can you please test again and confirm if you are still seeing the segfault.

Please mark the bug status as "New" after you have tested and confirmed.

Changed in gnome-nettool (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-nettool (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-nettool (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.