Issue 125060 in chromium: Theming completely broken after 20.0.1115.0

6 views
Skip to first unread message

chro...@googlecode.com

unread,
Apr 25, 2012, 4:59:45 PM4/25/12
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: OS-Linux Area-Undefined Type-Bug Pri-2

New issue 125060 by andreas....@gmail.com: Theming completely broken after
20.0.1115.0
http://code.google.com/p/chromium/issues/detail?id=125060

Chromium Version : 20.0.1116.0
URLs (if applicable) : n/a
Other browsers tested: n/a

What steps will reproduce the problem?
1. Start Chromium

What is the expected result?
Theme shows fine.

What happens instead?
See screenshots — almost everything "themed" is completely red (even when
using the GTK+ theme); load animations flicker.

The console repeats these three messages hundreds of times:
[15175:15175:31285407063:ERROR:resource_bundle.cc(97)] Failed to load
/usr/lib/chromium-dev/theme_resources_standard.pak
Some features may not be available.
[15175:15175:31285407334:ERROR:resource_bundle.cc(97)] Failed to load
/usr/lib/chromium-dev/ui_resources_standard.pak
Some features may not be available.
(chromium:15175): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without
calling gdk_pixbuf_loader_close() - this is not allowed. You must
explicitly end the data stream to the loader before dropping the last
reference.

Attachments:
gtk.png 31.9 KB
james_white.png 37.7 KB

chro...@googlecode.com

unread,
Apr 25, 2012, 5:21:45 PM4/25/12
to chromi...@chromium.org

Comment #1 on issue 125060 by andreas....@gmail.com: Theming completely
Since the title is a bit ambiguous: 20.0.1114.0 was fine. The two files in
the errors are indeed gone; the only two other pak files next to chrome.pak
are content_resources.pak and resources.pak.

(Arch Linux x64; Chromium built with GCC 4.7.0; no dependencies changed it
the last couple of days.)

chro...@googlecode.com

unread,
Apr 25, 2012, 6:21:46 PM4/25/12
to chromi...@chromium.org

Comment #2 on issue 125060 by andreas....@gmail.com: Theming completely
Apparently due to commit 133613, considering its changes to FILES.cfg and
resource_bundle_linux.cc: https://chromiumcodereview.appspot.com/10024050/

chro...@googlecode.com

unread,
Apr 26, 2012, 5:59:20 AM4/26/12
to chromi...@chromium.org

Comment #3 on issue 125060 by andreas....@gmail.com: Theming completely
Sorry for being hasty; this was simply a case of outdated build script. The
two files just weren't copied.

Please close this as invalid.

chro...@googlecode.com

unread,
Apr 26, 2012, 6:21:30 AM4/26/12
to chromi...@chromium.org

Comment #4 on issue 125060 by andriy.u...@gmail.com: Theming completely
Same problem appeared in 20.0.1116.0-154.1 (openSUSE 11.4)

chro...@googlecode.com

unread,
Apr 26, 2012, 9:19:49 AM4/26/12
to chromi...@chromium.org
Updates:
Owner: sa...@chromium.org

Comment #5 on issue 125060 by dhar...@chromium.org: Theming completely
(No comment was entered for this change.)

chro...@googlecode.com

unread,
Apr 26, 2012, 9:23:51 AM4/26/12
to chromi...@chromium.org

Comment #6 on issue 125060 by knur...@gmail.com: Theming completely broken
after 20.0.1115.0
http://code.google.com/p/chromium/issues/detail?id=125060

same issue here on openSUSE 12.1 and openSUSE Tumbleweed. Build
20.0.1116.0-154

chro...@googlecode.com

unread,
Apr 26, 2012, 12:25:53 PM4/26/12
to chromi...@chromium.org
Updates:
Status: Duplicate
Mergedinto: 125056

Comment #7 on issue 125060 by sa...@chromium.org: Theming completely broken
after 20.0.1115.0
http://code.google.com/p/chromium/issues/detail?id=125060

chro...@googlecode.com

unread,
Apr 28, 2012, 3:28:46 PM4/28/12
to chromi...@chromium.org

Comment #8 on issue 125060 by Megagree...@gmail.com: Theming completely
i can confirm this bug too:
Gentoo ~x86
chromium - [1115-1120]
//sorry my bad english

chro...@googlecode.com

unread,
Apr 28, 2012, 4:11:33 PM4/28/12
to chromi...@chromium.org

Comment #9 on issue 125060 by Megagree...@gmail.com: Theming completely
oops
doins out/Release/ui_resources_standard.pak || die
doins out/Release/theme_resources_standard.pak || die
work fine
//sorry my bad english

Reply all
Reply to author
Forward
0 new messages