Bug 772341

Summary: [abrt] gtkpod-2.1.0-1.fc16: __GI___libc_malloc: Process /usr/bin/gtkpod was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: raflexras <raflexras>
Component: gtk3Assignee: Matthias Clasen <mclasen>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: chkr, mclasen, tmz, yaugen.88
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:185f84c6f1991e92673c3fe799c91e39bdb60346
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 18:20:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dso_list
none
File: build_ids
none
File: maps
none
File: backtrace none

Description raflexras 2012-01-06 21:32:16 UTC 
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        gtkpod
crash_function: __GI___libc_malloc
executable:     /usr/bin/gtkpod
kernel:         3.1.0-7.fc16.i686
pid:            3267
pwd:            /home/raflexras
reason:         Process /usr/bin/gtkpod was killed by signal 11 (SIGSEGV)
time:           Thu 05 Jan 2012 02:12:10 PM EST
uid:            1000
username:       raflexras

backtrace:      Text file, 36435 bytes
build_ids:      Text file, 4797 bytes
dso_list:       Text file, 10598 bytes
maps:           Text file, 32432 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=RealmMobile
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=dd6081ff5b2d4efc2a6135f500000011-1325784763.37596-1434758935
:GNOME_KEYRING_CONTROL=/tmp/keyring-GM2JS9
:IMSETTINGS_MODULE=none
:USER=raflexras
:USERNAME=raflexras
:MAIL=/var/spool/mail/raflexras
:PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/raflexras/.local/bin:/home/raflexras/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/raflexras
:XMODIFIERS=@im=none
:GNOME_KEYRING_PID=1424
:LANG=en_US.utf8
:GDM_LANG=en_US.utf8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/raflexras
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=raflexras
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-1kwWw7uyZE,guid=e4be96d967fbe1fc40513f0a0000007b
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/raflexras
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-raflexras-zrT96o/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1429,unix/unix:/tmp/.ICE-unix/1429
:SSH_AUTH_SOCK=/tmp/keyring-GM2JS9/ssh
:GPG_AGENT_INFO=/tmp/keyring-GM2JS9/gpg:0:1
:GJS_DEBUG_OUTPUT=stderr
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/fedora-gtkpod.desktop
:GIO_LAUNCHED_DESKTOP_FILE_PID=3267

var_log_messages:
:Jan  5 14:02:33 RealmMobile kernel: [ 5512.618936] gtkpod[3199]: segfault at 0 ip 4453fc9e sp bfeec268 error 4 in libid3tag.so.0.3.0[4453c000+12000]
:Jan  5 14:02:37 RealmMobile abrt[3233]: Saved core dump of pid 3199 (/usr/bin/gtkpod) to /var/spool/abrt/ccpp-2012-01-05-14:02:33-3199 (100605952 bytes)
:Jan  5 14:12:10 RealmMobile kernel: [ 6089.987151] gtkpod[3267]: segfault at 4e49b784 ip 43ac4094 sp bff97450 error 4 in libc-2.14.90.so[43a4e000+1a6000]
:Jan  5 14:12:11 RealmMobile abrt[3331]: Saved core dump of pid 3267 (/usr/bin/gtkpod) to /var/spool/abrt/ccpp-2012-01-05-14:12:10-3267 (79921152 bytes)
Comment 1 raflexras 2012-01-06 21:32:19 UTC 
Created attachment 551263 [details]
File: dso_list
Comment 2 raflexras 2012-01-06 21:32:20 UTC 
Created attachment 551264 [details]
File: build_ids
Comment 3 raflexras 2012-01-06 21:32:22 UTC 
Created attachment 551265 [details]
File: maps
Comment 4 raflexras 2012-01-06 21:32:24 UTC 
Created attachment 551266 [details]
File: backtrace
Comment 5 abrt-bot 2012-03-30 11:51:18 UTC 
Backtrace analysis of bugs across components suggests the actual bug is in component gtk3, pango or glib2 instead of component gtkpod, reassigning to gtk3.

Bug #759067 from component nautilus was found to be similar to this bug.

This comment is automatically generated.
Comment 6 abrt-bot 2012-03-30 11:51:28 UTC 
*** Bug 759067 has been marked as a duplicate of this bug. ***
Comment 7 Fedora End Of Life 2013-01-16 15:28:18 UTC 
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 8 Fedora End Of Life 2013-02-13 18:20:30 UTC 
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.