Notice: Undefined variable: name in /srv/http/vhosts/ on line 248

Package Details: chromium-wayland 48.0.2548.0-2

Git Clone URL: (read-only)
Package Base: chromium-wayland
Description: The open-source project behind Google Chrome, an attempt at creating a safer, faster, and more stable browser
Upstream URL:
Keywords: chromium wayland
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: pypi
Maintainer: None
Last Packager: pypi
Votes: 8
Popularity: 0.001836
First Submitted: 2015-07-09 03:48
Last Updated: 2016-01-09 17:51

Dependencies (33)

Required by (24)

Sources (6)

Pinned Comments

pypi commented on 2016-04-09 03:00

"KeyError: 'Debug'" failures appear to be a race condition (on 'slower' machines); rebuild until it goes away (unless you can track it down :D).

The release schedule is based on the ozone-wayland project's releases, *not* Chromium's releases, mostly because it takes ages to build and I'd rather have something that does work...

EDIT: I've disowned the package since I'm not updating it (no recent upstream release so the version is fairly ancient, and it doesn't look like there will be a release as all the work is going into upstreaming it into chromium).

Latest Comments

1 2 3 Next › Last »

pypi commented on 2016-12-09 22:33

@YAOMTC: I'm not planning on doing a new release any time soon, especially since the version used here is ancient, but you should be able to fix the that build issue by either downgrading CUPS or applying the patch from

Hopefully upstreaming continues!

YAOMTC commented on 2016-12-09 22:16

Well, I tried building this, but when I wasn't running into the "KeyError: 'Debug'" failure, it was "ninja: build stopped: subcommand failed".

I might just wait for Chromium to get Wayland support, which looks like it shouldn't be too long...

10ne1 commented on 2016-10-06 07:56

Great news: An important chunk of ozone-wayland has been merged in Chromium mainline last week [1]. The remaining work on review has been rebased and is waiting review.

Hopefully in the not too distant future we can run chromium mainline with both x11 and wayland at the same time and not be stuck on an older version using the ozone-wayland repo.


10ne1 commented on 2016-06-20 22:45

@pypi Thanks for the info! It's really cool that they're upstreaming right this moment. I wonder if I take those two large diffs on review and apply them on chromium-dev how would it work...

pypi commented on 2016-06-20 20:25

@adirat: Said article was also wrong :)
Upstreaming is still ongoing, see,

The work going into chromium mentioned in the article came from a different source, *not* the ozone-wayland project, which had not got anything upstreamed; there are multiple people working on this!

10ne1 commented on 2016-06-20 08:19

AFAIK ozone-wayland was merged into mainline chromium starting with v50 and now the project is dead. This is why it has no releases anymore and is stuck at v48.


pypi commented on 2016-04-30 18:46

@wind0204: Glad you got it working!
It is rather buggy; see for an out of date list of bugs that we had found, and
The project itself appears to be lacking in manpower, which is probably the core issue.

wind0204 commented on 2016-04-30 11:32

I guess upgrading ninja from 1.6.0-2 to 1.7.1-1 did the job, or less likely changing march value to native and removing mtune clause in /etc/makepkg.conf

anyways, it's too buggy! how come it has got so many bugs in the very basic features? is it just me?

wind0204 commented on 2016-04-26 15:16

adding --no-parallel didn't help but the error message was different, it was 'Release' instead of 'Debug', thank you anyway pypi.

pypi commented on 2016-04-25 20:55

The problem appears to be similar to:

You could try building with --no-parallel added to the command line
for build/gyp_chromium; that may or may not help.
I'll have another go tracking down the root cause in the meantime, but
I'm not familiar with the gyp build system, and the error message is fairly cryptic...