On Fri, Sep 6, 2019 at 5:06 PM Ernestas Kulik wrote:
> On Fri, 2019-09-06 at 14:26 +, Zbigniew Jędrzejewski-Szmek wrote:
> > Hi,
> >
> > I upgraded to F31 recently, and I now I noticed that the gnome top
> > bar is always black. I miss the old translucent blue bar that would
> > only go black
On Wed, May 29, 2019 at 2:59 PM Tomas Popela wrote:
> I will mail some Chromium devs to consider backporting it.
>
It has been merged to Chromium 75 (
https://bugs.chromium.org/p/chromium/issues/detail?id=956644#c16 ) and will
be released next week when the Chrome 75 will be promoted to
On Wed, May 29, 2019 at 2:53 PM Tomas Popela wrote:
> it's this bug -
> https://bugs.chromium.org/p/chromium/issues/detail?id=949312 . It will
> probably be fixed in Chrome 76+ (current stable is Chrome 74), so that
> means it will take few months (unless someone from Chromi
Hi Brian,
it's this bug - https://bugs.chromium.org/p/chromium/issues/detail?id=949312 .
It will probably be fixed in Chrome 76+ (current stable is Chrome 74), so
that means it will take few months (unless someone from Chromium team
backports it).
Tom
On Wed, May 29, 2019 at 2:41 PM Brian (bex)
It was done by Patrick Uiterwijk (who's CC'ed).
Tom
On Mon, May 27, 2019 at 5:09 AM Chris Murphy
wrote:
> I filed a bug here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1714062
>
> However since that assigns it to mbriza who doesn't do binary signing
> for Windows or macOS, I'm not certain t
On Tue, May 29, 2018 at 8:23 PM, Simo Sorce wrote:
>
> Is screen sharing [at least of its own window(s)] supposed to work ?
> If I share the screen with a screen sharing app all I get to send is a
> black background, sometimes with the mouse cursor visibile on it.
>
No, that won't work because th
Hi everyone,
just a heads-up that we are going to rename the webkitgtk4 package to
webkit2gtk3 in the rawhide - please see [0]. I will take care of updating
the BR for the packages under gnome-sig myself and for others I will create
a PR.
$ dnf repoquery --whatrequires webkitgtk4 --arch x86_64
--
On Wed, Dec 13, 2017 at 1:17 PM, Sérgio Basto wrote:
> On Wed, 2017-12-13 at 12:58 +0100, Tomas Popela wrote:
> > On Wed, Dec 13, 2017 at 11:54 AM, Sérgio Basto
> > wrote:
> > > BTW , I checked debian package and they build webkit2gtk3 and
> > > webkit2gtk2 [1]
On Wed, Dec 13, 2017 at 11:54 AM, Sérgio Basto wrote:
> BTW , I checked debian package and they build webkit2gtk3 and webkit2gtk2
> [1] and also his naming looks better ;) (webkit2gtk-4.0) .
> So I would suggest webkit2gtk3-4.0 , webkit2gtk2-4.0 and webkit2gtk4-4.0
>
Just a note - there is nothi
Hi,
On Sat, Dec 9, 2017 at 5:06 PM, Neal Gompa wrote:
> On Fri, Dec 8, 2017 at 10:16 PM, Sérgio Basto wrote:
> > Thank you Michael , btw about package naming IMHO webkitgtk4 should be
> > called webkit2gtk3 and for gtk4 webkit2gtk4
> >
>
> The webkitgtk4-devel package already provides pkgconfig
On Thu, 2016-03-17 at 00:15 +0100, Marcin Juszkiewicz wrote:
> W dniu 16.03.2016 o 19:19, Tom Callaway pisze:
> >
> > And of course:
> >
> > chromium:https://bugzilla.redhat.com/show_bug.cgi?id=1270322
> qt5-qtwebengine contains chromium source code already so it may be good
> to check how it wa
On Mon, 2015-12-28 at 14:24 -0600, Michael Catanzaro wrote:
> This mail is in regards to WSA-2015-0002: http://webkitgtk.org/securi
> ty
> /WSA-2015-0002.html
>
> In short, we have by my count:
>
> * Zero CVEs affecting the webkitgtk4 package in F23
> * 40 CVEs affecting the webkitgtk4 package in
Hi,
On Sat, 2016-01-02 at 16:16 -0600, Michael Catanzaro wrote:
> Looking over the list, most of the impacted software we could live
> without, or stands a good chance of being ported in time. Evolution is
> mostly ported upstream, as is Midori.
Evolution's WebKit 2 port is targeted to be finishe
13 matches
Mail list logo
