Ubuntu
wireshark package

wireshark froze in __kernel_vsyscall()

Bug #182671 reported by Tim Jones on 2008-01-13

This bug report is a duplicate of: Bug #198884: Wireshark halts in Capture Interfaces window when started using gksu (Hardy, Intrepid). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	wireshark (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

Binary package hint: wireshark

Whenever I startup wireshark and do a 'list available capture devices' the window appears and the packet counts for each intereface are seemingly randomly updated, enabled, or disabled. When I try and cancel the capture wireshark hangs. This happens every time I do this.

My interfaces are:

eth0 - external fixed IP (hw: NetXtreme BCM5752 Gigabit Ethernet PCI Express)
eth1 - bridged (hw: VT6102 [Rhine-II])
tap0 - bridged
tap1 - bridged
br0 - the bridge

I had to force this bug report with a SIGTRAP to wireshark.

Cheers,

Tim

ProblemType: Crash
Architecture: i386
Date: Sun Jan 13 19:39:43 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/wireshark
NonfreeKernelModules: nvidia
Package: wireshark 0.99.7-1
PackageArchitecture: i386
ProcCmdline: /usr/bin/wireshark
ProcCwd: /home/tjones
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
LANG=en_GB.UTF-8
SHELL=/bin/ksh
Signal: 5
SourcePackage: wireshark
StacktraceTop:
__kernel_vsyscall ()
wait () from /lib/tls/i686/cmov/libpthread.so.0
?? ()
?? ()
?? ()
Title: wireshark crashed with signal 5 in __kernel_vsyscall()
Uname: Linux dog 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux
UserGroups:

Tags:

Revision history for this message

Tim Jones (tim-mr-dog) wrote on 2008-01-13:

Dependencies.txt Edit (2.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (419 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (21.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (610 bytes, text/plain; charset="utf-8")
Registers.txt Edit (491 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (665 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (693 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2008-01-14: Symbolic stack trace

Stacktrace.txt (retraced) Edit (55.0 KiB, text/plain)

StacktraceTop:__kernel_vsyscall ()
wait () from /lib/tls/i686/cmov/libpthread.so.0
sync_pipe_close_command (read_fd=<value optimized out>,
capture_stat_stop (sc=0x8b577e8) at capture.c:858
IA__g_cclosure_marshal_VOID__VOID (closure=0x8c09600,

Revision history for this message

Apport retracing service (apport) wrote on 2008-01-14: Symbolic threaded stack trace

ThreadStacktrace.txt (retraced) Edit (55.0 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2008-01-14: Stack trace with source code

StacktraceSource.txt Edit (4.0 KiB, text/plain)

Changed in wireshark:
importance:	Undecided → Medium

Revision history for this message

Connor Imes (ckimes) wrote on 2008-04-26:

lshw.txt Edit (18.4 KiB, text/plain)

On Ubuntu Hardy Heron I have run into the same (or very similar) problem when running wireshark under gksudo. Using sudo to run the program with superuser privileges seems to have avoided the problem.
If the OP finds this to work, perhaps the problem can be traced to gksudo rather than wireshark.

Running x86_64 kernel 2.6.24-16-generic

Attached lshw in case you need any more hardware details.

Revision history for this message

Keith Baker (keibak) wrote on 2008-05-01:

Same problem here.

Wireshark won't start with gksu (gksudo).
Using sudo works.

Cheers

Connor Imes (ckimes) on 2008-05-01

Changed in wireshark:
status:	New → Confirmed

Revision history for this message

Andrew Jorgensen (ajorg) wrote on 2008-05-13:

Same problems here. Problem also exists in openSUSE 11.0 beta2 under gnome-su. sudo works fine.

Revision history for this message

Connor Imes (ckimes) wrote on 2008-07-12:

This problem still exists in the latest version:

connor@lappy686-mk2:~$ uname -a
Linux lappy686-mk2 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux
connor@lappy686-mk2:~$ apt-cache policy wireshark
wireshark:
  Installed: 1.0.0-1
  Candidate: 1.0.0-1
  Version table:
*** 1.0.0-1 0
        500 http://mirrors.easynews.com hardy/universe Packages
        100 /var/lib/dpkg/status
connor@lappy686-mk2:~$ apt-cache policy gksu
gksu:
  Installed: 2.0.0-5ubuntu3
  Candidate: 2.0.0-5ubuntu3
  Version table:
*** 2.0.0-5ubuntu3 0
        500 http://mirrors.easynews.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     2.0.0-5ubuntu2 0
        500 http://mirrors.easynews.com hardy/main Packages

There are a number of other bug reports that appear to be duplicates of this, most notably bug #198884 which has a few duplicates. I will mark this bug as a duplicate of that one since that one has the most complete information and attention, despite being newer.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #198884 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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

Ubuntuwireshark package

wireshark froze in __kernel_vsyscall()

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
wireshark package