Page 1 of 2

File attachment fails in Chrome Version 50.0.2661.94 m

Posted: Tue May 10, 2016 3:13 pm
by hollyhubb
I was wondering if anyone else has seen this buggy behavior. Ever since the latest Chrome release (Version 50.0.2661.94 m), when users try to attach files using Chrome (AJAX, Zimbra 8.6.0_GA_1182), sometimes the files attach and sometimes nothing happens. It's so buggy that users may start the day not being able to attach files, then a few hours later they can, and then a few hours later they cannot. It has been incredibly difficult to troubleshoot because it is inconsistent. Sometimes I can open the user's mailbox via the admin console, using Chrome, and reproduce the problem but not always. I see no errors in the Windows logs nor in the Zimbra logs. No idea where to view Chrome logs if there are any. If anyone has experienced this issue, please let me know what you did to troubleshoot and resolve it. Thanks!

Re: File attachment fails in Chrome Version 50.0.2661.94 m

Posted: Tue May 10, 2016 5:35 pm
by L. Mark Stone
FWIW I have seen this behavior in several browsers over the past few months.

Hope that helps,
Mark

Re: File attachment fails in Chrome Version 50.0.2661.94 m

Posted: Wed May 11, 2016 6:28 pm
by xxcchhyy
same problem here

users run chrome on windows server 2008 R2 with latest updates

zimbra version - Release 8.6.0.GA.1153.UBUNTU14.64 UBUNTU14_64 FOSS edition, Patch 8.6.0_P6.

today chrome was updated to version 50.0.2661.102 m, tomorow I will see if it helps or not. If not, than I try to downgrade it, cant find another solution yet

Re: File attachment fails in Chrome Version 50.0.2661.94 m

Posted: Mon May 16, 2016 9:21 am
by slalomjohn
Zimbra 8.6.0_GA_1153.FOSS
Problem with attachments in Chrome 50.0.2661.102 m
In the Opera 37.0.2178.43 (on chrominium engine) no problems.
Symptoms:
1. Create new mail, enter (or no enter) recepients, click on "Attach", select file(s), click "Ok" - nothing doing - no attached file(s). O_o
2. Click again to "Attach" - select file(s), click "Ok" - 50% get error "Network error" or again get nothing in attachments or file(s) is attach to mail. O_O

Re: File attachment fails in Chrome Version 50.0.2661.94 m

Posted: Mon May 16, 2016 2:16 pm
by hollyhubb
Thank you all for confirming that you also experience the broken and inconsistent Chrome attachment behavior. If anyone finds a solution, I'm sure all of us would appreciate the sharing of that info. In the meantime my users have asked me to "fix Chrome" :shock: -Yeah, let me get started on that.... :lol:

Re: File attachment fails in Chrome Version 50.0.2661.94 m

Posted: Mon May 16, 2016 3:02 pm
by DualBoot
installing FireFox will solve the problem :mrgreen:

Re: File attachment fails in Chrome Version 50.0.2661.94 m

Posted: Mon May 23, 2016 8:01 am
by slalomjohn
DualBoot wrote:installing FireFox will solve the problem :mrgreen:


It's NOT resolve problem.
I can use Google Chrome, not Firefox.
If you can't help - don't posting any messages on this post, please.

Re: File attachment fails in Chrome Version 50.0.2661.94 m

Posted: Mon May 23, 2016 11:00 am
by DualBoot
If you want to be serious, may be you should pay for support ?

Re: File attachment fails in Chrome Version 50.0.2661.94 m

Posted: Fri May 27, 2016 7:21 am
by slalomjohn
DualBoot wrote:If you want to be serious, may be you should pay for support ?


Oh-oh... In the commercical version's this problem NOT detected? :?
Or developer's can fixed this bug in comercical version, but not fixed in FOSS? :|
I can't get fully support, but i can send erros and bugs to developers for correcting in future.

Re: File attachment fails in Chrome Version 50.0.2661.94 m

Posted: Fri May 27, 2016 10:04 am
by phoenix
slalomjohn wrote:
DualBoot wrote:If you want to be serious, may be you should pay for support ?


Oh-oh... In the commercical version's this problem NOT detected? :?
Or developer's can fixed this bug in comercical version, but not fixed in FOSS? :|
I can't get fully support, but i can send erros and bugs to developers for correcting in future.
Then you should file a report in Bugzilla.