| Summary: | Google-talkplugin fails in webkit gtk browsers under GNU/Linux | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Sam Stuewe <samuel.stuewe> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | bugs-noreply, cgarcia, grant_gayed, marko.rakamaric, swagiaal, zan |
| Priority: | P2 | ||
| Version: | 420+ | ||
| Hardware: | PC | ||
| OS: | Linux | ||
|
Description
Sam Stuewe
2012-10-28 18:38:25 PDT
I am unsure of the webkit gtk version to report. The version of libwebkit I have installed is 1.8.3-1 (from the Arch official repos). As an update, this problem is still present with local/webkitgtk2 1.10.2-2 why is this still uncomfirmed? while you can find so much users who's complaining about this issue. I am also affected. My webkit version is : webkitgtk2 1.10.2-2 same issue persist on webkit-gtk3 version will it ever be resolved or assigned to anyone? This bug definitely still exists, but the reporting system is a bit unhelpful here. I know the versions of libwebkit and webkit-gtk, but the available versions which I can report on do not follow the same versioning system. So, I don't actually know if the version I have selected is correct. But yeah, this is definitely still a thing. Can confirm with trunk. Receiving this output: No bp log location saved, using default. [000:000] Browser XEmbed support present: 1 [000:000] Browser toolkit is Gtk2. [000:000] Using Gtk2 toolkit [000:004] Starting client channel. [000:004] Warning(clientchannel.cc:436): Unreadable or no port file. Could not initiate GoogleTalkPlugin connection [000:005] Warning(clientchannel.cc:411): Could not initiate GoogleTalkPlugin connection [000:005] GoogleTalkPlugin not running. Starting new process... [000:005] Warning(optionsfile.cc:47): Load: Could not open file, err=2 [000:005] Warning(pluginutils.cc:251): Failed to get GoogleTalkPlugin path. Trying default. [000:006] Started GoogleTalkPlugin, path=/opt/google/talkplugin/GoogleTalkPlugin [000:007] Waiting for GoogleTalkPlugin to start... [001:103] Attempting to connect to GoogleTalkPlugin... [001:103] Warning(clientchannel.cc:436): Unreadable or no port file. Could not initiate GoogleTalkPlugin connection [001:103] Warning(clientchannel.cc:411): Could not initiate GoogleTalkPlugin connection [001:103] Waiting for GoogleTalkPlugin to start... [002:104] Attempting to connect to GoogleTalkPlugin... [002:105] Warning(clientchannel.cc:436): Unreadable or no port file. Could not initiate GoogleTalkPlugin connection [002:105] Warning(clientchannel.cc:411): Could not initiate GoogleTalkPlugin connection [002:105] Waiting for GoogleTalkPlugin to start... [003:106] Attempting to connect to GoogleTalkPlugin... [003:106] Warning(clientchannel.cc:436): Unreadable or no port file. Could not initiate GoogleTalkPlugin connection [003:106] Warning(clientchannel.cc:411): Could not initiate GoogleTalkPlugin connection [003:106] Waiting for GoogleTalkPlugin to start... [004:109] Attempting to connect to GoogleTalkPlugin... [004:109] Warning(clientchannel.cc:436): Unreadable or no port file. Could not initiate GoogleTalkPlugin connection ... (the iterations continuing) Interestingly, the hangouts actually function properly under WebKitGTK+ when the following is done: 1. Open the Chrome browser, go to https://plus.google.com/hangouts, 2. Start a hangout, wait for the initalization to complete & video to show, 3. Close the hangout window, but stay on https://plus.google.com/hangouts, 4. Start the GtkLauncher (testing on ToT, can't yet confirm for Epiphany), go to https://plus.google.com/hangouts, 5. Start a hangout, the video should now show. Now works with trunk and in WebKit2GTK+ 2.0, with Google Talk Plugin 3.19.1.0-1. Checked in the MiniBrowser app and Epiphany 3.8. The issue in the first place was the Talk plugin running with an incorrect libudev shared library, but this seems to have been fixed. Can confirm this is still an issue in WebKit1Gtk+ (as checked in the GtkLauncher app), both in 1.10 and 2.0. Hi Zan, > The issue in the first place was the Talk plugin running with an incorrect libudev shared library, but this seems to have been fixed. How did you diagnose that ? And did you find any workarounds ? I am working on a possibly related issue where eclipse (which uses webkit1) crashes when google-talkplugin is installed (https://bugs.eclipse.org/bugs/show_bug.cgi?id=334466) Plugins are no longer supported. |