Closed Bug 1238620 Opened 9 years ago Closed 9 years ago

Increase in user reports about uploading issues with trusteer rapport

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Version:
43 Branch
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox42 --- affected
firefox43 --- affected
firefox44 + affected
firefox45 + affected

People

(Reporter: philipp, Unassigned)

Details

[Tracking Requested - why for this release]: in the last months there is an increase of users in the sumo forum reporting that they are no longer able to upload larger files (some say over 500kb) to websites. these issues can generally be linked to the third-party trusteer rapport program that is running on their systems as disabling it can solve the issue...
here are some examples: https://support.mozilla.org/questions/firefox?tagged=bug1238620&show=all ilan, are you aware of those issues?
Flags: needinfo?(ilanf)
Component: Untriaged → Networking
Product: Firefox → Core
hi lawrence, maybe you can help bringing this to the attention of the right people as well. thanks!
Flags: needinfo?(lmandel)
Sylvestre - Can you please get in touch with Trusteer to share this issue?
Flags: needinfo?(lmandel) → needinfo?(sledru)
[Tracking Requested - why for this release]: Ritu, I believe we should track this. Email sent.
status-firefox44: --- → affected
tracking-firefox44: --- → ?
Flags: needinfo?(sledru)
They already replied with these questions: > Do you have a timeframe where this started? Also an example specific scenario / site to help us with the investigation? Philipp, any idea? Thanks
Flags: needinfo?(madperson)
according to one report the problem may have started on 2015/10/27 in particular. a common scenario that users tell us this issue is occurring, is when they are trying to upload photos over 500kb on their yahoo mail account as attachment or onto facebook.
Flags: needinfo?(madperson)
They get back to us yesterday: --- A fix for this issue was populated to our entire population on 13.1 with Rapport version 3.5.1507.104. We are monitoring the issue with our support teams and would appreciate if you would let us know if you still encounter this issue. --- So, it should be fixed soon.
Too late for 44, now a wontfix. Moving the tracking flag forward to Fx45.
status-firefox44: affected → wontfix
status-firefox45: --- → ?
tracking-firefox44: ? → -
tracking-firefox45: --- → ?
Philipp, could you find someone to verify if it is fixed or not? Thanks
status-firefox44: wontfix → affected
status-firefox45: ? → affected
tracking-firefox45: ? → +
Flags: needinfo?(ilanf) → needinfo?(madperson)
We might have a fix for this to tracking it for Fx44
tracking-firefox44: - → +
(In reply to Sylvestre Ledru [:sylvestre] from comment #9) > Philipp, could you find someone to verify if it is fixed or not? Thanks i've tried to follow up with a couple of affected users to find out if the update would fix this, but nobody replied. i haven't come across new reports fitting into this description recently anymore though, so this is a good sign at least! so i'll go ahead and change the status of the bug to resolved based on that...
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(madperson)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.