list,
I have Freebsd7.2 and have gnome2 installed by pkg_add -r option , I
want to burn DVD's, someone advised me by using brasero I can erase/write
CD/DVDs
steps followed was
1. in rc.conf added
devfs_system_ruleset=local
2. in loader.conf
atapicam_load=YES
3 in /etc/devfs.conf
[local=10]
#DVD+RW
add path 'acd*' mode 0660 group operator
add path 'cd0' mode 0666 group operator
#CAM passthrough
add path 'pass0' mode 0666 group operator
add path 'xpt*' mode 0666 group operator
[r...@kk /dev]# camcontrol devlist
HL-DT-ST DVDRAM GSA-4083N 1.08 at scbus0 target 0 lun 0 (cd0,pass0)
I inserted my dvd rw disk which has some .avi files, then launced
brasero fromgnome--applications--soundvideo--brasero disk burner
but from tools --erase I cant blank my DVD RW becoz no available disc
in Select a disc dialog screen in brasero.
How can I make brasero to doblank and burn DVDs successfully ?
Any hints most welcome from .
Thanks in advance
Dhanesh
For your information this is the debug output
r...@kk]# brasero -gb
hat 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.)
GConf 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.)
GConf 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.)
GConf 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.)
GConf 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.)
GConf 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.)
GConf 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.)
GConf 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
