Closed
Bug 741187
Opened 14 years ago
Closed 14 years ago
browse button fatal crash
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 741053
People
(Reporter: contrib, Unassigned)
References
()
Details
Attachments
(1 file)
|
31.44 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:14.0) Gecko/20120331 Firefox/14.0a1
Build ID: 20120331035305
Steps to reproduce:
Go to any website with the feature giving the ability to upload a file as http://image-heberg.fr or http://www.tineye.com/
Click on the browse button.
Actual results:
Firefox crash, no talkback window, no detection of the crash
Expected results:
A window should open with the ability to select a file on my computer
| Reporter | ||
Updated•14 years ago
|
Comment 1•14 years ago
|
||
Thanks for taking the time to report this problem!
Please follow the steps on http://support.mozilla.com/kb/Firefox%20crashes and report back here. Thanks!
| Reporter | ||
Comment 2•14 years ago
|
||
Hi Andre,
Same problem in safe mode.
I can't provide a crash report due to the unavailability of about:crashes (cf https://bugzilla.mozilla.org/show_bug.cgi?id=741186 )
The output from the console is :
(firefox-trunk:3305): Gtk-CRITICAL **: IA__gtk_clipboard_set_with_data: assertion `targets != NULL' failed
Erreur de segmentation
Comment 3•14 years ago
|
||
(In reply to Anael from comment #2)
> I can't provide a crash report due to the unavailability of about:crashes
Can you provide a stack using steps in https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report?
| Reporter | ||
Comment 4•14 years ago
|
||
Comment 5•14 years ago
|
||
There's something wrong with your system/firefox build (ref. bug 741186, bug 741189, bug 741187). Let's figure out bug 741186 first.
The debug log you attached lacks symbols, so it's not very useful.
Whiteboard: [waits on resolution of bug 741186]
| Reporter | ||
Comment 6•14 years ago
|
||
Whiteboard: [waits on resolution of bug 741186]
Comment 7•14 years ago
|
||
Thanks! The stack trace and the situation in which the crash occurs is the same as in bug 741053.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•