I am using Google Chromium on Debian (the one in debian depository). I am hitting some bug, that crashes Chrome, but that I can replicate only in Chromium, not in Chrome. (It might be present in Chrome too, I just cannot replicate it.)
I can't figure out how to enable crash reporting in Chromium.
This guide doesn't work - I don't have that option in Advanced.
This guide describes:
Linux
Breakpad is compiled in, but is not enabled by default. See IsCrashReportingEnabled() in chrome_browser_main_linux.cc for details on when it is enabled.
Set the gyp variable (GYP_DEFINES) linux_dump_symbols=1 to dump the debugging symbols for the chrome binary in the Breakpad symbol format as part of a build.
chrome_browser_main_linux.cc does not have this function.
breakpad_linux.cc has a function IsCrashReporterEnabled, which is similar enough; however, I'm not too clever by staring at the code.
I am not sure what is gyp and if I have to use it. (I don't want to rebuild whole Chromium just to enable crash reporting.)
Enabling crash reporting on Chromium is not possible, since there are no official Chromium builds. Chromium is built by the distro maintainers (Debian, Red Hat) and it might or might not have the debug info.
The only builds Google does is Chrome from the Chrome website.
Related
I am trying to develop a simple windows GUI in go (first attempt).
After considering a few packages to get me started, I landed on this https://github.com/lxn/walk and it seemed ideal. I cross-compiled from my ubuntu laptop and the provided demo worked on all target platforms (win7/8/10)
The problems came when I tried to start developing from my linux laptop - initially in atom, but I've since tried with sublime, emacs and phpstorm and noticed an issue with go get (so I'm guessing it's the underlying go tooling that's failing)
The first error I'm seeing is:
/../github.com/lxn/walk/tooltiperrorpresenter.go:8: undefined: ToolTip
This affects development across all affected IDEs tested:
disables autocomplete
halts linting
cant test
gofmt worked in some (perhaps tool ordering)
affecting any file referencing this lib.
And this is the first of many errors which seem to be due to the library importing its internal win package which contains files which are marked with the flag:
// +build windows
I cunningly decided to start ripping out these tags from the lib - hoping that would at least allow me to get on with development, but then I started seeing new errors regarding too many arguments being passed to syscalls in the win package - presumably because the different platforms (win/nix) have different numbers of parameters in those syscalls.
I then tried marking everything with the //+build windows flag, but the parade of errors remained unchanged.
I found some issues on the project github which are related:
https://github.com/lxn/win/issues/26 : no buildable Go source files
and there are solutions for "go getting" the files but none so far for my IDE woes.
I've also seen this type of issue in some other windows specific go libraries so I don't think it's an issue for the package author. But I would be interested to hear any solutions from a code architecture perspective if they exist
I haven't actually tried doing this from a windows VM yet (I presume that would solve the issue from my end) - but its a bit of a jarring solution as I'm already juggling vms to test the app so I'm keen to find another way.
TLDR:
Do I have to work from Windows machine / vm in order to have a fully
functional IDE when developing for windows from linux or is there a way to satisfy the go tooling
I was trying to follow the the installation tutorial of the Native Client SDK found here. However, my Samsung Chromebook (in developer mode) does not want to run ./naclsdk (chmod +x done), but instead returns the following:
32-bit runtime environment was not found on this
system. Specifically the 32-bit dynamic loader which is needed by the NaCl
compilers was not found ('/lib/ld-linux.so.2'). On modern debian/ubuntu
systems this is included in the 'libc6:i386' package.
On here they write that the PNaCl should run on ARM computers, however, on some other forums I read that wasn't the case. I've tried enabling two flags, as described on a site which I can't post due to a lack of reputation, but it looks like that'll only change things when using PNaCl, not during the installation of the SDK.
Is it possible to install that SDK on my Chromebook and, if so, how?
There's a bit of confusion: when the documentation says "PNaCl and NaCl work on ARM", it means the part that runs inside of Chrome which users would use. The SDK is currently only built for x86-64 Windows/Linux/OSX, and not for ARM. The main reason is that it's never been requested, probably because ARM machines are quite slow compared to usual development machines.
That being said, I don't think it's silly to use ARM as a development machine, and I've built my own PNaCl toolchain for ARM in the past. There are build instructions for the toolchain. I haven't built it recently, and it may have bitrotted a bit so if you run into issues I suggest emailing the team or better yet sending a patch! I expect any issue to be fairly minor, especially if you only want to use pnacl-clang or nacl-clang (as opposed to the GCC toolchain).
I've got a problem while trying to install rutoken plugin for Google Chrome v. 40.0.2214.115 (64-bit) on Ubuntu 14.04.
That's what I try:
Download plugin from http://www.rutoken.ru/support/download/rutoken-plugin/ and unpack files, so I had librtpkcs11ecp.so, npCryptoPlugin.so files.
Create a directory for plugins, in the Google Chrome's installation directory.
sudo mkdir /opt/google/chrome/plugins
Copy *.so files to the plugins directory.
Then I've restarted Chrome:
google-chrome -–enable-plugins
The problem is that when I run chrome://plugins/ there is no such plugin in a list.
It seems Java JRE is not more working on Chrome
https://askubuntu.com/a/590181
NPAPI support by Chrome
The Java plug-in for web browsers relies on the cross platform plugin architecture NPAPI, which has long been, and currently is, supported by all major web browsers. Google announced in September 2013 plans to remove NPAPI support from Chrome by "the end of 2014", thus effectively dropping support for Silverlight, Java, Facebook Video and other similar NPAPI based plugins. Recently, Google has revised their plans and now state that they plan to completely remove NPAPI by late 2015. As it is unclear if these dates will be further extended or not, we strongly recommend Java users consider alternatives to Chrome as soon as possible. Instead, we recommend Firefox, Internet Explorer and Safari as longer-term options.
I installed plugin updated but I face issue at testing time plugin not work properly in Chrome using link http://java.com/en/download/installed8.jsp?detect=jre If you got message "This plug-in is not supported" then follow following steps:
In your URL bar, enter:
chrome://flags/#enable-npapi
Click the Enable link for the Enable NPAPI configuration option.
Click the Relaunch button that now appears at the bottom of the
configuration page.
and test it again using http://java.com/en/download/installed8.jsp?detect=jre link.
I'm looking for the way to conduct cross-browser compatibility test on my ubuntu. Firefox and opera don't cause problems, but I didn't find any guide how to install older versions of chrome. Do you know how to check my code in this browser on my computer?
You can take screenshots in different versions in Browserstack. Also you can browse there using different browsers, but you will need to pay for that.
In general, there is no need to test compatibility against anything but the latest version of Chrome, since Chrome updates itself automatically. Just expect that anyone using Chrome to view your site will have the latest version.
Hey i was wondering if anyone else has had problems with css 3d running on chrome on linux (specifically fedora 17). Chrome in Windows seems to handle everything fine but for some reason it won't work in Fedora. I get errors saying that my browser doesn't support 3d transforms.
Chrome/ium is probably the most popular option, so if the version you tried wasn't working, you may want to update to the very latest -- something like the Chromium Daily Builds. If even that is too buggy to work with, you might want to try a different Webkit browser for Linux.
Midori and Epiphany are two decent options. As an added bonus, I think both of these browsers will use the version of Webkit that you have installed on your system (unlike Chrome, which comes with its own version of Webkit). That means that you should be able to build Webkit from the latest nightly source release, and Midori or Epiphany will automatically use that version.
WebKit Nightly Builds
I hope that this help you.