| 1 |
Am 25.01.2015 um 11:08 schrieb victor romanchuk: |
| 2 |
> On 01/24/2015 07:44 PM, Peter Humphrey wrote: |
| 3 |
>> On Saturday 24 January 2015 16:43:41 Nils Holland wrote: |
| 4 |
>> |
| 5 |
>>> I've been using chromium successfully on my ~x86 system for quite a |
| 6 |
>>> long time, but starting with the last two updates that came in during |
| 7 |
>>> the last few days (namely, chromium-40.0.2214.85 and |
| 8 |
>>> chromium-40.0.2214.91), I started having problems. |
| 9 |
>> --->8 |
| 10 |
>>> The question, thus, would probably be: Anyone using one of the recent |
| 11 |
>>> chromium-40 versions on ~x86 or anywhere else and seeing something |
| 12 |
>>> similar? Or probably someone who has experienced something like that |
| 13 |
>>> before and could offer a guess what might be wrong here - a real bug, |
| 14 |
>>> custom-cflags, or something entirely different? |
| 15 |
>> This is and amd64 box, not ~x86, but chromium-40.0.2214.91 is working fine |
| 16 |
>> here. It's not been running more than a few hours since today's upgrade, but |
| 17 |
>> at least it does run. |
| 18 |
>> |
| 19 |
> Also amd64: I observed another issue with chromium-40.0.2214.91 -- it breaks X11 with compositing wm |
| 20 |
> (i'm running compiz) when I activate any simple effect, e.g switch to another viewpoint or something |
| 21 |
> like that. At now catched that with Nvidia; have not tried with i915 (yet). |
| 22 |
> |
| 23 |
|
| 24 |
works fine with KDE and desktop effects turned on. Using xorg's amd |
| 25 |
drivers. Runs on for days without problems. |
| 26 |
|
| 27 |
www-client/chromium |
| 28 |
Available versions: 40.0.2214.91 |
| 29 |
Installed versions: 40.0.2214.85^d{tbz2}(17:00:07 19.01.2015) |
Archives