Search results

Hmm, are you sure you never ran the GUI remotely? Maybe there's some other part of the frontend that automatically generates that XML file then, because it wasn't there for me. I couldn't even do a "VBoxManage list systemproperties" as a result. This is with VirtualBox 4.0.12 from ports...

I just came across this error today when trying to setup VirtualBox without the Qt frontend. When I run VBoxManage for the first time to create a new VM, I get the same NS_ERROR_ABORT message along with the unhelpful info, "Most likely, the VirtualBox COM server is not running or failed to...

Maybe you don't have the Chinese fonts installed that it's looking for, as Chromium will simply use the system fonts. Others have had similar problems with other Asian languages in Chromium, till they installed the right fonts. You may want to google for how others installed Chinese fonts for...

There's a patch that was recently added to take out the gconf dependency, I'll look into backporting it to Chromium 6.

Hey, the problem is that Chromium depends on the SOCK_SEQPACKET socket type, which was only introduced recently into FreeBSD 9, to kill one of the three default processes that are opened every time you start up the browser. Basically, Chromium on FreeBSD will leave a single orphaned process...

On FreeBSD, this problem is probably related to that last line of debug output that you pasted: ERROR:chrome/app/chrome_dll_main.cc(234)] Gdk: shmget failed: error 12 (Cannot allocate memory) The free build of Chromium relies on SysV shared memory to pass rendered webpages between processes...

It was removed, as noted on the PR, along with MPEG-LA patented codecs and I'm hosting the tarball myself. Courgette isn't even compiled on linux or FreeBSD, so it was easy to just remove the source. Apparently they want to make sure of that though.

Not likely, I was just informed that the Chromium port is still under legal review by the FreeBSD Foundation and a decision will probably not be made till next month. Blame software patents and the trolls that brandish them as weapons, though sometimes they can be turned on other miscreants. ;)...

Hey, I'm the author of the chromium port. adamk, I didn't know about the glew issue, I'll add that to the conflicts. For those with redraw issues, that's addressed in the README on my site. You can set sysctl kern.ipc.shm_allow_removed=1 to avoid any rendering flakiness, caused by...

I just had this same problem where I had setup some local and remote FreeBSD jails but after changing the IPs, X forwarding stopped working with a similar xauth error. I had to make sure the correct domain and IP was properly placed in /etc/hosts inside the jails and X forwarding started...

Aah, you're right, I forgot to include one useful command that I used to figure out the fragment size dumpfs /dev/ad4s1a | more The info you're looking for is near the top, fragment size is called fsize.

I've started offering subscriptions to fund Chromium development. I'm using a new funding model, where my patches are closed for at most 1 year after the release date of a build, after which they're made available to subscribers under the same BSD license as Chromium. Also, I'm always making...

Of course you can install an i386 jail in an amd64 system, I did it last year using these i386 instructions and this general info on setting up a FreeBSD jail, and have been using it ever since. :) I don't know about FreeBSD 9 specifically, but it mostly works on 7.2. There are a few...

mechanic, I wouldn't go so far as to even call it a vanity project, just something I hacked together for myself. ;) However, because I've gotten so much good stuff for free from FreeBSD devs, I gave back what I'd done too, as Aragon says. As you say though, to be a real desktop app, it's going...

I've been posting test builds, patches, and updates at http://chromium.jaggeri.com for 5 months now, usually on a weekly basis. As for a port, the Chromium devs have been testing a build source tarball for months, which should be out eventually. Once they make that 140 MB tarball available...

I just ran into this problem cuz of some bad sectors so I thought I'd write up what I did to recover. What follows is based on this howto for linux and the equivalent for FreeBSD, expanded with my specific commands and output. I woke up this morning to find my system had crashed and rebooted...

It's probably related to system memory then. I'm underspeced for zfs with only 1 GB of RAM in the system, I bet you have more.

That makes sense that it wouldn't work for a different commit, as the codebase can change a fair amount after 150+ commits. :) That's why I always list the commits I used, so that others can make sure they're working off the same repository version. I don't see why you'd have to maintain...

I've been posting updated test builds every week or two and will continue to do so. Some chromium committers have expressed interest in merging this patch into their codebase so let's see when that happens. This port is not yet ready for primetime, as a tab will sometimes flake out and freeze...

Of course it can be done, I quickly found two tutorials within seconds of googling it. You might need some extra configuration for your jails, but maybe not. :)