Wireshark crashed with signal 5 when changing time column

Bug #125753 reported by laksdjfaasdf
8
Affects Status Importance Assigned to Milestone
wireshark (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: wireshark

Description:

I changed the time column in > Edit > Preferences. I chose "Absolute date and time" and clicked on "Apply".

How to reproduce:

1. Start sniffing on your network card.
2. Go to > Edit > Preferences > User Interface > Columns > Time > Format > "Absolute date and time"
3. Click on "Apply"

ProblemType: Crash
Architecture: i386
Date: Fri Jul 13 13:27:23 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/wireshark
NonfreeKernelModules: cdrom
Package: wireshark 0.99.6pre1-1
PackageArchitecture: i386
ProcCmdline: /usr/bin/wireshark
ProcCwd: /home/felix
ProcEnviron:
 LANGUAGE=de_DE.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: wireshark
Stacktrace:
 #0 0xb6099cab in g_logv () from /usr/lib/libglib-2.0.so.0
 #1 0xb6099f29 in g_log () from /usr/lib/libglib-2.0.so.0
 #2 0xb6099fa6 in g_assert_warning () from /usr/lib/libglib-2.0.so.0
 #3 0x08071a6e in ?? ()
 #4 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
Title: wireshark crashed with signal 5
Uname: Linux thinkubuntuz29 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups:

Tags: apport-crash
Revision history for this message
laksdjfaasdf (laksdjfaasdf) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:cf_reset_state ()
cf_open ()
cf_reload ()
packet_list_recreate ()
column_prefs_apply ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Hew (hew) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in wireshark:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Hew (hew) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in wireshark (Ubuntu):
status: Incomplete → Invalid
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.