-current and google-chrome
 

Noticed some issues with google chrome under -current. Having some flash/pepflash lag delays and various problems. Anyone else run into flash related problems in google-chrome under -current?

I've tried varying window manager environments and also with/without flash-player-plugin installed... still get laggy/crashy flash performance.

any ideas?

(64 Bit -current, google chrome 26.0.XX (from 14.0 slackbuild).)

Slack64-Current multilib
google-chrome-25.0.1364.97-x86_64-1.txz <--- used slackbuild from /extra
flash-player-plugin-11.2.202.261-x86_64-2_SBo.tgz
All is well here, no blue people.

edit:
Just built the newest version using the build in /extra and it's also working good.
google-chrome-26.0.1410.63-x86_64-1.txz

I have the same problem in firefox and chrome with kernel 3.8.8 and 3.8.11 as well.
Deleted .kde folder and nothing. can't play youtube videos or similar content

I had to boot again to kernel 3.2.29 and works with no issues.

I'm running Slack64-current

F.Y.I. Chrome does not use the NPAPI Flash plugin provided by flash-player-plugin-11.2.202.261-x86_64-2_SBo but rather the PPAPI (Pepper) Flash plugin it comes bundled with. If you use Chrome as your only browser, you need not even install flash-player-plugin-11.2.202.261-x86_64-2_SBo at all.

Thanks!
I didn't know that. :doh: :study:

@slackass: I don't think that most people realise to be honest. ;)

P.S. If you want an easy way to keep Chrome up to date, you can use my script, latest-chrome. Just make it executable and run it from time to time. If you already have the latest version it will simply print back a message to the terminal telling you this. However, if there is a newer version it will automatically download it and repack it locally into Slackware format (you don't have to run it as root for it to do the repackage as it includes its own makepkg function that will make a package with root owned files even when run as a regular user).

Go to chrome://plugins and disable chrome's built-in ppapi flash to use the SBo or alien flashplayer-plugin only.

Thanks ruario!!

I have been having the same issues. They recently started happening, but not on all websites. Youtube is un-watchable. You can temporarily switch to adobe flash version. Every now and then, pepper flash would do stuff like that. Google is usually pretty fast about fixing those things. I'm sure they will have an update here within the next few days.

:scratch: Looked for that option, but couldn't find it.

On the top right, click on (+)Details.

Thanks. Found it. Now off to the optometrist. :)

Still without the pepperflash plugin you can't view videos at the cbs.com site. As with other browsers and the regular flashplayer plugin, you can view the commercials, but not the show. Once the pepperflash plugin is "re-enabled" you can watch the program. This sort of nonsense by the big corporations really *^%$#* me off! :mad:

OTOH, the KDE developers are pulling the same scam by forcing us to install digiKam if we want to use the kipi-plugins with KDE apps other than digiKam.

Actually disabling peperflash through chrome://plugins did the trick for me. I was looking through the options for that; had completely forgotten that the plugins url feature was even there.

Seems kind of silly though that chrome would ship a built in peperflash that didn't perform properly? In either case I'm use the flash-player-plugin and all seems to work well for me thus far.

Thanks!

I have found out that I get better hardware acceleration performance from pepper flash. However, every now and then, things like this happen. I am pretty sure that it will be fixed soon. They usually do anyway.

When using the pepperflash player I've found the audio to be very choppy, as opposed to watching the same file with the standard flashplayer plug-in.