Hi!
I lately migrated my Squirremail to Roundcube 1.0.2 (with courier-imap 4.10.0 from Debian Wheezy as backend) and at first everything seemed fine.
But now more and more users report they don't see all mails when they select a folder, which I am able to verify once I log in from my system with their user and a master-password.
It for example only shows three unread mails while at the same time displaying something like "1 to 50 of 342 mails" in the list status.
What I did so far:
- switched from memcached to db for the index_cache
- disabled the index_cache
- disabled SORTing in the IMAP server
I enabled the imap debug log in a test system which show the same problem. I can see roundcube fetches all messages, but displays only some of them.
Sometimes I can get all messages to display after I wildly toggle the search filter from "All" to "Unread" or "Marked" or "with attachments" and back and forth and back again.
So far I am quite desperate because there is a mob with pitchforks forming outside of my office.
Has anybody seen that behavior? Any idea how to debug this any further?
Grüße, Sven.
On 09/25/2014 04:34 PM, Sven Hartge wrote:
It for example only shows three unread mails while at the same time displaying something like "1 to 50 of 342 mails" in the list status.
Sounds like http://trac.roundcube.net/ticket/1489996
A.L.E.C alec@alec.pl wrote:
On 09/25/2014 04:34 PM, Sven Hartge wrote:
It for example only shows three unread mails while at the same time displaying something like "1 to 50 of 342 mails" in the list status.
Sounds like http://trac.roundcube.net/ticket/1489996
Hmm, no, unless I miss something important. Roundcube works normal for those users, but only some messages are displayed, usually 1 to three.
Besides I run the latest release-1.0 branch from git, so this specific problem should be fixed there, no?
But I just discovered something quite interesting while using Chrome with a user account having those problems and having the JavaScript console open:
Uncaught SecurityError: Failed to read the 'contentDocument' property from 'HTMLIFrameElement': Blocked a frame with origin "https://webmail.somedomain.private" from accessing a frame with origin "chrome-extension://hdokiejnpimakedhajhdlcegeplioahd". The frame requesting access has a protocol of "https", the frame being accessed has a protocol of "chrome-extension". Protocols must match.
This (hdokiejnpimakedhajhdlcegeplioahd) is the LastPass Chrome-Extension. If I disable this extension, the folder displays normally.
I guess I will have to ask the users in questions what browsers they use and what extensions are active.
Grüße, Sven.
Sven Hartge sven@svenhartge.de wrote:
But I just discovered something quite interesting while using Chrome with a user account having those problems and having the JavaScript console open:
Uncaught SecurityError: Failed to read the 'contentDocument' property from 'HTMLIFrameElement': Blocked a frame with origin "https://webmail.somedomain.private" from accessing a frame with origin "chrome-extension://hdokiejnpimakedhajhdlcegeplioahd". The frame requesting access has a protocol of "https", the frame being accessed has a protocol of "chrome-extension". Protocols must match.
I see, cPanel had the same problem and fixed it at their side: http://forums.cpanel.net/f5/lastpass-chrome-extension-breaks-some-whm-functi...
Grüße, Sven
Sven Hartge sven@svenhartge.de wrote:
[...]
I now copied the full error message, mayby it helps debug the issue.
Another data point: I spoke with a user who had this problem with Firefox and we found out the Plugin/Adware "Browser Companion Helper" was installed. After deactivating said plugin the problem went away and reenabling made the problem occur again.
Uncaught SecurityError: Failed to read the 'contentDocument' property from 'HTMLIFrameElement': Blocked a frame with origin "https://webmail.somedomain.private" from accessing a frame with origin "chrome-extension://hdokiejnpimakedhajhdlcegeplioahd". The frame requesting access has a protocol of "https", the frame being accessed has a protocol of "chrome-extension". Protocols must match. jquery.min.js?s=1410863569:2 n.each.contents jquery.min.js?s=1410863569:2 n.extend.map jquery.min.js?s=1410863569:2 n.fn.(anonymous function) jquery.min.js?s=1410863569:2 init contextmenu.js?s=1410248110:381 rcm_callbackmenu_init contextmenu.js?s=1410248110:195 rcm_listmenu_init contextmenu.js?s=1410248110:16 (anonymous function) functions.js?s=1401792207:11 rcube_event_engine.triggerEvent common.js?s=1410863573:344 init_message_row app.js?s=1410960629:1814 (anonymous function) app.js?s=1410960629:202 rcube_event_engine.triggerEvent common.js?s=1410863573:344 rcube_list_widget.init_row list.js?s=1410863569:147 rcube_list_widget.insert_row list.js?s=1410863569:321 add_message_row app.js?s=1410960629:1970 (anonymous function) VM459:5 http_response app.js?s=1410960629:7017 $.ajax.success app.js?s=1410960629:6942 j jquery.min.js?s=1410863569:2 k.fireWith jquery.min.js?s=1410863569:2 x jquery.min.js?s=1410863569:4 b jquery.min.js?s=1410863569:4
Grüße, Sven.
Sven Hartge sven@svenhartge.de wrote:
Another data point: I spoke with a user who had this problem with Firefox and we found out the Plugin/Adware "Browser Companion Helper" was installed. After deactivating said plugin the problem went away and reenabling made the problem occur again.
JFTR: Got another extension causing this problem, for both Firefix and Google Chrome: ICQ Toolbar.
One user had problems with that one installed, after disabling it, Roundcube worked again.
Grüße, Sven.
Sven Hartge sven@svenhartge.de wrote:
Sven Hartge sven@svenhartge.de wrote:
Another data point: I spoke with a user who had this problem with Firefox and we found out the Plugin/Adware "Browser Companion Helper" was installed. After deactivating said plugin the problem went away and reenabling made the problem occur again.
JFTR: Got another extension causing this problem, for both Firefix and Google Chrome: ICQ Toolbar.
Another offender has been found: Norton Security Toolbar
I wonder if anything can be done on the side of Roundcube to mitigate the impact of such extensions.
Grüße, Sven.
On Mon, Oct 20, 2014 at 1:31 PM, Sven Hartge sven@svenhartge.de wrote:
Sven Hartge sven@svenhartge.de wrote:
Sven Hartge sven@svenhartge.de wrote:
Another data point: I spoke with a user who had this problem with Firefox and we found out the Plugin/Adware "Browser Companion Helper" was installed. After deactivating said plugin the problem went away and reenabling made the problem occur again.
JFTR: Got another extension causing this problem, for both Firefix and Google Chrome: ICQ Toolbar.
Another offender has been found: Norton Security Toolbar
I wonder if anything can be done on the side of Roundcube to mitigate the impact of such extensions.
When I read the call stack correctly, the error raises from the call to "init" in "contextmenu.js:381" which is part of the 3rd party contextmenu plugin. Please contact the author of that plugin directly regarding this issue. From the Roundcube core side, I don't see anything we could right now.
~Thomas
Thomas Bruederli thomas@roundcube.net wrote:
On Mon, Oct 20, 2014 at 1:31 PM, Sven Hartge sven@svenhartge.de wrote:
Sven Hartge sven@svenhartge.de wrote:
Sven Hartge sven@svenhartge.de wrote:
Another data point: I spoke with a user who had this problem with Firefox and we found out the Plugin/Adware "Browser Companion Helper" was installed. After deactivating said plugin the problem went away and reenabling made the problem occur again.
JFTR: Got another extension causing this problem, for both Firefix and Google Chrome: ICQ Toolbar.
Another offender has been found: Norton Security Toolbar
I wonder if anything can be done on the side of Roundcube to mitigate the impact of such extensions.
When I read the call stack correctly, the error raises from the call to "init" in "contextmenu.js:381" which is part of the 3rd party contextmenu plugin. Please contact the author of that plugin directly regarding this issue. From the Roundcube core side, I don't see anything we could right now.
Ah! This was the information I was missing. This also explains why not more people see this problem. I have only about 1 per 1000 of my users experiencing this and if you don't use the context menu plugin then none of your users will see the error.
As far as I know, John reads this list, but I will open an issue in Github referencing this thread.
Grüße, Sven.
Sven Hartge sven@svenhartge.de wrote:
Thomas Bruederli thomas@roundcube.net wrote:
When I read the call stack correctly, the error raises from the call to "init" in "contextmenu.js:381" which is part of the 3rd party contextmenu plugin. Please contact the author of that plugin directly regarding this issue. From the Roundcube core side, I don't see anything we could right now.
Ah! This was the information I was missing. This also explains why not more people see this problem. I have only about 1 per 1000 of my users experiencing this and if you don't use the context menu plugin then none of your users will see the error.
As far as I know, John reads this list, but I will open an issue in Github referencing this thread.
Just to be complete for the archive: John has fixed this issue #59 with commit c6b0c32926.
So far, everthing seems to be in order, I have yet to receive another bug report from my users and I am myself unable to provoke or reproduce the problem.
Grüße, Sven.
-
A.L.E.C -
Sven Hartge -
Thomas Bruederli