Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Comment 2RHEL Program Management
2011-01-10 15:29:00 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
First of all, could we get output of the command
rpm -qa \*xulrun\* \*firefox\* \*mozilla\* \*flash\* \*plugin\*
Please also install firefox-debuginfo (debuginfo-install is from
yum-utils package).
debuginfo-install firefox
Then run firefox with a parameter -g. That will start firefox running inside of gdb debugger. Then use command run and do whatever you did to make firefox crash. When it happens, you should go back to the gdb and run
(gdb) thread apply all backtrace
This produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment.
Please, install also valgrind (from valgrind package) and run
valgrind --trace-children=yes --log-file=/tmp/firefox-valgrind-log.txt /usr/bin/firefox
(that's one line command, browser breaking this line into two notwithstanding)
Please, attach the file /tmp/firefox-valgrind-log.txt to this bug as an attachment as well.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Matej,
Your steps your provided are relevant for firefox, not Thunderbird.
Secondly, neither application is crashing.
Lastly, Jan Horak is working on 666929 which is the identical issue in Firefox.
Please specify use cases where you'd like to be able to access gvfs volumes. After some discussion at mozbz#682838 different approach has been proposed.
(In reply to comment #19)
> Please specify use cases where you'd like to be able to access gvfs volumes.
> After some discussion at mozbz#682838 different approach has been proposed.
Here's just one example of a use case, but there are many others:
Say a member of our billing team would receive a spreadsheet from a customer or sales partner where collaborative editing would be required. In order to get a file saved to a GVFS volume (SFTP team file folder), you would have to save locally first, then manually move the file over. This is slow for productivity reasons, and counter-intuitive. Being able to write to and from SFTP mounted volumes from Firefox and Thunderbird would greatly benefit users.
I'm afraid we can't make it before 6.4 because we're currently busy with ESR 17 rebase (it should be released in February 2013) and we're still blocked by Mozilla API changes in near future.