Bug 1469724
Summary: | [abrt] nautilus: nautilus_bookmark_connect_file(): nautilus killed by signal 6 | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jean-François Fortin Tam <nekohayo> | ||||||||||||||||||||||
Component: | nautilus | Assignee: | Matthias Clasen <mclasen> | ||||||||||||||||||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||
Version: | 26 | CC: | anders, cosimo.cecchi, mclasen, mtinberg, nmg921, nobody+413398, t1gretto | ||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/25c29f2b0c245e952b1f4fe135a1e09038019b87 | ||||||||||||||||||||||||
Whiteboard: | abrt_hash:75e8e7cf895bc24c60552398d5b3c9133e1165b1;VARIANT_ID=workstation; | ||||||||||||||||||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||
Last Closed: | 2018-05-29 11:19:05 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: |
|
Description
Jean-François Fortin Tam
2017-07-11 18:03:56 UTC
Created attachment 1296383 [details]
File: backtrace
Created attachment 1296384 [details]
File: cgroup
Created attachment 1296385 [details]
File: core_backtrace
Created attachment 1296386 [details]
File: cpuinfo
Created attachment 1296387 [details]
File: dso_list
Created attachment 1296388 [details]
File: limits
Created attachment 1296389 [details]
File: maps
Created attachment 1296390 [details]
File: open_fds
Created attachment 1296391 [details]
File: proc_pid_status
Created attachment 1296392 [details]
File: var_log_messages
Similar problem has been detected: Zugriff auf iPhone Dokumente Accessing iPhone Documents reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: nautilus_bookmark_connect_file executable: /usr/bin/nautilus journald_cursor: s=66be7751c7fd4369a814d9f25b0c3f7f;i=773;b=36215d58dbff4963897752da8bbfa1ba;m=4d2cf1258;t=55563498ec8fa;x=5703b041c9ffbbae kernel: 4.11.11-300.fc26.x86_64 package: nautilus-3.24.2.1-1.fc26 reason: nautilus killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 10000 Similar problem has been detected: I had unmouted an archive and pressed back. So I've reproduced: 1. Mount a krita file (.kra) which is archive (open with archive mounter). 2. Click on the archive on left panel, so in main view the archives root would be displayed. 3. Unmount the archive, using the left panel, so main view would switch to home and the archive's entry would dissapear from right panel. 4. Click on Back in header bar (basically back to no more existing location) and nautilus would crash. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: nautilus_bookmark_connect_file executable: /usr/bin/nautilus journald_cursor: s=f86958fcb99b472092caaaa90b0d6a75;i=690c0;b=40d39974d6e24940aa4222e25863328d;m=2302408dce;t=55608048e3df7;x=8d55ce1f9dcf9c14 kernel: 4.11.11-300.fc26.x86_64 package: nautilus-3.24.2.1-1.fc26 reason: nautilus killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1000 *** Bug 1480366 has been marked as a duplicate of this bug. *** Similar problem has been detected: Tried to mount smb share by clicking on the favorites entry in the places menu at the top of screen reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: nautilus_bookmark_connect_file executable: /usr/bin/nautilus journald_cursor: s=daa6b5c867b84c32aa3c82eb3b35d03c;i=d8b29b;b=ba99bb381684416396d0ebf2684b456b;m=29d3b06a;t=556b8c4e07beb;x=9fc50f5601727e3 kernel: 4.11.11-300.fc26.x86_64 package: nautilus-3.24.2.1-1.fc26 reason: nautilus killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1000 *** Bug 1491930 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |