Hide Forgot
Description of problem: Copying files (videos) over rsync rsync -avzr 10.10.4.124:/home/casep/Videos/ Videos/ But I'm not able to reproduce it, so could be a separate issue Version-Release number of selected component: tracker-0.16.2-4.fc20 Additional info: reporter: libreport-2.1.8 backtrace_rating: 4 cmdline: /usr/libexec/tracker-extract crash_function: g_malloc executable: /usr/libexec/tracker-extract kernel: 3.11.5-302.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 g_malloc at gmem.c:109 #3 g_slice_alloc at gslice.c:1016 #4 _sysmem_new_block at gstallocator.c:415 #5 gst_allocator_alloc at gstallocator.c:312 #6 gst_buffer_new_allocate at gstbuffer.c:668 #7 video_buffer_pool_alloc at gstvideopool.c:195 #8 do_alloc_buffer at gstbufferpool.c:272 #9 default_acquire_buffer at gstbufferpool.c:995 #10 gst_buffer_pool_acquire_buffer at gstbufferpool.c:1099 #11 gst_video_decoder_allocate_output_frame at gstvideodecoder.c:3262
Created attachment 814796 [details] File: backtrace
Created attachment 814797 [details] File: cgroup
Created attachment 814798 [details] File: core_backtrace
Created attachment 814799 [details] File: dso_list
Created attachment 814800 [details] File: environ
Created attachment 814801 [details] File: limits
Created attachment 814802 [details] File: maps
Created attachment 814803 [details] File: open_fds
Created attachment 814804 [details] File: proc_pid_status
Another user experienced a similar problem: I started the computer ASUS N61 (January 2009) core i7 4GB RAM ATI HD5730 1GB RAM. Started Nemo and then qbittorrent, it ran for probably an hour and I saw the usual long list of errors, but these ones did not mention Nemo this time. The machine has WIn 7 factory installed, but I don't use it - only to update the antvirus once a week. Fedora 20 is installed and runs well in a Western Digital USB 3 1TB drive. It only works in a USB 2 port, as the USB 3 port is non bootable. I hope this helps. regards Steven Woods steven.woods3 reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/libexec/tracker-extract crash_function: g_malloc executable: /usr/libexec/tracker-extract kernel: 3.14.4-200.fc20.x86_64 package: tracker-0.16.4-2.fc20 reason: tracker-extract killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Hi, I am using Fedora21 and I also have this problem. On my machine, I can always reproduce it. Just running the following command will trigger this problem. /usr/libexec/tracker-extract -v 3 -f viewport-percent-graphic-user-01.svg
Created attachment 1018981 [details] The file trigger tracker-extract to crash
Created attachment 1018984 [details] Out of LANG=C /usr/libexec/tracker-extract -v 3 -f viewport-percent-graphic-user-01.svg
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.