nautilus crashes when launched from terminal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
Binary package hint: nautilus
1) Ubuntu 9.10
2) nautilus 1:2.28.1-0ubuntu1
3) Expected a folder window to open up when launching nautilus.
4) Everything described below is reproducible every time.
With nautilus closed, launching it normally from a terminal outputs the following without ever opening a window:
[code]
$ nautilus
(nautilus:15146): Eel-CRITICAL **: eel_preferences
** Message: Initializing gksu extension...
Initializing nautilus-dropbox 0.6.1
** (nautilus:15146): WARNING **: No marshaller for signature of signal 'UploadFinished'
** (nautilus:15146): WARNING **: No marshaller for signature of signal 'DownloadFinished'
** (nautilus:15146): WARNING **: No marshaller for signature of signal 'ShareCreateError'
(nautilus:15146): GLib-GObject-
Shutting down dropbox extension
Segmentation fault (core dumped)
[/code]
With nautilus closed, launching it with gksu from a terminal outputs the following and opens up a root nautilus window:
[code]
$ gksu nautilus
(nautilus:29889): Eel-CRITICAL **: eel_preferences
** Message: Initializing gksu extension...
Initializing nautilus-dropbox 0.6.1
** (nautilus:29889): WARNING **: No marshaller for signature of signal 'UploadFinished'
** (nautilus:29889): WARNING **: No marshaller for signature of signal 'DownloadFinished'
** (nautilus:29889): WARNING **: No marshaller for signature of signal 'ShareCreateError'
[/code]
It then outputs the following after being manually closed:
[code]
Shutting down dropbox extension
(nautilus:31758): Eel-WARNING **: "nautilus-
(nautilus:31758): GLib-GObject-
[/code]
Launching nautilus with AWN, which I use as a gnome-panel replacement, works. While nautilus is running, trying to launch it again from a terminal outputs the following and exits without affecting existing windows:
[code]
$ nautilus
(nautilus:28510): Eel-CRITICAL **: eel_preferences
[/code]
With gksu it behaves the same as when nautilus isn't already running (second [code] block above), and also doesn't affect existing windows.
ProblemType: Crash
Architecture: i386
Date: Sun Nov 1 21:32:53 2009
Disassembly: 0x14c9ad0: Cannot access memory at address 0x14c9ad0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelMo
Package: nautilus 1:2.28.1-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x14c9ad0: Cannot access memory at address 0x14c9ad0
PC (0x014c9ad0) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
exit () from /lib/tls/
__libc_start_main () from /lib/tls/
?? ()
Title: nautilus crashed with SIGSEGV in exit()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Uninstalling Dropbox only makes the two related messages go away, so I believe it has nothing to do with this issue.
PS: In the paragraph following the last [code] block, "second [code] block" should be "second and third [code] blocks".