Red Hat Bugzilla – Bug 544174
[abrt] crash detected in nautilus-2.28.2-1.fc12
Last modified: 2015-03-03 17:42:14 EST
abrt 1.0.0 detected a crash.
How to reproduce
1.Try to move an icon on the secondary desktop and nautilus crashes
Comment: I have a dual-head setup. My secondary X screen is my sharp LCD TV. If I try to move an icon around on the secondary screen, Nautilus crashes. One of the icons is for VLC. If I try to drag a movie clip from my primary X screen and drop it on VLC on the secondary screen (to play it), Nautilus crashes and my file gets DELETED! (at least I can't find where it went, locate after an updatedb does not find it.
Attached file: backtrace
reason: Process was terminated by signal 6
Created attachment 375999 [details]
Created attachment 377653 [details]
This backtrace is against the latest kernel and may be more complete
*** Bug 546504 has been marked as a duplicate of this bug. ***
UPDATE: The file is not getting deleted. As I drag on to the secondary screen, I initially failed to notice that, in addtion to the cursor appearing on the secondary screen, it also reappears at the left side of the PRIMARY screen.
Basically, when I drag off the right side of the primary screen, the cursor gets CLONED and appears on both screens simultaneously. When I thought I was dropping the file on VLC on the secondary screen, the primary screen copy of the cursor was over a folder on that desktop and that's where the file actually ended up getting dropped. Weird!
UPDATE #2: NOTE: The drag weirdness does not cause nautilus to crash so maybe THAT part of it is Xorg or something else.
The nautilus crash issue occurs only when I try to move an icon on the secondary desktop. Try right clicking and creating a new folder on the secondary desktop -- that should work okay. Next, try to drag it to another part of the screen and nautilus will crash. Renaming the folder causes it to disappear (it's still there in the Desktop directory, however).
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:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.