Package Details: chromium-dev 126.0.6423.2-1

Git Clone URL: https://aur.archlinux.org/chromium-dev.git (read-only, click to copy)
Package Base: chromium-dev
Description: The open-source project behind Google Chrome (Dev Channel)
Upstream URL: http://www.chromium.org
Keywords: browser web
Licenses: BSD
Submitter: None
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 160
Popularity: 0.010897
First Submitted: 2010-05-17 09:04 (UTC)
Last Updated: 2024-04-21 19:18 (UTC)

Dependencies (84)

Required by (0)

Sources (13)

Latest Comments

« First ‹ Previous 1 .. 80 81 82 83 84 85 86 87 88 89 90 .. 152 Next › Last »

sl1pkn07 commented on 2013-03-02 11:29 (UTC)

yes, i see http://wstaw.org/m/2013/03/02/plasma-desktopj22940.png for my it's not bad, but could be better

wuffleton commented on 2013-03-02 03:01 (UTC)

Is it just me, or does the new version ignore system font settings and/or uses a horrid font for tab titles? I've noticed that the tab title text is much blurrier and narrower in this build.

sl1pkn07 commented on 2013-03-02 00:24 (UTC)

are?? not include?? :S sorry guys. i don't know in my local copy have include it :S updating

jeagoss commented on 2013-03-02 00:14 (UTC)

I experienced the same issue as SirWuffleton. After adding jsoncpp to the depends array and adding jsoncpp to my system from AUR, everything worked just fine. sl1pkn07, you might update the depends array to include jsoncpp

sl1pkn07 commented on 2013-03-01 22:41 (UTC)

jsoncpp is as dependency

wuffleton commented on 2013-03-01 22:34 (UTC)

In that case, could it be that jsoncpp is a dependency? There exists a jsoncpp package in the AUR, and the presence of such a package is usually implied by use_system_X=1 I'm currently testing this theory to see if that's the issue.

sl1pkn07 commented on 2013-03-01 22:29 (UTC)

change use_system_jsoncpp=1 to use_system_jsoncpp=0 but build without any probelm for me :S (always build, install and test chromium by myseft before update, is some cases several times, if have error don't upload)

wuffleton commented on 2013-03-01 22:28 (UTC)

@sl1pkno7: It's only happening for me on the new version (27.0.1425.2-1) The previous version didn't have this issue and compiled without a problem.