my mint has been sooo buggy i don't know why i didn't upgrade i fresh installed maya. i should start another thread but you seem to always answer tobi so i'll just post this here if thats ok.
while i was editing fstab before i used nano i tried to gksu caja to do it in the gui for some reason and got the following error.
keep in mind this persisted through a reboot and also never did this before because i always ued gksu caja to get write permissions on my external hd w/ no issue. i see no d-bus daemon running why and how do i restart it. unrelated i was getting dbus issues connecting wireless w/ wicd on a diff OS the other day. is my hardware failing or is this all coincidence.
****note****
i can launch using "dbus-launch gksu caja" but why do i need to do it that way. just "gksu caja" gives following>>
------------
(gksu:3764): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
GConf Error: No D-BUS daemon running
(gksu:3764): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
GConf Error: No D-BUS daemon running
(gksu:3764): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
GConf Error: No D-BUS daemon running
(gksu:3764): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
GConf Error: No D-BUS daemon running
(gksu:3764): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(caja:3765): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported
(caja:3765): Eel-WARNING **: MateConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
(caja:3765): Eel-WARNING **: MateConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
(caja:3765): Eel-WARNING **: MateConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
(caja:3765): Eel-WARNING **: MateConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf warning: failure listing pairs in `/apps/caja/preferences': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/desktop/mate/file_views': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/desktop/mate/background': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/desktop/mate/lockdown': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/apps/caja/desktop': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/apps/caja/icon_view': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/apps/caja/desktop-metadata': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
(caja:3765): Unique-DBus-WARNING **: Unable to open a connection to the session 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.
(caja:3765): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
(caja:3765): Unique-DBus-WARNING **: Unable to open a connection to the session 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.
(caja:3765): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
linuxubuntu minty33 is online now Report This Post
