Bug 583450 - gPodder trigger a crash in GtkTreeView
Summary: gPodder trigger a crash in GtkTreeView
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fd3ad86de4ef7ad49e02f5a20ca...
: 644430 645803 651248 655279 657626 667876 675446 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-18 15:39 UTC by fred
Modified: 2012-08-16 19:12 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-16 19:12:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (54.03 KB, text/plain)
2010-04-18 15:39 UTC, fred
no flags Details

Description fred 2010-04-18 15:39:38 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gpodder
component: gpodder
executable: /usr/bin/python
kernel: 2.6.32.11-99.fc12.x86_64
package: gpodder-2.1-3.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. In Gpodder, I saved two mp3 on a USB disk
2. Then I removed properly the USB disk in KDE
3. Then iconified gpodder

Comment 1 fred 2010-04-18 15:39:41 UTC
Created attachment 407411 [details]
File: backtrace

Comment 2 Ville-Pekka Vainio 2010-05-13 20:27:53 UTC
The segfault happens at gsequence.c, which is apparently in glib. Maybe gtk or pygtk is doing something wrong here, though? Reassigning to gtk in case someone else is able to find out what went wrong.

Comment 3 Ville-Pekka Vainio 2010-10-19 19:14:18 UTC
*** Bug 644430 has been marked as a duplicate of this bug. ***

Comment 4 Ville-Pekka Vainio 2010-10-22 14:34:56 UTC
*** Bug 645803 has been marked as a duplicate of this bug. ***

Comment 5 Ville-Pekka Vainio 2010-10-22 14:36:46 UTC
People on the CC list: Is gtk the correct component for this bug or should I assign this to glib, pygtk or something else?

Comment 6 Bug Zapper 2010-11-03 16:49:54 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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 7 fred 2010-11-05 09:42:37 UTC
I've upgraded to Fedora 13.

gpodder doesn't crash now, when I use a USB disk.

Thanks

Comment 8 Ville-Pekka Vainio 2010-11-10 09:16:23 UTC
*** Bug 651248 has been marked as a duplicate of this bug. ***

Comment 9 Ville-Pekka Vainio 2010-11-10 09:20:26 UTC
See Dave Malcom's comments at https://bugzilla.redhat.com/show_bug.cgi?id=651248#c3

Comment 10 Ville-Pekka Vainio 2010-11-23 17:42:07 UTC
*** Bug 655279 has been marked as a duplicate of this bug. ***

Comment 11 Ville-Pekka Vainio 2011-01-07 11:28:22 UTC
*** Bug 667876 has been marked as a duplicate of this bug. ***

Comment 12 Ville-Pekka Vainio 2011-02-06 10:19:43 UTC
*** Bug 675446 has been marked as a duplicate of this bug. ***

Comment 13 Calum 2011-11-29 00:20:06 UTC
*** Bug 657626 has been marked as a duplicate of this bug. ***

Comment 14 abrt-bot 2012-03-21 15:49:45 UTC
Backtrace analysis found this bug to be similar to some already closed bugs from other components. You might want to check those bugs for additional information.

Bugs which were found to be similar to this bug: 
  gpodder: bug #603173, bug #645803
  gtk2: bug #651248

This comment is automatically generated.

Comment 15 Fedora End Of Life 2012-08-16 19:12:37 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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


Note You need to log in before you can comment on or make changes to this bug.