Bug 486088
| Summary: | nautilus browser mode (nautilus --browser) doesn't start. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | sangu <sangu.fedora> | ||||||
| Component: | gcc | Assignee: | Jakub Jelinek <jakub> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | rawhide | CC: | jakub, tbzatek, vinagr3 | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | nautilus-2.25.91-2.fc11 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-02-18 20:08:11 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: | |||||||||
| Attachments: |
|
||||||||
This is gcc-4.4.0 issue, working on it... Created attachment 332405 [details]
reproducer
Please check the attachment, this is obviously gcc bug.
Tested on debian gcc 4.3.2 (x86_64) and confirming it works fine.
gcc-4.4.0-0.19.x86_64
glibc-2.9.90-3.x86_64
custom kernel 2.6.28
Feel free to ping me on IRC for more information.
Tracked upstream. Fixed in nautilus-2.25.91-2.fc11 Thanks Tomáš Bžatek, I tested the release and after reboot nautilus is again working in browser mode. Should be now fixed in gcc-4.4.0-0.22. |
Created attachment 332355 [details] dmesg Description of problem: nautilus browser mode (nautilus --browser) doesn't start. IO high load. out of memory $ dmesg <skip> 429298 pages non-shared Out of memory: kill process 7021 (nautilus) score 696292 or a child Killed process 7021 (nautilus) $ cat ~/.xsession-errors <skip> (nautilus:6997): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Version-Release number of selected component (if applicable): 2.25.91-1.fc11 How reproducible: always Steps to Reproduce: 1. $ nautilus --browser 2. 3. Actual results: Expected results: Additional info: gvfs-1.1.6-1.fc11.x86_64