After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 596302 - Nautilus crashes when you drag a file from file-roller over the Places side-bar
Nautilus crashes when you drag a file from file-roller over the Places side-bar
Status: RESOLVED DUPLICATE of bug 589258
Product: nautilus
Classification: Core
Component: Sidebar
2.28.x
Other Linux
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-09-25 12:56 UTC by Chris Lord
Modified: 2009-10-10 13:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Chris Lord 2009-09-25 12:56:37 UTC
When you open an archive in file-roller and drag some of its contents over the Places side-bar in nautilus (just over, not dropping), nautilus will exit with a return code of 1.

I couldn't get a back-trace, but this was in the .xsession-errors:

The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 12880 error_code 5 request_code 24 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

I've seen this on Mandriva and Debian systems with what I assume is stock Nautilus 2.28.0.
Comment 1 Cosimo Cecchi 2009-10-10 13:59:33 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 589258 ***