Your message dated Fri, 15 May 2009 03:18:23 +0530
with message-id <[email protected]>
and subject line Re: wireshark: core dumped after saving the trace file as a 
HP-UX nettl file
has caused the Debian Bug report #475799,
regarding wireshark: core dumped after saving the trace file as a HP-UX nettl 
file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
475799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475799
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wireshark
Version: 1.0.0-1
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, I was running wireshark to analyse some DNS queries (via the web browser,
when pdnsd was installed locally on the same machine) and after capturing the
traffic, I saved the file as a "nettl" capture file.  Wireshark seemed to have
coredumped after saving the file.

$ 
$ sudo wireshark
**
** ERROR:(file.c:296):cf_reset_state: assertion failed: (cf->state != 
FILE_READ_IN_PROGRESS)
[1]    3884 abort (core dumped)  sudo wireshark
$ 
$ file wireshark-trace.trc
wireshark-trace.trc: "nettl" capture file

Giridhar

- -- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages wireshark depends on:
ii  libadns1              1.4-0.1            Asynchronous-capable DNS client li
ii  libatk1.0-0           1.22.0-1           The ATK accessibility toolkit
ii  libc6                 2.7-10             GNU C Library: Shared libraries
ii  libcairo2             1.4.14-1           The Cairo 2D vector graphics libra
ii  libcomerr2            1.40.8-2           common error description library
ii  libgcrypt11           1.4.0-3            LGPL Crypto library - runtime libr
ii  libglib2.0-0          2.16.3-1           The GLib library of C routines
ii  libgnutls26           2.2.2-1            the GNU TLS library - runtime libr
ii  libgtk2.0-0           2.12.9-2           The GTK+ graphical user interface 
ii  libkrb53              1.6.dfsg.3~beta1-4 MIT Kerberos runtime libraries
ii  libpango1.0-0         1.20.1-1           Layout and rendering of internatio
ii  libpcap0.8            0.9.8-3            system interface for user-level pa
ii  libpcre3              7.6-2              Perl 5 Compatible Regular Expressi
ii  libportaudio2         19+svn20071022-2   Portable audio I/O - shared librar
ii  wireshark-common      1.0.0-1            network traffic analyser (common f
ii  zlib1g                1:1.2.3.3.dfsg-12  compression library - runtime

Versions of packages wireshark recommends:
pn  gksu                          <none>     (no description available)

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIAYb54eu+pR04mIcRAk6fAKDXdPoK2SNNXp/aIKYVAmxCpEjmRwCeIpgs
ozE0qA2W4B6pfnFrasOmQTc=
=zq6D
-----END PGP SIGNATURE-----



--- End Message ---
--- Begin Message ---
On 08/04/22 23:47 +0530, Y Giridhar Appaji Nag said ...
> On 08/04/22 19:46 +0200, Joost Yervante Damad said ...
> > 
> > Thanks. Is it okay for you then if I close the bug, and if you find that it 
> > happens again, you can re-open it or write a new one?
> 
> I would suggest that you let the bug be open, so that someone else running
> into it can add more information.

Been over an year and nobody complained about this.  I haven't been able to
reproduce this bug either.  Hence closing.

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to