Bug 1272987
| Summary: | [abrt] nautilus: g_bit_lock(): nautilus killed by SIGSEGV | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vedran Miletić <vedran> | ||||||||||||||||||||||||||
| Component: | nautilus | Assignee: | Matthias Clasen <mclasen> | ||||||||||||||||||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||||
| Version: | 23 | CC: | afarrag, afonsobordado, ahmed751995, amolarakh, anass.1430, ariscop, bugzilla, ccecchi, desintegr, diogocamposwd, dragomir.dan, drindt, eischmann, elleander86, fiendishx, hunt4steven, icywind90, ifoolb, jiri.nytra, keramidasceid, liblit, lray+redhatbugzilla, luca.ciavatta, mailings, marco.motta, marko.m.kostic, mcatanzaro+wrong-account-do-not-cc, mclasen, m, nhjest, niki.guldbrand, novak.david, paul, philip, r, robk, Rsargent1972, scorpy_sk, sjcchaochn, tomspur, yonatan.el.amigo | ||||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/6afb7f76f57b21c7a579f22524e4838316b7ad9d | ||||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:1ada1091bfdfe85caa463d9a2ade3e7d6294c99f;VARIANT_ID=workstation; | ||||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||||
| Last Closed: | 2016-12-20 15:03:50 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
Vedran Miletić
2015-10-19 11:22:16 UTC
Created attachment 1084351 [details]
File: backtrace
Created attachment 1084352 [details]
File: cgroup
Created attachment 1084353 [details]
File: core_backtrace
Created attachment 1084354 [details]
File: dso_list
Created attachment 1084355 [details]
File: environ
Created attachment 1084356 [details]
File: exploitable
Created attachment 1084357 [details]
File: limits
Created attachment 1084358 [details]
File: maps
Created attachment 1084359 [details]
File: mountinfo
Created attachment 1084360 [details]
File: open_fds
Created attachment 1084361 [details]
File: proc_pid_status
Created attachment 1084362 [details]
File: var_log_messages
Another user experienced a similar problem: Browse remote directory using nautilus search function, crashes upon entering a subdir reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 5647 kernel: 4.2.3-300.fc23.x86_64 package: nautilus-3.18.1-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Fedora's ABRT tells me that this is the same problem I was having. I've also experienced this issue. I've found that I was able to reproduce it by doing the following: 1. Open Nautilus and open a mounted samba share, 2. Click on the left sidebar on a mounted USB drive, 3. Create a new tab and click to open a mounted samba share again. Another user experienced a similar problem: Dropbox notification was trying to open a photo (recently synchronised) using nautilus. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 24400 kernel: 4.2.5-300.fc23.x86_64 package: nautilus-3.18.1-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: I tried to access a specific folder on a Windows Share (through smb://) reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 17702 kernel: 4.2.6-300.fc23.x86_64 package: nautilus-3.18.2-2.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: I closed it while it was opening a directory and then it crashed. Since upgraded to F23 nautilus loads contents of directories very slow after some time, though I have directories contain massive amount of files such as my calibre library, it becomes very slow even when opening empty dirs after this happens. Besides, in Fedora 22 I can seldom open nautilus without killing it after at command line upon first login. It's just hanging there and the cursor is spinning after I click its icon. Sometimes killing tracker* brings it up. Not sure if the two relate to each other, just mention it. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 3947 kernel: 4.2.6-301.fc23.x86_64 package: nautilus-3.18.2-2.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Still happens in nautilus-3.18.3-1.fc23.x86_64. Will retry with nautilus-3.18.4-1.fc23.x86_64. Another user experienced a similar problem: Was ctrl+f searching for folder name in Nautilus reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 9895 kernel: 4.2.7-300.fc23.x86_64 package: nautilus-3.18.3-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Hi. I get this crash too. I was browsing a remote (SFTP) directory using nautilus search function. It also happens to me when clicking on a folder in the search results, but only when I'm searching on a remote folder (over SFTP). There also seems to be a timing component: if I wait a little (5-10sec) after I get the search results it crashes less often. I can trigger this crash fairly reliably 1. Go to the trash folder, it should display a blue bar at the top with restore/empty buttons 2. Click on a remote share 3. Immediately type to begin a search if you see the search bar appear before the blue bar from the trash folder disappears, it should trigger this crash Another user experienced a similar problem: Opened Nautilus, clicked Other location, clicked This computer... and it crashed. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 7974 kernel: 4.3.0-1.fc24.x86_64 package: nautilus-3.18.4-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: I was searching for a file. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus journald_cursor: s=f4e3d31c2cd74765bfef86f28866eb2f;i=19f3c;b=008ec9b821194bbba0cdb5f1eb3c6b36;m=8515a8132;t=529a4b9c667e6;x=e841afe8d5b7f77e kernel: 4.2.8-300.fc23.x86_64 package: nautilus-3.18.4-1.fc23 reason: nautilus killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: move a few dozen photos from one directory to another reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 5649 kernel: 4.3.4-300.fc23.x86_64 package: nautilus-3.18.5-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 *** Bug 1309162 has been marked as a duplicate of this bug. *** Similar problem has been detected: Searching inside a gvfs mountes samba fs for a file reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 6828 kernel: 4.3.5-300.fc23.x86_64 package: nautilus-3.18.5-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Similar problem has been detected: I used nautilus to search inside an samba share reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 7388 kernel: 4.4.3-300.fc23.x86_64 package: nautilus-3.18.5-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Similar problem has been detected: Did a search for "odt" then a search for "doc" and it suddenly crashed on me. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 4577 kernel: 4.4.4-301.fc23.x86_64 package: nautilus-3.18.5-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 *** Bug 1320975 has been marked as a duplicate of this bug. *** Similar problem has been detected: slow samba-connection, directory with lots of 2MB pictures. Changed from list view to tiles view. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 24391 kernel: 4.4.6-300.fc23.x86_64 package: nautilus-3.18.5-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 *** Bug 1323609 has been marked as a duplicate of this bug. *** Similar problem has been detected: I wrote some letters on keyboard to perform a research inside a nested folder and nautilus crashed. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 3436 kernel: 4.4.6-300.fc23.x86_64 package: nautilus-3.18.5-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 *** Bug 1329077 has been marked as a duplicate of this bug. *** *** Bug 1330471 has been marked as a duplicate of this bug. *** Similar problem has been detected: - opened sftp remote folder - selected 300 GB worth of files - hit delete - files are being added to the delete queue - opened a new tab - clicked on "home" bookmark reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 19886 kernel: 4.4.7-300.fc23.x86_64 package: nautilus-3.18.5-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Similar problem has been detected: Using nautilus to browse a network share (SMB) sometimes makes it crash, it might also be because i opened a second nautlius windows to the same share (difrent folder), I can't give a step-by-step to reproduce this because it's inconsistent reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 5467 kernel: 4.4.8-300.fc23.x86_64 package: nautilus-3.18.5-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Similar problem has been detected: Just after starting moving file to a nfs mounted directory i started typing to search for files. After that it crashed. This directory is quiet big (642 files/directories). Mount options: rw,nosuid,nodev,noexec,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp, port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.13,local_lock=none, addr=192.168.1.10,user=elleander NFS-server: CentOS 7.2 reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 29330 kernel: 4.4.9-300.fc23.x86_64 package: nautilus-3.18.5-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Similar problem has been detected: I searched inside a mounted samba share reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 9443 kernel: 4.4.9-300.fc23.x86_64 package: nautilus-3.18.5-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 *** Bug 1357249 has been marked as a duplicate of this bug. *** Similar problem has been detected: I was navigating on a ssh server, namely in kernel source folders. I was entering folders by typing folder name to search and pressing 'Enter', after going through several levels of depth nautilus crashed. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_bit_lock executable: /usr/bin/nautilus global_pid: 2472 kernel: 4.6.6-200.fc23.i686 package: nautilus-3.18.5-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. |