Bug 699109
Summary: | [abrt] gvfs-1.8.0-2.fc15: verify_metadata_block: Process /usr/libexec/gvfsd-metadata was killed by signal 11 (SIGSEGV) | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jirka Daněk <juraad> | ||||||||||||||
Component: | gvfs | Assignee: | Ondrej Holy <oholy> | ||||||||||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||
Priority: | unspecified | ||||||||||||||||
Version: | 23 | CC: | acf1fca, afsar-servis, agentbwoy007, alajal, alessandromachado.vip, alexey_kulikov, alexl, biosas, bnocera, bugzilla, bwalker, chrys87, computertwigs, cpatrick08, dan, dragomir.dan, dvacek, edimitrov, ehud.kaldor, emmanuel.pacaud, fonya, gaeran, goujunfeng, groug, guidoo666, haelrai, heraclituss, ivaka, jclaverogarcia, jlbouras, jlmeram89, juris.krumins80, justin.bryan.nix.prana, ken, kerry.kelbert, louis, love58900, lovenemesis, mcepl, mcepl, mdmpsyd, melchiaros, michael.faille, mike, mikethepsych, mikhail.v.gavrilov, mirvana-dmitry, mohammad_k908, mynamesha1, nalimilan, nigel.nquande, ohudlick, omega13a, pal666, pavol.ondercin, pds.oganin, pichan19, pupkin.work, req1348, rui.gouveia, sarrab1976, skurtsev, tonyvf, torel, Triv, tucnadave, tyler.whiting3, viendoor, vpodzime, waltsaw, wincc, yaugen.88, zeazide | ||||||||||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | All | ||||||||||||||||
OS: | Unspecified | ||||||||||||||||
Whiteboard: | abrt_hash:720703d73a4b64a1b38ad8863a8b7f5961d14dd9 | ||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||
Clone Of: | Environment: | ||||||||||||||||
Last Closed: | 2016-12-20 12:06: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
Jirka Daněk
2011-04-23 07:24:39 UTC
Created attachment 494376 [details]
File: maps
Created attachment 494377 [details]
File: event_log
Created attachment 494378 [details]
File: dsos
Created attachment 494379 [details]
File: backtrace
Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- init 5, login, crash. Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. open iso-file 2. 3. Comment ----- open iso-file Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. . Package: gvfs-1.8.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Got killed on its own Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Nothing 2. 3. Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I´ve installed the PAE kernel 2.newstart 3.try to install the virtualbox guest additions 4.0.6 Comment ----- The above is what I´ve performed mainly. It could also be some ohter stuff that causes the crash. Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. mounting ISO 2. 3. Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.2 2. 3. Package: gvfs-1.6.4-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I mounted an ISO file 2. I looked at the content 3. I unmounted the ISO 4. GVFS crashed. Comment ----- When mounting the ISO, it was mounted twice (instead of once). Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. unmounting ISO 2. 3. Package: gvfs-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. random crash unfortunately Package: gvfs-1.8.2-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Used Nautilus o browse a folder Package: gvfs-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Después de loguear y cargar la sesion 2. 3. Comment ----- Solamente al loguear la sesión y que se haya cargado la interfaz de Gnome. Aparentemente todo funciona, no observo ninguna anomalía. Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Open Windows network 2. 3. Package: gvfs-1.8.2-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Attempted to open file with very long filename in nedit text editor (non-reproducable) Package: gvfs-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. tweaked the colours in System Monitor's Preferences for display in the panel 2. upon save, the crash occured 3. (unit is up to date) Package: gvfs-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. tweaked the colours in System Monitor's Preferences for display in the panel 2. upon save, the crash occured 3. (unit is up to date) Package: gvfs-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Normal use (saving a file...) Package: gvfs-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.moved mouse to cancel screensaver 2.thats it! 3. Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Mount Iso 2.Mount second Iso 3.Crash occurs Comment ----- Mounted a Starcraft Original Iso, then tried to mount Broodwar Iso. No files appeared in the mounted Starcraft Iso Package: gvfs-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.This is a VitrualBox VM 2. On boot, logged into 'master' via gdm 3.A moment later, crash occured Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Open Windows network 2. 3. Package: gvfs-1.8.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- This came up in installing FC 15 Livedisk 686 version to boot from 16 Gb Kingston USB-flash stick with 2047 Mb overlay-partition and 9192 Mb home-partition. Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- startup to runlevel 5, login, crash Package: gvfs-1.9.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- not sure how it happened Package: gvfs-1.9.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- i dont know Package: gvfs-1.9.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- i dont know Package: gvfs-1.9.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Started Anaconda install. Package: gvfs-1.9.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Dunno..... Package: gvfs-1.8.2-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- viewing .ppt from archive mounted volume Package: gvfs-1.8.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- mount 1.4 GB drive Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Don't know 2. 3. Comment ----- Put in a flash drive Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Copy files from mounted .iso 2. 3. Package: gvfs-1.9.3-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Regular work Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Normal use 2. 3. Package: gvfs-1.8.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- could be that i was running the live usb and mounted a ext2 filesystem with some files that belong to root, and tryed to make a copy of one of those root files into a blank dvd.. Package: gvfs-1.8.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Model: Sager NP9850/Clevo M980U When the error occurs: On boot Graphics Cards: 2x 280M OEM SLI Possible problems: Fedora recognizes the graphics cards, but does not recognize the monitor. The same problem is on Ubuntu. Although I get a desktop, the display settings in system settings has no monitors in the list. It won't detect the display. See this forum thread for more details: http://ubuntuforums.org/showthread.php?s=216143a4a9b8581ece599d929f3ed9e8&t=1336670 This applies to this distro as well, I assume. I fail. Package: gvfs-1.10.0-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Possibly after double-clicking a YouTube video in the side bar. Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.??? 2. 3. Package: gvfs-1.10.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- ??????????? Package: gvfs-1.10.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- no idea how Package: gvfs-1.10.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- After install gdesklets... Package: gvfs-1.10.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- After install gdesklets... Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I simply put a DVD in my DVD drive. Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I'dont know 2. 3. Package: gvfs-1.8.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- been hacked need help 928-282-9476 dgfitz2000 Package: gvfs-1.8.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- been hacked need help 928-282-9476 dgfitz2000 I mounted an ISO with automounter, went to the folder (via the left pane of nautilus) and played an MP3 file with Gnome MPlayer. The mp3 kept playing, but the crash occurred in the background. backtrace_rating: 4 Package: gvfs-1.10.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 562085 [details]
File: backtrace
Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.i start computer from "hibernate" 2. 3. Package: gvfs-1.6.4-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.when I use computer after "hibernate". 2. 3. *** Bug 664881 has been marked as a duplicate of this bug. *** *** Bug 649074 has been marked as a duplicate of this bug. *** *** Bug 684525 has been marked as a duplicate of this bug. *** *** Bug 657917 has been marked as a duplicate of this bug. *** *** Bug 698527 has been marked as a duplicate of this bug. *** *** Bug 683625 has been marked as a duplicate of this bug. *** *** Bug 693099 has been marked as a duplicate of this bug. *** *** Bug 669950 has been marked as a duplicate of this bug. *** *** Bug 657047 has been marked as a duplicate of this bug. *** *** Bug 650065 has been marked as a duplicate of this bug. *** copying a file from .iso, mounted by archive mounter into .gvfs/... or may be just mounting is enough backtrace_rating: 4 Package: gvfs-1.10.1-3.fc16 OS Release: Fedora release 16 (Verne) Created attachment 581616 [details]
File: backtrace
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Just happened on F17 when watching YouTube video in Totem (by it's plugin). gvfs-1.12.3-1.fc17 Note: I was pointed here by ABRT (after generating backtrace). Hitting this in F18; I guess the maintainer isn't responding. I was file browsing in nautilus. backtrace_rating: 4 Package: gvfs-1.14.2-2.fc18 OS Release: Fedora release 18 (Spherical Cow) This is a known bug but we need a reproducer, backtrace is useless in this case. Can somebody try to reproduce with empty metadata database and post detailed repro steps here? We don't need random crashes but repeatable actions. Make sure to delete or backup ~/.local/share/gvfs-metadata first, then kill all gvfs processes and try to reproduce the issue. When I tried to rename a folder, the problem occured. backtrace_rating: 4 Package: gvfs-1.14.2-2.fc18 OS Release: Fedora release 18 (Spherical Cow) After I delete ~/.local/share/gvfs-metadata the bug seems to have been solved. Package: gvfs-1.14.2-3.fc18 OS Release: Fedora release 18 (Spherical Cow) This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. It can be reproduced by either clicking on the google-earth desktop icon or by entering google-earth in the terminal in either $ or # reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-metadata crash_function: verify_metadata_block executable: /usr/libexec/gvfsd-metadata kernel: 3.10.10-100.fc18.x86_64 package: gvfs-1.14.2-4.fc18 reason: Process /usr/libexec/gvfsd-metadata was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. Automatic bug reporter says that I have this bug on Fedora 20 There's quite a lot of reports for this bug on Fedora 20, reopening. https://retrace.fedoraproject.org/faf/reports/28246/ *** Bug 1059589 has been marked as a duplicate of this bug. *** cc Seen on F21 (the corruption of the data happened under F20). This bug will be fixed in the next upstream gvfs 1.23.4 release: https://bugzilla.gnome.org/show_bug.cgi?id=598561 *** Bug 1180878 has been marked as a duplicate of this bug. *** Reopening the bug, because unfortunately recent fixes doesn't fix all sources of crashes. However there were added (in gvfs-1.22.3 for f21, gvfs-1.23.4 for rawhide) some warnings that could help us to find the cause, why it is crashing. Does it crash for you regularly? Could you run the daemon manually until crash and provide the output? killall gvfsd-metadata; /usr/libexec/gvfsd-metadata 2> gvfsd-metadata.log Does it crash after computer startup? Or does it crash when you are using some applications? *** Bug 1123602 has been marked as a duplicate of this bug. *** *** Bug 1182068 has been marked as a duplicate of this bug. *** *** Bug 1187492 has been marked as a duplicate of this bug. *** There is easier way, how to get the warnings. You don't need to run metadata daemon manually, you can just get them from logs: journalctl -r _COMM=gnome-session | grep gvfsd-metadata > gvfsd-metadata.log *** Bug 1107540 has been marked as a duplicate of this bug. *** This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23 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. |