gears - Project Hosting on Google Code

Today 10 hours ago issue 988 (Gears doesn't work on FF 3.5.6 on Snow Leopard) reported by jmcdon10 - What steps will reproduce the problem? 1. Go to Google Calendar 2. Click 'offline' 3. click through dialog boxes. What is the expected output? What do you see instead? I expect Gcal to download calendar information via gears. Instead the 'offline' link becomes an orange circle with a white exclamation mark, and I get an error: Illegal redirect to a different origin What version of the product are you using? On what operating system? 3.5.6 on Snow Leopard. Please provide any additional information below. I had Gears installed on Safari from before Snow Leopard, so I uninstalled it using '/Library/Internet Plug-Ins/Gears.plugin/Contents/Resources/uninstall.command' and installed it via Firefox instead. I've tried disabling scripts and extensions, but to no avail (I don't have many anyway). What steps will reproduce the problem? 1. Go to Google Calendar 2. Click 'offline' 3. click through dialog boxes. What is the expected output? What do you see instead? I expect Gcal to download calendar information via gears. Instead the 'offline' link becomes an orange circle with a white exclamation mark, and I get an error: Illegal redirect to a different origin What version of the product are you using? On what operating system? 3.5.6 on Snow Leopard. Please provide any additional information below. I had Gears installed on Safari from before Snow Leopard, so I uninstalled it using '/Library/Internet Plug-Ins/Gears.plugin/Contents/Resources/uninstall.command' and installed it via Firefox instead. I've tried disabling scripts and extensions, but to no avail (I don't have many anyway). Yesterday 25 hours ago issue 987 (Not compatible with Linux x86 GCC3) commented on by operayatri - Same happening and I please need urgently to solve it!! Same happening and I please need urgently to solve it!! 33 hours ago issue 979 (Google Gears not compatible with your version of FireFox (Li...) commented on by louis.fourie - Same problem here. And since today it fails to update my Gmail Inbox. I need to disable Offline mode to be able to see any new mail. Same problem here. And since today it fails to update my Gmail Inbox. I need to disable Offline mode to be able to see any new mail. 41 hours ago issue 977 (Update fails on Linux/Firefox (incompatible build type)) commented on by rogerslurchers - Not working Ubuntu 9.10 and Firefox 3.5.5 Not working Ubuntu 9.10 and Firefox 3.5.5 Last 7 days Dec 15, 2009 issue 987 (Not compatible with Linux x86 GCC3) reported by dud...@cadet.ws - What steps will reproduce the problem? 1. Launch firefox with Gears installed. 2. 3. What is the expected output? What do you see instead? "Google Gears" could not be installed because it is not compatible with your Firefox build type (Linux_x86-gcc3). Please contact the author of this item about the problem. What version of the product are you using? On what operating system? Gears 0.5.32.0 Ubuntu 9.10 Kernel 2.6.31-9-rt Please provide any additional information below. Apears to be installed and running. But error message comes up every time FF is launched. G What steps will reproduce the problem? 1. Launch firefox with Gears installed. 2. 3. What is the expected output? What do you see instead? "Google Gears" could not be installed because it is not compatible with your Firefox build type (Linux_x86-gcc3). Please contact the author of this item about the problem. What version of the product are you using? On what operating system? Gears 0.5.32.0 Ubuntu 9.10 Kernel 2.6.31-9-rt Please provide any additional information below. Apears to be installed and running. But error message comes up every time FF is launched. G Dec 14, 2009 NotificationAPI (Providing desktop notifications for web applications.) Wiki page commented on by rastrano - Any news on this topic...??? BrowserPlus (http://browserplus.yahoo.com/developer/web/toolbox/notify/) of Yahoo implemented it (but not the onclick event on the notification popup that's the real important thing in my need (sending clickable links to webapp pages from server to the Desktop is very useful in event driven application development: eg. like monitoring tools, chats, etc.) I hope google team is working in this way... web need it! Any news on this topic...??? BrowserPlus (http://browserplus.yahoo.com/developer/web/toolbox/notify/) of Yahoo implemented it (but not the onclick event on the notification popup that's the real important thing in my need (sending clickable links to webapp pages from server to the Desktop is very useful in event driven application development: eg. like monitoring tools, chats, etc.) I hope google team is working in this way... web need it! Dec 14, 2009 NotificationAPI (Providing desktop notifications for web applications.) Wiki page commented on by rastrano - Any news on this... BrowserPlus of Yahoo implemented it (but not the onclick event on the notification popup that's my need (send link to webapp pages to the Desktop is very useful in event driven application like monitoring tools, chats, etc.) I hope google team is working in this way... web need it! Any news on this... BrowserPlus of Yahoo implemented it (but not the onclick event on the notification popup that's my need (send link to webapp pages to the Desktop is very useful in event driven application like monitoring tools, chats, etc.) I hope google team is working in this way... web need it! Dec 13, 2009 issue 977 (Update fails on Linux/Firefox (incompatible build type)) commented on by romano.nicola - Same thing here, on Fedora 12, kernel 2.6.31.6-166, Firefox 3.5.5-1, Gears 0.5.32.0 . It is NOT a language issue, as I have an English system, and no additional language packs installed. The message seems to pop up kind of randomly, I just got the popup, but there is no new update. Maybe it's firefox not being able to check for updates? Reinstalling google gears does not solve the issue. Same thing here, on Fedora 12, kernel 2.6.31.6-166, Firefox 3.5.5-1, Gears 0.5.32.0 . It is NOT a language issue, as I have an English system, and no additional language packs installed. The message seems to pop up kind of randomly, I just got the popup, but there is no new update. Maybe it's firefox not being able to check for updates? Reinstalling google gears does not solve the issue. Dec 12, 2009 issue 847 ([Mac] [Safari 4] [Snow Leopard] Gears not working Safari 4 -...) commented on by eslerj - It seems much more likely that the team that would fix this is more dedicated thr chrome osx browser, which, once GA, should have gears as part of it natively. It seems much more likely that the team that would fix this is more dedicated thr chrome osx browser, which, once GA, should have gears as part of it natively. Dec 12, 2009 issue 977 (Update fails on Linux/Firefox (incompatible build type)) commented on by baseballnut - Ubuntu 9.10 AND Kubuntu 9.10 both get this error, on both old and new installs of the latest repo version of Firefox. Ubuntu 9.10 AND Kubuntu 9.10 both get this error, on both old and new installs of the latest repo version of Firefox. Dec 12, 2009 issue 977 (Update fails on Linux/Firefox (incompatible build type)) commented on by jmmcl2 - still broken. gears v. 0.5.32.0 firefox v. 3.0.14 ubuntu 9.04 kernel 2.6.28-16-generic #55-Ubuntu SMP still broken. gears v. 0.5.32.0 firefox v. 3.0.14 ubuntu 9.04 kernel 2.6.28-16-generic #55-Ubuntu SMP Last 30 days Dec 11, 2009 issue 335 (Can't install on 64-bit Linux (linux-x86_64-gcc3)) commented on by jacobgodserv - Here's a Gentoo ebuild as promised. It expects the above r3405.patch file to be in the files/ directory. It's quite the hack, but it works. :) Here's a Gentoo ebuild as promised. It expects the above r3405.patch file to be in the files/ directory. It's quite the hack, but it works. :) Dec 11, 2009 issue 335 (Can't install on 64-bit Linux (linux-x86_64-gcc3)) commented on by dvpdiner2 - Any plans to include 64-bit Gears in 64-bit Chrome for Linux? Any plans to include 64-bit Gears in 64-bit Chrome for Linux? Dec 11, 2009 issue 335 (Can't install on 64-bit Linux (linux-x86_64-gcc3)) commented on by jacobgodserv - It works in Google Docs! To clarify ericvw's NS_OUTPARAM instructions, remove any mention from the interface.h file mentioned in the error. This define appears to be useful only if you're using a specific version of gcc (and we usually aren't) so removing it has no effect since the pre-compiler translates it to blank space anyway. I'm working on a Gentoo ebuild, for you Gentoo fans. ;) It works in Google Docs! To clarify ericvw's NS_OUTPARAM instructions, remove any mention from the interface.h file mentioned in the error. This define appears to be useful only if you're using a specific version of gcc (and we usually aren't) so removing it has no effect since the pre-compiler translates it to blank space anyway. I'm working on a Gentoo ebuild, for you Gentoo fans. ;) Dec 11, 2009 issue 335 (Can't install on 64-bit Linux (linux-x86_64-gcc3)) commented on by jacobgodserv - Freshly built and totally untested, but I thought I'd post anyway. Enjoy. maybe. ;) Freshly built and totally untested, but I thought I'd post anyway. Enjoy. maybe. ;) Dec 09, 2009 issue 984 (Xcode Project Needs Updating) commented on by djvasi - If you want to build for 64-bit, you'll need to use the 10.5 SDK. If you want to build for 64-bit, you'll need to use the 10.5 SDK. Dec 09, 2009 issue 977 (Update fails on Linux/Firefox (incompatible build type)) commented on by shannon.jacobs - Still broken here, and it complains two or three times after each boot... I'm only seeing on this one machine, so there must be something odd here. Where do I look to figure out the REAL problem? Still broken here, and it complains two or three times after each boot... I'm only seeing on this one machine, so there must be something odd here. Where do I look to figure out the REAL problem? Dec 09, 2009 issue 977 (Update fails on Linux/Firefox (incompatible build type)) commented on by Ben2talk - IT seems to be working, but I do get many dialogues complaining that I have Shiretoko - the wrong version of Firefox??? IT seems to be working, but I do get many dialogues complaining that I have Shiretoko - the wrong version of Firefox??? Dec 09, 2009 issue 977 (Update fails on Linux/Firefox (incompatible build type)) commented on by dorakeen - Also not working with Linux Ubuntu 9.04 Jaunty + Firefox 3.5.5 Also not working with Linux Ubuntu 9.04 Jaunty + Firefox 3.5.5 Dec 09, 2009 issue 986 (google gears for windows mobile.) reported by ramramesh2020 - Hi i was installed latest google gears in my windows mobile simulator. WM6.5 return error message like google gears not intialized correctly. WM5 hang on in getting location status? Does any one know the solution means. Please reply me. Thanks Ramesh Hi i was installed latest google gears in my windows mobile simulator. WM6.5 return error message like google gears not intialized correctly. WM5 hang on in getting location status? Does any one know the solution means. Please reply me. Thanks Ramesh Dec 09, 2009 issue 981 (Only first sheet of Google Spreadsheets doc displays when of...) commented on by ynedelin - I am having the same problem, any solutions? thanks Yury I am having the same problem, any solutions? thanks Yury Dec 08, 2009 issue 985 (missing +x glag) commented on by kuznetsov.alexey - same as Issue 19, but for third_party/gecko_1.9/linux/gecko_sdk/bin/* same as Issue 19, but for third_party/gecko_1.9/linux/gecko_sdk/bin/* Dec 08, 2009 issue 985 (missing +x glag) reported by kuznetsov.alexey - make[1]: execvp: ../third_party/gecko_1.9/linux/gecko_sdk/bin/xpidl: Permission denied please do svn set:prop +x make[1]: execvp: ../third_party/gecko_1.9/linux/gecko_sdk/bin/xpidl: Permission denied please do svn set:prop +x Dec 07, 2009 issue 970 (Geolocation timeout parameter behaviour does not match lates...) commented on by stevebl...@google.com - Correction ... The latest version of the W3C Geolocation spec (http://dev.w3.org/geo/api/spec- source.html#geolocation_interface) requires that for a watch ... - On success, the success callback is called and any timer is stopped - On failure, the error callback is called with code POSITION_UNAVAILABLE and any timer is NOT stopped - When the timer expires, the error callback is called with code TIMEOUT Correction ... The latest version of the W3C Geolocation spec (http://dev.w3.org/geo/api/spec- source.html#geolocation_interface) requires that for a watch ... - On success, the success callback is called and any timer is stopped - On failure, the error callback is called with code POSITION_UNAVAILABLE and any timer is NOT stopped - When the timer expires, the error callback is called with code TIMEOUT Dec 06, 2009 issue 979 (Google Gears not compatible with your version of FireFox (Li...) commented on by RossMKennedy - I am running FF 3.5.5 for Ubuntu (Karmic Koala) and I'm getting the same popup error at random. I keep Gmail open but it doesn't appear to require a particular action. It sometimes pops up when I start FF but comes while running sometimes as well. Been happening ever since I upgraded to Ubuntu 9.10, not sure if there's any connection though. I am running FF 3.5.5 for Ubuntu (Karmic Koala) and I'm getting the same popup error at random. I keep Gmail open but it doesn't appear to require a particular action. It sometimes pops up when I start FF but comes while running sometimes as well. Been happening ever since I upgraded to Ubuntu 9.10, not sure if there's any connection though. Dec 04, 2009 issue 847 ([Mac] [Safari 4] [Snow Leopard] Gears not working Safari 4 -...) commented on by lem...@gmail.com - Folks, take a hint from Issue 335, and use the issue tracker to share workarounds, or patches. If your comment doesn't substantively help solve this issue, it doesn't belong here. This project has a mailing list, and that's the proper place for your hopes, your fears, your burning questions, and your idle ruminations. It might seem counter-intuitive, but adding unproductive comments actually makes it less likely that this issue will be fixed. This is an open-source project. Yes, the committers are Googlers, but there's nothing stopping you from checking out the code and trying to fix this issue. In fact, someone started to do just that @40, but left @46 because of your "self-important whining." With the Gears Team seemingly focused on Windows-related issues, it's all the more important that issues like this one be attractive for outside developers to solve. In the spirit of taking my own advice, I checked out the source and tried to build it. I agree with the earlier comments @40, @41, @46, and @64. Scripting Additions are the new Input Manager, and it's the way to go for injecting code into 64-bit processes. Before I even started looking at the Input Manager code, however, I tried using Xcode to build the project. It didn't work, so I updated the Xcode project and submitted a patch in Issue 984. Folks, take a hint from Issue 335, and use the issue tracker to share workarounds, or patches. If your comment doesn't substantively help solve this issue, it doesn't belong here. This project has a mailing list, and that's the proper place for your hopes, your fears, your burning questions, and your idle ruminations. It might seem counter-intuitive, but adding unproductive comments actually makes it less likely that this issue will be fixed. This is an open-source project. Yes, the committers are Googlers, but there's nothing stopping you from checking out the code and trying to fix this issue. In fact, someone started to do just that @40, but left @46 because of your "self-important whining." With the Gears Team seemingly focused on Windows-related issues, it's all the more important that issues like this one be attractive for outside developers to solve. In the spirit of taking my own advice, I checked out the source and tried to build it. I agree with the earlier comments @40, @41, @46, and @64. Scripting Additions are the new Input Manager, and it's the way to go for injecting code into 64-bit processes. Before I even started looking at the Input Manager code, however, I tried using Xcode to build the project. It didn't work, so I updated the Xcode project and submitted a patch in Issue 984. Dec 04, 2009 issue 984 (Xcode Project Needs Updating) reported by lem...@gmail.com - It would be nice to be able to use Xcode to work on Issue 847, but gears/tools/osx/gears.xcodeproj/project.pbxproj hasn't been updated since r2827, and won't build without errors. I've attached a patch for fixes the build errors. For future reference, it was helpful to do the following things: Reinstall Xcode, since the Mac OS X 10.4 SDK is not included by default in the Snow Leopard Developer Tools. Switch the project compiler from the system default (GCC 4.2, which won't work with the 10.4 SDK) to GCC 4.0. Update Xcode's view of the project's files to match the changes in the gears/Makefile between r2827 and r3414. Patch /usr/include/curl/curl.h, because gears/base/safari/curl_downloader.mm #includes /usr/include/curl/curl.h, which results in a build error "/usr/include/curl/curl.h:35:66: error: curl/curlbuild.h: No such file or directory." Editing curl.h to remove the extra directory fixes this issue. The cURL project's log for curl.h at <http://curl.haxx.se/cvs.cgi/curl/include/curl/curl.h?r1=1.397&view=log> shows a series of changes to this line between revisions 1.391 and 1.397, so hopefully Apple will eventually pick up the change. Add SystemConfiguration.framework to the Gears.bundle target to supply some undefined _kSC symbols. Recreate the sqlite_google folder groups, so as to be independent of the underlying filesystem. Create a new target for skia, since it has been compiled from scratch since r3205, rather than just linking in a pre-compiled version. Then, add the skia target as a prerequisite for the Gears.bundle target, add libskia.a to the libraries that are linked into Gears.bundle, and remove the old skia linker flags. This eliminates linking errors about not finding the skia-dbg-osx-i386+ppc library. The Gears.plugin target also has a -lskia-dbg-osx- i386+ppc, flag set, but changing it to -lskia should fix it. Finally, set the skia target's visibility options to hidden to eliminate some linker warnings about symbol visibility. Add a user header search path of $(SRCROOT)/../../../third_party/zlib to libpng, so that it will include zlib.h from the project, rather than /usr/local/include. This eliminates linker errors about undefined symbols in pngread. Remove the sqlite target's SQLITE_OMIT_ATTACH flags, since parse.c in r3145 was generated with ATTACH enabled. This fixes linker errors about undefined attach, detach, and vacuum symbols in libsqlite's parse file. It would be nice to be able to use Xcode to work on Issue 847, but gears/tools/osx/gears.xcodeproj/project.pbxproj hasn't been updated since r2827, and won't build without errors. I've attached a patch for fixes the build errors. For future reference, it was helpful to do the following things: Reinstall Xcode, since the Mac OS X 10.4 SDK is not included by default in the Snow Leopard Developer Tools. Switch the project compiler from the system default (GCC 4.2, which won't work with the 10.4 SDK) to GCC 4.0. Update Xcode's view of the project's files to match the changes in the gears/Makefile between r2827 and r3414. Patch /usr/include/curl/curl.h, because gears/base/safari/curl_downloader.mm #includes /usr/include/curl/curl.h, which results in a build error "/usr/include/curl/curl.h:35:66: error: curl/curlbuild.h: No such file or directory." Editing curl.h to remove the extra directory fixes this issue. The cURL project's log for curl.h at <http://curl.haxx.se/cvs.cgi/curl/include/curl/curl.h?r1=1.397&view=log> shows a series of changes to this line between revisions 1.391 and 1.397, so hopefully Apple will eventually pick up the change. Add SystemConfiguration.framework to the Gears.bundle target to supply some undefined _kSC symbols. Recreate the sqlite_google folder groups, so as to be independent of the underlying filesystem. Create a new target for skia, since it has been compiled from scratch since r3205, rather than just linking in a pre-compiled version. Then, add the skia target as a prerequisite for the Gears.bundle target, add libskia.a to the libraries that are linked into Gears.bundle, and remove the old skia linker flags. This eliminates linking errors about not finding the skia-dbg-osx-i386+ppc library. The Gears.plugin target also has a -lskia-dbg-osx- i386+ppc, flag set, but changing it to -lskia should fix it. Finally, set the skia target's visibility options to hidden to eliminate some linker warnings about symbol visibility. Add a user header search path of $(SRCROOT)/../../../third_party/zlib to libpng, so that it will include zlib.h from the project, rather than /usr/local/include. This eliminates linker errors about undefined symbols in pngread. Remove the sqlite target's SQLITE_OMIT_ATTACH flags, since parse.c in r3145 was generated with ATTACH enabled. This fixes linker errors about undefined attach, detach, and vacuum symbols in libsqlite's parse file. Dec 03, 2009 issue 983 (ubuntu compatibility problem (?)) reported by taylorjh1 - What steps will reproduce the problem? I am repeatedly getting an error message from the Firefox 3.0.15 addon shown in attachment #1. It appears to be an update installation error. However, gears is installed and appears to be working properly, specifically in Google Docs. The version of Gears is shown in attachment # 2. I am using Ubuntu 9.04 (with updates). What is the expected output? What do you see instead? No error message. I see the error message although Gears appears to be working. What version of the product are you using? On what operating system? Gears: 0.5.32.0 Error message reports Gears: unidentified Ubuntu OS: 9.04 (with updates) Firefox: 3.0.15 Please provide any additional information below. What steps will reproduce the problem? I am repeatedly getting an error message from the Firefox 3.0.15 addon shown in attachment #1. It appears to be an update installation error. However, gears is installed and appears to be working properly, specifically in Google Docs. The version of Gears is shown in attachment # 2. I am using Ubuntu 9.04 (with updates). What is the expected output? What do you see instead? No error message. I see the error message although Gears appears to be working. What version of the product are you using? On what operating system? Gears: 0.5.32.0 Error message reports Gears: unidentified Ubuntu OS: 9.04 (with updates) Firefox: 3.0.15 Please provide any additional information below. Dec 03, 2009 issue 818 (Gmail offline installation hangs) commented on by ruchanziya - Same issue with Firefox 3.5.5 Mac OS X. Same issue with Firefox 3.5.5 Mac OS X. Dec 03, 2009 issue 975 (FF 3.0.15 said to be incompatible with Gears 0.5.33.0) commented on by Martin.McDowell - I heard that they won't develop Gears 2 as they will rely on HTML 5. I would still expect them to support bugfixes like this for existing versions. http://www.techradar.com/news/internet/google-plumps-for-html-5-over-gears-succesor-655358 I heard that they won't develop Gears 2 as they will rely on HTML 5. I would still expect them to support bugfixes like this for existing versions. http://www.techradar.com/news/internet/google-plumps-for-html-5-over-gears-succesor-655358 Dec 03, 2009 issue 975 (FF 3.0.15 said to be incompatible with Gears 0.5.33.0) commented on by pronoiaque - Google just stop support for googlegears !!! http://www.korben.info/html5-google-gears.html (french) Google just stop support for googlegears !!! http://www.korben.info/html5-google-gears.html (french) Dec 03, 2009 issue 975 (FF 3.0.15 said to be incompatible with Gears 0.5.33.0) commented on by meganox - These fixes work for me (firefox 3.0.15 on Ubuntu Jaunty): Disable firefox updating this extension for now by adding the boolean key: extensions.{000a9d1c-beef-4f90-9363-039d445309b8}.update.enabled = false Set the google updater shim to check again on Jan first 2010 (hopefully it will be fixed by then), by setting the key: extensions.google.updater.{000a9d1c-beef-4f90-9363-039d445309b8} to 1262304000000 The command to find that number is: date -d "Fri Jan 1 00:00:00 GMT 2010" +%s and add three zeros to the end. I tend to forget about little fixes like these, so hopefully I'll get a reminder in the new year that it's still not fixed and have to search for this thread to find out what the hell it was ;) Thanks to everyone who did the hard work! These fixes work for me (firefox 3.0.15 on Ubuntu Jaunty): Disable firefox updating this extension for now by adding the boolean key: extensions.{000a9d1c-beef-4f90-9363-039d445309b8}.update.enabled = false Set the google updater shim to check again on Jan first 2010 (hopefully it will be fixed by then), by setting the key: extensions.google.updater.{000a9d1c-beef-4f90-9363-039d445309b8} to 1262304000000 The command to find that number is: date -d "Fri Jan 1 00:00:00 GMT 2010" +%s and add three zeros to the end. I tend to forget about little fixes like these, so hopefully I'll get a reminder in the new year that it's still not fixed and have to search for this thread to find out what the hell it was ;) Thanks to everyone who did the hard work! Dec 03, 2009 issue 847 ([Mac] [Safari 4] [Snow Leopard] Gears not working Safari 4 -...) commented on by grahamperrin - 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 Dec 02, 2009 issue 979 (Google Gears not compatible with your version of FireFox (Li...) commented on by mmikucionis - yes, it seems that functionality of gears is intact, but the popup is annoying: I get it multiple times at random intervals, it steals focus (e.g. it takes over my keyboard input) and asks for attention (firefox is blinking in the taskbar everytime this happens). yes, it seems that functionality of gears is intact, but the popup is annoying: I get it multiple times at random intervals, it steals focus (e.g. it takes over my keyboard input) and asks for attention (firefox is blinking in the taskbar everytime this happens). Dec 02, 2009 issue 864 ("Gran Paradiso" ~= Firefox 3.0.8. => "Your browser is not cu...) commented on by johnson.eric.d - way beyond this version now - same issue in 3.5.5 way beyond this version now - same issue in 3.5.5 Dec 01, 2009 issue 979 (Google Gears not compatible with your version of FireFox (Li...) commented on by maik.vanrossum - Same here, get error first time the FF launches after boot. BUT when ignoring the message Gears seems to work just fine. It looks like off-line Gmail, Docs and Calendar all work. Same here, get error first time the FF launches after boot. BUT when ignoring the message Gears seems to work just fine. It looks like off-line Gmail, Docs and Calendar all work. Dec 01, 2009 issue 979 (Google Gears not compatible with your version of FireFox (Li...) commented on by maik.vanrossum - Same here, get error first time the FF launches after boot. Same here, get error first time the FF launches after boot. Dec 01, 2009 issue 979 (Google Gears not compatible with your version of FireFox (Li...) commented on by rha7.com - Forgot to say that this was happening with gears ubuntu package, uninstalled and directly installed the gears extension, and the problem persists with it as well. Forgot to say that this was happening with gears ubuntu package, uninstalled and directly installed the gears extension, and the problem persists with it as well. Dec 01, 2009 issue 979 (Google Gears not compatible with your version of FireFox (Li...) commented on by rha7.com - Confirmed error, only that it happens when I open firefox for the first time after boot up, Firefox 3.5.5, Gears 0.5.32.0, GNU/Linux Ubuntu 9.10 Karmic Koala. Confirmed error, only that it happens when I open firefox for the first time after boot up, Firefox 3.5.5, Gears 0.5.32.0, GNU/Linux Ubuntu 9.10 Karmic Koala. Dec 01, 2009 issue 749 (Gears 0.4.20.0 not compatable with Firefox 3.1 Beta 1) commented on by Drakkim - Last comment is completely unrelated to the (solved) topic here... maybe you replied to the wrong page? (I've done it before....) Last comment is completely unrelated to the (solved) topic here... maybe you replied to the wrong page? (I've done it before....) Dec 01, 2009 issue 847 ([Mac] [Safari 4] [Snow Leopard] Gears not working Safari 4 -...) commented on by Immutate - @60: I'm certainly glad to hear that google is moving towards the new HTML 5 standard, and hope that the project moves quickly. Snow Leopard has been GA for more than 3 months now, and we've only just been informed what direction google is moving toward in regards to gears in Snow Leopard/Safari. Combine that with the developer preview of Snow Leopard which has been available since June, I would have assumed development would be further along, or we'd at least have been told of this sooner. Here's hoping we can get some traction on google apps offline functionality, regardless of the technology used to re- implement the feature. @61: That would be the manual process I wasn't sure about ;) I really wish google would mark this defect's status as WontFix and update the gears homepage to accurately represent their stance. It seems as though this defect and all of the other gears/Snow Leopard issues that have been filed are simply being ignored. @60: I'm certainly glad to hear that google is moving towards the new HTML 5 standard, and hope that the project moves quickly. Snow Leopard has been GA for more than 3 months now, and we've only just been informed what direction google is moving toward in regards to gears in Snow Leopard/Safari. Combine that with the developer preview of Snow Leopard which has been available since June, I would have assumed development would be further along, or we'd at least have been told of this sooner. Here's hoping we can get some traction on google apps offline functionality, regardless of the technology used to re- implement the feature. @61: That would be the manual process I wasn't sure about ;) I really wish google would mark this defect's status as WontFix and update the gears homepage to accurately represent their stance. It seems as though this defect and all of the other gears/Snow Leopard issues that have been filed are simply being ignored. Dec 01, 2009 issue 979 (Google Gears not compatible with your version of FireFox (Li...) commented on by fmaz008 - I just had this error when FireFox openned (no tab, no other instances) on the google.ca home page. I just had this error when FireFox openned (no tab, no other instances) on the google.ca home page. Dec 01, 2009 issue 979 (Google Gears not compatible with your version of FireFox (Li...) commented on by mmikucionis - I have the same issue on Debian Iceweasel 3.5.5-1, Gears 0.5.32.0 I have the same issue on Debian Iceweasel 3.5.5-1, Gears 0.5.32.0 Dec 01, 2009 issue 847 ([Mac] [Safari 4] [Snow Leopard] Gears not working Safari 4 -...) commented on by johannes.stuehler - Longterm wise it surely makes sense to go this way for Google as well as for the user, but still, the way Google handles this issue is not the finest way. I hope there is something in the pipeline since the iPhone version of GMail is already making full use of HTML5 and offline storage. As a bad interim solution one can set the Safari User Agent to Mobile Safari to test and maybe use this feature once in a while... It is really weird that the full client lacks behind the iPhone version somehow. Longterm wise it surely makes sense to go this way for Google as well as for the user, but still, the way Google handles this issue is not the finest way. I hope there is something in the pipeline since the iPhone version of GMail is already making full use of HTML5 and offline storage. As a bad interim solution one can set the Safari User Agent to Mobile Safari to test and maybe use this feature once in a while... It is really weird that the full client lacks behind the iPhone version somehow. Dec 01, 2009 issue 749 (Gears 0.4.20.0 not compatable with Firefox 3.1 Beta 1) commented on by mattions - Sometimes gears brings my computer on his knees. More over is always complaining about the compability, but it works at the end of the day so I don't know. FF: 3.0.15 gears: 0.5.32.0 tryed to uninstal and reinstall. No luck. Sometimes gears brings my computer on his knees. More over is always complaining about the compability, but it works at the end of the day so I don't know. FF: 3.0.15 gears: 0.5.32.0 tryed to uninstal and reinstall. No luck. Dec 01, 2009 issue 847 ([Mac] [Safari 4] [Snow Leopard] Gears not working Safari 4 -...) commented on by augustlilleaas - @59: I am not misinformed, but I can see why you thought I was. I were speaking in terms of conventions, though - most project owners uses the number of stars on an issue to determine what should be deemed important. As @58 points out, it seems that the reason for the severity isn't that Google doesn't care about Mac, it's because Google doesn't care about gears, to put it bluntly. Here's another link referencing the same source on google going towards HTML5 instead of Gears. http://latimesblogs.latimes.com/technology/2009/11/google-gears.html @59: I am not misinformed, but I can see why you thought I was. I were speaking in terms of conventions, though - most project owners uses the number of stars on an issue to determine what should be deemed important. As @58 points out, it seems that the reason for the severity isn't that Google doesn't care about Mac, it's because Google doesn't care about gears, to put it bluntly. Here's another link referencing the same source on google going towards HTML5 instead of Gears. http://latimesblogs.latimes.com/technology/2009/11/google-gears.html Dec 01, 2009 issue 847 ([Mac] [Safari 4] [Snow Leopard] Gears not working Safari 4 -...) commented on by mkonomos - @59, I think that 58 seems to have answered the big question for us, if his answer is indeed correct. Basically, Google isn't ditching us. But they aren't going to waste time on Gears for Mac because they are basically 'leapfrogging' to HTML 5 instead. As much as it stinks for us as Mac users, it doesn't make much sense for them to continue developing a technology that was only a temporary fix anyway and apparently is becoming obsolete. So, as is often unfortunately the case for Mac users, we must have some patience. Making our voice heard isn't going to get us Gears anytime soon because they aren't going to do it. But if this gets some attention, perhaps they will do what they can to speed along the HTML 5 solution. @59, I think that 58 seems to have answered the big question for us, if his answer is indeed correct. Basically, Google isn't ditching us. But they aren't going to waste time on Gears for Mac because they are basically 'leapfrogging' to HTML 5 instead. As much as it stinks for us as Mac users, it doesn't make much sense for them to continue developing a technology that was only a temporary fix anyway and apparently is becoming obsolete. So, as is often unfortunately the case for Mac users, we must have some patience. Making our voice heard isn't going to get us Gears anytime soon because they aren't going to do it. But if this gets some attention, perhaps they will do what they can to speed along the HTML 5 solution. Dec 01, 2009 issue 847 ([Mac] [Safari 4] [Snow Leopard] Gears not working Safari 4 -...) commented on by Immutate - @57 I believe you are misinformed as to how Project Hosting works on Google Code, please see this support page for more information on the issue life-cycle and priority labeling. http://code.google.com/p/support/wiki/IssueTracker#Concepts The priority of an issue is an editable label, and is not automatically assigned based on how many people have starred the issue--unless that is the manual process which the google gears folks have said they follow. IMHO the only reason this is a Priority-Medium issue, is the fact that people haven't publicized the issue much. The reality appears to be that google could care less about their mac users, based on how much attention they appear to have given this issue. I've loved using google products for years, but to simply drop support for something in this fashion certainly makes me want to research other products in case google decides to drop support for other features/applications in project hosting or google apps. @57 I believe you are misinformed as to how Project Hosting works on Google Code, please see this support page for more information on the issue life-cycle and priority labeling. http://code.google.com/p/support/wiki/IssueTracker#Concepts The priority of an issue is an editable label, and is not automatically assigned based on how many people have starred the issue--unless that is the manual process which the google gears folks have said they follow. IMHO the only reason this is a Priority-Medium issue, is the fact that people haven't publicized the issue much. The reality appears to be that google could care less about their mac users, based on how much attention they appear to have given this issue. I've loved using google products for years, but to simply drop support for something in this fashion certainly makes me want to research other products in case google decides to drop support for other features/applications in project hosting or google apps. Nov 30, 2009 issue 977 (Update fails on Linux/Firefox (incompatible build type)) commented on by akakingess - Not working on 9.10 Karmic 64-bit with Firefox 3.5.5. Not working on 9.10 Karmic 64-bit with Firefox 3.5.5. Nov 30, 2009 issue 982 (Gears does not support Chrome on Mac) reported by jamen.berk - What steps will reproduce the problem? 1. Go to http://gears.google.com/ in Google Chrome in OS X What is the expected output? What do you see instead? Expected support for Google's browser. What version of the product are you using? On what operating system? Google Gears: 0.5.33.0 (operational in Firefox and Safari on same computer) Google Chrome: 4.0.249.12 OS X: 10.5.8 Please provide any additional information below. In addition to the explicit statement on the gears.google.com page, the about:plugins page and any Gears enabled site also confirm that Gears is not working in Chrome, despite Gears being installed for Firefox and Safari, and Gears.plugin being located in /Library/Internet Plug-Ins. I realize that at least some developers are aware of this issue, but I could not find another bug report and I wanted to both spread awareness and provide a location where those interested can stay up to date on any developments. What steps will reproduce the problem? 1. Go to http://gears.google.com/ in Google Chrome in OS X What is the expected output? What do you see instead? Expected support for Google's browser. What version of the product are you using? On what operating system? Google Gears: 0.5.33.0 (operational in Firefox and Safari on same computer) Google Chrome: 4.0.249.12 OS X: 10.5.8 Please provide any additional information below. In addition to the explicit statement on the gears.google.com page, the about:plugins page and any Gears enabled site also confirm that Gears is not working in Chrome, despite Gears being installed for Firefox and Safari, and Gears.plugin being located in /Library/Internet Plug-Ins. I realize that at least some developers are aware of this issue, but I could not find another bug report and I wanted to both spread awareness and provide a location where those interested can stay up to date on any developments.

issue 984 (Xcode Project Needs Updating) reported by lem...@gmail.com - It would be nice to be able to use Xcode to work on Issue 847, but gears/tools/osx/gears.xcodeproj/project.pbxproj hasn't been updated since r2827, and won't build without errors. I've attached a patch for fixes the build errors. For future reference, it was helpful to do the following things: Reinstall Xcode, since the Mac OS X 10.4 SDK is not included by default in the Snow Leopard Developer Tools. Switch the project compiler from the system default (GCC 4.2, which won't work with the 10.4 SDK) to GCC 4.0. Update Xcode's view of the project's files to match the changes in the gears/Makefile between r2827 and r3414. Patch /usr/include/curl/curl.h, because gears/base/safari/curl_downloader.mm #includes /usr/include/curl/curl.h, which results in a build error "/usr/include/curl/curl.h:35:66: error: curl/curlbuild.h: No such file or directory." Editing curl.h to remove the extra directory fixes this issue. The cURL project's log for curl.h at <http://curl.haxx.se/cvs.cgi/curl/include/curl/curl.h?r1=1.397&view=log> shows a series of changes to this line between revisions 1.391 and 1.397, so hopefully Apple will eventually pick up the change. Add SystemConfiguration.framework to the Gears.bundle target to supply some undefined _kSC symbols. Recreate the sqlite_google folder groups, so as to be independent of the underlying filesystem. Create a new target for skia, since it has been compiled from scratch since r3205, rather than just linking in a pre-compiled version. Then, add the skia target as a prerequisite for the Gears.bundle target, add libskia.a to the libraries that are linked into Gears.bundle, and remove the old skia linker flags. This eliminates linking errors about not finding the skia-dbg-osx-i386+ppc library. The Gears.plugin target also has a -lskia-dbg-osx- i386+ppc, flag set, but changing it to -lskia should fix it. Finally, set the skia target's visibility options to hidden to eliminate some linker warnings about symbol visibility. Add a user header search path of $(SRCROOT)/../../../third_party/zlib to libpng, so that it will include zlib.h from the project, rather than /usr/local/include. This eliminates linker errors about undefined symbols in pngread. Remove the sqlite target's SQLITE_OMIT_ATTACH flags, since parse.c in r3145 was generated with ATTACH enabled. This fixes linker errors about undefined attach, detach, and vacuum symbols in libsqlite's parse file.

It would be nice to be able to use Xcode to work on Issue 847, but gears/tools/osx/gears.xcodeproj/project.pbxproj hasn't been updated since r2827, and won't build without errors. I've attached a patch for fixes the build errors. For future reference, it was helpful to do the following things: Reinstall Xcode, since the Mac OS X 10.4 SDK is not included by default in the Snow Leopard Developer Tools. Switch the project compiler from the system default (GCC 4.2, which won't work with the 10.4 SDK) to GCC 4.0. Update Xcode's view of the project's files to match the changes in the gears/Makefile between r2827 and r3414. Patch /usr/include/curl/curl.h, because gears/base/safari/curl_downloader.mm #includes /usr/include/curl/curl.h, which results in a build error "/usr/include/curl/curl.h:35:66: error: curl/curlbuild.h: No such file or directory." Editing curl.h to remove the extra directory fixes this issue. The cURL project's log for curl.h at <http://curl.haxx.se/cvs.cgi/curl/include/curl/curl.h?r1=1.397&view=log> shows a series of changes to this line between revisions 1.391 and 1.397, so hopefully Apple will eventually pick up the change. Add SystemConfiguration.framework to the Gears.bundle target to supply some undefined _kSC symbols. Recreate the sqlite_google folder groups, so as to be independent of the underlying filesystem. Create a new target for skia, since it has been compiled from scratch since r3205, rather than just linking in a pre-compiled version. Then, add the skia target as a prerequisite for the Gears.bundle target, add libskia.a to the libraries that are linked into Gears.bundle, and remove the old skia linker flags. This eliminates linking errors about not finding the skia-dbg-osx-i386+ppc library. The Gears.plugin target also has a -lskia-dbg-osx- i386+ppc, flag set, but changing it to -lskia should fix it. Finally, set the skia target's visibility options to hidden to eliminate some linker warnings about symbol visibility. Add a user header search path of $(SRCROOT)/../../../third_party/zlib to libpng, so that it will include zlib.h from the project, rather than /usr/local/include. This eliminates linker errors about undefined symbols in pngread. Remove the sqlite target's SQLITE_OMIT_ATTACH flags, since parse.c in r3145 was generated with ATTACH enabled. This fixes linker errors about undefined attach, detach, and vacuum symbols in libsqlite's parse file.

Today

Yesterday

Last 7 days

Last 30 days