Bug 432445

Summary: yast shows GVFS warning dialog
Product: [openSUSE] openSUSE 11.1 Reporter: Alberto Passalacqua <alberto.passalacqua>
Component: YaST2Assignee: Hans Petter Jansson <hpj>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P1 - Urgent CC: dmacvicar, forgotten_h13THG8RK1, hpj, michael.monreal
Version: Beta 2   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Yast-gtk GVFS warning message
Yast2 logs

Description Alberto Passalacqua 2008-10-06 03:45:51 UTC
A dialog box with a warning message related to GVFS is shown when a module in Yast-gtk is launched (see screenshot for the full message).

Regards,
Alberto
Comment 1 Alberto Passalacqua 2008-10-06 03:46:29 UTC
Created attachment 243538 [details]
Yast-gtk GVFS warning message
Comment 2 Forgotten User h13THG8RK1 2008-10-06 14:40:52 UTC
Alberto, please run "/sbin/save_y2logs" and attach the output. Also, check if the error happens only when you run a tool from "/sbin/yast2" or when you a run tool directly through "/sbin/yast2 users" as well.

Anyway, I have no idea what it is and it seems unlikely it is specific to the GTK UI. If none of the yast guys have a clue, send this to Gnome. There are a lot of Gnome craziness going on like bug 428963.
Comment 3 Alberto Passalacqua 2008-10-07 01:59:27 UTC
Created attachment 243785 [details]
Yast2 logs

Hi Ricardo,
I attach the logs.

If I run /sbin/yast2 users, I get an error message who tells that the MIT cookie is invalid, and the connection to X is refused.

Regards,
Alberto
Comment 4 Hans Petter Jansson 2008-10-07 07:59:44 UTC
The GVFS warning message looks like it stems from a problem with root authenticating to the user's D-Bus. Could even be related to the X cookie.
Comment 5 JP Rosevear 2008-10-07 13:37:00 UTC
*** Bug 428967 has been marked as a duplicate of this bug. ***
Comment 6 Hans Petter Jansson 2008-10-08 05:56:44 UTC

*** This bug has been marked as a duplicate of bug 428963 ***