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 82437 - nautilus crashed when launched with a bogus command line parameter
nautilus crashed when launched with a bogus command line parameter
Status: RESOLVED DUPLICATE of bug 74311
Product: nautilus
Classification: Core
Component: general
0.x.x [obsolete]
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-21 03:34 UTC by Alex Duggan
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Attachments
attached backtrace with the --sync option (17.39 KB, text/plain)
2002-05-21 13:48 UTC, Alex Duggan
Details

Description Alex Duggan 2002-05-21 03:34:58 UTC
When launching nautilus HEAD, built on 5/20/02 with a bogus commandline
paramater e.g. 'nautilus --foobar', it segfaults upon startup, see attached
backtrace:

Starting program: /gnome/head/INSTALL/bin/nautilus --foobar
[New Thread 1024 (LWP 25576)]
[New Thread 2049 (LWP 25593)]
[New Thread 1026 (LWP 25594)]
[New Thread 2051 (LWP 25595)]
[New Thread 3076 (LWP 25598)]

Gdk-ERROR **: The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadPixmap (invalid Pixmap parameter)'.
  (Details: serial 5384 error_code 4 request_code 2 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.)
aborting...

Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 1024 (LWP 25576)]
0x40973458 in g_logv (log_domain=0x407c80d9 "Gdk", 
    log_level=G_LOG_LEVEL_ERROR, format=0x407c80f2 "%s", args1=0xbffff26c)
    at gmessages.c:503
503
		G_BREAKPOINT ();
Comment 1 Alex Duggan 2002-05-21 03:40:49 UTC
(gdb) bt
  • #0 g_logv
    at gmessages.c line 503
  • #1 g_log
    at gmessages.c line 526
  • #2 gdk_x_error
    at gdkmain-x11.c line 780
  • #3 bonobo_x_error_handler
    at bonobo-ui-main.c line 50
  • #4 _XError
    from /usr/X11R6/lib/libX11.so.6
  • #5 _XReply
    from /usr/X11R6/lib/libX11.so.6
  • #6 XSync
    from /usr/X11R6/lib/libX11.so.6
  • #7 gdk_flush
    at gdkevents-x11.c line 1888
  • #8 gdk_window_process_all_updates
    at gdkwindow.c line 2145
  • #9 gtk_container_idle_sizer
    at gtkcontainer.c line 1004
  • #10 g_idle_dispatch
    at gmain.c line 3129
  • #11 g_main_dispatch
    at gmain.c line 1617
  • #12 g_main_context_dispatch
    at gmain.c line 2161
  • #13 g_main_context_iterate
    at gmain.c line 2242
  • #14 g_main_loop_run
    at gmain.c line 2462
  • #15 gtk_main
    at gtkmain.c line 936
  • #16 main
    at nautilus-main.c line 263
  • #17 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129

Comment 2 Luis Villa 2002-05-21 04:16:52 UTC
Not marking this 2.0.0 because there is a trivial workaround- 'don't
use bogus cli stuff.' Even tempted not to mark it high.

Easy one to clean out, probably, dave.
Comment 3 Michael Meeks 2002-05-21 11:58:22 UTC
This is just precicely nothing to do with the command line parameter.
Comment 4 Michael Meeks 2002-05-21 12:00:57 UTC
Alex, if you can repeat - can you try it with the --sync argument, and
post a fresh backtrace, then we can actually pin-point where the error
occured.

Thanks.
Comment 5 Alex Duggan 2002-05-21 13:47:35 UTC
after running 'nautilus --sync --foobar' throught gdb, the backtrace
it too long to post so I have posted it here, 

http://www.astrolinux.com/stuff/nautilus_backtrace.txt
Comment 6 Alex Duggan 2002-05-21 13:48:50 UTC
Created attachment 8627 [details]
attached backtrace with the --sync option
Comment 7 Luis Villa 2002-05-21 19:13:20 UTC
Reopening, then...
Comment 8 Luis Villa 2002-05-22 22:05:59 UTC
Is this also bug 74311 or some variant thereof, dave?
Comment 9 Dave Camp 2002-05-23 17:51:09 UTC
Yessir.

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