[apport] gaim crashed with SIGSEGV when starting gaim

Bug #93790 reported by Krešo Kunjas
2
Affects Status Importance Assigned to Milestone
gaim (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gaim

just starting gaim from gnome-panel or menu. the second time i do that it all works withouth any problems...

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Mar 19 18:50:31 2007
Disassembly: 0xb7f3d610:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gaim
Package: gaim 1:2.0.0+beta6-1ubuntu2
PackageArchitecture: i386
ProcCmdline: gaim
ProcCwd: /home/kreso
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=hr_HR.UTF-8
 LANGUAGE=hr_HR.UTF-8
Signal: 11
SourcePackage: gaim
Stacktrace: #0 0xb7f3d610 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Uname: Linux hellfire 2.6.20-10-generic #2 SMP Mon Mar 12 00:02:49 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
Krešo Kunjas (deresh) wrote :
Revision history for this message
Krešo Kunjas (deresh) wrote :

stack trace:

[Thread debugging using libthread_db enabled]
[New Thread -1223488640 (LWP 13021)]
[New Thread -1241461872 (LWP 13026)]
[New Thread -1300943984 (LWP 13036)]
[New Thread -1309336688 (LWP 13039)]
[New Thread -1309717616 (LWP 13042)]
[Thread -1309717616 (LWP 13042) exited]
[New Thread -1309717616 (LWP 13056)]
[New Thread -1320158320 (LWP 13057)]
[New Thread -1328989296 (LWP 13060)]
[New Thread -1337382000 (LWP 13061)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1320158320 (LWP 13057)]
0xb7f63610 in _gst_parse_yylex () from /usr/lib/libgstreamer-0.10.so.0
(gdb) trace
trace command requires an argument
(gdb) backtrace
#0 0xb7f63610 in _gst_parse_yylex () from /usr/lib/libgstreamer-0.10.so.0
#1 0xb7f65acd in _gst_parse__yyparse () from /usr/lib/libgstreamer-0.10.so.0
#2 0xb7f68656 in _gst_parse_launch () from /usr/lib/libgstreamer-0.10.so.0
#3 0xb7f59f18 in gst_parse_launch () from /usr/lib/libgstreamer-0.10.so.0
#4 0xb7f4c24b in gst_parse_bin_from_description () from /usr/lib/libgstreamer-0.10.so.0
#5 0xb16eb2fb in ?? () from /usr/lib/gstreamer-0.10/libgstgconfelements.so
#6 0xb152bec8 in ?? ()
#7 0x00000001 in ?? ()
#8 0xb14fe378 in ?? ()
#9 0x0869c6b0 in ?? ()
#10 0xb152c9c8 in ?? ()
#11 0xb152cae8 in ?? ()
#12 0xb14fe378 in ?? ()
#13 0xb79e9131 in g_free () from /usr/lib/libglib-2.0.so.0
#14 0xb16eb5e5 in ?? () from /usr/lib/gstreamer-0.10/libgstgconfelements.so
#15 0xb152cb08 in ?? ()
#16 0xb16eb767 in ?? () from /usr/lib/gstreamer-0.10/libgstgconfelements.so
#17 0xb14fe3b8 in ?? ()
#18 0xb7f16663 in gst_element_set_state () from /usr/lib/libgstreamer-0.10.so.0
#19 0xb16e8704 in ?? () from /usr/lib/gstreamer-0.10/libgstgconfelements.so
#20 0x00000000 in ?? ()

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gaim:
importance: Undecided → Medium
status: Unconfirmed → Rejected
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.