grahamperrin - Project Hosting on Google Code

User Profile		Updates

Last 30 days Dec 18, 2009 jquerygears issue 1 (Safari 4.0.4 (6531.21.10) in Mac OS X 10.6.2 (10C540) pauses...) commented on - An alternative expression of the issue: * why is an OS that is without Gears and without ActiveX pausing at a line that seems to involve both Gears and ActiveX? An alternative expression of the issue: * why is an OS that is without Gears and without ActiveX pausing at a line that seems to involve both Gears and ActiveX? Dec 04, 2009 mozilla-keychain issue 13 (No prompt to update 1.0a7 to 1.0b1) reported - 1.0b1 was released over three months ago, I never received a prompt to update from 1.0a7. (I was half-way through reporting an incompatibility with Zotero 2.0b7.6, found Keychain Services Integration 1.0b1 only when I visited https://addons.mozilla.org/en-US/firefox/addon/13509 ). Are experimental add-ons excluded from Firefox update routines? 1.0b1 was released over three months ago, I never received a prompt to update from 1.0a7. (I was half-way through reporting an incompatibility with Zotero 2.0b7.6, found Keychain Services Integration 1.0b1 only when I visited https://addons.mozilla.org/en-US/firefox/addon/13509 ). Are experimental add-ons excluded from Firefox update routines? Dec 03, 2009 gears issue 847 ([Mac] [Safari 4] [Snow Leopard] Gears not working Safari 4 -...) commented on - Maybe exemplary: Saft extends Safari in any one of three ways, only one of which is limited to 32-bit. Screen shot at http://www.wuala.com/grahamperrin/public/2009/12/02/a/001.png The embrace of HTML 5 is welcomed. Parallel to that: if any developer is inclined to progress this issue 847, use of SIMBL may be most appropriate. http://www.culater.net/software/SIMBL/SIMBL.php Maybe exemplary: Saft extends Safari in any one of three ways, only one of which is limited to 32-bit. Screen shot at http://www.wuala.com/grahamperrin/public/2009/12/02/a/001.png The embrace of HTML 5 is welcomed. Parallel to that: if any developer is inclined to progress this issue 847, use of SIMBL may be most appropriate. http://www.culater.net/software/SIMBL/SIMBL.php Older Dec 02, 2009 jquerygears issue 1 (Safari 4.0.4 (6531.21.10) in Mac OS X 10.6.2 (10C540) pauses...) commented on - Screen shot of a pause at http://www.wuala.com/grahamperrin/public/2009/11/30/b/007.png Screen shot of a pause at http://www.wuala.com/grahamperrin/public/2009/11/30/b/007.png Dec 02, 2009 jquerygears issue 1 (Safari 4.0.4 (6531.21.10) in Mac OS X 10.6.2 (10C540) pauses...) commented on - Sorry, Google Code broke that Google Code URL :/ A short form of the same URL: http://ur1.ca/h0ip Sorry, Google Code broke that Google Code URL :/ A short form of the same URL: http://ur1.ca/h0ip Dec 02, 2009 jquerygears issue 1 (Safari 4.0.4 (6531.21.10) in Mac OS X 10.6.2 (10C540) pauses...) reported - Safari Web Inspector debugging scripts, pauses at factory = new ActiveXObject('Gears.Factory'); — that's at http://code.google.com/p/google-ajax- examples/source/browse/trunk/whereareyou/scripts/geometa.js?r=187#19 Safari Web Inspector debugging scripts, pauses at factory = new ActiveXObject('Gears.Factory'); — that's at http://code.google.com/p/google-ajax- examples/source/browse/trunk/whereareyou/scripts/geometa.js?r=187#19 Nov 28, 2009 rlog issue 7 (OS X 10.5 compile issue.) commented on - On Mac OS X 10.6.2 (10C540): [macbookpro08-centrim:~] gjp22% sudo port install rlog Password: ---> Computing dependencies for rlog ---> Fetching rlog ---> Attempting to fetch rlog-1.4.tar.gz from http://rlog.googlecode.com/files/ ---> Verifying checksum(s) for rlog ---> Extracting rlog ---> Applying patches to rlog ---> Configuring rlog ---> Building rlog ---> Staging rlog into destroot ---> Installing rlog @1.4_0 ---> Activating rlog @1.4_0 ---> Cleaning rlog [macbookpro08-centrim:~] gjp22% which rlog /usr/bin/rlog On Mac OS X 10.6.2 (10C540): [macbookpro08-centrim:~] gjp22% sudo port install rlog Password: ---> Computing dependencies for rlog ---> Fetching rlog ---> Attempting to fetch rlog-1.4.tar.gz from http://rlog.googlecode.com/files/ ---> Verifying checksum(s) for rlog ---> Extracting rlog ---> Applying patches to rlog ---> Configuring rlog ---> Building rlog ---> Staging rlog into destroot ---> Installing rlog @1.4_0 ---> Activating rlog @1.4_0 ---> Cleaning rlog [macbookpro08-centrim:~] gjp22% which rlog /usr/bin/rlog Nov 28, 2009 rlog issue 7 (OS X 10.5 compile issue.) commented on - [macbookpro08-centrim:~] gjp22% sudo port install rlog Password: ---> Computing dependencies for rlog ---> Fetching rlog ---> Attempting to fetch rlog-1.4.tar.gz from http://rlog.googlecode.com/files/ ---> Verifying checksum(s) for rlog ---> Extracting rlog ---> Applying patches to rlog ---> Configuring rlog ---> Building rlog ---> Staging rlog into destroot ---> Installing rlog @1.4_0 ---> Activating rlog @1.4_0 ---> Cleaning rlog [macbookpro08-centrim:~] gjp22% which rlog /usr/bin/rlog [macbookpro08-centrim:~] gjp22% sudo port install rlog Password: ---> Computing dependencies for rlog ---> Fetching rlog ---> Attempting to fetch rlog-1.4.tar.gz from http://rlog.googlecode.com/files/ ---> Verifying checksum(s) for rlog ---> Extracting rlog ---> Applying patches to rlog ---> Configuring rlog ---> Building rlog ---> Staging rlog into destroot ---> Installing rlog @1.4_0 ---> Activating rlog @1.4_0 ---> Cleaning rlog [macbookpro08-centrim:~] gjp22% which rlog /usr/bin/rlog Nov 22, 2009 greasekit issue 44 (Stop promoting the two Google Groups until after moderation ...) reported - http://groups.google.com/group/greasekit-users/topics http://groups.google.com/group/greasekit-dev/topics > LIVE SEX VIDEO CHAT … etc., creates a poor first impression of support for a very good software product. = Suggestion = At http://8-p.info/greasekit/ stop promoting the two groups until after the spam is removed and controlled. http://groups.google.com/group/greasekit-users/topics http://groups.google.com/group/greasekit-dev/topics > LIVE SEX VIDEO CHAT … etc., creates a poor first impression of support for a very good software product. = Suggestion = At http://8-p.info/greasekit/ stop promoting the two groups until after the spam is removed and controlled. Nov 21, 2009 greasekit issue 43 (inclusions and exclusions in the application support .js fil...) reported - Safari 4.0.4 (6531.21.10) Mac OS X 10.6.2 (10C540) FileVault enabled SIMBL 0.8.2 (maybe reporting itself as 0.8.1) Saft 12.0.2 (8020) http://userscripts.org/scripts/show/42087 Install GreaseKit menu \| Manage Scripts… select Diigolet click Edit (launches Dashcode) add inclusions and exclusions save the .js file command-tab to switch to Safari GreaseKit menu \| Reload All User Scripts = Issue = The exclusions specified in the file are neither listed in the UI of GreaseKit, nor effective in the browser. Safari 4.0.4 (6531.21.10) Mac OS X 10.6.2 (10C540) FileVault enabled SIMBL 0.8.2 (maybe reporting itself as 0.8.1) Saft 12.0.2 (8020) http://userscripts.org/scripts/show/42087 Install GreaseKit menu \| Manage Scripts… select Diigolet click Edit (launches Dashcode) add inclusions and exclusions save the .js file command-tab to switch to Safari GreaseKit menu \| Reload All User Scripts = Issue = The exclusions specified in the file are neither listed in the UI of GreaseKit, nor effective in the browser. Nov 21, 2009 greasekit issue 42 (hyphen in filename of application support .js file can cause...) commented on - The workaround was temporary. Now, I suspect that the problem is not related to a hyphen in the name of the file. The workaround was temporary. Now, I suspect that the problem is not related to a hyphen in the name of the file. Nov 21, 2009 greasekit issue 42 (hyphen in filename of application support .js file can cause...) reported - At ~/Library/Application Support/GreaseKit/ I created a file diigolet-greasekit.user Inclusions and exclusions specified within the file were not shown in the GreaseKit UI, and vice versa. = Workaround = 1. In Finder: rename the file, do not use a hyphen 2. in GreaseKit, reload all user scripts. At ~/Library/Application Support/GreaseKit/ I created a file diigolet-greasekit.user Inclusions and exclusions specified within the file were not shown in the GreaseKit UI, and vice versa. = Workaround = 1. In Finder: rename the file, do not use a hyphen 2. in GreaseKit, reload all user scripts. Nov 21, 2009 grahamperrin Starred project greasekit Nov 19, 2009 google-caldav-issues issue 26 (Can only store an event with a newer DTSTAMP is inaccurate) commented on - Referred from https://bugzilla.osafoundation.org/show_bug.cgi?id=12377#c5 Referred from https://bugzilla.osafoundation.org/show_bug.cgi?id=12377#c5 Nov 18, 2009 grahamperrin Starred project kcaldav Nov 17, 2009 soundflower issue 42 (Soundflower installs with weird permissions under non-admin) commented on - Similarly, I used Finder to change permissions for /Applications/Soundflower from no access to read only for everyone. Similarly, I used Finder to change permissions for /Applications/Soundflower from no access to read only for everyone. Nov 01, 2009 grahamperrin Starred project pubsubhubbub Sep 11, 2009 mozilla-keychain issue 2 (Can not sign in to Weave whilst Keychain Services Integratio...) commented on - Apparently resolved in/around Weave 0.7pre2 http://www.wuala.com/grahamperrin/public/2009/09/12/a.png Apparently resolved in/around Weave 0.7pre2 http://www.wuala.com/grahamperrin/public/2009/09/12/a.png Sep 11, 2009 mozilla-keychain issue 7 (whilst Keychain Services Integration 1.0a7 is enabled: Weave...) commented on - Apparently resolved in/around Weave 0.7pre2 http://www.wuala.com/grahamperrin/public/2009/09/12/a.png Apparently resolved in/around Weave 0.7pre2 http://www.wuala.com/grahamperrin/public/2009/09/12/a.png Aug 29, 2009 mozilla-keychain issue 5 (Already-loaded login passwords kept available even after key...) commented on - > enter basic authentication info into Safari once, and you're never > prompted again for the rest of your computer's existence Are we sure about that? The norm is: simply quit then relaunch the browser. A revisit to a URL that requires authenitcation will result in a prompt for re-authentication. Exceptions to that norm may arise from e.g. service providers' use of cookies _in addition to_ HTTP authentication. Topics that come to mind include http://groups.diigo.com/Diigo_HQ/forum/topic/9103 http://groups.diigo.com/Diigo_HQ/forum/topic/43029 http://groups.diigo.com/Diigo_HQ/forum/topic/43081 http://groups.diigo.com/Diigo_HQ/forum/topic/43168 where AFAICT diigoandlogincookie is valid for one year and Firefox behaviour was the odd one out -- Firefox requiring authenitcation at unexpected times, much to the ire of users. Eventually Firefox began behaving in the expected way, I guess that Diigo refined diigoandlogincookie to cater for a peculiarty of Firefox. > enter basic authentication info into Safari once, and you're never > prompted again for the rest of your computer's existence Are we sure about that? The norm is: simply quit then relaunch the browser. A revisit to a URL that requires authenitcation will result in a prompt for re-authentication. Exceptions to that norm may arise from e.g. service providers' use of cookies _in addition to_ HTTP authentication. Topics that come to mind include http://groups.diigo.com/Diigo_HQ/forum/topic/9103 http://groups.diigo.com/Diigo_HQ/forum/topic/43029 http://groups.diigo.com/Diigo_HQ/forum/topic/43081 http://groups.diigo.com/Diigo_HQ/forum/topic/43168 where AFAICT diigoandlogincookie is valid for one year and Firefox behaviour was the odd one out -- Firefox requiring authenitcation at unexpected times, much to the ire of users. Eventually Firefox began behaving in the expected way, I guess that Diigo refined diigoandlogincookie to cater for a peculiarty of Firefox. Aug 28, 2009 mozilla-keychain issue 5 (Already-loaded login passwords kept available even after key...) commented on - No argument that it could be useful, tsaling has described a use case. I see a different question … if a goal of Keychain Services Integration is: * to make Firefox _closer_ to Apple guidelines then should this particular add-on have options that make Firefox _less_ consistent with Apple application behaviours? If you alter what's normally expected of Keychain Services, for Mozilla/Firefox alone, it could be a step back down the road of Firefox being a less than sterling OS citizen. No objection to the feature request :-) just wondering whether this particular add-on (keyword: integration) is the best place for options that alter or extend the norm. Does that make sense? No argument that it could be useful, tsaling has described a use case. I see a different question … if a goal of Keychain Services Integration is: * to make Firefox _closer_ to Apple guidelines then should this particular add-on have options that make Firefox _less_ consistent with Apple application behaviours? If you alter what's normally expected of Keychain Services, for Mozilla/Firefox alone, it could be a step back down the road of Firefox being a less than sterling OS citizen. No objection to the feature request :-) just wondering whether this particular add-on (keyword: integration) is the best place for options that alter or extend the norm. Does that make sense? Aug 28, 2009 mozilla-keychain issue 7 (whilst Keychain Services Integration 1.0a7 is enabled: Weave...) commented on - Quit from Firefox, launched Firefox, reproduced the bug > ! > [JavaScript Application] > Couldn't sign in: null > [[OK]] Quit from Firefox, launched Firefox, reproduced the bug > ! > [JavaScript Application] > Couldn't sign in: null > [[OK]] Aug 28, 2009 mozilla-keychain issue 2 (Can not sign in to Weave whilst Keychain Services Integratio...) commented on - I spun it off to issue 7. May be a separate issue. I spun it off to issue 7. May be a separate issue. Aug 28, 2009 mozilla-keychain issue 7 (whilst Keychain Services Integration 1.0a7 is enabled: Weave...) commented on - > can't reproduce the bug. Odd. More specifically, nothing happens when I click Sign In. > can't reproduce the bug. Odd. More specifically, nothing happens when I click Sign In. Aug 28, 2009 mozilla-keychain issue 7 (whilst Keychain Services Integration 1.0a7 is enabled: Weave...) reported - 1. Firefox \| Tools \| Weave \| Sign In… 2. in the 'Sign in to Weave' dialogue, complete the three fields 3. click Sign In = Environment = * Firefox 3.5.2 * Mac OS X 10.6 * Weave 0.6 * Keychain Services Integration 1.0a7 = Bug = A sheet dropped down from the title bar of the Firefox window, > ! > [JavaScript Application] > Couldn't sign in: null > [[OK]] = Origin = Originally reported at http://code.google.com/p/mozilla-keychain/issues/detail?id=2#c13 = Reproduction = Now, I can't reproduce the bug. Odd. 1. Firefox \| Tools \| Weave \| Sign In… 2. in the 'Sign in to Weave' dialogue, complete the three fields 3. click Sign In = Environment = * Firefox 3.5.2 * Mac OS X 10.6 * Weave 0.6 * Keychain Services Integration 1.0a7 = Bug = A sheet dropped down from the title bar of the Firefox window, > ! > [JavaScript Application] > Couldn't sign in: null > [[OK]] = Origin = Originally reported at http://code.google.com/p/mozilla-keychain/issues/detail?id=2#c13 = Reproduction = Now, I can't reproduce the bug. Odd. Aug 28, 2009 mozilla-keychain issue 5 (Already-loaded login passwords kept available even after key...) commented on - I should add, in step 4 above I use Safari as the benchmark. I should add, in step 4 above I use Safari as the benchmark. Aug 28, 2009 mozilla-keychain issue 5 (Already-loaded login passwords kept available even after key...) commented on - > If I've authenticated to a page, then locked my keychain - say by > starting the screensaver or putting the computer to sleep - I > would argue that those active logins should be cleared and > keychain reauthentication be required I'm not sure that this is correct, at least for authentication of the type that's required for e.g. http://preview.diigo.com/ 1. show Keychain Access status in menu bar 2. quit Keychain Access 3. lock all keychains 4. visit a site that requires authentication -- one for which you have no key in a keychain 5. authenticate -- and DO NOT save in the keychain 6. lock your screen, wait a while 7. unlock your screen, reload the page. Re-authentication in this situation is not required. > If I've authenticated to a page, then locked my keychain - say by > starting the screensaver or putting the computer to sleep - I > would argue that those active logins should be cleared and > keychain reauthentication be required I'm not sure that this is correct, at least for authentication of the type that's required for e.g. http://preview.diigo.com/ 1. show Keychain Access status in menu bar 2. quit Keychain Access 3. lock all keychains 4. visit a site that requires authentication -- one for which you have no key in a keychain 5. authenticate -- and DO NOT save in the keychain 6. lock your screen, wait a while 7. unlock your screen, reload the page. Re-authentication in this situation is not required. Aug 28, 2009 mozilla-keychain issue 2 (Can not sign in to Weave whilst Keychain Services Integratio...) commented on - Now using Weave 0.6, the symptoms are different: > ! > [JavaScript Application] > Couldn't sign in: null > [[OK]] @ jfitzell Would you like me to continue in this report? Or shall we close this one and begin anew for 0.6? Now using Weave 0.6, the symptoms are different: > ! > [JavaScript Application] > Couldn't sign in: null > [[OK]] @ jfitzell Would you like me to continue in this report? Or shall we close this one and begin anew for 0.6? Aug 19, 2009 mozilla-keychain issue 2 (Can not sign in to Weave whilst Keychain Services Integratio...) commented on - Not my extension, it's the developer's :-) and thanks for clarifying. In any case, it's useful to think about what's possible within Apple's API for Keychain Services. Apple guides readers to http://www.opengroup.org/security/cdsa.htm Not my extension, it's the developer's :-) and thanks for clarifying. In any case, it's useful to think about what's possible within Apple's API for Keychain Services. Apple guides readers to http://www.opengroup.org/security/cdsa.htm Aug 19, 2009 mozilla-keychain issue 2 (Can not sign in to Weave whilst Keychain Services Integratio...) commented on - > fixed in Keychain Services! If a change is desired to Keychain Services, the suggestion should be made to Apple. > fixed in Keychain Services! If a change is desired to Keychain Services, the suggestion should be made to Apple. Aug 19, 2009 mozilla-keychain issue 4 (Sync with password manager) commented on - > the Keychain was kept in sync with the Password Manager Use case: I have nine keychains, necessarily separate. Each keychain relates to a role/function that may be handed over to a colleague, should I leave my place of work. Whilst synchronisation is desirable, I could not allow sync -- from Password Manager -- to place in any keychain an item that does not belong there. So: sync should should be optional. > the Keychain was kept in sync with the Password Manager Use case: I have nine keychains, necessarily separate. Each keychain relates to a role/function that may be handed over to a colleague, should I leave my place of work. Whilst synchronisation is desirable, I could not allow sync -- from Password Manager -- to place in any keychain an item that does not belong there. So: sync should should be optional. Aug 19, 2009 mozilla-keychain issue 4 (Sync with password manager) commented on - > use Weave Please see http://groups.google.com/group/mozilla-labs-weave/browse_frm/thread/bcfdeb3866f99e3a 'Weave, with Sync Services and Keychain Services in Mac OS X' (referred from http://www.brighton.ac.uk/centrim/Members/gjp4/2009/08/06 ). Also, at https://bugzilla.mozilla.org/show_bug.cgi?id=106400#c74 : > … an inherent problem with chrome:// passwords (usually stored by extensions, > Weave for example) … > use Weave Please see http://groups.google.com/group/mozilla-labs-weave/browse_frm/thread/bcfdeb3866f99e3a 'Weave, with Sync Services and Keychain Services in Mac OS X' (referred from http://www.brighton.ac.uk/centrim/Members/gjp4/2009/08/06 ). Also, at https://bugzilla.mozilla.org/show_bug.cgi?id=106400#c74 : > … an inherent problem with chrome:// passwords (usually stored by extensions, > Weave for example) … Aug 18, 2009 calaboration issue 56 (All calendars are showing up checked/grayed (even ones that ...) commented on - … more specifically, try resetting the SyncServices folder as part of a broader strategy. Including MobileMe in the mix (for a moment, ignoring the fact that David has not mentioned MobileMe): 1. disable any aspect of MobileMe that might affect synchronisation of calendars 2. in iSync, review preferences of all other virtual and physical devices — does there remain any reference to a calendar in Google Calendar? If so, remove that reference 3. disable or remove any other software that might affect synchronisation of calendars — think way back: have you experimented with other products? 4. disable or remove any other software that might affect interpretation of calendar-related files on disk — http://pastebin.ca/1534651 reminds me of a problem with even-t 5. remove from iCal all references to calendars in Google Calendar 6. restart Mac OS X 7. be patient, work without Google Calendar for a day or so 8. reset the SyncServices folder, restart Mac OS X 9. again be patient, work without Google Calendar for a day or so 10. restart Mac OS X 11. run Calaboration. That's fairly extreme, you might try it without steps 7 and 9. (So, why steps 7 and 9? Off-topic from Calaboration: simply removing even-t and restarting the OS did not resolve my problem. Some time later (days later?), my problem (Spotlight not effective in iCal) disappeared. That's a nebulous comment but I remind myself that in particularly puzzling situations, it may help to wait patiently after a step within a troubleshooting routine. Afterthought: maybe a daily, weekly or monthly cron or comparable job played a part in my case.) We also have products such as AppleJack http://applejack.sourceforge.net/ and OnyX http://www.titanium.free.fr/pgs/english.html for maintenance of caches etc. in single and multi user modes, but I don't imagine a need for them in this particular situation. … more specifically, try resetting the SyncServices folder as part of a broader strategy. Including MobileMe in the mix (for a moment, ignoring the fact that David has not mentioned MobileMe): 1. disable any aspect of MobileMe that might affect synchronisation of calendars 2. in iSync, review preferences of all other virtual and physical devices — does there remain any reference to a calendar in Google Calendar? If so, remove that reference 3. disable or remove any other software that might affect synchronisation of calendars — think way back: have you experimented with other products? 4. disable or remove any other software that might affect interpretation of calendar-related files on disk — http://pastebin.ca/1534651 reminds me of a problem with even-t 5. remove from iCal all references to calendars in Google Calendar 6. restart Mac OS X 7. be patient, work without Google Calendar for a day or so 8. reset the SyncServices folder, restart Mac OS X 9. again be patient, work without Google Calendar for a day or so 10. restart Mac OS X 11. run Calaboration. That's fairly extreme, you might try it without steps 7 and 9. (So, why steps 7 and 9? Off-topic from Calaboration: simply removing even-t and restarting the OS did not resolve my problem. Some time later (days later?), my problem (Spotlight not effective in iCal) disappeared. That's a nebulous comment but I remind myself that in particularly puzzling situations, it may help to wait patiently after a step within a troubleshooting routine. Afterthought: maybe a daily, weekly or monthly cron or comparable job played a part in my case.) We also have products such as AppleJack http://applejack.sourceforge.net/ and OnyX http://www.titanium.free.fr/pgs/english.html for maintenance of caches etc. in single and multi user modes, but I don't imagine a need for them in this particular situation. Aug 18, 2009 calaboration issue 56 (All calendars are showing up checked/grayed (even ones that ...) commented on - Try resetting the SyncServices folder, http://support.apple.com/kb/TS1627 Try resetting the SyncServices folder, http://support.apple.com/kb/TS1627 Aug 14, 2009 grahamperrin Starred project oberfs Aug 10, 2009 mozilla-keychain issue 2 (Can not sign in to Weave whilst Keychain Services Integratio...) commented on - The bug in Mozilla is invalidated. The bug in Mozilla is invalidated. Aug 07, 2009 mozilla-keychain issue 2 (Can not sign in to Weave whilst Keychain Services Integratio...) commented on - Re http://groups.google.com/group/mozilla-labs-weave/browse_frm/thread/e4f7ec3d074444cc I tried Weave 0.6pre1, no improvement. > I remember checking the Error Console, and there was an exception When I click the Sign In button, the messages area of Error Console reports: Invalid chrome URI: / The Activity Log of Weave presents no information coinciding with my click on the button. Re http://groups.google.com/group/mozilla-labs-weave/browse_frm/thread/e4f7ec3d074444cc I tried Weave 0.6pre1, no improvement. > I remember checking the Error Console, and there was an exception When I click the Sign In button, the messages area of Error Console reports: Invalid chrome URI: / The Activity Log of Weave presents no information coinciding with my click on the button. Aug 07, 2009 mozilla-keychain issue 2 (Can not sign in to Weave whilst Keychain Services Integratio...) commented on - Cross-posted to https://bugzilla.mozilla.org/show_bug.cgi?id=509007 Cross-posted to https://bugzilla.mozilla.org/show_bug.cgi?id=509007 Aug 06, 2009 mozilla-keychain issue 3 (credentials for Squid proxy-caching web server not drawn fro...) commented on - When I launch Firefox with it reloading a single page, http://centrim.mis.brighton.ac.uk/Members/gjp4/2009/08/06 I entered my credentials thirteen times before the dialogue stopped reappearing. If I close all windows then quit then re-launch, again the dialogue appears a few times. Maybe each dialogue corresponds to an add-in (I have e.g. Diigo and Xmarks). When I launch Firefox with it reloading a single page, http://centrim.mis.brighton.ac.uk/Members/gjp4/2009/08/06 I entered my credentials thirteen times before the dialogue stopped reappearing. If I close all windows then quit then re-launch, again the dialogue appears a few times. Maybe each dialogue corresponds to an add-in (I have e.g. Diigo and Xmarks). Aug 06, 2009 mozilla-keychain issue 3 (credentials for Squid proxy-caching web server not drawn fro...) reported - For all keychain entries relating to wwwcache.sussex.ac.uk I have added Firefox to the access control list, = Problem = Whilst connected to the Roaming Wi-Fi network at University of Sussex, after I launch Firefox and as it attempts to reload pages from a previous session, Firefox repeatedly presents an authentication dialogue — ? Authentication Required The proxy wwwcache.sussex.ac.uk:80 is requesting a user name and password. The site says: "Squid proxy- caching web server" User Name: Password: [Cancel] [[OK]] — and when I enter my user name, the password is not drawn from the keychain. If I enter my credentials manually maybe eight times in a row, the dialogue stops reappearing. http://www.diigo.com/06s9n for an annotated view of http://www.sussex.ac.uk/its/help/guides/cache , the 'Mozilla Firefox (Mac OS X)' section of which is possibly outdated; more recent versions of Firefox normally allow the user to [•] Use system proxy settings For me personally, this issue is negligible. In this building I most often make a wired network connection (requiring no proxy configuration) and before too long, the 'Roaming' network infrastructure will be replaced with something more capable. This report of the issue is mainly for the benefit of other users who may encounter the issue with other servers. For all keychain entries relating to wwwcache.sussex.ac.uk I have added Firefox to the access control list, = Problem = Whilst connected to the Roaming Wi-Fi network at University of Sussex, after I launch Firefox and as it attempts to reload pages from a previous session, Firefox repeatedly presents an authentication dialogue — ? Authentication Required The proxy wwwcache.sussex.ac.uk:80 is requesting a user name and password. The site says: "Squid proxy- caching web server" User Name: Password: [Cancel] [[OK]] — and when I enter my user name, the password is not drawn from the keychain. If I enter my credentials manually maybe eight times in a row, the dialogue stops reappearing. http://www.diigo.com/06s9n for an annotated view of http://www.sussex.ac.uk/its/help/guides/cache , the 'Mozilla Firefox (Mac OS X)' section of which is possibly outdated; more recent versions of Firefox normally allow the user to [•] Use system proxy settings For me personally, this issue is negligible. In this building I most often make a wired network connection (requiring no proxy configuration) and before too long, the 'Roaming' network infrastructure will be replaced with something more capable. This report of the issue is mainly for the benefit of other users who may encounter the issue with other servers. Aug 06, 2009 mozilla-keychain issue 2 (Can not sign in to Weave whilst Keychain Services Integratio...) commented on - FWIW I prefer to disable Weave. http://www.brighton.ac.uk/centrim/Members/gjp4/2009/08/06 highlights some related questions concerning Weave and the traditional Mozilla approach to saved passwords. (I should encourage discussion away from this issue tracker.) My gut feeling is that the conclusion to this issue will be wontfix … in other words, Weave should take a more integrated approach. FWIW I prefer to disable Weave. http://www.brighton.ac.uk/centrim/Members/gjp4/2009/08/06 highlights some related questions concerning Weave and the traditional Mozilla approach to saved passwords. (I should encourage discussion away from this issue tracker.) My gut feeling is that the conclusion to this issue will be wontfix … in other words, Weave should take a more integrated approach. Aug 05, 2009 mozilla-keychain issue 2 (Can not sign in to Weave whilst Keychain Services Integratio...) commented on - If I omit both password and passphrase, the Sign In button is followed (as expected) by a prompt to enter a password. If I omit the passphrase alone, the Sign In button is followed by a prompt to enter a phrase. If I omit the password alone, the Sign In button is followed by a prompt to enter a password. If I omit both password and passphrase, the Sign In button is followed (as expected) by a prompt to enter a password. If I omit the passphrase alone, the Sign In button is followed by a prompt to enter a phrase. If I omit the password alone, the Sign In button is followed by a prompt to enter a password. Aug 05, 2009 mozilla-keychain issue 2 (Can not sign in to Weave whilst Keychain Services Integratio...) commented on - Re the two options, [ ] Save password on this computer [ ] Automatically connect each time I start Firefox checking/unchecking seems to make no difference. Re the two options, [ ] Save password on this computer [ ] Automatically connect each time I start Firefox checking/unchecking seems to make no difference. Aug 05, 2009 mozilla-keychain issue 2 (Can not sign in to Weave whilst Keychain Services Integratio...) reported - Firefox 3.5.2, Mac OS X Weave 0.5 Keychain Services Integration 1.0a7 1. aim to sign in to Weave 2. in the 'Sign in to Weave' dialogue, complete the three fields 3. click Sign In = Bug = The Sign In button appears to be ineffective whilst Keychain Services Integration 1.0a7 is enabled. Help button is effective, but the resulting window does not appear until after the Cancel button is clicked. Cancel button is effective. Firefox 3.5.2, Mac OS X Weave 0.5 Keychain Services Integration 1.0a7 1. aim to sign in to Weave 2. in the 'Sign in to Weave' dialogue, complete the three fields 3. click Sign In = Bug = The Sign In button appears to be ineffective whilst Keychain Services Integration 1.0a7 is enabled. Help button is effective, but the resulting window does not appear until after the Cancel button is clicked. Cancel button is effective. Aug 04, 2009 sabredav TemporaryFileFilter (How to deal with the various temporary files clients create) Wiki page commented on - Treatment of all ._ files as temporary is not a good idea. Please see http://groups.google.com/group/sabredav-discuss/browse_frm/thread/a07d6cf6bc7b7b07/15b23ae8fabadbc1#15b23ae8fabadbc1 Treatment of all ._ files as temporary is not a good idea. Please see http://groups.google.com/group/sabredav-discuss/browse_frm/thread/a07d6cf6bc7b7b07/15b23ae8fabadbc1#15b23ae8fabadbc1 Jul 08, 2009 grahamperrin Starred project webdesktop-macosx Jun 30, 2009 chromium issue 10395 (3 Failing Layout Tests) commented on - I agree that it shouldn't block the release, but I'd like to see support for WebArchive in a future version. http://www.google.com/support/forum/p/Chrome/thread?tid=76aec22ddd494096&hl=en is my suggestion in the Chrome area, > Support WebArchive class and WebArchive format in Chromium and Chrome See also issue 15730, > outdated comment in test_expectations.txt I agree that it shouldn't block the release, but I'd like to see support for WebArchive in a future version. http://www.google.com/support/forum/p/Chrome/thread?tid=76aec22ddd494096&hl=en is my suggestion in the Chrome area, > Support WebArchive class and WebArchive format in Chromium and Chrome See also issue 15730, > outdated comment in test_expectations.txt Jun 30, 2009 chromium issue 15730 (outdated comment in test_expectations.txt) commented on - Sorry, a typo: Issue 10395 Sorry, a typo: Issue 10395 Jun 30, 2009 chromium issue 15730 (outdated comment in test_expectations.txt) reported - At http://src.chromium.org/viewvc/chrome/trunk/src/webkit/tools/layout_tests/test_expect ations.txt?view=markup&pathrev=19462 there are comments, // Chrome does not support WebArchives (just like Safari for Windows), // although we might eventually want to on Mac. Both lines of that comment are outdated: * Safari 4 for Windows does write and read WebArchive format * Chromium/Chrome support for the format is equally desirable on Windows. Suggestion: refer to ssue 10395: 3 Failing Layout Tests http://www.diigo.com/06fj6 for a highlighted view of the comments. At http://src.chromium.org/viewvc/chrome/trunk/src/webkit/tools/layout_tests/test_expect ations.txt?view=markup&pathrev=19462 there are comments, // Chrome does not support WebArchives (just like Safari for Windows), // although we might eventually want to on Mac. Both lines of that comment are outdated: * Safari 4 for Windows does write and read WebArchive format * Chromium/Chrome support for the format is equally desirable on Windows. Suggestion: refer to ssue 10395: 3 Failing Layout Tests http://www.diigo.com/06fj6 for a highlighted view of the comments. Jun 04, 2009 grahamperrin Starred project ical2svg

issue 56 (All calendars are showing up checked/grayed (even ones that ...) commented on - … more specifically, try resetting the SyncServices folder as part of a broader strategy. Including MobileMe in the mix (for a moment, ignoring the fact that David has not mentioned MobileMe): 1. disable any aspect of MobileMe that might affect synchronisation of calendars 2. in iSync, review preferences of all other virtual and physical devices — does there remain any reference to a calendar in Google Calendar? If so, remove that reference 3. disable or remove any other software that might affect synchronisation of calendars — think way back: have you experimented with other products? 4. disable or remove any other software that might affect interpretation of calendar-related files on disk — http://pastebin.ca/1534651 reminds me of a problem with even-t 5. remove from iCal all references to calendars in Google Calendar 6. restart Mac OS X 7. be patient, work without Google Calendar for a day or so 8. reset the SyncServices folder, restart Mac OS X 9. again be patient, work without Google Calendar for a day or so 10. restart Mac OS X 11. run Calaboration. That's fairly extreme, you might try it without steps 7 and 9. (So, why steps 7 and 9? Off-topic from Calaboration: simply removing even-t and restarting the OS did not resolve my problem. Some time later (days later?), my problem (Spotlight not effective in iCal) disappeared. That's a nebulous comment but I remind myself that in particularly puzzling situations, it may help to wait patiently after a step within a troubleshooting routine. Afterthought: maybe a daily, weekly or monthly cron or comparable job played a part in my case.) We also have products such as AppleJack http://applejack.sourceforge.net/ and OnyX http://www.titanium.free.fr/pgs/english.html for maintenance of caches etc. in single and multi user modes, but I don't imagine a need for them in this particular situation.

… more specifically, try resetting the SyncServices folder as part of a broader strategy. Including MobileMe in the mix (for a moment, ignoring the fact that David has not mentioned MobileMe): 1. disable any aspect of MobileMe that might affect synchronisation of calendars 2. in iSync, review preferences of all other virtual and physical devices — does there remain any reference to a calendar in Google Calendar? If so, remove that reference 3. disable or remove any other software that might affect synchronisation of calendars — think way back: have you experimented with other products? 4. disable or remove any other software that might affect interpretation of calendar-related files on disk — http://pastebin.ca/1534651 reminds me of a problem with even-t 5. remove from iCal all references to calendars in Google Calendar 6. restart Mac OS X 7. be patient, work without Google Calendar for a day or so 8. reset the SyncServices folder, restart Mac OS X 9. again be patient, work without Google Calendar for a day or so 10. restart Mac OS X 11. run Calaboration. That's fairly extreme, you might try it without steps 7 and 9. (So, why steps 7 and 9? Off-topic from Calaboration: simply removing even-t and restarting the OS did not resolve my problem. Some time later (days later?), my problem (Spotlight not effective in iCal) disappeared. That's a nebulous comment but I remind myself that in particularly puzzling situations, it may help to wait patiently after a step within a troubleshooting routine. Afterthought: maybe a daily, weekly or monthly cron or comparable job played a part in my case.) We also have products such as AppleJack http://applejack.sourceforge.net/ and OnyX http://www.titanium.free.fr/pgs/english.html for maintenance of caches etc. in single and multi user modes, but I don't imagine a need for them in this particular situation.

Last 30 days

Older