From owner-freebsd-questions@FreeBSD.ORG Sat Oct 16 19:45:04 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90EC9106567A for ; Sat, 16 Oct 2010 19:45:04 +0000 (UTC) (envelope-from mbeis@xs4all.nl) Received: from smtp-vbr16.xs4all.nl (smtp-vbr16.xs4all.nl [194.109.24.36]) by mx1.freebsd.org (Postfix) with ESMTP id 235768FC1A for ; Sat, 16 Oct 2010 19:45:01 +0000 (UTC) Received: from yokozuna.lan (213-84-73-82.adsl.xs4all.nl [80.101.78.208]) by smtp-vbr16.xs4all.nl (8.13.8/8.13.8) with ESMTP id o9GJOxat051835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 16 Oct 2010 21:24:59 +0200 (CEST) (envelope-from mbeis@xs4all.nl) Received: from yokozuna.lan (yokozuna.lan [IPv6:::1]) by yokozuna.lan (8.14.4/8.14.4) with ESMTP id o9GJOwC2071530 for ; Sat, 16 Oct 2010 21:24:58 +0200 (CEST) (envelope-from mbeis@xs4all.nl) Date: Sat, 16 Oct 2010 21:24:58 +0200 (CEST) From: Marco Beishuizen Sender: marco@yokozuna.lan To: freebsd-questions@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Virus-Scanned: by XS4ALL Virus Scanner Subject: chromium crashes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marco Beishuizen List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Oct 2010 19:45:04 -0000 Hi, I tried to run chromium as browser today but it crashes immediately: ... [1016/211130:WARNING:base/debug_util_posix.cc(228)] Don't know how to do this The program 'chrome' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAccess (attempt to access private resource denied)'. (Details: serial 741 error_code 10 request_code 139 minor_code 1) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) marco@yokozuna:~% opera opera [crash logging]: Can't read kernel memory: : /dev/mem: Permission denied opera [crash logging]: CRASH!! got signal SIGSEGV at address 298C9B5D ... Has anyone else has this too? Thanks in advance. Regards, Marco -- He who has imagination without learning has wings but no feet.