Bug 833082
| Summary: | [abrt] gvfs-1.12.3-1.fc17: g_logv: Process /usr/libexec/gvfsd-http was killed by signal 5 (SIGTRAP) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | marti coma <tusa1987> | ||||||||
| Component: | gvfs | Assignee: | Ondrej Holy <oholy> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | alexl, bnocera, d.m.berry | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:51ae53a3b273528a41ebeba8af9ad198718adb11 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-08-01 06:12:04 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
marti coma
2012-06-18 14:37:11 UTC
Created attachment 592676 [details]
File: backtrace
Created attachment 592677 [details]
File: maps
Created attachment 592678 [details]
File: open_fds
Something is causing an inordinate amount of file descriptors to be opened after I leave my workstation on for the weekend. When I come back to work on Monday, the system is unresponsive and I have to perform a hard-reset in order to regain control. Any attempt to do anything (open a file or program, etc.) results in a "too many files open" error. After I performed a hard-reset this morning, this error showed up. I'm not sure if it is the root cause, but I'm not sure how else to diagnose the problem. backtrace_rating: 4 Package: gvfs-1.12.3-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Power on after power outage backtrace_rating: 4 cmdline: /usr/libexec/gvfs-udisks2-volume-monitor crash_function: g_logv executable: /usr/libexec/gvfs-udisks2-volume-monitor kernel: 3.8.4-102.fc17.x86_64 package: gvfs-1.12.3-1.fc17 reason: Process /usr/libexec/gvfs-udisks2-volume-monitor was killed by signal 5 (SIGTRAP) uid: 1000 ureports_counter: 1 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 message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed. |