abrt detected a crash. How to reproduce ----- 1. 2. 3. Comment ----- While trying to get F12 beta samba to work with my F11 server box. Since this contains sensitive information, I would appreciate it if it doesn't get flagged public. Additional information ====== Attached files ---- backtrace cmdline ----- /usr/libexec/gvfsd-dav --spawner :1.7 /org/gtk/gvfs/exec_spaw/12 component ----- gvfs executable ----- /usr/libexec/gvfsd-dav kernel ----- 2.6.31.5-96.fc12.x86_64 package ----- gvfs-1.4.1-1.fc12 reason ----- Process was terminated by signal 11
(In reply to comment #0) > While trying to get F12 beta samba to work with my F11 server box. Since this > contains sensitive information, > I would appreciate it if it doesn't get flagged public. At first, this crashreport concerns gvfsd-dav, not gvfsd-smb[-browse]. Also, it does not contain any sensitive information. This looks to me like bug 500655.
The backtrace discloses several things in the avahi_service_resolver_new() call such as dns info and share name which also discloses a user name by reference... Regarding the crash, it happened while I was fiddling with samba settings and that's what I reported in the additional info. It could be like bug 500655 indeed as the backtrace hints me to name resolution. The network setup is somewhat non-standard. I use dynamic dns and the hosts are resolved via /etc/hosts and internal names are also binded to internal ip ranges in my dynamic dns provider's dns servers..maybe the setup has something to do with it.. Still, that's just an uneducated guess as I have gone nowhere near gvfs' code..
OK, setting as private. BTW. in abrt gui, just before the submission, I think it's possible to edit the backtrace and remove all sensitive information.
I believe I did try to edit it directly in the displayed window when I saw the call parameters. But I could be remembering wrong, too much work does that to you, heh. Next bug report I'll try to explore abrt's gui more thoroughly. If it doesn't allow editing at all, it's a very good feature to propose for implementation.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 539925 has been marked as a duplicate of this bug. ***
*** Bug 544788 has been marked as a duplicate of this bug. ***
*** Bug 546447 has been marked as a duplicate of this bug. ***
*** Bug 549301 has been marked as a duplicate of this bug. ***
*** Bug 557739 has been marked as a duplicate of this bug. ***
*** Bug 582167 has been marked as a duplicate of this bug. ***
*** Bug 594952 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.