Bug 656093
Summary: | [abrt] nautilus-2.91.2-1.fc15: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> | ||||
Component: | nautilus | Assignee: | Tomáš Bžatek <tbzatek> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | rawhide | CC: | ccecchi, mcepl, mcepl, selinux, tbzatek, tsmetana | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:542cd6522130fb47f5e4798355d7bf3e02c21904 AcceptedBlocker | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-04-15 19:47:14 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 617261 | ||||||
Attachments: |
|
Description
Adam Williamson
2010-11-23 03:16:04 UTC
Created attachment 462213 [details]
File: backtrace
Package: nautilus-2.91.2-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. I selected Places->Download to open nautilus folder view 2. got crash 3. Package: nautilus-2.91.2-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.just browsing through ftp share on my LAN 2. 3. Package: nautilus-2.91.2-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Tried to navigate to a 4GB SD card I'd just entered into my card reader 2. 3. Comment ----- I inserted an SD card. It didn't mount automatically as I should. An entry for it was present in the Places menu, so I clicked on that. Nothing appeared to happen (no window opened), and the crash notification appeared a few seconds later. marking this as F15 final blocker, nautilus should not be this broken. It's not nautilus to crash here, it's a python extension. Adam, which extensions do you have in /usr/lib/nautilus/extensions-2.0/python and /usr/share/nautilus-python/extensions? [tbl@tlondon python]$ ls -l /usr/lib64/nautilus/extensions-2.0/python total 104 -rwxr-xr-x. 1 root root 38627 Sep 23 11:09 nautilus-terminal.py -rw-r--r--. 2 root root 32309 Oct 3 18:36 nautilus-terminal.pyc -rw-r--r--. 2 root root 32309 Oct 3 18:36 nautilus-terminal.pyo [tbl@tlondon python]$ ls -l /usr/share/nautilus-python ls: cannot access /usr/share/nautilus-python: No such file or directory [tbl@tlondon python]$ ls -l /usr/lib64/nautilus-python/ total 32 -rwxr-xr-x. 1 root root 29296 Oct 8 14:56 nautilus.so [tbl@tlondon python]$ and [root@tlondon ~]# rpm -qa nautilus\* nautilus-sendto-2.90.0-7.fc15.x86_64 nautilus-terminal-0.7-1.fc15.x86_64 nautilus-debuginfo-2.91.2-1.fc15.x86_64 nautilus-2.91.2-1.fc15.x86_64 nautilus-python-0.7.0-3.fc14.1.x86_64 nautilus-extensions-2.91.2-1.fc15.x86_64 [root@tlondon ~]# [adamw@adam ebay]$ ls /usr/lib64/nautilus/extensions-2.0/python/ postrExtension.py postrExtension.pyc postrExtension.pyo nothing in /usr/share/nautilus-python/extensions (that dir doesn't actually exist). it could be caused by nautilus-python itself; I think I've had a bug like that before (nautilus would go completely crazy on startup if nautilus-python was installed, but work fine without it). Hmmm.... After removing nautilus-python-0.7.0-3.fc14.1.x86_64 (and nautilus-terminal-0.7-1.fc15.x86_64 as a dependency), the first 3 attempts at opening a folder via nautilus worked..... And..... powering up my LUKS encrypted USB hard drive, now mounts (before I had to mount it via palimpsest). Package: nautilus-2.91.2-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.see bug 657972 2. 3. Discussed at 2011-04-15 blocker review meeting. It's a clear blocker but no-one (including me) has seen it for a while, so closing: we will re-open if anyone hits it again. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers |