I can confirm that this is still an issue in Precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/596149
Title:
gdm can't login to any session
To manage notifications about this bug go to:
https:
This is unlikely to happen from the chromium side.
Most file handling code is written with cross-platform classes and I
don't know how I'd go about making it aware of a VFS. A (very quick)
glance over the gio interface makes me doubt we'll ever support it.
Theoretically, if the gnome vfs switched
Konqueror/Qt doesn't define symbols with the same names as functions in
GTK2. The problem is that the majority of functions in gtk2 and gtk3
have the same symbol names.
If Qt defined (for example) gtk_widget_show(), there'd be conflicts and
I'm pretty sure Konqueror wouldn't be able to run gtk2 pl
This isn't a chromium bug. Ambiance specifically requests similar colors
in Ambiance/gtk-2.0/apps/chromium.rc:
ChromeGtkFrame::frame-color = "#3c3b37"
ChromeGtkFrame::inactive-frame-color = lighter ("#3c3b37")
[...]
ChromeGtkFrame::incognito-frame-color = lighter ("#3c3b37")
ChromeGtkFra
Realistically, GTK3 isn't happening in chrome until GTK3 is in an LTS
version of Ubuntu, is common in other distributions, and a certain
proprietary browser plugin vendor has ported their very popular plugin
to GTK3 (because otherwise we'd have a process trying to link with both
versions of GTK).
This bug is two issues in different components.
The first part (chromium draws its custom window controls when maximized
in unity) was a problem with chromium and should be fixed in chromium
r83173, in case you guys want to backport it. (It also has some other
minor unity integration.)
The second
The problem has theoretically been fixed on and for the M12 branch.
It has not been fixed for M11 (and won't be) and can't be backported to
M10. Attached is a combined fix that I've tested on the M11 branch; it
should apply cleanly.
** Patch added: "Backport of changes from M12 to M11"
https:
This is a theoretical fix to the deadlock issue which should make it
onto the M12 branch (http://codereview.chromium.org/6878038/). It is not
entirely tested (and there's currently a weird crash regression in the
sync code on trunk right now). I'd like to hammer on it a little bit
more before I'd f
I don't know if this will be completely fixed before Natty ships, but
there's now an "Experimental GNOME menu bar support" in about:flags. The
menu bar is in flux and I haven't finalized a lot of the details, but
there's some support now.
--
You received this bug notification because you are a me
Public bug reported:
Binary package hint: light-themes
(Context: I'm the author of the Google Chrome GTK+ integration code.)
(Related fixed xubuntu bug:
https://bugs.launchpad.net/xubuntu-artwork/+bug/686239)
The current interaction between Ambiance and both Chrome 8 and 9 results
in a bright o
There currently aren't icon caches for Human or gnome on jaunty xubuntu:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.04
DISTRIB_CODENAME=jaunty
DISTRIB_DESCRIPTION="Ubuntu 9.04"
$ find /usr/share/icons -name "icon-theme.cache"
/usr/share/icons/hicolor/icon-theme.cache
/usr/share/ic
The Chromium project is interested in seeing this fixed. I would like to
turn the GTK interface on by default in Chromium and Google Chrome but
currently can't because our startup tests show a roughly 200ms
regression in startup time because of the lack of icon caches.
--
Gnome and Human icon the
12 matches
Mail list logo
