Bug 53101
| Summary: | Nautilus crashes on startup | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Public Beta | Reporter: | adam.huffman |
| Component: | nautilus | Assignee: | Havoc Pennington <hp> |
| Status: | CLOSED DUPLICATE | QA Contact: | Aaron Brown <abrown> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | roswell | CC: | george, sergio |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-11-09 13:04:33 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
adam.huffman
2001-09-03 16:45:05 UTC
Will need a backtrace (ideally with debug symbols) to get anywhere with this. Not crashing on most machines. I'll try making a package with symbols and put it up for download. Can you install the RPMs at http://people.redhat.com/~hp/test-packages/ then try running "gdb nautilus" and when it crashes type "backtrace" at the gdb prompt and attach the resulting output to this bug report? Thanks much! It was working yesterday, but crashed today:
(gdb) r
Starting program: /usr/bin/nautilus
[New Thread 1024 (LWP 1768)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 1768)]
0x4042434c in _init () from /usr/lib/libeel.so.0
(gdb) bt
#0 0x4042434c in _init () from /usr/lib/libeel.so.0
#1 0x40973196 in __libc_start_main (main=0x8070cf0 <main>, argc=1,
ubp_av=0xbffffaa4, init=0x805f228 <_init>, fini=0x80b4230 <_fini>,
rtld_fini=0x4000cff8 <_dl_fini>, stack_end=0xbffffa9c)
at ../sysdeps/generic/libc-start.c:129
Did you run the prelinker? That backtrace is before control flow ever hits the Nautilus code. I hadn't run the prelinker, no. Just tried gdb nautilus having run prelink and the backtrace is exactly the same. Hrm. I'm clueless basically. Nautilus main() hasn't even been called in that backtrace - so Nautilus code hasn't even had a chance to run. So it can't be causing the segfault, I don't think. Maybe gdb is confused and the backtrace is bogus, the linker is broken and crashes loading libeel, ... something bizarre like that. I'm not able to reproduce the problem, so it's hard to debug further. I am seeing the same problem. Relative Linux newbie, installing the shrinkwrap 7.2 just bought at Best Buy. This after a few hours of experience playing with 7.1 and about 30 years working with computers as a machine designer and system programmer. Have also seen a scenario where the Panel app segfaults when Gnome is started up. (Gnome endlessly tries to restart Panel, so it does no good to ack the error messages. A new one just pops up.) When the Panel is dead, Nautilus seems to be o.k. and vice-versa. |