Ubuntu
clamtk package

[apport] clamtk crashed with SIGSEGV in g_ascii_strtod()

Bug #102443 reported by wmblowers on 2007-04-03

Affects		Status	Importance	Assigned to	Milestone
	clamtk (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: clamtk

automatic crash report

ProblemType: Crash
Architecture: i386
Date: Tue Apr 3 12:34:04 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/clamtk
InterpreterPath: /usr/bin/perl
Package: clamtk 2.31-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/perl /usr/bin/clamtk
ProcCwd: /home/wmblowers
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: clamtk
StacktraceTop:
g_ascii_strtod () from /usr/lib/libglib-2.0.so.0
?? () from /usr/lib/libpango-1.0.so.0
?? ()
?? ()
?? ()
Uname: Linux wmblowers-desktop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message

wmblowers (wmblowers) wrote on 2007-04-03:

Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (739 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (17.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (665 bytes, text/plain; charset="utf-8")
Registers.txt Edit (538 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (554 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (581 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2007-04-03: Symbolic stack trace

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

StacktraceTop:IA__g_strdupv (str_array=0xbf9beeb4) at gstrfuncs.c:2443
pango_font_description_from_string (str=0x8422d48 "Sans Serif 9") at /build/buildd/pango1.0-1.16.1/./pango/fonts.c:1004
gtk_rc_parse_style (context=0x86357b0, scanner=0x863a088) at gtkrc.c:3575
gtk_rc_parse_any (context=0x86357b0, input_name=0x8618f90 "/home/wmblowers/.gtkrc-2.0-kde", input_fd=<value optimized out>, input_string=0x0) at gtkrc.c:2877
gtk_rc_context_parse_one_file (context=0x86357b0, filename=0x8618f90 "/home/wmblowers/.gtkrc-2.0-kde", priority=<value optimized out>, reload=0) at gtkrc.c:1027

Revision history for this message

Apport retracing service (apport) wrote on 2007-04-03: Symbolic threaded stack trace

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

Revision history for this message

Daniel Holbach (dholbach) wrote on 2007-04-04:

Thanks for your bug report. Something in your /home/wmblowers/.gtkrc-2.0-kde seems to make it crash. Can you attach that file to the bug report?

Changed in clamtk:
importance:	Undecided → Medium
status:	Unconfirmed → Needs Info

Revision history for this message

wmblowers (wmblowers) wrote on 2007-04-04: [Bug 102443]

I think I found a way to at least attach it to this email.

WLB :>)

# This file was written by KDE
# You can edit it in the KDE control center, under "GTK Styles and Fonts"

include "/usr/share/themes/Qt/gtk-2.0/gtkrc"

style "user-font"
{
font_name="Sans Serif 9"
}
widget_class "*" style "user-font"

gtk-theme-name="Qt"
gtk-font-name="Sans Serif 9"

Sebastien Bacher (seb128) on 2007-05-24

Changed in clamtk:
status:	Needs Info → Unconfirmed

Revision history for this message

Scott Kitterman (kitterman) wrote on 2007-05-30:

You might consider using klamav since that is a clamav gui designed to work with KDE.

Changed in clamtk:
status:	Unconfirmed → Confirmed

Revision history for this message

Scott Kitterman (kitterman) wrote on 2008-01-24:

FYI, the Feisty version of clamtk does not work with the Feisty version of clamav (I didn't know this yet when I last commented on the bug). Please check the version in feisty-backports (which does) or if you are on Gutsy now, please test again and let us know if this still happens.

Changed in clamtk:
status:	Confirmed → Incomplete

Revision history for this message

wolfger (wolfger) wrote on 2008-06-01:

Over 4 months without a response. If you need help figuring out how to use Feisty backports, see https://help.ubuntu.com/community/UbuntuBackports
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!