This should be resolved by future snapshots which will include
Mesa 10.2 instead of 10.4.
On Sat, Feb 21, 2015 at 05:55:21PM +, Brian wrote:
> As of the February 17th snapshot, I still see the black rectangle when I
> launch Chrome. I'm using xfce as my window manager and a radeon video (HD
As of the February 17th snapshot, I still see the black rectangle when I launch
Chrome. I'm using xfce as my window manager and a radeon video (HD 4600) card.
Using the disable-gpu option, I'm able to launch the browser, but now pages are
more likely to crash. Is Firefox now a better option?
On Wed, Jan 28, 2015 at 8:00 AM, Jonathan Gray wrote:
> On Wed, Jan 28, 2015 at 02:48:00AM -0500, STeve Andre' wrote:
> > On 01/28/15 02:27, Benoit Lecocq (BLQ) wrote:
> > >
> > >On 01/28/15 06:24, STeve Andre' wrote:
> > >>Chrome isn't working at the moment. The screen is sold black. If
> >
On Mon, Feb 16, 2015 at 06:16:15PM +0100, Giovanni Bechis wrote:
> On 02/16/15 18:04, Gilles Chehade wrote:
> > On Mon, Feb 16, 2015 at 05:17:27PM +0100, Mattieu Baptiste wrote:
> >> On Sat, Feb 14, 2015 at 7:06 PM, Marc Espie wrote:
> >>>
> >>> Probably not kernel... kernel from january first goe
On 02/16/15 18:04, Gilles Chehade wrote:
> On Mon, Feb 16, 2015 at 05:17:27PM +0100, Mattieu Baptiste wrote:
>> On Sat, Feb 14, 2015 at 7:06 PM, Marc Espie wrote:
>>>
>>> Probably not kernel... kernel from january first goes to the same black
>>> window.
>>>
>>
>> Hi,
>>
>> I'm seeing the "black
On Mon, Feb 16, 2015 at 05:17:27PM +0100, Mattieu Baptiste wrote:
> On Sat, Feb 14, 2015 at 7:06 PM, Marc Espie wrote:
> >
> > Probably not kernel... kernel from january first goes to the same black
> > window.
> >
>
> Hi,
>
> I'm seeing the "black window" issue since the Mesa update. Everythin
On Sat, Feb 14, 2015 at 7:06 PM, Marc Espie wrote:
>
> Probably not kernel... kernel from january first goes to the same black
> window.
>
Hi,
I'm seeing the "black window" issue since the Mesa update. Everything
was OK before.
This intel card works OK (with XFCE):
(full dmesg here: http://ww
On Sat, Feb 14, 2015 at 06:52:28PM +0100, Marc Espie wrote:
> On Sat, Feb 14, 2015 at 05:37:54PM +0200, Mihai Popescu wrote:
> > I see only a big black rectangle and nothing more but with
> > chromium-40.0.2214.111p0.
> >
> > Running snapshot ...
> >
> > OpenBSD 5.7-beta (GENERIC) #712: Fri Feb 1
On Sat, Feb 14, 2015 at 05:37:54PM +0200, Mihai Popescu wrote:
> I see only a big black rectangle and nothing more but with
> chromium-40.0.2214.111p0.
>
> Running snapshot ...
>
> OpenBSD 5.7-beta (GENERIC) #712: Fri Feb 13 12:20:07 MST 2015
> t...@i386.openbsd.org:/usr/src/sys/arch/i386/com
I see only a big black rectangle and nothing more but with
chromium-40.0.2214.111p0.
Running snapshot ...
OpenBSD 5.7-beta (GENERIC) #712: Fri Feb 13 12:20:07 MST 2015
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon X1650 Pro" rev
On Wed, Jan 28, 2015 at 07:00:32PM +1100, Jonathan Gray wrote:
> On Wed, Jan 28, 2015 at 02:48:00AM -0500, STeve Andre' wrote:
> > On 01/28/15 02:27, Benoit Lecocq (BLQ) wrote:
> > >
> > >On 01/28/15 06:24, STeve Andre' wrote:
> > >>Chrome isn't working at the moment. The screen is sold black.
* Jonathan Gray [28.01.2015 09:01]:
> It would be useful if people seeing this could mention what graphics
> hardware they are running and if they are using a self built version of
> xenocara with the Mesa update or the snapshots which seem to be lagging
> and don't have the Mesa update.
I see it
On Wed, Jan 28, 2015 at 07:00:32PM +1100, Jonathan Gray wrote:
> That is not a fix (and neither is --disable-gpu-compositing).
I have been running with --disable-gpu for months now due to chrome
failing to redraw. May be the same or a related bug?
https://code.google.com/p/chromium/issues/detail?
On 28 January 2015 at 03:00, Jonathan Gray wrote:
> On Wed, Jan 28, 2015 at 02:48:00AM -0500, STeve Andre' wrote:
>> On 01/28/15 02:27, Benoit Lecocq (BLQ) wrote:
>> >
>> >On 01/28/15 06:24, STeve Andre' wrote:
>> >>Chrome isn't working at the moment. The screen is sold black. If
>> >>I start
On 2015/01/28 19:00, Jonathan Gray wrote:
> The window manager used may matter as well, it seems chromium
> has had issues with non composited wms in the past.
I haven't checked this update yet, but there were definitely problems
with screen redraws with cwm amongst other WMs. If this is a suspect
On Wed, Jan 28, 2015 at 02:48:00AM -0500, STeve Andre' wrote:
> On 01/28/15 02:27, Benoit Lecocq (BLQ) wrote:
> >
> >On 01/28/15 06:24, STeve Andre' wrote:
> >>Chrome isn't working at the moment. The screen is sold black. If
> >>I start with chrome nytimes.com the title bar says New York Ti
On 01/28/15 02:27, Benoit Lecocq (BLQ) wrote:
On 01/28/15 06:24, STeve Andre' wrote:
Chrome isn't working at the moment. The screen is sold black. If
I start with chrome nytimes.com the title bar says New York Times,
so chrome is working but doesn't display.
I see an error message
On 01/28/15 06:24, STeve Andre' wrote:
>Chrome isn't working at the moment. The screen is sold black. If
> I start with chrome nytimes.com the title bar says New York Times,
> so chrome is working but doesn't display.
>
>I see an error message
>
> ATTENTION: default value of option
Chrome isn't working at the moment. The screen is sold black. If
I start with chrome nytimes.com the title bar says New York Times,
so chrome is working but doesn't display.
I see an error message
ATTENTION: default value of option force_s3tc_enable overridden by
environment.
[50:-195
19 matches
Mail list logo
