2014-09-24 21:56 GMT+02:00, Patrick Matthäi pmatth...@debian.org:
Am 21.07.2014 um 16:34 schrieb Andrey Gursky:
Hi,
on Jessie amd64 with
fglrx 14.4.2-1
xserver-xorg 1.15.1-1
chromium 36.0.1985.36-1 is the last one that crashes, 36.0.1985.84-1
is the next one available on amd64 that
Am 21.07.2014 um 16:34 schrieb Andrey Gursky:
Hi,
on Jessie amd64 with
fglrx 14.4.2-1
xserver-xorg 1.15.1-1
chromium 36.0.1985.36-1 is the last one that crashes, 36.0.1985.84-1
is the next one available on amd64 that doesn't crash anymore, such as
newer beta releases.
A drawback:
Hi,
on Jessie amd64 with
fglrx 14.4.2-1
xserver-xorg 1.15.1-1
chromium 36.0.1985.36-1 is the last one that crashes, 36.0.1985.84-1
is the next one available on amd64 that doesn't crash anymore, such as
newer beta releases.
A drawback: WebGL support is disabled. Turning it on with
chrome://flags
Previous ways explained before to start chromium failed for me, this one
worked:
chromium --blacklist-accelerated-compositing
This is the error that appears when chromium without parameters is started:
[12850:12850:0611/103331:ERROR:component_loader.cc(138)] Failed to parse
extension
Hi,
I'm using skype as untrusted user and have no problems (but I'm also
on i386), still chromium make X segfault because a safe configuration
for the user is missing, I'm trying to fix that but currently the only
way I found is to edit /usr/bin/chromium and add
On Fri, Apr 25, 2014 at 05:14:54PM +0200, Andrey Gursky wrote:
Hi,
with fglrx 14.4~rc1.0.apr17-1 and Xorg 1.15.1 just starting chromium
(and for sure skype also) still crashes the X:
I'm using skype as untrusted user and have no problems (but I'm also
on i386), still chromium make X segfault
Hi,
with fglrx 14.4~rc1.0.apr17-1 and Xorg 1.15.1 just starting chromium
(and for sure skype also) still crashes the X:
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x48) [0x7fb92a5fde58]
1: /usr/bin/X (0x7fb92a456000+0x1abb49) [0x7fb92a601b49]
2: /lib/x86_64-linux-gnu/libpthread.so.0
Launching chromium on a fresh install (without ~/.config/chromium) or
with the default config give me this segfault:
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7750c0f]
1: /usr/bin/X (0xb75a9000+0x1ab9e4) [0xb77549e4]
2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb758740c]
3:
My apologies for such a generic subject for a bug.
The bug I had when this was opened was something preventing me from
loading the desktop and has been fixed, gone.
The bug with chromium is something different.
I've debootstrapped a jessie today on a ssd, then dist-upgraded to
sid, now I've two
Version: 1:14.1~beta1.3-1
radeon hd7850
Xorg segfault
Version: 1:14.2~beta1.3-1
radeon hd7850
Xorg segfault
Version: 1:14.3~beta1.3-1
radeon hd7850
Xorg WORKS!
Thanks :-)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
sounds nice, but where can i get 1:14.3~beta1.3-1?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I'am very sorry. I mean version from sid:
1:14.3~beta1.0-1
:-)
My mistake
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
VLC and and Mplayer work for me too (fglrx 1:14.3~beta1.0-1 with Radeon
HD5850), but when i open a Website with Google Chorme (not Chromium)
wich contains Flash, i get this seg-fault. Other browser, wich not use
pepperflash but the default-Flash without hardware-acceleration, all
works fine.
Package: fglrx-driver
Version: 1:14.1~beta1.3-1
Severity: important
Dear Maintainer,
* What led up to the situation?
dist-upgrade
* What was the outcome of this action?
no desktop (Xorg exit), vt still working
* What outcome did you expect instead?
working desktop...
--
14 matches
Mail list logo
