Description of problem: I see this when starting gwibber: Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/gwibber/gwui.py", line 81, in on_click_link if not self.link_handler(uri, self) and self.load_externally: TypeError: link_handler() takes exactly 2 arguments (3 given) Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/gwibber/gwui.py", line 81, in on_click_link if not self.link_handler(uri, self) and self.load_externally: TypeError: link_handler() takes exactly 2 arguments (3 given) Version-Release number of selected component (if applicable): gwibber-0.7.3-4.223bzr.fc10 WebKit-gtk-1.1.0-0.16.svn40351.fc10.x86_64 Additional info: I think the reason that code is getting executed in the first place is because of a WebKit change; however I think the attached patch is needed.
Created attachment 332517 [details] gwibber-traceback.patch
Am I correct in thinking that you said this was caused by the webkit update on bodhi with bad karma? If so please close NOTABUG or reassign to WebKit :)
Well, that's when I first saw the traceback. However, looking at the code, 'link_handler' does indeed take two arguments so 'self.link_handler(uri, self)' (passing three) seems wrong.
Hey Tim, is this bug still a problem? I haven't seen it in my use.
Not seeing it with: gwibber-1.0.1-1.286bzr.fc10.noarch WebKit-gtk-1.0.0-0.15.svn37790.fc10.x86_64 but the original report was with a newer WebKit-gtk package. Will re-test with the updates-testing WebKit-gtk package this week and update this report.
Works fine with: gwibber-1.2.0-1.345bzr.fc10.noarch WebKit-gtk-1.1.0-0.16.svn40351.fc10.x86_64 although I had to re-enter my password in order to avoid '401 unauthorized' errors. Not sure why -- I just copied it from what was already in my keyring.
There was some revision in between that that had wacky things going with the GNOME keyring. Sorry for the inconvenience on that. I'm gonna go ahead and say this was fixed in version 1.2.0-1.345bzr.fc10