From owner-freebsd-chromium@FreeBSD.ORG Tue Nov 19 22:37:09 2013 Return-Path: Delivered-To: chromium@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 317CF1BA for ; Tue, 19 Nov 2013 22:37:09 +0000 (UTC) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id D3AA222C8 for ; Tue, 19 Nov 2013 22:37:08 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id rAJMAcwH008655 for ; Tue, 19 Nov 2013 14:10:38 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <528BE1DE.6010807@rawbw.com> Date: Tue, 19 Nov 2013 14:10:38 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: chromium@FreeBSD.ORG Subject: Chrome can't work from another user account due to DBus issue Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Nov 2013 22:37:09 -0000 I have kde4 running, but am trying to run chrome from another user that is allowed to connct to X. Chrome window opens and browsing works. However, when I go to Settings, and click on "Change proxy settings", I get chrome fail with the message below. It probably tries to retrieve the proxy settings from kde, but fails in the middle due to the permission issue I guess. It should either successfully retrieve settings, or fall back to the situation when there is no dbus available. Yuri --- messages --- $ chrome [57448:302067712:1119/135751:ERROR:bus.cc(395)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [57448:302067712:1119/135751:ERROR:native_backend_kwallet_x.cc(227)] Error contacting kwalletd (isEnabled) [57448:302067712:1119/135751:ERROR:bus.cc(395)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [57448:302067712:1119/135751:ERROR:native_backend_kwallet_x.cc(195)] Error contacting klauncher to start kwalletd [57448:302019584:1119/135751:ERROR:unix_domain_socket_util.cc(132)] connect /tmp/9C48171B049D4DBEEC459BB7D55695C9FD6EB90E.31.0.1650.57_service_ipc: No such file or directory Qt: Session management error: Could not open network socket kcmshell(57486)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'kcmshell4' crashing... KCrash: Attempting to start /usr/local/kde4/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/yuri1/.kde4/socket-eagle.yuri.org/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/local/kde4/lib/kde4/libexec/drkonqi directly drkonqi(57487)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch)