Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#15639 - [gnome-cups-manager] Failed to contact configuration server
Attached to Project:
Community Packages
Opened by Artiom Molchanov (artiom) - Wednesday, 22 July 2009, 15:37 GMT
Last edited by Allan McRae (Allan) - Saturday, 19 September 2009, 08:38 GMT
Opened by Artiom Molchanov (artiom) - Wednesday, 22 July 2009, 15:37 GMT
Last edited by Allan McRae (Allan) - Saturday, 19 September 2009, 08:38 GMT
|
DetailsDescription:
gnome-cups-manager give this error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: 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.) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: 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.) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: 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.) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: 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.) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: 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.) Additional info: gnome-cups-manager : 0.33-6 gconf : 2.26.2-2 dbusn : 1.2.14-1 Steps to reproduce: 1.Start System/Administration/Printing 2.Open a printer properties dialog 3. Press Become Administrator button |
This task depends upon
Closed by Allan McRae (Allan)
Saturday, 19 September 2009, 08:38 GMT
Reason for closing: Upstream
Additional comments about closing: gconf issue - see comment
Saturday, 19 September 2009, 08:38 GMT
Reason for closing: Upstream
Additional comments about closing: gconf issue - see comment
http://bugzilla.gnome.org/show_bug.cgi?id=555745