Brasero can't detect my DVD RW disc to erase and make it blank
dhaneshk k
dhaneshkk at hotmail.com
Sun Feb 21 11:47:47 UTC 2010
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
[root at 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 from gnome-->applications-->sound&video-->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 do blank and burn DVDs successfully ?
Any hints most welcome from .
Thanks in advance
Dhanesh
For your information this is the debug output
root at 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 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 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 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.)
(brasero:1690): GConf-WARNING **: Directory `/apps/brasero' was not being monitored by GConfClient 0x29719210
(brasero:1690): BraseroBurn-DEBUG: At burn-basics.c:94: Initializing Brasero-2.26.0
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin-manager.c:419: opening plugin directory /usr/local/lib/brasero/plugins
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin-manager.c:441: loading /usr/local/lib/brasero/plugins/libbrasero-burn-uri.so
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3079: New caps required Image BIN CUE CDRDAO CLONE format accepts files
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3139: Created new caps Image BIN CUE CDRDAO CLONE
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3265: New caps required Data ISO UDF SYMLINK Level 3 JOLIET VIDEO DEEP
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1034: Module CD/DVD Creator Folder successfully loaded
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1050: Creating default priority key /apps/brasero/config/priority/CD at 47@DVD at 32@Creator at 32@Folder-misc
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin-manager.c:441: loading /usr/local/lib/brasero/plugins/libbrasero-cdrdao.so
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD W appendable with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD W appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD W appendable with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD W closed with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD W closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD W closed with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD RW appendable with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD RW appendable with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD RW closed with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD RW closed with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD ROM closed with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD ROM closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD ROM closed with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3079: New caps required Image CDRDAO format accepts files
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD W blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc CD RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3079: New caps required Image CUE CDRDAO format accepts files
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW appendable with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW appendable with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW closed with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW closed with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW closed with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW closed with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW appendable with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW appendable with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1034: Module Cdrdao successfully loaded
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1050: Creating default priority key /apps/brasero/config/priority/Cdrdao-burn
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin-manager.c:441: loading /usr/local/lib/brasero/plugins/libbrasero-cdrecord.so
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3079: New caps required Image BIN format accepts files pipe
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD + W appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD + W blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD + RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD + RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD - (sequential) W appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD - (sequential) W blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD - (sequential) RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD - (sequential) RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD - (sequential) RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD W appendable with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD W appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD W appendable with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD W blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW appendable with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW appendable with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3158: New caps required Audio RAW 44100 Metadata Information format accepts files pipe
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3246: Created new caps Audio RAW 44100 Metadata Information
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3158: New caps required Audio RAW 44100 format accepts files pipe
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3246: Created new caps Audio RAW 44100
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD W blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3079: New caps required Image CUE CLONE format accepts files
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD + RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD + RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD + RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD - (sequential) RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD - (sequential) RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD - (sequential) RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD - (sequential) RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD - (sequential) RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD - (sequential) RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD - (sequential) RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD - (sequential) RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD + RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD + RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD + RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW appendable with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW appendable with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW closed with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW closed with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW closed with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW closed with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW appendable with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc CD RW appendable with data with audio
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1034: Module cdrecord successfully loaded
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1050: Creating default priority key /apps/brasero/config/priority/cdrecord-burn
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin-manager.c:441: loading /usr/local/lib/brasero/plugins/libbrasero-checksum-file.so
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3265: New caps required Data ISO UDF SYMLINK Level 3 JOLIET VIDEO DEEP
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD DL + W appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD DL + W closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD DL + RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD + W appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD + W closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD + RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD - (restricted) RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD DL - (sequential) W appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD DL - (sequential) W closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD - (sequential) W appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD - (sequential) W closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD - (sequential) RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD - (sequential) RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD W appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD W closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc CD RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1034: Module File Checksum successfully loaded
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1050: Creating default priority key /apps/brasero/config/priority/File at 32@Checksum-misc
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin-manager.c:441: loading /usr/local/lib/brasero/plugins/libbrasero-checksum.so
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3079: New caps required Image BIN format accepts files pipe
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1034: Module Image Checksum successfully loaded
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1050: Creating default priority key /apps/brasero/config/priority/Image at 32@Checksum-misc
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin-manager.c:441: loading /usr/local/lib/brasero/plugins/libbrasero-dvdauthor.so
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1030: Module encountered an error while registering its capabilities:
"dvdauthor" could not be found in the path
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin-manager.c:469: Load failure, no GType was returned "dvdauthor" could not be found in the path
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin-manager.c:441: loading /usr/local/lib/brasero/plugins/libbrasero-dvdcss.so
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1030: Module encountered an error while registering its capabilities:
Encrypted DVD: please install libdvdcss version 1.2.x
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin-manager.c:469: Load failure, no GType was returned Encrypted DVD: please install libdvdcss version 1.2.x
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin-manager.c:441: loading /usr/local/lib/brasero/plugins/libbrasero-dvdrwformat.so
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc BD DL RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc BD DL RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc BD DL RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc BD RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc BD RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc BD RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD DL + RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD DL + RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD DL + RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD + RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD + RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD + RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD - (restricted) RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD - (restricted) RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD - (restricted) RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD DL - (sequential) W appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD DL - (sequential) W closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3358: Created Disc DVD DL - (sequential) W blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD - (sequential) RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD - (sequential) RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD - (sequential) RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3346: Retrieved Disc DVD - (sequential) RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD - (sequential) RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD - (sequential) RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD - (sequential) RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD - (sequential) RW appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD DL - (sequential) W blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD DL - (sequential) W closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD DL - (sequential) W appendable with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD - (restricted) RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD - (restricted) RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD - (restricted) RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD + RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD + RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD + RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD DL + RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD DL + RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc DVD DL + RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc BD RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc BD RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc BD RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc BD DL RW blank
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc BD DL RW blank Unformatted
(brasero:1690): BraseroBurn-DEBUG: At burn-caps.c:3460: Adding blank caps for Disc BD DL RW closed with data
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1034: Module dvd+rw-format successfully loaded
(brasero:1690): BraseroBurn-DEBUG: At burn-plugin.c:1050: Creating default priority key /apps/brasero/config/priority/dvd at 43@rw-format-bu
[1]+ Stopped brasero -gb | less
[root at kk /dev]# camcontrol devlist
<HL-DT-ST DVDRAM GSA-4083N 1.08> at scbus0 target 0 lun 0 (cd0,pass0)
[root at kk /dev]# brasero -gb >brassero_debug.txt
su: brassero_debug.txt: Operation not supported
[root at kk /dev]# brasero -gb| > brassero_debug.txt
su: brassero_debug.txt: Operation not supported
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.)
(brasero:1728): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: 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.
(brasero:1728): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: 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 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 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 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 blocked the reply, the reply timeout expired, or the network connection was broken.)
(brasero:1728): GConf-WARNING **: Directory `/apps/brasero' was not being monitored by GConfClient 0x29719210
_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
More information about the freebsd-questions
mailing list