Bug 754961
| Summary: | [abrt] tumbler-0.1.22-4.fc16: g_type_check_instance_is_a: Process /usr/lib64/tumbler-1/tumblerd was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ralf Corsepius <rc040203> | ||||||
| Component: | tumbler | Assignee: | Christoph Wickert <christoph.wickert> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 16 | CC: | christoph.wickert, kevin, maxamillion, tgajeski | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:3691491a5f81e79d83546c1f90ec4f4a8b3a2d71 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-12-04 10:10:14 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Ralf Corsepius
2011-11-18 11:52:32 UTC
Created attachment 534378 [details]
File: backtrace
Created attachment 534379 [details]
File: maps
Package: tumbler-0.1.22-4.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Open an *.mpg in nautilus to play it with totem. Are you sure it was nautilus and Thunar was not involved here? I am beginning to think that the problem is not in tumbler' GStreamer plugin but in GStreamer itself. We have reports of other applications (e.g. midori) crashing and freezing as soon as they are trying to use GStreamer. (In reply to comment #4) > Are you sure it was nautilus and Thunar was not involved here? You are right on the spot - Though I was 100% sure to once have configured nautilus as my preferred "File Manager", I currently have Thunar :) [No idea about the cause, but I am facing other "automagic" Gnome3<->xfce switchers with gdm's "session"]. > I am beginning > to think that the problem is not in tumbler' GStreamer plugin but in GStreamer > itself. We have reports of other applications (e.g. midori) crashing and > freezing as soon as they are trying to use GStreamer. Hmm. I am currently pretty clueless, except that I only reported a very small numbers of the segfaults I actually have seen so far (I could flood you if I'd wanted to). Looks like a systematic issue with some files I have on disk to me. Also, as I don't actually know what thumbler does, I am not sure if it's actually launching totem on a particular video which causes the segfaults, but browsing a folder of videos - thumbnail creation? (In reply to comment #5) > (In reply to comment #4) > > Are you sure it was nautilus and Thunar was not involved here? > You are right on the spot - Though I was 100% sure to once have configured > nautilus as my preferred "File Manager", I currently have Thunar :) If you are using Xfce you can use exo-preferred-applications to select your favorite file manager. Not all GNOME apps honor this setting though and I don't know where to set the default file manager in GNOME 3.x > Also, as I don't actually know what thumbler does, I am not sure if it's > actually launching totem on a particular video which causes the segfaults, but > browsing a folder of videos - thumbnail creation? Bingo! You can remove /usr/lib*/tumbler-1/plugins/tumbler-gst-thumbnailer.so if the crashes continue. *** Bug 757641 has been marked as a duplicate of this bug. *** *** Bug 757641 has been marked as a duplicate of this bug. *** *** Bug 757641 has been marked as a duplicate of this bug. *** *** Bug 759846 has been marked as a duplicate of this bug. *** Thanks everybody for submitting this crash report. I have forwarded it to the developers at https://bugzilla.xfce.org/show_bug.cgi?id=8219 From now on, further investigation of this crash should take place in the Xfce bug tracker. I will get back to you if I need more info and let you know once this bug is resolved in Fedora. *** Bug 759935 has been marked as a duplicate of this bug. *** I am still facing this bug almost every day. However BZ now refuses to accept reports about it, probably due to the fact you have closed this BUG "fixed upstream": --- Running report_Bugzilla --- Logging into Bugzilla at https://bugzilla.redhat.com Checking for duplicates Bug is already reported: 754961 Logging out Status: CLOSED UPSTREAM https://bugzilla.redhat.com/show_bug.cgi?id=754961 => This bug has not been fixed in fedora. => You are cheating. (In reply to comment #13) > => This bug has not been fixed in fedora. > => You are cheating. Please take a minute to read the bugzilla documentation and become familar with the workflow. CLOSED UPSTREAM does not imply the bug is actually fixed in Fedora but "bugs closed with this resolution are filed in the upstream bugs tracker or reported to the upstream mailing list". More info is available at https://bugzilla.redhat.com/page.cgi?id=fields.html#status Let me quote you from bug 757641 comment 10: "There is nothing I can do about these segfaults." - So what do you expect me to to or to track here? If you really hit this bug every day, then please use the work around I have given you. TIA. (In reply to comment #14) > (In reply to comment #13) > > => This bug has not been fixed in fedora. > > => You are cheating. > > Please take a minute to read the bugzilla documentation and become familar with > the workflow. CLOSED UPSTREAM does not imply the bug is actually fixed in > Fedora but "bugs closed with this resolution are filed in the upstream bugs > tracker or reported to the upstream mailing list". > > More info is available at > https://bugzilla.redhat.com/page.cgi?id=fields.html#status As long as Fedora exists, I have been discouraging maintainers to use CLOSED UPSTREAM. because it's a bold lie, which is only useful to violently play down the number of bugs Fedora suffers from. Combined with the fact, abrt now "silently exits 0" once a bug was CLOSDED UPSTREAM, I am considering maintainers closing bugs "CLOSED UPSTREAM" to be doing so deliberately in hostile intentions. > Let me quote you from bug 757641 comment 10: "There is nothing I can do about > these segfaults." Correct. These segfaults happen in the background, without any any immediate interaction attached and without abrt not providing any helpful information to reproduce them. > - So what do you expect me to to or to track here? At minimum, I am expecting maintainers to keep bugs open as long as they affect Fedora - What you are doing is cheating! > If you really hit this bug every day, then please use the work around I have > given you. TIA. You mean to "rm /usr/lib*/tumbler-1/plugins/tumbler-gst-thumbnailer.so"? Certainly this stops the segfaults, ... because it's stops all thumbnailing. == Suppressing symptoms |