nautilus segfaults on startup

Bug #185779 reported by sojourner
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

after updates of 1/22/08 nautilus crashed . updates of nautilus were held back by python-nautilus . removed python-nautilus and updated nautilus now segfaults when started , does not get far enough to generate a new crash report .

package list

ron@ron-desktop:~$ dpkg -l | grep nautilus
ii libnautilus-burn4 2.21.5-0ubuntu1 Nautilus Burn Library - runtime version
ii libnautilus-extension1 1:2.21.6-0ubuntu2 libraries for nautilus components - runtime
ii nautilus 1:2.21.6-0ubuntu2 file manager and graphical shell for GNOME
ii nautilus-actions 1.4.1-1 nautilus extension to configure programs to
ii nautilus-data 1:2.21.6-0ubuntu2 data files for nautilus
ii nautilus-gksu 2.0.0-5ubuntu1 privilege granting extension for nautilus us
ii nautilus-open-terminal 0.8-1ubuntu1 nautilus plugin for opening terminals in arb
ii nautilus-sendto 0.12-2ubuntu1 integrates Evolution and Pidgin into the Nau
ron@ron-desktop:~$

backtrace

** (nautilus:11495): CRITICAL **: nautilus_file_new_from_filename: assertion `filename[0] != '\0'' failed

Program received signal SIGSEGV, Segmentation fault.
---Type <return> to continue, or q <return> to quit---
[Switching to Thread 0x7f40e11b36f0 (LWP 11495)]
0x00000000004b3b08 in ?? ()
(gdb) bt
#0 0x00000000004b3b08 in ?? ()
#1 0x0000000000431a3d in ?? ()
#2 0x0000000000431b5f in ?? ()
#3 0x00007f40dd385948 in g_type_create_instance ()
   from /usr/lib/libgobject-2.0.so.0
#4 0x00007f40dd36b36d in ?? () from /usr/lib/libgobject-2.0.so.0
#5 0x00007f40dd369d6d in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#6 0x00007f40dd36a8a2 in g_object_new_valist ()
   from /usr/lib/libgobject-2.0.so.0
#7 0x00007f40dd36a9e1 in g_object_new () from /usr/lib/libgobject-2.0.so.0
#8 0x0000000000431cda in ?? ()
#9 0x0000000000455955 in ?? ()
#10 0x00000000004559b7 in ?? ()
#11 0x000000000045d930 in ?? ()
#12 0x00007f40dd385791 in g_type_create_instance ()
   from /usr/lib/libgobject-2.0.so.0
#13 0x00007f40dd36b36d in ?? () from /usr/lib/libgobject-2.0.so.0
#14 0x000000000045d6c9 in ?? ()
#15 0x00007f40dd369d6d in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#16 0x00007f40dd36a7b6 in g_object_new_valist ()
   from /usr/lib/libgobject-2.0.so.0
#17 0x00007f40dea2e99a in gtk_widget_new () from /usr/lib/libgtk-x11-2.0.so.0
#18 0x0000000000434441 in ?? ()
---Type <return> to continue, or q <return> to quit---
#19 0x0000000000430834 in ?? ()
#20 0x0000000000450443 in ?? ()
#21 0x00007f40dcece3e4 in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#22 0x00007f40dced16f5 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0x00007f40dced1a15 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#24 0x00007f40de91a803 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#25 0x000000000043d942 in ?? ()
#26 0x00007f40dbaa31c4 in __libc_start_main () from /lib/libc.so.6
#27 0x000000000042d069 in ?? ()
#28 0x00007fffe91f48b8 in ?? ()
#29 0x0000000000000000 in ?? ()
(gdb)

Revision history for this message
sojourner (itsmealso2) wrote :

after todays jan 25 2008 updates it got far enough to crash , crash report sent .

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. The stacktrace is missing some symbols, Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem. Also what happens if you install the python-nautilus package, does it crashed?

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
sojourner (itsmealso2) wrote :

hope the attached file is what you need ,if not ask and I will try to provide . I cannot install the python-nautilus package , it blocks libeel2 and therefore nautilus , I had to uninstall it to update nautilus .

Revision history for this message
sojourner (itsmealso2) wrote :

after updates of jan 25 2008 about 2300 east coast US nautilus will start from terminal as root (sudo) does not start at boot still segfaults from terminal as user bt attached . even when started from term many functions not available , no icons on DT no RTclick on DT.

Revision history for this message
sojourner (itsmealso2) wrote :

as of updates on jan 27 2008 nautilus starts fully when run sudo , Icons for all partitions shown on desktop including those not in fstab but no aplication icons. RTclick menu now shows on desktop. Still segfaults when trying to start as user, backtrace is the same as the one directly above (newbtasuser)

Revision history for this message
sojourner (itsmealso2) wrote :

I found out that if I create a new user nautilus will start for that user at login . deleted ~.nautilus for my regular user name no help , still segfaults as regular user what file do I need to delete to get rid of the errors referenced in the BT ( icons and bookmarks ) ?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using "/usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash" in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in nautilus:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.